At least some comments are not relevant as most of those commenting
so far helper haven't helped in administration of the current system
at all, so there was no real basis for comparison.
From my point of view, the tracker on github is really basic and the
weak point that I gave up on trying to figure out if worth migrate
to it some time ago. I am not very happy with flyspray either, but
works fair enough not to consider a migration when I have no time to
do it myself. Anyhow, I did review other bugtracker systems, and all
of them have inconveniences.
Then, lately github started to get lot of problems, maybe because it
became too loaded.
Over the time, I learned/worked with two other 'cloud' hosting
services, berlios and sourceforge. And I have to say that from time
to time they did upgrades of the portals or underlying
infrastructure, so one has to spend time in coversions or learning
the new systems.
The main issue is again: who is going to do the work and do that for
long time. Like with restructuring of the code, there were voices
for it, with proposals to write and send scripts for automatization,
but that didn't happen so far. I don't think the restructuring of
the code will happen for the next release, soon we will have to
freeze the development.
It is not that I am agaist github or other 'cloud' portal, at the
end git is distrubuted system by design, so we can have it in many
places. It is about who is doing the work and administration in long
term. If we get a group of people committed to do it, we can have a
middle way for a while. Have a clone on github that you syncronyze
back and forth with current repository and see what people prefer to
use over the time, then we can decide which is the main repo and
eventually keep the other as backup.
Obviously, controlling the system completely is a big benefit, but
if proves that using a hosted one is better and reliable, then we
can make a decision. But I would avoid asking and following just a
blind vote from people that won't get into doing the actual work,
for a thing that is not critical now.
To summarize the way forward from my point of view:
- there has to be a gourp of 3-5 people willing to use github and
ready to maintain that as a clone for a while and syncronyze in both
ways
- try to advertise the benefits to convice more developers to use
that portal for source code development
- let at least several months to go on to see the evolution (some
people might try and then return), then ask for a decision
Cheers,
Daniel
On 8/30/13 2:28 PM, Alexandr S.
Dubovikov wrote:
+1 . easy to manage....
8/30/2013 2:23 PM, Carlos Ruiz Díaz wrote:
+1 for GitHub too
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013
- more details about Kamailio trainings at http://www.asipto.com -