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

Re: [Pharo-project] New Issue Tracker

by StÃ©phane Ducasse

On Feb 8, 2013, at 9:47 PM, Camillo Bruni wrote: > > On 2013-02-08, at 21:23, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > >> I would go for GitHub, its exposition is really good for the project. >> But if file attachments (other than pictures) is a showstopper, then... > > it is a show-stopper for now. A future development cycle might solve this, but > I don't want to change too many variables. > >> I would suggest: >> * Mantis (PHP Based, but with a SOAP API) http://mantisbt.org/ >> We've been using it in our company since 7 years ago, and it has >> proven to be really good. It's codebase is well organized too. Since a >> year or so, we integrated it with our development environment (Dolphin >> X6.1) by using its SOAP API (MantisConnect) and created some tool to >> version to and integrate from the issue repository. > > Maybe it is just me, but if I look at a page like this: > http://mantisbt.org/demo/view.php?id=15921 we used it for squeak and I never liked it. > I have to think how the heck you can make a website like this in 2012... > Then I feel more like investing a week of hacking to add a REST-API to trac :/ > >> * JIRA (Java Based) a little bloated, but highly customizable, I'm >> using its on-demand version this since two months ago. I'm not using >> any API. No judgement yet. > > > JIRA is pure overkill for me, yes it might solve a lot of issue and certainly > nice features, but I fear it is really too much

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

On 2013-02-08, at 21:23, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > I would go for GitHub, its exposition is really good for the project. > But if file attachments (other than pictures) is a showstopper, then... it is a show-stopper for now. A future development cycle might solve this, but I don't want to change too many variables. > I would suggest: > * Mantis (PHP Based, but with a SOAP API) http://mantisbt.org/ > We've been using it in our company since 7 years ago, and it has > proven to be really good. It's codebase is well organized too. Since a > year or so, we integrated it with our development environment (Dolphin > X6.1) by using its SOAP API (MantisConnect) and created some tool to > version to and integrate from the issue repository. Maybe it is just me, but if I look at a page like this: http://mantisbt.org/demo/view.php?id=15921 I have to think how the heck you can make a website like this in 2012... Then I feel more like investing a week of hacking to add a REST-API to trac :/ > * JIRA (Java Based) a little bloated, but highly customizable, I'm > using its on-demand version this since two months ago. I'm not using > any API. No judgement yet. JIRA is pure overkill for me, yes it might solve a lot of issue and certainly nice features, but I fear it is really too much

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

On 2013-02-08, at 21:19, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 8 February 2013 19:51, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> With the recent announcement of google code to shut down their public API I see >> a major functionality gone for our project. >> >> https://code.google.com/p/support/wiki/IssueTrackerAPI >> >> I would like to extend the functionality of our monkey, so it will become more intelligent: >> - give code critics feedback >> - reject new code that doesn't meet our criteria in general (unclassified methods / uncommented classes) >> - failing tests are serialized and attached to the issue >> - image with the changes integrated are attached to the issue >> >> ... you get the picture. All this stuff is impossible to achieve if there is no scriptable >> API available. By dropping that, google code becomes a silly toy with no further use to me. >> >> >> Requirements >> ------------ >> So, we have to come up with a new issue tracker by june with the following requirements: >> >> - dead simple issue reporting (most of the stuff out there just looks like a control panel for a space ship) >> - scriptable API >> - file attachements >> >> Additionally: >> - programmed in ruby or python >> - easily create sub-projects >> ...? >> >> Issue Tracker >> ------------- >> - I like trac a lot, but no API from what I read >> http://trac.edgewall.org/ >> - Jira, thats the space-ship-panel (and in this very same category, buzilla...) >> http://www.atlassian.com/software/jira >> - github? too simplistic no file upload >> https://github.com/dalehenrich/filetree/issues > > What's too simplistic, in particular? > > There's no file upload, but it does have an API and you could post > URLs to some server somewhere. What would be really cool is using the > git tools: you have a slice, you branch off master, apply the slice, > push the branch, and get github's diff. ok, that would work for most issues, but how do we deal with changes that require pre and post-scripts? Until we can rebuild our full image from sources we need to have pre- and postscripts for certain critical issues. Currently these scripts are communicated to the integrator, which is a very bad thing. I want to have that done automatically. => we need file uploads for a while we might be able to link gists into an issue. But I would prefer real files for now. June isn't that far away and I don't want to change too many variables at the same time. > You can signal bad pull requests by setting commit statuses on > commits: that API's pretty straightforward > (http://developer.github.com/v3/repos/statuses/) So the monkey could > apply lint rules etc., and colour the commit accordingly. I know of all of that and it is certainly what I want in the future but: - we do not run on git yet - we replace our main issue tracker so I would like to have something that works as close as possible to the existing solution we have.

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by Esteban A. Maringolo

2013/2/8 Tudor Girba <tudor(a)tudorgirba.com>: > Having an SSD? From my point of view, it's the best investment you can make in a machine these days. +1 I just added a mSATA SSD to my laptop (additionally to the HDD) and the speed improvement affects the whole system (I still don't understand why...) Regards, Esteban A. Maringolo

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Esteban A. Maringolo

I would go for GitHub, its exposition is really good for the project. But if file attachments (other than pictures) is a showstopper, then... I would suggest: * Mantis (PHP Based, but with a SOAP API) http://mantisbt.org/ We've been using it in our company since 7 years ago, and it has proven to be really good. It's codebase is well organized too. Since a year or so, we integrated it with our development environment (Dolphin X6.1) by using its SOAP API (MantisConnect) and created some tool to version to and integrate from the issue repository. * JIRA (Java Based) a little bloated, but highly customizable, I'm using its on-demand version this since two months ago. I'm not using any API. No judgement yet. Regards,

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Frank Shearar

On 8 February 2013 19:51, Camillo Bruni <camillobruni(a)gmail.com> wrote: > With the recent announcement of google code to shut down their public API I see > a major functionality gone for our project. > > https://code.google.com/p/support/wiki/IssueTrackerAPI > > I would like to extend the functionality of our monkey, so it will become more intelligent: > - give code critics feedback > - reject new code that doesn't meet our criteria in general (unclassified methods / uncommented classes) > - failing tests are serialized and attached to the issue > - image with the changes integrated are attached to the issue > > ... you get the picture. All this stuff is impossible to achieve if there is no scriptable > API available. By dropping that, google code becomes a silly toy with no further use to me. > > > Requirements > ------------ > So, we have to come up with a new issue tracker by june with the following requirements: > > - dead simple issue reporting (most of the stuff out there just looks like a control panel for a space ship) > - scriptable API > - file attachements > > Additionally: > - programmed in ruby or python > - easily create sub-projects > ...? > > Issue Tracker > ------------- > - I like trac a lot, but no API from what I read > http://trac.edgewall.org/ > - Jira, thats the space-ship-panel (and in this very same category, buzilla...) > http://www.atlassian.com/software/jira > - github? too simplistic no file upload > https://github.com/dalehenrich/filetree/issues What's too simplistic, in particular? There's no file upload, but it does have an API and you could post URLs to some server somewhere. What would be really cool is using the git tools: you have a slice, you branch off master, apply the slice, push the branch, and get github's diff. You can signal bad pull requests by setting commit statuses on commits: that API's pretty straightforward (http://developer.github.com/v3/repos/statuses/) So the monkey could apply lint rules etc., and colour the commit accordingly. frank > - redmine, possible kandidate > http://www.redmine.org/ > > > So what is your take on this?

Feb. 8, 2013

Re: [Pharo-project] [update 2.0] #20529

by StÃ©phane Ducasse

> > >> 20529 >> ----- >> >> Issue 7269: Code Critic automatically adds class without permission >> http://code.google.com/p/pharo/issues/detail?id=7269 > > ;-) Simon is improving the tools. He was fixing a bug and should release a new and better version. Stef > >> Issue 7238: LazyListMorph>>selectionFrameForRow: fails with a should not happen from Rectangle>>intersect:ifNone: >> http://code.google.com/p/pharo/issues/detail?id=7238 > > ;-) > >> >> Issue 6917: save as... to an already existing image throws a DNU >> http://code.google.com/p/pharo/issues/detail?id=6917 >> >> >> Diff information: >> http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.780.diff >> http://ss3.gemstone.com/ss/Pharo20/Manifest-Tests-MarcusDenker.26.diff >> http://ss3.gemstone.com/ss/Pharo20/Manifest-CriticBrowser-MarcusDenker.53.d… >> http://ss3.gemstone.com/ss/Pharo20/Manifest-Core-MarcusDenker.108.diff >> http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1304.diff >> >> > >

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by Tudor Girba

Having an SSD? From my point of view, it's the best investment you can make in a machine these days. Cheers, Doru On Feb 8, 2013, at 9:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor > > I would like to try on my new machine because may be if there is a large difference with yours we can plan to buy one with an SSD > and recycle yours. Does anybody have an idea if this is worth? > > Stef > >> pff... >> it finally built.. >> >> [ 99%] Building C object >> CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Prefs.c.obj >> [ 99%] Building C object >> CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Utils.c.obj >> Linking C executable /C/COG/blessed/results/Pharo.exe >> Creating library file: c:/COG/blessed/results/libPharo.dll.a >> [100%] Built target Pharo >> >> building all stuff from scratch takes a lot of time >> (cairo , freetype, png, ssl ...) >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- www.tudorgirba.com "Beauty is where we see it."

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by StÃ©phane Ducasse

Igor I would like to try on my new machine because may be if there is a large difference with yours we can plan to buy one with an SSD and recycle yours. Does anybody have an idea if this is worth? Stef > pff... > it finally built.. > > [ 99%] Building C object > CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Prefs.c.obj > [ 99%] Building C object > CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Utils.c.obj > Linking C executable /C/COG/blessed/results/Pharo.exe > Creating library file: c:/COG/blessed/results/libPharo.dll.a > [100%] Built target Pharo > > building all stuff from scratch takes a lot of time > (cairo , freetype, png, ssl ...) > > > -- > Best regards, > Igor Stasenko. >

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by StÃ©phane Ducasse

Thanks igor. We all know that some work is boring :) and I appreciate that you spend time on it without losing your soul :). Keep your great work and keep some energy for the fun part too :). Stef > - building VM on windows > - updating VM configs to use new location of NB > - fixes to NB for windows > - more precise copying of machine code for primitive 220 , to copy > exact machine code without extra garbage, > so it can fail primitive and won't run random machine instructions > > - testing if everything builds with "PharoVMBuilder build" > > > -- > Best regards, > Igor Stasenko. >

Feb. 8, 2013