Free TON Dev Experience Subgov Jury membership Contest #3

Ever TON Dev Experience Sub-Governance Contest Proposals
#1

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. Such a contest can be repeated many times if necessary.

Type

Contest

Contest entry period

Starts: 31 October, 2021 at 23:59 UTC
Ends: 08 November, 2021 at 23:59 UTC

Voting (assessment) period

Starts: 08 November, 2021 at 23:59 UTC
Ends: 18 November, 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

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

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.

footnote

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.

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.

UPDATE of 28/10/2021: added Jury members duties.

5 Likes
#2

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

#3

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.

#4

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.

#5

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.
#6

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.

#7

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

1 Like
#8

Fuhhh. I delayed the launch because I wanted to make a list of the duties of the jury members, so that they knew in advance what was expected of them when they would submit their applications.
It seems that the list is ready, here it is:

Duties of a jury member

  • 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.

footnote

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.

Фуххх. Тянул с запуском, потому что хотелось составить список обязанностей членов жюри, что бы они заранее знали что от них ожидается, когда будут подаваться.
Вроде список готов, вот он:

Обязанности члена жюри

  • Изучать описания новых конкурсов по мере их появления на форуме и в чате. Делать это еще до того, как они будут одобрены. Задавать вопросы организаторам, если что-то непонятно. Добиваться ясности в критериях оценки работ и методики выставления оценок.
  • Приступать к изучению работ, поданных на конкурс, сразу после начала периода голосования. Не откладывать до последнего момента.
  • Задавать участникам конкурса вопросы по содержанию работ, если что-то непонятно из их описания. (см.сноску ниже)
  • Участвовать во встречах с участниками конкурсов (АМА сессии).
  • Оценивать работы участников в соответствии с критериями оценки и по методике из описания конкурса.
  • Вместе с оценками, оставлять развернутые комментарии с обоснованием выставленной оценки.
  • Общаться с участниками конкурсов на форуме и в чате. В том числе, отвечать на вопросы участников о причинах выставленных оценок.
  • Повышать уровень своей квалификации в сферах, связанных с тематикой проводимых в DevEx сабгаве конкурсов.

Сноска

Было бы хорошо, если бы последний запрос членов жюри участнику был отправлен за день до окончания голосования, чтобы участник успели ответить. В противном случае, возможно, стоит подумать о разрешении сомнений в пользу участника. И не забывайте, что есть выходные, Рождество, Новый год, День Благодарения, Ханука и другие важные государственные праздники, которые могут значимыми для участников.

UPDATE: Added footnote

2 Likes
#9

Hi! I would like to participate in the life of your community. Can I apply for this position or has the competition passed?

#10

I’d add the following:

  • The last request from the juror to any submitter must be sent at least 24 hours before the voting ends (not counting weekends, Christmas, New Year, Thanksgiving, Hanookah and other key public holidays that can be valued by the participants). Otherwise, all the doubts must be resolved in the participant’s favor.

Let me explain: during the past contests it was a common practice to ask something at late night just before the voting end. It’s really weird when you try to wake the responsible engineer up at 4am to get some clarifications urgently requested by a juror. I hope this bad paractice will be stopped.

1 Like
#11

If you were the contest winner, it will allow you to prove your competence.

#12

I have participated in several competitions. Here is the work for which I finished 4th:
https://tonto.space - This is done in Laravel (PHP) and pure Js.
Competition article:
Каждый кристалл на счету: аналитика партнерств Free TON | Free TON House

Competition “Winners Directory”:
https://tonwinners.com - Also 4th place.

Unfortunately, until now I have not taken the first places.
Source code on my GitHub: Timuchen (Tim) · GitHub
GitHub contains little work as most of the work is done in private Bitbucket projects.

Will this pass as proof or do I need to win the contests?

1 Like
#13

I understand your pain, but

  1. I don’t know but for me it is too complicate. If I haven’t heard about Hanookah so how can I take it to consideration?

  2. From other side: why did they ask for clarification? Everything should be clear from the application itself and from the readme in the repo. If it is not, why should it be resolved in the participant’s favor?

  3. This is a clear point of conflict. I would rather not create it.

  4. After all I rephrased your wish in less declarative form. Otherwise, participants will begin to bring certificates from electric (and other) companies about the lack of electricity (and death of great-grandmother) and we will get bogged down in the arbitration of all this.

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.

#14

Fully agree with your softer proposal.

#15

I’ll try to participate, good luck everyone !
tg: @nerzh

1 Like
#16

Hi all, in a few minutes I’ll send my submission. For all the questions feel free to contact me via Telegram @SergeyEgorovSPb

1 Like
#17

My suggestion. I hope I can be helpful

1 Like
#18

I want to try to participate) @vadimrusakov

1 Like
#19

I am going to apply too. @fabrice_dune

1 Like
#20

I will apply too, @Ovenstent

1 Like