Michael Catanzaro commented: One more thing: if you just wanted to move gspell from gitlab.gnome.org to github.com, of course that would be sad, but that seems reasonable because you developed gspell yourself and it doesn't have any other maintainers. We don't allow core elements (like gedit) to be hosted externally, but gspell is an SDK dep and those are allowed to use whatever hosting they please. The problem here is the additional element of sabotage: trying to actively prevent other contributors from working on gspell is too much. We just cannot have GNOME software depending on a repo that says "contributions are no longer accepted." And gspell is more ingrained than amtk and tepl were, so our dependencies on it cannot easily be reverted. That said, I see [you changed your contribution policy here](https://github.com/gedit-org/gspell/commit/14c9363425f81dd2a894a5c757cba8f6a2debd60#diff-ea8677bf3f8815f111ec75a506f5af2faf35be890e1b1467bea73ed6fed6fd0e), so maybe allowing gspell to move would be OK after all. That said, it's _really_ confusing to have it hosted in the same GitHub organized that hosts non-renamed forks of gedit and gtksourceview. A compromise solution might look like: * Rename your gedit and gtksourceview forks * We archive gspell here and point it to your new repo * You agree not to close gspell to further contributions again (at least for the foreseeable future) -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/700#note_1279312 You're receiving this email because of your account on gitlab.gnome.org.
_______________________________________________ gnome-infrastructure mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
