Contributor's guidelines for Yuzu Browser.
Repository
https://github.com/hazuki0x0/YuzuBrowser
Linked Task Request
There was no task request made for this contribution. I offered to create some documents for the project and the project owner obliged. This request was made via a public issue on Github. That proposal was the creation of a privacy policy. After I was done creating the policy statement, I offered to create a contributor's guidelines since I said something about that in the privacy policy statement. The developer obliged, and opened an issue for it
Overview
Yuzu browser is an amazing software. I can't overemphasize how amazing it is right now. But there's a slight issue. The developer has keenly been maintaining the project. On the project's repository on Github, you will find that the developer has released 99 versions of the app. All the updates in those releases were mostly done by him. Every new thing that has been done on the app, was done by him. But, it shouldn't be so.
Aside from making source codes open and free, collaborative development is another component of an open source concept. Unfortunately, that has not been the case with this project. I don't know the reason though. But, it'd be great to see open source contributors get on the project and advance it further. Currently, there are only 5 contributors to the project. That is; me, the project owner, and some other persons.
I had to find a way to get people contributing and opted to create a "contributor's guidelines" for the project. Hopefully, this would spur people to contribute to the project, and show them the way to do so.
Actual content
As I earlier stated in the overview, I engaged in creating a contributor's guide for the project. The contributor's guide was concise and detailed. I highlighted how prospective contributors can get started with my making their contributions. Whatever they decided to contribute.
- Here's the link to the contributor's guide
Additional information
I sent the pull request for this content almost immediately as I was done with the privacy policy I had earlier created. However, it took quite some time for the developer to merge it. The content has now been merged.
Here's the link to the merged pull request
Hello, @harry-heightz. Good to see that you are actively contributing to the copywriting category. I appreciate your work, and I am looking forward to seeing more contribution from you. Well done.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Chat with us on Discord.
[utopian-moderator]
Thank you for your review, @knowledges! Keep up the good work!
Hey, @harry-heightz!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!
Hi, @harry-heightz!
You just got a 10.71% upvote from SteemPlus!
To get higher upvotes, earn more SteemPlus Points (SPP). On your Steemit wallet, check your SPP balance and click on "How to earn SPP?" to find out all the ways to earn.
If you're not using SteemPlus yet, please check our last posts in here to see the many ways in which SteemPlus can improve your Steem experience on Steemit and Busy.
Hi @harry-heightz!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server