Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
Stephen Ecob wrote: We're hearing complaints that some submitted patches aren't receiving enough attention, but there simply isn't enough maintainer time available There are 22 Current Active Developers listed in http://www.gpleda.org/people.html I see only few of them more than once a month on the mailing list. to give everyone as much attention as they'd like. More often than not, any dev response would be better than none. ---)kaimartin(--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
al davis wrote: If submitted patches don't receive enough attention, maybe there is something wrong with them. If so, then the contributor should receive feedback on what is wrong, rather than silence. In gnucap, I always give contributors top priority, but if a patch comes in without advance discussion, often there is something wrong with it. Well, my three trials to contribute were the opposite of out-of-the-blue. All of them started with me talking about the problem on the list. I announced, that I was working on a fix and even asked, what format the patch should be. Still, I had to do repeated nagging before I got feedback. ---)kaimartin(--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
On Friday 10 December 2010, kai-martin knaak wrote: al davis wrote: In gnucap, I always give contributors top priority, but if a patch comes in without advance discussion, often there is something wrong with it. Well, my three trials to contribute were the opposite of out-of-the-blue. All of them started with me talking about the problem on the list. I announced, that I was working on a fix and even asked, what format the patch should be. Still, I had to do repeated nagging before I got feedback. I don't remember that. What I remember is that you made a statement, I responded, and it stopped there. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
On Thursday 09 December 2010 21:06:06 Peter Clifton wrote: On Thu, 2010-12-09 at 21:22 +0100, Bert Timmerman wrote: ... gEDA and friends can even keep the SF tracker system ... Actually, I have been looking quite seriously at the possibility of ditching SF trackers and moving all the history of bugs to Launchpad. I can do a fairly lossless export, and I'm working on fixing some issues with the Launchpad bug import code to be able to translate any bug numbers embedded in the bug comments. Nothing is decided yet.. beyond verifying that it is technically feasible, I want to know that all the current developers buy in (or at least consent) to a move. Launchpad being properly open source now removes one potentially strong argument against its adoption, but no doubt there will be people who dislike it for other reasons, or trust SourceForge more than Canonical. I'd welcome feedback from people who actively encounter and report bugs (especially in favour of the move ;)). I'd also welcome feedback from anyone who works with bug reports, test patches, merge code etc... (Doesn't have to be with gEDA / PCB, anything regarding Launchpad / SourceForge). Launchpad seems to have a number of advantages of SF.net, including the ability to easily mark duplicate bugs and link bugs to a particular branch. But it also does simple, easy things better -- for example, it actually sends the right content type for attachments to the browser. It even has sensible URLs for bugs. You can also assign groups of people to a bug, as an alternative to individual developers. My main objection to Launchpad in the past was that it was closed-source, but now that that has been changed... it's hard to find a reason not to use it for bug tracking instead of SF.net. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
Am 10.12.2010 um 21:03 schrieb Peter TB Brett: My main objection to Launchpad in the past was that it was closed- source, but now that that has been changed... it's hard to find a reason not to use it for bug tracking instead of SF.net. I've commited a bunch of bugs against Ubuntu, the prestige-project of Launchpad. Finding similar bugs, or any related bug was almost impossible. The project's source code feels so far away I never got in touch with it. So, no engouragement to actually fix something. Another reason would be perhaps it's use of Bazaar instead of Git. This not-so enthusiastic experience might be Ubuntu specific, of course. Using Github, the experience was a lot better. Regarding the messenging system it's not as full featured as the others, but sufficiently featured. Everything on Github centers around the source code repository, so you almost have to run away to not start fixing the issue. Forks are still a fork, but pull requests and similar features make it more feel like a branch. Many people use this fork-and-pull-request thingy, so it's simple to review something or ask for refinements without worrying about the main repo. You can put comments right into the provided patches and they're picked up in the issue's tracker log. Very productive. my $0.02 Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
On Fri, 2010-12-10 at 22:01 +0100, Markus Hitter wrote: I've commited a bunch of bugs against Ubuntu, the prestige-project of Launchpad. Finding similar bugs, or any related bug was almost impossible. Possibly a weakness, but I don't see SF scoring any higher there. At least LP _has_ an option to search for similar bugs when you submit. The project's source code feels so far away I never got in touch with it. So, no engouragement to actually fix something. We're not (as far as I know) intending to move the source hosting. I assume you meant source hosting on LP, or did you mean the git.gpleda.org source-code feels so far...? Another reason would be perhaps it's use of Bazaar instead of Git. That is a pain, sure - but since we weren't intending to move the code hosting, it isn't a major problem. LP will happily track content in a git branch if you so desired. This not-so enthusiastic experience might be Ubuntu specific, of course. Ubuntu has the issue of there being a _LOT_ of individual packages. I often find half the battle is finding the package you want to report a bug against, and I suspect that would be much easier in our case. Might be wrong of course. Using Github, the experience was a lot better. Regarding the messenging system it's not as full featured as the others, but sufficiently featured. Github looks fun and friendly, but it is only free as in beer. This isn't a show stopper for me personally, but I think we can get some similar benefits without it. For example, I intend to write a post-commit hook for the git repository which can login to LP using its API and mark any bugs mentioned as fixed in the commit message as fix committed. Code review on github looks nice though. LP has similar, but only for bzr branches. See this for an example: https://code.launchpad.net/~pcjc2/notify-osd/fix_dropshadow/+merge/42804 -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
Date: Fri, 10 Dec 2010 20:03:29 + From: Peter TB Brett pe...@peter-b.co.uk Subject: Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]] On Thursday 09 December 2010 21:06:06 Peter Clifton wrote: On Thu, 2010-12-09 at 21:22 +0100, Bert Timmerman wrote: ... gEDA and friends can even keep the SF tracker system ... Actually, I have been looking quite seriously at the possibility of ditching SF trackers and moving all the history of bugs to Launchpad. I can do a fairly lossless export, and I'm working on fixing some issues with the Launchpad bug import code to be able to translate any bug numbers embedded in the bug comments. Nothing is decided yet.. beyond verifying that it is technically feasible, I want to know that all the current developers buy in (or at least consent) to a move. Launchpad being properly open source now removes one potentially strong argument against its adoption, but no doubt there will be people who dislike it for other reasons, or trust SourceForge more than Canonical. I'd welcome feedback from people who actively encounter and report bugs (especially in favour of the move ;)). I'd also welcome feedback from anyone who works with bug reports, test patches, merge code etc... (Doesn't have to be with gEDA / PCB, anything regarding Launchpad / SourceForge). Launchpad seems to have a number of advantages of SF.net, including the ability to easily mark duplicate bugs and link bugs to a particular branch. But it also does simple, easy things better -- for example, it actually sends the right content type for attachments to the browser. It even has sensible URLs for bugs. You can also assign groups of people to a bug, as an alternative to individual developers. My main objection to Launchpad in the past was that it was closed-source, but now that that has been changed... it's hard to find a reason not to use it for bug tracking instead of SF.net. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre Date: Fri, 10 Dec 2010 22:01:02 +0100 From: Markus Hitter m...@jump-ing.de Subject: Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]] To: gEDA user mailing list geda-user@moria.seul.org Message-ID: 07255762-6808-4563-9a82-8d28a0d7d...@jump-ing.de Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed [...] I've commited a bunch of bugs against Ubuntu, the prestige-project of Launchpad. Finding similar bugs, or any related bug was almost impossible. The project's source code feels so far away I never got in touch with it. So, no engouragement to actually fix something. Another reason would be perhaps it's use of Bazaar instead of Git. This not-so enthusiastic experience might be Ubuntu specific, of course. Using Github, the experience was a lot better. Regarding the messenging system it's not as full featured as the others, but sufficiently featured. Everything on Github centers around the source code repository, so you almost have to run away to not start fixing the issue. Forks are still a fork, but pull requests and similar features make it more feel like a branch. Many people use this fork-and-pull-request thingy, so it's simple to review something or ask for refinements without worrying about the main repo. You can put comments right into the provided patches and they're picked up in the issue's tracker log. Very productive. my $0.02 Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/ Maybe we should check out the rest of the alternatives: http://en.wikipedia.org/wiki/Comparison_of_Free_Software_Hosting_Facilities Also I realize you don't want to re-invent the wheel but I have a rack with a few servers at isc.org (the location of the F. Root nameserver). Mostly they run xen instances, but they are very much under utilized. If you want to roll your own setup, say out of debian packages it might be an option. Clif ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
On Thu, 2010-12-09 at 21:22 +0100, Bert Timmerman wrote: ... gEDA and friends can even keep the SF tracker system ... Actually, I have been looking quite seriously at the possibility of ditching SF trackers and moving all the history of bugs to Launchpad. I can do a fairly lossless export, and I'm working on fixing some issues with the Launchpad bug import code to be able to translate any bug numbers embedded in the bug comments. Nothing is decided yet.. beyond verifying that it is technically feasible, I want to know that all the current developers buy in (or at least consent) to a move. Launchpad being properly open source now removes one potentially strong argument against its adoption, but no doubt there will be people who dislike it for other reasons, or trust SourceForge more than Canonical. I'd welcome feedback from people who actively encounter and report bugs (especially in favour of the move ;)). I'd also welcome feedback from anyone who works with bug reports, test patches, merge code etc... (Doesn't have to be with gEDA / PCB, anything regarding Launchpad / SourceForge). -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
I'd welcome feedback from people who actively encounter and report bugs (especially in favour of the move ;)). I'd also welcome feedback from anyone who works with bug reports, test patches, merge code etc... (Doesn't have to be with gEDA / PCB, anything regarding Launchpad / SourceForge). We're hearing complaints that some submitted patches aren't receiving enough attention, but there simply isn't enough maintainer time available to give everyone as much attention as they'd like. If Launchpad makes it quicker and easier for maintainers to process patch submissions then it will help, let's adopt it. If you do trial Launchpad I'd be happy to funnel my bug reports and patches through it, I'd be interested to see how it compares to SF from the patch submitter's point of view. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TRACKERS [was: Re: gEDA-dev: Dev list [was: Random thoughts onthe future interface of PCB]]
If submitted patches don't receive enough attention, maybe there is something wrong with them. Maybe they don't work, introduce Nope, we just don't have a lot of time to review them. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
