Last update April 27, 2012

Help DProgress



Helping the progress of D    

There are several things keeping D from "going mainstream" in many people's minds. Here, a collection of things that could be done to help push D along its way to becoming a more widely recognized and used language is presented.

This is not intended to be a list purely for speculation or for giving reasons why D isn't popular yet. This is intended to be a list for people who want to help D to progress to pick something and start helping.

Table of contents of this page
Helping the progress of D   
Contributing to Phobos   
Compiler Support   
Debugging   
Documentation   
Libraries   
Related Wiki Pages   

Contributing to Phobos    

New code with major additions must run through a Boost Review cycle. It is suggested that you post to the Development Newsgroup to gauge interest and identify it isn't already being worked on. Don't get discouraged from low response as this can be for several reasons, but hopefully a sign that others agree it should be in Phobos will comment. And even if it is decided not to fit, if it is code you are interest in having others are likely too and can be its own library.

The process is a standard three weeks once the code is ready. Two weeks are left for review of the source and API, and is followed by a week of voting. During the review the code can be modified to appease the criticism, and it will be up to the submitter and review manager to decide if it makes sense to continue with a vote or postpone for a later review.

Smaller additions such as expanding existing functionality or fixing bugs can skip the formal review process. Remember that it is volunteers running this which means pull requests could have long waiting periods before getting reviewed. You can use the newsgroups to peek more interest in the request.

Compiler Support    

There are those who believe D is not viable until there are several implementations that are working to their fullness (in other words, nearly fully up to date with the spec).

Debugging    

Documentation    

Libraries    

I see this becoming something of a "Adopt-a-project" type page, where people can volunteer to do any of these things (permanently or just a single bit once). I think it could really help if people even just occasionally did something to add to a project.

This probably isn't very well thought-out, so hopefully some others will come and clean this page up and make it make more sense and lay it out better?

Related Wiki Pages    


FrontPage | News | TestPage | MessageBoard | Search | Contributors | Folders | Index | Help | Preferences | Edit

Edit text of this page (date of last change: April 27, 2012 3:51 (diff))