Status?

[bill stoddard <bi...@wstoddard.com>]

Bluesky Team,
The mailing list is very quiet....... too quiet... what is the plan for 
preparing code to check into the repository?  What work needs to be 
done, who is doing it and when will it be complete?  Please move any 
internal discussions to this list .. maybe some of the ASF people here 
can help resolve some of the issues.

If this project is to successfully incubate (graduate as an ASF 
project), we need to do a much better job communicating on the 
developer's list.

Bill

Re: Status?

[Shan Jiang <da...@gmail.com>]

We are checking the whole source code of RealClass system component by
component. To avoid the mistake of last commit. We check the source
code recursively. Checking source code include: list all the third
part libs and confirm their license. The result will be shown in
mailing list, after the work of check source code is finished. Any
suggestion for checking source code is expected.

Shan

2008/7/17, bill stoddard <bi...@wstoddard.com>:
> du.haipeng wrote:
>> We are a group of students working in the same room every day so it is
>> easy for us to have face to face discussions whenever we met some
>> problems.
>>
>> We havn't been used to puting all our things on the mail-list and this is
>> badly against the "open and communicate" mind of ASF. So the next step we
>> must try to make full use of it.
>>
>> On the other hand, poor English makes the communication hard, at least
>> from my point of view...
>>
>
> Yes, I completely understand both points you make. I know from first
> hand experience that it's possible to coach a team that works in the
> same room to use a mailing list to communicate. I don't have a simple
> answer for the English barrier. Perhaps it is sufficient for just enough
> communication (in English) to happen on the mailing list to give people
> who are NOT in the same room an understanding of the decisions being
> made and direction the project is taking. This is a real challenge for
> the bluesky team, but you must overcome this challenge to succeed at the
> ASF.
>
> Bill
>

Re: Status?

[bill stoddard <bi...@wstoddard.com>]

du.haipeng wrote:
> We are a group of students working in the same room every day so it is easy for us to have face to face discussions whenever we met some problems.
>
> We havn't been used to puting all our things on the mail-list and this is badly against the "open and communicate" mind of ASF. So the next step we must try to make full use of it.
>
> On the other hand, poor English makes the communication hard, at least from my point of view... 
>   

Yes, I completely understand both points you make. I know from first
hand experience that it's possible to coach a team that works in the
same room to use a mailing list to communicate. I don't have a simple
answer for the English barrier. Perhaps it is sufficient for just enough
communication (in English) to happen on the mailing list to give people
who are NOT in the same room an understanding of the decisions being
made and direction the project is taking. This is a real challenge for
the bluesky team, but you must overcome this challenge to succeed at the
ASF.

Bill

Re: Status?

["du.haipeng" <du...@gmail.com>]

We are a group of students working in the same room every day so it is easy for us to have face to face discussions whenever we met some problems.

We havn't been used to puting all our things on the mail-list and this is badly against the "open and communicate" mind of ASF. So the next step we must try to make full use of it.

On the other hand, poor English makes the communication hard, at least from my point of view... 




du.haipeng
2008-07-17



发件人： bill stoddard
发送时间： 2008-07-17 07:17:17
收件人： bluesky-dev@incubator.apache.org
抄送： 
主题： Status?

Bluesky Team,
The mailing list is very quiet....... too quiet... what is the plan for 
preparing code to check into the repository?  What work needs to be 
done, who is doing it and when will it be complete?  Please move any 
internal discussions to this list .. maybe some of the ASF people here 
can help resolve some of the issues.

If this project is to successfully incubate (graduate as an ASF 
project), we need to do a much better job communicating on the 
developer's list.

Bill