Closed MoritzHayden closed 2 years ago
I'd be open to it. In order to do that, though, it seems like I need permission to create repositories in the Ramsey Solutions org.
Alternately, you could fork this repository; and we could put a big link to your new repo in the README and archive this one.
I think it would be easier if you transferred it to me or @MoritzHayden and then one of us transferred it into our GitHub organization since we already have permission to do that. Thoughts?
Whoever I transfer to needs to delete your fork first. I just tried, and it says both of you already have a scut
repository.
Whoops, sorry about that. I deleted my fork so you should be able to try agin.
Thank you so much, David!
Sure thing: glad you're finding this library useful!
Hey @davidtheclark!
@jmmcduffie and I are both team members at Ramsey Solutions (Website) (GitHub), where we maintain several open source projects. We enjoy working with Scut, as do hundreds of thousands of developers around the world, and we want to make sure it receives the support it needs and deserves. Moving forward, would you be open to transferring Scut into @RamseyInHouse where it can continue to be supported into the future?