incubator-bluesky-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samul Kevin <>
Subject Re: code review and some requests
Date Tue, 10 Mar 2009 08:20:02 GMT
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.


2009/3/9 Bernd Fondermann <>

> On Sat, Mar 7, 2009 at 09:39, Samul Kevin <> 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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message