Skip to content
This repository has been archived by the owner on Aug 19, 2018. It is now read-only.

Roadmap

Ricky Curtice edited this page Sep 23, 2015 · 2 revisions

Welcome to our future hopes and goals! What you'll find below is a combination of arbitrary list and sequenced features to be worked on. Most, if not all, should have issue reports linked that give fuller detail.

Open tasks

These are tasks we have chosen to not work on ourselves but would love to see accomplished. Please, please dig in here! Of course there may be others working on the same task - the linked issue reports are excellent places to communicate about the issue. If there's no linked report, please make on and add the link!

As you'll see, the list is unsorted. There's no priority here, just a friendly list!

  • TODO

Feature list

This is roughly how the core development team prioritizes feature development. Note that this does not mean we are not interested in contributions in other areas, or contributions of low priority features. Contributions of any kind are always welcomed. But at the end of the day, it is better to have one feature 100% complete than two features 50% complete, which is why features should be prioritized and then worked on in order.

It is also a list that we are actively working on, so if you have an interest in helping with one of these, please contact us! Linked issue reports are excellent for communication on these.

Status key:

  • Ready: work has not yet started. Would you like to give it a go? Please do!
  • Active: work is proceeding, if you want to help please see the relevant issue report, pull request, and/or development fork!
  • Done: yay! It's completed! Done items will be purged from this list every release.

Priority key:

  • High: we want to see this in the next release if at all possible.
  • Medium: we want this in the next release, but not at the expense of High Priority items.
  • Normal: we are working on it, but it may not happen in the next release.

Note the lack of a "Low" priority. That is because there's no such thing as "Low" - it is either a priority or not. If not, then it might qualify as an open task or it's time to let it go visit its friends on the floor and be cut.

Feature Status Priority Comments
Expose Grid Name through llGetEnv Ready Normal
Add Support for Inventory Archive Ready Normal

Features we don't want

This isn't a list you'll often find in an open-source project. However as anyone who's developed a project knows, features can tend to creep. It's often very useful to have a list of features you are not interested in having pursued - this way time and energy are concentrated in a common direction. If you find something here that you'd really like to see implemented, and you have the wherewithal to give it a go, by all means do, even use the issue tracker to communicate. However, please understand that the likelihood of a pull request for one of these features being accepted is very low - though not impossible!

  • ...