After months or years of hard work, you push your open source project to GitHub and notifies it. Now it’s time to tell the world about it.
The moments you want to spend time writing code rather than getting the word in your project. Perhaps your project goes to viral and you don’t have to spend a lot of time selling. But the chance you need to do some jobs to build awareness, at least for the first few days. Fortunately, there are many people who have fallen on this road and are ready to help. In this article, the experienced constorters offer their advice to share open projects in the world’s origin.
Start clearly. Post on social media about your project. Submit it to Hacker News, Reddit, Product Effects, and same sites. Then keep an eye on peeled for people with the problem you solve. Answer their posts and let them know you have a potential solution. Reaching Podcasts and YouTube Channels. Submit talks to conferences. Offer to tell meetings.
Continue to highlight your work as you promote the project. Remember that people want to hear about helpful tools to solve real problems, as long as you are sure to help, and not just your followers. You may not be comfortable with self-promotion, but you need to improve your job to get it there. “You should not feel Icky about it,” Sidsehan rEASON Aaron Francis Told us a Q & A. “You put a lot of time making something helpful.”
Focus on the problem that your project is solved
What do you say when you support your work? First and most important, you need to know what’s the problem with your project to solve and can talk to potential users as possible. “One of the biggest mistakes I’ve seen is use more technical terminology,” as Chakra UI rEASON Coming with Albayo. It can be tempting to talk about the technologies you have built your solution, or the most recent buzzwords you think that users can be interested. But it’s easy to go to the sea and can’t cover the project value.
For example, your project can make wise use of descentralized computing principles, focus Tasha DrewCo-chaird for Kubneretes work group for multi-cancy, but what people think of why they should use it. “What message do you want people to take from your webpage or your reading? It may not be related to theory behind the code,” he said.
Use that message within anywhere: social media posts and profile, blog posts, tutorials, etc.
Documents, documents, documents!
Getting one’s attention is just a part of the war. If you want people to actually apply, share, and contribute to your project, you need clear, up-to-date documentation. “Write as much as you can stand to write,” Francis said. It doesn’t just make your experience better experience, can still improve your code. “If you find it difficult to link to a particular side, maybe a sign that it is very complicated and you need to simply apply it,” he explained.
Think more document code. You need to give things like easy starting, tutorials, and screencasts. “The video is really helpful for many people,” says Adebayo. “People learn different ways so it is important to give different types of content.”
May respond
It doesn’t matter how good your documentation is, people have more questions – and, if you are lucky, asking requests. It is important to be responding, especially if you just started. “The time end, we only get a life, also appreciated people who are willing to spend some of their precious resources to you,” Francis said. “That is not available to people who send requests to pull, but to people who focus on problems or also make suggestions on social media.”
That doesn’t mean you should call 24/7 to give an easy answer to each other’s question and comment. But it means you don’t allow pull, issue, and comments sit without answer. You need people to inform your project active, and you appreciate their input. “It’s afraid to get along with the people you don’t know, but you have to do it if you want to grow,” Adebayo said. “It’s a sure way to meet new people and make new friends who can help you in the future.”
Invest in time with onboarding contributions
You need to document both how your project is used, and how to contribute to it. Create atrivicting.md and code_of_conduct.md file with instructions in your contribution and code code. Allow these potential contributors who know you are open to contributions and you think others are with others. This is more helpful to give a list of what you want, and not, like potential contributions to.
Remember that No Code ContributionsAs with documentation, support, and graphic design, a large portion of any successful project. While it is not necessary not technical, you should not think of many technical knowledge. “You want to do your language and projects easily understood so that people at different technical skill levels can be interested,” said Drew.
Also make sure to exploit “Help Prefer” and “good first issue” labels. It helps people seek ways to contribute to finding your project.
dash contributed to open source now
Written to
https://github.blog/wp-content/uploads/2024/04/1200.630-Community-wLogo.png?fit=1200%2C630
2025-02-06 20:00:00
