Hi all,
Am .06.2017, 08:39 Uhr, schrieb sospartan <[email protected]>:
On Mon, Jun 12, 2017 at 1:18 PM, Raphael Bircher
<[email protected]>
wrote:
Hi all
So here is what I understand under a good project communication.
All relevant Informations go to the Mailing list.
You have not to bring all Informations to the Mailing list. If you for
example work together with an other person on a problem. You have not
to do
this on the ML. You can use Chat of Face to Face discussion. If you
would
bring all this communication to the Ml, we will have 100 mails per day,
with a load of content not interesting for all. The ML get unreadable,
and
that's the last thing we want.
Ho ever, sometimes you get the feeling that you have something the other
peoples have to know. Than simply stop the private discussion, and drop
a
mail to the list. This can be the following:
1) Compiling problems (everyone can run into it)
We are using travis to run CI. I'll make some change to notify dev@ ML
whenever it failed.
2) Problems who affects others.
2) Start working at a problem (to avoid double work)
4) End of the problem, with a link to the commit, patch or what ever.
About the 3 and 4, we use JIRA to document all WIP issues, which will
send
to ML about anything changed or status updated. Is this count?
In the Apache terms this is enough, yes.
5) DECISION MAKING
The last part is the most important one. Decisions has to be made in
public! There the project has most to work right now!
The last one is also the most difficult. But we should start now. Let's
start with bringing all proposal to the mail list.
Can someone tell me why this is so difficult for you. Do you know how lazy
consensus works?
Regards, Raphael
--
My introduction https://youtu.be/Ln4vly5sxYU
