Free TON Dev Experience Subgov Jury membership Contest #3 (WIP)

WIP = Work In Progress

Additional contest: Free TON Dev Experience Jury Contest

Short description

This contest is essentially a continuation of the #2 Free TON Dev Experience Jury Contest and #8 Additional contest: Free TON Dev Experience Jury Contest. Due to the fact that not everyone was able to participate in the previous contests, it was decided to provide an additional opportunity for those who want to become jury members.

Type

Contest

Contest entry period

Starts: 12 October, 2021 at 23:59 UTC
Ends: 24 October, 2021 at 23:59 UTC

Voting (assessment) period

Starts: 24 October, 2021 at 23:59 UTC
Ends: 31 October, 2021 at 23:59 UTC

Goal

The goal of the contest is to attract professional developers that will be motivated to enhance the Free TON ecosystem by participating in the Free TON Dev Experience subgovernance .

Contest submission requirements

Applicants must provide a curriculum vitae that demonstrates the following:

  • Knowledge of IT and/or blockchain technologies
  • Proof of engagement in open source development (a link to github account is a must have)
  • Proof of knowledge of the code base of the Free TON
  • Proof of good understanding of the decentralised governance
  • Disclosure of the organisations/ the companies they are working for
  • Disclosure of social network identity (Telegram ID, LinkedIn ID (if possible), Github ID)
  • Deployment of smart-contracts if you want to join Smart Contract Jury group
  • Choose the Jury group you want to join (you can choose several ones) - SDK Contests, Toolchain Contests, Node Contests, Smart Contract

Rights and duties of the winner as a member of the Free TON Dev Experience Jury

The duties of the Free TON Dev Experience Jury members are the following:

  • to ensure smooth running of Free TON Dev Experience subgovernance;
  • to ensure development of contests proposals;
  • to review the contests proposals;
  • to assess submissions for the contests, including if necessary code review or documentation review;
  • to ensure timely distribution of funds;
  • to participate in the activities of the Free TON Dev Experience subgovernance on a regular basis.

For the purpose of the efficient and timely assessment the jurors will be split into groups according to the topics of the contests to be run within Free TON Dev Experience subgovernance: SDK Contests, Toolchain Contests, Node Contests, Smart Contract. Check Free TON Dev Experience subgovernance proposal for more information.

The Free TON Dev Experience Jury members are eligible for their services for the remuneration from the Jury Remuneration Fund . The rewards are to be defined on case basis.

Assessment of the entrants to Free TON Dev Experience Jury Contest

Each of the initial members of the Free TON Dev Experience Subgovernance has to assess all the incoming applications.

A juror must assess the application on a scale of 1-10 (10 - the highest score, 1 - the lowest score), based on assessment criteria.

A juror must provide a writing feedback for each application.

The applications that can’t be read or contain irrelevant information, or submitted after the deadline are to be disqualified and rejected.

Procedural remarks

Participants must correctly upload their applications to the Free TON Dev Experience Jury contest (in PDF format) in order for the jurors to view them. If the application can’t be open or is submitted in the wrong format, the candidate will be rejected by the jury.

Participants must submit their applications before the deadline of the contest. If the application is submitted late, it will be rejected.

All submissions must include the contestant’s social network identity, a Telegram ID and Github ID, by which jurors can verify that the submission belongs to the individual who submitted it. ​ If not, the submission may be rejected .

Any juror may approach any applicant via Telegram and appoint an interview or ask several questions in writing to clarify any facts given in the application. The rejection to give an interview or to answer the questions can affect the score.

5 Likes

Is it really mandatory? Apart this, everything looks fine for me

The jury member must be a good experienced developer, and GitHub gives us the opportunity to check his activity for some recent period of time. If there are any other options to give us info like this - they could be used as well.

For example, I’m a good experienced developer but my personal GitHub is empty - I don’t develop public personal projects. My suggestion is to put this requirement from mandatory to desired.

Ok. We can put it to desired but honestly, if I am experienced developer, I can’t imagine my profile will be empty.

  1. I’m using the works from other developers which are not perfect. So I’m constantly making PRs and creating issues, taking part in discussions in others public repos.
  2. Github could show your activity for private projects as well:
    Publicizing or hiding your private contributions on your profile - GitHub Docs
    So if you’re experienced developer, your activity will be shown on the contributions panel of your profile.

I think it highly depends on the background of a particular developer. If she works mostly with mainstream stuff she would rather use widely reconginzed solutions rather than lame quick-and-dirty ones. But in case of concentrating on some exotic things, I agree, a number of bugs and fixes against the awkward stuff is expected.

You will be surprised when you find out how many bugs even mainstream stuff and widely recognized solutions contain.

1 Like