-
Notifications
You must be signed in to change notification settings - Fork 24
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
Upstream Module Adoption #84
Comments
Fwiw, as the second (much smaller) contributor to Cozy, I support this. I would also support the adoption of role sync and other general utilities that have yet to be splitter from the main bot code, although I understand the maintenance burden might be too large. |
Sure, you'd be getting development done likely faster and better than me |
Alright, sounds good - I'll update this issue as things get moved over. Thanks for the support! |
I don't have a ton of time today, but I've moved some modules over:
I'd like to document these properly as well, but that's an ongoing project right now. I'll try to list all the contributors to these modules at that point as well. As @Akarys42 suggested, I'll likely be creating additional modules based on other parts of Cozy that would be useful in general, such as the filtering system. I'll keep y'all up to date. |
Hello! It me!
When I was still working on Cozy, some of the modules I created were designed to be used by external projects. As I'm no longer part of Quilt, I'd like to adopt them as mainline, first-party Kord Extensions modules:
As I contributed the vast majority of the code present in these modules, I believe there should be no issue with this from a licensing standpoint. However, I wanted to make sure that was alright with the people who are now running this project.
Of course, you'll be able to use the adopted modules in Cozy as has always been the case - that's the point!
The text was updated successfully, but these errors were encountered: