Skip to content
New issue

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

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

Already on GitHub? # to your account

Request to move pronto-slim_lint runner repository into prontolabs #419

Open
ibrahima opened this issue Feb 16, 2022 · 2 comments
Open

Request to move pronto-slim_lint runner repository into prontolabs #419

ibrahima opened this issue Feb 16, 2022 · 2 comments

Comments

@ibrahima
Copy link
Contributor

Hi! I wrote the pronto-slim_lint runner a while ago for my own purposes, but I haven't been able to keep it up to date with newer Pronto releases. Others have asked to get access to maintain it, so I was wondering if it would be possible to move the repository into the prontolabs organization, so that others would be able to help maintain it. I expect that ultimately some of the folks asking to contribute to that runner might need to be the ones actually contributing and keeping it up to date, but I figured it would be better for it to be in a community organization where multiple people have access rather than a handful of people disconnected from the broader community. Thank you!

Concretely, I am guessing that we'd need to move the repository and also grant rubygems publish access to some others (or maybe a CI system?).

@ibrahima ibrahima changed the title Request to move pronto-slim_lint runner Request to move pronto-slim_lint runner repository into prontolabs Feb 16, 2022
@ashkulz
Copy link
Member

ashkulz commented Dec 31, 2022

@ibrahima I'm not sure who has permissions to do this, probably @mmozuras?

@ibrahima
Copy link
Contributor Author

ibrahima commented Jan 5, 2023

Ah yeah, I would guess so. Happy to help facilitate in any way that I can!

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

No branches or pull requests

2 participants