news



SimpleTicket DEMO Status

The SimpleTicket DEMO was taken down in June for two primary reasons.  First, the demo was getting hacked on a daily basis (the demo was a real install with admin access rights).  Second, the demo was descriptive of a combination of the original code and updates provided by Kate and Peter.  We are very close to the second major release of SimpleTicket and as a result we felt the existing demo was creating a major strain on engineering resources as well as being a poor demonstration of the ticketing system as it now exists.  We are in the midst of the resolving various issues, but as soon as we have the time we will release the demo so you can take a look (this time we will limit admin functions - such as ‘change password’ - you know who you are).

August 1, 2006 | Trackback |

Tags: SimpleTicket , simpleticket , opensource | Bookmark on del.icio.us | Digg It



8 Responses to “SimpleTicket DEMO Status”

  1. matthieu Says:

    hi,

    thx you very much for this crazy piece of soft. I can’t wait for V2 to come :-)
    Since i live in france and my customers speak french do you plan to include a way to translate the software ?

    Good luck

  2. Chris Says:

    After spending the better part of the day installing the svn code and squashing enough bugs to make it run, I’m going to go out on a limb here and say that “its NOWHERE near ready for primetime”. You should put some wording on your website saying that, to avoid a lot of frustration by people that try to use the software. If there once was a functional version of the software, you should at least provide a tarball of that release. As far as I can tell this software is a LONG way off, and it not useable in any way, shape, or form. I’m not sure how you can even try to sell a version of it in this state.

  3. Bill Says:

    So that August 1st date has come and gone. Is the version 2 release going to come? How about a status update? What kind of condition is it in, is the current code on the SVN? Will you be releasing a tarball and a zip?

  4. Anders Says:

    The svn repository is storing Version 1 not the latest code.

  5. ward harold Says:

    I’ve missed my share of dates in the past. I’ll probably miss more in the future - don’t tell my manager I said that! So I’m not upset over missing the August 1st release date.

    I would, however, like to encourage you to consider the Agile mantra of “release early, release often”. To wit, don’t be fixated on resolving every issue; if you release a set of features that are solid and provide value along with a statement of what features to expect in the next release - due in some, small, number of weeks - no one will be upset. I for one am far more interested in leveraging the Simpleticket data model/backend than I am in the UI.

  6. James Says:

    Is anything happening at all? It would be nice to have a response from the team with a status update.

  7. Alexander Muse Says:

    It is interesting, everyone has a different idea on how we should release the code. We released the code internally and we still are not happy. After integration of our version one data into the version two of the code we found a number of areas that need work.

    Chris (see above) thinks we should wait until the code is ready for prime time and Ward suggests, “release early, release often”. I guess there is a happy medium. We are swamped with work right now, our internal customer (Architel) is clamoring for the stats features to be turned up in our internal version so there is a good chance the code will be released eventually. On the other hand we have quite a few paying projects, not to mention our Big in Japan projects. If you know of any more Ruby on Rails programmers looking for full time work we have openings for three coders right now.

    So, Alex’s team is shooting to release at Barcamp, Texas. That is two weeks from now. Cross your fingers.

  8. Jonathan Says:

    Hey guys. We are looking for working Ruby ticketing system and well i’m guessing this is it. However i’m a little concerned about the project status. We really need something fairly stable that we can work on. I have two internal Ruby developers that i can task to assisting in development when we are in down time if someone is interested in talking about that. Also we are interested in extending the ticketing functionality to include more of a complete IT management platform. ie. Billing, Stock Control, Credits, Project work and Customer Contract Management.

    If you guys are interested please drop me a line and also an idea of wether the system can be made fairly stable or not would be good.

Leave a Reply