[Rock-dev] Rock development discussions

[Sylvain Joyeux]

> On 09/19/2014 10:33 AM, Jakob Schwendner wrote:
>> I have a feeling we need to improve the way we discuss our development of
>> Rock "development?" Or rather "maintenance"?
>>   A few ideas for this:
>> * do a video chat once a month. I would start with anyone who wants to
>> participate. When we reach number over the technology limit we could always
>> limit later to core development team.
> +1
>
> Maybe a video format where every guy sits alone in front of his own
> computer and talks to the group? This would equalize the perceived
> barrier between each participant, no matter how much physical distance
> there is between us.
+1 to "separate videos" (no more than 2 persons per screen). Meetings
where one person is outside and the rest in the same room is just
useless for the person that is not in the room. As soon as the
"in-room people" start talking to each other (which happens quite
naturally very often), the lone guy just does not understand what is
going on.

> What about Google hangout? Though I only know this tool as a Viewer, not
> as a User... To access the informations we could create links into
> specific positions inside the masses of video streams. Not very private,
> though.
I like the hangouts suggestion. Since the goal is to be public,
there's no issue with privacy to me ...

>> * Record decisions and discussions. The wiki is probably the best way for
>> now. I kind of liked the loomio tool, though.
> loomio... Looks like a full-featured "community council", suitable for
> the formal decisions? We also need to spread and collect the "implicit
> documentation" about the internals of the framework.
I don't think we're enough people so that adding yet-another-website
makes sense, honestly. We're what, 5 active developers (tops !) ? We
should probably vote on that one though ...;-)

> They just ask their co-worker or do a "autoproj rebuild".
The knowledgeable co-workers will need to have the discipline to
either fix the problem (on the machines *and* in Rock) or redirect
them to rock-users instead of answering questions. What one has to
stress there is that it is a much better solution even for them,
because "the knowledgeable co-worker" is not always around while there
is often someone reading rock-users.

Sylvain