Dropping the vxquery mailing list... To me VXQuery looks like an example of a project being let down by the Incubator PMC. This labeling issue was just an honest attempt at trying to be helpful not some underhanded attempt to try to circumvent the ASF release policy, if they were getting adequate mentoring it would have just been an opportunity to teach them more about the ASF release policies and processes. Similarly with the no releases in 4 years - they've attempted to release twice and both times it stalled getting the votes, what they need are mentors who can show them whats necessary to push releases and voting through the Incubator. In the past they've asked us for more mentors to help and got nothing. Its a small project but its managed to survive for 4 years here and still have some active committers and as they've just shown now when a problem is reported they fixed it in less than a day, so all credit to them for keeping on trying.
On Thu, Sep 5, 2013 at 9:46 AM, ant elder <ant.el...@gmail.com> wrote: > Thanks for doing that so promptly Till. > > ...ant > > > On Thu, Sep 5, 2013 at 4:00 AM, Till Westmann <t...@westmann.org> wrote: > >> Just for the record: The website is updated (from the branch that will >> hopefully be released soon). >> >> Till >> >> On Sep 4, 2013, at 12:11 AM, Marvin Humphrey <mar...@rectangular.com> >> wrote: >> >> > On Tue, Sep 3, 2013 at 11:42 PM, David Crossley <cross...@apache.org> >> wrote: >> >> ant elder wrote: >> >>> Hi Marvin, I had a look, that README being pointed to is just build >> >>> instructions on how to build the svn trunk isn't it, so not to some >> >>> released artifacts. Thats allowed isn't it, i'm pretty sure other >> projects >> >>> and podlings have done something similar anyway. Is it that the >> website >> >>> describes it as user installation instructions rather than developer >> build >> >>> instructions thats the issue? >> >>> >> >>> ...ant >> >> >> >> I reckon so. To clearly refer developers to developer resources >> >> is fine, but users no. They need to be referred to user instructions. >> > >> > In VXQuery's case, there's nothing to refer users to because in four >> years, >> > VXQuery has never made an incubating release. >> > >> > If developer instructions for accessing version control are added to the >> > website in accordance with ASF guidelines, of course that's fine -- so >> > long as all "user installation" instructions are removed. >> > >> > Here's more background from the legal-discuss list regarding the >> current policy, >> > this time from a different Board member, Doug Cutting: >> > >> > http://markmail.org/message/pelvob23vrzuzws5 >> > >> > Each PMC should attempt to ensure that every commit is in accord with >> > Apache's intellectual property policies. Releases are a double-check >> of >> > this. We hope that source code repositories are not legally >> considered >> > publications, but we don't know that courts will in fact always >> treat them >> > that way, so it's best to guard against that too. Note that the extra >> > scrutiny around releases both serves to double-check (belt and >> suspenders) >> > as well as to provide evidence that we do not consider the source >> code >> > repository as a publication. But again, we cannot depend on others to >> > agree with that, and must guard against other interpretations as >> best we >> > can. >> > >> > If VXQuery finds it uncomfortable not to have anything they can show >> users, >> > they can solve that by making a release. >> > >> > Marvin Humphrey >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
