Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

[RFC] Apache MXNet branding issues #21036

Closed
josephevans opened this issue May 20, 2022 · 4 comments
Closed

[RFC] Apache MXNet branding issues #21036

josephevans opened this issue May 20, 2022 · 4 comments
Labels
RFC Post requesting for comments

Comments

@josephevans
Copy link
Contributor

In our discussion thread in general@incubator about graduating Apache MXNet to a top level project, the Apache IPMC noticed some branding issues that should be addressed.

List of current violations identified:

Some issues (including branding) were brought up previously in a Apache JIRA ticket: https://issues.apache.org/jira/browse/INCUBATOR-253 but most were resolved last year.

Going forward, it would be nice to have a sort of monitor for identifying these violations sooner. Does anyone have bandwidth to create a monitor that uses a search engine to find trademark violations?

@josephevans josephevans added the RFC Post requesting for comments label May 20, 2022
@josephevans
Copy link
Contributor Author

The issues from AWS-provided DLAMIs should be resolved now.

@josephevans
Copy link
Contributor Author

I've notified trademarks@ of the 3 outstanding branding issues listed above. We do not have PPMC associated with these entities.

@josephevans
Copy link
Contributor Author

Created a PR to address GluonCV site branding issues: dmlc/gluon-cv#1747

@josephevans
Copy link
Contributor Author

The GluonCV website has been updated.

All items, except the Anaconda packages, have been resolved. We are currently working with trademarks@ to resolve this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
RFC Post requesting for comments
Projects
None yet
Development

No branches or pull requests

1 participant