Gregory's Server
@fedor that's fine if you use git for yourself (I have a git server with my personal projects that doesn't even run a web server). But if you build something that other people are likely to use too, then I think that it's important to show it on something that most people feel familiar with (unless you're only targeting a small niche of geeks). I feel like there's a lot of interesting software on #Sourcehut that could definitely benefit a lot of people, but most of those who aren't hardcore geeks don't even know what to do with a webpage that seems to be teleported straight from the 1990s and projects that don't even have a wiki or a couple of lines of documentation.
|
2 comments
 I think in many cases there's a mismatch in 'expectations management' that causes burnout in maintainers. Once a project grows in size and popularity the dynamics change to a large extent. And if the maintainers don't deal with that they'll see the burden and the expectations grow and grow. Entitlement may be false entitlement in their eyes, but users on the other hand also 'invest' by using the software. In part it is communication mismatches that cause things to go awry. |
@blacklight I highly disagree on the statement "you do something useful -> bear the obligation of making it X". Its a giant source of burnouts in open source.
No, you did something and decided to make it public in the way you like it - awesome! You love sourcehut interface and a mailining list as the way of communicating - awesome, that's your project and your decisions.