Meeting Notes: Weekly Calls 2021

From Kosmos Wiki
Jump to navigation Jump to search

Apr 15, 2021

Notes

  • Hyperchannel
    • Updated all deps, introduced Tailwind CSS. Ready for action.
  • Sockethub
    • Some housekeeping done. A blocking issue in master to be fixed.
  • Kredits
    • Finalized the last 2 cycles according to the changes agreed upon before
    • Some issues with Electrum co-signer pool. People not getting txs from it reliably.
    • Bumi started working on some prerequisites for the migration script, for moving kredits data to other chains/mainchains
    • raucao looked a bit into RSK again; seems like it could be an option for first mainnet deployment (avg tx fee ~$0.09)

Apr 8, 2021

Agenda

  • Kredits grants
    • Implications of payout threshold as planned before

Notes

  • Kredits grants
    • After discussion we determined that, instead of skipping payouts using a threshold number, the "salary"-to-"dividend" ratio should be adjusted. This will prevent skipping payouts when it's unjustified, and should create more incentive for active work. We'll adjust from 50/50 to 61.8/38.2 (golden ratio). The change will be retroactive for the last 3 months of the 6 month trial run.
  • Chat
    • Hyperchannel updated, and some fixes. Tailwind introduction next, then feature bonanza.
  • Infra
    • greg and raucao will finish migration of ejabberd cluster to private network

Mar 18, 2021

Agenda

  • Kredits grants
    • Minimum overall kredits amount issued to trigger payouts?
  • Sockethub

Notes

  • Sockethub
    • Refactoring, code coverage and linting, switching to Bull queue (from Kue). XMPP pairing with raucao and slvrbckt will happen today.
  • Kredits
    • How do we deal with cycles with little work done. Paying the same cycle grants as in normal/busy months seems unfair. Some options discussed:
      • Minimum amount of KS issued in cycle (static number, or calculated dynamically)
      • 6-month grant cycles (vs. 1 month)
      • Development velocity effects payout amount for cycle and dividends
    • Conclusion: Take the average of kredits issued in 3 previous cycles (velocity/difficulty), which defines the payout threshold. If threshold isn't reached, there are no payouts for that cycle but the newly issued Kredits are carried over (so no work is unaccounted for). The next cycle payout is made once the threshold is reached again (easier over time with less activity, due to taking the averages from the previous cycles).
    • Eventually, we would like a dashboard with these details. In the meantime use the Discourse forums so we can evaluate the new part of the process.

Jan 21, 2021

Agenda

  • Cycle payouts

Notes

  • The cycle payout spreadsheet updated by @raucao based on previous call with an update funds balance and actual numbers / contributions for all developers,
    • TODO: for kredits that haven’t been paid out (too small or no address) we need to document them for devs to claim in the future. (@raucao)
    • You could optionally have your payout address be a receiving address of the community wallet if you wanted to keep your reward in the community
    • Needs someone to verify amounts (@slvrbckt)
  • Kredits web dashboard should have a view for contributions within a cycle
  • Sockethub priorities - IRC connect bug and breaking up XMPP tasks into easy to tack pieces (@slvrbckt)
  • @greg and @raucao to pair on postgresql work again

Jan 7, 2021

Agenda

  • Chat (deploying new Sockethub and Hyperchannel)
  • Infrastructure updates
  • Kredits grants

Notes

  • Cannot deploy Hyperchannel/Sockethub yet, @galfert will create missing issue (from PR discussion)
  • The first kredits grants trial/experiment started in November, before the huge BTC price jump, so we agreed to lower the payout pool to 0.3 BTC to be used as the payout pool for the duration of 6 months from the first cyle

Nov 5, 2020

Agenda

  • Kredits grants
    • Payout scheme/ratios/numbers
    • Cycle block heights
  • Bitcoin multisig wallet
    • Electrum setup
  • Akkounts
    • New thoughts on tech stack and implementation details (@raucao)

Notes