Difference between revisions of "How You Can Help"

From D Wiki
Jump to: navigation, search
(link to wish list and review queue)
(Replaced content with "Merged with get involved.")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Our [[Wish_list|wish list]] and [[Review_Queue|review queue]] should you a good impression of what is needed.
+
Merged with [[Get_involved|get involved]].
 
 
== Documentation ==
 
 
 
* std.algorithm - see forum
 
 
 
== Wiki ==
 
 
 
* We need [http://wiki.dlang.org/Coming_From D as a second language] sections completed
 
* C and C++ need updating
 
* we need more examples of how to shift idiom to speak fluent D
 
* the Python page is started but needs fleshing out
 
* and most of the other sections are empty.
 
 
 
<blockquote>
 
One note about Walter's older C/C++ transition articles. They have good information on transition technicalities (e.g. "how do I do this thing in D that I used to do in C++?") but not a lot about the changes in coding style - making object copying not arbitrarily expensive, choosing struct vs. class, preferring pipelines and lazy to eager computation, etc. From what I see some folks come from C++, write their first D program in a stilted C++ idiom, and are left with the impression that the work is not worth the trouble.
 
 
 
Andrei
 
</blockquote>
 
 
 
== Past GSOC ideas ==
 
 
 
Some of these may still be interesting.
 
* [http://wiki.dlang.org/GSOC_2015_Ideas 2015]
 
* [http://wiki.dlang.org/GSOC_2014_Ideas 2014]
 
* [http://wiki.dlang.org/GSOC_2013_Ideas 2013]
 
* [http://www.prowiki.org/wiki4d/wiki.cgi?GSOC_2012_Ideas 2012]
 
* [http://www.prowiki.org/wiki4d/wiki.cgi?GSOC_2011_Ideas 2011]
 
 
 
== How to better promote your own D projects ==
 
 
 
<blockquote>
 
I hate the movie "Field of Dreams" where they push the idiotic idea of "Build it and they will come." No, they won't. There's a blizzard of stuff competing for their attention out there, why should they invest the time looking at your stuff? You need to tell them why!
 
 
 
Here's the frustrating typical pattern I've seen here for years:
 
 
 
# spend hundreds if not thousands of hours developing something really cool
 
# spend 2 minutes posting a link to the repository on D.announce
 
# someone posts it to reddit. Ignore it
 
# get frustrated that nobody looks at it
 
# get bitter and quit
 
 
 
Here's the pattern that works a lot better:
 
 
 
# spend hundreds if not thousands of hours developing something really cool
 
# spend 10 minutes writing the announcement to D.announce. Be sure to include:
 
#: who, what, where, when, why, and how
 
# someone posts it to reddit
 
# post the who, what, where, when, why and how on reddit AS SOON AS POSSIBLE after the reddit link appears. Stuff on reddit has a VERY SHORT shelf life. If it doesn't get action within a couple hours, it fades into oblivion. Identify yourself as the author, say AMA. The first one to post a comment tends to spark and set the tone for the discussion.
 
# check back on reddit once an hour or so for the next day, answer questions
 
# *****
 
# profit!
 
 
 
Walter Bright
 
</blockquote>
 
 
 
 
 
 
 
== Compiler Project List ==
 
* DMD (TBA)
 
* [http://wiki.dlang.org/LDC_project_ideas LDC]
 
* [http://wiki.dlang.org/GDC/ProjectIdeas GDC]
 
 
 
 
 
[[Category: Contribution Guidelines]]
 

Latest revision as of 11:51, 21 December 2016

Merged with get involved.