Re: Disclaimer text for incubated projects

2003-10-04 Thread Berin Lautenbach
Noel J. Bergman wrote: The draft seems to be using RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt) terminology. If so, let's please reference the RFC early in the document so that readers can find the operation definitions (thus establishing common volcabulary). Whoops. There is a line in there :

RE: Disclaimer text for incubated projects

2003-10-04 Thread Noel J. Bergman
Berin Lautenbach wrote: > [lots of really good stuff] The draft seems to be using RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt) terminology. If so, let's please reference the RFC early in the document so that readers can find the operation definitions (thus establishing common volcabulary). Dav

RE: [PROPOSAL] fold incubator-site into incubator CVS ( Re: Posting and tracking project tasks )

2003-10-04 Thread Noel J. Bergman
Nicola Ken Barozzi wrote: > Noel J. Bergman wrote: > > To a certain extent, the incubator is evolving, too. If evolving procedures > > that are not being disseminated, that's one problem. > > > I propose that a good way to address this situation will be to make active > > use of the new JIRA insta

RE: [Fwd: Fwd: Re: Disclaimer text for incubated projects]

2003-10-04 Thread Noel J. Bergman
Julie, > I'm still trying to figure out how everything works around > here. Any and all constructive feedback is welcome. And we are trying to improve the incubation process, so please feel free to make constructive suggestions as to what is/isn't working, and how you feel things can be improved

RE: Mentor vs. Shepherd

2003-10-04 Thread Noel J. Bergman
Mentor is preferable to me, too. :-) It is understood in technology circles, and has a different connotation than Shephard. The project has to mature, and develop as a Community, rather than a flock of coding sheep. People might perceive a Shephard as someone who will "do it" for them, which is

Re: Disclaimer text for incubated projects

2003-10-04 Thread Berin Lautenbach
David Jencks wrote: As podlings are not yet fully accepted as part of the Apache Software Foundation, any software releases (including code held in publically available CVS) made by Podlings will not be endorsed by the ASF. Podlings in Incubation SHALL NOT perform any releases of software

Re: Disclaimer text for incubated projects

2003-10-04 Thread Nicola Ken Barozzi
Sam Ruby wrote: Nicola Ken Barozzi wrote: Sam Ruby wrote: ... It seems to me a disclaimer on the website, perhaps also in the root directory of the associated CVS trees, and a process which prevents any official "release" to be created by projects in incubation should be more than sufficient.

Re: Disclaimer text for incubated projects

2003-10-04 Thread Rodent of Unusual Size
Tetsuya Kitahata wrote: > > People often lost the precious e-mails due to the current > Here "SPAM" > There "SPAM" > Everywhere "SPAM", "SPAM" oh, you mean like all the 'apache newsletter' messages i've received on just about every single asf list i'm on? > In the business world, "inbubation"/

Re: Disclaimer text for incubated projects

2003-10-04 Thread Stephen McConnell
David Jencks wrote: On Saturday, October 4, 2003, at 03:20 AM, Berin Lautenbach wrote: == Releases == As podlings are not yet fully accepted as part of the Apache Software Foundation, any software releases (including code held in publically available CVS) made by Podlings will not be endorse

Re: Disclaimer text for incubated projects

2003-10-04 Thread David Jencks
On Saturday, October 4, 2003, at 03:20 AM, Berin Lautenbach wrote: == Releases == As podlings are not yet fully accepted as part of the Apache Software Foundation, any software releases (including code held in publically available CVS) made by Podlings will not be endorsed by the ASF. Po

Re: incubation disclaimer and infrastructural reshuffle

2003-10-04 Thread Leo Simons
Stephen McConnell wrote: BZZZT, BZZZT, the above statement presumes that "release" and "publication" are one and the same. The distinction between a vote to "release" and a vote to "publish" is in my option an import aspect of active community based decision making. Communities vote to release,

Re: incubation disclaimer and infrastructural reshuffle

2003-10-04 Thread Stephen McConnell
Leo Simons wrote: Sam Ruby wrote: I would go further. Essentially, a release by a podling would require a vote by the incubator PMC to do so. a release by *any* project requires its supervising PMC to vote it through. Since for podlings, the supervising PMC is by definition the incubator PMC

Re: incubation disclaimer and infrastructural reshuffle

2003-10-04 Thread Leo Simons
Sam Ruby wrote: I would go further. Essentially, a release by a podling would require a vote by the incubator PMC to do so. a release by *any* project requires its supervising PMC to vote it through. Since for podlings, the supervising PMC is by definition the incubator PMC, you're not going any

Re: incubation disclaimer and infrastructural reshuffle

2003-10-04 Thread Sam Ruby
Leo Simons wrote: Branding The podling website should have a notice () on its front page pointing out that its under incubation, a notice in the root of its cvs (in README.txt or WARNING.txt or ...), a notice inside and alongside any downloadables it produces in a prominent location, and i

Re: Disclaimer text for incubated projects

2003-10-04 Thread Sam Ruby
Nicola Ken Barozzi wrote: Sam Ruby wrote: Tetsuya Kitahata wrote: On Fri, 3 Oct 2003 19:00:57 -0400 "Noel J. Bergman" <[EMAIL PROTECTED]> wrote: Judging from the move we made with james, CVS was easy. ezmlm a bit more involved, but our users seemed to find us easily enough when the list address

some source files seem to have @author tag containing copyright notices

2003-10-04 Thread robert burrell donkin
(cc'ing general to inform the pmc. if this is not the right procedure then hopefully someone will post a correction.) some of the source code (still under weblogic packages) contains some strange @author tags. example: @author Copyright (c) 1997 by WebLogic, Inc. All Rights Reserved. i think t

Re: Disclaimer text for incubated projects

2003-10-04 Thread Stephen McConnell
Berin Lautenbach wrote: is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the . Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized

Re: jUDDI - incubation status?

2003-10-04 Thread Tetsuya Kitahata
Status of this project?? I posted to [EMAIL PROTECTED] (for soliciting articles for the upcoming Apache Newsletter Issue #2) and found that the mail has been rejected. Status? -- Tetsuya. ([EMAIL PROTECTED]) On Wed, 24 Sep 2003 18:39:47 -0700 (PDT) (Subject: jUDDI - incubation status?) Davanum

incubation disclaimer and infrastructural reshuffle (was: Disclaimer...)

2003-10-04 Thread Leo Simons
Hi gang, long e-mail, with analysis of pros and cons, and some policy draft on some issues Berin didn't address yet last time I checked. Disclaimers --- a question at hand: how do we make clear to everyone that a project and all its related assets are "under incubation" (along with what th

Re: Disclaimer text for incubated projects

2003-10-04 Thread Nicola Ken Barozzi
Tetsuya Kitahata wrote: On Sat, 04 Oct 2003 11:49:01 +0200 Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: Sorry, but this has not worked. I guess you had a karma for jakarta-site2 and you had left 1. [EMAIL PROTECTED] 2. [EMAIL PROTECTED] 3. [EMAIL PROTECTED] .. at http://jakarta.apache.org/sit

Re: Disclaimer text for incubated projects

2003-10-04 Thread Berin Lautenbach
All, FWIW - the following is the extract (at time of writing) from the draft Policy document relating to the current discussion. I am about to move this into the drafts section of the site, so people can start hacking within CVS. Cheers, Berin = Podling Constraints = == Branding == P

Re: Disclaimer text for incubated projects

2003-10-04 Thread Stephen McConnell
Tetsuya Kitahata wrote: From my point of view, "disclaimer" page would be enough and the best "alternative". +1 -- Stephen J. McConnell mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comm

Re: Disclaimer text for incubated projects

2003-10-04 Thread Tetsuya Kitahata
On Sat, 04 Oct 2003 11:49:01 +0200 Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: > Sorry, but this has not worked. I guess you had a karma for jakarta-site2 and you had left 1. [EMAIL PROTECTED] 2. [EMAIL PROTECTED] 3. [EMAIL PROTECTED] .. at http://jakarta.apache.org/site/mail2.html as the

Re: Disclaimer text for incubated projects

2003-10-04 Thread Nicola Ken Barozzi
Sam Ruby wrote: Tetsuya Kitahata wrote: On Fri, 3 Oct 2003 19:00:57 -0400 "Noel J. Bergman" <[EMAIL PROTECTED]> wrote: Judging from the move we made with james, CVS was easy. ezmlm a bit more involved, but our users seemed to find us easily enough when the list address changed from [EMAIL PROTEC

Re: Auto-update of incubator site

2003-10-04 Thread Nicola Ken Barozzi
Sam Ruby wrote: Berin Lautenbach wrote: ... If there isn't - does anyone mind if I set up a cron job to update the site from CVS every six hours? I just added this to the list of sites that I automatically update (every six hours). Thanks :-) -- Nicola Ken Barozzi [EMAIL PROT

Re: Disclaimer text for incubated projects

2003-10-04 Thread Nicola Ken Barozzi
Sam Ruby wrote: Greg Stein wrote: ... Good point. My post was more aimed at the people who are shepherding the project (e.g. Sam) rather than the developers. IMO, Sam should know better, and should have fixed this long ago. Let me turn this around. You note a problem with a prior project. You p

Re: Disclaimer text for incubated projects

2003-10-04 Thread Sam Ruby
Tetsuya Kitahata wrote: On Fri, 3 Oct 2003 19:00:57 -0400 "Noel J. Bergman" <[EMAIL PROTECTED]> wrote: Judging from the move we made with james, CVS was easy. ezmlm a bit more involved, but our users seemed to find us easily enough when the list address changed from [EMAIL PROTECTED] to [EMAIL PRO

Re: Disclaimer text for incubated projects

2003-10-04 Thread Sam Ruby
Greg Stein wrote: But what pisses me off the most is that I raised this about wsrp4j a couple weeks ago, but it wasn't fixed. Aha, Okay. I think that the folks in wsrp4j just did not know how to do. It happens all the time. People should not blame ones' ignorance. Agreed. And I raised the point tw

Re: Auto-update of incubator site

2003-10-04 Thread Sam Ruby
Nicola Ken Barozzi wrote: Berin Lautenbach wrote: Peoples, Is there a cron job anywhere that auto-updates the incubator site out of CVS? http://incubator.apache.org/updating_docs.html doesn't mention one, but at the same time doesn't indicate that you have to log into the site to do a "cvs up

Re: Disclaimer text for incubated projects

2003-10-04 Thread Sam Ruby
Berin Lautenbach wrote: Sam Ruby wrote: Can I ask that you document the process of updating the site? Looks like it's already there, but not very obvious. I will add to the side-bar, but in the interim : http://incubator.apache.org/updating_docs.html Thank you! That is more than sufficient for

Re: Auto-update of incubator site

2003-10-04 Thread Sam Ruby
Berin Lautenbach wrote: Peoples, Is there a cron job anywhere that auto-updates the incubator site out of CVS? http://incubator.apache.org/updating_docs.html doesn't mention one, but at the same time doesn't indicate that you have to log into the site to do a "cvs up". If there isn't - does a

Re: Auto-update of incubator site

2003-10-04 Thread Tetsuya Kitahata
I would rather like to get the script for forrestbot which is used and running at forrestbot.cocoondev.org. I would be able to re-produce sites and trigger the forrestbot batch from my win2k server, I guess. What I need would be "getting the forrestbot sample script from Jeff" ... that would be e

Re: Mentor vs. Shepherd

2003-10-04 Thread Nicola Ken Barozzi
Berin Lautenbach wrote: Nicola and others, I note in the DraftPolicy document you have done a s/shepherd/mentor/g. Is this our final call on the title for these people? I.e. should I make the same change to the Process Description? As I wrote in the commit doc, I regard Mentor as more a counsel

[PROPOSAL] fold incubator-site into incubator CVS ( Re: Posting and tracking project tasks )

2003-10-04 Thread Nicola Ken Barozzi
Noel J. Bergman wrote: To a certain extent, the incubator is evolving, too. If evolving procedures that are not being disseminated, that's one problem. I propose that a good way to address this situation will be to make active use of the new JIRA install, Serge and I have scheduled for next Thursd

Re: Disclaimer text for incubated projects

2003-10-04 Thread Nicola Ken Barozzi
Jim Jagielski wrote: Nicola is sending/has sent to you the result of the vote. I was waiting for 72 hours after the ACK of the board, as is required, to declare you guys in the PMC, but it has leaked out ;-) In any case, you guys are in :-) On Friday, October 3, 2003, at 02:20 PM, Ted Leung wro

Re: technology sucks

2003-10-04 Thread Nicola Ken Barozzi
Tetsuya Kitahata wrote: Hi, On Tue, 23 Sep 2003 09:02:59 +0200 Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote: I'm the moderator there, and I didn't see your mail. I apologise for missing it, it was not intentional. Sorry. Okay, then can the config of the [EMAIL PROTECTED] be changed? When? Who? How

Re: Auto-update of incubator site

2003-10-04 Thread Nicola Ken Barozzi
Berin Lautenbach wrote: Peoples, Is there a cron job anywhere that auto-updates the incubator site out of CVS? http://incubator.apache.org/updating_docs.html doesn't mention one, but at the same time doesn't indicate that you have to log into the site to do a "cvs up". If there isn't - does a