Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
Hi, > Again, we are NOT releasing release candidates. No but companies that your PPMC members are employed by are. Those PPMC members are in a good position to make sure their employers are aware of and follow ASF policies where needed. It's part of a (P)PMC duties to make sure branding, releases and trademarks are correctly followed. [1] At the very least these PPMC members should be bringing it to the attention of the PPMC for discussion on what to do. Ideally the companies involved should be going to the PPMC to ask for feedback or review on this sort of content and releases. Having un-voted on release candidates been made available to the general public with the projects name on it is problematic in a number of ways. > - We will include a branding and trademark usage guideline page on mxnet > website. That would be help. You can also just refer people to existing ASF policies. > - We will conduct a review of trademark usage as part of our board > reporting process. As there are now several outstanding trademarks issue that would be appreciated. The original issue the board brought to the incubator attention still has not been fully addressed. You next report is not due for a few months, however you are welcome to make an out of band report. Either way I'll need some information to include in the next incubator report due in a week or so. Thanks, Justin 1. https://www.apache.org/foundation/marks/responsibility.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] New builds server and who should access
On Tue, Jul 28, 2020 at 1:50 PM Josh Fischer wrote: > 2.) Why just IPMC members? Seems it could be helpful/empowering to allow > committers access to this folder to help when they want to/can. I can > also see that opening this folder up to all incubator committers increases > the possibility of error. At the very least, allow PPMC members access to the folder for their project? Nathan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] New builds server and who should access
1.) I agree 2.) Why just IPMC members? Seems it could be helpful/empowering to allow committers access to this folder to help when they want to/can. I can also see that opening this folder up to all incubator committers increases the possibility of error. - Josh On Mon, Jul 27, 2020 at 5:22 PM Justin Mclean wrote: > Hi, > > > Do we want to have podlings request their own separate folders to ease > transitions and help with graduation and retirement? My answer is yes. > > +1 to that as its less work for project, infra and the incubator. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Distribution guidelines for platforms
Hi, +1, binding. I've been quietly following similar discussion in some different threads, because I've had the same issues with mentoring incubators, including help some pmc members to release in some TLPs. According to my understanding, whether it is incubation project or top-level project, there are some unclear places in the distribution, especially after more and more package management tools appear, PyPI, NuGet, Helm, DockerHub and so on. I highly respect the foundation's concern and effort on intellectual property and brand legal. From the perspective of the development of the project, we may need to have more flexible mechanisms to ensure that our products are easy to be distributed. thus improving the speed of iteration and release flexibility of the products. In that point, clarification in incubators is a great thing, and projects can learn to adapt to the rules as soon as they are hatched. But I'm also concerned about whether the rules should be applied to the top-level projects(Maybe this discussion goes beyond IPMC), and I would be totally supportive of such continuity and compliance between Podlings and TLPs. Best Regards, Von Gosling > On Jul 21, 2020, at 10:42 AM, Justin Mclean wrote: > > Hi, > >> This has been in discussion in many threads for more than a year [1] so a >> few more days is not a big deal. > > Anyone have anything to add at this point? > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
