Re: [MENTORS] New DISCLAIMER-WIP approved by board

2019-08-23 Thread Justin Mclean
Hi,

I’ve also updated [1], feedback as allways welcome. 

Thanks,
Justin

1. https://incubator.apache.org/guides/releasemanagement.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [MENTORS] New DISCLAIMER-WIP approved by board

2019-08-23 Thread John D. Ament
This is a major incubator policy change.  It's worth a note to podlings@ at
a minimum.

On Fri, Aug 23, 2019, 00:29 Justin Mclean  wrote:

> Hi,
>
> Does anyone think we should mail this out to all incubating PMC? (e.g
> private@ or dev@). I'm not really sure that I want to spam 50 odd
> projects like that, but it woful be useful in getting this knowledge out
> there.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [MENTORS] New DISCLAIMER-WIP approved by board

2019-08-22 Thread Justin Mclean
Hi,

Does anyone think we should mail this out to all incubating PMC? (e.g private@ 
or dev@). I'm not really sure that I want to spam 50 odd projects like that, 
but it woful be useful in getting this knowledge out there.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [MENTORS] New DISCLAIMER-WIP approved by board

2019-08-22 Thread Justin Mclean
Hi,

> It's odd that this is addressed to mentors, rather than the podlings
> themselves.

I’m expecting that mentor will pass this information on to podlings that would 
need to use it.

>  However, is the new disclaimer-wip meant to be shown within
> the release or on the podlings website or both?

It’s intended for releases but I don’t see why it couldn’t be both.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [MENTORS] New DISCLAIMER-WIP approved by board

2019-08-22 Thread John D. Ament
It's odd that this is addressed to mentors, rather than the podlings
themselves.  However, is the new disclaimer-wip meant to be shown within
the release or on the podlings website or both?

On Thu, Aug 22, 2019 at 9:05 PM Justin Mclean 
wrote:

> Hi,
>
> At the recent board meeting, the board has informally approved the use of
> the DISCLAIMER-WIP.
>
> If you use the DISCLAIMER-WIP disclaimer [1] you can make an ASF release
> that doesn't need to follow ASF release policy. You will need to list the
> reason why in this disclaimer. By the time you graduate, you are expected
> to follow all ASF policies.
>
> Note that the release must be legal and follow the licensing conditions of
> any bundled 3rd party software. That means if you accidentally put a binary
> in the release and don't include the relevant licenses, the release is
> probably going to get a -1 vote.
>
> For a full list of what you need to follow to make releases this way, see
> [2].
>
> If it's your first release and you included 3rd party code, I would
> strongly recommend you use this new disclaimer.
>
> If you use the old DISCLAIMER, then the release needs to follow ASF
> release policy.
>
> Thanks,
> Justin
>
> 1. http://incubator.apache.org/policy/incubation.html#disclaimers
> 2. https://issues.apache.org/jira/browse/LEGAL-469
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


[MENTORS] New DISCLAIMER-WIP approved by board

2019-08-22 Thread Justin Mclean
Hi,

At the recent board meeting, the board has informally approved the use of the 
DISCLAIMER-WIP.

If you use the DISCLAIMER-WIP disclaimer [1] you can make an ASF release that 
doesn't need to follow ASF release policy. You will need to list the reason why 
in this disclaimer. By the time you graduate, you are expected to follow all 
ASF policies.

Note that the release must be legal and follow the licensing conditions of any 
bundled 3rd party software. That means if you accidentally put a binary in the 
release and don't include the relevant licenses, the release is probably going 
to get a -1 vote.

For a full list of what you need to follow to make releases this way, see [2].

If it's your first release and you included 3rd party code, I would strongly 
recommend you use this new disclaimer.

If you use the old DISCLAIMER, then the release needs to follow ASF release 
policy.

Thanks,
Justin

1. http://incubator.apache.org/policy/incubation.html#disclaimers
2. https://issues.apache.org/jira/browse/LEGAL-469
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org