D project management for better growth and longevity

[js.mdnq]

On Thursday, 21 February 2013 at 14:29:26 UTC, bearophile wrote:
> See also Gerrit, etc:
>
> http://forum.dlang.org/thread/kzjhkzskghqopvcnacla@forum.dlang.org
>
> Bye,
> bearophile

This is just a forum. There is no hierarchical relationship 
between projects and user collaboration is hard to 
initiate(requires making a post and get emails, etc...). One 
can't work themselves down into the project hierarchy to get to 
more specific details.

An IDE, for example, would compose many areas

IDE - IDE's for D
   DIDE - The D IDE
      Main - The main project
        Core - The core code
        Gui -
        ....
      Debugger -
        ....
      Plugins -
        ....
   D for Eclipse - An D plugin for Eclipse
      ....
   ....

A person would normally see for the overview, just IDE(in this 
case). If they want to download or contribute to the IDE 
development they will follow the IDE link which will expand the 
children of IDE. This allows them to see currently what kind of 
IDE development is taking place. There will be information 
supplied about who to contact, current stats, a forum 
specifically for IDE discussion, etc. If they are interested in 
DIDE they can click on it and get the same type of 
information(but specific to DIDE). If they want to see if a 
specific type of plugin is under development or done they can 
click on plugins. If they want to write a new plugin they have 
the ability to start a new plugin and it will be added.

As you descend down the tree the project development becomes more 
specific all higher levels have access to the lower 
levels(essentially one can view the D forum which will show the 
forums for all the lower levels(the children)).

Such a hierarchical design breaks down the project into as small 
pieces as required. For example, further down the chain one could 
have a specific node representing a single function that is used. 
A complete discussion about the function and it's behavior can be 
found in it's forum and who is monitoring and working on it can 
be communicated with. Its forum will not show any messages from 
other nodes(since it is a terminal in the tree). (but any 
ancestor will have access to it's forum and information)

For example, suppose you write your nifty GC but there is a 
problem with a function. Someone can "clone" just the function 
and write there own/fix up the problem and you can merge it if 
you feel like it(and are the owner of the project).

So, the idea is to have macroscopic level and microscopic.(but it 
would all be uniformly the same).