person backing up his car exploitable with the following four panels:
- person looking ahead. the text below him says, “wow a cool software. let’s check out the community”
- screenshot with the text
Community
The main place where the community gathers is our Discord server. Feel free to join there to ask questions, help out others, share cool things you created with Typst, or just to chat. - hand on gear shift zoomed in, switching to reverse
- person looking behind with the text “nevermind”.
You don’t have to. Fork it, make it better. Crush the existing developers, see them driven before you and hear the lamentations of their Patreon donators.
It’s open source software. Forking and improving is a core feature.
If people have a decent idea but a shit implementation, supercede them.
Sure. If you need software support, build a support system and get everyone else to use it. Makes perfect sense. I hope you live exclusively by this principal.
What? This is about documentation and maintenance of an open source project, this isn’t a SaaS situation.
If your documentation sucks, you’re no better than the discord hell the original project came from.
And yes, I only work with open source projects that are run well, or I fork them and maintain them for personal use.
I’m interested, what’s your process for ‘personal’ forks? Any extra steps?
The one discord thing I do is mention I am making the fork, then spend the first while doing the documentation I wish existed. I set up the repo to accept issues and allow discussion.
Conan the Developer has spoken!