Skip to content

Commit

Permalink
finished up code-of-conduct.md and created finding-users.md and wrote…
Browse files Browse the repository at this point in the history
… in it
  • Loading branch information
LizzyOrji123 committed Oct 24, 2023
1 parent 5adac19 commit 05644cf
Show file tree
Hide file tree
Showing 2 changed files with 202 additions and 2 deletions.
60 changes: 58 additions & 2 deletions _articles/pidgin/code-of-conduct.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,14 @@ The [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Ci

Put one CODE_OF_CONDUCT file for your project's main directory, and make sure say your community fit see am by linking am for your CONTRIBUTING or README file.

## How to enforce your code of conduct
## How you go take think your code of conduct to stand gidi gba

<aside markdown="1" class="pquote">
Code of conduct wey dem nor dey enforce, or wey dem nor fit enforce, e bad pass if dem nor get any code of conduct: e show say the values wey dey the code of conduct nor dey important or dem nor dey respected for your community.
<p markdown="1" class="pquote-credit">
[Ada Initiative](https://webcache.googleusercontent.com/search?q=cache:YfqdTk5H9ikJ:https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community)
</p>
</aside>

You suppose explain how you go enforce your code of conduct **_before_** person violate am. Some reasons why you suppose do am be say:

Expand All @@ -53,6 +60,55 @@ No forget say person fit wan report violation about person wey dey receive those
For inspiration, check out Django's [enforcement manual](https://www.djangoproject.com/conduct/enforcement-manual/) (though you may not need something this comprehensive, depending on the size of your project).

## How to enforce your code of conduct
## How your code of conduct go take stand gidi gba

Sometimes, despite your best efforts, somebody go do something wey dey violate this code. There are several ways to address negative or harmful behavior when it comes up.

### Gather plenty gist about the mata

Arrange community member voice make aeh dey important as your own dey. If person report say somebody violate the code of conduct, take am seriously and investigate the matter, even if e nor match your own experience with that person. As you do like this, you dey show your community say you value their perspective and trust their judgment.

The community member wey dey involved fit be person wey dey always cause trouble and dey make other people dey uncomfortable, or e fit be say e talk or do something just once. You fit take action based on the situation.

Before you yarn, give yourself time to understand wetin happen. Read the person's past comments and conversations make you sabi who e be and why e fit do something like that. Try gather different perspectives from other people about the person and the way e take behave.

<aside markdown="1" class="pquote">
No let yourself enter argument. No allow yourself sidetrack, dey address another person's behavior before you don finish with the main matter. Just focus on wetin you need.
<p markdown="1" class="pquote-credit">
— Stephanie Zvan, ["So You've Got Yourself a Policy. Now What?"](https://the-orbit.net/almostdiamonds/2014/04/10/so-youve-got-yourself-a-policy-now-what/)
</p>
</aside>

### Carry action waeh make sense

After you don gather and process enough information, you go need to decide wetin you go do. As you dey consider your next steps, remember say your goal as a moderator na to promote safe, respectful, and collaborative environment. Consider how you go take handle the matter and how your response fit affect the way other community members go take dey behave and their expectations for future.

If person report say somebody violate the code of conduct, e na you suppose handle am, not the person wey report. Sometimes, the person wey report dey risk plenty things like e career, reputation, or physical safety. Forcing am to confront the person wey dey harass am fit put am for wahala. You suppose dey communicate directly with the person wey dey involved, except the person wey report request something different.

You fit respond to code of conduct violation for different ways:

- **Warn the person wey dey involved publicly** and explain how their behavior affect others, preferably for the place where e happen. If possible, public communication go show the rest of the community say you dey serious about the code of conduct. Make you dey kind but firm for your communication.

- **Privately reach out to the person** wey dey involved to explain how their behavior affect others. You fit use private communication channel if the situation get sensitive personal information. If you communicate privately with person, e good make you CC those wey first report the situation, so dem go know say you don take action. Ask the person wey report make e agree before you CC am.

Sometimes, you fit no fit resolve the matter. The person wey dey involved fit dey aggressive or hostile when you confront am, or e no fit change their behavior. For this kind situation, you fit consider stronger action. For example:

- **Suspend the person** wey dey involved for the project, you go enforce am through temporary ban wey go stop am from participating for any aspect of the project.

- **Permanently ban** the person from the project.

Make you no take banning members lightly, e be like say e be something wey no fit change and no fit reconcile different perspectives. You suppose only take these measures if e clear say you no fit resolve the matter.

## The work waeh you fit do as a maintainer

Code of conduct nor be law wey dem just dey put as dem like. Na you be the enforcer of the code of conduct and e dey your responsibility to follow the rules wey the code of conduct don establish.

As a maintainer, na you set the guidelines for your community and you go enforce those guidelines based on the rules wey dey your code of conduct. This one mean say, any report wey you receive about code of conduct violation, you suppose take am serious. The person wey report the matter suppose get thorough and fair review of wetin dem complain. If you come find out say the behavior wey dem report nor be violation, make you yan that one give dem straight and explain why you nor go take action on top am. As dem see that one, na them sabi how dem go fit take the behavior wey dem dey complain tolerate, or dem fit stop to dey participate for the community.

If person report behavior wey nor _technically_ violate the code of conduct, e fit still show say there be problem for your community, and you suppose investigate this potential problem and take action as e dey necessary. This one fit include say you go revise your code of conduct to make am clear the kind behavior wey dem go accept, or make you talk to the person wey dem report say e dey skirt the edge of wetin dem expect and e dey make some participants dey uncomfortable, although e nor violate the code of conduct.

In the end, as a maintainer, na you dey set and enforce the standards for acceptable behavior. You get the power to shape the community values of the project, and participants dey expect make you enforce those values in a way wey dey fair and even-handed.

## Encourage the character wey you want make people see for this world 🌎

When person see say one project nor dey friendly or e nor dey welcoming, even if e just one person behavior people still dey tolerate, e fit make plenty contributors run comot, some of dem wey you never go fit even see. E nor dey always easy to adopt or enforce code of conduct, but if you dey promote environment wey dey welcoming, e go help your community grow.
144 changes: 144 additions & 0 deletions _articles/pidgin/finding-users.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,144 @@
---
lang: pidgin
title: How to find the people to helep your project
description: You go helep your open source project grow if you bin put am with people waeh dey happy happy.
class: finding
order: 3
image: /assets/images/cards/finding.png
related:
- beginners
- building
---

## Dey talk the koko

Dem nor get law wey talk say you suppose promote open source project when you first launch am. Plenty reasons dey wey fit make person dey work for open source wey nor get to do with popularity. Instead make you hope say other people go find and use your open source project, you suppose spread the word about your hard work!

## Make you dey find your message

Before you start the real work of promotion for your project, you suppose sabi explain wetin your project dey do, and why e dey important.

Wetin make your project different or interesting? Why you create am? As you dey think about your project's message and value, try look am through the eyes of the people wey fit use am and those wey fit contribute to am.

For example, @robb dey use code examples to yan clearly why him project, [Cartography](https://github.com/robb/Cartography), dey useful:

![Cartography README](/assets/images/finding-users/cartography.jpg)

If you wan go deeper for messaging, check Mozilla's ["Personas and Pathways"](https://mozillascience.github.io/working-open-workshop/personas_pathways/) exercise for developing user personas.

## Helep people to dey find and folow your project

<aside markdown="1" class="pquote">
Ideally, you suppose get one "home" URL wey you go fit promote and direct people to for your project. You nor need spend plenty money for fine design or even buy domain name, but your project suppose get one main place where people fit find am.
<p markdown="1" class="pquote-credit">
— Peter Cooper & Robert Nyman, ["How to Spread the Word About Your Code"](https://hacks.mozilla.org/2013/05/how-to-spread-the-word-about-your-code/)
</p>
</aside>

**Make you get clear handle to promote your work.** Twitter handle, GitHub URL, or IRC channel na easy way wey you fit use point people to your project. These outlets still dey give your project's growing community place wey dem go fit gather.

If you nor wan set up outlets for your project now, make you dey promote your own Twitter or GitHub handle for everything wey you dey do. Promoting your Twitter or GitHub handle go show people how dem fit take contact you or follow your work. If you go talk for meeting or event, make you sure say your contact information dey for your bio or slides.

<aside markdown="1" class="pquote">
<img src="https://avatars.githubusercontent.com/nathanmarz?s=180" class="pquote-avatar" alt="avatar">
One mistake wey I make for those early days... no be say I start Twitter account for the project. Twitter na better way to dey give people updates about the project and dey always show people the project.
<p markdown="1" class="pquote-credit">
@nathanmarz, ["History of Apache Storm and Lessons Learned"](http://nathanmarz.com/blog/history-of-apache-storm-and-lessons-learned.html)
</p>
</aside>

**Make you think about create website for your project.** Website dey make your project dey friendly and easy to navigate, especially when you combine am with clear documentation and tutorials. Having website still show say your project dey active and e go make your audience feel comfortable say dem fit use am. Give examples to show people as dem fit take use your project.

[@adrianholovaty](https://news.ycombinator.com/item?id=7531689), co-creator of Django, talk say website na _"by far the best thing we did with Django in the early days"_.

If your project dey for GitHub, you fit use [GitHub Pages](https://pages.github.com/) create website. [Yeoman](http://yeoman.io/), [Vagrant](https://www.vagrantup.com/), and [Middleman](https://middlemanapp.com/) na [few examples](https://github.com/showcases/github-pages-examples) of excellent, comprehensive websites.

![Vagrant homepage](/assets/images/finding-users/vagrant_homepage.png)

Now wey you don get message for your project and easy way wey people fit take find your project, make you waka comot go yan with your audience!

## Go where your project's audience dey (online)

Online outreach na correct way wey you fit take share and spread the word quickly. As you use online channels, e fit help you reach wide audience.

Make you use existing online communities and platforms to reach your audience. If your open source project na software project, e possible say you fit find your audience for [Stack Overflow](https://stackoverflow.com/), [Reddit](https://www.reddit.com), [Hacker News](https://news.ycombinator.com/), or [Quora](https://www.quora.com/). Find the channels wey you believe say people go benefit well or go dey excited about your work.

<aside markdown="1" class="pquote">
<img src="https://avatars.githubusercontent.com/pazdera?s=180" class="pquote-avatar" alt="avatar">
Each program get specific functions wey only small number of users go find useful. Nor go dey disturb plenty people as you fit. Instead, focus your efforts on communities wey go gain from knowing about your project.
<p markdown="1" class="pquote-credit">
@pazdera, ["Marketing for open source projects"](https://radek.io/2015/09/28/marketing-for-open-source-projects-3/)
</p>
</aside>

See as you fit find ways to share your project well:

* **Know the relevant open source projects and communities.** Sometimes, you nor need promote your project directly. If your project dey perfect for data scientists wey dey use Python, make you sabi the Python data science community. As people sabi you, opportunities go naturally show face to talk about and share your work.
* **Find people wey dey face the problem wey your project solve.** Search through forums wey relate to your project's target audience, and try to answer their questions. If e dey right, find polite way to suggest your project as solution.
* **Ask for feedback.** Introduce yourself and your work to audience wey your project fit benefit. Make you specific about the people wey you think say your project go fit help. Try to complete the sentence: _"I think my project go really help X, people wey dey try do Y_". Listen and respond to others' feedback, rather than just promoting your work.

Generally, focus on helping others before you ask for something in return. Because anybody fit easily promote project online, e go get plenty noise. To stand out from the crowd, give people background about who you be, nor be just wetin you want.

If nobody pay attention or respond to your initial outreach, nor let am discourage you! Most project launches nor dey one-time thing, e fit take months or years. If you nor get response the first time, try different method, or look for ways to add value to other people's work first. Promotion and launch of your project go take time and dedication.

## Waka go where your project's audience dey (offline)

![Public speaking](/assets/images/finding-users/public_speaking.jpg)

Offline events dey very popular to promote new projects to people. Dem be very good way to reach audience wey dey engage and build better human connections, especially if you wan reach developers.

If you be [newbie for public speaking](https://speaking.io/), you fit start by dey find local meetup wey relate to the language or system wey your project dey based on.

<aside markdown="1" class="pquote">
<img src="https://avatars.githubusercontent.com/jhamrick?s=180" class="pquote-avatar" alt="avatar">
I bin dey very nervous about PyCon. I bin wan give talk, I only know few people wey dey there, I bin wan dey there for one whole week. (...) But I no suppose dey worry, PyCon bin sweet die! (...) Everybody bin friendly and I rarely get time wey I no dey talk with people!
<p markdown="1" class="pquote-credit">
@jhamrick, ["How I learned to Stop Worrying and Love PyCon"](http://www.jesshamrick.com/2014/04/18/how-i-learned-to-stop-worrying-and-love-pycon/)
</p>
</aside>

If you never talk for event before, e dey normal to feel nervous! Just remember say the people wey dey the audience dey there because dem really wan hear wetin you wan talk about.

As you dey write your talk, try focus on the things wey your audience go find interesting and get value from. Make your language dey friendly and approachable. Smile, breathe well, and enjoy yourself.

<aside markdown="1" class="pquote">
<img src="/assets/images/finding-users/lena.jpg" class="pquote-avatar" alt="avatar">
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.
<p markdown="1" class="pquote-credit">
— 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/)
</p>
</aside>

When you feel say you don ready, try consider talk for conference to promote your project. Conferences fit help you reach plenty people, sometimes from different parts of the world.

Find conferences wey relate to the language or system wey your project dey use. Before you submit your talk, try do research about the conference so that you fit arrange your talk to match the people wey go attend and increase your chance to talk for the conference. Sometimes you fit know the kind of audience wey you wan get by checking the people wey don talk for the conference before.

<aside markdown="1" class="pquote">
<img src="https://avatars.githubusercontent.com/ry?s=180" class="pquote-avatar" alt= "avatar">
I write polite message to the JSConf people beg them make dem give me small chance make I fit talk for JSConf EU. (...) I bin very scared, I wan present the thing wey I don work on for six months. (...) All the time I bin dey think, oh my God. Wetin I dey do here?
<p markdown="1" class="pquote-credit">
@ry, ["History of Node.js" (video)](https://www.youtube.com/watch?v=SAc0vQCC6UQ&t=24m57s)
</p>
</aside>

## Kulekule your reputation

Apart from the strategies wey we don yarn before, the best way to invite people to share and contribute to your project na to share and contribute to their projects.

To help newcomers, share resources, and make thoughtful contributions to other people's projects go help you build positive reputation. To be an active member for open source community go help people to understand wetin you dey do, and dem fit dey pay attention to and share your project. To dey develop relationships with other open source projects fit even lead to official partnerships.

<aside markdown="1" class="pquote">
<img src="https://avatars.githubusercontent.com/shazow?s=180" class="pquote-avatar" alt="avatar">
The only reason urllib3 is the most popular third-party Python library today is because it's part of requests.
<p markdown="1" class="pquote-credit">
@shazow, ["How to make your open source project thrive"](https://about.sourcegraph.com/blog/how-to-make-your-open-source-project-thrive-with-andrey-petrov/)
</p>
</aside>

E no dey too early or too late to begin build your reputation. Even if you don launch your own project before, dey always look for ways to help others.

No get quick fix wey go give you audience. To gain the trust and respect of others dey take time, and building your reputation no dey end.

## No relent!

E fit tey before people go notice your open source project. E dey okay! Some of the most popular projects wey dey today, e take years before dem reach the level wey dem dey now. Focus on building relationships instead of dey hope say your project go just blow. Be patient, and continue to dey share your work with those wey dey appreciate am.

0 comments on commit 05644cf

Please sign in to comment.