Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
On Tue, May 15, 2012 at 1:28 PM, Alex Dean a...@crackpot.org 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 - not sure if someone has db access to Trac to try it out: https://gist.github.com/619537 It's a fairly straightforward sql query which then writes out each page in markdown - presumably suitable for dropping into github. If someone can get a dump of the 'wiki' table from Trac I'm happy to try it as well. The replacement pattern could probably be run on individual pages as well. I'm not sure how many pages there are to convert manually - I suspect it's more than I have time to convert. Would rather see us find a way to just move em all. 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
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
Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
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
Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
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
Re: [Ganglia-developers] Trac Wiki, Bugzilla and GitHub
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 still available in EPEL: http://dl.fedoraproject.org/pub/epel/6/x86_64/ Is this really an issue? Thanks, Bernard -- 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
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 PM, 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 still available in EPEL: http://dl.fedoraproject.org/pub/epel/6/x86_64/ Is this really an issue? Thanks, Bernard -- 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 signature.asc Description: Message signed with OpenPGP using GPGMail -- 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
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 just turn off the issue tracker in github to avoid people opening issues in the wrong place? -- 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
+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 bern...@vanhpc.org wrote: 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 have not been able to get ahold of the admins who could tell us what's going on. This is not the first time it has happened. So either we move the Bugzilla instance to somewhere we have more control or we move them to GitHub Issues, it just can't stay where it is. I agree however that there are probably more bugs in Bugzilla than GitHub Issues so perhaps moving from GitHub Issues - Bugzilla and disabling GitHub Issues is the way to go. But I am also under the impression some folks like GitHub Issues better. Anybody else have any comments? Thanks! Bernard On Thursday, May 10, 2012, Daniel Pocock wrote: 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 just turn off the issue tracker in github to avoid people opening issues in the wrong place? -- 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 javascript:; 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
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 simplicity of it. However I think that tackling the export/import of migration may buy our project a bit of goodwill from others who would like to make that switch as well... -Dave On 05/10/2012 10:01 AM, Brad Nicholes wrote: +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 Libern...@vanhpc.org wrote: 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 have not been able to get ahold of the admins who could tell us what's going on. This is not the first time it has happened. So either we move the Bugzilla instance to somewhere we have more control or we move them to GitHub Issues, it just can't stay where it is. I agree however that there are probably more bugs in Bugzilla than GitHub Issues so perhaps moving from GitHub Issues - Bugzilla and disabling GitHub Issues is the way to go. But I am also under the impression some folks like GitHub Issues better. Anybody else have any comments? Thanks! Bernard On Thursday, May 10, 2012, Daniel Pocock wrote: 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 just turn off the issue tracker in github to avoid people opening issues in the wrong place? -- 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.netjavascript:; 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 -- 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
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 tickets from Bugzilla to GitHub Issues Option 1) is the simplest solution at the moment, because it's just a matter of doing a dump of the bugs and re-importing them to another instance. Or we could simply just copy all the files over. Option 2) takes a lot more work, and I have no experience with this. Dave -- if you are volunteering, that would be great. However, we will need to make sure that all the tickets are migrated correctly and that we do not lose past/current tickets. I am currently trying to locate the admins of the server hosting bugzilla.ganglia.info to see what's going on. It is still down... Thanks, Bernard On Thu, May 10, 2012 at 10:33 AM, Dave Rawks d...@pandora.com wrote: 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 simplicity of it. However I think that tackling the export/import of migration may buy our project a bit of goodwill from others who would like to make that switch as well... -Dave On 05/10/2012 10:01 AM, Brad Nicholes wrote: +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 Libern...@vanhpc.org wrote: 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 have not been able to get ahold of the admins who could tell us what's going on. This is not the first time it has happened. So either we move the Bugzilla instance to somewhere we have more control or we move them to GitHub Issues, it just can't stay where it is. I agree however that there are probably more bugs in Bugzilla than GitHub Issues so perhaps moving from GitHub Issues - Bugzilla and disabling GitHub Issues is the way to go. But I am also under the impression some folks like GitHub Issues better. Anybody else have any comments? Thanks! Bernard On Thursday, May 10, 2012, Daniel Pocock wrote: 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 just turn off the issue tracker in github to avoid people opening issues in the wrong place? -- 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.netjavascript:; 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 -- 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
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 long term? Brad Nicholes bnicho...@netiq.com wrote: +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 bern...@vanhpc.org wrote: 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 have not been able to get ahold of the admins who could tell us what's going on. This is not the first time it has happened. So either we move the Bugzilla instance to somewhere we have more control or we move them to GitHub Issues, it just can't stay where it is. I agree however that there are probably more bugs in Bugzilla than GitHub Issues so perhaps moving from GitHub Issues - Bugzilla and disabling GitHub Issues is the way to go. But I am also under the impression some folks like GitHub Issues better. Anybody else have any comments? Thanks! Bernard On Thursday, May 10, 2012, Daniel Pocock wrote: 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 just turn off the issue tracker in github to avoid people opening issues in the wrong place? 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 javascript:; 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
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 job every month to dump the data and send it to someone. Is that what you are referring to? 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 long term? Where do you see that Debian has discontinued support for the package? I believe the package is now bugzilla3 as opposed to just bugzilla? Thanks, Bernard -- 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
[Ganglia-developers] Trac Wiki, Bugzilla and GitHub
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 documentation is somewhat fragmented between Trac and GitHub. Bugs are also filed in two places: Bugzilla and GitHub Issues. To new users this is confusing and we should do our best to resolve this. 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. If you are a happy Ganglia user and would like to help, please either reply back to this thread or to me privately. Thank you for reading. Bernard, on behalf of the Ganglia Team -- 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
