> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>
> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher <dave2w...@comcast.net> wrote:
>>
>> Hi -
>>
>>> On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz
>>> <bdelacre...@codeconsult.ch> wrote:
>>>
>>> Hi,
>>>
>>> On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean <jus...@classsoftware.com>
>>> wrote:
>>>> ...I put up suggested text changes for an incubator disclaimer here [1]...
>>>
>>> Basically just adding this, right?
>>>
>>>> Some of the project releases may not follow ASF policy or have
>>>> incomplete or unknown licensing conditions....
>>>
>>> It works for me but I'd say "incubating project" to be clearer.
>>
>> How is this?
>>
>> “Some of the incubating project’s releases may not be fully compliant with
>> ASF policy. For example, releases may have incomplete or unreviewed
>> licensing conditions. Known issues will be described on the project’s status
>> page."
>
> I would suggest we have a policy where known issues are actually
> listed in the DISCLAIMER itself. Along the lines of:
>
> "Some of the incubating project’s releases may not be fully compliant
> with ASF policy. For example, releases may have incomplete or
> unreviewed licensing conditions. What follows is a list of known
> issues the project is currently aware of (note that this list, by
> definition, is likely to be incomplete):”
-1.
This only works for issues known before a release is cut. It does NOT WORK if
the issue is discovered during the release vote. Why? Because we are trying to
allow the release to go through without redoing it and this would require
reworking the release.
I would rather do it outside of the release. Policing the actual DISCLAIMER is
not easily feasible and decreases the burden.
If this is the decision then it leads to a choice that is worse than the status
quo.
>
> I would also suggest we add an explicit note warning our downstream consumers:
>
> "If you are planning to incorporate this work into your
> product/project, please be aware that you will need to conduct a
> thorough licensing review to determine the overall implications of
> including this work”
This is a reasonable approach for the usual DISCLAIMER but …
Regards,
Dave
>
>>>> ...It also been suggested than any known issues be listed in the
>>>> disclaimer...
>>>
>>> I don't think that works as modifying the disclaimer to list issues
>>> will change the digests of the archive that's being voted on - and
>>> those shouldn't change IMO.
>>>
>>> As Paul suggests in a different thread I'd go for easy to find tickets
>>> to describe those changes. The disclaimer might point to
>>> http://incubator.apache.org/release-issues which in turn points to
>>> those tickets, keyed by release name and version number. Or something
>>> like that - a permalink that points to the details.
>>
>> I would suggest that in a revamping of podling status pages that the podling
>> can list current issues with each release.
>>
>> The link to that page is easy: http://incubator.apache.org/projects/<podling>
>>
>> BTW - I’ve changed my thoughts on a Whimsical version of the status data and
>> am planning to put these in as AsciiDoc pages / YML into the Incubator’s Git.
>>
>> Regards,
>> Dave
>>
>>>
>>> -Bertrand
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>
> ---------------------------------------------------------------------
> 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
