Until I update the Vervis UI to allow ticket search by tag, I’m collecting here potential tasks with which I’d love to get some help, or that are relatively small and self contained collaboration ideas, especially for the weekly Peers projects jam.
ForgeFed and federation
Collect vocabulary items for ForgeFed: Look at the UI, at the JSON API and at the DB schema of a forge such as Gitea or GitLab CE, and make a list of properties for some object/type. For example, all the properties of an issue. Or a merge request. Or an issue comment.
Feedback on modeling of federated open-ticket: Read the “TODO” parts in ticket #50 and let me know what you think :) I’d like to decide on a good secure future proof strategy
Read about WebMention, how can it be used here for federation?
Read about IndieAuth, how can it be used here for federation?
Write requirements and user stories for Continuous Integration: I never used CI so idk much about how it works, it would be nice if someone who uses CI could describe it, how you use it, how it works for you, what you gain from it etc.
Test features on Vervis and document result: think of some operation to do here, such as register, login, open a ticket, etc., and what you’d like it to look like. Try it here, document your steps, the results, did they match your expectation, ideas for improvement etc. You can document by opening a ticket here. If that doesn’t work, paste your text somewhere and ping me (fr33domlover) on #peers @ Freenode or email me (same username, at riseup.net). Examples for things to check: