digitalmars.D - The hackathon week roundup
- Andrei Alexandrescu (34/34) May 02 2015 The hackathon week (Apr 25 - May 1) saw 70 PRs created (compare to 68
- weaselcat (8/11) May 02 2015 already got pulled
- Ilya Yaroshenko (2/4) May 02 2015 May I transfer the repositories (both GitHub and RTD) to the
- Andrei Alexandrescu (2/6) May 02 2015 That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei
- Walter Bright (2/9) May 02 2015 I think it's a great idea. It'd have to be Boost licensed, though.
- Rikki Cattermole (3/13) May 02 2015 Shouldn't it be creative commons because it is more a creative work aka
- Walter Bright (2/4) May 02 2015 Everything else is boost licensed. Consistency.
- Andrei Alexandrescu (2/12) May 02 2015 Ilya, your turn. Proceed and be bold. -- Andrei
- Ilya Yaroshenko (5/21) May 03 2015 I have requested repository transfer to Andrei because only
- Ilya Yaroshenko (8/24) May 03 2015 Project Home
- Mike (15/17) May 02 2015 My idea:
- Martin Nowak (2/14) May 03 2015 Good idea
The hackathon week (Apr 25 - May 1) saw 70 PRs created (compare to 68 created Apr 18 through 24). Not much difference in terms of new work, but the PRs closed during the same two periods (75 vs 53) reflect a good bump in the reviewing activity. Another related data point: 143 PRs were updated (e.g. revised, commented on etc) during the hackathon week vs. 78 the week before that. Great work, thanks! Some good stuff has been happening, some manifestly hackathon-related, some perhaps just coincidental. * Article "Using D Templates for Gamedev": https://marfisc.wordpress.com/2015/04/29/using-d-templates-for-gamedev. Did well on reddit (http://www.reddit.com/r/programming/comments/34ah1q/using_d_templates_fo _game_development/) although it's been classified as spam for a few hours. * Proof of concept: https://github.com/JinShil/stm32f42_discovery_demo/blob/master/README.md * Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?) * WIP: tracing memory allocations, see http://forum.dlang.org/thread/mhhmnr$2euj$1 digitalmars.com, https://github.com/D-Programming-Language/dmd/pull/4621, https://github.com/D-Programming-Language/dmd/pull/4625, https://github.com/D-Programming-Language/druntime/pull/1246. * The "if(arr)" warning has been undone. This has caused a fair amount of stir. We believe we made the right call, though sadly it's impossible to make everyone happy. Please bear with us. * WIP: Unique https://github.com/D-Programming-Language/phobos/pull/3225 and RefCounted (can't seem to find the PR - where is it?) * WIP: allocators http://forum.dlang.org/thread/mi1qph$cgr$1 digitalmars.com All in all, a great week! Congratulations to all participants, and let's do it again sometime. I'm looking into ways to make this more interactive (google hangouts?) and more fun (contests? prizes? etc). Chime in! Again - this is terrific. Many thanks to everyone who participated! Andrei
May 02 2015
On Saturday, 2 May 2015 at 23:02:05 UTC, Andrei Alexandrescu wrote:* WIP: Unique https://github.com/D-Programming-Language/phobos/pull/3225 and RefCounted (can't seem to find the PR - where is it?)already got pulled https://github.com/D-Programming-Language/phobos/pull/3171 Worth adding: AFAIK unique(?) and refcounted are completely usable in nogc, and most of the unit tests likely can be marked nogc for them to help prevent breakage.
May 02 2015
* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 02 2015
On 5/2/15 4:50 PM, Ilya Yaroshenko wrote:That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 02 2015
On 5/2/2015 5:12 PM, Andrei Alexandrescu wrote:On 5/2/15 4:50 PM, Ilya Yaroshenko wrote:I think it's a great idea. It'd have to be Boost licensed, though.That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 02 2015
On 3/05/2015 1:27 p.m., Walter Bright wrote:On 5/2/2015 5:12 PM, Andrei Alexandrescu wrote:Shouldn't it be creative commons because it is more a creative work aka documentation?On 5/2/15 4:50 PM, Ilya Yaroshenko wrote:I think it's a great idea. It'd have to be Boost licensed, though.That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 02 2015
On 5/2/2015 7:43 PM, Rikki Cattermole wrote:Shouldn't it be creative commons because it is more a creative work aka documentation?Everything else is boost licensed. Consistency.
May 02 2015
On 5/2/15 6:27 PM, Walter Bright wrote:On 5/2/2015 5:12 PM, Andrei Alexandrescu wrote:Ilya, your turn. Proceed and be bold. -- AndreiOn 5/2/15 4:50 PM, Ilya Yaroshenko wrote:I think it's a great idea. It'd have to be Boost licensed, though.That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 02 2015
On Sunday, 3 May 2015 at 04:13:35 UTC, Andrei Alexandrescu wrote:On 5/2/15 6:27 PM, Walter Bright wrote:I have requested repository transfer to Andrei because only members of a organisation can transfer. Andrey or/and someone from D core team, please send me your user names at readthedocs.org.On 5/2/2015 5:12 PM, Andrei Alexandrescu wrote:Ilya, your turn. Proceed and be bold. -- AndreiOn 5/2/15 4:50 PM, Ilya Yaroshenko wrote:I think it's a great idea. It'd have to be Boost licensed, though.That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 03 2015
On Sunday, 3 May 2015 at 04:13:35 UTC, Andrei Alexandrescu wrote:On 5/2/15 6:27 PM, Walter Bright wrote:Project Home https://readthedocs.org/projects/d/ Repository https://github.com/andralex/thenextafterc Short URLs http://d.readthedocs.org http://d.rtfd.orgOn 5/2/2015 5:12 PM, Andrei Alexandrescu wrote:Ilya, your turn. Proceed and be bold. -- AndreiOn 5/2/15 4:50 PM, Ilya Yaroshenko wrote:I think it's a great idea. It'd have to be Boost licensed, though.That'd be a fine idea. Thoughts from Walter, Martin et al? -- Andrei* Tutorial: http://d.readthedocs.org (btw should we link that from the homepage?)May I transfer the repositories (both GitHub and RTD) to the D-Programming-Language community?
May 03 2015
On Saturday, 2 May 2015 at 23:02:05 UTC, Andrei Alexandrescu wrote:I'm looking into ways to make this more interactive (google hangouts?) and more fun (contests? prizes? etc). Chime in!My idea: 1. Members of the D leadership/committers form a working group. 2. The working group creates of list of bugs they are willing to work on. 3. Hackathon is announced. To motivate participants, the working group agrees to fix a bug of the winner's choosing. 4. After the hackathon, the working group subjectively chooses a winner from the participants. 5. The winner discloses which bug they would like fixed, and the qualified members of the working group agrees to fix it for the next release. 7. Wash, rinse, repeat. Mike
May 02 2015
On Sunday, 3 May 2015 at 04:15:58 UTC, Mike wrote:My idea: 1. Members of the D leadership/committers form a working group. 2. The working group creates of list of bugs they are willing to work on. 3. Hackathon is announced. To motivate participants, the working group agrees to fix a bug of the winner's choosing. 4. After the hackathon, the working group subjectively chooses a winner from the participants. 5. The winner discloses which bug they would like fixed, and the qualified members of the working group agrees to fix it for the next release. 7. Wash, rinse, repeat.Good idea
May 03 2015