61–70 of 193 posts
That does look like a pure copy of Linear UI wise
> See what 2,300+ folks in a forum get up to oh okay > Join our Discord sadness. where's the forum?
It’s funny as I think discord is actually kind of harder to get into than the old irc method. With irc there was no history or permanence so there was a relationship between discussion and what made it into the project as source or docs. With discord it’s weird because the expectation seems to be on me to wade through hundreds or thousands of messages to find docs because there are people who hang out and read everyt…
> See what 2,300+ folks in a forum get up to oh okay > Join our Discord sadness. where's the forum?
A hard pass from me, especially when an answer to a simple question requires me to drink from their firehose of a search...
It's not so much "not JIRA", it's that managing code bases outside of the code base is hard and awkward. And due respect to fossil-scm, I don't know if any way to do it otherwise. The goal here is to look at something that tells an organisation why chnages to a codebase occurred. Each individual commit can have a nice explanation (in a given human language) of why that specific change occurred. But how does one link…
Ticketing systems are useful for a lot of other things such as keeping track of work on an individual level, or managing project resource allocations on a company wide level, but I'm not sure it's the best tool to do audits and have accountability. It will at best be a secondary source of that data.
Earlier quoted context omitted.
It’s funny as I think discord is actually kind of harder to get into than the old irc method. With irc there was no history or permanence so there was a relationship between discussion and what made it into the project as source or docs. With discord it’s weird because the expectation seems to be on me to wade through hundreds or thousands of messages to find docs because there are people who hang out and read everyt…
Discord does have an okayish search feature which gave me a desired answer most of the time I joined a server because of a particular program I had. Enormous downside being that you have to guess the previously used wording if you don't have an error message or something.
So while it is in the interest of the open source project that as many people going forward can benefit from past Q&A, it is in the interest of Discord to require you to install their client to search.
Silos are sad.
It's not so much "not JIRA", it's that managing code bases outside of the code base is hard and awkward. And due respect to fossil-scm, I don't know if any way to do it otherwise. The goal here is to look at something that tells an organisation why chnages to a codebase occurred. Each individual commit can have a nice explanation (in a given human language) of why that specific change occurred. But how does one link…
Most Jira "alternatives" don't really get Jira in first place.