You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bluesky-dev@incubator.apache.org by Bill Stoddard <wg...@gmail.com> on 2009/08/10 14:11:14 UTC
How to proceed - next steps
Bluesky Team,
We need to make plans to take this project to graduation. To graduate,
the project must have code to release and have a sustainable community.
Right now, we don't have code, we don't have a community and we don't
have a plan for acquiring either.
What remains to be done to release working code? What are the blocking
issues preventing us from releasing working code? What is the plan to
work through each blocking issue? Have the GPL/LGPL and other license
compatibility problems been resolved and if not, what is the outlook to
resolving these problems? If you can submit a step by step plan for how
we will get to working code, I will work with the mentors on getting
team members commit access to the project.
Clearly, we need to grant commit access to some new team members.
Please provide a list of proposed new committers, their role in the
project and how long we expect those people to be around. I am
expecting a relatively small list here, so please do not include people
who are unlikely to spend time learning how to work on ASF projects or
make significant contributions. Once I see and review the list, I'll
provide instructions for what to do next.
My plan is to revoke the ids of the inactive members (people who have
graduated and moved on). Will post those id's to this list and give the
team time to review before asking the infrastructure team to revoke the ids.
Thanks
Bill
Re: How to proceed - next steps
Posted by Luciano Resende <lu...@gmail.com>.
Let me apologize in advance for the harshness on this e-mail, but we
are already long ways into Incubation and at least the open discussion
part of "the Apache Way" should be known by all members of the
community at this point.
2009/8/10 Samuel Kevin <lo...@gmail.com>:
> Hi，Bill：
> our summer vacation ranges from 28th,July to 15th,August. And i just came
> back from my hometown where hardly can i connect to internet.
>
> 2009/8/10 Bill Stoddard <wg...@gmail.com>
>
>> Bluesky Team,
>> We need to make plans to take this project to graduation. To graduate, the
>> project must have code to release and have a sustainable community. Right
>> now, we don't have code, we don't have a community and we don't have a plan
>> for acquiring either.
>
> Actually, A rough plan had been made before the beginning of the summer
> vacation. We'd complete it soon after 15th, August.
>
The minute you guys entered incubation, this stopped being the "the
Bluesky Dev Team at XJTU" to become a BlueSky Community at Apache.
Roadmap discussions, what's next kind of plans should be all done on
the project public mailing list, and not in a room with couple local
people. It's not too late, please finalize this planning or whatever
it is in this mailing list, with all students and professors
interacting together with proposed goals and additional comments from
everybody else from the community.
>>
>>
>> What remains to be done to release working code? What are the blocking
>> issues preventing us from releasing working code? What is the plan to work
>> through each blocking issue? Have the GPL/LGPL and other license
>> compatibility problems been resolved and if not, what is the outlook to
>> resolving these problems? If you can submit a step by step plan for how we
>> will get to working code, I will work with the mentors on getting team
>> members commit access to the project.
>
> We've start the replacement of FFmpeg with Theora and Vorbis. But if we
> could solve this problem by compiling FFmpeg into LGPLed and provide FFmpeg
> lib in a non-ASF site, it could save us at least 2 months.
>
I liked that there is a open thread on this issue, I guess that we can
work on the details about this on that thread. The main issue here is
how we are going to make the LGPled code available outside ASF.
>>
>> Clearly, we need to grant commit access to some new team members. Please
>> provide a list of proposed new committers, their role in the project and how
>> long we expect those people to be around. I am expecting a relatively small
>> list here, so please do not include people who are unlikely to spend time
>> learning how to work on ASF projects or make significant contributions.
>> Once I see and review the list, I'll provide instructions for what to do
>> next.
>>
Bill, I'll wait for the "what to do next here", but I'd really like to
see some JIRAs and Patches coming from this new members before they
get any project karma.
> I will contact Dr Jiangshan tomorrow and provide the list soon.
>
Is Dr. Jiangshan participating on the project, how about asking him to
reply to the e-mail thread and give the names on this thread.
Remember, it's all about an open community and open communication...
>>
>> My plan is to revoke the ids of the inactive members (people who have
>> graduated and moved on). Will post those id's to this list and give the
>> team time to review before asking the infrastructure team to revoke the ids.
>>
+1
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: How to proceed - next steps
Posted by Samuel Kevin <lo...@gmail.com>.
Hi，Bill：
our summer vacation ranges from 28th,July to 15th,August. And i just came
back from my hometown where hardly can i connect to internet.
2009/8/10 Bill Stoddard <wg...@gmail.com>
> Bluesky Team,
> We need to make plans to take this project to graduation. To graduate, the
> project must have code to release and have a sustainable community. Right
> now, we don't have code, we don't have a community and we don't have a plan
> for acquiring either.
Actually, A rough plan had been made before the beginning of the summer
vacation. We'd complete it soon after 15th, August.
>
>
> What remains to be done to release working code? What are the blocking
> issues preventing us from releasing working code? What is the plan to work
> through each blocking issue? Have the GPL/LGPL and other license
> compatibility problems been resolved and if not, what is the outlook to
> resolving these problems? If you can submit a step by step plan for how we
> will get to working code, I will work with the mentors on getting team
> members commit access to the project.
We've start the replacement of FFmpeg with Theora and Vorbis. But if we
could solve this problem by compiling FFmpeg into LGPLed and provide FFmpeg
lib in a non-ASF site, it could save us at least 2 months.
>
> Clearly, we need to grant commit access to some new team members. Please
> provide a list of proposed new committers, their role in the project and how
> long we expect those people to be around. I am expecting a relatively small
> list here, so please do not include people who are unlikely to spend time
> learning how to work on ASF projects or make significant contributions.
> Once I see and review the list, I'll provide instructions for what to do
> next.
>
I will contact Dr Jiangshan tomorrow and provide the list soon.
>
> My plan is to revoke the ids of the inactive members (people who have
> graduated and moved on). Will post those id's to this list and give the
> team time to review before asking the infrastructure team to revoke the ids.
>
> Thanks
> Bill
>
--
Bowen Ma a.k.a Samuel Kevin @ Bluesky Dev Team XJTU
Shaanxi Province Key Lab. of Satellite and Terrestrial Network Tech
http://incubator.apache.org/bluesky/
Re: How to proceed - next steps
Posted by Shan Jiang <da...@gmail.com>.
Now, the developers of MERSMP all are in vacation untill almost 22 August.
So the plan of releasing MERSMP working code and the new developers list
will be presented after 22 August.
On Tue, Aug 11, 2009 at 6:58 PM, Shan Jiang <da...@gmail.com> wrote:
> At present ,fortunately, the LGPL-based FFmpeg library has been integrated
> successfully in the Realclass system with dynamic link in testing process
> and the LGPL-based FFmpeg is functional. That is significant for makeing
> Realclass follow ASL! The next stage work is that we release working code of
> Realclass as soon as possible. The plan to release working code will be
> discussed and presented in bluesky-maillist during several days.
>
> Another significant thing is that MERSMP system, another component of
> Bluesky, begin to be submited to Apache SVN. This system is web service
> program based on the B/S architecture by Java. It is another important goal
> for us to release the MERSMP working code. The plan of releasing MERSMP in
> Apache will be discussed in the maillist during several days.
>
> By the way, the new developers of Bluesky will be listed in a few days.
>
>
> On Mon, Aug 10, 2009 at 10:11 PM, Bill Stoddard <wg...@gmail.com>wrote:
>
>> Bluesky Team,
>> We need to make plans to take this project to graduation. To graduate,
>> the project must have code to release and have a sustainable community.
>> Right now, we don't have code, we don't have a community and we don't have a
>> plan for acquiring either.
>>
>> What remains to be done to release working code? What are the blocking
>> issues preventing us from releasing working code? What is the plan to work
>> through each blocking issue? Have the GPL/LGPL and other license
>> compatibility problems been resolved and if not, what is the outlook to
>> resolving these problems? If you can submit a step by step plan for how we
>> will get to working code, I will work with the mentors on getting team
>> members commit access to the project.
>> Clearly, we need to grant commit access to some new team members. Please
>> provide a list of proposed new committers, their role in the project and how
>> long we expect those people to be around. I am expecting a relatively small
>> list here, so please do not include people who are unlikely to spend time
>> learning how to work on ASF projects or make significant contributions.
>> Once I see and review the list, I'll provide instructions for what to do
>> next.
>>
>> My plan is to revoke the ids of the inactive members (people who have
>> graduated and moved on). Will post those id's to this list and give the
>> team time to review before asking the infrastructure team to revoke the ids.
>>
>> Thanks
>> Bill
>>
>
>
>
> --
> Shan Jiang a.k.a dane @ Bluesky Dev Team XJTU
>
--
Shan Jiang a.k.a dane @ Bluesky Dev Team XJTU
Re: How to proceed - next steps
Posted by Shan Jiang <da...@gmail.com>.
At present ,fortunately, the LGPL-based FFmpeg library has been integrated
successfully in the Realclass system with dynamic link in testing process
and the LGPL-based FFmpeg is functional. That is significant for makeing
Realclass follow ASL! The next stage work is that we release working code of
Realclass as soon as possible. The plan to release working code will be
discussed and presented in bluesky-maillist during several days.
Another significant thing is that MERSMP system, another component of
Bluesky, begin to be submited to Apache SVN. This system is web service
program based on the B/S architecture by Java. It is another important goal
for us to release the MERSMP working code. The plan of releasing MERSMP in
Apache will be discussed in the maillist during several days.
By the way, the new developers of Bluesky will be listed in a few days.
On Mon, Aug 10, 2009 at 10:11 PM, Bill Stoddard <wg...@gmail.com>wrote:
> Bluesky Team,
> We need to make plans to take this project to graduation. To graduate, the
> project must have code to release and have a sustainable community. Right
> now, we don't have code, we don't have a community and we don't have a plan
> for acquiring either.
>
> What remains to be done to release working code? What are the blocking
> issues preventing us from releasing working code? What is the plan to work
> through each blocking issue? Have the GPL/LGPL and other license
> compatibility problems been resolved and if not, what is the outlook to
> resolving these problems? If you can submit a step by step plan for how we
> will get to working code, I will work with the mentors on getting team
> members commit access to the project.
> Clearly, we need to grant commit access to some new team members. Please
> provide a list of proposed new committers, their role in the project and how
> long we expect those people to be around. I am expecting a relatively small
> list here, so please do not include people who are unlikely to spend time
> learning how to work on ASF projects or make significant contributions.
> Once I see and review the list, I'll provide instructions for what to do
> next.
>
> My plan is to revoke the ids of the inactive members (people who have
> graduated and moved on). Will post those id's to this list and give the
> team time to review before asking the infrastructure team to revoke the ids.
>
> Thanks
> Bill
>
--
Shan Jiang a.k.a dane @ Bluesky Dev Team XJTU