I'll clean this up tonight (https://github.com/flarum-lang) and then we'll just open up membership to any translator and their packs. Can I add you too rob006 ? Anyone else interested?

Understand this organization will be a community project then, I will join in but only to guarantee the survival of those language packs.

      luceos If it will become a place where everyone can contribute, I'm in. I need to focus on my education and I am worried that I will not be able to devote enough time to the package This is why I archived my package.

          tolgaaaltas I enabled sync again, new phrases should be exported in a moment. Please don't archive these repos without warning - read-only repos crashes process for exporting translations to all language packs.

          @luceos I'm fine with that, but I don't want to manage team of translators. I could help with technical stuff, but every language pack needs native speaker that could review translations and tag new releases, and I don't want to search for such people and decide who should be language pack maintainer.

              rob006 I'm fine with that, but I don't want to manage team of translators. I could help with technical stuff, but every language pack needs native speaker that could review translations and tag new releases, and I don't want to search for such people and decide who should be language pack maintainer.

              I agree.

              I think you should do the weblate thing like you always did. But having access to repositories or even creating them if need be helps.

              I also don't want to hunt for activity. So maybe we just need someone or multiple people to pull this cart a bit, meaning;

              • onboarding new translators
              • keeping track of the translations so that unmanaged ones can be marked incompatible.
              • merging prs and working on issues
              • etc

              I'll make sure to promote this team on the docs and site so that we can be sure it lifts off fast.

                • transfer repo to flarum-lang
                • update git link on packagist.org
                • update weblate
                • update link in discussion on discuss

                Anything I'm missing?

                luceos From "Weblate perspective": just move repo to org and ping me when it is done. I'll update URLs in script then (although old URL should work anyway, so moving repo should be safe).

                Since there is no new maintainer I just leave @tolgaaaltas his permissions on Weblate for now.

                  BTW: You can't rename package on Packagist, so I'm not sure if it would not be easier to just create new package when new maintainer for language pack will show up. For now we could just leave @tolgaaaltas's repos and packages as is. With Weblate you don't necessarily need a maintainer to update language pack - everyone can contribute directly to language pack repo through Weblate and install updated version from dev-master. Maintainer is needed in long run to ensure translations quality before make stable release, but package could live without maintainer for some time.

                    rob006 yeah that's correct. My thought was to just keep the package name as is for now, but we might as well also rename the package to flarum-lang/italian or something once they move into the organisation.

                        luceos That is what I would want to avoid, because flarum-lang/italian becomes official-like package, and probably someone that does not know anything about Italian would need to decide who will be maintainer of this language pack. Personally I would prefer if community would just use forks and own namespaces to handle abandoned packages. What we really need is just list of actively maintained language packs, so it will be easier for users to decide which package use for their language, and don't stuck with abandoned package.

                            rob006 I think we shouldn't be afraid about official-like. We just need to clarify the reasoning behind this. And yes we will always have people who don't read or understand, the same happens with FoF at times.

                            The drawback of using forks is that they get scattered everywhere. I would prefer just keeping all those repositories under one organisation, cooperatively managed by the translators - or people they and we choose to run point on that. It would greatly help new translators and help with keeping old ones maintained.

                                luceos The drawback of using forks is that they get scattered everywhere.

                                I don't think that this would be a problem if in documentation there would be a list of actively maintained language packs, so people would know which package install and don't need to randomly pick from 5 language packs for their langue (of which 4 are abandoned).

                                    I plan to be involved with Flarum in the long term for both personal and non-personal projects, so I will actively update the Spanish package, however I also want to help in this if that is the way to go.

                                    I really agree with @luceos that having a single organization would be useful, I mean if I now go to my composer and want to install X language it's not easy, in fact I always have to look at the package names, instead with this it would be as easy as putting flarum-lang/ and the language name and check at that moment if that language exists or install it.

                                    I think at some point the languages had to be official in some way, precisely for maintenance and clarity (the user has to know what to install), there are communities that are completely in another language so its maintenance is as important as the core extensions.

                                    I don't know how @Kakifrucht feels about this, he has developed the German language package so far.

                                    Otherwise I would be willing to manage the German translation.

                                    rob006 But this does not prevent the problem, I mean at any moment the package could stop being active and we would be back to the same thing, create another package with another name and have 5 abandoned, or have I misunderstood?

                                        Darkle create another package with another name and have 5 abandoned

                                        Yeah, and then we just update link to actively maintained package in docs. A lot less work and responsibility than maintaining semi-official org for translations.

                                          Ideally translating would be a multi people effort. German form example was well maintained but haven’t even a Beta 16 version yet. If there are multiple people we could ensure it gets done (quicker). So hosting the packs officially be a Flaum owned repository I would like. Having a tool like weblate could make it much more feasible that more people work on a Language pack.