Slashdot Mirror

← Back to Domains

Domain: fsck.com

Stories and comments across the archive that link to fsck.com.

Comments · 16

  1. Re:Old old story. by think_nix · · Score: 4, Insightful · on Amazon Kindle Proprietary Format Broken

    Not only that but also Jessie Vincent showed at oscon (his 5 minute speech starts at 2:13 on the video) How he already reversed engineered and installed ubuntu 9.04 on the Kindle. After watching his presentation and hearing about all the crap amazon actually does with these things, I am surprised anyone would still even consider buying one.

  2. Re:PDF SUPPORT? by bhartman34 · · Score: 1 · on Ubuntu 9.04 On Kindle 2

    For the Kindle 2, you can use Savory. It's a version of Calibre (which he mentioned in the presentation) ported to run natively on the Kindle 2. I've got the original Kindle, so I've been using Calibre to do the conversion on my desktop.

  3. Thank you to by ectoraige · · Score: 1 · on Unsung Heroes of Open Source

    Jesse Vincents who took req and ran with it to develop RT.

    Thank you, sir.

  4. Re:Show some initiative by babbage · · Score: 4, Informative · on Making the Case for Better Bugtracking Tools?
    No, please don't use Bugzilla -- it's reputation far exceeds its actual quality. Bugzilla is an arcane, tightly bundled colledtion of hard to extend CGI scripts sitting on top of a bizarre MySQL schema. If it doesn't exactly meet your needs (i.e. you are not the Mozilla project), extending it can be a nightmare.

    May I humbly suggest that you take a look at RT: Request Tracker instead. RT is a general purpose ticketing system, suitable not only for bug tracking, for for all kinds of organized message exchange within an organization (i.e. help desk, sales force tracking, some aspects of inventory management, etc). RT allows users to collaborate via a web interface, email, or the command line. By providing multiple interaction interfaces, RT encourages users to work with the system by communicating the way they would already, rather than working against them by forcing them to adapt to a wholly new system. If you don't like the web interface, feel free to change it. If it's still not enough, people can just use email instead -- just cc: your RT account on ticket related mails, and include the ticket number in the subject line. Hey presto, people can do almost what they were doing in the first place.

    RT is written in clean, OO Perl making wise use of CPAN libraries instead of implementing everything from scratch. It will run on a variety of operating systems & databases (MySQL, PostgreSQL, Oracle). The system is well documented, easily extensible, and comes with a vibrant & supportive user community. It can even be integrated with things like pagers, so that the creation of critical tickets can send out a pager message to key personnel.

    All in all, RT is a very nice, very well engineered system that IMO is far more suitable for most users than Bugzilla, for which the suitable scope is much more restricted. That's why RT is now being used in, among other places, Perl's bug tracker at rt.perl.org.

    Disclaimer: My company uses RT, and I have met Jesse Vincent, RT maintainer, a handful of times, and even though I think it would be pretty cool if people switched to RT and bought support contracts from Jesse, I have nothing to gain if any of this happens. I just sincerely think that RT is better software than Bugzilla for almost all users, and would like to see development of the software continue to flourish and become accepted more widely. Spend a week messing around with RT and IMO you'll never want to go back to Bugzilla...

  5. Re:Show some initiative by babbage · · Score: 4, Informative · on Making the Case for Better Bugtracking Tools?
    No, please don't use Bugzilla -- it's reputation far exceeds its actual quality. Bugzilla is an arcane, tightly bundled colledtion of hard to extend CGI scripts sitting on top of a bizarre MySQL schema. If it doesn't exactly meet your needs (i.e. you are not the Mozilla project), extending it can be a nightmare.

    May I humbly suggest that you take a look at RT: Request Tracker instead. RT is a general purpose ticketing system, suitable not only for bug tracking, for for all kinds of organized message exchange within an organization (i.e. help desk, sales force tracking, some aspects of inventory management, etc). RT allows users to collaborate via a web interface, email, or the command line. By providing multiple interaction interfaces, RT encourages users to work with the system by communicating the way they would already, rather than working against them by forcing them to adapt to a wholly new system. If you don't like the web interface, feel free to change it. If it's still not enough, people can just use email instead -- just cc: your RT account on ticket related mails, and include the ticket number in the subject line. Hey presto, people can do almost what they were doing in the first place.

    RT is written in clean, OO Perl making wise use of CPAN libraries instead of implementing everything from scratch. It will run on a variety of operating systems & databases (MySQL, PostgreSQL, Oracle). The system is well documented, easily extensible, and comes with a vibrant & supportive user community. It can even be integrated with things like pagers, so that the creation of critical tickets can send out a pager message to key personnel.

    All in all, RT is a very nice, very well engineered system that IMO is far more suitable for most users than Bugzilla, for which the suitable scope is much more restricted. That's why RT is now being used in, among other places, Perl's bug tracker at rt.perl.org.

    Disclaimer: My company uses RT, and I have met Jesse Vincent, RT maintainer, a handful of times, and even though I think it would be pretty cool if people switched to RT and bought support contracts from Jesse, I have nothing to gain if any of this happens. I just sincerely think that RT is better software than Bugzilla for almost all users, and would like to see development of the software continue to flourish and become accepted more widely. Spend a week messing around with RT and IMO you'll never want to go back to Bugzilla...

  6. Bug tracking by m_ilya · · Score: 2 · on Interview With The KDE And GNOME Release Managers
    the world's best bug tracking software

    Bugzilla is way far from being the best bug tracking software. For example just compare it featureset with RT.

  7. RT by jkujawa · · Score: 5, Informative · on Cross Platform Help Desk Applications?

    http://www.fsck.com/projects/rt/
    RT is very good. I've never heard anyone say a bad thing about it. It is very much worth checking out.

  8. Us.. by Xunker · · Score: 4, Informative · on Cross Platform Help Desk Applications?

    We (my company, that is) uses this. It's web based totally and extensible with perl.

  9. About that competition... by Anonymous Coward · · Score: 0 · on Mozilla's 100,000th Bug

    To an RT user, this article comes off as a troll. Covad's installation of RT has long since passed the 500K-ticket mark.

  10. look at RT by ckolar · · Score: 3 · on Open Source Help-Desk Software?

    We recently deployed RT (www.fsck.com/projects/rt/). It is a compact system with email, web, and command line interfaces. The stable version (1.x) does not allow the requestors to check the status via the web, but v2 (which is now at beta 2) does. If you check the status page of the web site you can get into a server running v2 to check it out. We have fallen in love with it and it is chugging happily away on a P120. It is implemented using mod_perl and mySQL, it took all of 5 minutes to get up and running. Cheers.

  11. Mod this question "-1: Didn't check Google" by penguinboy · · Score: 1 · on Open Source Help-Desk Software?

    Here are two systems I found in less than five minutes:

    The Open Directory is also a good source of information - the have a whole page of Help Desk programs (though not all are OSS).

  12. RT by ASaidi · · Score: 1 · on Web-Based Helpdesks?

    Request Tracker is a very useful web tech support program. It is available at: http://www.fsck.com/projects/rt/index.ht ml

  13. There are MANY resources out there. by BigEd · · Score: 5 · on Web-Based Helpdesks?
    Check out this page for a list of most if not all of them. It has synopsis, and reviews.

    RT, Keystone, and php Helpdesk would be good starting points.

  14. RT trouble ticketing system by WebTurtle · · Score: 1 · on Trouble Ticket Systems?
    You may want to look at RT (Request Tracker). It is an open-source GPLed trouble-ticketing system created by Jesse Vincent. They are about to release version 2. It has SQL backend, and is quite sophisticated.

    http://www.fsck.com/projects/rt/

  15. The next big internet failure by Jeffrey+Baker · · Score: 1 · on MP3.com Going Public
    Is there an open contact-list protocol yet that isn't owned by Microsoft?

    The IETF has formed an Instant Messaging and Presence Protocol working group. Their mailing list archive is at http://lists.fsck.com/cgi-bin/wilma/pip

  16. Two points by Chris+Hanson · · Score: 1 · on Open Real Time Messaging System
    A couple of thoughts I had on reading this item.
    1. Zephyr

      It works, it scales (somewhat), it supports real authentication, it's open, it presents the right paradigm for instant messaging and online discussion. (Since I used it heavily at CMU, using AOL Instant Messenger, IRC, and ICQ is just painful.)

      Go to ftp://athena-dist.mit.edu/pub/ATHENA/z ephyr/ to download the source.

    2. IMPP

      There's an effort underway by the IETF to come up with a standard protocol for instant messaging and "presence information" called IMPP. Anyone considering working on a project like this should get in the loop so they can make sure all their bases are covered, and so that they can interoperate with others' servers.

      Go to http://lists.fsck.com/cgi-bin/wilma/pip for mailing list archives.