Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    bnewbold
    @bnewbold
    Welcome!
    Allan Nordhøy
    @kingu_gitlab
    I was going to contribute, but then I saw the notice that said I had to come here and discuss matters.
    bnewbold
    @bnewbold
    Hi @kingu_gitlab ! I am just setting up weblate now for the first time
    Allan Nordhøy
    @kingu_gitlab

    hosted.weblate.org/contributor-agreement/internetarchive/fatcat-scholar/?next=/projects/internetarchive/fatcat-scholar/ says

    By contributing (thanks!), you agree to license your translation strings under the same terms as the rest of the source code for this project. In particular, strings may be edited by other contributors and re-used in other projects (under the same terms). Your contributions will be attributed on the Weblate website; if you would like further attribution in the repository, please contact the maintainers. Contributions and communications on the Weblate platform are additionally covered under the Fatcat Code of Conduct; see https://guide.fatcat.wiki/code_of_conduct.html

    The first part of that is replicated in 3.2 and 6.4 of https://hosted.weblate.org/legal/terms/
    bnewbold
    @bnewbold
    I think that the project is now unlocked and contributions should be possible. It also looks like attribution is included in commit messages, eg: https://github.com/internetarchive/fatcat-scholar/pull/2/commits
    Allan Nordhøy
    @kingu_gitlab
    As for the latter, I don't understand how you expect anyone, much less contributors to read your superflous rules, when you don't read the conditions of services you use.
    bnewbold
    @bnewbold
    I'm not sure what the contributor experience looked like, because I signed up with weblate as a host account. Did it show the Weblate terms of use at the same time as the project-specific terms? Did it specifically mention AGPL 3+ at that time?
    Allan Nordhøy
    @kingu_gitlab
    Request to start nb_NO translation sent
    bnewbold
    @bnewbold
    there is a good chance we will make a round of updates to text on the site in the next week or so ("source strings"). I can add an additional notification about that to the site
    Allan Nordhøy
    @kingu_gitlab
    @bnewbold The Hosted Weblate terms are required to use an account on Weblate. I am not sure hosts actually skip this
    That would be an oversight if so
    bnewbold
    @bnewbold
    regarding nb_NO: so far I have only used generic/non-local language codes ("de", "zh"). I am probably not using the correct technical term for this distinction. would you be alright if I add "nb" instead of "nb_NO"?
    Allan Nordhøy
    @kingu_gitlab
    @bnewbold I'd obviously love to help, but I am not comitting to a code of conduct
    nb_NO is the correct locale the web-browser will look for.
    bnewbold
    @bnewbold
    and related to starting a new language: there is an option to pre-seed translations from previous weblate projects and/or machine translation services (google translate?). do you think it would be helpful to try that first and then edit the results? or is it better to start from scratch and use the auto-translation suggestions one at a time?
    Allan Nordhøy
    @kingu_gitlab
    Don't auto-translate anything. You can share between own components, and allow the translations to populate other components
    other projects
    Is editing turned off?
    Gitter was just sold btw
    bnewbold
    @bnewbold
    yes, I saw, sold again. I hope matrix integration will not be disruptive
    i'm not sure what you mean by editing; editing on weblate? the components were "Locked" while I resolved a git issue, but seems to be unlocked now
    Allan Nordhøy
    @kingu_gitlab
    For what it is worth, Hosted is a community of 24 622 registered accounts, and makes due with https://github.com/WeblateOrg/weblate/blob/master/CONTACT.md and it changed from much of what is in https://guide.fatcat.wiki/code_of_conduct.html
    You probably have automatic locking on. "Lock on errors"
    bnewbold
    @bnewbold
    regarding the code of conduct: as mentioned at the top, if there are specific objectionable terms we are open to feedback and change. as an individual and organization we think some ground rules for discourse are important, and we think these are a good starting point. if you disagree I respect that
    I have "Lock on Error" enabled, but I believe there is no error now, and the "This project/component is locked due to an error" is gone for me now
    Allan Nordhøy
    @kingu_gitlab
    Without which we wouldn't have ground rules for discourse? The insult belongs with however created it, not me.
    Could you add https://hosted.weblate.org/user/kingu/ as a reviewer?
    It might be that only admins can see the settings
    bnewbold
    @bnewbold
    that interface only seems to control administrative access. I think I do not have the reviewer feature enabled
    Allan Nordhøy
    @kingu_gitlab
    Didn't think of that. But I can help out based on descriptions of what the error is should any problems arise.
    It is a funny world when "the fatcat code of conduct" breaks licensing terms. The irony is, if you will systematic. :)
    bnewbold
    @bnewbold
    the error should be resolved now, it had to do with moving the upstream repository to a new location
    and adding "push" permissions. you have caught me just as I am configuring things for the first time, so some bumps in the road!