Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Allan Nordhøy
    @kingu_gitlab
    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!
    Allan Nordhøy
    @kingu_gitlab
    Yeah, it doesn't like that. I found that out some weeks ago
    bnewbold
    @bnewbold
    overall I have been impressed with weblate. there are some corner cases like this but the integrations seem to work ok overall
    Allan Nordhøy
    @kingu_gitlab
    To be fair the self-service is brand new
    bnewbold
    @bnewbold
    I'm not sure what the future of our organizational use will be. We have not done much translation/internationalization of services so far. and usually prefer to self-host, so may end up moving to a self-hosted instance
    Allan Nordhøy
    @kingu_gitlab
    We had Pootle back in the day, but nowadays all the effort is going into Weblate
    bnewbold
    @bnewbold
    I also, to be honest, do not have as much experience with things like RTL (right to left) translation, so that will probably be a challenge if/when we get to that
    Allan Nordhøy
    @kingu_gitlab
    @bnewbold Well you will grow some respect and disdain for me in turn for a better quality stringbase, if you play my game.
    I am not good at that, and it seems like something you would think someone had worked out the kinks in by now, but no
    So there is delete and repost, but no edit. Hmmm
    bnewbold
    @bnewbold
    Just to clarify, what are you looking at editing? a translation?
    Allan Nordhøy
    @kingu_gitlab
    I imagine it is the usual fare of poor source strings foisted on unsuspecting translators
    Allan Nordhøy
    @kingu_gitlab
    So I am torn between accepting a CLA, and not being able to prevent even worse translations propagating to other compoents.
    Allan Nordhøy
    @kingu_gitlab
    Are you noticing civil discourse somehow manifested without the aide of that text-document? Yet you retained all the powers you had and have anyhow. It does however think itself to encompass even "chat rooms", so I am out. Best of luck with or without me.
    bnewbold
    @bnewbold
    testing if gitter will pull "cards" for links: https://fatcat.wiki/release/xsrqlgn4dngujiktfb4a5hpsmq
    I have added translation files for es, ru, ar. These are some languages with relatively large amounts of (open) content in fatcat
    An earlier version of the search interface would "boost" results in the currently active language, and would also swap the title and "original_title" fields if there was a match between the interface language and the content language
    Harsh Sharma
    @hs2361
    @bnewbold Could you guide me as to what is to be done about internetarchive/fatcat#62 ? You've mentioned a few sources, so what exactly is to be done using those sources? I'm new here, so any guidance from you would be appreciated
    bnewbold
    @bnewbold
    Hi @hs2361 !
    I don't have a "recipe" of next steps for the retraction import next steps. If you are hoping to get oriented, I think the guide (guide.fatcat.wiki) is a good place to start, as well as the API documentation (api.fatcat.wiki). There is a cookbook in the guide with examples of how to create an editgroup, make edits to an existing "release" (or create a new release), and then submit the editgroup for review. The easiest way to do this today is working with python
    the "release schema" section of the guide talks about the data model and schema, and should have a description of the "withdrawn" and "retracted" metadata
    the design notes for the withdrawn/retraction fields are here, from last year: https://github.com/internetarchive/fatcat/blob/master/proposals/20190509_v03_schema_tweaks.md#withdrawn-fields
    it probably helps to consider what edits should be made, and what metadata is necessary to make them, and then work backwards to find the correct metadata publicly available
    is this helpful? it would be easier if I had a similar example project to point you to, but we don't have one yet
    bnewbold
    @bnewbold
    @hs2361 this project might be helpful, they seem to have consolidated PubMed and Crossref retractions:
    https://github.com/fathomlabs/open-retractions
    http://openretractions.com/
    Harsh Sharma
    @hs2361
    Thank you, I will take a look.