April 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by Esteban Lorenzano

> On 7 Apr 2017, at 19:28, Ben Coman <btc(a)openinworld.com> wrote: > > I was disappointed that conversation didn't pick up in discord after the last announcement. it wasâ¦ but today is friday, people always talk less :) Esteban > > cheers -ben > > P.S. > I'm interested in playing with the discord API. > https://discordapp.com/developers/docs/reference <https://discordapp.com/developers/docs/reference> > but I can't get past the first step of OAuth authentication. > https://discordapp.com/developers/docs/topics/oauth2 <https://discordapp.com/developers/docs/topics/oauth2> > > I tried a few weeks ago reading through several of the top Pharo OAuth search links, > but it was beyond my ken and I got discouraged. Perhaps some kind soul > with past OAuth experience would find it easier to crack and open the door > for others to work on the remaining API. > > Perhaps we could do something similar to the Google API Service Discovery tool > https://www.min.at/prinz/?x=entry:entry150318-104537 <https://www.min.at/prinz/?x=entry:entry150318-104537> > > I got a list of endpoints > https://gist.github.com/SinisterRectus/9518f3e7d0d1ccb4335b2a0d389c30b0 <https://gist.github.com/SinisterRectus/9518f3e7d0d1ccb4335b2a0d389c30b0> > from the API chat channel > https://discordapp.com/invite/discord-api <https://discordapp.com/invite/discord-api> > > It would be cool to have a chat channel inside a Pharo Image that could > understand dropped Class>>method links. Also a group voice channel from within > Pharo might be a good adjunct to a game engine like Ronnie is developing. > > more cheers -ben > > On Sat, Apr 8, 2017 at 12:25 AM, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > That's the solution Unreal followed , they were on Slack , the shut it down and left a message. > > Moving to Discord is super easy and it literally takes a minute. We can leave an invite link to the closed Slack and that's it. > There is no need to wait for a planatery alignment or GSOC. It's far more complicated to setup ah fogbuz account for reporting Pharo bugs. There is also nothing new to learn for its usage. I also have a custom made bot made in Python which we can customize to accommodate for specific needs. > > > On Fri, 7 Apr 2017 at 16:00, Esteban A. Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: > We could shut down Slack team or leave a sticky note in the general > channel saying that we moved everything to Discord. > > Regards! > > > Esteban A. Maringolo > > > 2017-04-07 9:39 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>>: > > I would not mind moving to Discord. But, what is the plan to kill Slack? Can > > a Slack project be simply removed? > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > On Apr 7, 2017, at 8:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > Hi, > > > > That. > > Iâm also willing to try another service if you find something better, but I > > find discord cool enough. > > Some remarks: > > > > - I actually like Slack. The problem is the amount of information lost > > because they do not display more than 10k lines (or we pay, and is super > > expensive). > > - No, plain #irc is not an option. Community has talkedâ¦ and it does not > > worksâ¦ I have had more productive talks in one month in Slack than 5 years > > trying #irc. > > > > cheers! > > Esteban > > > > > > > >

April 7, 2017

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by Ben Coman

I was disappointed that conversation didn't pick up in discord after the last announcement. cheers -ben P.S. I'm interested in playing with the discord API. https://discordapp.com/developers/docs/reference but I can't get past the first step of OAuth authentication. https://discordapp.com/developers/docs/topics/oauth2 I tried a few weeks ago reading through several of the top Pharo OAuth search links, but it was beyond my ken and I got discouraged. Perhaps some kind soul with past OAuth experience would find it easier to crack and open the door for others to work on the remaining API. Perhaps we could do something similar to the Google API Service Discovery tool https://www.min.at/prinz/?x=entry:entry150318-104537 I got a list of endpoints https://gist.github.com/SinisterRectus/9518f3e7d0d1ccb4335b2a0d389c30b0 from the API chat channel https://discordapp.com/invite/discord-api It would be cool to have a chat channel inside a Pharo Image that could understand dropped Class>>method links. Also a group voice channel from within Pharo might be a good adjunct to a game engine like Ronnie is developing. more cheers -ben On Sat, Apr 8, 2017 at 12:25 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > That's the solution Unreal followed , they were on Slack , the shut it > down and left a message. > > Moving to Discord is super easy and it literally takes a minute. We can > leave an invite link to the closed Slack and that's it. > There is no need to wait for a planatery alignment or GSOC. It's far more > complicated to setup ah fogbuz account for reporting Pharo bugs. There is > also nothing new to learn for its usage. I also have a custom made bot made > in Python which we can customize to accommodate for specific needs. > > > On Fri, 7 Apr 2017 at 16:00, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > >> We could shut down Slack team or leave a sticky note in the general >> channel saying that we moved everything to Discord. >> >> Regards! >> >> >> Esteban A. Maringolo >> >> >> 2017-04-07 9:39 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >> > I would not mind moving to Discord. But, what is the plan to kill >> Slack? Can >> > a Slack project be simply removed? >> > >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > On Apr 7, 2017, at 8:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> > >> > Hi, >> > >> > That. >> > Iâm also willing to try another service if you find something better, >> but I >> > find discord cool enough. >> > Some remarks: >> > >> > - I actually like Slack. The problem is the amount of information lost >> > because they do not display more than 10k lines (or we pay, and is super >> > expensive). >> > - No, plain #irc is not an option. Community has talkedâ¦ and it does not >> > worksâ¦ I have had more productive talks in one month in Slack than 5 >> years >> > trying #irc. >> > >> > cheers! >> > Esteban >> > >> > >> > >> >>

April 7, 2017

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by Dimitris Chloupis

That's the solution Unreal followed , they were on Slack , the shut it down and left a message. Moving to Discord is super easy and it literally takes a minute. We can leave an invite link to the closed Slack and that's it. There is no need to wait for a planatery alignment or GSOC. It's far more complicated to setup ah fogbuz account for reporting Pharo bugs. There is also nothing new to learn for its usage. I also have a custom made bot made in Python which we can customize to accommodate for specific needs. On Fri, 7 Apr 2017 at 16:00, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > We could shut down Slack team or leave a sticky note in the general > channel saying that we moved everything to Discord. > > Regards! > > > Esteban A. Maringolo > > > 2017-04-07 9:39 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > > I would not mind moving to Discord. But, what is the plan to kill Slack? > Can > > a Slack project be simply removed? > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > On Apr 7, 2017, at 8:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > Hi, > > > > That. > > Iâm also willing to try another service if you find something better, > but I > > find discord cool enough. > > Some remarks: > > > > - I actually like Slack. The problem is the amount of information lost > > because they do not display more than 10k lines (or we pay, and is super > > expensive). > > - No, plain #irc is not an option. Community has talkedâ¦ and it does not > > worksâ¦ I have had more productive talks in one month in Slack than 5 > years > > trying #irc. > > > > cheers! > > Esteban > > > > > > > >

April 7, 2017

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by Serge Stinckwich

On Fri, Apr 7, 2017 at 4:39 PM, philippe.back(a)highoctane.be <philippe.back(a)gmail.com> wrote: > We just invited gsoc students and we have the mentors channel running and > then we shit things down. We can keep this until the GSOC is finish. -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 7, 2017

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by philippe.back＠highoctane.be

We just invited gsoc students and we have the mentors channel running and then we shit things down. Lame. Phil Le 7 avr. 2017 15:06, "Norbert Hartl" <norbert(a)hartl.name> a Ã©crit : > If enough people move and there is a note the others will follow > > Norbert > > Am 07.04.2017 um 14:39 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > > I would not mind moving to Discord. But, what is the plan to kill Slack? > Can a Slack project be simply removed? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Apr 7, 2017, at 8:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > That. > Iâm also willing to try another service if you find something better, but > I find discord cool enough. > Some remarks: > > - I actually like Slack. The problem is the amount of information lost > because they do not display more than 10k lines (or we pay, and is super > expensive). > - No, plain #irc is not an option. Community has talkedâ¦ and it does not > worksâ¦ I have had more productive talks in one month in Slack than 5 years > trying #irc. > > cheers! > Esteban > > > > >

April 7, 2017

Re: [Pharo-dev] Rationale behind the "ifTrue:/ifFalse: returns instead of and:/or:'s" rule

by John Brant

> 2) I just want to know why someone created such rule :). Because the author of the last update of the initialize method is Marcus :) Probably to stop people from writing code like this: (borderColor isColor and: [ borderColor isTranslucentButNotTransparent ]) ifTrue: [ ^ true ]. ^ false instead of: ^borderColor isColor and: [ borderColor isTranslucentButNotTransparent ] :) John Brant

April 7, 2017

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by Norbert Hartl

If enough people move and there is a note the others will follow Norbert > Am 07.04.2017 um 14:39 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > > I would not mind moving to Discord. But, what is the plan to kill Slack? Can a Slack project be simply removed? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Apr 7, 2017, at 8:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> Hi, >> >> That. >> Iâm also willing to try another service if you find something better, but I find discord cool enough. >> Some remarks: >> >> - I actually like Slack. The problem is the amount of information lost because they do not display more than 10k lines (or we pay, and is super expensive). >> - No, plain #irc is not an option. Community has talkedâ¦ and it does not worksâ¦ I have had more productive talks in one month in Slack than 5 years trying #irc. >> >> cheers! >> Esteban >> >> >

April 7, 2017

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

by Esteban A. Maringolo

We could shut down Slack team or leave a sticky note in the general channel saying that we moved everything to Discord. Regards! Esteban A. Maringolo 2017-04-07 9:39 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > I would not mind moving to Discord. But, what is the plan to kill Slack? Can > a Slack project be simply removed? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Apr 7, 2017, at 8:59 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > That. > Iâm also willing to try another service if you find something better, but I > find discord cool enough. > Some remarks: > > - I actually like Slack. The problem is the amount of information lost > because they do not display more than 10k lines (or we pay, and is super > expensive). > - No, plain #irc is not an option. Community has talkedâ¦ and it does not > worksâ¦ I have had more productive talks in one month in Slack than 5 years > trying #irc. > > cheers! > Esteban > > >

April 7, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60463 Home: https://github.com/pharo-project/pharo-core

April 7, 2017

[pharo-project/pharo-core] f11e1b: 60463

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f11e1b23580a181c6391f80fb53bda19c4f690a7 https://github.com/pharo-project/pharo-core/commit/f11e1b23580a181c6391f80f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-07 (Fri, 07 Apr 2017) Changed paths: M ConfigurationOfFlatQA.package/ConfigurationOfFlatQA.class/instance/symbolic versions/stable_.st A ConfigurationOfFlatQA.package/ConfigurationOfFlatQA.class/instance/versions/versionv3%5F3%5F1_.st R QualityAssistant.package/QANautilusPluginMorph.class/instance/updating/themeChanged.st M QualityAssistant.package/QASettings.class/class/settings-definition/qaNautilusPlugginSettingOn_.st R QualityAssistant.package/QASettings.class/class/settings-definition/settingsMoovedNotice_.st R Renraku.package/extension/RBUndeclaredReferenceRule/instance/check_forCritiquesDo_.st R Renraku.package/extension/RBVariableNotDefinedRule/instance/check_forCritiquesDo_.st M Renraku.package/extension/TBehavior/instance/glmCritiqueSourceIn_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60462.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60463.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60462.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60463.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-BasicCommandLineHandler.package/CommandLineHandler.class/instance/accessing/name.st Log Message: ----------- 60463 19923 QA v3.3.1 https://pharo.fogbugz.com/f/cases/19923 19922 System-BasicCommandLineHandler calls name method https://pharo.fogbugz.com/f/cases/19922 http://files.pharo.org/image/60/60463.zip

April 7, 2017