GM! Where is v2 happening and how can General magic help finish it off?

[GriffGreen]

GM Wesley! We would love to make sure tokenlog v2 is ready by september to be used by Grassroots Economics for voting on their Commons :-D

@rbsal97 would be our project manager to take it on, tagging him here so I don't lose track!

[rbsal97]

Hi Wesley! Would like to have some more information and details for us to Fastrack and make preparations for this project.

My TG and Discord lines are open for faster discussions.

[wslyvh]

Hi @GriffGreen @rbsal97

Thanks for reaching out. As you might know, I haven't been able to develop / maintain this lately. Been pretty much stale for years now. The V2 is probably at 80% or something right now at the next branch https://github.com/wslyvh/tokenlog/tree/next

Which should be a more stable/robust and performing version (build on Next.js) Let me know how you want to approach this? Do you want to contribute to this repo or should we look at migrating this into an org/repo that the commons team has access to?

[rbsal97]

Hi @wslyvh, can I schedule a call with you early next week to discuss this further? Ill be initiating this call and will relay to our dev the outcome of our meeting.

The agenda (Open for discussion) would include:

1. PRD
2. Tokenlog Current State and Future State Discussion.
3. MVP
4. Timeline

Please let me know what time are you available for this :D

[wslyvh]

Had some time to start things up again @rbsal97

V2 development has been going on at the next branch. As said, I think it's roughly 80% done. https://github.com/wslyvh/tokenlog/tree/next

You can try and test it out at (DAI voting on this repo) https://tokenlog.vercel.app/wslyvh/tokenlog

What's left here is saving the votes itself.

1. on the front-end, votes are passed through the components to the context/vote-context to a function called vote. There's a TODO comment there which should POST /votes the vote to the back-end.

2. On the back-end, this doesn't exists yet. The votes service exists at /api/votes but doesn't exists or handle it yet. It should do some basic checks (vote is valid, no race-conditioning, etc.) and pass the vote on to the repository/voting to save it to the DB.

It seems like that's it, although it probably requires a bit of testing and fine-tuning (it's been a while, sorry)

V2 requires 2 env variables DB_CONNECTIONSTRING - which should be a valid MongoDb connection string (I use Mongo Cloud, Atlas) GITHUB_ACCESS_TOKEN - a valid personal access token to access the Github API

Happy to help get a dev up to speed. Also open to migrating the repo into an org that the team has better access to

[rbsal97]

Hi @wslyvh

Our dev is currently looking at it. He mentioned he can implement the last changes. We will be sending you the timeline once we finalize it with him. We can also create a bridged channel on discord for better communication. We will be also migrating this repo to GM for better access.

cc: @GriffGreen

[rbsal97]

Hi @wslyvh,

Our dev has already mapped out the missing components but he asked if you have time for a quick call just to ensure we are on the same page.