This is yet another L1 team proposal. I propose a team of 6 people + 1 assistant to handle all the necessary work to do the parity upgrade work in Q2. Please look at the details outlined below.
At the moment it looks like proposal 11463 and 11462 are not passing. Both of them. I think the final result is not settled yet. But I smell a certain risk, that none of these proposals passes. But having no team to work on the L1 would be the worst thing that could happen to us as the community of this chain. This is why I decided to put this one here on Agora.
Scope of Work:
The scope of work is pretty straightforward: The main scope of work for this team is to make the parity upgrade. This means:
- API breakage and upgrade Testing for the alpha release v2.0.0 of the terrad binary
- Finalize the currently ongoing switch to the canonical wasmd smart contracting platform and migrating the current wasm state of the chain to that canonical platform
- API breakage and upgrade testing for the wasmd upgrade
- Houskeeping and finalization and/or testing of backlog items and issues in the GitHub repository under GitHub - classic-terra/core: GO implementation of the Terra Classic Protocol
$6,200/month for Bilbo Baggins x 3 months = $18,600 overall for Q2
$6,200/month for SolidSnake x 3 months = $18,600 overall for Q2
$6,200/month for Vinh x 3 months = $18,600 for Q2
$5,000/month for NotJoshC x 3 months = $15,000 overall for Q2
$5,000/month for MangoChutney x 3 months = $15,000 overall for Q2
$5,000/month for ChopstickSensei x 3 months = $15,000 overall for Q2
$5,000/month for LuncBurnArmy x 3 months = $15,000 overall for Q2
In addition to that (and to make the resulting sum nicely round and dandy) I would suggest $34,200 of “flexibility budget”. The team is free to use this flexibility budget in order to pay for computing costs, office management systems or even consulting.
That’s an overall $150,000. At a conversion rate of 0,000126 this makes roughly 1,182,965,300 of LUNC out of the community pool. This is about the half of what is currently in there. So it leaves enough room for other spend proposals to pass or even for the Q3 work to be put forward.
The amount received from a spend proposal would be swapped to USTC first. To exit from volatility risk. Payments of team members would happen at a monthly basis at the end of the month.
This proposal would only be put up for a vote on Station if none of the proposals 11463 and 11462 passes. It’s subject to modifications as the discussion goes on.
The scope of work might look a bit fuzzy. I am not a good proposal writer. But I am a software developer. And I can tell you this: In software development we can try to break down the issues to be tackled to the nitty-gritty and try to plan everything through with contracts and penalties and all that stuff. Or we can give a general but precise scope of work and let the details fit into that - giving the team room to adapt to changing external situations. I prefer the latter approach.
You will notice the inclusion of @LuncBurnArmy. A team needs a manager. Believe me. Rabbi says it’s not needed. But he didn’t worked on that Q1 team. In Q1 @LuncBurnArmy
- moderated our daily talks and planning sessions.
- took care of the GitHub backlog and project houskeeping
- made the outlines, presentations and timelines
- handled the community sentiment and outside communications (you know - that’s what I respect him most for)
- handled some fun items like the Luna Classic Status page
So - I wouldn’t wanna miss him. He is a sincere and transparent person. And he REALLY earned that bump - Especially for handling you - the community - extremely well and professionally (without outage or rant or whatever).
Jacob is missing from this proposal. I am sure you guys and gals know about his recent rant on Twitter. He publicly described the Terra Classic chain to be the cursed daughter of Do Kwon and wants to publicly smash and burn the Notional validator hardware and sprinkle it with holy water. I mean - It’s funny that he wants to destroy his hardware and I am really excited to see that video that he promised. But - c’mon. It’s not funny how he talks about us and how he presents us in the greater Cosmos space. Sorry, that guy does not belong here. Never - ever!
Next question you probably gonna have: I am missing in that team. To keep the budged straight I had the choice to include Vinh or myself into the L1 team. The obvious choice is Vinh. He has much more experience with Cosmos SDK than I do. Period.
Let’s talk about this. I mean, I discussed none of this with the the individuals involved. So it’s really like a very rough outline of what I imagine under “Q2 L1 work”. Pholuna made a similar proposal that does not include LBA. Check that one out too. We need to find a consensus on this matter. And it would be nice to have a consensus that passes a little better that with 51% yes votes. Everything else splits us apart. So let me know what you think!