Hello Jordan, yes I was used to no putting something to have the link for both text and address.
I have just fixed it now.

jordanjay29 I don't understand, it's the same way as any other extension. Should be put once in the documentation not everywhere for every extension. Imagine, tomorrow it changes? We would ALL have to change our topics?

      Quenti These guidelines exist for the convenience of our community members here, so they can have all the information they need on an extension in order to install and use it. The installation method will not change tomorrow.

      If you add the instructions to your first post, I can approve it.

          Quenti by installation instructions, we meant the composer command(s).

          I'm not 100% sure what the translation of your text is but that doesn't sound like how we install extensions.

          I just checked and your extensions appear to not be published to Packagist. See https://flarum.org/docs/extend/distribution.html for how we distribute Flarum extensions.

            Quenti you have to host your package on a Composer-compatible package directory, otherwise other users won't be able to install it. We recommend Packagist which is the official platform for all open-source packages for Composer. You can see every other extension published here has been added to Packagist by their authors. You can find the instructions to add your package to Packagist in the link I posed above.

                I moved this to the dev tag for the moment.

                What are we talking about? I'm giving a translation that I made on my spare time.
                This translation is a unique file.
                First of all we ask contributor to make an extension, which doesn't give visibility to all the languages available.
                Two your contributors have to host their extensions. Typically I wanted to have a look at the Catalan extension but I couldn't have the Github repository has been removed.
                And now you ask me to install and sign up to other websites only to make available my translation.
                Don't you think you go too far and have to treat your community differently?

                  Hi Quenti,

                  Hate to chime in, but there is no need for personal attacks. I have removed your last sentence as it doesn't get anyone anywhere.

                  The guidelines are there for all extension creators to follow; we aren't singling you out at all. Without us having these guidelines, extensions would not work properly and things would be a big mess. We appreciate all extensions that are made for Flarum as we all know it takes time and work to get a finished product. In its current state, we cannot approve this extension until all extension guidelines have been met.

                  I do hope you understand. Thanks mate.

                    Quenti I'm sorry that this is causing you some frustration. We're not trying to make this process difficult, simply consistent for our community.

                    In Flarum, our extensions are installed and removed through Composer. This is an essential part, because it simplifies what would otherwise be a complex mess of file editing and folder shuffling. We don't want our users to go through that process, and Composer makes it easy.

                    You can read in our documentation how this procedure works. We don't require the use of sites like Github and Packagist (and as clarkwinkelmann mentioned these are not the only options, simply the most commonly used) to burden our extension developers, most of them find it a convenient method for hosting and distribution. Using them also relieves Flarum of the need to provide hosting and serving files to our users, which would greatly increase our costs, and only duplicate what's already available in Github and Packagist.

                    Since you do have a Github account for your repository, using Packagist should be a simple matter since you can log in with your Github account. The instructions I gave, as well as instructions on Packagist's website, should walk you through the process of getting it working. When the release is tagged and picked up by Packagist, which usually happens within an hour, your extension should be able to be installed via composer require Mejans/lang-occitan.

                    Please know that we greatly appreciate the efforts of our extension developers, and especially those who translate the languages. We also appreciate the variety of different users who come to Flarum, and we aim to provide them with a consistent method for obtaining extensions. This is how we treat our community, with consistency, so I hope you understand the reasons for the requests here.

                        9 days later

                        Quenti Thanks, I split out our discussion and moved the first post to Extensions tag. I appreciate your efforts and I can't wait to see people using your language pack!