On Tue, May 15, 2012 at 1:28 PM, Alex Dean wrote:
> I did a little hunting for Trac Wiki converters, and didn't find much. I
> ended up manually reformatting a few pages as Asciidoc. It was a little
> tedious, but not terrible.
>
> https://github.com/ganglia/ganglia-web/wiki
I did find this - n
On May 15, 2012, at 1:47 PM, Aaron Nichols wrote:
> The trac wiki import is likely to be more involved than the issues import.
> There are tools for importing Trac issues into bugzilla and they convert the
> wiki syntax so I'm assuming we can re-use that work to import wiki pages.
> Either wa
On Tue, May 15, 2012 at 11:05 AM, Bernard Li wrote:
> Thanks for the links Jesse.
>
> Aaron, Evan, could you two take a look to see how feasible these tools
> are? Does GitHub provide some sort of sandbox where you can play with
> imports?
>
It's not difficult to setup a new project / new accou
Thanks for the links Jesse.
Aaron, Evan, could you two take a look to see how feasible these tools
are? Does GitHub provide some sort of sandbox where you can play with
imports?
I'll try to get a previous Bugzilla dump to you guys so you can play
around with it.
Aaron, I realize I still owe you
On Tue, May 15, 2012 at 10:36:34AM -0400, Brad Nicholes wrote:
>I'm not sure that just abandoning the issues in Bugzilla is a good idea
>without at least trying to follow up with the person who submitted the issue.
>Some of the issues may still be valid and we certainly don't want to abandon
>t
I'm not sure that just abandoning the issues in Bugzilla is a good idea without
at least trying to follow up with the person who submitted the issue. Some of
the issues may still be valid and we certainly don't want to abandon those.
How much effort would it be to try to either validate or fol
I spoke with Vladimir briefly on IRC and he recommends that we just
move to GitHub Issues, reason being it works better with the GitHub
workflow (as Alex Dean also mentioned in his email).
I am okay with this, as long as we take the effort to go through
bugzilla.ganglia.info and close out obsolete
On 12/05/12 00:44, Bernard Li wrote:
> Hi Daniel:
>
> On Fri, May 11, 2012 at 3:08 AM, Daniel Pocock wrote:
>
>> If I host it, it would purely be on a voluntary basis, so I would be
>> hoping for upstream and/or Debian to be providing convenient packages
>> and security updates. Although I am
The integration between github issues and the general github workflow (linking
of issues to pull requests, etc) is pretty nice to work with. I think we'll
have fewer problems with the bug-tracker being out of sync with the real state
of the code if we use github.
alex
On May 11, 2012, at 7:44
Hi Daniel:
On Fri, May 11, 2012 at 3:08 AM, Daniel Pocock wrote:
> If I host it, it would purely be on a voluntary basis, so I would be
> hoping for upstream and/or Debian to be providing convenient packages
> and security updates. Although I am quite capable of installing it
> manually, time s
On 11/05/12 05:32, Bernard Li wrote:
> Hi Daniel:
>
> On Thu, May 10, 2012 at 2:01 PM, Daniel Pocock 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 wil
Hi Daniel:
On Thu, May 10, 2012 at 2:01 PM, Daniel Pocock 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 job every month to
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
l
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 ticke
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
si
+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
, Bernard
Li wrote:
> Hi Daniel:
>
> Just for the record, I actually like Bugzilla
Hi Daniel:
Just for the record, I actually like Bugzilla and would like to keep using
it. However because we do not have direct ownership to the server (it is
being hosted at UC Berkeley) it makes it hard to maintain. For instance it
has currently been down for at least two days and so far I hav
> 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 w
Dear Ganglia Community:
For those who have used Ganglia for at least two years you should have
witnessed a shift in development from SourceForge to GitHub.
This transition benefited the project as it encourages more users to
contribute code and patches. A side effect to this, however, is that
do
19 matches
Mail list logo