What is Utopian? State Of The Art Forever Stored In The Blockchain. 107 Days Since The Beginning.

utopian-post-banner.png

Find here all the details about the state of the art of the Utopian.io platform as of today, January 13 2018.

What is Utopian.io?

Utopian.io is a STEEM based online platform rewarding contributions to Open Source projects. A project is Open Source when its codebase is public and editable, usually hosted on Github.

Utopian.io is the first online moderated STEEM based platform that enforces a set of rules each contributor should follow before contributing. The rules can be found here https://utopian.io/rules

Using Utopian.io you can contribute to Open Source projects and be rewarded for that or crowdsource your Open Source project using task requests.

- Contributions Categories

Below a full list of categories available in Utopian.io where you can submit your contribution.

- Suggestions Category

Suggestions are minor features/enhancements that you would like to have in an Open Source project.

- Development Category

Any merged Pull Request you have submitted for every project hosted on Github.

- Bug Hunting

In this category you can report bugs you have found in an Open Source project.

- Translations Category

This category is meant for translations you have updated or created for an Open Source project.

- Graphics Category

This category is meant for graphics/videos/motion graphics you have realised for an Open Source project.

- Analysis Category

This category is meant for providing a data analysis you have generated for an Open Source project.

- Visibility

This category is meant for providing results of online social engagement, ads and similar for an Open Source project.

- Documentation

You can use this category when documenting an official documentation for an Open Source project in a merged Pull Request.

- Tutorials and Video Tutorials

This category is meant for providing highly technical tutorials about an Open Source project.

- Copywriting Category

This category is meant for showing copywriting work you have completed for an Open Source project.

- Blog Post Category

You can use this category to 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.

Task Requests Categories

Below a full list of tasks available in Utopian.io where you can submit a request that contributors should get done.

- Task Requests for Conceptors/Thinkers

By submitting a task request in this category you are requesting contributors to provide concepts and ideas.

- Task Requests for Developers

In this category you can write if you are looking for developers joining your crew.

- Task Requests for Bug Hunters

In this category you can post if you are looking to spot bugs in your system/software/website and similar.

- Task Requests for Translators

You can only post in this category if you are looking for translators to translate your project.

- Task Requests for Designers

You can post in this category if you are looking for designers to join your Open Source project.

- Task Requests for Tech Writers

This category is meant only for requiring help in updating/creating the documentation of your Open Source project.

- Task Requests for Data Analysts

This category is meant for requesting data analysis for your Open Source project.

- Task Requests for Influencers

This category is meant for requesting help of social influencers in spreading the word about your project.

3,748,717 Steem Power Delegated to @utopian-io

The official @utopian-io account has a total amount of 3,748,717 Steem Power Delegated. The delegated Steem power is used to upvote all the accepted contributions in Utopian.io. The delegated Steem is given by the Sponsors.

Screen Shot 2018-01-13 at 19.27.14.png

Sponsors / Delegators

By delegating your voting power you are enabled as an Utopian Sponsor.In Utopian Sponsors share 20% of the author rewards generated on Utopian based on the amount delegated.

For example with 1 Million SP delegated to Utopian, you will receive an average 1000 Liquid Steem per week.
The profits increase as the author rewards increase, therefore delegation is a commitment for the growth of Utopian.

As a Sponsor you will be credited also on every promotional activity.

The delegated Voting Power is used to reward all the accepted contributions submitted in Utopian using the Utopian Bot.

Moderators / Supervisors

The Utopian Moderators check every submitted contributions in Utopian in order to evaluate if the contributions meet or not the https://utopian.io/rules.

The Utopian Moderators share 5% of the author rewards generated on Utopian based on the number of reviewed contributions (either accepted or rejected). The profits increase as the author rewards increase, therefore moderating is a commitment for the growth of Utopian.

Contributions that have been rejected won't be voted by the Utopian Bot.

Announced Milestones

Here a list of announced milestones. Find the details on this post.

  • Utopian Registration Module
  • Public Integrable APIs
  • Kickstarter Campaign
  • Automation
  • Utopian Bounties system
  • Utopian Internal Delegation Split
  • Utopian Promotional Placements
  • Utopian V2
  • Utopian Browser Extension

Stats

  • Utopian.io has a total of 23235 submitted contributions.
    Screen Shot 2018-01-13 at 19.16.28.png
  • 15700 contributions were accepted as valid contributions.
    Screen Shot 2018-01-13 at 19.18.00.png
  • Utopian.io has a total number of 84 enabled Moderators.
    Screen Shot 2018-01-13 at 19.21.12.png
  • Utopian.io has a total number of 116 Sponsors/Delegators.
    Screen Shot 2018-01-13 at 19.20.45.png
  • Utopian has generated 435628 SBD.
    Screen Shot 2018-01-13 at 20.04.14.png

Utopian Community-Driven Witness

We are made of developers, system administrators, entrepreneurs, artists, content creators, thinkers. We embrace every nationality, mindset and belief.

Utopian.io is the first Community-Driven Witness. Every decision will be taken as per the consensus of the entire community.


Snapshot of the current Utopian Rules

Below a snapshot of the rules as per the date of this post that you can find on https://utopian.io/rules.

General Rules

Immediate Rejection

Not respecting one or more of the rules below will lead to direct rejection of your contribution.

Hard VS Soft Rules

Rules are implicitly marked as Hard rules. Soft rules are marked with the label [SOFT].

  • All the rules not marked as [SOFT] lead to immediate rejection.
  • All the rules marked as [SOFT] may lead to rejection if you have been notified about the same mistake multiple times. In any other case the Moderator will ask for a change but accept your contribution anyways.

Editor Templates

When submitting a contribution you will find a standard template that you should follow when writing the details of your contribution.

  • Templates are editable, as long as your contribution has a clear format.
  • Templates can be extended.
  • Templates can be translated in a different language than english as long as the category allows that. Check the specific rules for each category.

Temporary / Lifetime Bans - Utopian Downvote

Utopian may ban your account temporarily or for the lifetime and may also proceed for a downvote in any of the following cases.

  • Any user found harassing a member of the Utopian Moderators or in general any member of the Utopian teams.
  • Using multiple accounts to clearly abuse the system.
  • Keep contributing with low quality contributions even after being notified.
  • Plagiarism.
  • Using Licensed or commercial materials or Creative Commons without citing the source even after being notified.
  • Tag spamming. [SOFT]
  • Commercial/Copyrighted Materials

    No commercial or copyrighted material should ever be used in a contribution.

    • Only Creative Commons for Images and Videos can be accepted and the source should be always cited.
    • You retain full responsibility when using copyrighted or commercial materials without proper permission.

    Contributions must be Formal and Professional

    A moderator may reject a contribution if it is not written in a formal and professional style.

    • The contributor should follow the templates provided in the editor for each category. [SOFT]
    • The writing style should be formal never informal.
    • The writing style should be professional.
    • Sentences like: Hello Utopians, Hello Steemians, Dear friends and similar informal sentences may lead to rejection. [SOFT]
    • Sentences like resteem, follow, upvote may lead to immediate rejection. [SOFT]
    • Quality of the images and videos used in the contribution should be high. Low res images and videos will be rejected. [SOFT]
    • A contribution with bad grammar will be rejected if the contents may be really hard to understand. [SOFT]

    Contributions must be Informative

    The contribution must contain as much detail as possible and have some graphical content in it (images, charts, videos, etc) where applicable. The length of the body of the contribution should be enough to give every possible detail about the submitted contribution.

    Contributions must be in English

    Contents of the contributions (post content) must be in plain English and fully understandable. The only accepted exceptions are:
    • Contributions under the Tutorials, Video Tutorials Category and Blog posts.

    Never Submitted Before

    Contributions must be unique. Users must first check if the same or very similar contribution has been submitted before.

    • Same contributions will never be accepted in Utopian twice by the same or different user.
    • Contents already shared on the Steem blockchain in general may still be rejected if submitted in Utopian.
    • Contents already shared anywhere else may still be rejected if submitted in Utopian.
    • Same contents already shared before in Utopian or anywhere else by different users may still be rejected if a moderator recognises plagiarism.

    Author of the Contribution

    The contribution must provide as much detail as possible to verify the actual work done and that you are the author.

  • If your Steem/Utopian username does not match with the username used in an external platform, you must either edit the username in the external platform or provide an immediate way to verify you are the author.
  • Contributions Must Not Contain Spam

    The contribution should not contain any clear attempt to profit solely from a commercial perspective, and should not be written in a way that suggests the contributor is looking to maximise the returns.

  • The author may provide links to his social profiles in a way that does not disturb the reader.
  • Links to commercial products are forbidden.
  • Misusing the mentions by mentioning other Steem/Utopian users without an obvious reason will lead to rejection. [SOFT]
  • Contributions Must Not Contain Defamation

    Contributions must not use namecalling directed at other users of the Steem blockchain. Contributions may not contain false information about another user that may be perceived as defamatory.

    Contributions Should Not Solicit for Unrelated Activities

  • Contributors should not ask for Steem/Steemit related activities in their posts, such as upvotes, resteems and follows. [SOFT]
  • Contributors should not ask for Utopian related activities in their posts, such as upvotes and follows. [SOFT]
  • Contributors should not solicit for any activity in general that it is not strictly accepted by the Utopian Rules.
  • Contributors should not ask for witness votes in their Utopian posts. [SOFT]
  • Unvoting - Rejection After Approval

    Utopian can unvote or reject an accepted contribution if it is found out that the contribution did not meet the rules and had been upvoted by mistake. This decision considers cases such as attempts of plagiarism, copying work and ideas of others or other violation of the rules which would be obvious to see that the contribution does not deserve the reward.

    Github Repository

    • The linked Github repository must always contain code, a README and a license. [SOFT]
    • Contributions for un-official repositories will only be accepted if present in Utopian un-official repos whitelist
    • Contributions on official repositories that are mirrors of another subversioning system are always accepted.
    • Contributions on repositories that had no updates for longer than 1 year, will be rejected.
    • Contributions on forks that do not have any difference/improvement from the original project won't be accepted.

    Categories Rules

    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.

    Task Requests

  • Task requests are meant to be made by the project owner when looking for contributions.
  • A task must be explained in great detail and provide all the necessary details for it to actually be completed. In one task request, there should not be more than one task; and if more, they must be related to the category where the task request is being submitted.
  • Generic task requests, like "We are looking for contributors" won't be accepted.
  • You should always provide contact details for the contributor to get in touch with you.
  • You should always define a deadline. [SOFT]
  • Conceptors/Thinkers

    • By submitting a task request in this category you are requesting contributors to provide concepts and ideas.
    • You must provide great details about what you are looking for and the problems you want to solve with a concept.
    • Images, screenshots, links and examples are always welcome in this category.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Developers

    • In this category you can only write if you are looking for developers joining your crew.
    • You must provide all the details for the developers to contribute to your project.
    • Documentation, Repositories, Communities (e.g. Slack, Discord) and specific details are necessary.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Bug Hunters

    • In this category you can only post if you are looking to spot bugs in your system/software/website and similar.
    • You must provide every possible detail for the bug hunters to be able to start the hunting.
    • You must include for example browsers, devices, operating systems and similar info where you want bugs to be spotted.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Translators

    • You can only post in this category if you are looking for translators to translate your project.
    • You must provide any necessary information for the translators to start their work.
    • Location of the files to be translated, tools to use, languages you are looking for and similar info are necessary.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Designers

    • You can only post in this category if you are looking for designers to join your Open Source project.
    • You must provide exactly what you are looking and how would you like it to be in great details.
    • Whether you are looking for a logo, layout, banner or similar, your request has to be very specific.

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

    Tech Writers

    • This category is meant only for requiring help in updating/creating the documentation of your Open Source project.
    • You must be very specific about which part of the documentation you wish to update/create.
    • It is important to provide the tools you wish to use and necessary info for the documentation to be actually written.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Data Analysts

    • This category is meant only for requesting data analysis for your Open Source project.
    • Your request must be very specific about the numbers you wish to extract.
    • You must provide the tools and all the information necessary for the analyses to be actually completed.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Influencers

    • This category is meant only for requesting help of social influencers in spreading the word about your project.
    • You must provide any possible detail for the influencers to effectively share your Open Source project.
    • You must also provide any graphic, video and similar digital goods the influencers are supposed to share.

    Not respecting the rules will either give you lower exposure or your task request won't be accepted.

    Report a Moderation Issue

    Get in touch with the Supervisor assigned to the moderator that reviewed your contribution. Find them on this document.

    Moderation

    • Utopian Moderators/Supervisors have full rights to reject or accept a contribution.
    • Supervisors may always revert an accepted/rejected contribution.

    Application as an Utopian Moderator

    • You must write a public Steemit post proposing his intentions, one category or more related categories he would like to moderate, his field of expertise and should nominate one existing Supervisor.
    • The public Steemit post must be pasted in the channel #mod-applicant on Discord. In order to nominate a Supervisor pick one from the official list.

    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.

    Application as an Utopian Supervisor

    • Supervisors will only be accepted if they have moderated at least 600 contributions and being active since at least 2 months.
    • Supervisors must have a proved strong general know-how of the Utopian platform and its categories.
    • Supervisors should always check the work of their teams and make sure work on other teams is proceeding correctly.
    • Supervisors must have a weekly public review of the work of their teams.

    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.

    See our FAQ

    Click here to view our Frequently Asked Questions(FAQ) page, where we detail the most asked questions and their answers.


    Top Utopian Sponsors


    @freedom - Vote Witness

    @misterdelegation

    @ned

    @transisto

    @wackou - Vote Witness

    @xeldal - Vote Witness

    Top Utopian Moderators


    @ruah

    @knowledges

    @drigweeu

    @espoem

    @damla

    @omeratagun

    H2
    H3
    H4
    3 columns
    2 columns
    1 column
    340 Comments
    Ecency