incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Cheung <felixche...@apache.org>
Subject Re: [MENTORS] IPMC Policy change work in progress disclaimer
Date Fri, 02 Aug 2019 06:18:31 GMT
+1


On Thu, Aug 1, 2019 at 11:17 PM Paul King <paulk@asert.com.au> wrote:

> Kudos for progressing this idea. I really like it. It should allow
> improvements from the perspective of both podlings and reviewers.
>
> Cheers, Paul.
>
> On Fri, Aug 2, 2019 at 12:25 PM Justin Mclean <justin@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added
> > to the IPMC policy page. [1]
> >
> > Podlings can now select which disclaimer they want to use. If they want
> to
> > use the standard disclaimer then their releases must comply with all ASF
> > policy. If they want the incubator to be more lenient in voting on their
> > release or know that the release has some issues not in line with ASF
> > policy then the work in progress disclaimer can be used.
> >
> > Unless the release is simple and straightforward, I would recommend that
> a
> > podling uses the work in progress disclaimer for the first couple of
> > releases.
> >
> > For what is allowed under the work in progress disclaimer please see this
> > legal JIRA [2]. This allows a lot more in a release but not everything.
> > Certain things are required like having a LICENSE, NOTICE and
> > DISCLAIMER-WIP, and while it would be OK to include compiled code you
> still
> > need to comply with any licensing for that code.
> >
> > By the time a podling graduates it's expected that they are making
> > releases with the standard disclaimer.
> >
> > Here is the text of the DISCLAIMER-WIP where the Incubator is the
> sponsor:
> > ____
> > Apache  #Podling-Name# is an effort
> > undergoing incubation at The Apache Software Foundation (ASF),
> > sponsored by the Apache Incubator. Incubation is required of all
> > newly accepted projects until a further review indicates that the
> > infrastructure, communications, and decision making process have
> > stabilized in a manner consistent with other successful ASF projects.
> > While incubation status is not necessarily a reflection of the
> > completeness or stability of the code, it does indicate that the
> > project has yet to be fully endorsed by the ASF.
> >
> > Some of the incubating project's releases may not be fully compliant
> > with ASF policy. For example, releases may have incomplete or
> > un-reviewed 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):
> > #List of known issues go here#
> >
> > 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. For the current status of this project through the
> > Apache
> > Incubator visit:
> > http://incubator.apache.org/project/#Podling-Name#.html
> > ____
> >
> > Just fill in #Podling-Name# with your podling name and list the known
> > issues in the correct place.
> >
> > Thanks,
> > Justin
> >
> > 1. https://incubator.apache.org/policy/incubation.html#disclaimers
> > 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message