Italian translation #2464

forgoroe · 2021-07-08T10:57:43Z

Have you followed the contributing guidelines?
Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

forgoroe · 2021-07-14T11:49:54Z

Any updates on this? I am almost done translating best-practices.md in full

nholden · 2021-07-14T21:22:48Z

Thanks for your work on this, @forgoroe! ❤️

Looking good! Please let us know when the translation is fully complete and we can review it. Here's a tip from the contributing guide in case it's helpful:

Completing an initial translation of the whole site is a fairly large task. One way to break that task up is to work with other translators through pull requests on your fork. Example: pull requests on fork for German translation and corresponding initial pull request for German translation on this repository. You can also add collaborators to your fork if you'd like to invite other translators to commit directly to your fork and share responsibility for merging pull requests.

Could you revert the changes to Gemfile.lock?

Raphael-MOUQUIN · 2021-07-20T09:48:07Z

Hi all,
Have can we merge submitted corrections?

Thnaks for your collaboration
Best Regards
Raphael

P.S.
referencing #2462

itsbagpack

It looks like this translation is still work in progress as there are articles in there that are still in English and need to be translated to Italian. As such, I will be converting this PR to Draft. Please let us know when the translation is complete and ready for another review. Thank you!

itsbagpack · 2021-07-21T19:15:26Z

_articles/it/best-practices.md

+toc:
+  what-does-it-mean-to-be-a-maintainer: "Cosa significa essere un maintainer?"
+  documenting-your-processes: "Il processo di documentazione"
+  learning-to-say-no: "Imparare a dire di no"
+  leverage-your-community: "Utilizza la tua community"
+  bring-in-the-robots: "Automatizza"
+  its-okay-to-hit-pause: "Prenditi una pausa"


The toc section here should be removed as per point 5 in our Contribution guidelines

itsbagpack · 2021-07-21T19:15:56Z

_articles/it/building-community.md

+toc:
+  setting-your-project-up-for-success: "Setting your project up for success"
+  growing-your-community: "Growing your community"
+  resolving-conflicts: "Resolving conflicts"


The toc section should be removed as per point 5 of our Contribution guidelines

mrymzf

Marym

chat is open number on 910 140 4305

forgoroe · 2021-07-24T10:54:02Z

Thanks for your work on this, @forgoroe! ❤️

Looking good! Please let us know when the translation is fully complete and we can review it. Here's a tip from the contributing guide in case it's helpful:

Completing an initial translation of the whole site is a fairly large task. One way to break that task up is to work with other translators through pull requests on your fork. Example: pull requests on fork for German translation and corresponding initial pull request for German translation on this repository. You can also add collaborators to your fork if you'd like to invite other translators to commit directly to your fork and share responsibility for merging pull requests.

Could you revert the changes to Gemfile.lock?

whenever I run script/test I get changes to the Gemfile.lock file. How do I avoid this? Should I add Gemfile.lock to .gitignore and commit to own "it" branch to avoid having to manually discard those changes every time a test is run? Do you have any advice on how to handle this? Thank you!

mrymzf · 2021-07-24T12:06:43Z

_articles/it/building-community.md

+* **Clearly explain how to contribute**, using [your CONTRIBUTING file](../starting-a-project/#writing-your-contributing-guidelines) and keeping your issues up-to-date.
+* **Good first issues**: To help new contributors get started, consider explicitly [labeling issues that are simple enough for beginners to tackle](https://help.github.com/en/articles/helping-new-contributors-find-your-project-with-labels). GitHub will then surface these issues in various places on the platform, increasing useful contributions, and reducing friction from users tackling issues that are too hard for their level.
+
+[GitHub's 2017 Open Source Survey](http://opensourcesurvey.org/2017/) showed incomplete or confusing documentation is the biggest problem for open source users. Good documentation invites people to interact with your project. Eventually, someone will open an issue or pull request. Use these interactions as opportunities to move them down the funnel.


http://-practices.md

Raphael-MOUQUIN · 2021-08-02T18:35:07Z

ok better. thanks all for your help and contributions Best Regards

…

On 24/07/2021, mrymzf ***@***.***> wrote: @mrymzf commented on this pull request. > + +### Make people feel welcome + +One way to think about your project's community is through what @MikeMcQuaid calls the [contributor funnel](https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/): + +![Contributor funnel](/assets/images/building-community/contributor_funnel_mikemcquaid.png) + +As you build your community, consider how someone at the top of the funnel (a potential user) might theoretically make their way to the bottom (an active maintainer). Your goal is to reduce friction at each stage of the contributor experience. When people have easy wins, they will feel incentivized to do more. + +Start with your documentation: + +* **Make it easy for someone to use your project.** [A friendly README](../starting-a-project/#writing-a-readme) and clear code examples will make it easier for anyone who lands on your project to get started. +* **Clearly explain how to contribute**, using [your CONTRIBUTING file](../starting-a-project/#writing-your-contributing-guidelines) and keeping your issues up-to-date. +* **Good first issues**: To help new contributors get started, consider explicitly [labeling issues that are simple enough for beginners to tackle](https://help.github.com/en/articles/helping-new-contributors-find-your-project-with-labels). GitHub will then surface these issues in various places on the platform, increasing useful contributions, and reducing friction from users tackling issues that are too hard for their level. + +[GitHub's 2017 Open Source Survey](http://opensourcesurvey.org/2017/) showed incomplete or confusing documentation is the biggest problem for open source users. Good documentation invites people to interact with your project. Eventually, someone will open an issue or pull request. Use these interactions as opportunities to move them down the funnel. http://-practices.md -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #2464 (review)

nholden · 2021-08-17T22:17:30Z

whenever I run script/test I get changes to the Gemfile.lock file. How do I avoid this? Should I add Gemfile.lock to .gitignore and commit to own "it" branch to avoid having to manually discard those changes every time a test is run? Do you have any advice on how to handle this? Thank you!

@forgoroe: Hmm, I haven't heard of this issue! Are you still bumping into it? It looks like changes to Gemfile.lock are no longer on this branch.

It looks like this is still true:

It looks like this translation is still work in progress as there are articles in there that are still in English and need to be translated to Italian. As such, I will be converting this PR to Draft. Please let us know when the translation is complete and ready for another review. Thank you!

MikeMcQuaid

Need to fix CI failures https://github.com/github/opensource.guide/pull/2464/checks?check_run_id=3532342460#step:7:38

dahuison · 2021-09-18T05:53:58Z

Another mental breakdown..thank you hub..
And jbbank.There was a present ..ill try it later..
Thankyou thanks you you ...i love hub..

brookreflections · 2021-09-20T01:33:04Z

YES- happens so easily- so sorry. My issue caused me the same thing- too mush of a loss for me. Still hunting for a savior. Terrible for a senior pensioner- big lost considering current price. Hard earned fiat. dh xx [image: photo] Create your own email signature <https://www.wisestamp.com/create-own-signature/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

…

On Sat, 18 Sept 2021 at 15:55, dahuison ***@***.***> wrote: Another mental breakdown..thank you hub.. And jbbank.There was a present ..ill try it later.. Thankyou thanks you you ...i love hub.. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2464 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASH6ZZQS6U25BQKD3RNMVVTUCQSUPANCNFSM5AAP6EKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Karitta123

Karitta

forgoroe added 2 commits June 28, 2021 13:20

add it.yml

e32311d

set up it folder, translate 1/2 best-practices (it)

7912a07

forgoroe requested a review from a team as a code owner July 8, 2021 10:57

This comment has been minimized.

Sign in to view

forgoroe added 2 commits July 21, 2021 15:16

best-practices.md update (3/4 done)

21d9fa2

revert Gemfile.lock

dca79c2

itsbagpack reviewed Jul 21, 2021

View reviewed changes

itsbagpack marked this pull request as draft July 21, 2021 19:17

remove toc sections; finish best-practices.md translation

7d699f1

mrymzf reviewed Jul 24, 2021

View reviewed changes

translate 1/2 building-community.md

de6fb63

MaryJaneLove4 approved these changes Aug 9, 2021

View reviewed changes

MikeMcQuaid marked this pull request as ready for review September 7, 2021 09:51

Merge branch 'main' into it

2f8b458

MikeMcQuaid marked this pull request as draft September 7, 2021 09:52

MikeMcQuaid suggested changes Sep 7, 2021

View reviewed changes

MikeMcQuaid added the translation label Sep 7, 2021

Karitta123 reviewed Oct 2, 2021

View reviewed changes

MikeMcQuaid closed this Oct 4, 2021

Italian translation #2464

Italian translation #2464

Uh oh!

Conversation

forgoroe commented Jul 8, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment has been minimized.

forgoroe commented Jul 14, 2021

Uh oh!

nholden commented Jul 14, 2021

Uh oh!

Raphael-MOUQUIN commented Jul 20, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

itsbagpack left a comment

Choose a reason for hiding this comment

Uh oh!

itsbagpack Jul 21, 2021

Choose a reason for hiding this comment

Uh oh!

itsbagpack Jul 21, 2021

Choose a reason for hiding this comment

Uh oh!

mrymzf left a comment

Choose a reason for hiding this comment

Uh oh!

forgoroe commented Jul 24, 2021

Uh oh!

mrymzf Jul 24, 2021

Choose a reason for hiding this comment

Uh oh!

Raphael-MOUQUIN commented Aug 2, 2021 via email

Uh oh!

nholden commented Aug 17, 2021

Uh oh!

MikeMcQuaid left a comment

Choose a reason for hiding this comment

Uh oh!

dahuison commented Sep 18, 2021

Uh oh!

brookreflections commented Sep 20, 2021 via email

Uh oh!

Karitta123 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

forgoroe commented Jul 8, 2021 •

edited

Loading

Raphael-MOUQUIN commented Jul 20, 2021 •

edited

Loading