iTop can be enhanced in many ways by creating independent 'extension' modules without the need to alter its code... but the documentation is a bit lacking in this area I must admit.
However we did investigate migrating from SourceForge/SVN to GitHub one year ago when SourceForge experienced a very long outage (SF.net remained read-only for 2 weeks last summer).
3 things prevented us from doing the jump:
- We are also using SVN for a number of things internally, so we'd better migrate to git as well internally at the same time, since having to develop with a mix of GIT and SVN is a bit painful
- command line tools are great, but sometimes you need some GUI tools for browsing and to assist you for some less usual tasks. I did a bit of research last year and was very disappointed with the quality of open-source GUI tools for GIT on Linux. There are some tools for browsing, some for "committing" but no single tool for everything and the UI is often quite crude. If you know of a good GUI GIT client for Linux, I'm interested ;-)
- migrating from SVN to GIT does not preserve revision numbers (since branches are not reflected in the same manner in GIT and SVN). This means that all tickets referencing revision numbers should be migrated too... and that's not an easy task.
These are the main reasons (plus the lack of time, of course) explaining why we're still using SVN, even if GIT seems the way to go.
Regards,
Last edit: Denis 2016-05-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was (a few years ago) part of the migration of a big development team from svn to git, in the beginning we were using git-svn to have both running, and we kept the svn repository as read only even after the migration. It was a pain sometimes but it was worth it.
Most of the time I'm using the client that is provided in inteliJ (full version of phpStorm - all jetbrains tools have a nice git interface)
for a separate UI I recently started using GitKraken (it is free, but not open source)
Is there some kind of "standardized" was for you to add/propose changes to the current system?
i.e: I enhanced the email-reply extension to allow a list of emails in addition to the user select statement, and the ability to filter by organization in the email-sync
br Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
right now it seems to me quite complicated to add new features to itop - most of this based on the fact that the main tracker is sourceforge / svn.
Would you consider moving to github / bitbucket / gitlab to give the comunity the ability to contribute more to itop?
Keep up the good work!
br Michael
Hi Michael,
iTop can be enhanced in many ways by creating independent 'extension' modules without the need to alter its code... but the documentation is a bit lacking in this area I must admit.
However we did investigate migrating from SourceForge/SVN to GitHub one year ago when SourceForge experienced a very long outage (SF.net remained read-only for 2 weeks last summer).
3 things prevented us from doing the jump:
- We are also using SVN for a number of things internally, so we'd better migrate to git as well internally at the same time, since having to develop with a mix of GIT and SVN is a bit painful
- command line tools are great, but sometimes you need some GUI tools for browsing and to assist you for some less usual tasks. I did a bit of research last year and was very disappointed with the quality of open-source GUI tools for GIT on Linux. There are some tools for browsing, some for "committing" but no single tool for everything and the UI is often quite crude. If you know of a good GUI GIT client for Linux, I'm interested ;-)
- migrating from SVN to GIT does not preserve revision numbers (since branches are not reflected in the same manner in GIT and SVN). This means that all tickets referencing revision numbers should be migrated too... and that's not an easy task.
These are the main reasons (plus the lack of time, of course) explaining why we're still using SVN, even if GIT seems the way to go.
Regards,
Last edit: Denis 2016-05-17
Hi Denis,
I was (a few years ago) part of the migration of a big development team from svn to git, in the beginning we were using git-svn to have both running, and we kept the svn repository as read only even after the migration. It was a pain sometimes but it was worth it.
Most of the time I'm using the client that is provided in inteliJ (full version of phpStorm - all jetbrains tools have a nice git interface)
for a separate UI I recently started using GitKraken (it is free, but not open source)
Is there some kind of "standardized" was for you to add/propose changes to the current system?
i.e: I enhanced the email-reply extension to allow a list of emails in addition to the user select statement, and the ability to filter by organization in the email-sync
br Michael