Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 12870 invoked from network); 20 Jan 2004 19:17:15 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Jan 2004 19:17:15 -0000 Received: (qmail 62481 invoked by uid 500); 20 Jan 2004 19:17:06 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 62431 invoked by uid 500); 20 Jan 2004 19:17:06 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 62418 invoked from network); 20 Jan 2004 19:17:06 -0000 Received: from unknown (HELO logictrends.com) (64.190.71.44) by daedalus.apache.org with SMTP; 20 Jan 2004 19:17:06 -0000 Date: Tue, 20 Jan 2004 14:25:26 -0500 Message-Id: <200401201425.AA321847962@logictrends.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: "Wes McKean" Reply-To: To: "Apache Directory Developers List" , "Apache Directory Developers List" Subject: Re: Jump Starting Development X-Mailer: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Before much more coding is done, I would like to see our incubatino web site brought up to date, on par with at least Geronimo. I would like to see the list of components/tasks that need to be worked on, designed, developed whatever. I understand that we don't assign these to folks. They volunteer to work on them, and then we note it on the web site who is working on that module. >Thanks for asking these questions. Every now and then we need to >take the pulse of the project and maybe hit the reset button. Constructive questions need to come from the right direction... Here are my primary areas of focus: 1. ASN.1 stuff (Java side) 2. Database stuff (I've rewritten it twice now :-) and I want to share what I have done with the community. and, if you want 3. Project Coordinator ( I won't say manager here :-) Let me know Alex, and I'll help you compile a project plan/list. Who has volunteered to keep the web-site up to date? Wes ---------- Original Message ---------------------------------- From: Alex Karasulu Reply-To: "Apache Directory Developers List" Date: Tue, 20 Jan 2004 12:05:52 -0500 >Wes, > >> After being in the incubator for several months, and seeing that the vast >> majority of code changes and commits are being done by Alex, I thought it >> would be a good idea to begin a discussion on jump starting development on >> the directory project. Oh, before I continue, let me admit I haven't >> contributed anything :-) > >Well that's not true. You've contributed alot but if you're refering to >you subversion issues getting in the way since entering the incubator etc >I understand. > >> Here's my wish list: >> >> 1. I would like to see the server broken up into a list of components with >> the work that needs to be performed on each. I would like to see a list of >> goals for the project and website as a whole as well. > >I'll try to work on this although some subsystems right now are >more placeholders. Their breakdown into fine grained components >are still to be determine. I'll try to indicate this where I can. >Perhaps I'll collect this info in http://www.apache.org/~akarasulu >under my user account. > >> 2. I would like to see a who is working on what. > >Jeff: > * C/C++ ASN.1 Stuff > * Java LDAP Client Code > * LDAP Protocol & Stress Testing Suite > >Alex: > * ... give me time to compile this list > >Robb: > * Don't know. > >> 3. I would like us all to recruit more developers. > >Whhhew! Me too that was one of the main reasons for incubation >and this is slowly happening. I'm begining to realize that I >have to work on various things to build and strengthen this >community. On the top of my list is documentation, some process >for keeping people in sync with each other - but then again >that's what this list is primarily for. > >> I believe that if the tasks are laid out, people would work on what >> interests them. The goals would be measurable, and we all would know what >> we could work on to fit in our schedule. I also think this would go a long >> way towards attracting new developers. > >+1 but keep in mind members of this team should not be here to >be assigned tasks. They should pick up whatever they feel they >want to do. This is not a company - its a community. No one >should be directing it but there can be facilitators though - >perhaps this is what you mean. > >> Let's face it. Alex has been doing the majority of the coding. However, if >> he burns out and quits the project, we will lose our visionairy, and that >> concerns me. > >Me too. It's very important to me to have more core developers on >Eve. Back in sourceforge we were working a bit better but the >process of entering the incubator and changing a few things put us >back a tiny bit. Now though we should be able to gain that loss >very rapidly through the things we gain from the incubator. I >personally have to do more to get people more involved and that >starts with more documentation. > >> Maybe we can get some good feed back from the Apache veterans. > >I'm listening intently for any advice. > >Thanks for asking these questions. Every now and then we need to >take the pulse of the project and maybe hit the reset button. > >Alex > > >