Some good comments and questions from the desktop-arch list. Worth thinking about as Fedora is one of the few places that has to bridge between itself and a huge number of upstream projects and at the same time have a commitment to free software for our infrastructure as well as what we distribute. Thoughts? (For the record, before it's mentioned, re-implement Launchpad as free software is not a solution, I suspect. We can do something with the rest of the free software community that everyone could adopt if we try and solve it the right way.) --Chris
--- Begin Message ---
- Subject: [Desktop_architects] Cross-site bug tracking
- From: John Cherry <cherry@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Apr 2007 08:13:22 -0700
I'm sure you are all aware that Canonical has released a beta version of its launchpad service. Launchpad was founded to run the Ubuntu project, but it's now open to other projects. Three--Zope, Jokosher and SilvaCMS--are hosted there now. http://news.com.com/Canonical+wants+open-source+cooperation/2100-7344_3-6174662.html?tag=html.alert An interesting note in the announcement caught my eye. Mark made the following statement... "The company's goal isn't to gobble up the activity of other hosting sites, Shuttleworth said. "We're not trying to convince people to switch off their own infrastructure and adopt Launchpad wholesale," he said. For example, one feature of Launchpad is the ability to link bugs tracked on Launchpad with related bugs at other sites." One of our breakout sessions at DAM-3 was "defect tracking across projects". The summary of this session was: - did not have the right people to make progress - explored a few use cases - The GNOME project uses a point system on defects. Points are given for comments, resolved bugs, etc. Developers with more points can do more with the system. Since this group of architects spans orgs, projects, and distos, I have to at least raise the question with this group regarding our defect tracking issues. - Is the work on defect tracking across projects that is being done with the Launchpad site something that can be leveraged by the community? - Does anyone on this list have some experience with the bug linking that is being done on Launchpad? John ==================================================================== Desktop Architects Meeting - 4 Google Headquarters, Mountain View, CA June 14-16 http://www.linux-foundation.org/en/Desktop_Architects_Meeting_4 _______________________________________________ Desktop_architects mailing list Desktop_architects@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/desktop_architects
--- End Message ---
--- Begin Message ---
- Subject: Re: [Desktop_architects] Cross-site bug tracking
- From: "Aaron J. Seigo" <aseigo@xxxxxxx>
- Date: Tue, 10 Apr 2007 10:23:15 -0600
- In-reply-to: <1176218002.3473.25.camel@xxxxxxxxxxxxxxxxxxxxxxx>
- User-agent: KMail/1.9.6
On Tuesday 10 April 2007, John Cherry wrote: > - Is the work on defect tracking across projects that is being > done with the Launchpad site something that can be leveraged > by the community? as long as Launchpad is not Free software, i doubt it. personally, i find bugzilla and the rest of the centralized, online bug systems an increasingly poor fit for Free software development. i'd love to see a truly distributed bug system, perhaps bringing to bug tracking what git is bringing / has brought to distributed scm. trying to bridge the various bug systems is a pragmatic approach and starts to bridge the gap between various cross-stream sources, but falls far short of addressing other very real issues that exist such as: - providing a way for upstream to know about these down/cross-stream links - how to cater to those who would like to get involved with Free software but have only intermitent or expensive internet connections. - a shared identity system so one can identify the probable quality and/or value of the reports/comments - a distributed search / data mining facility so common bugs fixed upstream that affect multiple other upstream projects can be agregated and dealt with. the last point is very important from the perspective of an upstream project as it really means that launchpad does next to nothing for upstream unless upstreams start using the same centralized system. for example, see this report: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/80665 which links to this: http://bugs.kde.org/show_bug.cgi?id=108440 as you can see, there is no mention on bugs.kde.org of the launchpad notice. which means that anything posted on the launchpad bug goes unnoticed by me as an upstream participant. if you notice on those bugs, the reporters graciously taken the time to post to each bug, meaning we expect twice the efforts from them to make it work well. that's inane. multiply by N projects and it can quickly get out of hand as cross stream linkage grows. i think launchpad is a nice solution for canonical's team to keep track of what they are doing, but as someone sitting upstream i really don't find it very interesting. making it better would mean: - making it Free software so other projects can use it on their self-hosted systems and so we aren't investing in a single point of potential failure - be able to move comments from the launchpad bug post to upstream's tracker with a single click. you wouldn't want all comments moved automatically as they are made as they are often specific to downstream; one could view the bugs as two branches in a scm tree, really, where one would like to merge patches (in this case, comments and file uploads) back and forth with ease - provide an offline mechanism, e.g. be able to run a local copy of the bug tracking software with select bugs downloaded and then sync'd. really, it starts to look a lot like the best thing we could do is get rid of the "bugs in a database" model and move to an scm based system which would give us distributed tracking and possibly even distributed reporter identity (a lot easier than most identity systems since there's no really "valuable" information tied to the identity; it's just a convenient way to track conversation). there could be a web front end to it and for searching the easiest thing to do would be to index it using a second tool such as strigi which is designed specifically for indexing large bodies of information and allowing them to be efficiently searched. the bonus with the latter is that the offline version would already be fully ready for desktop integration as systems such as strigi are being integrated with the Free software desktop more and more. ah, if only i had more time to work on other projects. or a clone army. that'd be cool. or scary, depending on your viewpoint. ;) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)Attachment: pgprXQzxUJ6oG.pgp
Description: PGP signature_______________________________________________ Desktop_architects mailing list Desktop_architects@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/desktop_architects
--- End Message ---
_______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board
