Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[OLD] Legacy Polish Translation Progress #1

Closed
82 of 94 tasks
tesseralis opened this issue Feb 10, 2019 · 80 comments
Closed
82 of 94 tasks

[OLD] Legacy Polish Translation Progress #1

tesseralis opened this issue Feb 10, 2019 · 80 comments

Comments

@tesseralis
Copy link
Member

tesseralis commented Feb 10, 2019 •
edited by jakubdrozdek
Loading

Slack

https://react-translations.slack.com - join to see the glossary and chat with other team members!
Channels:
#pl - general discussion
#pl-glossary - the glossary (use the search feature to find words)

Maintainer List

Retired maintainers

For New Translators

To translate a page:

  1. Check that no one else has claimed your page in the checklist and comments below.
  2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
  3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.

Please be prompt with your translations! If you find find that you can't commit any more, let the maintainers know so they can assign the page to someone else.

For Maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

When PRs are merged, make sure to mark that page as completed!
Note: We require two maintainers to approve a PR for it to be merged.

Note: Since most of the PRs are created from forks, we can't add our own commits to them. Let's make a rule that if a PR's author doesn't respond within 7 days, we take the translated page over. Another person can create their own PR with the translated content, apply any suggestions added to the old PR, and submit. To be fair, let's not remove entirely the original author from the list below - just add the new translator after comma.
If the author leaves a message that they won't be available for a few days - that's fine, we'll wait.

Core Pages

To do before releasing as an "official" translation. Please translate these pages first.

Basics

API Reference

Navigation

These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

Next Steps

These are the next most important translations, ordered by importance:

Installation

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

Testing

Warnings

These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

Advanced Guides

FAQ

Contributing

Priority: Low

  • How to Contribute
  • Codebase Overview
  • Implementation Notes
  • Design Principles

Components

Components in src/components that have some text in them.

Additional Translations

These are not the primary translation targets.
@tesseralis tesseralis mentioned this issue Feb 10, 2019
Merged
@jakubdrozdek
Copy link
Member

jakubdrozdek commented Feb 10, 2019 •
edited
Loading

Do we (the maintainers) need to put the name of the page we want to translate in the comments here? Or do we just add our username next to the page without asking? ;-) Just curious.

@tesseralis
Copy link
Member Author

tesseralis commented Feb 10, 2019 •
edited
Loading

Up to you! But it might be a nice courtesy to other contributors and to the other maintainers.

@jakubdrozdek
Copy link
Member

Okay then, I'll start off with the style guide.

@jakubdrozdek jakubdrozdek pinned this issue Feb 10, 2019
@TeoTN
Copy link
Contributor

TeoTN commented Feb 10, 2019 •
edited
Loading

Grand! I'll go for Basics first:

  • Hello World
  • Introducing JSX
  • Rendering Elements
  • Components and Props
    (If adjustments to align w/style guide are required, I'll follow)

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Feb 10, 2019 •
edited
Loading

@TeoTN:
@tesseralis wrote above: "Please take only one page at a time". I'm actually okay with picking multiple pages at once, since there's only three of us right now and there's lots of work ahead. But I want to know for sure. What's the verdict? :-)

@TeoTN
Copy link
Contributor

TeoTN commented Feb 10, 2019

I took these since they're relatively short and basic - I can adjust ;)

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Feb 10, 2019 •
edited
Loading

Where do you prefer to keep the glossary? Should we create an issue for it, put into the style guide (like the Spanish team did) or create a separate file?

@TeoTN
Copy link
Contributor

TeoTN commented Feb 10, 2019

I'd vote for putting it into a style guide

@jakubdrozdek
Copy link
Member

I'll take these next:

  • State and Lifecycle
  • Handling Events

@tesseralis
Copy link
Member Author

It's up to you -- it's your project and you can change that rule if you want if you feel it's too restrictive for a small group. Even though it might be a few of you now, more people might join in later.

@tesseralis
Copy link
Member Author

Though I would encourage you to submit pull requests for pages as soon as you're done with them instead of, say, doing five pages and submitting one big pull request for all of them. One thing another language maintainer pointed out is that you could make one consistent style error that isn't caught until PR, which means you'll have to go back and change all your work!

@tesseralis tesseralis mentioned this issue Feb 11, 2019
Closed
@cvqprs
Copy link
Member

cvqprs commented Feb 11, 2019

Guys @jakubdrozdek, @bartlomiejzuber, and @TeoTN I would like to help u with this translation. Where can I start? Do you have any slack etc. to communicate?

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Feb 11, 2019 •
edited
Loading

We communicate via Github Issues. Maybe later on we will add other ways to discuss.

@iamarek
Copy link
Contributor

iamarek commented Feb 11, 2019

I'd like to help. I would take care of Getting Started page, if that's fine, since I almost have it done?

@jakubdrozdek
Copy link
Member

@TeoTN @iamarek @cvqprs @bartlomiejzuber Since we need approval of TWO maintainers for a PR to be merged, please don't let them wait for too long unreviewed.

@bartlomiejzuber
Copy link
Member

bartlomiejzuber commented Feb 11, 2019 •
edited
Loading

@jakubdrozdek @cvqprs @TeoTN @iamarek I've made discord channel for us. You can join using this link:
(We have moved to Spectrum). I think it would be easier to communicate via discord. 🤙

// edit
Please use link to Spectrum channel: https://spectrum.chat/reactjs-org-i18n.

@jakubdrozdek
Copy link
Member

My discord says that this link is either invalid or outdated...

@cvqprs
Copy link
Member

cvqprs commented Feb 12, 2019 •
edited
Loading

The same here, issue with link.

If I can suggest https://spectrum.chat/ or https://rocket.chat/ - free slack alternatives.

@jakubdrozdek
Copy link
Member

@tesseralis Could you add @iamarek to the team?

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Feb 12, 2019 •
edited
Loading

@iamarek @TeoTN @cvqprs @bartlomiejzuber Please add the PR reference to the list above, right after you create it. It will make the list consistent and up-to-date at all times, and it will be easier to track the progress or see when and how was the file translated.

@jakubdrozdek
Copy link
Member

I have created reactjs-org-i18n community on Spectrum (https://spectrum.chat/reactjs-org-i18n). Please join if you want to discuss anything related to the docs translation process.

@marcinostrouch
Copy link
Contributor

@tesseralis Hello. My name is Marcin. I used to be a professional English-Polish translator and I am a React enthusiast. I'd be very happy to contribute to this project. Please be so kind as to add me to the group. Here's my LinkedIn profile.

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Feb 12, 2019 •
edited
Loading

Cool, more experienced volunteers! @marcinostrouch, welcome aboard!
Please go to our Spectrum channel and join the discussion. Nat will probably add you some time later.

@tesseralis
Copy link
Member Author

@marcinostrouch you can start by choosing a page to translate! If you want to be a maintainer, update the list of Polish translation maintainers and get one of the current maintainers to approve it, and I'll add you to the list.

@marcinostrouch
Copy link
Contributor

Great! Thank you guys @tesseralis @jakubdrozdek

@jakubdrozdek
Copy link
Member

@iamarek @cvqprs Please do the same with the list of Polish translation maintainers (as @tesseralis mentioned) if you want to be maintainers, too.

@jakubdrozdek
Copy link
Member

We are switching the communication platform again... But hopefully for the last time.
Please join to the Slack workspace called react-translations via this link. If it doesn't work for you for some reason, send me your e-mail address and I'll invite you.

@marcinostrouch
Copy link
Contributor

Doing "Conditional Rendering"

@michal-bednarz
Copy link
Contributor

Hi, I want to help with translations so I'll take "Error Boundaries"

@tesseralis
Copy link
Member Author

I'm going to put the testing section under "Next Steps" for now so you all don't end up losing progress on Core ;)

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Sep 3, 2019 •
edited
Loading

Thanks, @tesseralis! :) Makes sense. Did you notice a drop in the percentage of our progress?

@jakubdrozdek
Copy link
Member

@tesseralis Hey, Nat. Could you add @m8ms to React Community? I'd like to add him to the translation team, but I'm allowed to add Community members only.

@michal-bednarz
Copy link
Contributor

Hey again, I would like to help with translating 'JSX In Depth' page :)

@karpiuMG
Copy link
Contributor

Hey guys, I will take "Uncontrolled Components" section :)

@karpiuMG
Copy link
Contributor

I'll take "React Without JSX" next

@karpiuMG
Copy link
Contributor

I'll take "Babel, JSX, and Build Steps"

@karpiuMG
Copy link
Contributor

I'll take "File Structure" next

@karpiuMG
Copy link
Contributor

I'll take "Virtual DOM and Internals"

@jakubdrozdek jakubdrozdek reopened this Jan 16, 2020
@karpiuMG
Copy link
Contributor

Taking "Passing Functions to Components"

@michal-bednarz
Copy link
Contributor

I'll take Optimizing Performance next :) JSX in depth in code review already

@stepek
Copy link
Contributor

stepek commented Feb 3, 2020 •
edited
Loading

i'll take Typechecking With PropTypes #185

@jakubdrozdek
Copy link
Member

@tesseralis Hey! I just noticed there are a couple of checkboxes missing on the translation list in the first post. Do you have the complete list and could you paste it here? Or at least tell me where can I get the latest pages list :-) Thanks in advance.

@polapolaczek
Copy link

Hey! If I may - I started translation of Portals page #215

@jakubdrozdek
Copy link
Member

jakubdrozdek commented Aug 18, 2020 •
edited
Loading

@polapolaczek @mbiesiad Please join our Slack workspace to see the glossary and check how we translate things here :-)
Link to Slack workspace is in the first post of this thread.

@mbiesiad
Copy link
Contributor

@jakubdrozdek Is this still active? Is this link correct? I'm a member of several workspaces there, but here is a problem with log in.. I'll try again close to the Fri. Let's keep in touch, greetings.

@jakubdrozdek
Copy link
Member

It is. Maybe you need some kind of invite? I remember there's this link: https://rt-slack-invite.herokuapp.com/. Maybe it still works?

@mbiesiad
Copy link
Contributor

it works! thanks a lot 🦄

@marcin-wicha
Copy link
Contributor

Hi. I'd like to translate Reconciliation page. To me it's a very important part of the docs that's often misunderstood.

@marcin-wicha
Copy link
Contributor

@jakubdrozdek #236 Reconciliation is waiting for review 👍

@b3s23love
Copy link

HI, I would like to translate: Versioning Policy

rickhanlonii pushed a commit that referenced this issue Apr 17, 2023
@renancouto
Fix legacy link (#1)
7863b5b
@gaearon gaearon changed the title Polish Translation Progress [OLD] Legacy Polish Translation Progress Apr 25, 2023
@gaearon
Copy link
Member

gaearon commented Apr 25, 2023

Thanks to everyone who contributed to the old website translation!
Closing this issue in favor of the new translation: #287.

@gaearon gaearon closed this as completed Apr 25, 2023
@gaearon gaearon unpinned this issue Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests