I noticed a few comments from Ward and Vince regarding the status of SimpleTicket as an open source project. To Ward’s question, “…does this mean that SimpleTicket is no longer open source?” Absolutely not, we are committed to keeping SimpleTicket open source using the GPL.
To Vince’s answer, “…he took it back in house to develop.” The hard part about building software is deciding what to build. In the end we need SimpleTicket for our business and we must have certain features. One day I looked at the demo version and it looked nothing like the software we had intended, instead it was circa 1999 radio buttons. I proposed to the two most active non-Architel developers that they continue the project with their vision and we would continue a different project using our vision. They decided they would rather complain than to continue their own version of the project.
To meet our deadlines (we had missed our May deadline working with the community) we hired coders to complete the second version of SimpleTicket. Once it is released we would love to start building a community around the project. Ward, we would love to have you on board. But just as I said to the other developers, I don’t want you to waste your time on code that will never find its way into SimpleTicket. By working together we can make sure that we all get what we want. Go ahead and wait for the new code and if you like it and want to get involved please give me a call or send me an email.
July 6, 2006 |
Trackback |
[4] Comments
Tags: SimpleTicket , Rails , Architel , Ajax , Ajaxian , Biginjapan , simpleticket , rubyonrails , bij , podcast , podserve , alexleverington | Bookmark on del.icio.us | Digg It
Several of you have emailed asking for updates on the new code and instead of replying individually we decided to post our progress here.
We have built a secondary code repository and a new deployment server to demonstrate advances. Our current estimates are that we will have our next release ready for internal review within 17 and 22 days. Here is the breakdown:
- ticket search engine, creation, update and ajax calls (6-7 days)
- customers, users and engineer implementation (2-3 days)
- client side interface recoding (4-5 days)
- statistics (1-2 days)
- bug fixes, performance optimization and rss (4-5 days)
The latest code was delivered today and included ticket lists and customers list with all views detailed in the version 2.0 wireframes. The code is 100% new (rails/xhtml/css) with database access. We are generating some very nice code!
June 20, 2006 |
Trackback |
[2] Comments
Tags: SimpleTicket , Rails , Ajax , simpleticket , code | Bookmark on del.icio.us | Digg It
I thought it might be helpful to restate what ‘our’ mission was when creating a SimpleTicket.
Architel wanted to create a ticket system that was SIMPLE and easy to use. We wanted to take advantage of cool presentation features like Ajax and great UI (we still need some help there) for the users. We did not want to create a ticketing system that could do everything, just a few things well. Less is more was our moto. There are several other open source ticketing systems, but none of them were right for our company. Why? They were written by people who wanted to use them instead of for the people who needed them Just spend some time with them. They have way too many options and features and those option and features make them terribly difficult to use. Most traditional (low tech) businesses don’t use ticketing systems because they are 1) too expensive and/or 2) too complicated to understand. We want SimpleTicket to be written for any business with between 1 and 20 IT professionals. We don’t want SimpleTicket to be written to support an ISP or an IT support company.
To summarize, SimpleTicket should be:
- Simple
- Easy to Use
- Easy on the Eyes
- Limited Feature Set
- Perfect for an IT department (1-20 IT professionals)
That said, we know that there is room for other versions of SimpleTicket. More complicated and feature-rich versions. Perhaps once the code is clean and the release is stable we can create a permanent branch called SimpleTicket Pro. In any event, our roadmap (after the next two releases) includes an API that will allow anyone to create any sort of ‘plug-in’ they desire for SimpleTicket. This way, you can make SimpleTicket as complicated as you want to. We will keep thinking about having a ‘Pro’ branch/version, but be certain that our plug-in strategy will allow for almost any use desired by the community. But we never want to lose sight of our target client – keep SimpleTicket simple – please!
April 3, 2006 |
Trackback |
No Comments
Tags: SimpleTicket , Ajax , simpleticket , opensource , simple , smb , mission | Bookmark on del.icio.us | Digg It
Kevin did a great job presenting SimpleTicket at BarCampDallas. Woot! The source code has been released, now the real work begins - with the community (that hopefully) will be formed around the tool.
What is SimpleTicket? Think simple, easy to use trouble ticket system freely distributed via the GPL license written using Ruby on Rails with Ajaxian goodness.
January 28, 2006 |
Trackback |
[3] Comments
Tags: SimpleTicket , Open Source , Trouble Ticket , Rails , Ajax , Ajaxian , Ruby on Rails , barcamp , barcampdallas | Bookmark on del.icio.us | Digg It
Source posted on the SourceForge…
Download from here!
SimpleTicket is an open source trouble ticket system written using Ruby on Rails. NOTE: THIS IS THE FIRST RELEASE (pre-Beta). Lots of you wanted to help us finish all of the features so we have posted the source. Also, check out the SVN:
svn co svn://project.simpleticket.net/trunk
January 28, 2006 |
Trackback |
[14] Comments
Tags: SimpleTicket , Ajax , digg , simpleticket , rubyonrails , sourceforge , ticketsystem , opensource | Bookmark on del.icio.us | Digg It
— Next Page »
