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)
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.
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!

Regards, Raphael

--
My introduction https://youtu.be/Ln4vly5sxYU

Reply via email to