Changes from last sprint:
Thanks to our new addition, @dannymate, there are now three editors. The editors can thus take on more organizational tasks this sprint than last.
Every week we will now ask members to tell the editors, what tasks they want to try to complete in the week and check in with them at the end of the week to see how they have been progressing.
The weekly reports will be published on Wednesday for this sprint. A week for guild purposes is now from Wednesday to Tuesday. This is so we don’t have a deadline every Monday and we can all enjoy our weekends a little more.
As there are now three editors, we want to devote more time to recruiting and coordinating members. This means that we will be always looking to integrate new members into an ongoing sprint.
As part of our strategy for recruiting new members, we have also started a Kbin Magazine to post about the current state of the Guild. We’ll post about ongoing challenges, updates and recruit new members there.
The proposal phase is going to continue until Wednesday 20th, when we’ll publish the next weekly report containing a description of all proposals made up to that point. All members who have signed up through our form up to that point will receive a link to vote on the proposals. The decision will be announced in an irregular weekly report and a blog post on the 22nd.
This week was the proposal phase of the sprint.
- LibRate ActivityPub Support
- Kbin Moderation Application
- Use magic-links to make issue trackers on Forgejo more accessible
Anyone was open to make a proposal through our form.
The vote between these proposals is currently taking place and will end Friday 00:00 UTC.
This week, @axiomizer and @kiend joined the Guild. This means that we currently have 5 active members.
We are always looking for new members to join us. So, if you want to join, please contact us or fill out the form.
There’ll be an irregular report on Friday to declare the proposal that was accepted by the Guild.
At that point, development starts with a check-up day on Saturday. All members should try to be available
at least part of that day, both to get-to-know each other and to start organizing the sprint into tasks.
The initial tasks will most likely be discovery tasks with the goal of investigating the project & creating
more concrete tasks with a difficulty rating and time estimation required.
The editors will then start with check-ins and the promise system.
The result of the second ballot is in.
A strong majority has selected LibRate ActivityPub Support as the project to work on during this sprint. The results of the ballot can be reviewed here
- Kick off task management with Taiga.io as our Kanban
- Invited members to the Guild Alpha Codeberg organisation
- Work on setting up a developer environment
- Defining initial tasks around ActivityPub, Webfinger and discovery of the LibRate project.
- We are going to using Fediverse Pasture for testing our ActivityPub implementation. Thanks to @helge for their advice.
- Lay out steps towards reaching the first proposal Milestone (Well technically we’re doing Milestone 2 first now.) and break down tasks into workable chunks.
- Assign Subject Matter Experts for: Svelte, Go, WebFinger, DevOps and ActivityPub in LibRate.
- Research Go Crypto Libraries to prepare for HTTP Signatures library [Go]
- Research Webfinger & how to implement it in LibRate [WebFinger]
- Research AP Actors and how to serialize them [ActivityPub]
- Research AP inboxes and how to process them (research background tasks in LibRate) [ActivityPub]
- Begin front-end research of Milestone 1 [Svelte]
- Indentify improvements to spinning up local development environments [DevOps]
The goal of this initiative is to always have someone able to take the lead on indentified important topics. Members pick up a topic, learn about it and can lead discussions around it. Of course, Members will be able to work on tasks outside of their subject matter.
ActivityPub - Open, decentralized social networking protocol. You know the one that serves as the basis for the Fediverse.
WebFinger - Often paired alongside ActivityPub. Allows for discovery of information about people and things identified by a URI.
Go - The back-end language for LibRate.
Svelte - The front-end language for LibRate. Also SvelteKit may need to be researched.
DevOps - Focus on bringing a good DX experience to members working on LibRate in this sprint.