Yeah, at first it was fun to read the new topics but now it’s just old news 
1 Like
Q. What improvements can we make for TRON Grand Hackathon 2022 Season 3 which is set for mid-September?
(Please suggest all ideas you have. We don’t mind if your post is too long as the TRON DAO team will really read all posts on this thread!)
It would be good to consider the possibility of handling different languages.
Including Spanish could be a GREAT start 
Everything else is incredible, very exciting to be participating in these spaces and I am still very grateful for the team behind to achieve all this 
Q. How do you feel about vote buying? How do we draw the lines between promoting a project and asking for vote support, giving incentives to possibly win a prize by voting, and giving tokens/gifts outright to voters?
It is not correct to buy the vote, the results simply become unfair… the good thing is that the greatest weight is on the side of the judges and that can be balanced
But there is a collateral effect when buying votes (increases SPAM in the forums) and I consider that this is even more problematic because intelligent conversations are not generated
----Greetings to the whole community, excellent weekend for all 
----
6 Likes
Justin Sun’s projects need to be supported
i wonder who;s gonna win the 5k cmmunity prize!? 
We should distinguish two cases here: if a previous winner creates a completely new product (new project or significant feature addition to the previous) or if a winner does a minor cosmetic change and participate again.
In the first case we have teams that keep working and bringing innovation the the ecosystem and should be allowed to participate without limitations.
The second case should be excluded. The rules for S2 already require that and I think that some projects that have been admitted could have been excluded with the current rules.
3 Likes
There should be a separate prize category for the Aleady winners and pre-existing projects 
First of all thanks a ton @TronLive for conducting another successful hackathon 
! The overall positivity and engagement in TRON is growing organically over the past few months 
.
For Q1 few suggestions:
-
Apart from standard tracks we have, how about introducing a 5th track called NEWBIE !
The prizepool for original 4 tracks remain the same … but lower for NEWBIE Track.
New projects with small team/community can have option to participate in either 1 … if they are confident they can choose standard track … if not then complete with other newbie… this will lessen heart burns and also provide a platform for new projects to grow organically! -
Some flexibility can be introduced in count of winners as a % of participants! For eg if a track has 100 participants while another has say 20 ! The one with more tracks can have more numbers of winners as say a fixed consolation prize. So for eg in the above assumption… the track having 100 participants can get 4-5 additional consolation winners.
-
The voting period can be made smaller say 5-7 days.
-
In Devpost or platform wherever the S3 is conducted … the entry should have a segment for the judges to record feedback / suggestions… this will help the projects introspect and improve on their offerings .
Regarding Q2 : Pay per vote should be a strict no.
3 Likes
I had read somewhere that 
is where democracy started …. Jk 
1 Like
Birthplace of “Modern” democracy. 
1 Like
The idea of a separate track for newbies is interesting. Maybe we don’t need a separate track that projects must choose, but it would be enough to have an additional voting only track to award the best new projects, in addition to the normal voting tracks where old and new projects would run together.
1 Like
I like the idea of having a newbie track. Great and elegant solution
2 Likes
This is actually a good idea to prevent people from simply voting for one project they know without checking out the others. Also received multiple requests on the reduction of community voting time, we can probably make the judging time long (as the judges need them) but community voting time shorter. Thanks @Stian
Thanks @fabsltsa. We will help ensure the hackathon rules are more precise in subsequent hackathons. Right now for S2, the following rule is stated - “Build (or significantly update) a software application/dApp/website that integrates with the TRON/BTTC blockchain”, therefore, if a project is on TRON/BTTC blockchain, or has integrated with TRON/BTTC blockchain by using tokens/APIs/functions from TRON/BTTC ecosystem, it counts. This is to attract projects from other chains to join our ecosystem. We hope these projects will see our community will show more support if they make more effort to be on our blockchain as well! 
Another request for minimum vote per track here. Looks like we may probably get this on the next community vote. Glad that you find S2 already has many improvements compared to the last one. Thanks @Dendorion!
Another request here from @Sirluke to reduce community voting time. Looks like @trondao will have to come up with a timeframe that works best for the judges and the community (probably a separate timeframe for judges and community). Good idea on limiting the option for new posters to create a new topic! Thanks.
Thanks for your suggestions @klappetron. Since some of the tracks do not need deployment on tronscan, for example, a web that utilizes TronLink and supports the ecosystem, or a project that uses TRON API to carry out functions. However, we do agree that more precise statements can be made so participants will understand the scope of the hackathon. TRON has tried open-source or “codes to judges” hackathons in the past and it results in way fewer participants. Maybe we can utilize the forum and request participants to create a project post towards the start and document the progress as they go. This will help the community see the evolution of the project as it goes through its own milestones. Thanks again for sharing your opinions!
8 Likes
Yeah looks like reduced community timeframe idea is been liked by many 
Another thing which would help for a decent community vote, would also be to check the engagement on the projects posts in the Hackathon TronDAO forum. There are projects who have a lot of community engagement in their posts. Giving continuous updates, others are completely dead and focussing only on getting votes.
Maybe for the next Hackathon, it would also be good to weigh in community engagement in the posts as a factor for community voting. Then it is more then just ticking a check mark in a box, but also about interaction.
We need to get this forum filled with people engaging with each other and with the projects on TRON, we don’t need voting machines as they come and go…
1 Like
It’s hard to get the perfect blend @JasonHunter. Last time when TRON Foundation hosted a pure 100% judges-only hackathon, the community complained about foundation being bias. Therefore, TRON DAO chose to split the prize to two pools so we have the best of both worlds. Hope that with all these feedbacks, S3 community voting will be even better!
Welcome @DahmerLee! Thanks for voicing out. Yes, it is important to choose a project that has good potential so it can last and the community can benefit from it. We hope to see you around often.
@PrimoOceanDAO Teams should not be able to do anything they want, hence there are rules for competition.
If you think most of the users on this platform are bias, then may be you should reevaluate the situation - Is the glass three-quarters full or one-quarter empty?
Don’t you agree that if most users are against one’s opinion, maybe the opinion itself most likely has a problem?
By the way, if you haven’t read the official statement on vote buying, we urge you to check out TRON Grand Hackathon 2022 Season Two - #253 by admin.hackathon
Anyway, we are not against PrimoOceanDAO and truly welcome any serious participants that help grow the ecosystem. We just like to point out that participants should abide to rules for competition otherwise everything will be out of order. Stay sTRONg and keep building!
@WindsOfChange92 Moderators are having a tough time as there are way more new participants, new users and new topics for this season. Good idea on consolidating topic, maybe it can be taken into consideration @admin.hackathon
Keep up the good topic contributions to the forum!
@JavierGarza The possibility of handling different languages for our hackathon is definitely good, however, there isn’t enough foreign language participants of a single language at this point yet. May be if you can gather enough Spanish community members to join as hackathon participants, then there’s a chance for us to have this in the near future =)
3 Likes
I’ve made a suggestion on Telegram going in that sense. For projects that are on other chains and consider coming over, if they are building quality, trondao and community projects could collaborate in order to make their migration/expansion to tron as smooth as possible. A separate hackathon/competition could be organised for them.
I think that the grand hackathon should be only for projects that have built on Tron and BTTC mainnet as we are judging a finished products ready to run.
Also I would add that in order to make the competition more fair for new projects, instead of excluding teams/projects, we could simply exclude pre-existing products even tho they have been substantially improved. Each entry should be a new product bringing value to the ecosystem and ready to use (on mainnet).
3 Likes
Formato Hackathon S2, 5 votos por pista ya que da opción a votar para más proyectos.
Agreed, each season has its nuances. As you have pointed out before, once we reach S3 the same problems might arise. Hard to please everyone.
1 Like
Unrelated: USA is not the birth place, Baby Daycare, Kindergarten or even Hired Nanny of Democracy
Just too triggered to let that statement slide
2 Likes
I’m genuinely curious if the forum has an algorithm that detects user language as I hardly see users in languages other than English, projects too
2 Likes