This is our request for help. We need someone to take charge of
managing our documentation making sure they are up to date and in one
canonical location. We'll also need someone to help with importing the
bugs in Bugzilla to GitHub Issues.
We definitely have to abandon bugzilla?
Can we
+1 for sticking with bugzilla. If we can move it to somewhere that is more
maintainable, that would be better. But I would hate to just abandon
everything there.
Brad
On 5/10/2012 at 10:01 AM, in message
ca+3xn_lykk8gveq0itiak980t7w4hk+awrpy0fk39bvhgpg...@mail.gmail.com, Bernard
Li
FWIW, the guys at github are eager to assist people with bulk importing
of issues via their json issue format. And they have been trying to
encourage people to write export tools for bugzilla and other
services/software.
I'd be a fan of moving from bugtracker to github just for the one-stop
To be honest, I don't really have a strong opinion either way. At the
same time I haven't used GitHub Issues so I cannot comment on its
usability versus Bugzilla.
Currently we have two options:
1) Migrate bugzilla.ganglia.info to another server which is more maintainable
2) Migrate all the
Whatever/whoever does it, I think we should make sure a data dump is
always available.
Is there any issue tracker that keeps data with the repo itself?
As for bugzilla, I thought about installing it on a vm, but I found that
Debian has discontinued support for the package, is it the best option
Hi Daniel:
On Thu, May 10, 2012 at 2:01 PM, Daniel Pocock dan...@pocock.com.au wrote:
Whatever/whoever does it, I think we should make sure a data dump is
always available.
Well, if we migrate Bugzilla instance to a server which we have full
control, it will just be a matter of running a cron
