You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@weex.apache.org by Raphael Bircher <rb...@gmail.com> on 2017/06/12 05:18:08 UTC
Good project communication 1
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
Re: Good project communication 1
Posted by sospartan <so...@gmail.com>.
Now when travis CI Failed, a mail notification will send to dev@
https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=blobdiff;f=.travis.yml;h=9e0e77d6903263a2372fa92d576b66acb3a87ce4;hp=d0b76756567616a85007ca5962d2cb927d5c9637;hb=8e1cc1f62b6f5689bb91bedb4f20786f2b3e03b6;hpb=c689a8ab731b80519bb1e852cce39b2e54a5c36e
On Mon, Jun 12, 2017 at 2:51 PM, Raphael Bircher <rb...@gmail.com>
wrote:
> Hi all,
>
> Am .06.2017, 08:39 Uhr, schrieb sospartan <so...@gmail.com>:
>
> On Mon, Jun 12, 2017 at 1:18 PM, Raphael Bircher <rbircherapache@gmail.com
>> >
>> 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
>
--
Best Regards!
sospartan
http://weex.apache.org/ <https://weex-project.io/>
Re: Good project communication 1
Posted by Raphael Bircher <rb...@gmail.com>.
Hi all,
Am .06.2017, 08:39 Uhr, schrieb sospartan <so...@gmail.com>:
> On Mon, Jun 12, 2017 at 1:18 PM, Raphael Bircher
> <rb...@gmail.com>
> 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
Re: Good project communication 1
Posted by sospartan <so...@gmail.com>.
On Mon, Jun 12, 2017 at 1:18 PM, Raphael Bircher <rb...@gmail.com>
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?
> 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.
> Regards, Raphael
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
--
Best Regards!
sospartan
http://weex.apache.org/ <https://weex-project.io/>