19 Jul
2011
19 Jul
'11
7:58 p.m.
Hello,
sightly off-topic and cc-ed to users mailing lists, but hopefully there
will be people giving valuable feedback based on their experience.
When we started the integration of source code for kamailio and ser, we
went for FlySpray as issue tracking system (aka bug tracker). The
project seems to be dead, nothing happened to it for long time, no
updates and there are warnings using latest php versions, that may
result in malfunctionality or no-functionality with future versions.
Therefore maybe it is the time to make a decision, rather soon than
later, but this time we should look a bit more carefully to available
options, to avoid ending up (in short time) to the same issue.
I see two major options:
A) going to use a source code hosting portal for bug traker (like
sourceforge, berlios, github, a.s.o.)
B) going to use an existing software to be installed on our server and
managed by us
I tend to go for A) as the maintenance of the software will not be done
by us. I do not know which would be the best choice to go for. Of
course, we should consider possible down times (like it happened in the
past) or slow connection to their servers.
B) will give us full control, but then it is about the time to maintain
it (upgrades, security patches, a.s.o.). More than that, it is about
selecting the right software to go with. Since SEMS code is now hosted
in GIT repo of sip-router.org, maybe the tracker can be used by them as
well, eventually by future related projects hosted in our git.
Opinions?
Thanks,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
19 Jul
19 Jul
7:03 p.m.
New subject: [sr-dev] issue tracking system
Daniel-Constantin Mierla writes:
Opinions?
i read somewhere that code.google.com now supports git. it also
includes an issues tracker, but i don't know how good it is.
-- juha
8:22 p.m.
New subject: [sr-dev] issue tracking system
Hey Juha,
yes it does - here is an example of another project I work with that uses
the issuetracker of code.google:
http://code.google.com/p/doubango/issues/list
On Tue, Jul 19, 2011 at 7:03 PM, Juha Heinanen <jh(a)tutpro.com> wrote:
Daniel-Constantin Mierla writes:
Opinions?
i read somewhere that code.google.com now supports git. it also
includes an issues tracker, but i don't know how good it is.
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
8:05 p.m.
We have been extremely happy with Mantis as a self-hosted approach.
It is easy to use, yet has the sophistication and flexibility for a
needed to manage a project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of
JIRA for issues.asterisk.org.
For fairly large projects like this one[1], I have always favoured
internal hosting of such systems in order to maintain maximum control,
use optional plugins, make customisations, etc. I think that would
make the most sense for the SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's bigger
than 99% of open-source which, after all, consists largely of projects
done by one person or a few people at most.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
8:18 p.m.
+1 for Jira. If you have the resources to setup and manage JIRA then I would
suggest this too. We use and it is really very good
On Tue, Jul 19, 2011 at 8:05 PM, Alex Balashov <abalashov(a)evaristesys.com>wrote;wrote:
We have been extremely happy with Mantis as a
self-hosted approach. It is
easy to use, yet has the sophistication and flexibility for a needed to
manage a project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of JIRA for
issues.asterisk.org.
For fairly large projects like this one[1], I have always favoured internal
hosting of such systems in order to maintain maximum control, use optional
plugins, make customisations, etc. I think that would make the most sense
for the SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's bigger than
99% of open-source which, after all, consists largely of projects done by
one person or a few people at most.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
______________________________**_________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http:/…
10:07 p.m.
Hello,
some comments about all provided options so far:
- google code tracker -- haven't use it at all, going to look a bit at it
- github - maybe I missed some setting, but the issue tracker there
seems to be to simplistic - no way to categorize in bugs or feature requests
- jira - folks at SER used it in the past when we were two projects,
reporting that it was rather buggy to keep using it -- maybe it was just
the version purchased at that time (several years ago). I am not
familiar with its administration at all
- mantis - I have no experience with it to say pro/con opinions. Is the
administration (upgrade, patching) easy enough? Does it support
multi-projects on the same instance?
- redmine - it is the one I use for various needs, therefore I have some
experience with its administration. However, I cannot say that it is a
thing I would like to take care of. It seems to be a bit heavy, I had to
patch it (for some quite basic features such as different email address
for different projects or the body of notification emails -- I have to
say I am not that familiar with it and I may have missed some
plugins/settings)
For self installed app, at this time my preferences would be redmine,
mantis, jira -- a big + to rise the rank in the order would come if
there is going to be someone to commit for the maintenance of either
one. Haven't made my mind for hosted options yet.
More comments? Any other options?
Thanks,
Daniel
On 7/19/11 8:18 PM, Jason Penton wrote:
+1 for Jira. If you have the resources to setup and
manage JIRA then I
would suggest this too. We use and it is really very good
On Tue, Jul 19, 2011 at 8:05 PM, Alex Balashov
<abalashov(a)evaristesys.com <mailto:abalashov@evaristesys.com>> wrote:
We have been extremely happy with Mantis as a self-hosted
approach. It is easy to use, yet has the sophistication and
flexibility for a needed to manage a project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of
JIRA for issues.asterisk.org <http://issues.asterisk.org>.
For fairly large projects like this one[1], I have always favoured
internal hosting of such systems in order to maintain maximum
control, use optional plugins, make customisations, etc. I think
that would make the most sense for the SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's
bigger than 99% of open-source which, after all, consists largely
of projects done by one person or a few people at most.
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
11:25 p.m.
On 07/19/2011 01:07 PM, Daniel-Constantin Mierla wrote:
More comments? Any other options?
Other options:
Request Tracker (rt) http://requesttracker.wikia.com/wiki/HomePage - a
number of telcos in USA use rt for their ticket system
Comments:
its 10% of the technology, 90% of how committed the team is to using it.
Whatever the most-active contributors want to use is going to be most
successful.
20 Jul
20 Jul
2:32 a.m.
We use RT as a ticketing system too. It's great for that. But I don't think
it's suitable as a bug tracking or project management database for software
development per se, and that's not what it was intended for.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Jul 19, 2011, at 5:25 PM, Nathan Angelacos <nangel(a)nothome.org> wrote:
On 07/19/2011 01:07 PM, Daniel-Constantin Mierla
wrote:
More comments? Any other options?
Other options:
Request Tracker (rt) http://requesttracker.wikia.com/wiki/HomePage - a number of telcos
in USA use rt for their ticket system
Comments:
its 10% of the technology, 90% of how committed the team is to using it.
Whatever the most-active contributors want to use is going to be most successful.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
11:37 a.m.
Btw, anyone has any experience/feedback with BugGenie?
http://www.thebuggenie.com/
Just found it and at least it looks pretty. However, does not seem well
documented on the web site, neither big community around (based on a
quick look).
Thanks,
Daniel
On 7/20/11 2:32 AM, Alex Balashov wrote:
We use RT as a ticketing system too. It's great
for that. But I don't think it's suitable as a bug tracking or project management
database for software development per se, and that's not what it was intended for.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Jul 19, 2011, at 5:25 PM, Nathan Angelacos<nangel(a)nothome.org> wrote:
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
On 07/19/2011 01:07 PM, Daniel-Constantin Mierla
wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users More comments? Any other options?
Other
options:
Request Tracker (rt) http://requesttracker.wikia.com/wiki/HomePage - a number of telcos
in USA use rt for their ticket system
Comments:
its 10% of the technology, 90% of how committed the team is to using it.
Whatever the most-active contributors want to use is going to be most successful.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 
12:45 a.m.
On Tue, Jul 19, 2011 at 22:07, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
Hello,
some comments about all provided options so far:
- google code tracker -- haven't use it at all, going to look a bit at it
- github - maybe I missed some setting, but the issue tracker there seems to
be to simplistic - no way to categorize in bugs or feature requests
- jira - folks at SER used it in the past when we were two projects,
reporting that it was rather buggy to keep using it -- maybe it was just the
version purchased at that time (several years ago). I am not familiar with
its administration at all
We were using it several years ago and although I personally liked it,
the software (closed source java application) suffered from memory
leaks and needed to be restarted quite often. That may or may not be
true with recent versions, but you wouldn't know unless you set it up
and keep using it for a while.
Note that to be able to use it, we would need to:
- Apply for the open-source license from Atlassian
- Get a server to run it on (Jira can be a memory hog)
-Jan
- mantis - I have no experience with it to say pro/con
opinions. Is the
administration (upgrade, patching) easy enough? Does it support
multi-projects on the same instance?
- redmine - it is the one I use for various needs, therefore I have some
experience with its administration. However, I cannot say that it is a thing
I would like to take care of. It seems to be a bit heavy, I had to patch it
(for some quite basic features such as different email address for different
projects or the body of notification emails -- I have to say I am not that
familiar with it and I may have missed some plugins/settings)
Another option, simpler than redmine, would be trac:
http://trac.edgewall.org/
It's simpler than most other applications (which imho is a plus), but
it does not support multiple projects on a single instance (may not be
a problem since you can have multiple instances).
-Jan
For self installed app, at this time my preferences
would be redmine,
mantis, jira -- a big + to rise the rank in the order would come if there
is going to be someone to commit for the maintenance of either one. Haven't
made my mind for hosted options yet.
More comments? Any other options?
Thanks,
Daniel
On 7/19/11 8:18 PM, Jason Penton wrote:
+1 for Jira. If you have the resources to setup and manage JIRA then I would
suggest this too. We use and it is really very good
On Tue, Jul 19, 2011 at 8:05 PM, Alex Balashov <abalashov(a)evaristesys.com>
wrote:
We have been extremely happy with Mantis as a self-hosted approach. It is
easy to use, yet has the sophistication and flexibility for a needed to
manage a project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of JIRA
for issues.asterisk.org.
For fairly large projects like this one[1], I have always favoured
internal hosting of such systems in order to maintain maximum control, use
optional plugins, make customisations, etc. I think that would make the
most sense for the SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's bigger
than 99% of open-source which, after all, consists largely of projects done
by one person or a few people at most.
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
11:23 a.m.
On 7/20/11 12:45 AM, Jan Janak wrote:
On Tue, Jul 19, 2011 at 22:07, Daniel-Constantin
Mierla
<miconda(a)gmail.com> wrote:
trac was really giving me
headaches in the past. I tried once and never
looked back to it. Maybe just some bad experience, but no plan here to
touch it again, I rather look at alternatives.
Cheers,
Daniel
Hello,
some comments about all provided options so far:
- google code tracker -- haven't use it at all, going to look a bit at it
- github - maybe I missed some setting, but the issue tracker there seems to
be to simplistic - no way to categorize in bugs or feature requests
- jira - folks at SER used it in the past when we were two projects,
reporting that it was rather buggy to keep using it -- maybe it was just the
version purchased at that time (several years ago). I am not familiar with
its administration at all
We were using it several years ago and although I
personally liked it,
the software (closed source java application) suffered from memory
leaks and needed to be restarted quite often. That may or may not be
true with recent versions, but you wouldn't know unless you set it up
and keep using it for a while.
Note that to be able to use it, we would need to:
- Apply for the open-source license from Atlassian
- Get a server to run it on (Jira can be a memory hog)
-Jan
- mantis - I have no experience with it to say
pro/con opinions. Is the
administration (upgrade, patching) easy enough? Does it support
multi-projects on the same instance?
- redmine - it is the one I use for various needs, therefore I have some
experience with its administration. However, I cannot say that it is a thing
I would like to take care of. It seems to be a bit heavy, I had to patch it
(for some quite basic features such as different email address for different
projects or the body of notification emails -- I have to say I am not that
familiar with it and I may have missed some plugins/settings)
Another option,
simpler than redmine, would be trac:
http://trac.edgewall.org/
It's simpler than most other applications (which imho is a plus), but
it does not support multiple projects on a single instance (may not be
a problem since you can have multiple instances).
-Jan
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
For self installed app, at this time my
preferences would be redmine,
mantis, jira -- a big + to rise the rank in the order would come if there
is going to be someone to commit for the maintenance of either one. Haven't
made my mind for hosted options yet.
More comments? Any other options?
Thanks,
Daniel
On 7/19/11 8:18 PM, Jason Penton wrote:
+1 for Jira. If you have the resources to setup and manage JIRA then I would
suggest this too. We use and it is really very good
On Tue, Jul 19, 2011 at 8:05 PM, Alex Balashov<abalashov(a)evaristesys.com>
wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users We have been extremely happy with Mantis as a
self-hosted approach. It is
easy to use, yet has the sophistication and flexibility for a needed to
manage a project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of JIRA
for issues.asterisk.org.
For fairly large projects like this one[1], I have always favoured
internal hosting of such systems in order to maintain maximum control, use
optional plugins, make customisations, etc. I think that would make the
most sense for the SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's bigger
than 99% of open-source which, after all, consists largely of projects done
by one person or a few people at most.
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
11:35 a.m.
Hi,
We are also using the Mantis and as Alex said is very flexible and easy to
use.
2011/7/19 Daniel-Constantin Mierla <miconda(a)gmail.com>
- mantis - I have no experience with it to say pro/con opinions. Is the
administration (upgrade, patching) easy enough? Does it support
multi-projects on the same instance?
We had no troubles upgrading it, it was quite straightforward IIRC. It does
support as many projects as you want and you can add subprojects to them.
Also, another feature I like is that you can easily link a commit with the
bug id so that info appears automatically in the bug report.
Best regards,
Santi
27 Jul
27 Jul
2:46 p.m.
We use it and keep it rebooting every now and when.
-1
-jiri
On 7/19/11 8:18 PM, Jason Penton wrote:
+1 for Jira. If you have the resources to setup and
manage JIRA then I would suggest this too. We use and it is really very good
On Tue, Jul 19, 2011 at 8:05 PM, Alex Balashov <abalashov(a)evaristesys.com
<mailto:abalashov@evaristesys.com>> wrote:
We have been extremely happy with Mantis as a self-hosted approach. It is easy to
use, yet has the sophistication and flexibility for a needed to manage a
project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of JIRA for
issues.asterisk.org <http://issues.asterisk.org>.
For fairly large projects like this one[1], I have always favoured internal hosting
of such systems in order to maintain maximum control, use optional
plugins, make customisations, etc. I think that would make the most sense for the
SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's bigger than
99% of open-source which, after all, consists largely of projects done by one
person or a few people at most.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670 <tel:%2B1-678-954-0670>
Fax: +1-404-961-1892 <tel:%2B1-404-961-1892>
Web: http://www.evaristesys.com/
_________________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users
<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
20 Jul
20 Jul
12:53 p.m.
On Tuesday 19 July 2011, Alex Balashov wrote:
We have been extremely happy with Mantis as a
self-hosted approach.
It is easy to use, yet has the sophistication and flexibility for a
needed to manage a project of non-trivial size.
Hello,
just had a quick look to Mantis, looks fine. Also the installation and
administration does not look that dificult, the documentation provide a lot of
details. From the installation requirements it should be also fine, the
development looks at least from the commit stats healthy as well.
I've a lot of experience with Jira, its in general a good system, but maybe
its a bit to heavy for our use. I also don't like the fact that its not really
open source software.
I could install a test setup in the next days on our server, if you like.
For fairly large projects like this one[1], I have
always favoured
internal hosting of such systems in order to maintain maximum control,
use optional plugins, make customisations, etc. I think that would
make the most sense for the SR/Kamailio community.
This is also my opinion.
Best regards,
Henning
27 Jul
27 Jul
11:50 p.m.
+1 for Mantis. We use it as well (self-hosted) without any issues, both
internally and for our customers.
Andreas
On 07/19/2011 08:05 PM, Alex Balashov wrote:
We have been extremely happy with Mantis as a
self-hosted approach. It
is easy to use, yet has the sophistication and flexibility for a needed
to manage a project of non-trivial size.
On the other hand, Digium recently moved away from it in favour of JIRA
for issues.asterisk.org.
For fairly large projects like this one[1], I have always favoured
internal hosting of such systems in order to maintain maximum control,
use optional plugins, make customisations, etc. I think that would make
the most sense for the SR/Kamailio community.
-- Alex
[1] It's not nearly as large as say, the Linux kernel, but it's bigger
than 99% of open-source which, after all, consists largely of projects
done by one person or a few people at most.
19 Jul
19 Jul
8:28 p.m.
New subject: [sr-dev] issue tracking system
2011/7/19 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:
I see two major options:
A) going to use a source code hosting portal for bug traker (like
sourceforge, berlios, github, a.s.o.)
B) going to use an existing software to be installed on our server and
managed by us
I tend to go for A) as the maintenance of the software will not be done by
us. I do not know which would be the best choice to go for. Of course, we
should consider possible down times (like it happened in the past) or slow
connection to their servers.
B) will give us full control, but then it is about the time to maintain it
(upgrades, security patches, a.s.o.). More than that, it is about selecting
the right software to go with. Since SEMS code is now hosted in GIT repo of
sip-router.org, maybe the tracker can be used by them as well, eventually by
future related projects hosted in our git.
I vote for installing Redmine (the best multri project tracker/wiki
I've ever seen) or hosting the project in Github.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
4668
days inactive
4676
days old
15 comments
12 participants
participants (12)
-
Alex Balashov -
Andreas Granig -
Daniel-Constantin Mierla -
Henning Westerholt -
Iñaki Baz Castillo -
Jan Janak -
Jason Penton -
Jason Penton -
Jiri Kuthan -
Juha Heinanen -
Nathan Angelacos -
Santiago Gimeno