Hello All,
It's been 5 days now since the announcement that I'll be taking the lead on the Tickets CAD project. I wanted to share a status report with our community of users.
1) I've registered another domain name
ticketscad.com to replace the previous .org domain name, which is now serving false warnings of malware, in an attempt to trick you into installing their 'security' tool, which is basically expensive snake oil.
If you see anywhere the .org URL, please reach out to the webmasters or contacts for those sites and help clean up the risk of spreading malware. That old domain only has value because these guys know there are links all over that can drive traffic to their malware business.
2) I've released an updated version 3.4A that addresses the traccar mysql integration as well as adds a user-agent string onto the open street map server tile requests which allow more servers to permit caching of map titles for offline use. Both of these patches had already existed on the GitHub account with the unknown owner.
3) We have official access and ownership over the GitHub account located at:
https://github.com/openises I'd like to extend a special thank you to the anonymous person who made this possible and for his support of the project.
I'd like to call on everyone here to review the list and consider helping out in some way. Lots of these tasks involve confirming bugs, or confirming the issue does not exist on your installation. We have other tasks that involve documenting the use of or the installation of the software. Many of you may have already done this in your organization for internal use. I beg of you to share your time and resources to give a little back to the project. Do you have any documents to share? Even if it's anonymous and requires we clean up what you have. It may be easier to start with your foundation.
5) We're in the process of recreating a GIT repository that recreates the history of the code. We've uncovered cases where it's likely patching verses a clean install would create different versions of the software. Once this timeline is built, you can use the visual tools in GitHub to view the history of the code and to understand the why and how of the incremental improvements that have been made.
Thank you everyone for your support. You are awesome and I appreciate you.
-Eric Osterberg
Tickets CAD project Lead