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

Reply via email to