crowdsourcing

Problem:
The translator sometimes does not make correct spaces around tags. For example:

<p>Click on the links<a href="...">here</a>or<a href="...">here</a>.</p>

Solution suggestion:
Create new quality check. Logic like:

• if tag: a, strong, b, i, ...
• and if following chars are before or after the tag: \p{L}
• then show a failed check

Subject of the issue

Right now its not possible to share individual announcements. If we can provide a link with unique time stamp, the URL can be shared.

Expected behaviour

The time stamp should be a unique URL

The Accessibility Foundation has made an accessibility of the Open Food Facts web site. There is a number of issues that they pointed out and that we should fix.

Report OpenFoodFact 15-12-2020.pdf

Who would be interested in fixing some of them?

In #147 we modified the reply sending logic so that it first sets hyperlinks to a temp value and rely on promises to fill in hyperlinks after loading finishes.

However, the procedure may fail and cause forever polling scenario like this:
https://cofacts.g0v.tw/reply/H4TBinABWiTSPYAZPHxn

Needs further discussion on

• How many replies are affected
• How this can be mitigated

There should be one at least in C#, people shouldn't need to always roll their own solutions for this.

Ref: https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-Mth-vd5RPWqdLOfRJHHcg

• Color the contribution graph according to the user's max contribution count
• Crop old contribution like Github on mobile
• Use Math.floor to round-up the contribution to color

Estamos usando a versão 6.6.5 da biblioteca, mas ela tem uma comunidade super ativa e já está na versão 7.19!
Essa tarefa é pra simplesmente mudar pra usar a versão mais recente, verificando se não quebrou o layout. Opcionalmente podemos estudar as novas features que foram implementadas nesse meio tempo pra ver se alguma é interessante pra nós :)

Github da Sweetalert2:
https://github.com/swee

Until now, amti's testing has been entirely manual. There have been three reasons for this
decision:

1. amti began as a tool I built for myself. Originally, I wanted to demo the idea of
   reproducible, version controlled crowdsourcing pipelines and to make my own
   crowdsourcing research reproducible. I open sourced amti so that others could run my
   pipelines, to share the idea of reproducible