You are reading content from Scuttlebutt
@dan %6FK81ftRN7csSBCOvBI9YHMEq4DpuHFqsRV9q7i50oE=.sha256

Report: Tools for Transparency & Accountability

This is a fork of original post

The Document lives on hackmd here

@Alanna I have added another tool/project/team 'Social Wallet API'

Kieran and I will also add the 'MMT Transaction Log' which was built by @Kieran @Nikolai and @peg in the first 3 months of mmt

Really great report :)

@dan %KkM3DWhCOzvXZ63sqQgjweiXJp2TUokHqL/18iiMVAU=.sha256

Pragmatic Next Steps

In my opinion our path forward looks something like the following:

  1. We have our process mostly figured. It's sucky but works.
  2. We should transport our current process to a shared spreadsheet as this will allow formulas, to define the logics, do double entry and is an imporvement on what we are currently doing. It's fairly low overhead to get this set up.
  3. We continue to define our requirements and figure out the best course from there...

How does this compare with what y'all are thinking?

cc: @Kieran @Alanna @mix @peg

@kieran %jrO4bryTlYAmjgFgLb71DUURx51ucNqmqBeKMKLEaps=.sha256

I think transitioning to a spreadsheet at the moment is going to be the clearest and easiest mechanism to maintain while we try out other tools. Was a suggestion I made a couple of weeks ago when it was clear writing tx's into a HackMD was unnecessarily laborious and error prone.

Thanks for bumping the MMT tx log. @Dan Hassan. Pet project of mine that does work and is live, although I do think the UI isn't designed for this current concern, its an open ended system and could easily be abstracted / transitioned to another ruby/rails app to add reliability to any system.

@dan %bD6dVU9LtkL8Hboh6X6aWkIn8QrXidsBBMIFT7XHVY4=.sha256

@peg wrote the following the previous thread

@Alanna - i just read your report on tools and loved it! Has filled me with ideas.

I guess right now we are really focusing on payroll - which is not what cobudjet or opencollective specifically are made for. But for sure we want to be able to do other things, like paying expenses, making donations/grants to other groups etc, and there will be a lot more crossover with these tools. Pretty exciting idea to team up with opencollective.

Manually sending transaction info to cosigner(s) is a pain

Thats true. But i think we gotta see this as an opportunity to gather information - it would be good if we could have some way of sending it to the other co-signer that also added it to our accounts at the same time.

User has not chosen to be hosted publicly
@dan %+uZXfQk2xqncQxQiooNw1l76H5KfhlT70/k3ahfi0Us=.sha256

@Alanna mix's stake in the sand method has worked well so far. Happy for you to go ahead and pick a starting point and we can go from there. Speaking for myself I have no preference.

User has not chosen to be hosted publicly
@kieran %l5idy6OAU3ZqnFLN2SICmiyoi1MvZpD/p4P8l2ANgAI=.sha256

@peg I'd written a local spreadsheet for the time-being, was just confirming a final piece of info. I'll post to the shared one that's now live (Thanks @Alanna!), and I'll nudge you when the tx's are sent.

Join Scuttlebutt now