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/02/06 00:35:52 UTC
code review and some requests
I've started looking at some of the files in the dtu and I have some
questions:
asyncsocketex.h and clientsocket.h each contain some class declarations
that sound very familiar, CAsyncSocketEx and CClientSocket, so I googled
them... and got many hits. Are these original files or were they
pulled from another project?
dtunit.h includes a file jmutex.h... where does jmutex.h come from?
I have similar question on multiple files and it is just not feasible
for me to review each file in this level of detail..
Before I spend more time doing code review, I would like to see several
things:
0) A full accounting of all bluesky code that was pulled from other
projects.
It is not wrong to pull code from other projects to include in bluesky,
provided the other project license allow you to do so. However, we MUST
ALWAYS give proper attribution to any code we copy into bluesky. The
original author's copyright statements must NOT be removed and we must
also capture that copyright statement in the LICENSE file that will be
distributed with bluesky. Here is the license file that is distributed
with Apache HTTP Server:
http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
Scroll down into the LICENSE file, and you will discover many copyright
statements from other projects for code that Apache HTTP Server is using.
If bluesky uses code from other projects, we must clearly identify the
code and include the copyright statements in the LICENSE file, just as
the Apache HTTP Server project has done.
1) the bluesky team should identify each external library needed to
build and run each bluesky component (dtu, student, teacher and tserver)
For each external library, please report a) the name of the library b)
brief description of the service the library provides c) how it links
into bluesky (static at build time or dynamic at runtime) and also d)
the license of the library. Updating this link for each bluesky
component would be good:
http://incubator.apache.org/bluesky/files/html/lib_support.html
2) Instructions on how to build each component.
3) Instructions on how to get bluesky running (a demo)
I need Steps 0-2 completed before I can conduct more code reviews.
Let me know if you have any question.
Thanks
Bill
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi, Bill:
we've done 0-2 steps. And recording of the demo of Bluesky is on going.
What should we do next to accelerate the process of commiting the code?
Regards,
Kevin
2009/2/6 Bill Stoddard <wg...@gmail.com>
> I've started looking at some of the files in the dtu and I have some
> questions:
>
> asyncsocketex.h and clientsocket.h each contain some class declarations
> that sound very familiar, CAsyncSocketEx and CClientSocket, so I googled
> them... and got many hits. Are these original files or were they pulled
> from another project?
>
> dtunit.h includes a file jmutex.h... where does jmutex.h come from?
>
> I have similar question on multiple files and it is just not feasible for
> me to review each file in this level of detail..
>
>
> Before I spend more time doing code review, I would like to see several
> things:
>
> 0) A full accounting of all bluesky code that was pulled from other
> projects.
>
> It is not wrong to pull code from other projects to include in bluesky,
> provided the other project license allow you to do so. However, we MUST
> ALWAYS give proper attribution to any code we copy into bluesky. The
> original author's copyright statements must NOT be removed and we must also
> capture that copyright statement in the LICENSE file that will be
> distributed with bluesky. Here is the license file that is distributed with
> Apache HTTP Server:
>
> http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
>
> Scroll down into the LICENSE file, and you will discover many copyright
> statements from other projects for code that Apache HTTP Server is using.
>
> If bluesky uses code from other projects, we must clearly identify the code
> and include the copyright statements in the LICENSE file, just as the Apache
> HTTP Server project has done.
>
> 1) the bluesky team should identify each external library needed to build
> and run each bluesky component (dtu, student, teacher and tserver)
>
> For each external library, please report a) the name of the library b)
> brief description of the service the library provides c) how it links into
> bluesky (static at build time or dynamic at runtime) and also d) the license
> of the library. Updating this link for each bluesky component would be good:
>
> http://incubator.apache.org/bluesky/files/html/lib_support.html
>
> 2) Instructions on how to build each component.
> 3) Instructions on how to get bluesky running (a demo)
>
>
> I need Steps 0-2 completed before I can conduct more code reviews.
>
> Let me know if you have any question.
> Thanks
> Bill
>
>
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi, Bill:
1 and 2 questions will be finished in one week. We could fasten steps if
you think we are too slow.
regards
Kevin.
2009/2/6 Bill Stoddard <wg...@gmail.com>
> I've started looking at some of the files in the dtu and I have some
> questions:
>
> asyncsocketex.h and clientsocket.h each contain some class declarations
> that sound very familiar, CAsyncSocketEx and CClientSocket, so I googled
> them... and got many hits. Are these original files or were they pulled
> from another project?
>
> dtunit.h includes a file jmutex.h... where does jmutex.h come from?
>
> I have similar question on multiple files and it is just not feasible for
> me to review each file in this level of detail..
>
>
> Before I spend more time doing code review, I would like to see several
> things:
>
> 0) A full accounting of all bluesky code that was pulled from other
> projects.
>
> It is not wrong to pull code from other projects to include in bluesky,
> provided the other project license allow you to do so. However, we MUST
> ALWAYS give proper attribution to any code we copy into bluesky. The
> original author's copyright statements must NOT be removed and we must also
> capture that copyright statement in the LICENSE file that will be
> distributed with bluesky. Here is the license file that is distributed with
> Apache HTTP Server:
>
> http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
>
> Scroll down into the LICENSE file, and you will discover many copyright
> statements from other projects for code that Apache HTTP Server is using.
>
> If bluesky uses code from other projects, we must clearly identify the code
> and include the copyright statements in the LICENSE file, just as the Apache
> HTTP Server project has done.
>
> 1) the bluesky team should identify each external library needed to build
> and run each bluesky component (dtu, student, teacher and tserver)
>
> For each external library, please report a) the name of the library b)
> brief description of the service the library provides c) how it links into
> bluesky (static at build time or dynamic at runtime) and also d) the license
> of the library. Updating this link for each bluesky component would be good:
>
> http://incubator.apache.org/bluesky/files/html/lib_support.html
>
> 2) Instructions on how to build each component.
> 3) Instructions on how to get bluesky running (a demo)
>
>
> I need Steps 0-2 completed before I can conduct more code reviews.
>
> Let me know if you have any question.
> Thanks
> Bill
>
>
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi, Bernd:
Thank you, i guess i fully understand now. I am also anticipating that
day we could solve all the problems and sit down, instead of drinking beer,
have some tea.^_^
regards
Kevin
2009/3/11 Bernd Fondermann <be...@googlemail.com>
> On Tue, Mar 10, 2009 at 09:20, Samul Kevin <lo...@gmail.com> wrote:
> > Hi, Bernd:
> > sorry, i don't mean that. For It's just a rough plan so we want to
> make
> > it look like "decent" after we have a discussion. Then we post it in
> mailing
> > list for another discussion. We've made lots of stupid mistakes, so we
> don't
> > wanna make things worse.
>
> You won't make anything better by having two separate communities, one
> internal team, one at Apache Incubator.
> Not the code or the reporting is your first and foremost problem. One
> day this is all solved and we will meet and drink some beer and have
> fun about it.
> The biggest problem is that you make a difference between your on-site
> team and the rest (us). Please share your decision making process with
> us. Then we are able to share our ideas about it with you.
>
> Thank you,
>
> Bernd
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: code review and some requests
Posted by Bernd Fondermann <be...@googlemail.com>.
On Tue, Mar 10, 2009 at 09:20, Samul Kevin <lo...@gmail.com> wrote:
> Hi, Bernd:
> sorry, i don't mean that. For It's just a rough plan so we want to make
> it look like "decent" after we have a discussion. Then we post it in mailing
> list for another discussion. We've made lots of stupid mistakes, so we don't
> wanna make things worse.
You won't make anything better by having two separate communities, one
internal team, one at Apache Incubator.
Not the code or the reporting is your first and foremost problem. One
day this is all solved and we will meet and drink some beer and have
fun about it.
The biggest problem is that you make a difference between your on-site
team and the rest (us). Please share your decision making process with
us. Then we are able to share our ideas about it with you.
Thank you,
Bernd
Re: code review and some requests
Posted by J Aaron Farr <fa...@apache.org>.
On Wed 11 Mar 2009 15:23, Samul Kevin <lo...@gmail.com> wrote:
> Hi Aaron:
> Thank you. i really appriciate what you've said and the help you've
> given us.
> “加油” is good， but “多可以” is not that suitable, it should be “都可以”。 “多”
> means many， “都” means both or all。
Oops. My Chinese literacy has become quite embarrassing. I promise
I'll do better if engaged in an actual conversation. :-)
>
> 2009/3/11 J Aaron Farr <fa...@apache.org>
>
>> On Tue 10 Mar 2009 16:20, Samul Kevin <lo...@gmail.com> wrote:
>>
>> > Hi, Bernd:
>> > sorry, i don't mean that. For It's just a rough plan so we want to
>> make
>> > it look like "decent" after we have a discussion. Then we post it in
>> mailing
>> > list for another discussion. We've made lots of stupid mistakes, so we
>> don't
>> > wanna make things worse.
>> > As to the silence of the dev-mailing list, due to the delay of
>> > commiting source code to svn repos. we can't bring on too many things.
>> eg,
>> > if we are talking about code problem or newly developing bluesky system,
>> how
>> > could other people get involved in?
>> > We feel embarrassed or some kind of shame for retarding process of
>> > podling. We wanna make huge progress in this semester.So, we wish in two
>> > weeks we could achieve the standard to upload source code.
>>
>> It's ok. Every podling goes through some mistakes. Don't worry about
>> it.
>>
>> The best way you can make a better impression now is by using the
>> mailing list for all your discussions. Even if you're not sure about
>> what you want to do, discuss it here. Even if the code isn't in Apache
>> yet, you can still discuss it here. In English, in Chinese. 多可以。
>>
>> > And some of the committers were graduated from university, new comers
>> > like me are gradually learning this system and trying to contribute to
>> > this system. i don't think i am doing well but i will drain to do my
>> > best.
>>
>> You're doing fine. It's a lot to learn and you have many people here
>> willing to help. 加油！
>>
>> --
>> J Aaron Farr jadetower.com [US] +1 724-964-4515
>> 馮傑仁 cubiclemuses.com [HK] +852 8123-7905
>>
--
J Aaron Farr jadetower.com [US] +1 724-964-4515
馮傑仁 cubiclemuses.com [HK] +852 8123-7905
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi Aaron:
Thank you. i really appriciate what you've said and the help you've
given us.
�����͡� is good�� but ������ԡ� is not that suitable, it should be �������ԡ��� ���ࡱ
means many�� ������ means both or all��
regards
Kevin
2009/3/11 J Aaron Farr <fa...@apache.org>
> On Tue 10 Mar 2009 16:20, Samul Kevin <lo...@gmail.com> wrote:
>
> > Hi, Bernd:
> > sorry, i don't mean that. For It's just a rough plan so we want to
> make
> > it look like "decent" after we have a discussion. Then we post it in
> mailing
> > list for another discussion. We've made lots of stupid mistakes, so we
> don't
> > wanna make things worse.
> > As to the silence of the dev-mailing list, due to the delay of
> > commiting source code to svn repos. we can't bring on too many things.
> eg,
> > if we are talking about code problem or newly developing bluesky system,
> how
> > could other people get involved in?
> > We feel embarrassed or some kind of shame for retarding process of
> > podling. We wanna make huge progress in this semester.So, we wish in two
> > weeks we could achieve the standard to upload source code.
>
> It's ok. Every podling goes through some mistakes. Don't worry about
> it.
>
> The best way you can make a better impression now is by using the
> mailing list for all your discussions. Even if you're not sure about
> what you want to do, discuss it here. Even if the code isn't in Apache
> yet, you can still discuss it here. In English, in Chinese. ����ԡ�
>
> > And some of the committers were graduated from university, new comers
> > like me are gradually learning this system and trying to contribute to
> > this system. i don't think i am doing well but i will drain to do my
> > best.
>
> You're doing fine. It's a lot to learn and you have many people here
> willing to help. ���ͣ�
>
> --
> J Aaron Farr jadetower.com [US] +1 724-964-4515
> �T���� cubiclemuses.com [HK] +852 8123-7905
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: code review and some requests
Posted by J Aaron Farr <fa...@apache.org>.
On Tue 10 Mar 2009 16:20, Samul Kevin <lo...@gmail.com> wrote:
> Hi, Bernd:
> sorry, i don't mean that. For It's just a rough plan so we want to make
> it look like "decent" after we have a discussion. Then we post it in mailing
> list for another discussion. We've made lots of stupid mistakes, so we don't
> wanna make things worse.
> As to the silence of the dev-mailing list, due to the delay of
> commiting source code to svn repos. we can't bring on too many things. eg,
> if we are talking about code problem or newly developing bluesky system, how
> could other people get involved in?
> We feel embarrassed or some kind of shame for retarding process of
> podling. We wanna make huge progress in this semester.So, we wish in two
> weeks we could achieve the standard to upload source code.
It's ok. Every podling goes through some mistakes. Don't worry about
it.
The best way you can make a better impression now is by using the
mailing list for all your discussions. Even if you're not sure about
what you want to do, discuss it here. Even if the code isn't in Apache
yet, you can still discuss it here. In English, in Chinese. 多可以。
> And some of the committers were graduated from university, new comers
> like me are gradually learning this system and trying to contribute to
> this system. i don't think i am doing well but i will drain to do my
> best.
You're doing fine. It's a lot to learn and you have many people here
willing to help. 加油！
--
J Aaron Farr jadetower.com [US] +1 724-964-4515
馮傑仁 cubiclemuses.com [HK] +852 8123-7905
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi, Bernd:
sorry, i don't mean that. For It's just a rough plan so we want to make
it look like "decent" after we have a discussion. Then we post it in mailing
list for another discussion. We've made lots of stupid mistakes, so we don't
wanna make things worse.
As to the silence of the dev-mailing list, due to the delay of
commiting source code to svn repos. we can't bring on too many things. eg,
if we are talking about code problem or newly developing bluesky system, how
could other people get involved in?
We feel embarrassed or some kind of shame for retarding process of
podling. We wanna make huge progress in this semester.So, we wish in two
weeks we could achieve the standard to upload source code.
And some of the committers were graduated from university, new comers
like me are gradually learning this system and trying to contribute to this
system. i don't think i am doing well but i will drain to do my best.
Regards
Kevin
2009/3/9 Bernd Fondermann <be...@googlemail.com>
> On Sat, Mar 7, 2009 at 09:39, Samul Kevin <lo...@gmail.com> wrote:
> > we've already sketch a basic plan of work in this semester. We'll discuss
> it
> > in next Tuesday, and i will write an formal plan in mailing list.
>
> Ahm, what? Sorry, but if you are saying that you want to do internal
> planning and then after the discussion has taken place want to come to
> the public list than you are again and still mistaken about how your
> "open source project" is required to be run here at Apache: All
> decision making is done on the project's public mailing list, from
> start to the end.
>
> I don't see any code or discussion, very few people participating
> compared to the long list of initial committers.
>
> Does it make sense to wait any longer for improvements?
>
> Bernd
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi, Luciano:
Thanks for your kindness suggestion^_^ , but i guess we won't bother
you to do that.
regards
Kevin
2009/3/9 Luciano Resende <lu...@gmail.com>
> On Mon, Mar 9, 2009 at 3:22 AM, J Aaron Farr <fa...@apache.org> wrote:
> > On Mon 09 Mar 2009 13:34, Bernd Fondermann <
> bernd.fondermann@googlemail.com> wrote:
> >
> >> On Sat, Mar 7, 2009 at 09:39, Samul Kevin <lo...@gmail.com>
> wrote:
> >>> we've already sketch a basic plan of work in this semester. We'll
> discuss it
> >>> in next Tuesday, and i will write an formal plan in mailing list.
> >>
> >> I don't see any code or discussion, very few people participating
> >> compared to the long list of initial committers.
> >
> > I agree with Bernd on this.
> >
> > If you want BlueSky to continue in Incubation, you need to have all
> > discussions on this mailing list. If you have a meeting, then you
> > should post the minutes/notes to the mailing list. Everyone who wants
> > to contribute to the project should communicate here.
> >
>
> +1
>
> > If there are concerns about language, please use Chinese. This is
> > better than silence.
> >
>
> Well, this will be like silence to me :) but indeed, even if things
> get written in Chinese, there are Google or other tools that can do a
> somewhat decent translation to English and other languages.
>
> > --
> > J Aaron Farr jadetower.com [US] +1 724-964-4515
> > �T���� cubiclemuses.com [HK] +852 8123-7905
> >
>
>
>
> --
> 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: code review and some requests
Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Mar 9, 2009 at 3:22 AM, J Aaron Farr <fa...@apache.org> wrote:
> On Mon 09 Mar 2009 13:34, Bernd Fondermann <be...@googlemail.com> wrote:
>
>> On Sat, Mar 7, 2009 at 09:39, Samul Kevin <lo...@gmail.com> wrote:
>>> we've already sketch a basic plan of work in this semester. We'll discuss it
>>> in next Tuesday, and i will write an formal plan in mailing list.
>>
>> I don't see any code or discussion, very few people participating
>> compared to the long list of initial committers.
>
> I agree with Bernd on this.
>
> If you want BlueSky to continue in Incubation, you need to have all
> discussions on this mailing list. If you have a meeting, then you
> should post the minutes/notes to the mailing list. Everyone who wants
> to contribute to the project should communicate here.
>
+1
> If there are concerns about language, please use Chinese. This is
> better than silence.
>
Well, this will be like silence to me :) but indeed, even if things
get written in Chinese, there are Google or other tools that can do a
somewhat decent translation to English and other languages.
> --
> J Aaron Farr jadetower.com [US] +1 724-964-4515
> 馮傑仁 cubiclemuses.com [HK] +852 8123-7905
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: code review and some requests
Posted by J Aaron Farr <fa...@apache.org>.
On Mon 09 Mar 2009 13:34, Bernd Fondermann <be...@googlemail.com> wrote:
> On Sat, Mar 7, 2009 at 09:39, Samul Kevin <lo...@gmail.com> wrote:
>> we've already sketch a basic plan of work in this semester. We'll discuss it
>> in next Tuesday, and i will write an formal plan in mailing list.
>
> I don't see any code or discussion, very few people participating
> compared to the long list of initial committers.
I agree with Bernd on this.
If you want BlueSky to continue in Incubation, you need to have all
discussions on this mailing list. If you have a meeting, then you
should post the minutes/notes to the mailing list. Everyone who wants
to contribute to the project should communicate here.
If there are concerns about language, please use Chinese. This is
better than silence.
--
J Aaron Farr jadetower.com [US] +1 724-964-4515
馮傑仁 cubiclemuses.com [HK] +852 8123-7905
Re: code review and some requests
Posted by Bernd Fondermann <be...@googlemail.com>.
On Sat, Mar 7, 2009 at 09:39, Samul Kevin <lo...@gmail.com> wrote:
> we've already sketch a basic plan of work in this semester. We'll discuss it
> in next Tuesday, and i will write an formal plan in mailing list.
Ahm, what? Sorry, but if you are saying that you want to do internal
planning and then after the discussion has taken place want to come to
the public list than you are again and still mistaken about how your
"open source project" is required to be run here at Apache: All
decision making is done on the project's public mailing list, from
start to the end.
I don't see any code or discussion, very few people participating
compared to the long list of initial committers.
Does it make sense to wait any longer for improvements?
Bernd
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
we've already sketch a basic plan of work in this semester. We'll discuss it
in next Tuesday, and i will write an formal plan in mailing list.
regards
Kevin
2009/3/6 Bill Stoddard <wg...@gmail.com>
> Samul Kevin wrote:
>
>> Hi,Bill
>> The developer of the group is still on vacation. So i can't answer you
>> in detail. But i can 100% sure that they write the code themselves.
>> At first this project was under windows platform, so you can see class
>> like CAsyncSocketEx and CClientSocket are actually in MFC, however, when
>> tranplanting the project to linux, they rewrite the code with the same
>> class
>> name. As to jmutex.h, it is included in jrtplib.check out this url
>> http://research.edm.uhasselt.be/~jori/page/index.php?n=CS.Jrtplib<http://research.edm.uhasselt.be/%7Ejori/page/index.php?n=CS.Jrtplib>
>> .
>> I will tell relevant person to answer your question more specificly as
>> soon as they come back to school.
>>
>>
>
> Hi, Kevin.
> Anything new to report?
>
> Thanks
> Bill
>
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU
Re: code review and some requests
Posted by Bill Stoddard <wg...@gmail.com>.
Samul Kevin wrote:
> Hi,Bill
> The developer of the group is still on vacation. So i can't answer you
> in detail. But i can 100% sure that they write the code themselves.
> At first this project was under windows platform, so you can see class
> like CAsyncSocketEx and CClientSocket are actually in MFC, however, when
> tranplanting the project to linux, they rewrite the code with the same class
> name. As to jmutex.h, it is included in jrtplib.check out this url
> http://research.edm.uhasselt.be/~jori/page/index.php?n=CS.Jrtplib.
> I will tell relevant person to answer your question more specificly as
> soon as they come back to school.
>
Hi, Kevin.
Anything new to report?
Thanks
Bill
Re: code review and some requests
Posted by Samul Kevin <lo...@gmail.com>.
Hi,Bill
The developer of the group is still on vacation. So i can't answer you
in detail. But i can 100% sure that they write the code themselves.
At first this project was under windows platform, so you can see class
like CAsyncSocketEx and CClientSocket are actually in MFC, however, when
tranplanting the project to linux, they rewrite the code with the same class
name. As to jmutex.h, it is included in jrtplib.check out this url
http://research.edm.uhasselt.be/~jori/page/index.php?n=CS.Jrtplib.
I will tell relevant person to answer your question more specificly as
soon as they come back to school.
regards
Kevin
2009/2/6 Bill Stoddard <wg...@gmail.com>
> I've started looking at some of the files in the dtu and I have some
> questions:
>
> asyncsocketex.h and clientsocket.h each contain some class declarations
> that sound very familiar, CAsyncSocketEx and CClientSocket, so I googled
> them... and got many hits. Are these original files or were they pulled
> from another project?
>
> dtunit.h includes a file jmutex.h... where does jmutex.h come from?
>
> I have similar question on multiple files and it is just not feasible for
> me to review each file in this level of detail..
>
>
> Before I spend more time doing code review, I would like to see several
> things:
>
> 0) A full accounting of all bluesky code that was pulled from other
> projects.
>
> It is not wrong to pull code from other projects to include in bluesky,
> provided the other project license allow you to do so. However, we MUST
> ALWAYS give proper attribution to any code we copy into bluesky. The
> original author's copyright statements must NOT be removed and we must also
> capture that copyright statement in the LICENSE file that will be
> distributed with bluesky. Here is the license file that is distributed with
> Apache HTTP Server:
>
> http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE
>
> Scroll down into the LICENSE file, and you will discover many copyright
> statements from other projects for code that Apache HTTP Server is using.
>
> If bluesky uses code from other projects, we must clearly identify the code
> and include the copyright statements in the LICENSE file, just as the Apache
> HTTP Server project has done.
>
> 1) the bluesky team should identify each external library needed to build
> and run each bluesky component (dtu, student, teacher and tserver)
>
> For each external library, please report a) the name of the library b)
> brief description of the service the library provides c) how it links into
> bluesky (static at build time or dynamic at runtime) and also d) the license
> of the library. Updating this link for each bluesky component would be good:
>
> http://incubator.apache.org/bluesky/files/html/lib_support.html
>
> 2) Instructions on how to build each component.
> 3) Instructions on how to get bluesky running (a demo)
>
>
> I need Steps 0-2 completed before I can conduct more code reviews.
>
> Let me know if you have any question.
> Thanks
> Bill
>
>
>
--
Bowen Ma a.k.a Samul Kevin @ Bluesky Dev Team XJTU