Nick, I have not yet updated the ACL's for existing Apache committers. will try to do that when i get a chance.
thanks, dims On Mon, Jun 1, 2009 at 10:47 AM, Nicholas L Gallardo <[email protected]> wrote: > Correction: > > On #2, does that mean that the folks who ARE already Apache committers don't > have svn access? > > Nicholas Gallardo > WebSphere - REST & WebServices Development > [email protected] > Phone: 512-286-6258 > Building: 903 / 5G-016 > Nicholas L Gallardo/Austin/i...@ibmus > > > Nicholas L Gallardo/Austin/i...@ibmus > > 06/01/2009 09:44 AM > > Please respond to > [email protected] > > To > [email protected] > cc > > Subject > Re: [Wink] next steps... > Thanks Dims... > > On #2, does that mean that the folks who aren't already Apache committers > don't have svn access? This is probably outlined in the contribution section > of the incubator docs. I'll go do some self-educating there. > > As for references to employers, agreed. That was more of a recognition that > we will have two known sources to see the project. That said, for those that > are unfamiliar with the Apache process, using employer emails and such is > fine. Dims is referring more to the intent with which we comment. i.e., > we're participating as individuals and not as a corporation. > > Thanks for keeping us in line here... > > Regards, > > -Nick > > Nicholas Gallardo > WebSphere - REST & WebServices Development > [email protected] > Phone: 512-286-6258 > Building: 903 / 5G-016 > Davanum Srinivas <[email protected]> > > Davanum Srinivas <[email protected]> > > 06/01/2009 09:36 AM > > Please respond to > [email protected] > To > [email protected] > cc > Subject > Re: [Wink] next steps... > Nick, Folks, > > #1) I'll let you guys hash it out :) > > #2) Please create a new issue in JIRA and upload the code. I'll upload > the code to svn from there. Please remember to click on the option to > allow apache to use the code when you upload a zip. Typically we drop > the code to a directory called contrib and then copy bits and pieces > to trunk/branches. > > #3) I've created a wiki space in confluence. Please get started here. > I'll figure out how to hook that into the main web site. Lot's of > projects use this mechanism and will help us get started quickly. > http://cwiki.apache.org/confluence/display/WINK/Index > > thanks, > dims > > PS: Everyone, please drop references to your employers :) We are all > here representing ourselves. > > On Mon, Jun 1, 2009 at 10:04 AM, Nicholas L Gallardo > <[email protected]> wrote: >> >> Hi All! >> >> I'm really excited that we've gotten the project off the ground. A huge >> thanks to Dims for helping guide us through the incubator process and >> getting us to this point. >> >> With that... I thought I'd throw out a few ideas for next steps and see >> what people though. >> >> 1) Project Guidelines - Before we start dropping code, it would help if we >> all level set on a set of guidelines for how we want to see the project >> run. I've seen other projects do this with a stated set of guidelines >> that >> are posted publicly. If we do it that way, we have something to refer new >> contributors to so I'm all for that if there are no objections. If there >> are other suggestions, please fire away. >> >> 2) Project Structure - We need to decide on a structure for the >> repository. In the past we've talked about having a structure where each >> of the teams that are contributing code (IBM and HP) could drop their >> entire code base and have it build/run. I still think that's a good idea. >> As a next step there, I'm going to be looking into the incubator process >> website to see if there are any particular constraints wrt project >> structure, etc. >> >> 3) Project Website - We also need to get a project website up and running >> that discusses a little bit about what we're doing and a wiki for some >> common working space. Both of these should be available under the >> incubator resources, but I haven't looked into exactly how we get that >> setup. Does anyone want to look into that? If not, I'm happy to do so >> and >> report back. >> >> 4) First Tasks - Once the above is complete, we're basically ready to kick >> off the project in earnest and start building our runtime. I know the IBM >> team is itching to get to this point and I'd guess the same is true for >> the >> HP team. There was a note that went to the incubator that laid out a >> little bit of this. I'll resurface that and add some detail. Maybe this >> is where we can start laying out some of the planning via the wiki. One >> of >> the first things that comes to mind will be an evaluation period where we >> do some comparison of the HP and IBM codebases to see what features we >> want >> to bring forth in the common runtime. >> >> Anyway... that's what I see for the short term (next day or so) before we >> dive in. I hope everyone else is excited, this should be a fun project! >> >> Cheers, >> >> -Nick >> >> >> Nicholas Gallardo >> WebSphere - REST & WebServices Development >> [email protected] >> Phone: 512-286-6258 >> Building: 903 / 5G-016 > > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > -- Davanum Srinivas :: http://davanum.wordpress.com
