Re: Some instructions are misleading on mentor page

2020-10-10 Thread Justin Mclean
Hi,

I agree this could be clearer:

"Mentors MUST be on the IPMC. This should be checked prior to beginning 
incubation. Any prospective Mentors who are not yet on the IPMC should ask to 
be added (by election). Email the application to priv...@incubator.apache.org.”

How about this:

"Mentors MUST be on the IPMC. This should be checked before beginning 
incubation. Any prospective Mentors who are not yet on the IPMC, and who are 
ASF members, should ask to be added. Email the application to 
priv...@incubator.apache.org. Any prospective Mentors who are not ASF members 
or IPMC members could be voted onto the IPMC by the IPMC in the normal way, but 
unless the proposed Mentors have been active in the Incubator, this is unlikely 
to happen."

Thanks,
Justin





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



Some instructions are misleading on mentor page

2020-10-10 Thread Dave Fisher
Hi -

The instructions here [1] are misleading.

(a) An ASF Member who is not on the IPMC may be added via “application”

(b) Non IPMC members who are not ASF Members do NOT file applications. Instead 
they are nominated, secretly, by an IPMC member and voted on by the IPMC. There 
is no assurance that an application is accepted.

I’m looking for others to suggest the PR.

Regards,
Dave

[1] https://incubator.apache.org/guides/mentor.html#mentors_must_be_on_the_ipmc
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: New distribution guidelines

2020-10-10 Thread Tianqi Chen
Sharing some thoughts about this particular question. The intention of the
guideline is to clearly distinguish the Apache from non-apache ones (to
protect apache's brand).

There are a few ways to achieve so:

- W0: Change the release note to indicate the tag is non-apache
- W1: Change the release title in the github page to include non-apache or
pre-incubation
- W2: Delete the original tag and create a new tag with pre-incubation
suffix (note that many projects might use tag that follows semantic
versioning).

W0 + W1 already serves the purpose pretty clearly, as users who browse the
github release tag page would clearly get the information.

As Ovilia mentioned,  W2 might create some disruptions for users who wish
to use pre-incubation releases and makes the transition less smooth for the
podling.
It might also create confusion about the software's history as some
project might expect the tag might need to follow semantic versioning.
Not requiring W2 might be desirable to make the new podling transition
smooth while also protecting apache's brand(via W0 and W1)

TQ

On Sat, Oct 10, 2020 at 2:23 AM Ovilia  wrote:

> Hi Justin,
>
> I have a question about the guidelines.
>
> > Any releases that exist before coming into incubation need to be clearly
> described on the release page and tagged as such on
>
> Does this mean that we need to change the tag/release name from something
> like "4.1.0" to be "4.1.0-non-apache-release" or "4.1.0-before-incubation",
> or just add a notification in the description that this is a release before
> incubation?
> P.S. I'm not sure if changing the version name would break some CDN relying
> on GitHub version.
>
> Thanks
>
> *Ovilia*
>
>
> On Mon, Oct 5, 2020 at 12:26 PM Justin Mclean 
> wrote:
>
> > Hi PPMC members,
> >
> > New distribution guidelines, that we have been working on for some time,
> > have been published here:
> > https://incubator.apache.org/guides/distribution.html
> >
> > They contain information on distributing releases on 3rd party platforms
> > including Maven, GitHub*, *Docker, NPM and PiPy.
> >
> > Note that these are good suggestions on best practice and incubating
> > projects can do things differently, but if you follow these guidelines,
> you
> > are less likely to have issues on graduation.
> >
> > If you have any questions or feedback on these guidelines, please do so
> on
> > the Incubator general list.
> >
> > Thanks,
> > Justin
> >
>


[jira] [Commented] (INCUBATOR-255) Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html

2020-10-10 Thread Henry Saputra (Jira)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211596#comment-17211596
 ] 

Henry Saputra commented on INCUBATOR-255:
-

[~johndament] - please close this Jira ticket. I am able to help Datalab with 
this issue. Thanks

> Rename "DLab" to "DataLab" on https://incubator.apache.org/clutch/datalab.html
> --
>
> Key: INCUBATOR-255
> URL: https://issues.apache.org/jira/browse/INCUBATOR-255
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Vira Vitanska
>Priority: Major
> Attachments: Rename.png
>
>
> This ticket follows 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-145 and 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-184.
> So now our podling is in process of replacing old name by new one from DLab 
> to DataLab.
> 
> There is a page [https://incubator.apache.org/clutch/datalab.html]
> Could you replace dlab by datalab in:
>  # project website link name
>  # issue tracker link name
>  # wiki link name?
> I guess that I've reported to an appropriate side (Project Incubator) if I am 
> wrong please correct me.
> Thanks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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