Ok, no problem with it, it just was a question about how to handle this situation.
Thanks! 2018-05-31 13:36 GMT+02:00 Carlos Soriano <csori...@gnome.org>: > Yeah, I agree the translators tools should learn how to deal with > different GitLab groups... this will be quite useful soon when Engagement > group has also projects that translators at GNOME wants to help translating > with. > > Let me know if you have any questions about that. > > On Thu, 31 May 2018 at 13:31, Piotr Drąg <piotrd...@gmail.com> wrote: > >> 2018-05-31 13:21 GMT+02:00 Carlos Soriano <csori...@gnome.org>: >> > Hey Daniel, >> > >> > library-web and others are infrastructure projects, so they are handled >> > differently on purpose. >> > >> > Fractal is not a GNOME app, so it's not in GNOME/. Ideally they would >> be... >> > but I don't think they started the process for that yet, if any. >> > >> > Moving them to the non-GNOME section in dammed-lies looks like the >> proper >> > solution. >> > >> >> Hi, >> >> Infrastructure projects are still GNOME projects, so that leaves us >> with only Fractal as a non-GNOME project. I don’t think creating a new >> release set for just one module is worth it, and I do hope Fractal >> will move to GNOME/ soon. Additionally, it being in a different group >> on GitLab shouldn’t change anything in the standard translator >> workflow. I’m sorry if you needed to make any changes in your >> scripting and automation — had I known, I would definitely notify you >> earlier. >> >> Best regards, >> >> -- >> Piotr Drąg >> https://piotrdrag.fedorapeople.org >> >
_______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
