D project management for better growth and longevity

[js.mdnq]

On Thursday, 21 February 2013 at 21:32:56 UTC, Jacob Carlborg 
wrote:
> On 2013-02-21 13:53, js.mdnq wrote:
>> This is an idea I have that I believe can help D become in 
>> time one of
>> the most popular, if not the, programming language.
>>
>> The D language, excluding some of known issues, has many great 
>> language
>> constructs that set it above the mainstream programming 
>> languages today.
>> While there are many competitors to D, D seems to have stronger
>> fundamentals and IMO a better language syntax steaming from 
>> it's
>> relation to C/C++.
>>
>> There are several problems with D as it stands but the main 
>> one is the
>> userbase. For proper development there must be users or are 
>> willing to
>> invest the time and energy to create the tools to make more 
>> users want
>> to use D(which will result in a cycle (or rather a spiral)).
>
> Something like this, but with forms as well:
>
> https://www.ruby-toolbox.com/

lol, someone stole my idea! ;) Looks like it has many features I 
am talkig about. I'm not sure if you can dive down an endless 
hierarchy though but seems to have a lot of the features(I 
haven't checked it out enough to know but)

(the organizational and visual theme looks a bit chaotic to me 
but seems to have docs, code, and other stuff(no forum per 
project))

I would say it has a close concept to mine but not exactly the 
same.

mine would be implemented something like

class node {
    node[] children; // child nodes
    forum(children);  // A forum interface for this node with 
access to the child forums
    management; // List of people who manage this project and all 
children
    buildscript; // Some type of script to do something
    wiki(children); // A help/info system about this node and all 
children
    dependencies;  // a list of cross-references for internode 
dependencies.
    data;  // Data for the node (source code or whatever)
    statistics;  // Statistics about the node
    info;        // node info(name, version, etc...)
    ...
}

Each element of node has a web page associated with it to 
visualize the data.

The web page for a node would be something like an html page that 
shows a forum link, wiki link, dependencies link, info about the 
project, the members, related projects(siblings), etc...

Unlike ruby, each node can contain subnodes which can deal with 
specific areas of a larger project(e.g., for an ide, just the 
gui, or some specific part of the gui).

This way large projects can be infinitely parsed down to very 
small bits that anyone can work on and which can propagate up to 
the root node(and this is the power of such a hierarchy).