Re: Two-phased code donation proposal

2017-02-28 Thread Emmanuel Lécharny
That is a sane sugestion. +1 Le 01/03/2017 à 00:20, Geertjan Wielenga a écrit : > Hi all, > > I'd like to propose a two-phased code donation -- the first for all the > parts necessary for building a Java SE distribution of NetBeans IDE and the > second for all the other parts. > > I.e., the first

Two-phased code donation proposal

2017-02-28 Thread Geertjan Wielenga
Hi all, I'd like to propose a two-phased code donation -- the first for all the parts necessary for building a Java SE distribution of NetBeans IDE and the second for all the other parts. I.e., the first code donation would be 5a-d in the link below and the second code donation would be 5e-f in t

Re: DevNexus

2017-02-28 Thread Zoran Sevarac
Sounds great! Congrat! On Mon, Feb 27, 2017 at 4:42 PM, Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Hi all, > > It was really great at DevNexus last week: > > 1. DevNexus donated a Silver Sponsorship to NetBeans, in support of our > move to Apache. Thanks again DevNexus! > > 2.

Re: Code contribution process.

2017-02-28 Thread Wade Chandler
> On Feb 28, 2017, at 05:17, Emmanuel Lécharny wrote: > > > > Le 27/02/2017 à 17:17, Wade Chandler a écrit : >> I think it already does mean something. Contributors have the right to >> actually vote, where as someone sending a patch doesn’t. > > Actually, no. > > Of course, everyone can vo

Re: Slack vs dev list (was: Code contribution process.)

2017-02-28 Thread Bertrand Delacretaz
On Tue, Feb 28, 2017 at 11:19 AM, Neil C Smith wrote: > ...Slack is also transient and a larger community can quickly get to a > point where the archive only lasts a few weeks... And even if the archive is permanent that doesn't help much for jumping late into a discussion that started a few days

Re: Slack vs dev list (was: Code contribution process.)

2017-02-28 Thread Emmanuel Lécharny
Le 27/02/2017 à 18:38, Neil C Smith a écrit : > On 27 February 2017 at 16:02, Bertrand Delacretaz > wrote: >> My (own, unwritten) rule in Apache projects is to move things to the >> dev list as soon as they go beyond the level of a coffee machine >> discussion - and when they do, restart the dis

Re: Slack vs dev list (was: Code contribution process.)

2017-02-28 Thread Neil C Smith
On 28 February 2017 at 08:56, Timon Veenstra wrote: >> Conversations like on slack usually don't make good documentation > Transferring this common practice, when someone says something worth > remembering on slack, we put it on the wiki (or issue tracker when its bug > related). I'm not sur

Re: Code contribution process.

2017-02-28 Thread Emmanuel Lécharny
Le 27/02/2017 à 17:17, Wade Chandler a écrit : > I think it already does mean something. Contributors have the right to > actually vote, where as someone sending a patch doesn’t. Actually, no. Of course, everyone can vote, but some votes are binding votes, when others are just informative. Ty

Re: Slack vs dev list (was: Code contribution process.)

2017-02-28 Thread Timon Veenstra
> > > things might get lost that are important without us realising, > particularly in channels other than #general. Whether the solution is > logging or another similar service with better archiving, I don't > know. I do think it's a communication medium that ends up being used > in a way that's