On Thursday, 18 June 2015 at 20:58:38 UTC, ketmar wrote:
> On Thu, 18 Jun 2015 14:45:26 +0000, Etienne wrote:
>
>> My point is, we need to be able to extend it to build and link an application with a custom druntime/phobos/dmd version from source.
>
> exactly what you can do with Reggae. now Reggae needs a good package manager, which dub isn't.

I'm not sure how you put 2 and 2 together to come up with Reggae. It seems to be an executable generator with a build configuration. It leaves it up to the user to come up with D code to figure out the build.

I'm talking about cloning phobos/druntime/dmd github repositories and automatically building them. No messing around with environment variables and such.

On Fri, 19 Jun 2015 02:00:41 +0000, Etienne wrote:

> On Thursday, 18 June 2015 at 20:58:38 UTC, ketmar wrote:
>> On Thu, 18 Jun 2015 14:45:26 +0000, Etienne wrote:
>>
>>> My point is, we need to be able to extend it to build and link an application with a custom druntime/phobos/dmd version from source.
>>
>> exactly what you can do with Reggae. now Reggae needs a good package manager, which dub isn't.
> 
> I'm not sure how you put 2 and 2 together to come up with Reggae.
> It seems to be an executable generator with a build configuration. It
> leaves it up to the user to come up with D code to figure out the build.
> 
> I'm talking about cloning phobos/druntime/dmd github repositories and automatically building them. No messing around with environment variables and such.

ah, that's easy: simply include Reggae build script into the package. even half-assed package managers can include custom install/build scripts into packages and execute them. so is dub is package manager...

On 06/17/2015 08:35 PM, Andrei Alexandrescu wrote:
> You wouldn't just not go to work for two weeks and then show up at your desk as if nothing happened. This kind of stuff needs some level of planning, barring exceptional events.

Yeah that didn't work too well, sorry for the trouble.
I was extremely busy before dconf (that's part of why I missed my
flight) and didn't spend much thought on the release. Probably didn't
take it that serious, given how infrequently we handled it before.

I was also under the impression that people were informed. http://forum.dlang.org/post/5554D763.1080308@dawg.eu

Interestingly this links back to our missing communication infrastructure.
We should have regular (semi-public) meetings involving all core
contributors to plan development, releases, and everything D.
Private (irregular) email discussion don't cut it, b/c they leave most
people uninformed. The newsgroup doesn't work either, b/c it's too busy
with daily news.

We pay a lot for the lack of communication (it's key in a more hierarchical structure), b/c noone but Walter and you can push something on the development agenda without a screaming rant on the newsgroup. This is a main reason why so much work gets stuck/killed in the pull request stage (who could have discussed it before), and also the main reason why we rarely collaborate on topics.

-Martin

On Friday, 19 June 2015 at 16:02:34 UTC, Martin Nowak wrote:
> On 06/17/2015 08:35 PM, Andrei Alexandrescu wrote:
>> You wouldn't just not go to work for two weeks and then show up at your desk as if nothing happened. This kind of stuff needs some level of planning, barring exceptional events.
>
> Yeah that didn't work too well, sorry for the trouble.
> I was extremely busy before dconf (that's part of why I missed my
> flight) and didn't spend much thought on the release. Probably didn't
> take it that serious, given how infrequently we handled it before.
>
> I was also under the impression that people were informed. http://forum.dlang.org/post/5554D763.1080308@dawg.eu

That post says you'd be back on June 7th, whereas Andrei posted that he couldn't find you on June 17th.  Typo?

> Interestingly this links back to our missing communication infrastructure.
> We should have regular (semi-public) meetings involving all core
> contributors to plan development, releases, and everything D.
> Private (irregular) email discussion don't cut it, b/c they leave most
> people uninformed. The newsgroup doesn't work either, b/c it's too busy
> with daily news.
>
> We pay a lot for the lack of communication (it's key in a more hierarchical structure), b/c noone but Walter and you can push something on the development agenda without a screaming rant on the newsgroup. This is a main reason why so much work gets stuck/killed in the pull request stage (who could have discussed it before), and also the main reason why we rarely collaborate on topics.

All these and your suggestions in the linked thread seem like worthwhile improvements.  The impression I get is that everyone in the core team is too busy with their real jobs, other than Walter, to make meetings easy to coordinate.  Not sure of a ready solution for that.

On Friday, 19 June 2015 at 16:02:34 UTC, Martin Nowak wrote:
> Interestingly this links back to our missing communication infrastructure.
> We should have regular (semi-public) meetings involving all core
> contributors to plan development, releases, and everything D.
> Private (irregular) email discussion don't cut it, b/c they leave most
> people uninformed. The newsgroup doesn't work either, b/c it's too busy
> with daily news.
>
> We pay a lot for the lack of communication (it's key in a more hierarchical structure), b/c noone but Walter and you can push something on the development agenda without a screaming rant on the newsgroup. This is a main reason why so much work gets stuck/killed in the pull request stage (who could have discussed it before), and also the main reason why we rarely collaborate on topics.
>
> -Martin

You could use a teamchat like Slack, HipChat, ChatGrape or even Let's Chat.

On 06/19/2015 02:41 PM, "Jacques =?UTF-8?B?TcO8bGxlciI=?= <jacques.mueller@gmx.de>" wrote:
>
> You could use a teamchat like Slack, HipChat, ChatGrape or even Let's Chat.

Or irq.

On Friday, 19 June 2015 at 19:27:09 UTC, Nick Sabalausky wrote:
> On 06/19/2015 02:41 PM, "Jacques =?UTF-8?B?TcO8bGxlciI=?= <jacques.mueller@gmx.de>" wrote:
>>
>> You could use a teamchat like Slack, HipChat, ChatGrape or even Let's Chat.
>
> Or irq.

IRC, I hope, is what you mean. Chatting by interrupts sounds horrible.

Andrei comes in IRC occasionally (less lately, he used to be in there daily).

It's a shame we don't have more core devs in there. It's a fairly active channel with a couple hundred people at any given time.

On Friday, 19 June 2015 at 21:00:27 UTC, Brad Anderson wrote:
> On Friday, 19 June 2015 at 19:27:09 UTC, Nick Sabalausky wrote:
>> On 06/19/2015 02:41 PM, "Jacques =?UTF-8?B?TcO8bGxlciI=?= <jacques.mueller@gmx.de>" wrote:
>>>
>>> You could use a teamchat like Slack, HipChat, ChatGrape or even Let's Chat.
>>
>> Or irq.
>
> IRC, I hope, is what you mean. Chatting by interrupts sounds horrible.
>
> Andrei comes in IRC occasionally (less lately, he used to be in there daily).
>
> It's a shame we don't have more core devs in there. It's a fairly active channel with a couple hundred people at any given time.

That's #d on freenode, I should say (even though freenode is kind of the obvious place for open source projects these days).

On 06/19/2015 05:00 PM, Brad Anderson wrote:
> On Friday, 19 June 2015 at 19:27:09 UTC, Nick Sabalausky wrote:
>> On 06/19/2015 02:41 PM, "Jacques =?UTF-8?B?TcO8bGxlciI=?=
>> <jacques.mueller@gmx.de>" wrote:
>>>
>>> You could use a teamchat like Slack, HipChat, ChatGrape or even Let's
>>> Chat.
>>
>> Or irq.
>
> IRC, I hope, is what you mean. Chatting by interrupts sounds horrible.
>

Erm...that's right, "chat" doesn't start with "q" :)

On 6/19/15 2:00 PM, Brad Anderson wrote:
> IRC, I hope, is what you mean. Chatting by interrupts sounds hor-

It sure does! :)