Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DEACB6CC4 for ; Thu, 30 Jun 2011 08:38:38 +0000 (UTC) Received: (qmail 71490 invoked by uid 500); 30 Jun 2011 08:38:29 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 70638 invoked by uid 500); 30 Jun 2011 08:38:17 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 70619 invoked by uid 99); 30 Jun 2011 08:38:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2011 08:38:11 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of grobmeier@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-iw0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2011 08:38:06 +0000 Received: by iwn4 with SMTP id 4so1903946iwn.6 for ; Thu, 30 Jun 2011 01:37:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=YKve3D8pSb5UnIh719Ine1GGjVCkaFyJ2gcjE0cT0Xs=; b=vyF7dJ3KQ0rD85Q5O76LiSfcgo8JqbXzFsuFLzLh10Pl7Oad3JCWqhRVxJnnz9+o/e DMt2YzXWOQO6Hn1eXNBik2IFgOUHsSM34J6udMDxdvuy+SSxQ2ewsZsZ+bYxmZ2gsRaV e1cgD3d8V6C/+v3yUNeWhCXJa/ReMdGEudRfU= Received: by 10.42.177.8 with SMTP id bg8mr1720075icb.144.1309423065076; Thu, 30 Jun 2011 01:37:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.170.2 with HTTP; Thu, 30 Jun 2011 01:37:23 -0700 (PDT) In-Reply-To: References: <769513.63076.qm@web161428.mail.bf1.yahoo.com>

From: Christian Grobmeier Date: Thu, 30 Jun 2011 10:37:23 +0200 Message-ID: Subject: Re: Bluesky calls for a new mentor! To: general@incubator.apache.org Cc: bluesky-dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > I believe projects from =C2=A0school could also rock in Apache as well. Y= ou can > look down up on us but you can't deny others. This is not the point. The point is, if you have contributors who have no apache id, they a) need to sign an ICLA b) need to create an Jira issue and attach an svn diff there, ticking the "allowed to use for the ASF" box c) need to ask development questions on the mailinglist, not by ICQ, MSN or whatever You can actually work with students, no problem. But it should happen visible. Even when you are in the same room, it should be visible to all other parties around the world. Otherwise you will never get an development community. > =C2=A0 =C2=A0 I had a propose that community give us the last chance for = 1-2month and > certain member could become our mentor to lead us finish =C2=A0releasing = the > newest version. =C2=A0 During this time slot. What you would see includes= : I am not sure if the term "mentor" is used well here. A "mentor" is not here to help you in development questions. A mentors role is to oversee how the project progresses, guide people to work after the apache way. After 3 years you should already know about the apache way and mentor should be obsolet (from a teaching role only). A mentor is for sure NO project lead. He can point you to the according docs of "how to release code", for example. > =C2=A0 1. gradually increasing discussion in bluesky-dev mailing list. > =C2=A0 Meaningless discussion would not count. ALL discussion must happen on list, from now on. If it didn't happen on list, it didn't happen, as a wise man once said. > =C2=A0 2. committing of source code after they were cleaned up. > =C2=A0 Inactive committers would be revoked and new committers would appl= y to join > =C2=A0 in. Now or never. It is "commit then review" Potential new committers must show their interest on the mailing list - otherwise your mentors cannot decide if they should support a invitation or not. As you know, new committers must be voted in. The discussion should also happen before, on list. > =C2=A0 3. preparing for what release needs and make the release successfu= l. Thus > =C2=A0 the new developers and committers could completely experienced the= release > =C2=A0 process and know about "How" things are done in Apache community b= etter. You should start working on the apache way even before the release. If it didn't work well before, it will not work well while releasing. > =C2=A0 =C2=A0 If community accept my suggestion, individually, i want the= BlueSky > project under strict surveillance by community members. If we can't fulfi= ll > what we just promised, then just kick us out of here and i would have not= ing > to say. I (personally) have no problems with waiting just another 2 or 3 months. I cannot imagine anyone would like to step up as a mentor at the moment. My suggestion: try to work out the apache way now. Use jira and the mailinglist. Students contribute patches through jira. Committers apply them. And so on. If that all happens, your Jira is full of contributions and your mailinglist full of discussions. If that is the case, come back to this list and ask for a mentor again - probably somebody is willling to step up again. If you have more questions on "how apache works", I am pretty sure you'll get an answer on this list. Cheers, Christian > =C2=A0 =C2=A0 Well, suppose we live through that, besides working in Apac= he way, we > would continually working on to evolve BlueSky to make it much more easie= r > to use in =C2=A0e-learning area and used in a larger scope(now bluesky ha= s > been deployed in China and is about to be applied in India ), so that mor= e > students in undeveloped district could share the same high quality educat= ion > as the developed area. > =C2=A0 =C2=A0 =C2=A0Sincerely, i would invite you Ralph to be our mentor = in this 1-2 month > if you were not busy enough and willing to guide us. Don't feel sorry if = you > want to refuse me.TOT > regards, > Kevin > > 2011/6/30 Ralph Goers > >> Sorry, but the explanation below makes things sound even worse. Apache >> projects are not here to give students a place to do school work. What y= ou >> have described is not a community. =C2=A0If the project cannot build a c= ommunity >> of people who are interested in the project for more than a school term = then >> it doesn't belong here. >> >> Ralph >> >> On Jun 29, 2011, at 8:12 PM, SamuelKevin wrote: >> >> > Hi, Noel: >> > >> > 2011/6/30 Noel J. Bergman >> > >> >> Joe Schaefer wrote: >> >>> Chen Liu wrote: >> >>>> We propose to move future development of BlueSky to the Apache >> Software >> >>>> Foundation in order to build a broader user and developer community= . >> >> >> >>> You are supposed to be doing your development work in the ASF >> subversion >> >>> repository, using ASF mailing lists, as peers. >> >> >> >> Chen, as Joe points out, these are what BlueSky should have been doin= g >> for >> >> the past three (3) years, and yet we still here a proposal for the >> future. >> >> >> >>> Looking at the (limited) commit history, there is a total imbalance >> >> between >> >>> the number of people associated with the development work (20+) and = the >> >>> number of people with Apache accounts here (2). >> >> >> >> I guess i can explain that. Most of the developers of BlueSky project >> are >> > students. As you all know, students come =C2=A0when they join in schoo= l and go >> > after they graduate. So the active developers are around 10. Like we u= sed >> to >> > have 5 committers, but now we only have 2 committers in active. >> > >> >> Again, as Joe points out, ALL of BlueSky development should been done >> via >> >> the ASF infrastructure, not periodically synchronized. =C2=A0We are a >> >> development >> >> community, not a remote archive. >> >> >> >>> What we really need you to discuss are *plans*, how you will impleme= nt >> >> them, >> >>> who will implement them, and how you will collaborate in the codebas= e >> as >> >> peers. >> >> >> >> Joe, again, has this on the money. =C2=A0The BlueSky project must imm= ediately >> >> make significant strides to rectify these issues. =C2=A0Now, not late= r. >> >> >> >> We should see: >> >> >> >> 1) All current code in the ASF repository. >> >> 2) All development via ASF accounts (get the rest of the people signe= d >> >> up). >> >> 3) Ddevelopment discussion on the mailing list. >> >> 4) All licensing issues cleaned up. >> >> >> >> According to what you've listed, i would forward your suggestion to >> bluesky >> > dev list and wish we could make a quick response after >> > discussion. Appreciate your help. >> > regards, >> > Kevin >> > >> >> =C2=A0 =C2=A0 =C2=A0 --- Noel >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> >> For additional commands, e-mail: general-help@incubator.apache.org >> >> >> >> >> > >> > >> > -- >> > Bowen Ma a.k.a Samuel Kevin @ Bluesky Dev Team =C2=A0 =C2=A0XJTU >> > Shaanxi Province Key Lab. of Satellite and Terrestrial Network Tech >> > http://incubator.apache.org/bluesky/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> > > > -- > Bowen Ma a.k.a Samuel Kevin @ Bluesky Dev Team =C2=A0 =C2=A0XJTU > Shaanxi Province Key Lab. of Satellite and Terrestrial Network Tech > http://incubator.apache.org/bluesky/ > --=20 http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org