nyxnor
October 13, 2022, 8:21pm
12
Mycobee:
Proposed Solution:
Move all source code to a Gitea instance (I am happy to maintain and have a domain registered). We can use their issues feature to define and prioritize work, and create project boards with clearly defined acceptance criteria as well as Good Starter Issue
tags for new contributors.
We can use scripts to migrate issues from Phabricator to Gitea, and have all the relevant repositories on under one organization which @Patrick can be the admin.
Would like gitea over github thousand times.
Mycobee:
Proposed Solution:
We could easily implement the new Discourse chat plugin for conversations between devs, and perhaps a bit of lighthearted convo too, in case contributors want to get to know each other and build community
Discourse chat seems best because it doesn’t involve using a different platform.
IRC can only be text, and someone needs to host the relay server for clients that disconnects.
Fan of Cwtch, but someone needs to test if it works on Whonix.
Sarah Lewis built an asynchronous and group messaging solution on top of the Ricochet protocol written in Go.
This would be an interesting major addition to Whonix if there are enough resources to package it independently. I will open a ticket depending on feasibility.
/cc @iry because you are interested in Ricochet.
http://gitopcybr57ris5iuivfz62gdwe2qk5pinnt2wplpwzicaybw73stjqd.onion/cwtch.im/cwtch/issues/392
Mycobee:
Building community is important IMO. I think a general chit-chat forum could be good, or a chat for that.
I like getting to know the humans I am working with as people, within their desired privacy parameters of course
I get it, it may not be as productive as the forum as we need to keep things separated by thread, and easy read for every user to understand, but maybe people become more productive when they are happy they can chat with people around them.
1 Like