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 Samul Kevin <lo...@gmail.com> on 2009/04/07 12:20:14 UTC
Blluesky PMC report
http://wiki.apache.org/incubator/April2009#preview
Personally, i don't satisfy about the work of last month. Much slower than
i expected. We have to accelerate the speed.
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bill Stoddard <wg...@gmail.com>.
Samul Kevin wrote:
> i've sent the grant file to you, have you received that?
>
Yes, I have it. Will review it tomorrow.
Thanks,
Bill
> 2009/4/15 Bill Stoddard <wg...@gmail.com>
>
>
>> Samul Kevin wrote:
>>
>>> This License Agreement is entered into as of the ___ day of
>>> ____________, ______ by ___________________________ ("Licensor"),
>>> should i fill up blanks the date this project entering incubation or
>>> the date we sign this code grant?
>>>
>>>
>> Use the date the code grant is signed.
>>
>> Bill
>>
>>
>
>
>
>
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
i've sent the grant file to you, have you received that?
2009/4/15 Bill Stoddard <wg...@gmail.com>
> Samul Kevin wrote:
> > This License Agreement is entered into as of the ___ day of
> > ____________, ______ by ___________________________ ("Licensor"),
> > should i fill up blanks the date this project entering incubation or
> > the date we sign this code grant?
> >
>
> Use the date the code grant is signed.
>
> Bill
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bill Stoddard <wg...@gmail.com>.
Samul Kevin wrote:
> This License Agreement is entered into as of the ___ day of
> ____________, ______ by ___________________________ ("Licensor"),
> should i fill up blanks the date this project entering incubation or
> the date we sign this code grant?
>
Use the date the code grant is signed.
Bill
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
This License Agreement is entered into as of the ___ day of
____________, ______ by ___________________________ ("Licensor"),
should i fill up blanks the date this project entering incubation or
the date we sign this code grant?
2009/4/14 Bill Stoddard <wg...@gmail.com>
> Samul Kevin wrote:
>
>> Hi, BIll
>> i finished the coding work and almost complete the testing job. i took a
>> view of the grant file today. Is there a sample to guide me fill all the
>> blanks?
>>
>>
>>
> It's really simple. Here is a code grant from Covalent (now owned by
> SpringSource) for the J2G tool:
>
>
> https://issues.apache.org/jira/secure/attachment/12349176/Covalent-J2G-Tool.pdf
>
> Here are two key points you need to understand:
> 1. Who should sign the code grant?
> I think code developed at XJTU (西安交通大学) as part of the bluesky project is
> owned by the university. I expect Prof Zheng has sufficient authority to
> sign the code grant. (XJTU students will not have the authority to sign the
> code grant). Note that signing the code grant does NOT change, in any way,
> XJTUs ability to do what it wants with the code. The code grant allows the
> ASF to redistribute the code under the Apache License.
>
> 2. You are only granting code to the ASF that was developed at XJTU... the
> grant does not cover code that you pick up and reuse from other projects.
> You must, of course, maintain copyright statements in the code you pick up
> from other sources.
>
> Let me know if you have any other questions.
>
> Bill
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bill Stoddard <wg...@gmail.com>.
Samul Kevin wrote:
> Hi, BIll
> i finished the coding work and almost complete the testing job. i took a
> view of the grant file today. Is there a sample to guide me fill all the
> blanks?
>
>
It's really simple. Here is a code grant from Covalent (now owned by
SpringSource) for the J2G tool:
https://issues.apache.org/jira/secure/attachment/12349176/Covalent-J2G-Tool.pdf
Here are two key points you need to understand:
1. Who should sign the code grant?
I think code developed at XJTU (西安交通大学) as part of the bluesky
project is owned by the university. I expect Prof Zheng has sufficient
authority to sign the code grant. (XJTU students will not have the
authority to sign the code grant). Note that signing the code grant does
NOT change, in any way, XJTUs ability to do what it wants with the code.
The code grant allows the ASF to redistribute the code under the Apache
License.
2. You are only granting code to the ASF that was developed at XJTU...
the grant does not cover code that you pick up and reuse from other
projects.
You must, of course, maintain copyright statements in the code you pick
up from other sources.
Let me know if you have any other questions.
Bill
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
Hi, BIll
i finished the coding work and almost complete the testing job. i took a
view of the grant file today. Is there a sample to guide me fill all the
blanks?
regards,
Kevin
2009/4/8 Bill Stoddard <wg...@gmail.com>
> Samul Kevin wrote:
>
>> 2009/4/8 Bertrand Delacretaz <bd...@apache.org>
>>
>>
>>
>>> Hi,
>>>
>>> On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com>
>>> wrote:
>>>
>>>
>>>> http://wiki.apache.org/incubator/April2009#preview...
>>>>
>>>>
>>> It would be good, IMHO, to include some info about the community side
>>> of things...a recent thread [1] seems to indicate that most of the
>>> BlueSky committers are not working on the project anymore.
>>>
>>>
>>>
>> And the people who are now contributing to the project are not listed as
>> commiters. It does not matter. Though acting slowly, people are working.
>> I
>> am now more seriously concerned about the progress. I thought the
>> speeding
>> of podling would be fastened , however, it is still like turtle
>> crawling....in 1 and 3/4 month since the beginning of this semester. Yes,
>> things get a little better now. But i don't think it is good enough. We
>> have
>> reasons, as having classes or working on several projects simultaneously,
>> nevertheless, i don't think we can treat them as excuses to fend off not
>> doing THIS PROJECT good.
>>
>>
>>
>
> A critical milestone will be getting the code grant in place and checking
> the code into svn. When the code is checked into svn, we can look for
> contributors from outside the XJTU students and begin building a sustainable
> community (I think we have some people in India interested in the project).
> We simply have to begin releasing code from the ASF if the project is
> ever to take the next step to sustainability. Samul, I will work with you
> this week to do the next round of code review;
> Here is the software grant that XJTU needs to submit for code developed by
> XJTU: http://www.apache.org/licenses/software-grant.txt
> Please review and begin preparing it.
>
> Now... I have a very difficult question to ask...
> Bluesky project relies heavily on video technology, most of which is not
> suitable for redistribution by the ASF (due to licensing terms and
> condition). The team has made a great effort over the past year to scrub
> the project clean of incompatibly licensed code, but is it enough? My
> concern is that the project will never be able to resolve the difficulties
> around the licensing of the video technologies... and that maybe the ASF is
> not the best home for Bluesky for this reason.
> My question... can we really succeed in realizing the goals of the bluesky
> project under the license and legal constraints imposed by the ASF? Is it
> really possible?
>
> Bill
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
2009/4/10 Bill Stoddard <wg...@gmail.com>
>
> 2009/4/10 Bill Stoddard <wg...@gmail.com>
>>
>>
>>
>>>
>>> My concern is not with the team... my concern is with the technology, or
>>> to
>>> be precise, my concern is with the licensing of the technology. The ASF
>>> places restrictions on what kind of software licenses we can use. Can we
>>> find suitable alternatives to the GPL components Bluesky relies on? I am
>>> waiting on the team to tell me. If the answer is no, then we have to
>>> face
>>> up to reality... there is no shame in admitting defeat if there are
>>> forces
>>> beyond our control guiding our choices. We can move the project to a
>>> different venue (sourceforge maybe?) and distribute Bluesky as GPL code?
>>> I
>>> don't want to admit defeat just yet... I hope the team can solve the
>>> problem... but if solving the problem means reinventing ffmpeg, with a
>>> different license, then we really cannot succeed, can we? What other
>>> alternatives do we have?
>>>
>>>
>>>
>> i remember that BSD license does not conflict with ASL. And Theora and
>> Vorbis are both BSD-like . Though it needs discussion in legal-disuss to
>> decide whether it is available under ASL . Personally, i assure about
>> that.
>>
>>
> The ASF can redistribute code under a BSD-like license. No problem with
> that.
>
>> So if we could prove that FFmpeg could be replaced by Theora and Vorbis,
>> this problem surely can be solved. I will start the comparion after i
>> finish
>> coding a moldue, which probably would be completed tonight. The only thing
>> i
>> am concerned is that i can't forecast the time this comparison takes....
>>
>>
>>
> Good Luck
>
Thanks, May Confucius be with me.^_^
>
> Bill
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bill Stoddard <wg...@gmail.com>.
> 2009/4/10 Bill Stoddard <wg...@gmail.com>
>
>
>>
>> My concern is not with the team... my concern is with the technology, or to
>> be precise, my concern is with the licensing of the technology. The ASF
>> places restrictions on what kind of software licenses we can use. Can we
>> find suitable alternatives to the GPL components Bluesky relies on? I am
>> waiting on the team to tell me. If the answer is no, then we have to face
>> up to reality... there is no shame in admitting defeat if there are forces
>> beyond our control guiding our choices. We can move the project to a
>> different venue (sourceforge maybe?) and distribute Bluesky as GPL code? I
>> don't want to admit defeat just yet... I hope the team can solve the
>> problem... but if solving the problem means reinventing ffmpeg, with a
>> different license, then we really cannot succeed, can we? What other
>> alternatives do we have?
>>
>>
> i remember that BSD license does not conflict with ASL. And Theora and
> Vorbis are both BSD-like . Though it needs discussion in legal-disuss to
> decide whether it is available under ASL . Personally, i assure about that.
>
The ASF can redistribute code under a BSD-like license. No problem with
that.
> So if we could prove that FFmpeg could be replaced by Theora and Vorbis,
> this problem surely can be solved. I will start the comparion after i finish
> coding a moldue, which probably would be completed tonight. The only thing i
> am concerned is that i can't forecast the time this comparison takes....
>
>
Good Luck
Bill
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
2009/4/10 Bill Stoddard <wg...@gmail.com>
> Samul Kevin wrote:
>
>> 2009/4/8 Bill Stoddard <wg...@gmail.com>
>>
>>
>>
>>> Samul Kevin wrote:
>>>
>>>
>>>
>>>> 2009/4/8 Bertrand Delacretaz <bd...@apache.org>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> http://wiki.apache.org/incubator/April2009#preview...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> It would be good, IMHO, to include some info about the community side
>>>>> of things...a recent thread [1] seems to indicate that most of the
>>>>> BlueSky committers are not working on the project anymore.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> And the people who are now contributing to the project are not listed
>>>> as
>>>> commiters. It does not matter. Though acting slowly, people are
>>>> working.
>>>> I
>>>> am now more seriously concerned about the progress. I thought the
>>>> speeding
>>>> of podling would be fastened , however, it is still like turtle
>>>> crawling....in 1 and 3/4 month since the beginning of this semester.
>>>> Yes,
>>>> things get a little better now. But i don't think it is good enough. We
>>>> have
>>>> reasons, as having classes or working on several projects
>>>> simultaneously,
>>>> nevertheless, i don't think we can treat them as excuses to fend off not
>>>> doing THIS PROJECT good.
>>>>
>>>>
>>>>
>>>>
>>>>
>>> A critical milestone will be getting the code grant in place and checking
>>> the code into svn. When the code is checked into svn, we can look for
>>> contributors from outside the XJTU students and begin building a
>>> sustainable
>>> community (I think we have some people in India interested in the
>>> project).
>>> We simply have to begin releasing code from the ASF if the project is
>>> ever to take the next step to sustainability. Samul, I will work with
>>> you
>>> this week to do the next round of code review;
>>> Here is the software grant that XJTU needs to submit for code developed
>>> by
>>> XJTU: http://www.apache.org/licenses/software-grant.txt
>>> Please review and begin preparing it.
>>>
>>>
>>
>> ok, i will dig into it as soon as finish my coding work.
>>
>>
>>
>>> Now... I have a very difficult question to ask...
>>> Bluesky project relies heavily on video technology, most of which is not
>>> suitable for redistribution by the ASF (due to licensing terms and
>>> condition). The team has made a great effort over the past year to
>>> scrub
>>> the project clean of incompatibly licensed code, but is it enough? My
>>> concern is that the project will never be able to resolve the
>>> difficulties
>>> around the licensing of the video technologies... and that maybe the ASF
>>> is
>>> not the best home for Bluesky for this reason.
>>>
>>>
>>
>> yes, the critical part of Bluesky system is video and audio tech. Surely
>> we
>> can't us FFmpeg, but at least we could try to find a suitalbe replacement
>> which in my opinion, there is chance that this problem could be solved.
>>
>>
>>
>>> My question... can we really succeed in realizing the goals of the
>>> bluesky
>>> project under the license and legal constraints imposed by the ASF? Is it
>>> really possible?
>>>
>>>
>>>
>>
>> i talked to a friend today. And she analized me as a man who has good
>> traits except self-confidence. she thought that I always think about the
>> worst part so that i am used to be hesitating on doing things. Though i
>> am
>> gradually change this defect these days, no shame to say, i guest it
>> contributes most in my not finding a girlfriend-_-!.
>> i assume to complete this project as to hitch a girl who you love but
>> pretty hard to chase. there are two way beyond, get drunk (countless wine
>> for triumph)or get fucked (lose like hell). Actually, like many people, i
>> didn't anticipate the success of this project at first. But gradually, i
>> found that there is chance we could make it if we sacrifice time to
>> contribute. The chance might be tiny if you chase the girl while it is
>> naught if you just bury the love in the bottom of your heart. Even if the
>> projcet fail at last, i want a decent end after my toiling days and hours.
>> Where there is a will, there is a way. To my understanding, the future
>> of
>> podling of Bluesky lies on the will of us -- participators of this
>> project.
>> If we were all determined, i don't believe we could not success. I throw
>> the
>> same question to my companions, since we've started it, how could end it?
>> sucessfully, decently or shamely.
>>
>>
>>
> ^_^
>
>
> My concern is not with the team... my concern is with the technology, or to
> be precise, my concern is with the licensing of the technology. The ASF
> places restrictions on what kind of software licenses we can use. Can we
> find suitable alternatives to the GPL components Bluesky relies on? I am
> waiting on the team to tell me. If the answer is no, then we have to face
> up to reality... there is no shame in admitting defeat if there are forces
> beyond our control guiding our choices. We can move the project to a
> different venue (sourceforge maybe?) and distribute Bluesky as GPL code? I
> don't want to admit defeat just yet... I hope the team can solve the
> problem... but if solving the problem means reinventing ffmpeg, with a
> different license, then we really cannot succeed, can we? What other
> alternatives do we have?
>
i remember that BSD license does not conflict with ASL. And Theora and
Vorbis are both BSD-like . Though it needs discussion in legal-disuss to
decide whether it is available under ASL . Personally, i assure about that.
So if we could prove that FFmpeg could be replaced by Theora and Vorbis,
this problem surely can be solved. I will start the comparion after i finish
coding a moldue, which probably would be completed tonight. The only thing i
am concerned is that i can't forecast the time this comparison takes....
>
> Bill
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bill Stoddard <wg...@gmail.com>.
Samul Kevin wrote:
> 2009/4/8 Bill Stoddard <wg...@gmail.com>
>
>
>> Samul Kevin wrote:
>>
>>
>>> 2009/4/8 Bertrand Delacretaz <bd...@apache.org>
>>>
>>>
>>>
>>>
>>>> Hi,
>>>>
>>>> On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> http://wiki.apache.org/incubator/April2009#preview...
>>>>>
>>>>>
>>>>>
>>>> It would be good, IMHO, to include some info about the community side
>>>> of things...a recent thread [1] seems to indicate that most of the
>>>> BlueSky committers are not working on the project anymore.
>>>>
>>>>
>>>>
>>>>
>>> And the people who are now contributing to the project are not listed as
>>> commiters. It does not matter. Though acting slowly, people are working.
>>> I
>>> am now more seriously concerned about the progress. I thought the
>>> speeding
>>> of podling would be fastened , however, it is still like turtle
>>> crawling....in 1 and 3/4 month since the beginning of this semester. Yes,
>>> things get a little better now. But i don't think it is good enough. We
>>> have
>>> reasons, as having classes or working on several projects simultaneously,
>>> nevertheless, i don't think we can treat them as excuses to fend off not
>>> doing THIS PROJECT good.
>>>
>>>
>>>
>>>
>> A critical milestone will be getting the code grant in place and checking
>> the code into svn. When the code is checked into svn, we can look for
>> contributors from outside the XJTU students and begin building a sustainable
>> community (I think we have some people in India interested in the project).
>> We simply have to begin releasing code from the ASF if the project is
>> ever to take the next step to sustainability. Samul, I will work with you
>> this week to do the next round of code review;
>> Here is the software grant that XJTU needs to submit for code developed by
>> XJTU: http://www.apache.org/licenses/software-grant.txt
>> Please review and begin preparing it.
>>
>
> ok, i will dig into it as soon as finish my coding work.
>
>
>> Now... I have a very difficult question to ask...
>> Bluesky project relies heavily on video technology, most of which is not
>> suitable for redistribution by the ASF (due to licensing terms and
>> condition). The team has made a great effort over the past year to scrub
>> the project clean of incompatibly licensed code, but is it enough? My
>> concern is that the project will never be able to resolve the difficulties
>> around the licensing of the video technologies... and that maybe the ASF is
>> not the best home for Bluesky for this reason.
>>
>
> yes, the critical part of Bluesky system is video and audio tech. Surely we
> can't us FFmpeg, but at least we could try to find a suitalbe replacement
> which in my opinion, there is chance that this problem could be solved.
>
>
>> My question... can we really succeed in realizing the goals of the bluesky
>> project under the license and legal constraints imposed by the ASF? Is it
>> really possible?
>>
>>
>
> i talked to a friend today. And she analized me as a man who has good
> traits except self-confidence. she thought that I always think about the
> worst part so that i am used to be hesitating on doing things. Though i am
> gradually change this defect these days, no shame to say, i guest it
> contributes most in my not finding a girlfriend-_-!.
> i assume to complete this project as to hitch a girl who you love but
> pretty hard to chase. there are two way beyond, get drunk (countless wine
> for triumph)or get fucked (lose like hell). Actually, like many people, i
> didn't anticipate the success of this project at first. But gradually, i
> found that there is chance we could make it if we sacrifice time to
> contribute. The chance might be tiny if you chase the girl while it is
> naught if you just bury the love in the bottom of your heart. Even if the
> projcet fail at last, i want a decent end after my toiling days and hours.
> Where there is a will, there is a way. To my understanding, the future of
> podling of Bluesky lies on the will of us -- participators of this project.
> If we were all determined, i don't believe we could not success. I throw the
> same question to my companions, since we've started it, how could end it?
> sucessfully, decently or shamely.
>
>
^_^
My concern is not with the team... my concern is with the technology, or
to be precise, my concern is with the licensing of the technology. The
ASF places restrictions on what kind of software licenses we can use.
Can we find suitable alternatives to the GPL components Bluesky relies
on? I am waiting on the team to tell me. If the answer is no, then we
have to face up to reality... there is no shame in admitting defeat if
there are forces beyond our control guiding our choices. We can move
the project to a different venue (sourceforge maybe?) and distribute
Bluesky as GPL code? I don't want to admit defeat just yet... I hope
the team can solve the problem... but if solving the problem means
reinventing ffmpeg, with a different license, then we really cannot
succeed, can we? What other alternatives do we have?
Bill
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
2009/4/9 Luciano Resende <lu...@gmail.com>
> On Wed, Apr 8, 2009 at 10:29 AM, Samul Kevin <lo...@gmail.com>
> wrote:
> >> Now... I have a very difficult question to ask...
> >> Bluesky project relies heavily on video technology, most of which is not
> >> suitable for redistribution by the ASF (due to licensing terms and
> >> condition). The team has made a great effort over the past year to
> scrub
> >> the project clean of incompatibly licensed code, but is it enough? My
> >> concern is that the project will never be able to resolve the
> difficulties
> >> around the licensing of the video technologies... and that maybe the ASF
> is
> >> not the best home for Bluesky for this reason.
> >
> > yes, the critical part of Bluesky system is video and audio tech. Surely
> we
> > can't us FFmpeg, but at least we could try to find a suitalbe replacement
> > which in my opinion, there is chance that this problem could be solved.
> >
> >
>
> With the disclaimer that I don't know much about the internals and
> challenges in BlueSky code, can this problem be workarounded/solved by
> requiring the user to download some software that is capable to do the
> video/audio work... and we just delegate to it when we need to play a
> video/audio ? Similar to what we have in some Linux distribution,
> where it by default does not support mp3, but if you download a given
> piece of software (e.g xmms) you can listen to mp3 music.
>
i guess there is difference. Bluesky code include the head files of FFmpeg,
so i don't think this problem could be solved just by installing FFmpeg on
user's machine....
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Luciano Resende <lu...@gmail.com>.
On Wed, Apr 8, 2009 at 10:29 AM, Samul Kevin <lo...@gmail.com> wrote:
>> Now... I have a very difficult question to ask...
>> Bluesky project relies heavily on video technology, most of which is not
>> suitable for redistribution by the ASF (due to licensing terms and
>> condition). The team has made a great effort over the past year to scrub
>> the project clean of incompatibly licensed code, but is it enough? My
>> concern is that the project will never be able to resolve the difficulties
>> around the licensing of the video technologies... and that maybe the ASF is
>> not the best home for Bluesky for this reason.
>
> yes, the critical part of Bluesky system is video and audio tech. Surely we
> can't us FFmpeg, but at least we could try to find a suitalbe replacement
> which in my opinion, there is chance that this problem could be solved.
>
>
With the disclaimer that I don't know much about the internals and
challenges in BlueSky code, can this problem be workarounded/solved by
requiring the user to download some software that is capable to do the
video/audio work... and we just delegate to it when we need to play a
video/audio ? Similar to what we have in some Linux distribution,
where it by default does not support mp3, but if you download a given
piece of software (e.g xmms) you can listen to mp3 music.
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
2009/4/8 Bill Stoddard <wg...@gmail.com>
> Samul Kevin wrote:
>
>> 2009/4/8 Bertrand Delacretaz <bd...@apache.org>
>>
>>
>>
>>> Hi,
>>>
>>> On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com>
>>> wrote:
>>>
>>>
>>>> http://wiki.apache.org/incubator/April2009#preview...
>>>>
>>>>
>>> It would be good, IMHO, to include some info about the community side
>>> of things...a recent thread [1] seems to indicate that most of the
>>> BlueSky committers are not working on the project anymore.
>>>
>>>
>>>
>> And the people who are now contributing to the project are not listed as
>> commiters. It does not matter. Though acting slowly, people are working.
>> I
>> am now more seriously concerned about the progress. I thought the
>> speeding
>> of podling would be fastened , however, it is still like turtle
>> crawling....in 1 and 3/4 month since the beginning of this semester. Yes,
>> things get a little better now. But i don't think it is good enough. We
>> have
>> reasons, as having classes or working on several projects simultaneously,
>> nevertheless, i don't think we can treat them as excuses to fend off not
>> doing THIS PROJECT good.
>>
>>
>>
>
> A critical milestone will be getting the code grant in place and checking
> the code into svn. When the code is checked into svn, we can look for
> contributors from outside the XJTU students and begin building a sustainable
> community (I think we have some people in India interested in the project).
> We simply have to begin releasing code from the ASF if the project is
> ever to take the next step to sustainability. Samul, I will work with you
> this week to do the next round of code review;
> Here is the software grant that XJTU needs to submit for code developed by
> XJTU: http://www.apache.org/licenses/software-grant.txt
> Please review and begin preparing it.
ok, i will dig into it as soon as finish my coding work.
>
>
> Now... I have a very difficult question to ask...
> Bluesky project relies heavily on video technology, most of which is not
> suitable for redistribution by the ASF (due to licensing terms and
> condition). The team has made a great effort over the past year to scrub
> the project clean of incompatibly licensed code, but is it enough? My
> concern is that the project will never be able to resolve the difficulties
> around the licensing of the video technologies... and that maybe the ASF is
> not the best home for Bluesky for this reason.
yes, the critical part of Bluesky system is video and audio tech. Surely we
can't us FFmpeg, but at least we could try to find a suitalbe replacement
which in my opinion, there is chance that this problem could be solved.
>
> My question... can we really succeed in realizing the goals of the bluesky
> project under the license and legal constraints imposed by the ASF? Is it
> really possible?
>
i talked to a friend today. And she analized me as a man who has good
traits except self-confidence. she thought that I always think about the
worst part so that i am used to be hesitating on doing things. Though i am
gradually change this defect these days, no shame to say, i guest it
contributes most in my not finding a girlfriend-_-!.
i assume to complete this project as to hitch a girl who you love but
pretty hard to chase. there are two way beyond, get drunk (countless wine
for triumph)or get fucked (lose like hell). Actually, like many people, i
didn't anticipate the success of this project at first. But gradually, i
found that there is chance we could make it if we sacrifice time to
contribute. The chance might be tiny if you chase the girl while it is
naught if you just bury the love in the bottom of your heart. Even if the
projcet fail at last, i want a decent end after my toiling days and hours.
Where there is a will, there is a way. To my understanding, the future of
podling of Bluesky lies on the will of us -- participators of this project.
If we were all determined, i don't believe we could not success. I throw the
same question to my companions, since we've started it, how could end it?
sucessfully, decently or shamely.
>
> Bill
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bill Stoddard <wg...@gmail.com>.
Samul Kevin wrote:
> 2009/4/8 Bertrand Delacretaz <bd...@apache.org>
>
>
>> Hi,
>>
>> On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com> wrote:
>>
>>> http://wiki.apache.org/incubator/April2009#preview...
>>>
>> It would be good, IMHO, to include some info about the community side
>> of things...a recent thread [1] seems to indicate that most of the
>> BlueSky committers are not working on the project anymore.
>>
>>
> And the people who are now contributing to the project are not listed as
> commiters. It does not matter. Though acting slowly, people are working. I
> am now more seriously concerned about the progress. I thought the speeding
> of podling would be fastened , however, it is still like turtle
> crawling....in 1 and 3/4 month since the beginning of this semester. Yes,
> things get a little better now. But i don't think it is good enough. We have
> reasons, as having classes or working on several projects simultaneously,
> nevertheless, i don't think we can treat them as excuses to fend off not
> doing THIS PROJECT good.
>
>
A critical milestone will be getting the code grant in place and
checking the code into svn. When the code is checked into svn, we can
look for contributors from outside the XJTU students and begin building
a sustainable community (I think we have some people in India interested
in the project). We simply have to begin releasing code from the ASF
if the project is ever to take the next step to sustainability. Samul,
I will work with you this week to do the next round of code review;
Here is the software grant that XJTU needs to submit for code developed
by XJTU: http://www.apache.org/licenses/software-grant.txt
Please review and begin preparing it.
Now... I have a very difficult question to ask...
Bluesky project relies heavily on video technology, most of which is not
suitable for redistribution by the ASF (due to licensing terms and
condition). The team has made a great effort over the past year to
scrub the project clean of incompatibly licensed code, but is it
enough? My concern is that the project will never be able to resolve
the difficulties around the licensing of the video technologies... and
that maybe the ASF is not the best home for Bluesky for this reason.
My question... can we really succeed in realizing the goals of the
bluesky project under the license and legal constraints imposed by the
ASF? Is it really possible?
Bill
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
2009/4/8 Bertrand Delacretaz <bd...@apache.org>
> Hi,
>
> On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com> wrote:
> > http://wiki.apache.org/incubator/April2009#preview...
>
> It would be good, IMHO, to include some info about the community side
> of things...a recent thread [1] seems to indicate that most of the
> BlueSky committers are not working on the project anymore.
>
And the people who are now contributing to the project are not listed as
commiters. It does not matter. Though acting slowly, people are working. I
am now more seriously concerned about the progress. I thought the speeding
of podling would be fastened , however, it is still like turtle
crawling....in 1 and 3/4 month since the beginning of this semester. Yes,
things get a little better now. But i don't think it is good enough. We have
reasons, as having classes or working on several projects simultaneously,
nevertheless, i don't think we can treat them as excuses to fend off not
doing THIS PROJECT good.
>
> -Bertrand
>
> [1] http://markmail.org/message/2fp7hs6dxyfb2lyy
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Tue, Apr 7, 2009 at 2:20 PM, Samul Kevin <lo...@gmail.com> wrote:
> http://wiki.apache.org/incubator/April2009#preview...
It would be good, IMHO, to include some info about the community side
of things...a recent thread [1] seems to indicate that most of the
BlueSky committers are not working on the project anymore.
-Bertrand
[1] http://markmail.org/message/2fp7hs6dxyfb2lyy
Re: Blluesky PMC report
Posted by Samul Kevin <lo...@gmail.com>.
i find that the whole group, including me of course, is lack of pressure. i
need to apply some "pressure"....
2009/4/8 Luciano Resende <lu...@gmail.com>
> On Tue, Apr 7, 2009 at 5:20 AM, Samul Kevin <lo...@gmail.com> wrote:
> > http://wiki.apache.org/incubator/April2009#preview
> >
> Thanks Samul
>
> > Personally, i don't satisfy about the work of last month. Much slower
> than
> > i expected. We have to accelerate the speed.
> >
>
> Something to discuss on the list.. how you guys can make faster progress...
>
> > --
> > Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
> >
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: Blluesky PMC report
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Apr 7, 2009 at 5:20 AM, Samul Kevin <lo...@gmail.com> wrote:
> http://wiki.apache.org/incubator/April2009#preview
>
Thanks Samul
> Personally, i don't satisfy about the work of last month. Much slower than
> i expected. We have to accelerate the speed.
>
Something to discuss on the list.. how you guys can make faster progress...
> --
> Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/