Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
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 follow up on the open issues? OTOH, I guess leaving bugzilla as read-only means that the issues will still be there and not necessarily be lost. We could close out each ticket in bugzilla with a note to the submitter that says that if the bug is still an issue then resubmit the bug to GitHub Issues. I guess what I am saying is that I don't have a strong opinion either way. Brad On 5/14/2012 at 11:37 AM, in message CA+3XN_+bV1pjKaQ2_D-_omo0dYticBJNJPhKy=ot7xniyj0...@mail.gmail.com, Bernard Li bern...@vanhpc.org wrote: 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 tickets and move all the relevant open ones to GitHub Issues. We can leave the old bugs in Bugzilla for archival purposes and in read-only mode. Another option which Vladimir suggest is just forget about the old tickets in Bugzilla and start fresh in GitHub Issues. I am leaning towards option 1 -- what do you guys think? Thanks, Bernard On Sat, May 12, 2012 at 2:12 AM, Daniel Pocock dan...@pocock.com.au wrote: On 12/05/12 00:44, Bernard Li wrote: Hi Daniel: On Fri, May 11, 2012 at 3:08 AM, Daniel Pocock dan...@pocock.com.au 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 spent maintaining such an install of bugzilla would cut into time spent maintaining any other open source packages I contribute to Thanks to Ben Hartshorne, I was able to find this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638705 So yeah, bugzilla is temporarily removed from Debian. However, it's Yes, that was the same link I posted - it doesn't say temporary or permanent, it just says they need at least 2 people willing to support the package in some sense. It also suggests that the way upstream distributes the tarball makes it necessary to do a lot of patching, that deters people from maintaining a package. still available in EPEL: http://dl.fedoraproject.org/pub/epel/6/x86_64/ Is this really an issue? Yes, definitely, because if something like that is publicly accessible, it needs security updates. Debian and RHEL often put out security updates for supported packages within a matter of hours (much faster than the non-Linux platform vendor) The reason for using Debian is that I already have a VM running for reSIProcate, it could be shared for the Ganglia project, used to bootstrap releases, etc. The physical server is under a commercial hosting contract in Telehouse, one of London's most well connected data centres: http://en.wikipedia.org/wiki/Telehouse_Europe#London -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
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 the Trac Wiki dumps -- if someone else here who has admin access to SourceForge could help with this, that would be great. Thanks! Bernard On Tue, May 15, 2012 at 8:32 AM, Jesse Becker becker...@mail.nih.gov wrote: 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 those. How much effort would it be to try to either validate or follow up on the open issues? OTOH, I guess leaving bugzilla as read-only means that the issues will still be there and not necessarily be lost. We could close out each ticket in bugzilla with a note to the submitter that says that if the bug is still an issue then resubmit the bug to GitHub Issues. I guess what I am saying is that I don't have a strong opinion either way. There's no way to do a bulk import? I'm slightly surprised. http://stackoverflow.com/questions/7281304/migrate-bugzilla-issues-to-github-issue-tracker https://github.com/dowee/bugzilla-importer Maybe useful: https://gitorious.org/bugmail/dumpbugzilla and going the other way... https://gitorious.org/bugmail/github-issues-export Brad On 5/14/2012 at 11:37 AM, in message CA+3XN_+bV1pjKaQ2_D-_omo0dYticBJNJPhKy=ot7xniyj0...@mail.gmail.com, Bernard Li bern...@vanhpc.org wrote: 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 tickets and move all the relevant open ones to GitHub Issues. We can leave the old bugs in Bugzilla for archival purposes and in read-only mode. Another option which Vladimir suggest is just forget about the old tickets in Bugzilla and start fresh in GitHub Issues. I am leaning towards option 1 -- what do you guys think? Thanks, Bernard On Sat, May 12, 2012 at 2:12 AM, Daniel Pocock dan...@pocock.com.au wrote: On 12/05/12 00:44, Bernard Li wrote: Hi Daniel: On Fri, May 11, 2012 at 3:08 AM, Daniel Pocock dan...@pocock.com.au 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 spent maintaining such an install of bugzilla would cut into time spent maintaining any other open source packages I contribute to Thanks to Ben Hartshorne, I was able to find this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638705 So yeah, bugzilla is temporarily removed from Debian. However, it's Yes, that was the same link I posted - it doesn't say temporary or permanent, it just says they need at least 2 people willing to support the package in some sense. It also suggests that the way upstream distributes the tarball makes it necessary to do a lot of patching, that deters people from maintaining a package. still available in EPEL: http://dl.fedoraproject.org/pub/epel/6/x86_64/ Is this really an issue? Yes, definitely, because if something like that is publicly accessible, it needs security updates. Debian and RHEL often put out security updates for supported packages within a matter of hours (much faster than the non-Linux platform vendor) The reason for using Debian is that I already have a VM running for reSIProcate, it could be shared for the Ganglia project, used to bootstrap releases, etc. The physical server is under a commercial hosting contract in Telehouse, one of London's most well connected data centres: http://en.wikipedia.org/wiki/Telehouse_Europe#London -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has
Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
On Tue, May 15, 2012 at 11:05 AM, Bernard Li bern...@vanhpc.org 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 account in github, I'm not worried about finding a place to play around. Once we have some export data to play with we should be able to get going. I've found a few different tools for importing from bugzilla to github. 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 way, having some exported data to experiment with would be great. Aaron -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
