New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This project are dead ? #3936
Comments
Yes it's active. This is not an issue or feature request so please close this. Thanks. |
Thanks man 👍 |
@JediKev I assume this since I'm watching several projects on github by checking the latest activities (mainly commits) every few months to check the development status and the direction the devs/the project is going. These are mostly projects in beta status or with big plans for the next major version and it's the easiest way to do. So when there are no commits or releases over several month people often consider a project to be stalled / dead. |
@Chefkeks |
@Chefkeks I understand that but that's not how everyone operates. We are going to start being a lot more active and post roadmaps, etc. soon but just because something hasn't had commits in a while doesn't mean it's dead. You could view the website and forums and see that it's clearly not dead. Cheers. 👍🏻 |
@JediKev |
@Chefkeks true stuff. We should definitely reference the site and forums on the readme to give people more reference! Cheers. |
@cloudcon I think you'll love osTicket. It's really robust and you can customize almost everything. Plus it's only going to get better from here 😉 |
Many thanks @JediKev, I did not think my question would go that far. 😉 |
@cloudcon no problem! If you have any trouble at all you can search through here under Issues or visit the forums at http://osticket.com/forum. More than likely someone has had the same problem and it is now fixed or a fix is on the way. |
FYI: Started a repo about how Awesome osTicket is, happy to merge pulls: |
"May require modifications to osTicket core." |
I wish to know if this project has been active.
The last commit is november 2016.
The text was updated successfully, but these errors were encountered: