I have seen quiet a few people offering to help. . asking how to help. . . the fact is that we have no clue how to pitch in. You want patches and fixes? Then give us access to the new branch. Why would I waste my time working on patches to the 1. x branch when 2. x is allegedly so close to being released? You want community involvement? Great - give us avenues to help you. Tell us what we can do. And not via PM - put posts up, get discussions going. Get the code up, bugs and all. Give us project overviews, status updates, bug lists, feature lists. You can't expect a community to help, when you give us nothing to start with. If we have to jump through hoops, we are not going to. If there are easy ways to contribute, then people will. I have seen this over and over with open source projects. The ones that succeed are the ones that are easy to contribute to.
You have a great product. Build the community and it will flourish. Stunt it's development and your users will flock elsewhere.
-Barnstormer
You have a valid point to all of this and you're preaching to the choir. However, I am not a developer. I've made attempts contact the developers, but contact to them is limited to PM's from what I've seen.
The source code is copyright by Digital Frontiers and the same developers for eTicket also develop Help Center Live.
I've been going through the bug reports on my own time trying to fix them, but I (by myself that is) can only do so much.
I've seen screenshots of version 2 and I can tell you that they look great! I don't have the source code for it though, so I can't help you in that regard.
June 22, 2008, 08:16:18 AM
