Noted below. I will leave others to add anything I’ve missed.
On Mon, Jul 13, 2020 at 8:15 PM Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > Currently PiPy is not an ASF supported platform and you may have some > difficulty in complying with ASF policies. Are you aware of the trademark, > branding and other ASF policies that apply here? Also are you are aware > that the ASF release process involve the PPMC and IPMC voting on release > which can take some time? > Re: PyPI - I am aware of the ongoing discussion on the distribution guideline, plus from working with other communities in the past, so I believe I can provide some guidance there. > At the ASF discussions need to take place on the mailing list, you seem to > have a number of other communication channels, is it going to be an issue > moving some of that discussion off them and onto the mailing list? As for community, google group maps well to dev@a.o, Gitter can move to ASF slack (with dev@ summary), GitHub issue can continue - I would think they would work well. > It is rare for projects to exit incubation in under a year. Will there be > any issues if this process takes longer? > > It may be better off to start with a single dev list and add the user list > later as needed. Is there a reason you want both at the start? And this project can start with dev@ > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >