Hi,
Dave I'm a bit surprised at your -1 given this guidelines have been discussed
before on several lists (including this one) and you’ve not had any objections
that I can recall. What is your main concern here?
Thanks,
Justin
HI,
> For clarity, you mean that the dependencies included in a binary fit valid
> classes of licenses with correct notices.
No, while that might also be the case, what I was saying is that a release must
be voted on by the IPMC.
>>> Would there be cases where the convenience binaries must be
Hi -
Big observation. I’m uncomfortable with the Incubator making Apache Policy
beyond adding DISCLAIMERs. Other Board and Operations VPs have been delegated
policy making. Yes, that is hard and unclear. Perhaps this proposal could
inform those discussions.
More inline.
> On Jul 5, 2020, at
Hi,
> Does the convenience binaries include nightlys? Or CI test builds?
In general they do not not, as wording states “approved releases” i.e. that
means that the IPMC must vote on the release artefact. Also note that only
approved code can be in a convenance binary, which again means it only
Hi Justin,
When examining these clauses in the context of distribution in our project
(MXNet), I had a few questions to clarify. In the release guideline, there are
the following statements:
> Convenience binaries need to follow licensing policy and not include any
> category X licensed
Hi,
> If there is consensus why vote?
To confirm consensus, it’s just a formality, but with a policy change, it may
be useful to point to a vote result at a later date.
Also a vote may get more IPMC member looking at them and some provide some
additional useful feedback.
Thanks,
Justin
If there is consensus why vote?
Sent from my iPhone
> On Jul 5, 2020, at 6:04 PM, Justin Mclean wrote:
>
> Hi,
>
> Given there no more discussion here I guess I’ll assume it’s good and I’ll
> put it up for a VOTE. These can be modified as needed later.
>
> Thanks,
> Justin
>
Hi,
Given there no more discussion here I guess I’ll assume it’s good and I’ll put
it up for a VOTE. These can be modified as needed later.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For
Hi,
> - Maybe add a comment about who/how to get the ability to publish under the
> Docker Hub account.
I would ask Infra as I don’t know the exact details, I’m not aware of any
documentation on it.
> - And, encouragement to follow the same signing and checksumming practice as
> for
Hi,
> I independently noticed and added [1] so that's covered.
Thanks for adding that.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
I independently noticed and added [1] so that's covered.
On Mon, Jun 29, 2020 at 12:06 PM Joey Frazee
wrote:
>
> Justin this is great and I find myself searching mailing lists and INFRA and
> LEGAL JIRAs for past guidance like this.
>
> A few nit-y suggestions:
>
> - I think it’d be helpful to
Justin this is great and I find myself searching mailing lists and INFRA and
LEGAL JIRAs for past guidance like this.
A few nit-y suggestions:
- I think it’d be helpful to link out to the Nexus info [1].
- Maybe add a comment about who/how to get the ability to publish under the
Docker Hub
Hi,
> The name on Pipy could be https://pypi.org/project/apache- to
> keep consistent with other platforms.
>
> The name on NPM has the same issue.
As long as it clear it’s an Apache project (for releases made by the PPMC) then
any similar variations is fine.
Thanks,
Justin
Hi,
> The name on Pipy could be https://pypi.org/project/apache- to
keep consistent with other platforms.
Sorry I mean, to keep consistent with current released projects [1].
[1] https://pypi.org/search/?q=apache
Best,
---
Xiangdong Huang
School of Software,
Hi Justin,
The name on Pipy could be https://pypi.org/project/apache- to
keep consistent with other platforms.
The name on NPM has the same issue.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Justin Mclean 于2020年6月28日周日
Hi,
> I have a question regarding the nature of the document and the vote. I see
> that the title for this document is "Distribution Guidelines". Do you
> intend to have this document considered as a distribution policy?
Yes it’s policy but podlings can ask for exceptions or come up with their
Hi Justin,
Thanks for starting the discussion and for putting together the draft.
Having a guideline on distributions should definitely be helpful. This is
very relevant to the distribution issues we are addressing in MXNet so I
will take a close look and try to contribute.
I have a question
Hi,
I think these have been draft long enough and it's time to make them official.
[1]
Anyone have any comments or suggested changes, additions or modifications
before I call a vote to do so?
Thanks,
Justin
1.https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines
18 matches
Mail list logo
