k0dep / originer Goto Github PK

Hi @k0dep,

Favo from OpenUPM - a platform collects open-source UPM packages. First of all, thanks for creating this awesome open-source package. I am writing to you because OpenUPM is preparing to comply with Unity's Terms of Services (TOS) Updates. Your package is available on our platform, and I need your help to make some changes.

According to the Unity Package Manager Naming Convention, the package name should use reverse domain name notation, at least 3 sections joined by a dot: tld.org-name.package-name. For example com.littlebigfun.addressable-importer.

• tld is the top-level domain, like com, org and so on. If you're not sure about what to use, please use com.
• org-name is your organization name. With tld together it makes sure the organization name is globally unique to its registered owner. You should avoid using a tld and org-name combination that may be confusing to users, like com.unity or com.github.
• package-name is your package name.

Your package name is originer. I recommend you to update it to comply with the naming convention by,

• change the package name in package.json.
• bump the version field of package.json.
• create a Git tag.

Please reply to me if you've made the change, I will update the OpenUPM side to make it live.

If you do not respond to the issue, It will be closed by the end of Jan 2021, and your package will be removed from our platform. Please notice that Unity Package Guiding Principles & Guidelines do not apply to you when you host Packages on GitHub for Unity users to download and put the Packages in their projects, as long as the hosted Package does not, directly or indirectly, leverage the Unity Editor as a marketing or distribution platform. Thus, you don't have to change anything if you don't intend to publish the package on a scoped registry (like OpenUPM).

Sorry for the inconvenience, feel free to discuss with me if you have any questions.

BR
Favo

Hi @k0dep,

As #4 get fixed, please consider bump the version and create github release 3.0.1

The tag is already 3.0.0, but package.json remains 2.0.0.

https://github.com/k0dep/Originer/tree/3.0.0

What if two packages with the same name exist? Shouldn't you at least be requiring the github username in the package name? "foo.bar" for github.com/foo/bar ?