Planned repository transfer: nuwave/lighthouse → spawnia/lighthouse #2767
spawnia
announced in
Announcements
Replies: 1 comment 1 reply
-
|
Hi Spawnia, You have been an exemplary maintainer and I fully support this proposal. It's been years that I actively used Lighthouse but seeing your efforts passing by via email notifications has created a lot of respect for you, keeping this project up to date and up to specs. Personally I'd create a new org or become a full member of the existing one instead of moving to a personal space, but that's entirely up to you. Keep it up! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm planning to transfer this repository to my personal GitHub account, @spawnia, and wanted to announce it here before anything happens.
Christopher Moore (@chrissm79), who created Lighthouse in 2016, is fully on board - he offered this transfer back in December 2022 and has confirmed it again now. I'm grateful for everything he built and for his continued support.
I've been the sole active maintainer since early 2020. Having the repo live under a company org I'm not part of creates unnecessary confusion - for users doing due diligence, for potential sponsors, and for me when I need to do anything administrative. Moving it to my personal account makes the reality visible.
What changes:
What stays:
nuwave/lighthouse- no changes to yourcomposer.jsonNuwave\Lighthouse\A package and namespace rename is a separate, much larger migration - not part of this move.
There's no hard deadline on this. I'm posting in advance to give everyone a chance to raise concerns before anything moves.
If you have questions or thoughts, share them here.
Beta Was this translation helpful? Give feedback.
All reactions