[Sugar-devel] Community (was: Re: Bug tracking Vs Patch review)

[Tomeu Vizoso]

On Tue, Aug 31, 2010 at 12:49, Sascha Silbe
<sascha-ml-reply-to-2010-2 at silbe.org> wrote:
> Excerpts from Tomeu Vizoso's message of Tue Aug 31 10:33:40 +0200 2010:
>
>> Yes, we agreed on that, but then, just for the sake of argument,
>> several unchecked statements were made that unfairly represented the
>> current Sugar development model and the work of several members of our
>> community.
> [...]
>> Again, you are misrepresenting me just for the sake of argument,
> [...]
>> And we are going to fix this by throwing shit to our colleagues.
> [...]
>> One person is working on merging them, several others have preferred
>> just to complain about it.
> [...]
>> Visible because someone has invested a lot of time giving it
>> visibility in the mailing list and made bombastic statements so other
>> people were forcedly dragged into the discussion?
>
> And so on.
>
> Please sit back, have a cup of your favourite beverage and relax.
>
> We all care very much about Sugar. But we should care equally much about
> each other, not engage in dirty fights. If you want to blow off some
> steam, please consider organising a Sugar Labs deathmatch [1] and/or
> co-op match [2] instead. Sauerbraten [3] not only has nice, clean,
> easily hackable code and an in-game map editor, but is also a fun and
> awesome-looking game (though it doesn't have a co-op match mode, only
> co-op editing).

Frankly, just calming down the rhetoric and sticking to the facts
would help a big deal. We're not trying to manage anything that other
communities haven't managed to get with.

> FWIW, I can totally relate to Bernie; I have even stopped trying to get
> most of my patches into mainline, including bug fixes. So we definitely
> need to find some solution. Not necessarily THE solution; we can always
> revise the process. But the current state hurts us (= Sugar Labs) very
> much.

I'm not saying things are ok, just that complaining about what we have
now is not going to fix anything by itself.

> What do you think about a model where we have some git repo that
> everyone can commit to after they got, say, at least two Reviewed-By
> (including one from a core / "long"-term developer)? The contributors
> would get more testing of their work (=> less bugs in the release) and
> the module maintainers would be able to pick resp. skip the patches they
> feel (un)comfortable with.

But then we would need to resync at some point or merging would get
worst with time?

> Another idea would be a mailing list where early versions of patches are
> posted and can get some (incomplete) review. This would allow
> contributors to get fast & easy feedback with a limited amount of time
> spent for the reviewers. Reviews could just point out a subset of issues;
> a thorough review and deciding whether it's good enough to be merged
> would happen like above.

I liked how it worked in sugar-devel for a while, a separate mailing
list would be also ok if the reviews do disturb people or whatever is
the reason for having stopped doing that.

> This would be a perfect fit for a Sugar Camp session; unfortunately I
> don't see one coming up at any place I could commit on attending in
> the near future. But maybe you (Tomeu), Aleksey, Bernie and James
> (Cameron) could try a face-to-face meeting to lay some foundation?
> I imagine Mel would be an awesome moderator.

Most productive discussion about this issue was with Marco whom said
he would try to find time to adapt Patchwork to our needs. I'm pretty
sure he won't mind help from the many people that care about this
issue. Any volunteers?

Regards,

Tomeu

> Sascha
>
> [1] http://en.wikipedia.org/wiki/Deathmatch_(gaming)
> [2] http://en.wikipedia.org/wiki/Cooperative_gameplay
> [3] http://sauerbraten.org/
> --
> http://sascha.silbe.org/
> http://www.infra-silbe.de/
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>