Think Technically
Our Approach and how we use our mind determine the kind of ideas we share on our favorite open source projects. Thinking technically enable extensive thinking, which will define the quality of any idea shared.
I have much love for the open source world because of the flexibility and transparency. I want to encourage more people to switch to using open source projects.
As always, Utopian is one of the great supporters of open source projects in a variety of ways: Project development, creating graphical contents, visibility to the world, suggestions, translations, copywriting, analysis, bug hunting, tutorials, video tutorials, blogs, and documentation. what else do we need to promote the open source world, that Utopian has not provided?
Switch to using open source projects
Open source projects are known for being friendly. I have been using different open source projects, and I find them more flexible, useful, and appealing to use over some closed-source applications.
Open source projects allow easy interaction between users and projects owners.
The open source world is growing every day, like a moving ship (Projects) of low density on a sea of great upthrust (Contributors).
Join this kind of ship, or become a contributor to open source project to improve all of your favorite open source projects.
Utopian is here to incentivize open source project users and projects owners in dynamic ways.
Read on
There are numerous benefits to using open source project. However, I will focus on some that are related to suggestions.
The GitHub issues feature allow fast interaction between project owners and users by allowing users to easily submit their requests.
If you're using an application and wish to see some intriguing features that will make the app more appealing, open source has your back. Feature requests enable direct contact with projects owners via the project repository. And these days you have the added advantage of submitting those requests through Utopian.
The open source world is a place that allows for collaborative building of a project irrespective of location, time and language. Everyone is imperative in the open source world, and I think that is a huge reason to join.
Become a better open source idea contributor
Contributing to open source projects through Utopian is not complex, but it is technical. Everyone starts somewhere, and you may be an existing or prospective contributor to open source projects. In either case, this should be helpful to you.
Sharing ideas for open source projects may seem to be less prestigious, as folks with coding skills are the main reason we can all use any application. However, You can improve any project by sharing ideas that will get the attention of the developers. all you need is proper understanding of Utopian's policies and guidelines.
First, Read and assimilate Utopian Policies and Guidelines for a better understanding of how to contribute. Proceed to the Suggestion category guidelines.
I will now be elaborate on the guidelines.
Suggestions are technical feature/enhancements that are of significant potential added-value to an Open Source project.
This means that any feature or section improvement you wish to see in open source projects must be related to adding code and must have a tangible value to the project.
Suggestions should not be related to processes and or organizational issues.
ideas that are related to how open source projects should be managed by the project owner or team will not be considered.
E.g. A suggestion to remove ads from an application, or suggestions that do not have direct impact on the project code.
Images, charts, screenshots, links, references and examples should be included when applicable.
The suggestion should include graphical representation of the idea for better understanding, as they say:
a picture is worth a thousand words.
Suggestions should be original, unique and uncommon among similar or competing apps.
As mentioned in my previous post, the idea you wish to share should be original.
Submissions should include extensive details and (when possible) instructions for the suggested feature to be actualized.
Make your idea realistic. Provide adequate information and any explanations needed, as well as how you believe the idea could be implemented.
The title of the submission post should include the project's name, and a short but informative description of the suggestion described in the post.
The title should be informative enough to understand what you are proposing.
e.g Improvement by adding more detailing functions to actifit
These are the basics one needs to understand the guidelines. If you take note of this, you should be able to share better ideas on your favorite open source projects through Utopian.
Be professional and responsible
Be professional in each of your approaches, your interactions with Utopian moderators and project owners should be done professionally.
I have seen some contributors trying to force project owners to like their suggestion. They end up in a chat fight, which is absolutely wrong.
After you draft and submit your suggestion to Utopian, copy a brief part of the suggestion. Exclude the long details about the project.
Copy your proposal, mockups, and benefits. Then, submit to the Github issues page for the project owner to see your proposal. Wait for the project owner's response. Whether it is positive or negative, be professional.
Conclusion
We, at the Utopian Suggestions category, want more thinkers to come aboard and share ideas on open source projects. We want you to join the dazzling, collaborative, open source world and enjoy all of its benefits.
You can comment your questions if you have any. Or, even better, join thousands of people in Utopian's discord server and get involved.
Series
https://steemit.com/utopian-io/@tykee/tips-for-idea-category-contributors-on-utopian