3 ms·

Thanks for adding us. Here's a little background on why we built Manuscript: We launched FogBugz back in 2000 as one of the first bug-tracking systems around.

Thanks for adding us. Here's a little background on why we built Manuscript: We launched FogBugz back in 2000 as one of the first bug-tracking systems around. Since it launched, the platform has been used to fix over 50 million bugs, by tens of thousands of teams around the world. But recently, we’ve been thinking about “Big Bugs” [0], trying to imagine how we can address both the necessary parts of shipping software and the larger risks that too often get overlooked. So today, we’re using that same engine to create something new: Manuscript. See our launch post for further info: https://medium.com/make-better-software/introducing-manuscript-aa4aabdc0f6c https://medium.com/make-better-software/introducing-manuscri... [0] https://medium.com/make-better-software/software-matters-in-the-world-f24d25b255d7 https://medium.com/make-better-software/software-matters-in-...

aeorgnoieang 9y ago
This is a really aggravating comment. It's content-less marketing drivel. You didn't 'build Manuscript'. You just changed the name of an existing hosted issue/ticket management service. And you've made some cosmetic changes to the client-side code that uses the 'FogBugz engine' (back-end code). And now you're spouting really insipid bullshit about "Big Bugs". Please excuse my intense skepticism about that being anything other than nothing. There's a few things I still like about FogBugz versus its 'competitors' – creating a 'case' (issue/ticket) from an email, being able to create hierarchical trees of cases, and being able to search cases. But everything else has been stale for a long time. You don't even have real integrated version control! Kiln is about as basic of a web wrapper around Git as possible. Or maybe the code reviews are okay? I don't know. I've never used them nor ever heard or read of anyone else doing so either. Why's Kiln off on its own? Hosting a Git repo isn't exactly trivial if you're offering it for free, but you killed the free plan a while ago and I don't think anywhere near as many people as are using GitHub have ever even known of Kiln. The propose UX improvements are also very very un-inspiring. To whom is FogBugz – I mean Manuscript – going to be marketed? Because it certainly doesn't seem to be programmers.
- GarethX 9y ago
  Sorry to hear I've aggravated you! There's more to it than cosmetic changes. Relevant to your comment is the new integration experience, which leverages Glitch. This enables you to connect up your other tools easily, so you can use the best tool for the job, like GitHub for integrated version control. As well as other tools like Slack, Trello and Google Docs.
  - aeorgnoieang 9y ago
    I'm sorry I'm being so aggravating too. We're hurt most by those to which we're closest! I've been using FogBugz for almost a decade now, and it's been overall really positive. But I'm sad that it hasn't really kept up. You mentioned using other tools – "like GitHub for integrated version control". I can't understand why anyone would use GitHub and FogBugz/Manuscript. GitHub already does pretty much everything FogBugz does, plus it's like 'embedded version control' instead of just 'integrated'. Maybe Anil will push thru some fucking Markdown support tho before I'm finished migrating to GitLab. You guys (the extended Fog Creek family anyways) are probably half the reason why Markdown has been so widespread [i.e. Stack Overflow]. FogBugz has been marketed forever as being just for making software! How can you have relegated all of your users to using 'rich text' for so many years? Why?! (Also, would you please add a 'description' to the cases so everyone can see, at the top of the case, a checklist [written in Markdown!] with everything that needs to be completed before the case can be closed? And how 'bout some case description templates too why'll you're at it?)
    - GarethX 9y ago
      Thanks for the feedback, I'll pass those suggestions on. One big reason why people use us with a GitHub integration is that GitHub is almost entirely used by developers only, and yet creating software requires input from people across roles and departments. Manuscript with GitHub integration means you can collaborate across your whole organization, and involve Design, Support, Marketing and other teams, while developers still get to use the version control system they want.
    - anildash 9y ago

aeorgnoieang 9y ago

This is a really aggravating comment. It's content-less marketing drivel. You didn't 'build Manuscript'. You just changed the name of an existing hosted issue/ticket management service. And you've made some cosmetic changes to the client-side code that uses the 'FogBugz engine' (back-end code). And now you're spouting really insipid bullshit about "Big Bugs". Please excuse my intense skepticism about that being anything other than nothing. There's a few things I still like about FogBugz versus its 'competitors' – creating a 'case' (issue/ticket) from an email, being able to create hierarchical trees of cases, and being able to search cases. But everything else has been stale for a long time. You don't even have real integrated version control! Kiln is about as basic of a web wrapper around Git as possible. Or maybe the code reviews are okay? I don't know. I've never used them nor ever heard or read of anyone else doing so either. Why's Kiln off on its own? Hosting a Git repo isn't exactly trivial if you're offering it for free, but you killed the free plan a while ago and I don't think anywhere near as many people as are using GitHub have ever even known of Kiln. The propose UX improvements are also very very un-inspiring. To whom is FogBugz – I mean Manuscript – going to be marketed? Because it certainly doesn't seem to be programmers.

GarethX 9y ago
Sorry to hear I've aggravated you! There's more to it than cosmetic changes. Relevant to your comment is the new integration experience, which leverages Glitch. This enables you to connect up your other tools easily, so you can use the best tool for the job, like GitHub for integrated version control. As well as other tools like Slack, Trello and Google Docs.
- aeorgnoieang 9y ago
  I'm sorry I'm being so aggravating too. We're hurt most by those to which we're closest! I've been using FogBugz for almost a decade now, and it's been overall really positive. But I'm sad that it hasn't really kept up. You mentioned using other tools – "like GitHub for integrated version control". I can't understand why anyone would use GitHub and FogBugz/Manuscript. GitHub already does pretty much everything FogBugz does, plus it's like 'embedded version control' instead of just 'integrated'. Maybe Anil will push thru some fucking Markdown support tho before I'm finished migrating to GitLab. You guys (the extended Fog Creek family anyways) are probably half the reason why Markdown has been so widespread [i.e. Stack Overflow]. FogBugz has been marketed forever as being just for making software! How can you have relegated all of your users to using 'rich text' for so many years? Why?! (Also, would you please add a 'description' to the cases so everyone can see, at the top of the case, a checklist [written in Markdown!] with everything that needs to be completed before the case can be closed? And how 'bout some case description templates too why'll you're at it?)
  - GarethX 9y ago
    Thanks for the feedback, I'll pass those suggestions on. One big reason why people use us with a GitHub integration is that GitHub is almost entirely used by developers only, and yet creating software requires input from people across roles and departments. Manuscript with GitHub integration means you can collaborate across your whole organization, and involve Design, Support, Marketing and other teams, while developers still get to use the version control system they want.
  - anildash 9y ago