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. Such a contest can be repeated many times if necessary.
Starts: 31 October, 2021 at 23:59 UTC
Ends: 08 November, 2021 at 23:59 UTC
Starts: 08 November, 2021 at 23:59 UTC
Ends: 18 November, 2021 at 23:59 UTC
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 .
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
The objectives of the Free TON Dev Experience Jury members are as follows
- 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 participate in the activities of the Free TON Dev Experience subgovernance on a regular basis.
The duties of the Free TON Dev Experience Jury members are the following:
- Study descriptions of new contests as they appear on the forum and/or in the chat. Do this even before they are approved. Ask the organizers questions if something is not clear. Achieve clarity in the criteria for evaluating work and the methodology for assigning marks.
- Start studying the works submitted for the contests immediately after the beginning of the voting period. Don’t put it off until the last moment.
- Ask the participants of the contest questions about the content of the works, if something is not clear from their work description. (see footnote below)
- Participate in meetings with participants of the contests that you are evaluating (AMA sessions).
- Evaluate the work of the participants in accordance with the evaluation criteria and according to the methodology from the description of the competition.
- Along with the marks, leave detailed comments with the justification of the mark.
- Communicate with contestants on the forum and in the chat. Including, to answer the questions of the participants about the reasons for the given marks.
- Improve the level of their own qualifications in areas related to the topics of contests held in DevEx subGov.
It would be nice if the last jury members’s request to any participant was sent at least a day before the end of the voting so participants have time to respond. Otherwise, probably you should think about resolving the doubts in the participant’s favor. And, please, don’t forget that there’re weekends, Christmas, New Year, Thanksgiving, Hanookah and other key public holidays that can be valued by participants.
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.
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.
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.
UPDATE of 28/10/2021: added Jury members duties.