Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-06-08 Thread Andrei Alexandrescu via Digitalmars-d
On 6/8/16 8:32 AM, Dicebot wrote: FYI: I'd like to take over DIP management, currently drafting out process and tools for new system ( https://github.com/Dicebot/DIPs ) That would be great, thanks for your service! -- Andrei

Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-06-08 Thread Dicebot via Digitalmars-d
On Tuesday, 7 June 2016 at 20:50:48 UTC, Seb wrote: On Thursday, 26 May 2016 at 22:05:52 UTC, Seb wrote: On Sunday, 8 May 2016 at 11:39:45 UTC, Nordlöw wrote: I'm in favour of this, Seb. IMO, the pros outweigh the cons. Integrated peer-review is a big win. We already see at our github repos

Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-06-07 Thread Andrei Alexandrescu via Digitalmars-d
On 6/7/16 10:50 PM, Seb wrote: On Thursday, 26 May 2016 at 22:05:52 UTC, Seb wrote: On Sunday, 8 May 2016 at 11:39:45 UTC, Nordlöw wrote: I'm in favour of this, Seb. IMO, the pros outweigh the cons. Integrated peer-review is a big win. We already see at our github repos that peer review/help

Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-06-07 Thread Seb via Digitalmars-d
On Thursday, 26 May 2016 at 22:05:52 UTC, Seb wrote: On Sunday, 8 May 2016 at 11:39:45 UTC, Nordlöw wrote: I'm in favour of this, Seb. IMO, the pros outweigh the cons. Integrated peer-review is a big win. We already see at our github repos that peer review/help is great, so why not for the

Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-05-26 Thread Seb via Digitalmars-d
On Sunday, 8 May 2016 at 11:39:45 UTC, Nordlöw wrote: I'm in favour of this, Seb. IMO, the pros outweigh the cons. Integrated peer-review is a big win. We already see at our github repos that peer review/help is great, so why not for the DIPs?

Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-05-08 Thread Nordlöw via Digitalmars-d
On Thursday, 28 April 2016 at 08:28:20 UTC, Seb wrote: A couple of advantages: 1) Full page generator engine included - extending the setup or template is easy 2) Dlang theme/branding -> official status 3) In future: Detailed Git history 4) Peer-review on Github 5) Plain-text (+offline

Re: [RFC] D Improvement Proposals: Move to git + markdown?

2016-04-28 Thread Vladimir Panteleev via Digitalmars-d
On Thursday, 28 April 2016 at 08:28:20 UTC, Seb wrote: Anyhow my question was: do you like the move to a git repository and markdown? How about github.com/dlang/dips and dips.dlang.org? Personally I think it's unnecessary. DIPs are generally drafted by one person (as their language

[RFC] D Improvement Proposals: Move to git + markdown?

2016-04-28 Thread Seb via Digitalmars-d
Hi all, as mentioned in a previous thread, I thought it would be cool to have all DIPs in a git repo as many DIPs had wrong "status" headers. It turns out, it is not that much work & I quickly went ahead with a small export & convert to markdown script [2]. Moreover it converts the header