Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It may be time to rename this repo #113

Open
michaelgwelch opened this issue Oct 1, 2020 · 2 comments
Open

It may be time to rename this repo #113

michaelgwelch opened this issue Oct 1, 2020 · 2 comments

Comments

@michaelgwelch
Copy link
Member

Initially we had planned that this library would only support the basics like our old MMDA did. But it's growing was past that. As such it might make more sense to rename the repo following the release naming: metasys-rest-api-client or some such thing.

Maybe less disruptive to any consumers would be to update the README that this is being archived and add a link to the new repo. Then archive this repo. Then push the source to the new repo and continue development there.

Just helpful I think if the deliverables match the repo name and if the repo name matches what we are actually delivering. Thoughts @Federico-Artioli ?

@Federico-Artioli
Copy link
Collaborator

Hi Michael, I see your point and to be fair I'm a bit concern to rename now the repo (and everything related as Nuget package etc..). Especially if there is the risk to create some 'confusion' to the current users (maybe they cannot see benefit on rename it). In any case if you think it is really needed I would propose to postpone it a bit due to I'm going to make a new release (v4.2) by mid October. Would it be maybe better to do it with the new v5.0 for Metasys 12?

@michaelgwelch
Copy link
Member Author

Yes, I didn't meant to suggest we need to do it right now. Waiting until 12.0 is probably best. And when we rename it we should probably move it to the Johnson Controls org.

We can leave this one behind in an archived state, with the README updated to point to new location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants