incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: [appeal] Help JSPWiki Graduate!
Date Mon, 10 Aug 2009 03:49:07 GMT
Gee, i hope that more people will assist with this offer
to review your project status. That was supposed to be
your week to have some special attention.

More below ...

Janne Jalkanen wrote:
> >The podling Status page hasn't been updated in ages.
> >
> >Personally i would at least add some News items in there.
> >That would help to encourage more participants and helps
> >the IPMC at graduation review time.
> >There are some items that i expect are already done.
> >Investigate some other projects status files.
> Yes, we're keeping our task list in JIRA instead of the web page,  
> simply because it's a lot easier, and encourages participation more  
> than a static HTML file somewhere.

I know. However, that page is what the incubation docs ask for.
Remember that the Incubator PMC (all volunteers with no time)
currently has 38 projects to oversee. We must have such information
in a consistent place and format.

That is a high-level summary, whereas your Jira can provide
detail for some tasks.

>  We should probably have a link to  
> the relevant JIRA issues so that the info is in one place (as you well  
> know, information kept in multiple locations is always out of date).
> We have multiple news channels out there (a blog, the wiki, an a  
> twitter account).  So perhaps we should just feed the Twitter news  
> stream in a badge onto the page?
> >Clutch shows that there is one new committer since entry.
> It should show two new committers; Harry Metske and Florian Holeczek.   
> Don't know why that is.

Hmmm, but i just showed you in the next sentence.

> >It gets that from the status News section. I tried to find
> >your Incubator Proposal wiki page and compare with the current
> >list of committers, but could not find it.
> The incubator proposal wiki page is at 

I suggest adding a link to it alongside all other proposals
In that way, Incubator PMC members can readily see it
when it comes time for any review.

> >and provide decent patches. Getting more committers
> >should encourage others.
> True...
> >I suggest practicing ahead of time, as it will be less
> >frustrating when you go for the real release. Note down
> >your steps. Look around other projects and TLPs - many
> >have notes about their release process so that other devs
> >can assist and can do it themselves next time.
> Releasing is a process we've done over many times :-).

Of course, but not here at the ASF.

My suggestions were to assist you to avoid the trap of
not having some things ready, therefore your first attempt
at an ASF release might get held up.

> >Most say that whoever is designated the Release Manager
> >needs to be prepared to put in a large amount of time.
> Unfortunately, nobody over here has a large amount of time available :- 
> (.  JSPWiki is *fully* voluntary, which means that other priorities  
> are more important often.  This BTW explains our very long incubation  
> time as well.

Same for many projects. That is one reason why you need to
encourage new committers/PMC members and so help to spread
the knowledge and the administrative workload.

> >License headers:
> >I glanced at some files. Looks okay. If not already done,
> >then i suggest running RAT or using other tools from the
> >"committers" repository.
> >I see that your "LICENSE" file includes references to
> >the supporting products licenses. Personally i think that
> >that is a reasonable solution to a hard maintenance problem.
> >Others say that we are required to display actual text of
> >all licenses there.
> Yes, we chose to put the actual licenses under doc/ with the LICENSE  
> file being a reference to them.  Otherwise it becomes a real PITA to  
> maintain, esp. considering that we've been changing our support  
> libraries quite a lot recently.
> >Hmmm, i think that this file is intended for actual
> >notices that are requested in the various supporting products
> >licenses.
> Never really knew the purpose :-)

There is probably some link in the incubation documentation.
leads to:

> >One thing that you can get ready prior to release
> >is the distribution area at w.a.o/dist/incubator/jspwiki/
> Gotcha.
> >Look around other TLPs. Many have HEADER.html etc. files.
> >(Yes i know that not many other incubating projects do it.)
> >For people who stumble directly to mirrors or worse,
> >directly to w.a.o/dist/ space, rather than going via your
> >project's download page, these notices encourage them to
> >download from the mirrors instead, and provide instructions
> >for download verification. For example see Forrest.
> >We store those ancillary files in our SVN.
> OK, good.  And then a script copies it in the right place during  
> release process, I take it?

See general instructions in

No, the websites are managed in SVN. Your project's
committer does ssh to the server and deliberately does
an 'svn up' (of course after initial checkout) in

Note that that is just the HEADER.html and README.html
and KEYS file that i am talking about. Actual distribution
artifacts are not stored in SVN.

Anyway, as suggested, look at other projects and the
mirror docs.

> >I am not sure what the requirements are to notify that
> >the release is by a project in incubation. There are some
> >docs at site. See the mirror headers
> >at w.a.o/dist/incubator/ top-level. There is some disclaimer
> >text there that you might like to use too.
> Yes, it's something that we've been wondering...  Our release scheme  
> will look interesting with a version numbering such as "JSPWiki-3.0.0- 
> alpha-1-incubating". ;-)
> >The KEYS file is something else that you can get ready ahead
> >of release time. Even if it only contains the signature of
> >the Release Manager. Better with more, of course.
> It should be up to date already.

I meant adding the KEYS file to that distribution area
as explained by the various "How to ASF mirror" docs.

> >Anyway, i hope that helps a little to ease your next phase.
> Thanks; that should help!
> One interesting question is what we should do to "" domain.  
> I'm quite willing to give it to ASF, no worries, just to ease any  
> potential trademark issues; but whether ASF wants it is another matter.

That desrves its own discussion thread.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message