من مصلحتك جذب المساهمين الذين يستمتعون ويستطيعون القيام بالأشياء التي لا تستطيع القيام بها. هل تحب البرمجة لكن لا تحب الرد على issues؟ إذن حدد هؤلاء الأشخاص في مجتمعك ودعهم يتولون ذلك.
-— @gr2m, ["المجتمعات الترحيبية"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["المجتمعات الترحيبية"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/bg/building-community.md b/_articles/bg/building-community.md index 2d3ffd75b20..e599af9c505 100644 --- a/_articles/bg/building-community.md +++ b/_articles/bg/building-community.md @@ -163,7 +163,7 @@ related: * **Стартирайте файл CONTRIBUTORS или AUTHORS във вашия проект**, който изброява всички, които са допринесли за вашия проект, както прави [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Ако имате значителна общност, **изпратете бюлетин или напишете публикация в блог**, като благодарите на сътрудниците. [Тази седмица в Rust](https://this-week-in-rust.org/) на Rust и [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) на Hoodie са два добри примера. +* Ако имате значителна общност, **изпратете бюлетин или напишете публикация в блог**, като благодарите на сътрудниците. [Тази седмица в Rust](https://this-week-in-rust.org/) на Rust и [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) на Hoodie са два добри примера. * **Дайте достъп за ангажиране на всеки сътрудник.** @felixge установи, че това кара хората [да бъдат по-развълнувани да усъвършенстват корекциите си](https://felixge.de/2013/03/11/the-pull-request-hack.html) и дори намери нови поддържащи за проекти, по които не е работил от известно време. @@ -177,7 +177,7 @@ related:
\[Във ваш\] най-добър интерес е да набирате сътрудници, които се радват и които са способни да правят нещата, които вие не сте. Обичате ли да кодирате, но не и да отговаряте на въпроси? След това идентифицирайте онези хора във вашата общност, които го правят, и им го позволете.
-— @gr2m, ["Приветстващи общности"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Приветстващи общности"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/bn/building-community.md b/_articles/bn/building-community.md index 7d3a9a46aae..eabd7f3d066 100644 --- a/_articles/bn/building-community.md +++ b/_articles/bn/building-community.md @@ -163,7 +163,7 @@ See if you can find ways to share ownership with your community as much as possi * **Start a CONTRIBUTORS or AUTHORS file in your project** that lists everyone who's contributed to your project, like [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) does. -* If you've got a sizable community, **send out a newsletter or write a blog post** thanking contributors. Rust's [This Week in Rust](https://this-week-in-rust.org/) and Hoodie's [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) are two good examples. +* If you've got a sizable community, **send out a newsletter or write a blog post** thanking contributors. Rust's [This Week in Rust](https://this-week-in-rust.org/) and Hoodie's [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) are two good examples. * **Give every contributor commit access.** @felixge found that this made people [more excited to polish their patches](https://felixge.de/2013/03/11/the-pull-request-hack.html), and he even found new maintainers for projects that he hadn't worked on in awhile. @@ -177,7 +177,7 @@ While you may not always find someone to answer the call, putting a signal out t
\[It's in your\] best interest to recruit contributors who enjoy and who are capable of doing the things that you are not. Do you enjoy coding, but not answering issues? Then identify those individuals in your community who do and let them have it.
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/building-community.md b/_articles/building-community.md index d8985713137..dadfdf62f41 100644 --- a/_articles/building-community.md +++ b/_articles/building-community.md @@ -163,7 +163,7 @@ See if you can find ways to share ownership with your community as much as possi * **Start a CONTRIBUTORS or AUTHORS file in your project** that lists everyone who's contributed to your project, like [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) does. -* If you've got a sizable community, **send out a newsletter or write a blog post** thanking contributors. Rust's [This Week in Rust](https://this-week-in-rust.org/) and Hoodie's [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) are two good examples. +* If you've got a sizable community, **send out a newsletter or write a blog post** thanking contributors. Rust's [This Week in Rust](https://this-week-in-rust.org/) and Hoodie's [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) are two good examples. * **Give every contributor commit access.** @felixge found that this made people [more excited to polish their patches](https://felixge.de/2013/03/11/the-pull-request-hack.html), and he even found new maintainers for projects that he hadn't worked on in awhile. @@ -177,7 +177,7 @@ While you may not always find someone to answer the call, putting a signal out t
\[It's in your\] best interest to recruit contributors who enjoy and who are capable of doing the things that you are not. Do you enjoy coding, but not answering issues? Then identify those individuals in your community who do and let them have it.
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/de/building-community.md b/_articles/de/building-community.md index 8415d5ff371..0f8dcfca050 100644 --- a/_articles/de/building-community.md +++ b/_articles/de/building-community.md @@ -183,7 +183,7 @@ Schauen Sie, ob Sie Wege finden können, Verantwortlichkeiten so weit wie mögli * **Führen Sie eine CONTRIBUTORS- oder AUTHORS-Datei in Ihrem Projekt**, die alle Leute aufzählt, die einen Beitrag geleistet haben, wie z.B. bei [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Wenn Sie schon eine etwas größere Gemeinschaft versammelt haben, **senden Sie eine Rundmail oder schreiben ins Blog**, dass Sie Kontributor\*innen danken. Rusts [This Week in Rust](https://this-week-in-rust.org/) und Hoodies [Shoutout-Grüße](http://hood.ie/blog/shoutouts-week-24.html) sind zwei gute Beispiele dafür. +* Wenn Sie schon eine etwas größere Gemeinschaft versammelt haben, **senden Sie eine Rundmail oder schreiben ins Blog**, dass Sie Kontributor\*innen danken. Rusts [This Week in Rust](https://this-week-in-rust.org/) und Hoodies [Shoutout-Grüße](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) sind zwei gute Beispiele dafür. * **Geben Sie allen Mitwirkenden Schreibzugriff.** @felixge fand heraus, dass dies Leute [zu mehr Feinschliff ihrer Beiträge anspornt](https://felixge.de/2013/03/11/the-pull-request-hack.html), und gewann sogar neue Maintainer\*innen für Projekte, an denen er selbst schon eine Weile nicht mehr arbeitete. @@ -201,7 +201,7 @@ Während Sie vielleicht nicht immer Leute finden, die einem Aufruf folgen, erhö _\[It's in your\] best interest to recruit contributors who enjoy and who are capable of doing the things that you are not. Do you enjoy coding, but not answering issues? Then identify those individuals in your community who do and let them have it._-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/de/finding-users.md b/_articles/de/finding-users.md index fd285623e13..f54ad6cdec5 100644 --- a/_articles/de/finding-users.md +++ b/_articles/de/finding-users.md @@ -129,7 +129,7 @@ Während Sie Ihren Vortrag ausarbeiten, konzentrieren Sie sich auf das für Ihr _When you start writing your talk, no matter what your topic is, it can help if you see your talk as a story that you tell people._-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/el/building-community.md b/_articles/el/building-community.md index 12d11d82e45..612fde789a2 100644 --- a/_articles/el/building-community.md +++ b/_articles/el/building-community.md @@ -163,7 +163,7 @@ related: * **Ξεκινήστε ένα αρχείο CONTRIBUTORS ή AUTHORS στο πρότζκετ σας** το οποίο θα απαριθμεί όλους όσους έχουν συνεισφέρει στο πρότζεκτ σας, όπως κάνει το [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Αν έχετε μια σημαντική κοινότητα, **αποστείλετε ένα ενημερωτικό δελτίο ή γράψτε μια δημοσίευση στο ιστολόγιο** ευχαριστώντας τους συνεισφέροντες. Το [This Week in Rust](https://this-week-in-rust.org/) του Rust και το [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) του Hoodie είναι δύο καλά παραδείγματα. +* Αν έχετε μια σημαντική κοινότητα, **αποστείλετε ένα ενημερωτικό δελτίο ή γράψτε μια δημοσίευση στο ιστολόγιο** ευχαριστώντας τους συνεισφέροντες. Το [This Week in Rust](https://this-week-in-rust.org/) του Rust και το [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) του Hoodie είναι δύο καλά παραδείγματα. * **Δώστε σε κάθε συνεισφέροντα πρόσβαση για commit.** Ο @felixge διαπίστωσε ότι αυτό έκανε τους ανθρώπους [πιο ενθουσιασμένους να γυαλίζουν τις διορθώσεις τους](https://felixge.de/2013/03/11/the-pull-request-hack.html), και βρήκε ακόμα και νέους συντηρητές για πρότζεκτ στα οποία δεν είχε δουλέψει για λίγο καιρό. @@ -177,7 +177,7 @@ related:
\[Είναι προς το συμφέρον σας\] να προσλάβετε συνεργάτες που απολαμβάνουν και είναι ικανοί να κάνουν τα πράγματα που εσείς δεν κάνετε. Σας αρέσει να προγραμματίζετε, αλλά όχι να απαντάτε σε θέματα; Τότε εντοπίστε εκείνα τα άτομα στην κοινότητά σας που το κάνουν και αφήστε τα να το κάνουν.
-- @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +- @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/es/building-community.md b/_articles/es/building-community.md index fe289f559de..918f985a5a8 100644 --- a/_articles/es/building-community.md +++ b/_articles/es/building-community.md @@ -163,7 +163,7 @@ Observa si puedes encontrar maneras de compartir la propiedad de tu comunidad ta * **Inicia un archivo de COLABORADORES o AUTORES en tu proyecto** que liste a todos los que colaboraron con tu proyecto, como lo hace [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Si tienes una comunidad considerable, **envía un boletín o escribe un post en un blog** agradeciendo a los colaboradores. Rust's [This Week in Rust](https://this-week-in-rust.org/) y Hoodie's [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) son dos buenos ejemplos. +* Si tienes una comunidad considerable, **envía un boletín o escribe un post en un blog** agradeciendo a los colaboradores. Rust's [This Week in Rust](https://this-week-in-rust.org/) y Hoodie's [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) son dos buenos ejemplos. * **Da a cada colaborador permiso para hacer commit.** @felixge encontró con esto que las personas [se entusiasmaran por pulir sus parches](https://felixge.de/2013/03/11/the-pull-request-hack.html), e incluso encontró nuevas personas para mantener proyectos en los que no había trabajado hace tiempo. @@ -179,7 +179,7 @@ Aunque no siempre encuentres quien responda tu pedido, poner una señal po \[Está entre\] tus mayores intereses se encuentra reclutar colaboradores que disfruten y que sean capaces de hacer las cosas que tu no puedes. ¿Te gusta escribir código, pero no responder a los problemas? Entonces identifica aquellos individuos en tu comunidad que lo hacen y permiteles hacer lo suyo.-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/es/finding-users.md b/_articles/es/finding-users.md index d433069aa78..076d8091c69 100644 --- a/_articles/es/finding-users.md +++ b/_articles/es/finding-users.md @@ -108,7 +108,7 @@ Mientras escribes tu charla, enfócate en lo que el público pueda e
Cuando comienzas a escribir tu charla, sin importar cuál sea tu tópico, puede ser de ayuda ver a tu charla como una historia que le cuentas a la gente.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/fa/building-community.md b/_articles/fa/building-community.md index 15cc1d0c63d..dc6af10c16d 100644 --- a/_articles/fa/building-community.md +++ b/_articles/fa/building-community.md @@ -164,7 +164,7 @@ related: * **یک فایل مشارکت کننده یا مولف در پروژه تان را شروع کنید** تا همه افرادی که به پروژه تان کمک می کردند مانند [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) را لیست کنید. -* **اگر شما یک انجمن بزرگ دارید، یک خبرنامه منتشر کنید یا یک پست وبلاگی بنویسید** که قدردان مشارکت کنندگان هستید. خبرنامه های [This Week in Rust](https://this-week-in-rust.org/) و [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) هودی دو نمونه خوب از این موارد هستند. +* **اگر شما یک انجمن بزرگ دارید، یک خبرنامه منتشر کنید یا یک پست وبلاگی بنویسید** که قدردان مشارکت کنندگان هستید. خبرنامه های [This Week in Rust](https://this-week-in-rust.org/) و [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) هودی دو نمونه خوب از این موارد هستند. * **به همه مشارکت کنندگان دسترسی Commit کردن بدهید.** @fleixge پی برد که این کار، [افراد را وادار می کند](https://felixge.de/2013/03/11/the-pull-request-hack.html) تا با هیجان بیشتری patch هایشان را اصلاح کنند و حتی باعث می شود اعضای جدید برای پروژه هایی بیابید که روی آنها سرمایه گذاری نکرده بودید. @@ -178,7 +178,7 @@ related:
به بهترین وجه به نفعتان است که مشارکت کنندگانی را به عضویت بگیرید که از کارشان لذت می برند و کسانی که قادر به انجام کارهایی هستند که شما نمی توانید انجام دهید. آیا شما از کدگذاری لذت می برید، اما از جواب دادن به موضوعات لذت نمی برید؟ پس آن افرادی را در انجمن خود شناسایی کنید که این کارها را انجام می دهند.
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/fa/finding-users.md b/_articles/fa/finding-users.md index 065db4d0644..36aeed806e9 100644 --- a/_articles/fa/finding-users.md +++ b/_articles/fa/finding-users.md @@ -108,7 +108,7 @@ related:
وقتی احساس کردید که آمادهاید، سخنرانی در کنفرانسها به منظور تبلیغ پروژهی خود را مد نظر قرار دهید. کنفرانسها میتوانند به شما کمک کنند تا به افراد بیشتری، گاهی اوقات از سراسر جهان، دسترسی پیدا کنید.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/fr/building-community.md b/_articles/fr/building-community.md index 1dec5be76ab..98550e98c63 100644 --- a/_articles/fr/building-community.md +++ b/_articles/fr/building-community.md @@ -162,7 +162,7 @@ Voyez si vous pouvez trouver le moyen de partager la propriété avec votre comm * **Démarrez un fichier CONTRIBUTORS ou AUTHORS dans votre projet** qui répertorie tous ceux qui ont contribué à votre projet, comme [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Si vous avez une communauté importante **, envoyez un bulletin d'information ou rédigez un article** remerciant les contributeurs. [La semaine de Rust](https://this-week-in-rust.org/) et celle de Hoodie [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) sont deux bons exemples. +* Si vous avez une communauté importante **, envoyez un bulletin d'information ou rédigez un article** remerciant les contributeurs. [La semaine de Rust](https://this-week-in-rust.org/) et celle de Hoodie [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) sont deux bons exemples. * **Donnez à chaque contributeur un droit de commit.** @felixge a trouvé que cela rendait les gens [plus excités de fignoler leurs patches](https://felixge.de/2013/03/11/the-pull-request-hack.html ), et il a même trouvé de nouveaux responsables pour des projets sur lesquels il n'avait pas travaillé depuis longtemps. @@ -176,7 +176,7 @@ Même s'il se peut que vous ne trouviez pas toujours quelqu'un pour répondre à
\[Il est dans votre\] intérêt de recruter des collaborateurs qui aiment et qui sont capables de faire les choses dont vous n'êtes pas. Aimez-vous le codage, mais ne répondez pas aux problèmes ? Ensuite, identifiez les personnes de votre communauté qui le font et laissez-les en avoir.
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/fr/finding-users.md b/_articles/fr/finding-users.md index ab5c6e81ac4..d2e218f8e74 100644 --- a/_articles/fr/finding-users.md +++ b/_articles/fr/finding-users.md @@ -109,7 +109,7 @@ Au fur et à mesure que vous écrivez votre exposé, concentrez-vous sur ce que
Lorsque vous commencez à écrire votre discours, quel que soit votre sujet, cela peut aider si vous voyez votre conversation comme une histoire que vous racontez.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/hi/building-community.md b/_articles/hi/building-community.md index 642194d3c0b..f182deab4ca 100644 --- a/_articles/hi/building-community.md +++ b/_articles/hi/building-community.md @@ -164,7 +164,7 @@ related: * **अपने प्रोजेक्ट में एक योगदानकर्ता या लेखक फ़ाइल प्रारंभ करें** जिसमें आपके प्रोजेक्ट में योगदान देने वाले सभी लोगों की सूची हो, जैसे [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) करता है. -* यदि आपके पास एक बड़ा समुदाय है, तो **एक समाचार पत्र भेजें या एक ब्लॉग पोस्ट लिखें** योगदानकर्ताओं को धन्यवाद दें। जंग का [This Week in Rust](https://this-week-in-rust.org/) और हुडीज़ [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) दो अच्छे उदाहरण हैं. +* यदि आपके पास एक बड़ा समुदाय है, तो **एक समाचार पत्र भेजें या एक ब्लॉग पोस्ट लिखें** योगदानकर्ताओं को धन्यवाद दें। जंग का [This Week in Rust](https://this-week-in-rust.org/) और हुडीज़ [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) दो अच्छे उदाहरण हैं. * **प्रत्येक योगदानकर्ता को पहुंच प्रदान करें** @felixge ने पाया कि इसने लोगों को बनाया है [more excited to polish their patches](https://felixge.de/2013/03/11/the-pull-request-hack.html), और उन्हें उन परियोजनाओं के लिए नए अनुरक्षक भी मिल गए जिन पर उन्होंने कुछ समय से काम नहीं किया था। @@ -178,7 +178,7 @@ related:
\[यह आपके हित में है\] ऐसे योगदानकर्ताओं को भर्ती करना जो आनंद लेते हैं और जो वह काम करने में सक्षम हैं जो आप नहीं कर सकते। क्या आपको कोडिंग में मजा आता है, लेकिन मुद्दों का जवाब देना नहीं? फिर अपने समुदाय में उन व्यक्तियों की पहचान करें जो ऐसा करते हैं और उन्हें ऐसा करने दें।
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/hu/building-community.md b/_articles/hu/building-community.md index e771c1f5641..09210e6b4d6 100644 --- a/_articles/hu/building-community.md +++ b/_articles/hu/building-community.md @@ -163,7 +163,7 @@ Nézd meg, hogyan találhatod meg a módját, hogy a lehető legnagyobb mérték * **Állíts össze egy CONTRIBUTORS vagy AUTHORS fájlt a projektben,** amely listáz mindenkit aki hozzájárul a projekthez. Például ahogy a [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) csinálja. -* Ha széles közösséged van, **akkor küldj ki hírlevelet vagy vezess blogot** amelyen megköszönöd a hozzájárulásokat. A Rust-nak a [Heti Rust](https://this-week-in-rust.org/) és a Hoodie-nak a [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) két jó példa erre. +* Ha széles közösséged van, **akkor küldj ki hírlevelet vagy vezess blogot** amelyen megköszönöd a hozzájárulásokat. A Rust-nak a [Heti Rust](https://this-week-in-rust.org/) és a Hoodie-nak a [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) két jó példa erre. * **Minden közreműködő kapjon commit jogot.** @felixge szerint az emberek [sokkal aprólékosabban kidolgozzák a hozzájárulásukat](https://felixge.de/2013/03/11/the-pull-request-hack.html), és még több karbantartót lehet bevonni, akik esetleg korábban passzívak voltak. @@ -177,7 +177,7 @@ Bár nem mindig válaszolnak a felhívásodra, de egy jelzés kiküldése növel
A te érdeked az, hogy olyan munkatársakat toborozz, akik élvezik és képesek megtenni azokat a dolgokat, amelyeket te nem. Szereted a kódolást, de nem válaszolsz a kérdésekre? Keresd meg azokat a személyeket a közösségben, akik ezt megteszik, és hagyd őket dolgozni.
-— @gr2m, ["Befogadó közösségek"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Befogadó közösségek"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/hu/finding-users.md b/_articles/hu/finding-users.md index e582fc904e1..19c9f618fad 100644 --- a/_articles/hu/finding-users.md +++ b/_articles/hu/finding-users.md @@ -109,7 +109,7 @@ A beszéd írásakor összpontosíts arra, amit szerinted a közönség érdekes
Amikor az előadásodat készíted, segíthet – függetlenül a témától –, ha úgy tekintesz rá, mint egy történetre, amit elmesélsz a hallgatóságnak.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/id/building-community.md b/_articles/id/building-community.md index 01235e4efda..fc967c92734 100644 --- a/_articles/id/building-community.md +++ b/_articles/id/building-community.md @@ -162,7 +162,7 @@ Cari cara untuk bisa berbagi kepemilikan dengan komunitas Anda sebanyak mungkin. * **Bualah dokumen CONTRIBUTORS atau AUTHORS pada proyek Anda** yang mendata semua orang yang berkontribusi pada proyek Anda, seperti [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Jika Anda memiliki komunitas yang cukup besar, **kirimkan surat berita atau tuliskan blog** dan ucapkan terima kasih pada kontributor. [This Week in Rust](https://this-week-in-rust.org/) milik Rust dan [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) milik Hoodie adalah dua contoh bagus. +* Jika Anda memiliki komunitas yang cukup besar, **kirimkan surat berita atau tuliskan blog** dan ucapkan terima kasih pada kontributor. [This Week in Rust](https://this-week-in-rust.org/) milik Rust dan [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) milik Hoodie adalah dua contoh bagus. * **Berikan setiap kontributor akses commit.** @felixge menemukan bahwa hal ini membuat orang lain [lebih tertarik untuk memperbaiki perbaikan mereka](https://felixge.de/2013/03/11/the-pull-request-hack.html), dan dia juga menemukan pengelola baru untuk proyek yang tidak dia kelola selama beberapa waktu. @@ -176,7 +176,7 @@ Meskipun tidak selalu mudah untuk mendapatkan orang yang memenuhi panggilan Anda
Pastikan untuk merekrut kontributor yang menikmati dan mampu melakukan sesuatu yang tidak Anda bisa lakukan. Apakah Anda suka membuat kode, tetapi tidak suka menjawab laporan permasalahan? Maka cari orang-orang pada komunitas Anda yang suka dengan hal itu dan biarkan mereka untuk melakukannya.
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/id/finding-users.md b/_articles/id/finding-users.md index 4244d95f423..c8fe0933097 100644 --- a/_articles/id/finding-users.md +++ b/_articles/id/finding-users.md @@ -109,7 +109,7 @@ Ketika Anda mulai menuliskan presentasi Anda, fokus pada apa yang akan dianggap
Ketika Anda mulai menuliskan isi presentasi Anda, tidak perduli topiknya, hal itu bisa membantu jika Anda melihatnya seperti menceritakan sebuah cerita kepada orang lain.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/it/building-community.md b/_articles/it/building-community.md index 94ec2a38069..7fa601c4005 100644 --- a/_articles/it/building-community.md +++ b/_articles/it/building-community.md @@ -163,7 +163,7 @@ Vedi se riesci a trovare modi per condividere il più possibile la proprietà co * **Avvia un file CONTRIBUTORI o AUTORI nel tuo progetto** che elenca tutti coloro che hanno contribuito al tuo progetto come [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Se hai una community numerosa, **invia una newsletter o scrivi un post sul blog** ringraziando i contributori. [This Week in Rust](https://this-week-in-rust.org/) di Rust e [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) di Hood sono due ottimi esempi. +* Se hai una community numerosa, **invia una newsletter o scrivi un post sul blog** ringraziando i contributori. [This Week in Rust](https://this-week-in-rust.org/) di Rust e [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) di Hood sono due ottimi esempi. * **Concedi l'accesso al commit a ogni collaboratore.** @felixge ha scoperto che rendeva le persone [più entusiaste di migliorare le proprie soluzioni](https://felixge.de/2013/03/11/the-pull-request-hack.html) e ha anche trovato nuovi manutentori per progetti su cui non lavorava da un po'. @@ -177,7 +177,7 @@ Anche se potresti non trovare sempre qualcuno che risponda alla chiamata, diffon
\[Nel tuo\] miglior interesse è reclutare collaboratori che si divertano e siano capaci di fare cose che tu non sei. Ti piace programmare ma non rispondi alle domande? Quindi identifica le persone nella tua comunità che lo fanno e consenti loro di farlo.
-— @gr2m, ["Comunità accoglienti"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Comunità accoglienti"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ja/building-community.md b/_articles/ja/building-community.md index 22a34b08a22..547dd3746ce 100644 --- a/_articles/ja/building-community.md +++ b/_articles/ja/building-community.md @@ -162,7 +162,7 @@ CONTRIBUTING ファイルに、新しいコントリビューターに始め方 * **CONTRIBUTORS ファイルや AUTHORS ファイルをプロジェクトに作ろう。** [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) が実施しているように、これらのファイルにプロジェクトにコントリビュートしてくれた人すべてをリストしましょう。 -* かなり大きなコミュニティを既に獲得しているのであれば、コントリビューターへの感謝を伝える **ニュースレターを送ったり、ブログポストを書いたりしましょう。** Rust の [This Week in Rust](https://this-week-in-rust.org/) や Hoodie の [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) はどちらも良い事例です。 +* かなり大きなコミュニティを既に獲得しているのであれば、コントリビューターへの感謝を伝える **ニュースレターを送ったり、ブログポストを書いたりしましょう。** Rust の [This Week in Rust](https://this-week-in-rust.org/) や Hoodie の [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) はどちらも良い事例です。 * **全てのコントリビューターにコミット権限を与えよう。** @felixge はこれによって人々が [パッチに磨きをかけることによりワクワクするようになる](https://felixge.de/2013/03/11/the-pull-request-hack.html)ことに気づき、更にしばらくの間取り組んでいなかったプロジェクトの新しいメンテナーを見つけることさえできたのです。 @@ -176,7 +176,7 @@ CONTRIBUTING ファイルに、新しいコントリビューターに始め方
あなたがやりたいと思わないことを楽しんでやってくれるコントリビューターを募集する事が得策です。コーディングは好きだけどイシューに回答するのは好きではありませんか？それなら、コミュニティの中からそれを楽しんでくれる人を探し出して、その人にやってもらいましょう。
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ja/finding-users.md b/_articles/ja/finding-users.md index 7dfc476f9f2..e7b55d99a50 100644 --- a/_articles/ja/finding-users.md +++ b/_articles/ja/finding-users.md @@ -109,7 +109,7 @@ Django の共同作者の [@adrianholovaty](https://news.ycombinator.com/item?id
あなたの発表の準備を始める時に、トピックが何であれ、あなたの発表が人々に物語を伝えるのだと考える事は助けになるでしょう。
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/ko/building-community.md b/_articles/ko/building-community.md index 307442652bb..d3b0c1d02d1 100644 --- a/_articles/ko/building-community.md +++ b/_articles/ko/building-community.md @@ -163,7 +163,7 @@ CONTRIBUTING 파일에 새 기여자들이 시작할 방법을 자세히 설명 * [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md)가 사용하는 방법처럼 **CONTRIBUTORS 혹은 AUTHORS 파일**을 만들어 모든 프로젝트 기여자를 담은 하나의 목록을 작성하세요. -* 어느 정도 규모의 커뮤니티가 형성됐다면 기여자들에 대한 감사를 담은 **뉴스 레터를 보내거나 블로그 포스트를 게시하세요**. Rust의 [This Week in Rust](https://this-week-in-rust.org/)와 Hoodie의 [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html)가 좋은 예입니다. +* 어느 정도 규모의 커뮤니티가 형성됐다면 기여자들에 대한 감사를 담은 **뉴스 레터를 보내거나 블로그 포스트를 게시하세요**. Rust의 [This Week in Rust](https://this-week-in-rust.org/)와 Hoodie의 [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html)가 좋은 예입니다. * **모든 참여자에게 커밋 권한을 부여하세요.** @felixge는 이 방법이 사람들이 [더 열심히 패치를 개선하게 한다는 사실](http://felixge.de/2013/03/11/the-pull-request-hack.html)을 알았고, 그가 자리에 없는 동안 프로젝트 관리자 일을 맡아 주는 사람들을 발견하기도 했습니다. @@ -177,7 +177,7 @@ CONTRIBUTING 파일에 새 기여자들이 시작할 방법을 자세히 설명
\[It's in your\] best interest to recruit contributors who enjoy and who are capable of doing the things that you are not. Do you enjoy coding, but not answering issues? Then identify those individuals in your community who do and let them have it.
-— @gr2m, ["Welcoming Communities”](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities”](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ko/finding-users.md b/_articles/ko/finding-users.md index 545394fc19b..32b8b45ceb4 100644 --- a/_articles/ko/finding-users.md +++ b/_articles/ko/finding-users.md @@ -109,7 +109,7 @@ Django의 공동 크리에이터인 [@adrianholovaty](https://news.ycombinator.c
When you start writing your talk, no matter what your topic is, it can help if you see your talk as a story that you tell people.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk”](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk”](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/ms/building-community.md b/_articles/ms/building-community.md index 4226e9d79a7..4ae0194bb47 100644 --- a/_articles/ms/building-community.md +++ b/_articles/ms/building-community.md @@ -163,7 +163,7 @@ Lihat apakah anda boleh mencari cara untuk berkongsi pemilikan dengan komuniti a * **Mulakan fail CONTRIBUTORS atau AUTHORS dalam projek anda** yang menyenaraikan semua orang yang menyumbang untuk projek anda, seperti [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) -* Sekiranya anda mempunyai komuniti yang cukup besar, **menghantar surat berita atau menulis catatan blog** mengucapkan terima kasih kepada penyumbang. Penyumbang Rust [This Week in Rust](https://this-week-in-rust.org/) dan penyumbang Hoodie [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) adalah dua contoh yang baik. +* Sekiranya anda mempunyai komuniti yang cukup besar, **menghantar surat berita atau menulis catatan blog** mengucapkan terima kasih kepada penyumbang. Penyumbang Rust [This Week in Rust](https://this-week-in-rust.org/) dan penyumbang Hoodie [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) adalah dua contoh yang baik. * **Berikan akses kepada setiap penyumbang.** @felixge mendapati bahawa ini menjadikan orang [lebih teruja untuk menggilap patch mereka](https://felixge.de/2013/03/11/the-pull-request-hack.html), dan dia malah menjumpai penyelenggara baru untuk projek-projek yang belum pernah dia kerjakan sebentar lagi. @@ -177,7 +177,7 @@ Walaupun anda mungkin tidak selalu menjumpai seseorang untuk menjawab panggilan
\[Ia ada di dalam anda\] minat terbaik untuk merekrut penyumbang yang menikmati dan yang mampu melakukan perkara yang bukan anda lakukan. Adakah anda menikmati pengekodan, tetapi tidak menjawab masalah? Kemudian kenal pasti individu-individu dalam komuniti anda yang melakukannya dan biarkan mereka memilikinya.
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ms/finding-users.md b/_articles/ms/finding-users.md index 4b2f76d08e9..ed2864bb9b6 100644 --- a/_articles/ms/finding-users.md +++ b/_articles/ms/finding-users.md @@ -109,7 +109,7 @@ Semasa anda menulis ceramah anda, tumpukan perhatian kepada perkara yang menarik
Apabila anda mula menulis ceramah anda, tidak kira apa topik anda, ia dapat membantu sekiranya anda melihat perbincangan anda sebagai cerita yang anda sampaikan kepada orang lain.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/nl/building-community.md b/_articles/nl/building-community.md index 15b99b75b94..8c7e30589e2 100644 --- a/_articles/nl/building-community.md +++ b/_articles/nl/building-community.md @@ -174,7 +174,7 @@ Kijk of je manieren kunt vinden om het eigendom zoveel mogelijk met je gemeensch * **Start een CONTRIBUTORS- of AUTHORS-bestand in uw project** met een lijst van iedereen die aan uw project heeft bijgedragen, zoals [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) doet. -* Als je een omvangrijke community hebt, **stuur dan een nieuwsbrief of schrijf een blogpost** om bijdragers te bedanken. Rust's [Deze week in Rust](https://this-week-in-rust.org/) en Hoodie's [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) zijn twee goede voorbeelden. +* Als je een omvangrijke community hebt, **stuur dan een nieuwsbrief of schrijf een blogpost** om bijdragers te bedanken. Rust's [Deze week in Rust](https://this-week-in-rust.org/) en Hoodie's [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) zijn twee goede voorbeelden. * **Geef elke bijdrager toegang tot commit.** @felixge ontdekte dat dit mensen [meer enthousiast maakte om hun patches op te poetsen](https://felixge.de/2013/03/11/the-pull-request-hack.html), en hij vond zelfs nieuwe beheerders voor projecten waaraan hij al een tijdje niet had gewerkt. @@ -192,7 +192,7 @@ Hoewel je misschien niet altijd iemand vindt om de oproep te beantwoorden, vergr _\[It's in your\] best interest to recruit contributors who enjoy and who are capable of doing the things that you are not. Do you enjoy coding, but not answering issues? Then identify those individuals in your community who do and let them have it._-— @gr2m, ["Gastvrije gemeenschappen"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Gastvrije gemeenschappen"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/nl/finding-users.md b/_articles/nl/finding-users.md index bae56a7678c..f0c5b22caaf 100644 --- a/_articles/nl/finding-users.md +++ b/_articles/nl/finding-users.md @@ -124,7 +124,7 @@ Concentreer u tijdens het schrijven van uw lezing op wat uw publiek interessant _When you start writing your talk, no matter what your topic is, it can help if you see your talk as a story that you tell people._-— Lena Reinhard, ["Hoe u een Tech Conferentie Lezing voorbereidt en schrijft"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["Hoe u een Tech Conferentie Lezing voorbereidt en schrijft"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/pcm/building-community.md b/_articles/pcm/building-community.md index b4dda5686fc..dddb23ec88e 100644 --- a/_articles/pcm/building-community.md +++ b/_articles/pcm/building-community.md @@ -157,7 +157,7 @@ Try look for ways wey you fit share this ownership with your community as much a * **Start CONTRIBUTORS or AUTHORS file for your project** wey go list everybody wey don yan-kick for your project, like [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) do. -* If your community don shapely well-well, **send newsletter or write blog post** to appreciate the people wey don yan-kick. Rust's [This Week in Rust](https://this-week-in-rust.org/) and Hoodie's [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) na two examples wey dey good. +* If your community don shapely well-well, **send newsletter or write blog post** to appreciate the people wey don yan-kick. Rust's [This Week in Rust](https://this-week-in-rust.org/) and Hoodie's [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) na two examples wey dey good. * **Give every contributor access to commit.** @felixge see say this one dey ginger people, e make dem dey shine their patches [more](https://felixge.de/2013/03/11/the-pull-request-hack.html), and e even find new maintainers for projects wey e never dey touch for long. @@ -167,7 +167,7 @@ The fact na say [most projects get](https://peerj.com/preprints/1233/) only one Even if you no fit always find person to answer the call, once you put signal for there, e dey increase chance say other people go waka come yan-kick. The earlier you start, the better for you, because e go make people waka come fast-fast. -Na for [Welcoming Communities](http://hood.ie/blog/welcoming-communities.html), @gr2m yarn say e dey for your [best interest](https://peerj.com/preprints/1233/) to find contributors wey sabi and enjoy to do the things wey you no sabi. If you like code but e no dey easy for you to answer issues, try find people for your community wey sabi, make dem handle am. +Na for [Welcoming Communities](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html), @gr2m yarn say e dey for your [best interest](https://peerj.com/preprints/1233/) to find contributors wey sabi and enjoy to do the things wey you no sabi. If you like code but e no dey easy for you to answer issues, try find people for your community wey sabi, make dem handle am. ## Settling Wahala diff --git a/_articles/pl/building-community.md b/_articles/pl/building-community.md index ea217246994..27d23a36b6a 100644 --- a/_articles/pl/building-community.md +++ b/_articles/pl/building-community.md @@ -171,7 +171,7 @@ Sprawdź, czy możesz w jak największym stopniu znaleźć sposób na dzielenie * **Uruchom plik CONTRIBUTORS lub AUTHORS w swoim projekcie** zawiera listę wszystkich, którzy przyczynili się do twojego projektu, takich jak [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Jeśli masz sporą społeczność, **wyślij biuletyn lub napisz post na blogu** dziękując autorom. Rusta [This Week in Rust](https://this-week-in-rust.org/) i Hoodie'ego [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) są dwoma dobrymi przykładami +* Jeśli masz sporą społeczność, **wyślij biuletyn lub napisz post na blogu** dziękując autorom. Rusta [This Week in Rust](https://this-week-in-rust.org/) i Hoodie'ego [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) są dwoma dobrymi przykładami * **Daj dostęp każdemu współautorowi.** @felixge stwierdził, że to sprawiło, że ludzie są [bardziej podekscytowani dopracowywaniem swoich łat](https://felixge.de/2013/03/11/the-pull-request-hack.html), a nawet znalazł nowych opiekunów dla projektów, nad którymi on od jakiegoś czasu nie pracował. @@ -187,7 +187,7 @@ Chociaż nie zawsze możesz znaleźć kogoś, kto odbierze połączenie, wysłan \[It's in your\] best interest to recruit contributors who enjoy and who are capable of doing the things that you are not. Do you enjoy coding, but not answering issues? Then identify those individuals in your community who do and let them have it.-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/pl/finding-users.md b/_articles/pl/finding-users.md index 90f50ca631d..2bea2c5e51e 100644 --- a/_articles/pl/finding-users.md +++ b/_articles/pl/finding-users.md @@ -117,7 +117,7 @@ Pisząc swoje przemówienie, skup się na tym, co zainteresuje twoją publiczno When you start writing your talk, no matter what your topic is, it can help if you see your talk as a story that you tell people.-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/pt/building-community.md b/_articles/pt/building-community.md index 89c93b66a5e..a1bda6379de 100644 --- a/_articles/pt/building-community.md +++ b/_articles/pt/building-community.md @@ -160,7 +160,7 @@ Procure encontrar maneiras de compartilhar a propriedade com a sua comunidade o * **Crie um arquivo CONTRIBUTORS ou AUTHORS em seu projeto** que liste todos os que contribuíram para o seu projeto, como o [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) faz. -* Se você possui uma comunidade de tamanho razoável, **envie uma newsletterm ou escreva um post em um blog** agradecendo aos contribuidores. A [This Week in Rust](https://this-week-in-rust.org/), do Rust, e a [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html), da Hoodie, são dois bons exemplos. +* Se você possui uma comunidade de tamanho razoável, **envie uma newsletterm ou escreva um post em um blog** agradecendo aos contribuidores. A [This Week in Rust](https://this-week-in-rust.org/), do Rust, e a [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html), da Hoodie, são dois bons exemplos. * **Dê permissão de commit para cada um dos contribuidores.** @felixge descobriu que isso fez as pessoas [mais entusiasmadas em polir suas modificações](https://felixge.de/2013/03/11/the-pull-request-hack.html), e até mesmo descobriu novos mantenedores para projetos que ele não havia trabalhado por algum tempo. @@ -174,7 +174,7 @@ Muito embora nem sempre você encontre alguém para responder ao chamado, coloca
\[É do seu\] maior interesse recrutar membros que gostem e sejam capazes de fazer coisas que você não seja. Você gosta de programar, mas não de responder a issues? Então identifique aqueles indivíduos, na sua comunidade, que o façam e deixe-os fazê-lo.
- — @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) + — @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/pt/finding-users.md b/_articles/pt/finding-users.md index f16ee4c13ec..fd45581c7dd 100644 --- a/_articles/pt/finding-users.md +++ b/_articles/pt/finding-users.md @@ -109,7 +109,7 @@ Quando escrever sua fala, foque no que seu público irá achar interessante e ir
Quando você começa a escrever sua palestra, não ligar para qual é o seu tópico pode ajudar, se você enxegar sua palestra como uma história que você conta para as pessoas.
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/ro/building-community.md b/_articles/ro/building-community.md index 68b61861dd8..1eac3bb676e 100644 --- a/_articles/ro/building-community.md +++ b/_articles/ro/building-community.md @@ -194,7 +194,7 @@ Vezi dacă poți găsi moduri de a împărți proprietatea cu comunitatea ta câ * **Începe un fișier CONTRIBUTORS sau AUTHORS în proiectul tău** care listează pe toți cei care au contribuit la proiectul tău, la fel cum face [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Dacă ai o comunitate considerabilă, **trimite un buletin informativ sau scrie o postare de blog** mulțumind contributorilor. [This Week in Rust](https://this-week-in-rust.org/) al Rust și [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) al Hoodie sunt două exemple bune. +* Dacă ai o comunitate considerabilă, **trimite un buletin informativ sau scrie o postare de blog** mulțumind contributorilor. [This Week in Rust](https://this-week-in-rust.org/) al Rust și [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) al Hoodie sunt două exemple bune. * **Dă tuturor contributorilor accesul pentru a face commit-uri** @felixge a găsit că aceasta a făcut oamenii [mai încântați să-și finiseze patch-urile](https://felixge.de/2013/03/11/the-pull-request-hack.html), și el chiar a găsit noi întreținători pentru proiecte la care n-a lucrat de ceva timp. @@ -215,7 +215,7 @@ Realitatea este că [cele mai multe proiecte au doar](https://peerj.com/preprint-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ro/finding-users.md b/_articles/ro/finding-users.md index f74eb1b24c1..49b47241e44 100644 --- a/_articles/ro/finding-users.md +++ b/_articles/ro/finding-users.md @@ -144,7 +144,7 @@ Pe măsură ce-ți scrii discursul, concentrează-te pe ce va găsi interesant p-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/ru/building-community.md b/_articles/ru/building-community.md index d36599b4600..011982f34fd 100644 --- a/_articles/ru/building-community.md +++ b/_articles/ru/building-community.md @@ -163,7 +163,7 @@ related: * **Запустите файл CONTRIBUTORS или AUTORS в своем проекте**, в котором перечислены все, кто внес свой вклад в ваш проект, как, например, [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md). -* Если у вас большое сообщество, **разошлите информационный бюллетень или напишите сообщение в блоге** с благодарностью участникам. [This Week in Rust](https://this-week-in-rust.org/) от Rust и [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) от Hoodie — два хороших примера. +* Если у вас большое сообщество, **разошлите информационный бюллетень или напишите сообщение в блоге** с благодарностью участникам. [This Week in Rust](https://this-week-in-rust.org/) от Rust и [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) от Hoodie — два хороших примера. * **Предоставьте каждому участнику доступ к коммитам.** @felixge обнаружил, что это заставило людей [с большим энтузиазмом оттачивать свои патчи](https://felixge.de/2013/03/11/the-pull-request-hack.html), и он даже нашел новых сопровождающих для проектов, над которыми давно не работал. @@ -177,7 +177,7 @@ related:
\[В ваших\] интересах набирать участников, которым нравится и которые способны делать то, что вам не нравится. Вам нравится писать код, но вы не любите отвечать на вопросы? Определите людей в вашем сообществе, которые это делают, и дайте им это.
-— @gr2m, [«Дружелюбные сообщества»](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, [«Дружелюбные сообщества»](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ru/finding-users.md b/_articles/ru/finding-users.md index 3c569fabe6b..ccfcfa3a658 100644 --- a/_articles/ru/finding-users.md +++ b/_articles/ru/finding-users.md @@ -109,7 +109,7 @@ related:
При подготовке к своему докладу, независимо от его темы, попробуйте представить его как историю, которые вы рассказываете людям.
-- Лена Рейнхард, [«Как подготовить и написать доклад на технической конференции»](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +- Лена Рейнхард, [«Как подготовить и написать доклад на технической конференции»](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/sa/building-community.md b/_articles/sa/building-community.md index 99dba2b7781..cf7c765091f 100644 --- a/_articles/sa/building-community.md +++ b/_articles/sa/building-community.md @@ -141,7 +141,7 @@ Kubernetes kops इव किञ्चन परियोजनानि द्
तव असमर्थान् कार्याणि अन्येषु कर्तुम् प्रेरय। यदि त्वं कोड् रुचिं कुर्वसि किन्तु issue उत्तरदायित्वं न रोचते तर्हि तान् लोकान् चिन्वन्तु यैः एषा भूमिका अनुरूपा।
-— @gr2m, ["Welcoming Communities"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Welcoming Communities"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/sw/building-community.md b/_articles/sw/building-community.md index c3500bfecc5..d6df9fcd476 100644 --- a/_articles/sw/building-community.md +++ b/_articles/sw/building-community.md @@ -163,7 +163,7 @@ Angalia ikiwa unaweza kupata njia za kushiriki umiliki na jamii yako kadri iweze * **Anzisha faili ya CONTRIBUTORS au AUTHORS katika mradi wako** inayoorodhesha kila mtu ambaye amechangia kwenye mradi wako, kama [Sinatra](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) inavyofanya. -* Ikiwa una jamii kubwa, **tuma jarida au andika chapisho la blogu** ukishukuru wachangiaji. [Hii Wiki katika Rust](https://this-week-in-rust.org/) na [Shoutouts za Hoodie](http://hood.ie/blog/shoutouts-week-24.html) ni mifano miwili nzuri. +* Ikiwa una jamii kubwa, **tuma jarida au andika chapisho la blogu** ukishukuru wachangiaji. [Hii Wiki katika Rust](https://this-week-in-rust.org/) na [Shoutouts za Hoodie](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) ni mifano miwili nzuri. * **Wape kila mchango ruhusa ya kuingia.** @felixge alipata kuwa hii ilifanya watu [kuwa na shauku zaidi ya kusafisha patches zao](https://felixge.de/2013/03/11/the-pull-request-hack.html), na hata alipata watunzaji wapya kwa miradi ambayo hakuwa amefanya kazi nayo kwa muda. @@ -177,7 +177,7 @@ Ingawa huenda usipate mtu kila wakati wa kujibu wito, kuweka ishara huko nje kun
\[Ni katika maslahi yako\] kuajiri wachangiaji wanaofurahia na wana uwezo wa kufanya mambo ambayo huwezi. Je, unafurahia kuandika msimbo, lakini si kujibu masuala? Basi tambua watu hao katika jamii yako ambao wanafanya hivyo na uwaachie.
-— @gr2m, ["Jamii za Kukaribisha"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Jamii za Kukaribisha"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ta/building-community.md b/_articles/ta/building-community.md index f7e17cdb471..449389303fa 100644 --- a/_articles/ta/building-community.md +++ b/_articles/ta/building-community.md @@ -162,7 +162,7 @@ related: * [சினாட்ரா](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) போன்று உங்கள் திட்டத்தில் பங்களித்த அனைவருக்கும் **உங்கள் திட்டத்தில் ஒரு பங்களிப்பாளர்கள்(CONTRIBUTORS) அல்லது நூலாசிரியர்கள்(AUTHORS) கோப்பைத் தொடங்கவும்.** -* உங்கள் சமூகம் பெரியதாயிருந்தால், **ஒரு செய்திமடலை முடிக்க அல்லது வலைப்பதிவு இடுகையை எழுதுவதன் முலம்** பங்களிப்பாளர்களுக்கு நன்றி சொல்லுங்கள். ரஸ்ட்-ன் [இந்த வாரம் ரஸ்ட்](https://this-week-in-rust.org/) மற்றும் ஹூடி-ன் [கூச்சலிடுங்கள்](http://hood.ie/blog/shoutouts-week-24.html) இரண்டு நல்ல உதாரணங்களாகும். +* உங்கள் சமூகம் பெரியதாயிருந்தால், **ஒரு செய்திமடலை முடிக்க அல்லது வலைப்பதிவு இடுகையை எழுதுவதன் முலம்** பங்களிப்பாளர்களுக்கு நன்றி சொல்லுங்கள். ரஸ்ட்-ன் [இந்த வாரம் ரஸ்ட்](https://this-week-in-rust.org/) மற்றும் ஹூடி-ன் [கூச்சலிடுங்கள்](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) இரண்டு நல்ல உதாரணங்களாகும். * **ஒவ்வொரு பங்களிப்பாளரும் ஒப்பவிக்கும் அனுமதி தரவும்.** இது மக்களை [அவர்களின் இணைப்புகளை மெருகூட்டுவதற்கு மிகவும் உற்சாகமாக இருக்கிறது](https://felixge.de/2013/03/11/the-pull-request-hack.html)என்று @felixge கண்டறிந்தார், மேலும் அவர் சமீபத்தில் வேலை செய்யாத திட்டங்களில் கூட புதிய பராமரிப்பாளர்களைக் கண்டார். @@ -176,7 +176,7 @@ related:
பணியை அனுபவிக்கும் பங்களிப்பாளர்களைப் பணியமர்த்துதல் மற்றும் நீங்கள் இல்லாத காரியங்களைச் செய்யக்கூடியவர்கள் யார் என்பதில் \[இது உங்கள் சிறந்த ஆர்வத்தில் உள்ளது\]. நீங்கள் குறியீடு எழுதுவதை அனுபவிக்கிறீர்களா, ஆனால் சிக்கல்களுக்கு பதிலளிப்பதில்லையா? பின்னர் உங்கள் சமூகத்தில் அந்த நபர்களை அடையாளம் காணுங்கள், அவர்கள் அதைச் செய்யட்டும்.
-— @gr2m, ["வரவேற்பு சமூகங்கள்"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["வரவேற்பு சமூகங்கள்"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/ta/finding-users.md b/_articles/ta/finding-users.md index e58820e1e1e..3cb8f6c6b65 100644 --- a/_articles/ta/finding-users.md +++ b/_articles/ta/finding-users.md @@ -109,7 +109,7 @@ related:
உங்கள் உரையைத் தொடங்கும்போது, உங்கள் தலைப்பு என்னவாக இருந்தாலும் சரி, உங்கள் உரையை ஒரு கதையாக நீங்கள் பார்த்தால், அதை மக்களுக்குக் கூறும்பொழுது உதவும்.
-— லேனா ரெய்ன்ஹார்ட், ["ஒரு தொழில்நுட்ப மாநாடு பேச்சு தயாரித்தல் மற்றும் எழுதவது எப்படி"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— லேனா ரெய்ன்ஹார்ட், ["ஒரு தொழில்நுட்ப மாநாடு பேச்சு தயாரித்தல் மற்றும் எழுதவது எப்படி"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/tr/building-community.md b/_articles/tr/building-community.md index db9461e5b0e..dcac157c6ce 100644 --- a/_articles/tr/building-community.md +++ b/_articles/tr/building-community.md @@ -163,7 +163,7 @@ Mülkiyetinizi topluluğunuzla mümkün olduğunca paylaşmanın yollarını bul * Projenizde, projenize katkıda bulunan herkesi listeleyen **bir CONTRIBUTORS veya AUTHORS dosyası başlatın**,[Sinatra'nın](https://github.com/sinatra/sinatra/blob/HEAD/AUTHORS.md) yaptığı gibi. -* Oldukça büyük bir topluluğunuz varsa, **bülten gönderin veya katkıda bulunanlara teşekkür eden bir blog yazısı yazın**. Rust'ın [Rust'ta Bu Hafta](https://this-week-in-rust.org/) ve Hoodie'nin [Shoutouts](http://hood.ie/blog/shoutouts-week-24.html) bültenleri iki güzel örnek. +* Oldukça büyük bir topluluğunuz varsa, **bülten gönderin veya katkıda bulunanlara teşekkür eden bir blog yazısı yazın**. Rust'ın [Rust'ta Bu Hafta](https://this-week-in-rust.org/) ve Hoodie'nin [Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html) bültenleri iki güzel örnek. * **Her katkıda bulunana commit izni verin.** @felixge, bunun insanları [yamalarını geliştirme konusunda daha heyecanlı](https://felixge.de/2013/03/11/the-pull-request-hack.html) hale getirdiğini buldu ve bir süredir üzerinde çalışamadığı projeler için yeni geliştiriciler buldu. @@ -177,7 +177,7 @@ Gerçek şu ki çoğu projede işlerin çoğunu yapan [yalnızca](https://peerj.
\[Sizin için\] yapamadığınız şeyleri yapma yeteneğine sahip olan ve zevk alan katılımcıları işe almak en iyisidir. Kodlamayı seviyor musunuz, ancak soruları yanıtlamıyor musunuz? Topluluğunuzdaki bireylerin bunu yapmasına izin verin.
-— @gr2m, ["Toplulukları Karşılama"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["Toplulukları Karşılama"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/tr/finding-users.md b/_articles/tr/finding-users.md index e57ec3d59ce..a2bcd9067c3 100644 --- a/_articles/tr/finding-users.md +++ b/_articles/tr/finding-users.md @@ -109,7 +109,7 @@ Konuşmanızı yazarken, izleyicilerinizin ilginç bulacağı ve değer kazanaca
Konuşmanızı yazmaya başladığınızda, konunuz ne olursa olsun, konuşmanızı insanlara anlattığınız bir hikaye olarak görmeniz yararlı olabilir.
-- Lena Reinhard, ["Teknik Konferans Konuşması Nasıl Hazırlanır ve Yazılır"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +- Lena Reinhard, ["Teknik Konferans Konuşması Nasıl Hazırlanır ve Yazılır"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/zh-hans/building-community.md b/_articles/zh-hans/building-community.md index 67504dafbb1..e7701de6cc0 100644 --- a/_articles/zh-hans/building-community.md +++ b/_articles/zh-hans/building-community.md @@ -166,7 +166,7 @@ redirect_from: /zh-cn/building-community/ * **在项目中添加一个贡献者文件(CONTRIBUTORS) 或者作者文件(AUTHORS)** 用于记录每一个参与贡献的人。 -* 如果社区有了一定的规模，那么 **发送一封信或者发表一篇博客** 感谢贡献者们。Rust的[Rust周报](https://this-week-in-rust.org/)和Hoodie的[Shoutouts](http://hood.ie/blog/shoutouts-week-24.html)就是两个非常好的范例。 +* 如果社区有了一定的规模，那么 **发送一封信或者发表一篇博客** 感谢贡献者们。Rust的[Rust周报](https://this-week-in-rust.org/)和Hoodie的[Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html)就是两个非常好的范例。 * **给每个贡献者提交的通道。**@felixge发现这样会使大家[越发乐意斟酌他们的补丁](https://felixge.de/2013/03/11/the-pull-request-hack.html)，以及他甚至发现，在他没有工作的一段时间，项目依然有新的维护者进来。 @@ -180,7 +180,7 @@ redirect_from: /zh-cn/building-community/
你们最大的兴趣是招募喜欢你们项目以及能够做你们不能做的事的贡献者。你喜欢编码，但不喜欢回答issues？那么让社区中能做这件事的人去做。
-— @gr2m, ["打造受欢迎的社区"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["打造受欢迎的社区"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/zh-hans/finding-users.md b/_articles/zh-hans/finding-users.md index f4557de3864..dc421f0f02b 100644 --- a/_articles/zh-hans/finding-users.md +++ b/_articles/zh-hans/finding-users.md @@ -110,7 +110,7 @@ redirect_from: /zh-cn/finding-users/
你写演讲稿的时候，不管你的主题是什么，如果你能把你的演讲当成是给别人讲故事的话，效果会更好。
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)
diff --git a/_articles/zh-hant/building-community.md b/_articles/zh-hant/building-community.md index 90c5937a31a..c45c3b24eb8 100644 --- a/_articles/zh-hant/building-community.md +++ b/_articles/zh-hant/building-community.md @@ -164,7 +164,7 @@ redirect_from: /zh-tw/building-community/ * **在專案中添加一個貢獻者列表或者作者列表** 記錄每一個參與貢獻的人。 -* 如果社群有了一定的規模，就 **發送一封信或者發表一篇文章** 感謝貢獻者們。[Rust 週報](https://this-week-in-rust.org/)和 Hoodie 的[Shoutouts](http://hood.ie/blog/shoutouts-week-24.html)就是兩個非常好的範例。 +* 如果社群有了一定的規模，就 **發送一封信或者發表一篇文章** 感謝貢獻者們。[Rust 週報](https://this-week-in-rust.org/)和 Hoodie 的[Shoutouts](https://web.archive.org/web/20160516163538/http://hood.ie/blog/shoutouts-week-24.html)就是兩個非常好的範例。 * **給每個貢獻者提交的權限。**@發現這樣會使大家[越來越樂意發表他們的補丁](https://felixge.de/2013/03/11/the-pull-request-hack.html)，甚至找到人手來協助維護他已很久沒處理的專案。 @@ -178,7 +178,7 @@ redirect_from: /zh-tw/building-community/
對社群最有利的做法是招募喜歡你們專案的人，而且這個人還能夠做你們做不到的事情。你是否喜歡寫程式，但不喜歡回覆 issue ？ 那就讓社群裡能做這件事的人去做。
-— @gr2m, ["打造溫暖的社群"](http://hood.ie/blog/welcoming-communities.html) +— @gr2m, ["打造溫暖的社群"](https://web.archive.org/web/20160516130845/http://hood.ie/blog/welcoming-communities.html)
diff --git a/_articles/zh-hant/finding-users.md b/_articles/zh-hant/finding-users.md index 9627eb3cf42..ec4439d6882 100644 --- a/_articles/zh-hant/finding-users.md +++ b/_articles/zh-hant/finding-users.md @@ -110,7 +110,7 @@ redirect_from: /zh-tw/finding-users/
當你開始寫你的演講稿的時候，不管你的主題是什麼，如果你能把你的演講當成是給別人講故事的話，效果會更更好。
-— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/) +— Lena Reinhard, ["How to Prepare and Write a Tech Conference Talk"](https://web.archive.org/web/20201128162836/http://wunder.schoenaberselten.com/2016/02/16/how-to-prepare-and-write-a-tech-conference-talk/)