Open 9rb opened 6 years ago
@9rb please send your name and email to ops@rchain.coop
sent. Thanks..
On Wed, Jan 17, 2018 at 4:20 AM, HJ Hilbolling notifications@github.com wrote:
@9rb https://github.com/9rb please send your name and email to ops@rchain.coop
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rchain/Members/issues/217#issuecomment-358244674, or mute the thread https://github.com/notifications/unsubscribe-auth/AV1jjBRK7Frf5n8pJ68KJQ6rthVZ5QlGks5tLbtogaJpZM4RRJVW .
--
Other than raising the issue, I don't see any progress here in January. I'm adding a comment here so I can get my name in a slot to reward @9rb.
@Ojimadu regarding the other rewards you assigned, did you base it on some progress that isn't mentioned here? Point me to it or describe it, please?
working draft of requirements and thoughts on how we can use this as a testbed for Rholang
Please sign the draft, give status, and give links to context such as this issue.
@dckc Just to clear things, I did not assign any reward neither did I set a budget on this issue. I saw a budget of $400 under my name I dont know how that came to be as I did not participate in this issue and I am not among the participants or assignees. Please edit your post above.
Will do. I'm on mobile just now.
Looks like we ought to keep a keen eye on the budget program.
@jimscarver I'd like to propose a working group on this while @kitblake is in Tampa next week.
@patrick727, Yes, lots happening on the sheet lately from disappearing and appearing names, to random budget setting like in my case above. I really like what @dckc is doing on issue #260. Hopefully, we can get to adopt that when he is done. @dckc I suggest creating a new issue for your work. We can move this discussion to #260 or on the new issue if you decide to create it.
@dckc, will follow those guidelines for signature, status, links to context etc.. getting up to speed on that :-)
perhaps SL on github may be of most interest to the board and members at this time, since a lot of activity monitoring and analysis are focused there?
@jimscarver @9rb I'm interested in looking at the source code for social ledger -- 1.x, 1.5, and 2.x. I'm struggling to find it. Got any clues for me?
The social ledger prototype code is not ready for public access. Send me your preferred email access and I will add you to our gitlab repository @dckc
I've created the github repo https://github.com/DigitalLifeCollective/basecamp for social ledger 2.0 development but haven't committed code yet. I should get around to it soon. There is not yet any real code as we are still making decisions about the architecture and tools
yawn. Wake me when it's shared publicly.
Explore RChain requirements and architecture alternatives to implement social ledger on platforms of interest to RChain, in their priority order. Deploy current SL on Discord, so RChain team can play with it and provide feedback and requirements from that context -- i.e. prototype based requirements gathering, rather than from cold. Discord does not support markdown (no way to embed URL, click on it and have it do something). We may need to provide folks a link that they can follow to act on those.
A strech goal is to explore SL implementation using Rholang (eat our own dog food).