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

Point users to new upstream repository: openstack4j/openstack4j #1296

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

olivergondza
Copy link
Collaborator

We are continuing the project development in openstack4j/openstack4j for the lack of traction here[1]. I am filing this to help users to easily locate the active upstream.

@auhlig, @gondor, please have a look. I would appreciate if you would integrate this.

[1] https://groups.google.com/forum/#!topic/openstack4j/pY2eee760QQ

@auhlig
Copy link
Member

auhlig commented Feb 17, 2020

Does that make sense to you @gondor?

@gondor
Copy link
Member

gondor commented Mar 12, 2020

@olivergondza let's keep this in the original repo since it has the larger user base. Let me know what permissions and access you want so we can keep It there and give you the flexibility to be the main maintainer

@gondor
Copy link
Member

gondor commented Mar 12, 2020

@auhlig ^^ for visibility since we were emailing each other about this

@olivergondza
Copy link
Collaborator Author

olivergondza commented Mar 12, 2020

@gondor, thanks for getting back to us and offering the possibility to continue the development here!

I would like to keep the vision of building a community around the project and distributing the permission across several people to eliminate the bus factor and to have a healthy developer ecosystem. Also, if we move the development back here, I find it important to merge back openstack4j/openstack4j and openstack4j/openstack4j.github.io including the releases produced there (so the version numbers will not clash). EDIT: reverting back groupId, website links, etc.

Speaking of permissions needed, these are the ones I can think of:

  • Becoming an owner of the github repos openstack4j and openstack4j.com (probably undesirable for the whole group) so we can manage the code, teams, integrations, etc.
  • Administrative permissions to the google discussion group.
  • Permissions to release bits to maven central.
  • We also need a long term commitment to maintain and fund the domain registration. I would be happy to take that, as well.

With all those announcements I published lately about separating the project to openstack4j github group, it might actually be smoother to just stick to that one. I believe with explicit control of the webpage and the source repo, we can redirect the users quite effectively - so I am offering the possibility of just finishing the move there while keeping you guys as maintainers in case you are interested. Though, I would understand if you feel strongly for ContainX group.

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

Successfully merging this pull request may close these issues.

3 participants