Y’all have no idea how intruiging it was reading through your Ideas, point of views, It was really fun
Great minds guys… great minds
So from all the tiny points I could gather from everyone’s suggestions, I think i can bridge into all of them and suggest something more cummulative
And the way i see it this has more pros than cons if any…
So i was thinking, why not this:
-
I did a little digging recently and found that we have about 160+ members on the community a lot of which are inactive on the community. Firstly we can’t all be writers , we’ve got devs (hold that thought) etc. I mean how many way can you possibly deploy a smart contract. We need more standard and unique pieces right, ones that meets our readers needs and not just ours.
-
And we’re creating these for the comunity right?, at the same time we need everyone’s hands on deck, why don’t we share roles
Lets have: Writers, Writers and Reviewers, and Voters, Devs (who aren’t writers) as distinctive roles.
Afterall I don’t think any one ever thought of writing about a bug while building on celo, something a lot of dev. must have gone through, So for a dev. role for example you can come up ane be like (Hi I encountered a bug while working on this, although i got to solve it,…You can drop an description and maybe pictures about your bug and how you solve it and if It’s something a lot of people “beginners” happens to be facing and would like to know how to overcome you get an incentive for proposing a solution, and then a writer picks it up as a short topic to write on and explains about it.) that’s just by the way though.
-
If we are really targeting the audience why not let them decide (including the entire web3 community out there) which also brings us to inviting the web3 community out there to join the celo sage and become voters to vote on what contents they’d like to see being written and maybe get incentives too if it their unique idea gets approved by a lot of (voters not writers) they also get inncentives. and not just that (their reasons for wanting that content being written).
-
So as reviewer or writer or both you cannot vote. Let the community decide what they want to read on, which also means creating the role for voters, (who are not writers) but can also pitch proposals on tutorials they want. That takes away the biasness entirely so far.
-
The distinctive roles can be determined on activeness on the community “Cheers”. Either ways everybody benefits from the system
I know this is a lot to process, and still not structured too. I had it in a rush myself …
But I’m pretty sure this sets off the idea of the solution we reallly need for the whole voting system and some other solutions we are looking to improve to help the community in terms of more roles…
And as always please bombard this comment with those great minds, We’ll have to solution we need in no time, still on this Idea, Just more neatly standardized
Mayowa Julius (Phenzic)