Voting

[carletex]

Let's discuss on how admin will be able to vote. Some init ideas:

• We have a builder table with roles. roles = admin => you can vote
• We can give every admin 100 points (or whatever) and they have to spread out the point to all the different projects => sign.
• Not sure if they should see or not the other votes from admin
• Do we need privates notes?
• Maybe we have some flags (requirements are met, no cheating, the extension work, not spam... etc) so we can have some greenlight before voting.

[damianmarti]

100 points per voter sounds good.

I think that is better if you can't see the votes from the other voters, but we need to be able to send "signals" to other voters.

We can start allowing the voters to add comments to a project and we can add some flags later.

I don't think that we need private notes, I think that comments that all the admin can see are enough for now.

[carletex]

I think that is better if you can't see the votes from the other voters, but we need to be able to send "signals" to other voters.

Yep, one option is not showing anything at all (might be the most neutral way to do it :D). But the signaling is important too (especially if there are a lot of submissions). Maybe we could show that a project have "votes" but not showing how many? Very open!

I don't think that we need private notes, I think that comments that all the admin can see are enough for now.

Yes, sorry, with "private notes" I mean notes for (all!) admins, not visible for users. It's how we called them in grants.

[damianmarti]

@carletex I will add the feature to vote using 100 points (public for all the admins by now) and then we can improve from that. Sounds good to you?

[carletex]

hey @damianmarti !

Just talked with Austin and Shiv about this. Instead of 100 points, we thought that we could start with a 0 to 10 vote. Admins can vote for any submission with anything between 0 and 10.

About public/private... not sure yet, but I think that's easy to change (just hide in the UI :D)

Let's start with the simplest solution. Thanks!!

[damianmarti]

@carletex I'm thinking about adding the flags (requirements are met, no cheating, the extension work, not spam... etc), and saving this data to a json field in the submissions table, to be able to add new flags easily if we want.

I think it will be useful to have info about who set each flag, maybe we can add an automatic comment with this information for now.

Please, let me know what you think, and I can start implementing it then!

[carletex]

Hey @damianmarti

All of those flags might be overkill for this one, but I could see that feature in the future template.

For now: how about we create an "eligible flag"?? Well, not sure if it's just a flag because it can have 3 states, right?

• Elegible
• Non elegible
• (pending) The default state, before an admin has evaluated it.

json field

What are the downsides of this? Hard to query them? I guess it's ok for now.

We could also just do an extra field, but we'd have to create new columns for new flags in the future. NOt sure, up to you!

I think it will be useful to have info about who set each flag, maybe we can add an automatic comment with this information for now.

If we end up using the JSON field, maybe we can save a prop with the address of the admin who set the flag.

[damianmarti]

Hey @damianmarti

All of those flags might be overkill for this one, but I could see that feature in the future template.

For now: how about we create an "eligible flag"?? Well, not sure if it's just a flag because it can have 3 states, right?

• Elegible
• Non elegible
• (pending) The default state, before an admin has evaluated it.

json field

What are the downsides of this? Hard to query them? I guess it's ok for now.

We could also just do an extra field, but we'd have to create new columns for new flags in the future. NOt sure, up to you!

I think it will be useful to have info about who set each flag, maybe we can add an automatic comment with this information for now.

If we end up using the JSON field, maybe we can save a prop with the address of the admin who set the flag.

@carletex ok, I can start adding only a field for the Eligible status for now, and we can start using the comments to share more information between the voters.

[carletex]

Thanks Damu!

Closing this since we already created the issues / PRs