Suggestion Rules

• Suggestions are minor features/enhancements that you would like to have in an Open Source project.
• Suggestions may be only related to the technical aspects of the project not process or organisational issues.
• Suggestions must provide all the details for the requested features to be actually built.
• Images, screenshots, links and examples are always welcome in this category.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Development Rules

• Only merged Pull Requests will be accepted.
• Only merged Pull Requests on the official repository will be accepted or on a fork as long as the fork is not just a mirror of the original one.
• The contribution will be rejected if the merged Pull Request is older than 7 dayssince the submitted contribution.
• Simple and common code snippets that can be easily found or reproduced can't be submitted in the development category.
• You must always link the merged pull requests with the given functionality in the editor.
• If your username on Github does not correspond to the Utopian username you must use the "Name" field in the Github settings and enter there your Utopian/Steem username to verify you are the author.
• Images, screenshots, links and examples are not necessary but preferred.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Bug Hunting Rules

• In this category you can only report bugs you have found in an Open Source project.
• You must provide every possible detail to reproduce the bug.
• You should show a video or an animated GIF if the bug can be recorded on screen.
• You must include: browsers, devices, operating systems used and similar info to reproduce the bug.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Translations Rules

• This category is meant only for translations you have updated or created for an Open Source project.
• Minimum 1000 words per translation contribution. Text that is supposed to remain untranslated (links, code, paths, ...) or duplicated strings/text can't be included in the minimum amount of words.
• Proofread or merged translations are always preferred. Submitting translations that are not proofread will lead to a lower vote.
• You could translate less than the minimum amount of words if the project itself has less to be translated in total. May lead to a lower vote.
• The contribution will be rejected if the submitted translation is older than 7 days since the submitted contribution. This rule does not apply for proofread translations.
• If it is obvious that you can't properly write in the source language of the translation, your contribution will be rejected.
• Only translations on CrowdIn or Github are accepted. You should not translate the words and provide them in your Utopian post directly.
• Your Github Account or Crowdin Account must match your Steem/Utopian account. If it does not you must use the field "Full Name" in Crowdin to show you are the author.
• You must include every possible detail to check the translations and the tools you have used to translate.
• Entire translations are always preferred. If you are writing about a partial translation we reserve the right to evaluate the actual work.
• Same translations from different authors will be accepted if the moderator can recognise the newest translation has better quality.
• If the provided translation is obviously machine-translated for more than its 20% or has low quality will be rejected.
• Proof-reading is not acceptable in Utopian as a valid contribution.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Graphics Rules

• This category is meant only for graphics/videos/motion graphics you have realised for an Open Source project.
• Use of templates is prohibited, the contribution must be direct result of your own work.
• T-shirts and merchandising in general are not valid contributions in Utopian.
• You must provide a link or credit to all assets you have used in your contribution and make sure you have permission to use them for commercial use. including: images, videos, fonts, 3D models, etc.
• You must provide samples of your creations directly on this post and include public links to the full design.
• You must include every possible detail to verify the work done.
• If you are spontaneously contributing by enhancing an existing design, you must provide all the details to compare your work with the existing one and the reasons/benefits why your work should be accepted.
• You must provide the editable files, as .Svg .Eps .Pdf ( .Ai .Psd .Cdr. ) . Flatten and rasterized layers are not editable.
• You should also provide the different variations in terms of sizes, colors and applications of your graphic design.
• Designs are preferred to be in a vector format unless the project owner specifies a different format.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Analysis Rules

• This category is meant only for providing a data analysis you have generated for an Open Source project.
• You must include the results of your analyses and the reasons why you have generated them.
• You should include example scripts which generated the results for your analysis, if applicable, or any information on how the data was generated.
• Recurring analyses that are obviously script generated will lead to a lower vote.
• If you are not pasting the entire analysis here you must provide public links to it.
• Results of the analyses, in the form of charts or tables are mandatory in this category.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Visibility Rules

• This category is meant only for providing results of online social engagement, ads and similar for an Open Source project.
• Promotions done on chats (e.g. Whatsapp, Telegram and similar) won't be accepted as valid contributions.
• Only ads on Search engines, Social media platforms, Thunderclap campaigns, posts on social media accounts with at least 10000 followers / potential audience will be accepted as valid contributions.
• You must have reached at least an audience of 1000 people.
• You must include links and proofs of the visibility effort you made and write down the results.
• You must provide a clear way to recognise you are the author of the social effort, by matching your Steem/Utopian account with the one on the social platforms or by using any other field to immediately verify that.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Documentation Rules

• Only merged Pull Requests on the official repository will be accepted or on a fork as long as the fork is not just a mirror of the original one.
• This category is meant only when working on the Official documentation of an Open Source project.
• If your username on Github does not correspond to the Utopian username you must use the "Name" field in the Github settings and enter there your Utopian/Steem username to verify you are the author.
• Documentation category is meant only for the official project documentation. Use the Tutorials category if this is not the case.
• If you are not pasting the entire documentation here you must provide public links to it.
• You must link Pull Requests you have submitted on Github for the official documentation using the functionality provided in the editor.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Tutorial Rules

• This category is meant only for providing tutorials about an Open Source project.
• Machine translated tutorials will be rejected.
• Tutorials may only be about the technical aspects of the project or how-tos for the final users.
• End-user focused tutorials must address a minimum of three substantial concepts that are unique to the Open Source project and essential learning requirements for end-users. Preference is given to tutorials that are part of a curriculum (series) of tutorials all of which are sequential and built on previously learned skills and knowledge. Ubiquitous functions, such as Save, Open, and Print are unacceptable as substantial concepts.
• Trivial on-screen installation processes are not acceptable as valid tutorials.
• Gameplay is not acceptable as a valid tutorial.
• How-tos about graphic and design softwares are not acceptable as valid contributions.
• Tutorials can be in any language.
• If your tutorial also contains a video you should use the Video Tutorials category.
• You must write the entire tutorial on the Utopian Post
• Tutorials should made up a course curriculum, while not mandatory this is highly suggested.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Video Tutorial Rules

• This category is meant only for providing video tutorials about an Open Source project.
• Video Tutorials using a machine voice will be rejected.
• The video and audio recording should be in HD (720 the min).
• Video Tutorials may only be about the technical aspects of the project or how-tos for the final users.
• End-user focused tutorials must address a minimum of three substantial concepts that are unique to the Open Source project and essential learning requirements for end-users. Preference is given to tutorials that are part of a curriculum (series) of tutorials all of which are sequential and built on previously learned skills and knowledge. Ubiquitous functions, such as Save, Open, and Print are unacceptable as substantial concepts.
• Trivial on-screen installation processes are not acceptable as valid tutorials.
• Gameplay is not acceptable as a valid tutorial
• How-tos about graphic and design softwares are not acceptable as valid contributions.
• Video Tutorials can be in any language.
• You must embed the video directly in this post. Youtube or Dtube videos are accepted.
• Video Tutorials should made up a course curriculum, while not mandatory this is highly suggested.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Copywriting Rules

• This category is meant only for showing copywriting work you have completed for an Open Source project.
• Linking pull requests from Github is encouraged, but not required if not applicable.
• Contents of your copywriting can be in any language.
• You must be the author of the copywriting work and provide a clear way to verify that.
• Read the official Wikipedia explanation for what acceptable Copywriting work is.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Blog Post Rules

• You must provide an original and a unique editorial content of very high quality that is strongly related to the promotion and development of open-source related projects. Blogs must have a unique and consistent format.
• Blog posts must be part of a series. You must use the provided template and link other blog posts of your series
• If this is the first blog post of a series you are going to write, there must be clear explanations and expectations about the series you are going to propose.
• You may only write blog posts that are related to the promotion, development and functions of open-source projects.
• Blog posts must provide detailed content and overviews related to the open-source projects.
• Blog posts can be in any language.
• Images, screenshots, links and examples are not necessary but preferred.

Not respecting the rules will either give you lower votes or your contribution won't be accepted.

Related Categories

A moderator may only apply for one category or more as long as they have related know-how

• Suggestions - Visibility - Tasks for Thinkers - Tasks for Influencers
• Translations - Tasks for Translators
• Graphics - Tasks for Designers
• Development - Bug Hunting - Documentation - Tasks for Developers, Bug Hunters and Tech Writers
• Analysis - Tasks for Data Analysts
• Tutorials - Video Tutorials
• Copywriting - Blog Posts

Losing Moderation Rights

A Moderator will have to step back if the majority of the other Moderators/Supervisors/Advisors/Overseers believe the position should be left or if the Supervisor assigned to him opts for that.

Losing Supervisor Rights

A Supervisor will have to step back if the majority of the other Supervisors/Advisors/Overseers believe the position should be left.