Hi Justin, > It’s not seperate as you release candidates being distributed to users. I still want to know why release candidates are being released in this way, in particular by companies where there are MXnet PPMC members. What steps will the PPMC will take to stop this from happening in the future?
Again, we are NOT releasing release candidates. DJL is not MXNet, and it does not represent MXNet. Even though it's from my day job employer and I'm a PPMC member, whoever took the action doesn't represent me or the PPMC. I also want to know why it was released like that. Here are the steps I'm taking on behalf of the PPMC on this: - As DJL was developed by a separate team as a separate project, I first reached out to them through an internal channel and clarified the requirement for using the name mxnet in their releases. Either they or I will provide an update on the resolution. - We will include a branding and trademark usage guideline page on mxnet website. - We will conduct a review of trademark usage as part of our board reporting process. Feel free to advise appropriate additional steps. > Here’s another branding/trademark issue [8] and anther [9] and another [10]. If I search for "MXNet" here [11] I get 30 hits and some issues. I believe your project has PPMC members from the companies listed here? Yes, there are PPMC members that are employed by this company, including me. I'm starting a thread with the PPMC on the project private list for resolving the issues on the marketplace website. Bear in mind that any entity can list items on such a site, and they do not represent either the PPMC or the company that runs it, just like google search results don't represent the google employees. > I’m on OSX and don’t have gcc set up correctly, clang fails to compile as it encounters an unknown option. So it’s probably just my setup, however I’m not even sure of OSX is a supported platform. OSX compilation config and steps can be found in https://github.com/apache/incubator-mxnet/blob/v1.x/config/darwin.cmake#L18-L34. We are improving our installation guide to make it easier to discover. Regards, Sheng On Sun, Jul 26, 2020 at 5:19 PM Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > It seems that most of the concerns are branding/trademark/legal issues > from those third-party projects which relies on MXNet and the AWS > marketplace (or MXNet's downstream projects), which could be tracked > separately and improved continually to 100% meet the requirement of > incubating Apache project, so probably not affect this source release and > can be addressed later. > > It’s not seperate as you release candidates being distributed to users. I > still want to know why release candidates are being released in this way, > in particular by companies where there are MXnet PPMC members. What steps > will the PPMC will take to stop this from happening in the future? > > > For mshadow, I'm wondering if completing the IP clearance process is the > only mandatory requirement for this source code release, then we might need > to hold on the current release process until it's finished > > It will need to be completed before this can be released. > > Thanks, > Justin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
