From time to time ideas for features and plug-ins are raised in the forum that are already on the roadmap or are acknowledged by core developers to be desirable. The core developers have proven themselves to be a very talented and dedicated group. But each has only two hands and 24 hours in the day. The question arises: how to expose the vision and expertise of the core developers in order to leverage the talents and energies of the wider community. In other words, how can developers in the community effectively contribute code to the framework that is in line with its fundamental vision?
Although documentation is slim (but growing!), a developer can readily produce components and other plug-ins. But if the developer is hungry to use Tin Can or variables or some feature of this significance, he or she has to either sit back and wait or invest much time working alone at a solution that, in the end, may conflict with the requirements of other modules on the roadmap.
Brainstorm: Is there value in gathering core developers and other interested parties (a) to identify desirable but not yet developed features/modules, and then for each (b) architect a development strategy at any level that seems appropriate—with the outcome to be made available to the community.
The outcome for each might be a statement that includes any number of things: preferred libraries, links to APIs, outlines of necessary steps in code development, traps to avoid, perhaps some pseudo-code. Maybe a repository can be established for each to serve as a base for development. It could include this output; maybe in some cases a js file with stubs might be provided.
This approach doesn’t have to be reserved for the big-ticket items. If a component is almost ready to be released but lacks a properties.schema or doesn’t have all the functions of question.view implemented or such, publicizing a to-do list might speed these along.
Are there other ways to jump start development in the community that is compatible with the vision of core developers?
It is an exciting time with framework v2.0 right around the corner. Quite a milestone. But at the edge of excitement is a tease of anticipation: I wonder what’s next?!