Hi,
How is providing guidance on ASF policy to podlings unfair if it makes their
life easier? Again these guidelines add nothing that a TLP shouldn’t already be
doing. They may do it in a slightly different way, and that’s OK and also
allowed by these guidelines.
Put it this way without that g
> So what would you suggest as an alternative?
As I've been consistently suggesting in the discussion thread and in this
thread, I hope that ASF could move forward together on the distribution
guidelines, and the consensus should bind all projects, TLP and podlings alike.
Taking the shortcut fo
Hi,
> Again, in my opinion, the act of interpretation of existing rules in a new
> context is making new rules. Thus, all the rules in the guidelines are new
> rules.
If you see it that way , then every single project (both projects in the
incubator and TLPs) makes new rules when they interpre
> > Personally, I believe that interpretation is still making new rules.
> Please point to one of these new rules.
Again, in my opinion, the act of interpretation of existing rules in a new
context is making new rules. Thus, all the rules in the guidelines are new
rules.
> > As a podling PPMC
Hi,
> This description suggests that the nature of this guideline is the
> interpretation of the
> existing Apache policies in the context of distribution on third-party
> platform.
That is correct.
> Personally, I believe that interpretation is still making new rules.
Please point to one of
Hi Justin,
While I appreciate your efforts in putting together the guidelines, your reply
seems to indicate
that this guideline is not making new rules, which is apparently false.
Specifically, you wrote:
> Nothing as far as I can see is added only clarified and put into context for
> differen
[
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156491#comment-17156491
]
Justin Mclean commented on INCUBATOR-253:
-
It's really going to depend on the
[
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156483#comment-17156483
]
Sheng Zha commented on INCUBATOR-253:
-
[~jmclean] you added some notes to it and I
Hello all,
This is a call for a vote to release Apache NuttX (Incubating) version
9.1.0.
The Apache NuttX community has voted on and approved a proposal to
release
Apache NuttX (Incubating) version 9.1.0.
We now kindly request the Incubator PMC members review and vote on this
incubator release.
Hi,
> A reference to http://www.apache.org/dev/#releases ought to be first from any
> incubator policy or guidance page. Problems with the dev page should be
> addressed. If the Foundation wide policy and guidance is weak then that
> should be fixed so that an Incubating podlings can use the pr
Hi Justin,
To me the Foundation Dev Guidance comes first and it is currently buried within
the Incubator policy and guidance.
A reference to http://www.apache.org/dev/#releases ought to be first from any
incubator policy or guidance page. Problems with the dev page should be
addressed. If the
Hi -
You note over 30 contributors to GeoSpark, but there are only 8 initial
committers. Has the move to the Apache Incubator been thoroughly discussed in
the existing community? Is anyone being excluded?
Best Regards,
Dave
Sent from my iPhone
> On Jul 12, 2020, at 12:36 PM, Felix Cheung wro
Any questions or concerns? If not, I can kick off the VOTE thread shortly.
On Thu, Jul 9, 2020 at 6:12 AM Felix Cheung wrote:
> Hi,
>
> We would like to propose Apache Sedona, currently known in its community
> as GeoSpark, as a new project under the Apache Incubator.
>
> Sedona is a big geosp
13 matches
Mail list logo
