- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Github and Fogbugz integration

by Tim Mackinnon

I also wonder when they measure the popularity of a language/community whether GitHub issues is a measure (I suspect it is), so it may be advantageous to show activity particularly for a smaller community. Like others, I'm not a big fan of fogbugz (never understood why Joel is considered a god), but it's ok, and it's served its purpose. I'd seriously switching. I Tim Sent from my iPhone > On 19 Aug 2017, at 21:40, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > >> On Sat, Aug 19, 2017 at 10:32 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> > I see little reason not to allow both ways of reporting bugs. >> It seems that the need to create an account in FB to even view/search issues has been a big barrier to new(er) would-be contributors. I expect this difficulty would be multiplied since, in the process of reporting a bug on GH, they would not be able to easily determine if it had already been opened on FB > > Tons of issues are reported in GH that are closed minutes as the issue they report does not even exist. Closing an issue is just a matter of pressing a button and you can always redirect the user to the issue in FB. > > Frankly I am no fan of FB, I find Github interface less powerful but far simpler and better designed. What annoyed me is that fogbuz did not even subscribed me to my own issues (issues I created) . I did not go back because I thought people ignored me , then one day I decided to create a new bug report and found out that people have replied almost immediately to my old ones. Then I realised that Fogbuz did not alert me through email , then I dig up its settings and found the way enable email alerts. Suffice to say I was not very happy with this. > > I prefer GH also because I have already been using it with Python way before I was introduced into Pharo, so its not just newcomer who will prefer GH , I think the vast majority of people coming from other languages will do too. GH is almost a monopoly at this point. > > Pretty much every one says moving to git and github will be costly , like Stef just did. Blender made the move I think a year ago, so much noise in the mailing list whether its really worth it moving from svn to git more than 1 million line of code and more than a decade of commits. Later admitted it was far easier than they expected. > > Point is that people are lazy, we are just are, and we like to keep doing things we are familiar with because learning is hard. Problem is not learning is far more costly. > > I have been a defender of git and github in the pharo mailing lists for years now even though many resisted me and tried to convince me how Pharo and git will never properly work and here we are, not regretting a second of it and I am sure that other people who were supportive too dont either. > > But I never forced my opinion on anyone and I wont now. I am just saying , if I have the choice between github and fogbuz, for me its github all the way. Likewise if its iceberger vs gitup , gitup all the way. > > On the other hand , its great to live in a time having so many choices ;)

Aug. 20, 2017

Launcher Opening Tiny Windows

by Sean P. DeNigris

Check out this screenshot. <http://forum.world.st/file/n4962615/Screenshot_2017-08-19_19.png> The red arrow points to an open "window" of a newly created Pharo 6.0 based image, minimized to the point of barely being visible. Clicking on it makes a title bar somewhat more visible, the edges of which can then be dragged as any other window. Anyone else seeing this? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-Opening-Tiny-Windows-tp4962615.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

by Sean P. DeNigris

Eliot Miranda-2 wrote > While basenameWithoutExtension is an intension revealing selector it is > soon loooonnnnngggg :-) For file manipulation code that's a problem. I > wonder if something like bodyName is better because it's shorter. While I too feel a bit of pain from the long selector, I have reservations with #bodyName because I already know I will not remember what that means and will have to constantly look it up. IIRC we already have #base and #basename, which seem to be made up labels for subtle distinctions and I can never remember the difference. I think the domain here is nuanced enough to defy simple labels. I remember when we first integrated FS there was confusion/unworkability around "extension" vs. "extensions" for e.g. /myfile.tar.zip vs. /mypackage.1.mcz ----- Cheers, Sean -- View this message in context: http://forum.world.st/19609-FileReference-base-should-be-before-last-separa… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-dev] Lowering the pain of newbies

by Sean P. DeNigris

Stephane Ducasse-3 wrote > any idea is welcome From http://forum.world.st/Woe-unto-thee-who-assigns-to-class-side-name-td485973… : Issue 16947: Class-side Inst Var "#name" Allowed, But Breaks System https://pharo.fogbugz.com/f/cases/16947/Class-side-Inst-Var-name-Allowed-Bu… ----- Cheers, Sean -- View this message in context: http://forum.world.st/Lowering-the-pain-of-newbies-tp4961937p4962584.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Dimitris Chloupis

On Sat, Aug 19, 2017 at 10:32 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I see little reason not to allow both ways of reporting bugs. > It seems that the need to create an account in FB to even view/search > issues has been a big barrier to new(er) would-be contributors. I expect > this difficulty would be multiplied since, in the process of reporting a > bug on GH, they would not be able to easily determine if it had already > been opened on FB Tons of issues are reported in GH that are closed minutes as the issue they report does not even exist. Closing an issue is just a matter of pressing a button and you can always redirect the user to the issue in FB. Frankly I am no fan of FB, I find Github interface less powerful but far simpler and better designed. What annoyed me is that fogbuz did not even subscribed me to my own issues (issues I created) . I did not go back because I thought people ignored me , then one day I decided to create a new bug report and found out that people have replied almost immediately to my old ones. Then I realised that Fogbuz did not alert me through email , then I dig up its settings and found the way enable email alerts. Suffice to say I was not very happy with this. I prefer GH also because I have already been using it with Python way before I was introduced into Pharo, so its not just newcomer who will prefer GH , I think the vast majority of people coming from other languages will do too. GH is almost a monopoly at this point. Pretty much every one says moving to git and github will be costly , like Stef just did. Blender made the move I think a year ago, so much noise in the mailing list whether its really worth it moving from svn to git more than 1 million line of code and more than a decade of commits. Later admitted it was far easier than they expected. Point is that people are lazy, we are just are, and we like to keep doing things we are familiar with because learning is hard. Problem is not learning is far more costly. I have been a defender of git and github in the pharo mailing lists for years now even though many resisted me and tried to convince me how Pharo and git will never properly work and here we are, not regretting a second of it and I am sure that other people who were supportive too dont either. But I never forced my opinion on anyone and I wont now. I am just saying , if I have the choice between github and fogbuz, for me its github all the way. Likewise if its iceberger vs gitup , gitup all the way. On the other hand , its great to live in a time having so many choices ;)

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Sean P. DeNigris

> I see little reason not to allow both ways of reporting bugs. It seems that the need to create an account in FB to even view/search issues has been a big barrier to new(er) would-be contributors. I expect this difficulty would be multiplied since, in the process of reporting a bug on GH, they would not be able to easily determine if it had already been opened on FB ----- Cheers, Sean -- View this message in context: http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962547.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Cyril Ferlicot

On sam. 19 aoÃ»t 2017 at 21:14, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Useless piece of info , I think I am the first person to actually create a > github issue for Pharo. It was not for pharo code it was for pharo > documentation > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues/1 > > Since then not only UPBE but also other pharo doc github repos have been > using github issues , so we already doing that and none has blamed me > > so far > > :D > I think this thread is about Pharo in itself. The github project "pharo-project/pharo". Not about the documentation or the independent projects as Pillar, Voyage & co. > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Dimitris Chloupis

Useless piece of info , I think I am the first person to actually create a github issue for Pharo. It was not for pharo code it was for pharo documentation https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues/1 Since then not only UPBE but also other pharo doc github repos have been using github issues , so we already doing that and none has blamed me so far :D On Sat, Aug 19, 2017 at 10:00 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi sean > > I prefer to continue to use fogbugz. Changing is really costly. > > Stef > > On Sat, Aug 19, 2017 at 6:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > Guillermo Polito wrote > >> Sadly, this just works for the integration of commits into the main > >> branches, not pull requests. For pull request integration we will > probably > >> need a home made solution. > > > > Now that we are moving development to GH, has there been any discussion > of > > moving issue tracking there as well? > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > >

Aug. 19, 2017

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

by Stephane Ducasse

Tx Holger!!!! Really tx. On Fri, Aug 18, 2017 at 11:54 AM, Holger Freyther <holger(a)freyther.de> wrote: > Hi, > > when running Pharo in production you might want to install the image and a VM from distribution packages. So far there were no current public packages and during the last months I have modernized the debian packaging and recently added CentOS rpm packaging as well. The process of generating new source packages is integrated into the pharo-vm travis-ci build as well. > > Every time that master of pharo-vm.git is updated a new source package will be uploaded to the Open(SUSE) Build Service and new packages will be built and are available in a "latest" package feed. The generated (and used) sourcecode is inside the source package and will be archived by the OBS platform (one can even nicely diff versions). The "stable" VM is not built from pharo-vm.git (yet?) so it doesn't show on OBS yet. > > Below are some semi-tested installation notes in case you want to try it out. The binary names are picked to allow to install the 32bit and 64bit VM in parallel. The names currently are: > > - pharo6-32 (32bit version) > - pharo6-64 (64bit version) > - pharo6-32-ui (32bit version with X11 dependencies) > - pharo6-64-ui (64bit version with X11 dependencies) > > > CentOS 6.8: > > # Add the repo > $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > > # Install 32bit packages (with X11 dependency for *-ui or not) > > $ yum install pharo6-32-ui.i686 or pharo6-32.i386 > > # Install 64bit packages > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > > CentOS 7 (only 64bit): > > > $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > Debian 8: > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/D… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui (or pharo6-32 or pharo6-64) > > Ubuntu 14.04 LTS > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui > > Ubuntu 16.04 > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui > > >

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Stephane Ducasse

Hi sean I prefer to continue to use fogbugz. Changing is really costly. Stef On Sat, Aug 19, 2017 at 6:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Guillermo Polito wrote >> Sadly, this just works for the integration of commits into the main >> branches, not pull requests. For pull request integration we will probably >> need a home made solution. > > Now that we are moving development to GH, has there been any discussion of > moving issue tracking there as well? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 19, 2017