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

add ROS Orphaned Package Maintainers to maintainer tag #69

Conversation

k-okada
Copy link
Contributor

@k-okada k-okada commented May 14, 2017

@rctoris I'm willing to release this repository in to kinetic/lunar on behalf of unmaintaned package maintaner groups, before releasing this repoistory we need to add new version and tags, if you do not have time to do that, could you give write permission to @k-okada ?

c.f https://discourse.ros.org/t/releasing-repositories-form-other-people/1797

@k-okada
Copy link
Contributor Author

k-okada commented May 14, 2017

@rctoris
Copy link
Contributor

rctoris commented May 24, 2017

@k-okada I think the best thing to do at this point is to fork to project and GBP as either an orphaned un-maintained package or with a new maintainer if someone is willing. I am no longer associated with Bosch and cannot grant write access to their repositories at this point and unfortunately do not know who to contact in order to get that. I could also put a message on the repo stating where the project has moved to.

@dirk-thomas
Copy link

@chaoflow @flixr @iluetkeb @KaijenHsiao @NikolausDemmel @proan @sosentos Can any of the other owner of this org unit comment if they are willing to move the repository to a ros org unit instead since it seems to be abandoned?

@Karsten1987
Copy link

cc @MatthiasRoland @maxriz

@NikolausDemmel
Copy link

Yes, IMHO we should move it.

@k-okada
Copy link
Contributor Author

k-okada commented Jun 7, 2017

@dirk-thomas so, can we move the repo?

@dirk-thomas
Copy link

I don't know anybody who has access for this repo. So you will have to fork it.

@KaijenHsiao
Copy link
Contributor

@lorenzoriano

@NikolausDemmel
Copy link

I can move it. What do I have to do?

@NikolausDemmel
Copy link

I.e. where exactly should this be moved and the release repo?

@k-okada
Copy link
Contributor Author

k-okada commented Jun 7, 2017

thanks, may be https://github.com/ros-drivers ? and usb_cam-release to https://github.com/ros-gbp ?

@NikolausDemmel
Copy link

Alright. Waiting on confirmation from @dirk-thomas

@dirk-thomas
Copy link

may be https://github.com/ros-drivers ? and usb_cam-release to https://github.com/ros-gbp ?

Sounds good.

@lorenzoriano
Copy link

Yup @NikolausDemmel please transfer it to the new organization. It's quite easy once you have the permission. Please let me know if you need assistance

@NikolausDemmel
Copy link

I tried to do the transfer of this repo, but I got an error saying "You don’t have the permission to create repositories on ros-drivers". Not sure if that triggered a notification for ros-drivers Owners to confirm the transfer.

Also, I noticed that the release repo is in another organization, which I cannot access. @rctoris, you are the only one listed under "people" for https://github.com/bosch-ros-pkg-release. Could you maybe give ownership to that organization to the owners of bosch-ros-pkg?

@rctoris
Copy link
Contributor

rctoris commented Jun 9, 2017

I also tried to move the repo but I don't have access to ros-gbp

@k-okada
Copy link
Contributor Author

k-okada commented Jun 13, 2017

@rctoris @NikolausDemmel thank you for your effort, may be you have to add @dirk-thomas to your organization and ask them to move the repo, or ask @dirk-thomas to include @rctoris @NikolausDemmel to ros-drivers and ros-gbp

@NikolausDemmel
Copy link

Jup, it seems according to https://help.github.com/articles/transferring-a-repository-owned-by-your-organization/ that I would need "repository creation rights" on the receiving organization. The option that the receiver gets an email to confirm seems only available for transferring to another user account, not organization.

By now I have rights also to the release org, so I could do the transfer of both repos.

@dirk-thomas
Copy link

dirk-thomas commented Jun 13, 2017

@NikolausDemmel I added you temporarily to both org units. Please let me know once you have moved the repos.

@NikolausDemmel
Copy link

@dirk-thomas I transfered the release repo to ros-gbp, but you gave me access to ros, not ros-drivers. Should I transfer to ros, else please give me access to ros-drivers.

P.S.: When asked which teams to give access for the release repo, I only added Owners, so you might need to sort out permissions as needed.

@dirk-thomas
Copy link

dirk-thomas commented Jun 13, 2017

@NikolausDemmel Sorry, fixed. I will add @k-okada as a collaborator which allows him to add more people.

@NikolausDemmel
Copy link

It is done. As teams I again added only "Core Team".

@dirk-thomas
Copy link

@NikolausDemmel Thanks for transferring the repos.

@k-okada You are now a collaborator on both repos with the admin role. So you can add other people to the repo as well. Please take it from here,

@k-okada k-okada merged commit 92a82d8 into ros-drivers:develop Jun 14, 2017
@k-okada k-okada deleted the add_ros_orphaned_packages_maintaneres_to_package_xml branch June 14, 2017 06:55
@k-okada
Copy link
Contributor Author

k-okada commented Jun 14, 2017

@dirk-thomas @NikolausDemmel Thank you all, finally released in to kinetic!!!! -> ros/rosdistro#15225

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.

7 participants