February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] New Issue Tracker

by Marcus Denker

On Feb 8, 2013, at 10:10 PM, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > > > Fog Creek would be happy to provide all of you with a free FogBugz On > Demand account. It has a good API, it has file attachments, it has > custom workflows, triggers, and plugins, and we're about to release a > version that's Gmail-level fast (which I could turn on immediately for a > Pharo account, so you don't have to use the existing "slow" version). I > know it's a relatively complete tracker compared to e.g. GitHub Issues, > but I'd like to believe that our UI is easier to navigate than some of > the other options. Plus, I'd be happy to help migrate your issues from > Google Code to FogBugz on your behalf, with full history if you'd like. > That sound very interesting! I will play with it (I did already in the past a little) > I know I pretty much lurk on this list these days, but I've been > programming in Squeak since 1996 and Pharo since it came into existence; > giving all of you a free, good bug tracker would make me quite happy. :-) 1996â¦ I think I stumbled on it in 1997. Considering that many now e.g. at RMoD where perfect eToys target age (and younger) back thenâ¦ strange. Marcus

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

On 2013-02-08, at 23:30, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > On Fri, Feb 8, 2013 at 2:22 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> On Feb 8, 2013, at 10:00 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> >> wrote: >> >>> (regarding Mantis) >>> >>> 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> we used it for squeak and I never liked it. >>> >>> It is ugly as it gets, I don't like its appearance either. I won't >>> argue on that :) >>> >>> But it is reliable, flexible and full of features. >>> >> >> But if you look at it.. they published statistics for Squeak, and >> it was something like 10 people used it in 12 months on 50 bugs >> (or something like that). >> >> We closed >1500 in not even 10 monthsâ¦ the software used as >> a issue tracker has to be some kind of influence on that. >> > > That's not a valid comparison. In Squeak trunk bugs are getting fixed at a > much higher rate than that but it isn't tracked on the issue tracker, > because....... > we mostly don't use an issue tracker. sigh! which is impressive in 2013...

Feb. 8, 2013

Re: [Pharo-project] Less than 50 issues!

by Sean P. DeNigris

Current stats: 27 Open 2.0 Issues (down from 41) [1] 02 Ready to Review (down from 15) [2] 01 Ready to Integrate [3] ______ = 22 Outstanding [4] Less than half of the original 50 left!! What a great sprint :) [1] http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D2.0 [2] http://code.google.com/p/pharo/issues/list?can=2&q=label%3AMilestone-2.0+st… [3] http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixToInclude+Mi… [4] http://code.google.com/p/pharo/issues/list?cursor=pharo%3A7102&q=label%3AMi… -- View this message in context: http://forum.world.st/Less-than-50-issues-tp4667961p4668735.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Eliot Miranda

On Fri, Feb 8, 2013 at 2:22 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Feb 8, 2013, at 10:00 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > > > (regarding Mantis) > > > > 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> we used it for squeak and I never liked it. > > > > It is ugly as it gets, I don't like its appearance either. I won't > > argue on that :) > > > > But it is reliable, flexible and full of features. > > > > But if you look at it.. they published statistics for Squeak, and > it was something like 10 people used it in 12 months on 50 bugs > (or something like that). > > We closed >1500 in not even 10 monthsâ¦ the software used as > a issue tracker has to be some kind of influence on that. > That's not a valid comparison. In Squeak trunk bugs are getting fixed at a much higher rate than that but it isn't tracked on the issue tracker, because....... we mostly don't use an issue tracker. > > Marcus > > > -- best, Eliot

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Marcus Denker

On Feb 8, 2013, at 10:00 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > (regarding Mantis) > > 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> we used it for squeak and I never liked it. > > It is ugly as it gets, I don't like its appearance either. I won't > argue on that :) > > But it is reliable, flexible and full of features. > But if you look at it.. they published statistics for Squeak, and it was something like 10 people used it in 12 months on 50 bugs (or something like that). We closed >1500 in not even 10 monthsâ¦ the software used as a issue tracker has to be some kind of influence on that. Marcus

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

On 2013-02-08, at 22:10, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > On Fri, Feb 8, 2013, at 04:04 PM, Camillo Bruni wrote: >> >> On 2013-02-08, at 21:58, "Esteban A. Maringolo" <emaringolo(a)gmail.com> >> wrote: >> >>> (regarding Mantis) >>> >>> 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> we used it for squeak and I never liked it. >>> >>> It is ugly as it gets, I don't like its appearance either. I won't >>> argue on that :) >>> >>> But it is reliable, flexible and full of features. >>> >>> We talked about migrating to JIRA, but we have ~12000 issues tracked, >>> and moving off is not an option by now. >>> >>> On aesthetics I like the simplicity of GitHub or the "style" of JIRA >>> (some bloatware can be removed and/or hidden). >> >> true JIRA is already much better. But still compared to trac or github... >> :D >> >> Well in the end we might survive with JIRA as well ;) since issues should >> be >> filed in from the image directly. So the interface is mostly a problem >> for the >> integrators ;) > > > Fog Creek would be happy to provide all of you with a free FogBugz On > Demand account. It has a good API, it has file attachments, it has > custom workflows, triggers, and plugins, and we're about to release a > version that's Gmail-level fast (which I could turn on immediately for a > Pharo account, so you don't have to use the existing "slow" version). I > know it's a relatively complete tracker compared to e.g. GitHub Issues, > but I'd like to believe that our UI is easier to navigate than some of > the other options. Plus, I'd be happy to help migrate your issues from > Google Code to FogBugz on your behalf, with full history if you'd like. Fog Creek, rings a bell... right the Trello guys ;) that's a very good start ;) > I know I pretty much lurk on this list these days, but I've been > programming in Squeak since 1996 and Pharo since it came into existence; > giving all of you a free, good bug tracker would make me quite happy. I am evaluating it right now ;) looks nice so far. Just for the record, even though I am right now the only one driving this conversation I am by far not the person to decide ;) but I hope I can at least filter out some rusty solutions...

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Benjamin Pollack

On Fri, Feb 8, 2013, at 04:04 PM, Camillo Bruni wrote: > > On 2013-02-08, at 21:58, "Esteban A. Maringolo" <emaringolo(a)gmail.com> > wrote: > > > (regarding Mantis) > > > > 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> we used it for squeak and I never liked it. > > > > It is ugly as it gets, I don't like its appearance either. I won't > > argue on that :) > > > > But it is reliable, flexible and full of features. > > > > We talked about migrating to JIRA, but we have ~12000 issues tracked, > > and moving off is not an option by now. > > > > On aesthetics I like the simplicity of GitHub or the "style" of JIRA > > (some bloatware can be removed and/or hidden). > > true JIRA is already much better. But still compared to trac or github... > :D > > Well in the end we might survive with JIRA as well ;) since issues should > be > filed in from the image directly. So the interface is mostly a problem > for the > integrators ;) Fog Creek would be happy to provide all of you with a free FogBugz On Demand account. It has a good API, it has file attachments, it has custom workflows, triggers, and plugins, and we're about to release a version that's Gmail-level fast (which I could turn on immediately for a Pharo account, so you don't have to use the existing "slow" version). I know it's a relatively complete tracker compared to e.g. GitHub Issues, but I'd like to believe that our UI is easier to navigate than some of the other options. Plus, I'd be happy to help migrate your issues from Google Code to FogBugz on your behalf, with full history if you'd like. I know I pretty much lurk on this list these days, but I've been programming in Squeak since 1996 and Pharo since it came into existence; giving all of you a free, good bug tracker would make me quite happy. --Benjamin

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

On 2013-02-08, at 21:58, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > (regarding Mantis) > > 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> we used it for squeak and I never liked it. > > It is ugly as it gets, I don't like its appearance either. I won't > argue on that :) > > But it is reliable, flexible and full of features. > > We talked about migrating to JIRA, but we have ~12000 issues tracked, > and moving off is not an option by now. > > On aesthetics I like the simplicity of GitHub or the "style" of JIRA > (some bloatware can be removed and/or hidden). true JIRA is already much better. But still compared to trac or github... :D Well in the end we might survive with JIRA as well ;) since issues should be filed in from the image directly. So the interface is mostly a problem for the integrators ;)

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Esteban A. Maringolo

(regarding Mantis) 2013/2/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > we used it for squeak and I never liked it. It is ugly as it gets, I don't like its appearance either. I won't argue on that :) But it is reliable, flexible and full of features. We talked about migrating to JIRA, but we have ~12000 issues tracked, and moving off is not an option by now. On aesthetics I like the simplicity of GitHub or the "style" of JIRA (some bloatware can be removed and/or hidden). Regards, Esteban A. Maringolo

Feb. 8, 2013

Re: [Pharo-project] FileTree

by Camillo Bruni

On 2013-02-07, at 14:17, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Loading FileTree like this (I assume this is the official way): > > Gofer new > url: 'http://ss3.gemstone.com/ss/FileTree'; > package: 'ConfigurationOfFileTree'; > load. > ((Smalltalk at: #ConfigurationOfFileTree) project version: #'stable') load. > > in Pharo 2.0 (20511) makes two system packages dirty: > > Monticello (MCVersionInfo #date & #time were removed). > MonticelloGUI (MCFileRepositoryInspector #refresh was removed). > > shouldn't it just load cleanly ? I would assume so... => maybe open an issue on https://github.com/dalehenrich/filetree

Feb. 8, 2013