-
Notifications
You must be signed in to change notification settings - Fork 491
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
Move repository to lightning organization #925
Comments
Concept ACK |
Ack, sure, pending @Roasbeef giving perms... |
First round of invites just went out! Who should I invite from the Electrum project, @SomberNight? |
Just made the blips repo and added @ryanthegentry as a maintainer there since he's been shepherding the process through so far. Admin perms should be inherited there as well.
I think this one should stay (to preserve it as is, since it belongs to Joseph after all), it's pretty out dated in any case compared to the current state of the network. |
Great, got the invite! The Github tools should let you transfer the lightning-rfc repository to the lightning org now, and once it's migrated we can rename it to "bolts" from withing the lightning org 🚀 |
I guess you could invite me. Although historically we probably haven't contributed enough to the spec to warrant merge permissions. |
And so shall it be done: https://github.com/lightning/lightning-rfc! Redirect looks to be working as well: https://github.com/lightningnetwork/lightning-rfc/pulls |
As discussed in https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-October/003276.html, it seems like we have agreement to move the specifications to the https://github.com/lightning repository.
To summarize, the reasons we want to move are:
@Roasbeef could you give all of us admin rights to the
lightning
org?We should then:
lightning-rfc
repository using github's migration toolblips
repository (let's get this one rolling)We should also remove links to https://lightning.network since it seems we also don't have access to that website and it's very outdated.
The text was updated successfully, but these errors were encountered: