Alexandre Franke commented on a discussion: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/677#note_1265163 Ok. That’s one criteria. There are many other ones, which arguably are more important, though. It’s still using GTK **2**. Not even 3, which would already be cause for concern. That makes it unfit for GNOME. As I said above, *no release since 2016*. Code changes are not the only thing that need to be shipped. Your repository history is full of translation commits, and all that work is wasted if it doesn’t get released (not to mention the miscellaneous other fixes). All of that can change though. What do you want to do? If you plan on making regular releases and modernise the code base, maybe it can stay in GNOME. If you just make releases but won’t touch the code, World or your own namespace seem more appropriate. Being moved to the Archive does not mean deleting the project by the way. It’s preserving the repository as it currently is. If your software is still working today, there is no reason it should stop once it moves to the Archive. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/677#note_1265163 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
