@elieuw I'm on a 6-person team of sysadmins looking after a few servers. We are students. We spend on average.. dunno.. 1h a week? on administrating these servers. We need to balance it with our university classes. Our job could be easily done by one person working half-time, or even less.
And we're struggling. Our servers need more time, several big things need to be done. But this requires having knowledge about what's on the servers already, learning about the new stuff, and deploying it.
@elieuw but these tasks often have a common context, some pieces of knowledge and coordination that need to be known and consistent across people doing these tasks. If you add more people, the communication overhead increases.
So, comments. On file lines, on diff lines, or on pull requests. How do we implement them? And is a pull request basically sending "hey can you pull ac7f... from git.example.com/..." over your favourite communication method, or do we need something more formal?
@rysiek@codewiz@dashie IMO wikis could easily be either a separate branch or a subdir in the git repo, only needs a CI to render it. (btw. CI doesn't need federation at all)
issues... I have a feeling the solution will become apparent once we have figured out how to do comments/reviews.
@rysiek@codewiz@dashie IMO for short-term solutions it'd be cool to evaluate which of the following can be implemented on top of git or APub: - issues - wikis - comments/reviews - any other important feature of github I missed?
@cjd@gc IOW "it's ok, just keep doing whatever you are doing, and everything will be fine." or "God has a plan and it's way better than anything you could come up with"
@HerraBRE @rysiek One of the most important things I've learned about security during last few years is that it consists of not just Confidentiality and Integrity, but also Availability. So a situation where you can't connect to a server, or decrypt a message, is still treated as a security failure. There's often (always?) a tradeoff between Availability and the other two components, but it's not true that security people don't care about Availability.