Re: [riot-devel] Open Processes Task Force
Hey, On 05/28/15 15:59, Emmanuel Baccelli wrote: > > - introducing a "show-stopper" textual label for comments on > PRs > > (if absent, would require less or no ACK before being merged, after some > > agreed-upon probation time). The idea would be to increase agility > > - introducing a "high-impact" label on PRs (would require more > > ACKs before being merged). > > That's pretty much the idea of the labels "minor" and "major" (impact). > > @Kaspar care to comment? If I remember correctly you saw some use in > introducing something like the "high-impact" label? They would do fine. We should but some rough guidelines on when something is "major" and that it then needs at least two ACKs and an extended concept review. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
Hi again everyone,
just one general comment: this thread currently has a lower priority
compared to the efforts towards next month's new RIOT release.
So basically, for those involved: take your time to provide input other
than +1 for the idea of having such a task force ;)
I plan to provide soonish some input on the tentative definition of what a
task force is (and what it is not).
Best,
Emmanuel
On Thu, May 28, 2015 at 3:59 PM, Emmanuel Baccelli <
emmanuel.bacce...@inria.fr> wrote:
>
> On Thu, May 28, 2015 at 7:53 AM, Oleg Hahm wrote:
>
>> Hi!
>>
>> > - introducing a "show-stopper" textual label for comments on
>> PRs
>> > (if absent, would require less or no ACK before being merged, after some
>> > agreed-upon probation time). The idea would be to increase agility
>> > - introducing a "high-impact" label on PRs (would require more
>> > ACKs before being merged).
>>
>> That's pretty much the idea of the labels "minor" and "major" (impact).
>>
>>
>
> @Kaspar care to comment? If I remember correctly you saw some use in
> introducing something like the "high-impact" label?
>
> Cheers
>
> Emmanuel
>
>
>
>> Cheers,
>> Oleg
>> --
>> printk("; corrupted filesystem mounted read/write - your computer
>> will explode within 20 seconds ... but you wanted it so!\n");
>> linux-2.4.3/fs/hpfs/super.c
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
On Thu, May 28, 2015 at 7:53 AM, Oleg Hahm wrote:
> Hi!
>
> > - introducing a "show-stopper" textual label for comments on PRs
> > (if absent, would require less or no ACK before being merged, after some
> > agreed-upon probation time). The idea would be to increase agility
> > - introducing a "high-impact" label on PRs (would require more
> > ACKs before being merged).
>
> That's pretty much the idea of the labels "minor" and "major" (impact).
>
>
@Kaspar care to comment? If I remember correctly you saw some use in
introducing something like the "high-impact" label?
Cheers
Emmanuel
> Cheers,
> Oleg
> --
> printk("; corrupted filesystem mounted read/write - your computer
> will explode within 20 seconds ... but you wanted it so!\n");
> linux-2.4.3/fs/hpfs/super.c
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
Hi!
> - introducing a "show-stopper" textual label for comments on PRs
> (if absent, would require less or no ACK before being merged, after some
> agreed-upon probation time). The idea would be to increase agility
> - introducing a "high-impact" label on PRs (would require more
> ACKs before being merged).
That's pretty much the idea of the labels "minor" and "major" (impact).
Cheers,
Oleg
--
printk("; corrupted filesystem mounted read/write - your computer
will explode within 20 seconds ... but you wanted it so!\n");
linux-2.4.3/fs/hpfs/super.c
pgpOWZkaMArs3.pgp
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
Hi Kaspar, On Thu, May 28, 2015 at 12:08 AM, Kaspar Schleiser wrote: > Hey, > > On 05/28/15 00:02, Emmanuel Baccelli wrote: > > I propose to launch a task force focusing on open processes at work in > > the RIOT community. > +1 > > We need to be careful not to over-design our processes, but a task force > identifying possible improvements sounds very useful. > > I agree about the danger of over-designing here. The main idea is to make sure that the mains mechanisms at work can be grasped by both outsiders and insiders. The advantages looked for here are : (i) transparency, as in: people outside this community can more quickly understand how we work, and (ii) upgradeability, as in: people inside the community can more easily identify what works and what does not (anymore) and introduce changes when/where needed. We need to be precise only at "some" level, and "some" here should understood as "minimal" subject to (i) and (ii) being satisfied. Does it make sense? cheers Emmanuel > Kaspar > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
Hi Martine, On Thu, May 28, 2015 at 2:15 AM, Martine Lenders wrote: > Hi, > Just to be clear, we are talking about administrative processes on our > work in RIOT here, right? Not some kind of system processes. > > yes (although I'm not so sure about the term "administrative" here ;). Basically, the focus of this task force is to talk about how the community organizes itself, around the technical work to be done. Concerning this organization: - some level of details should be defined somewhere, for transparency reasons - the way we organize is bound to evolve over time due to the evolution of both the community and of the work to be done So this would be the "place" to talk about this and design this evolution together. Best, Emmanuel > Cheers, > Martine > Am 28.05.2015 00:09 schrieb "Kaspar Schleiser" : > >> Hey, >> >> On 05/28/15 00:02, Emmanuel Baccelli wrote: >> > I propose to launch a task force focusing on open processes at work in >> > the RIOT community. >> +1 >> >> We need to be careful not to over-design our processes, but a task force >> identifying possible improvements sounds very useful. >> >> Kaspar >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel >> > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
Hi, Just to be clear, we are talking about administrative processes on our work in RIOT here, right? Not some kind of system processes. Because that's what I was thinking first Manu's mail was about and I had a really hard time wrapping my head around it. Cheers, Martine Am 28.05.2015 00:09 schrieb "Kaspar Schleiser" : > Hey, > > On 05/28/15 00:02, Emmanuel Baccelli wrote: > > I propose to launch a task force focusing on open processes at work in > > the RIOT community. > +1 > > We need to be careful not to over-design our processes, but a task force > identifying possible improvements sounds very useful. > > Kaspar > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Open Processes Task Force
Hey, On 05/28/15 00:02, Emmanuel Baccelli wrote: > I propose to launch a task force focusing on open processes at work in > the RIOT community. +1 We need to be careful not to over-design our processes, but a task force identifying possible improvements sounds very useful. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Open Processes Task Force
Hi everyone, I propose to launch a task force focusing on open processes at work in the RIOT community. The goals are both (i) maintenance/improvements of these processes to adapt to the evolution of our community, and (ii) ensure an appropriate level of transparency concerning what the current processes are. If interested, please PING this thread for starters, and don't hesitate to bring in comments or more content/suggestions. To be more concrete, I propose the task force would work for starters on items such as the below. - document/discuss the lessons learnt so far for current processes, for instance: - what are the lessons learnt for our "task force" concept in practice? - should we not define more precisely what a "task force" is? - what other definitions are needed (e.g. an even smaller unit a.k.a. "design team" a la "scrum team")? - discuss the need for, and merits of (new) development processes, for instance: - introducing a "show-stopper" textual label for comments on PRs (if absent, would require less or no ACK before being merged, after some agreed-upon probation time). The idea would be to increase agility - introducing a "high-impact" label on PRs (would require more ACKs before being merged). - discuss the need for, and merits of (new) strategic coordination, for instance: - do we need more technical leadership? Goal: optimize the order of PR merging - if so, what shape should this leadership take? Requirement: scalability with community size and sustainability w.r.t. to time, which means avoiding bottlenecks somehow... Cheers Emmanuel ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
