Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Formalities #2

Open
2 of 9 tasks
Keraito opened this issue Feb 9, 2019 · 3 comments
Open
2 of 9 tasks

Formalities #2

Keraito opened this issue Feb 9, 2019 · 3 comments

Comments

@Keraito
Copy link
Contributor

Keraito commented Feb 9, 2019

So now that we have our repo (🎉!), let's decide on some formal rules before we get into translating áll the stuff. Deciding on and documenting them should hopefully make both the processes now as well as in the future go way smoother 😄.

Todos ✔️

  • Cleanup some of the repo (I saw some crowdin stuff in the README).
  • Do you guys prefer to communicate through Github or do we want to set up a Discord/Slack/Spectrum for easier communication?

Translation Rules 📝

  • As described here, we should make a glossary and/or style guide consisting of terms which we either do or do not want to translate and if so, how they are translated to make it consistent. We should probably do this in a way that is easy to extend/change it and discuss about those proposals. Personally, a MD file of some sort where we discuss in PRs is fine for me. For the initial batch, we could make an exception for this to make it go smoother. Glossary & style guidelines #5
  • Is it more important to keep the translation as similar to the original as possible, or is it better to express it naturally in Dutch in cases where it's hard to keep it similar? (I prefer the latter).

Review Process 🔍

We should decide on some rules on:

  • How will we review proposals/translations? What will we pay attention to and what not?
  • When will we merge it?
  • Since we're with only 3 people atm, how many approvals is considered mergeable?

Repository Organisation 🗑

  • Personally, I like to have labels like Ready for Review or Do not merge in order to keep everything organised, but definitely would also like to hear what you guys want.
  • Do we want to keep all the process in Dutch Translation Progress #1 or also make a Project board?

Usefull resources 📘

There's probably more stuff, but let's stick to this for now as it's already a lot 😺

(And use all the emojis!)
@jochenboesmans @rickbeerendonk
@reactjs/reactjs-org-dutch-translation

@rickbeerendonk
Copy link
Contributor

I'm in 🇵🇦 and rural 🇨🇴 for the next 2 days. I will study all procedures and I'll start picking up translations by Tuesday.

@jochenboesmans
Copy link
Contributor

Do you guys prefer to communicate through Github or do we want to set up a Discord/Slack/Spectrum for easier communication?

A more direct/informal medium of communication would definitely be nice. Personally I would prefer Slack.

we should make a glossary and/or style guide

As soon as we've put together the initial glossary & style guidelines, I'd put it up in a place that's easy for everyone to see.

Is it more important to keep the translation as similar to the original as possible, or is it better to express it naturally in Dutch in cases where it's hard to keep it similar? (I prefer the latter).

I think this highly depends on whether the translation still feels natural or not.

@rickbeerendonk
Copy link
Contributor

Do you guys prefer to communicate through Github or do we want to set up a Discord/Slack/Spectrum for easier communication?

A more direct/informal medium of communication would definitely be nice. Personally I would prefer Slack.

Slack is best for me too.

Is it more important to keep the translation as similar to the original as possible, or is it better to express it naturally in Dutch in cases where it's hard to keep it similar? (I prefer the latter).

I think this highly depends on whether the translation still feels natural or not.

I have the same preference. Professional React users in Holland might use the English docs anyway. Dutch might be preferred by amateurs and kids in school. So it should feel as natural as possible to them.

react-translations-bot pushed a commit that referenced this issue Oct 10, 2022
* Added documentation for React.createFactory

* Update beta/src/content/apis/react/createFactory.md

Co-authored-by: Strek <[email protected]>

* minor editorial updates (#2)

* Update createFactory.md

* Update createFactory.md

* edits

Co-authored-by: Strek <[email protected]>
Co-authored-by: Holly Sweeney <[email protected]>
Co-authored-by: Dan Abramov <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants