- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi, Thanks! It seems to work now. Cheers, Doru > On Sep 15, 2016, at 12:13 AM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Hi Doru, > > it looks like thereâs a problem with copySupport.mk, I had the same problem with the Spec booklet. The file is using Linux only syntax for the cp command. This was fixed for the Spec booklet after I raised an issue there, but it seems the fix was not propagated everywhere it needs to be. Have a look at https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/c… and try to update your copySupport, it may fix your problem. > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >> On Sep 14, 2016, at 18:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> Ok, I found this document: >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> And now I tried this: >> >> wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >> chmod +x download.sh >> ./download.sh >> ./pillar archetype book >> >> and I got the book template. But, I do not know how to compile the book. I tried >> >> make >> >> or >> make book >> >> but I get: >> >> make >> mkdir -p ./book-result >> find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp {} --parents -r ./book-result \; >> cp: ./Chapters/Chapter1/figures is a directory (not copied). >> cp: --parents: No such file or directory >> cp: -r: No such file or directory >> cp: ./figures is a directory (not copied). >> cp: --parents: No such file or directory >> cp: -r: No such file or directory >> cp: ./support/figures is a directory (not copied). >> cp: --parents: No such file or directory >> cp: -r: No such file or directory >> cp -r support/ ./book-result >> cp .latexmkrc ./book-result >> cp: .latexmkrc: No such file or directory >> make: *** [copySupport] Error 1 >> >> >> I must be doing something wrong, but I do not know what. I am on a Mac 10.11 and I am using bash. Could someone point me in the right direction? >> >> Cheers, >> Doru >> >> >>> On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Where can I find the new template system for Pillar? >>> >>> Cheers, >>> Doru >>> >>> >>>> On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: >>>> >>>> Hello, >>>> >>>> I'm happy to announce the latest release of Pillar. >>>> This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. >>>> What did it bring and what are the largest changes ? >>>> >>>> â¢ Huge cleaning of code and Dependencies >>>> â¢ Many bug fixes >>>> â¢ Huge refactoring of internal parts >>>> â¢ Extract phase management into an external project (LightPhaser) >>>> â¢ Transformers and Phases are all Pipes >>>> Remove Compilation cycle >>>> â¢ Remove template handling from Pillar >>>> â¢ Remove generation of pillarpostExport.sh >>>> â¢ Pillar now exports files to JSON format >>>> â¢ Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) >>>> â¢ Possibility to load an archetype with a Makefile to compile pillar files >>>> Features >>>> â¢ Check phase to check syntax >>>> â¢ EPub exporter for e-books (use pillar archetypes for this) >>>> â¢ Semantic links to Youtube and Wikipedia >>>> â¢ Citations for LaTeX >>>> â¢ Structures (see Pillar documentation) >>>> â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc >>>> â¢ Improvement of parsing configuration failure message >>>> Major changes >>>> â¢ Metadata field in configuration to separate data from configuration properties >>>> â¢ Support files in configuration does no longer exists >>>> â¢ "disableTransformers" property is now named "disabledPhases" >>>> â¢ AsciiDoc file extension is now ".asciidoc" >>>> â¢ Pillar now manages one input file, not a collection of input files anymore >>>> â¢ Parameter inputFiles is now replaced by inputFile >>>> The documentation of Pillar will be update as soon as possible to fit those changes. >>>> >>>> Cheers, >>>> >>>> Thibault >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Sometimes the best solution is not the best solution." >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "It's not how it is, it is how we see it." >> >> >> > > -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

Sept. 14, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Johan Fabry

Hi Doru, it looks like thereâs a problem with copySupport.mk, I had the same problem with the Spec booklet. The file is using Linux only syntax for the cp command. This was fixed for the Spec booklet after I raised an issue there, but it seems the fix was not propagated everywhere it needs to be. Have a look at https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/c… and try to update your copySupport, it may fix your problem. -- Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > On Sep 14, 2016, at 18:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Ok, I found this document: > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > And now I tried this: > > wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > chmod +x download.sh > ./download.sh > ./pillar archetype book > > and I got the book template. But, I do not know how to compile the book. I tried > > make > > or > make book > > but I get: > > make > mkdir -p ./book-result > find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp {} --parents -r ./book-result \; > cp: ./Chapters/Chapter1/figures is a directory (not copied). > cp: --parents: No such file or directory > cp: -r: No such file or directory > cp: ./figures is a directory (not copied). > cp: --parents: No such file or directory > cp: -r: No such file or directory > cp: ./support/figures is a directory (not copied). > cp: --parents: No such file or directory > cp: -r: No such file or directory > cp -r support/ ./book-result > cp .latexmkrc ./book-result > cp: .latexmkrc: No such file or directory > make: *** [copySupport] Error 1 > > > I must be doing something wrong, but I do not know what. I am on a Mac 10.11 and I am using bash. Could someone point me in the right direction? > > Cheers, > Doru > > >> On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> Where can I find the new template system for Pillar? >> >> Cheers, >> Doru >> >> >>> On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: >>> >>> Hello, >>> >>> I'm happy to announce the latest release of Pillar. >>> This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. >>> What did it bring and what are the largest changes ? >>> >>> â¢ Huge cleaning of code and Dependencies >>> â¢ Many bug fixes >>> â¢ Huge refactoring of internal parts >>> â¢ Extract phase management into an external project (LightPhaser) >>> â¢ Transformers and Phases are all Pipes >>> Remove Compilation cycle >>> â¢ Remove template handling from Pillar >>> â¢ Remove generation of pillarpostExport.sh >>> â¢ Pillar now exports files to JSON format >>> â¢ Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) >>> â¢ Possibility to load an archetype with a Makefile to compile pillar files >>> Features >>> â¢ Check phase to check syntax >>> â¢ EPub exporter for e-books (use pillar archetypes for this) >>> â¢ Semantic links to Youtube and Wikipedia >>> â¢ Citations for LaTeX >>> â¢ Structures (see Pillar documentation) >>> â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc >>> â¢ Improvement of parsing configuration failure message >>> Major changes >>> â¢ Metadata field in configuration to separate data from configuration properties >>> â¢ Support files in configuration does no longer exists >>> â¢ "disableTransformers" property is now named "disabledPhases" >>> â¢ AsciiDoc file extension is now ".asciidoc" >>> â¢ Pillar now manages one input file, not a collection of input files anymore >>> â¢ Parameter inputFiles is now replaced by inputFile >>> The documentation of Pillar will be update as soon as possible to fit those changes. >>> >>> Cheers, >>> >>> Thibault >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Sometimes the best solution is not the best solution." >> > > -- > www.tudorgirba.com > www.feenk.com > > "It's not how it is, it is how we see it." > > >

Sept. 14, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi, Ok, I found this document: https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… And now I tried this: wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh chmod +x download.sh ./download.sh ./pillar archetype book and I got the book template. But, I do not know how to compile the book. I tried make or make book but I get: make mkdir -p ./book-result find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp {} --parents -r ./book-result \; cp: ./Chapters/Chapter1/figures is a directory (not copied). cp: --parents: No such file or directory cp: -r: No such file or directory cp: ./figures is a directory (not copied). cp: --parents: No such file or directory cp: -r: No such file or directory cp: ./support/figures is a directory (not copied). cp: --parents: No such file or directory cp: -r: No such file or directory cp -r support/ ./book-result cp .latexmkrc ./book-result cp: .latexmkrc: No such file or directory make: *** [copySupport] Error 1 I must be doing something wrong, but I do not know what. I am on a Mac 10.11 and I am using bash. Could someone point me in the right direction? Cheers, Doru > On Sep 14, 2016, at 10:49 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Where can I find the new template system for Pillar? > > Cheers, > Doru > > >> On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: >> >> Hello, >> >> I'm happy to announce the latest release of Pillar. >> This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. >> What did it bring and what are the largest changes ? >> >> â¢ Huge cleaning of code and Dependencies >> â¢ Many bug fixes >> â¢ Huge refactoring of internal parts >> â¢ Extract phase management into an external project (LightPhaser) >> â¢ Transformers and Phases are all Pipes >> Remove Compilation cycle >> â¢ Remove template handling from Pillar >> â¢ Remove generation of pillarpostExport.sh >> â¢ Pillar now exports files to JSON format >> â¢ Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) >> â¢ Possibility to load an archetype with a Makefile to compile pillar files >> Features >> â¢ Check phase to check syntax >> â¢ EPub exporter for e-books (use pillar archetypes for this) >> â¢ Semantic links to Youtube and Wikipedia >> â¢ Citations for LaTeX >> â¢ Structures (see Pillar documentation) >> â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc >> â¢ Improvement of parsing configuration failure message >> Major changes >> â¢ Metadata field in configuration to separate data from configuration properties >> â¢ Support files in configuration does no longer exists >> â¢ "disableTransformers" property is now named "disabledPhases" >> â¢ AsciiDoc file extension is now ".asciidoc" >> â¢ Pillar now manages one input file, not a collection of input files anymore >> â¢ Parameter inputFiles is now replaced by inputFile >> The documentation of Pillar will be update as soon as possible to fit those changes. >> >> Cheers, >> >> Thibault > > -- > www.tudorgirba.com > www.feenk.com > > "Sometimes the best solution is not the best solution." > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

Sept. 14, 2016

Re: [Pharo-dev] Latest Configuration of XPath is broken

by Henrik Nergaard

Platform is Pharo 6 - Image 60202. Loading it again in the same image still gives the same error, also for -monty.92 I cannot replicate this error using a clean image, so It might have been some rare bug in how the repository were added or something. Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of monty Sent: Friday, September 9, 2016 3:00 PM To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] Latest Configuration of XPath is broken Looks OK: https://ci.inria.fr/pharo-contribution/job/XPath/PHARO=60,VERSION=stable,VM… >From the output: > Project: XMLParser release-2.8.7 [2.8.7] Could you try manually loading the latest ConfigurationOfXMLParser from its repo and using the latest XPath config again, and tell me what platform you're using (Pharo, Squeak, GS)? >From: "Henrik Nergaard" <henrik.nergaard(a)uia.no> >To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >Subject: [Pharo-dev] Latest Configuration of XPath is broken > >Hi, > >Trying to load XPath using the latest configuration (ConfigurationOfXPath-monty.91) gives the following error: >MetacelloProjectSpecLoadError: No version found for #'release-2.8.7' of ConfigurationOfXMLParser because: The symbolic version #'release-2.8.7' is not defined in ConfigurationOfXMLParser for the current platform. Possible symbolic version values include: #(#bleedingEdge #development #'release-2' #'release-2.4' #'release-2.5' #'release-2.5.3' #'release-2.5.5' #'release-2.6' #'release-2.6.3' #'release-2.6.5' #'release-2.6.8' #'release-2.7.3' #'release-2.7.4' #'release-2.7.6' #'release-2.7.7' #'release-2.8.1' #'release-2.8.3' #'release-2.8.6' #stable) > >ConfigurationOfXPath-monty.90 loads fine. > >Best regards,

Sept. 14, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi, Where can I find the new template system for Pillar? Cheers, Doru > On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <thibault.arloing(a)hotmail.fr> wrote: > > Hello, > > I'm happy to announce the latest release of Pillar. > This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. > What did it bring and what are the largest changes ? > > â¢ Huge cleaning of code and Dependencies > â¢ Many bug fixes > â¢ Huge refactoring of internal parts > â¢ Extract phase management into an external project (LightPhaser) > â¢ Transformers and Phases are all Pipes > Remove Compilation cycle > â¢ Remove template handling from Pillar > â¢ Remove generation of pillarpostExport.sh > â¢ Pillar now exports files to JSON format > â¢ Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) > â¢ Possibility to load an archetype with a Makefile to compile pillar files > Features > â¢ Check phase to check syntax > â¢ EPub exporter for e-books (use pillar archetypes for this) > â¢ Semantic links to Youtube and Wikipedia > â¢ Citations for LaTeX > â¢ Structures (see Pillar documentation) > â¢ Footnotes for HTML, Markdown, LaTeX and AsciiDoc > â¢ Improvement of parsing configuration failure message > Major changes > â¢ Metadata field in configuration to separate data from configuration properties > â¢ Support files in configuration does no longer exists > â¢ "disableTransformers" property is now named "disabledPhases" > â¢ AsciiDoc file extension is now ".asciidoc" > â¢ Pillar now manages one input file, not a collection of input files anymore > â¢ Parameter inputFiles is now replaced by inputFile > The documentation of Pillar will be update as soon as possible to fit those changes. > > Cheers, > > Thibault -- www.tudorgirba.com www.feenk.com "Sometimes the best solution is not the best solution."

Sept. 14, 2016

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] pillar support in gtinspector

by Tudor Girba

Hi Nicolai, Did you commit your changes with the highlight of == code? Cheers, Doru > On Sep 6, 2016, at 4:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-08-29 21:41 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this: > > Gofer new > smalltalkhubUser: 'Moose' project: 'PetitParser'; > package: 'PetitAnalyzer'; > package: 'PetitIndent'; > package: 'PetitIslands'; > smalltalkhubUser: 'Moose' project: 'GToolkit'; > package: 'GT-InspectorExtensions-Pillar'; > load > > Then you can just inspect a book folder and you get this: > > <inspector-pillar.png> > > I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes. > > It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start. > > Cheers, > Doru > > > nice! > > I just played a bit with the code to apply larger different font sizes for the headings and > use the code styler for inlined code ("=="). > > Maybe we should use a different code styler or add a way to instruct the styler to ignore unknown classes or uknown selectors :) > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Sept. 14, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by stepharo

> Hi nicolai > > Why we should not accept > > foo > <func: (3+4) res:0> > ^ self > > and be forced to put around '' > > foo > < func: '(3+4)' res: 0 > > ^ self > > I understand that we store literal but why you do not like it :). > > > First of all, the old compiler did not accept this. And I am a bit > sensitive about changes, we allow a different syntax > just because RB happens to allow this (and maybe no one knows why or > it just does not happens on purpose). valid point. > > And another reason, even without my fix, if we don't put quotes around > that expression, the reformatting the source will convert this to: > > foo > <func: #(3 #+ 4) res: 0> > ^ self What I noticed is that I could not write foo <expr: 3 + 4 result: 7> but it worked when I put () so I did it in the new code I wrote. > And, even if (3+4) looks like an expression, it is just a list of > literals something like this: > > foo > <func: ([[[}}}) res:0> > ^ self > > would be allowed too. This one is ugly > But of course this is only my own opinion :) > > We can change it back and maybe add support for the reformatter to not > convert it to the literal array #(3 #+ 4) . I do not know in fact this is why I asked :) Now may be my idea to use pragma to get something like pythondoctest is a bad idea but I really want to have literal programming. What do you think? If we have ' ' then it would be good that the syntax higlighter works with a special mode inside the ' ' > > > nicolai > > > > Stef > > > 60220 > 19086 do not allow expressions as pragma arguments > https://pharo.fogbugz.com/f/cases/19086 > <https://pharo.fogbugz.com/f/cases/19086> > > > >

Sept. 14, 2016

Re: [Pharo-dev] [ANN] Regular tech hangouts every month

by Dimitris Chloupis

My recommendation is that you use a live text chat whatever else you use. Generally speaking most video chat clients also include a text chat. A live text chat would allow for more people to participate especially people on slow connections. Of course the more people join on a video chat the bigger the latency. Voice chat is also tricky for long conversations because you have no indication when someone wants to talk or when someone is about to talk so people tend to talk one over the other which happens also on video chat too. So by starting with a live text you allow a lot of people to participate to the coversation, also in a live text chat you can have several conversations going on at the same time which makes things also a lot easier and faster. I have done Google Hangouts in the past, it was ok, the advantage of the hangouts and video chat is that it is dead easy to share a screen so its easy to show people what you talking about. I would not try Google Hangouts or any other video chat with more than 10 people, it would be crazy 20 people trying to find an opportunity to speak and the latency making things harder. On Wed, Sep 14, 2016 at 10:14 PM stepharo <stepharo(a)free.fr> wrote: > Hi esteban > > to get started we should use something that does not require videos and > see how it works. > > My teenagers at home use discord.... :( > > and they told me it works well. > > > Stef > > Le 14/9/16 Ã 14:50, Esteban Lorenzano a Ã©crit : > > Hi, > > > > Last board meeting we decided to take some actions to improve > communication and one of the ideas we had is to start some regular meetings > each month, to talk about current release development issues. > > > > Since Iâm the one who will do it, I decided: > > > > - I will handle those meetings every last Tuesday of every month at 16h > UTC (So people from America-The-Continent can joinâ¦ Yes, is a continent, > not a country) > > - I will send main topic one week earlier (but it will be an open > QA/brainstorm session). > > - You can send me topics you want to discuss anytime > > - I will *invite* (I mean: force) relevant people for topics to talk > (for example, Denis to talk about remote debugging, Pavel/Guille/Christophe > about bootstrap) > > > > I still do not know the medium: > > - terf? problem is that a) everybody needs to install a client (is not > heavy, but I think there is no linux client) and b) I still donât know how > the thing works ;) (but it would be cool to use a smalltalk app). > > - hangouts? Iâm fed up with the 10 limitâ¦ we (the consortium) are > willing to pay some (not *much*, but some) to have better sessions (we need > them also for consortium meetings who always runs out of slots). > > - other? > > > > Well, I will sort out this before the meeting :) > > > > Anywayâ¦ next tech meeting will beâ¦ (suspenseâ¦)â¦ > > > > Tuesday 27 September 16h UTC > > > > cheers, > > Esteban > > > > >

Sept. 14, 2016

Re: [Pharo-dev] [ANN] Regular tech hangouts every month

by stepharo

Hi esteban to get started we should use something that does not require videos and see how it works. My teenagers at home use discord.... :( and they told me it works well. Stef Le 14/9/16 Ã 14:50, Esteban Lorenzano a Ã©crit : > Hi, > > Last board meeting we decided to take some actions to improve communication and one of the ideas we had is to start some regular meetings each month, to talk about current release development issues. > > Since Iâm the one who will do it, I decided: > > - I will handle those meetings every last Tuesday of every month at 16h UTC (So people from America-The-Continent can joinâ¦ Yes, is a continent, not a country) > - I will send main topic one week earlier (but it will be an open QA/brainstorm session). > - You can send me topics you want to discuss anytime > - I will *invite* (I mean: force) relevant people for topics to talk (for example, Denis to talk about remote debugging, Pavel/Guille/Christophe about bootstrap) > > I still do not know the medium: > - terf? problem is that a) everybody needs to install a client (is not heavy, but I think there is no linux client) and b) I still donât know how the thing works ;) (but it would be cool to use a smalltalk app). > - hangouts? Iâm fed up with the 10 limitâ¦ we (the consortium) are willing to pay some (not *much*, but some) to have better sessions (we need them also for consortium meetings who always runs out of slots). > - other? > > Well, I will sort out this before the meeting :) > > Anywayâ¦ next tech meeting will beâ¦ (suspenseâ¦)â¦ > > Tuesday 27 September 16h UTC > > cheers, > Esteban >

Sept. 14, 2016

Re: [Pharo-dev] [ANN] Regular tech hangouts every month

by GastÃ³n Dall' Oglio

Hello all. In my work we begin to use www.zoom.us, it works really well. Looking at the characteristic for basic plan (free) seem to be enough: 50 participants, unlimited number of meetings, 40 minutes per meeting. https://zoom.us/pricing It have clients for all platforms https://zoom.us/download My 2 cents Cheers from America... the-continent :) 2016-09-14 9:50 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Last board meeting we decided to take some actions to improve > communication and one of the ideas we had is to start some regular meetings > each month, to talk about current release development issues. > > Since Iâm the one who will do it, I decided: > > - I will handle those meetings every last Tuesday of every month at 16h > UTC (So people from America-The-Continent can joinâ¦ Yes, is a continent, > not a country) > - I will send main topic one week earlier (but it will be an open > QA/brainstorm session). > - You can send me topics you want to discuss anytime > - I will *invite* (I mean: force) relevant people for topics to talk (for > example, Denis to talk about remote debugging, Pavel/Guille/Christophe > about bootstrap) > > I still do not know the medium: > - terf? problem is that a) everybody needs to install a client (is not > heavy, but I think there is no linux client) and b) I still donât know how > the thing works ;) (but it would be cool to use a smalltalk app). > - hangouts? Iâm fed up with the 10 limitâ¦ we (the consortium) are willing > to pay some (not *much*, but some) to have better sessions (we need them > also for consortium meetings who always runs out of slots). > - other? > > Well, I will sort out this before the meeting :) > > Anywayâ¦ next tech meeting will beâ¦ (suspenseâ¦)â¦ > > Tuesday 27 September 16h UTC > > cheers, > Esteban >

Sept. 14, 2016