I think it has been suggested elsewhere, but a subversion repository could help, so it would be easier to apply patches etc. That would also make sure, that people could follow the development as it comes by.

5 months later

I agree, it would be much easier to contribute patches etc. - and maybe also easier for the head devs to merge addons / fixes.

I'm willing to provide hosting with setup & maintnance if needed - or maybe easier to use something like sourceforge or google?

Best regards

Chris :)

18 days later

Or https://launchpad.net(https://launchpad.net) ?

12 days later

or even better Mercurial

Using a distributed scc would allow us to track and merge our mods back into the latest releases. If you use svn, hg is an easy go. Git is popular in this category, but imo, its' learning curve is too steep for general adoption.

http://mercurial.selenic.com/wiki(http://mercurial.selenic.com/wiki)

a year later

Want to Contribute

I would be interested in contributing code to the project if a repository was available.

My clients and I all use OSTicket, and we have each made modifications to our individual deployments which might be useful to other users and help improve the base application.

Definitely something to consider...

5 days later

This is not an open source project - no SVN :(

Hey SpudR,

"osTicket is a widely-used open source support ticket system." -taken from osticket.com landing page.

Really?

This is not an open source project - no SVN :(

We distribute the source code freely under an open source license... so it's very much open, but we limit write access to the official repo to a small number of people-too many cooks, and all that... If you have something you feel would be useful or want to contribute, post it in the mods section, that way people who want to implement it can do so (or email us about it if you don't want to do that), and if it's something we feel would be a good fit for the official release, we'll be in touch. :)

20 days later

Request for read only access.

We distribute the source code freely under an open source license... so it's very much open, but we limit write access to the official repo to a small number of people-too many cooks, and all that... If you have something you feel would be useful or want to contribute, post it in the mods section, that way people who want to implement it can do so (or email us about it if you don't want to do that), and if it's something we feel would be a good fit for the official release, we'll be in touch. :)

Hi,

i really appreciate that you distribute the code freely, but it would get more easily to apply a certain mod if the project would have been on svn.one more point i would like to add,you keep the write access of the core, and provide us with read access only.In this way we could test or create mods/patch and further if you like you can add those mods to core as a functionality.

Regards,

DK

2 months later

github?

Well, if it's open source why doesn't some one from the community just start a github repo with it. Then everyone could fork off of it for their own mods and such. Then people could get the modded versions easier.

Is there anything in the osTicket license that prohibits going this route?

-jeremy

UPDATE: Doh! As usual, I'm late to the party. There already are some osTicket repositories on Git.

Write a Reply...