October 2022 - Pharo-vm - lists.pharo.org

Looking for an engineer position to work on Virtual Machines

by Pierre Misse-Chanabier

Hello, My name is Pierre Misse-Chanabier. I'm finishing my PhD in the RMOD team on testing Virtual Machines in about two months. I am therefore looking for a Job, hopefully in the Pharo community ! Ideally, I'm looking to work in the domains of Virtual Machines or Language Tooling, or Meta-programing, but I'm open to other opportunities. See my CV attached. I have to stay in Lille for at least the next year, therefore, I am looking to work remotely. Here are my most important projects and publications about them: Illicium : a framework to generate C code from Pharo code. Github repository: [ https://github.com/hogoww/Illicium | https://github.com/hogoww/Illicium ] IWST'19 Illicium: A modular transpilation toolchain from Pharo to C [ https://hal.archives-ouvertes.fr/hal-02297860/ | https://hal.archives-ouvertes.fr/hal-02297860/ ] version poster SAC'22 & full ICSR'22: Differential testing of simulation-based VM generators: automatic detection of VM generator semantic gaps between simulation and generated VMs [ https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 | https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 ] [ https://dl.acm.org/doi/abs/10.1145/3477314.3507171 | https://dl.acm.org/doi/abs/10.1145/3477314.3507171 ] Polyphemus: Retro engineering of the Pharo Image, and ease of VM tooling Github Repository: [ https://github.com/hogoww/Polyphemus/ | https://github.com/hogoww/Polyphemus/ ] Video Presentation for Esug Innovation award (I was unable to present it myself): [ https://www.youtube.com/watch?v=zf3cCtNW830 | https://www.youtube.com/watch?v=zf3cCtNW830 ] VMIL'22: Ease VM Level Tooling with Language Level Ordinary Object Pointers [ https://hal.inria.fr/hal-03827632 | https://hal.inria.fr/hal-03827632 ] (preprint) I am particularly interested in my latest work: Polyphemus. I have also worked on many part of the Pharo ecosystem. The Pharo VM, The Pharo bootstrap, Calypso, Debugger, selector extraction, Iceberg scripting, SUnit ... Let me know if you have openings or questions ! Pierre

Oct. 25, 2022

Re: Cleaning stale branches

by Guille Polito

Thanks Luc! We have done some cleaning there, I hope thatâs better now. G > El 5 oct 2022, a las 15:50, Luc Fabresse <luc.fabresse(a)imt-nord-europe.fr> escribiÃ³: > > Hello, > > Propositions: > > - PharoX = should be the default branch (dev branch) > - Pharo9 = the current stable branch > - Cog -> I would keep cog because Pharo-0 is misleading ; it looks like that it is the VM for Pharo Image v 0 :-) > - pharo -> yes remove it > - dev-7 -> cog-pharo7 ? > - headless -> feat/headless ? to me, it is a feature branch that started on top of cog > > Luc > > Le mer. 5 oct. 2022 Ã 10:37, Guille Polito <guillermo.polito(a)inria.fr <mailto:guillermo.polito@inria.fr>> a Ã©crit : > We have a couple of stale branches, named a bit chaotically, Iâd like to rename them in a good way, but I donât remember what they are about :) > The numbers below (behind | ahead) are according to the current stable pharo9 branch. > > <GrÃ¡fico_pegado-3.png> > > <GrÃ¡fico_pegado-4.png> > > - headless has already the new tree organisation with cmake > - dev-7 and pharo branches have the old tree organisation, dev-7 has some bugfixes when comparing to `pharo` > - Cog has the original imported version from monticello > > Maybe we can have some naming convention for branches? > > - pharo-[version] to denote major development version branches > - feat/[feature] for feature branches if needed > > Then the four above should be renamed accordingly. Something on the lines of... > > - Cog -> rename as pharo-0? > - pharo -> can be removed > - dev-7 -> pharo-1 > - headless -> pharo-2 > > ? > > G > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org <mailto:pharo-vm@lists.pharo.org> > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org <mailto:pharo-vm-leave@lists.pharo.org> > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org

Oct. 5, 2022

Re: Making pharoX the default branch

by Guille Polito

Thanks for the input! This is now done! > El 5 oct 2022, a las 15:21, Luc Fabresse <luc.fabresse(a)imt-nord-europe.fr> escribiÃ³: > > > +1 > > --+- (default) dev - Pharo X (nowadays) ---> > | |--- feature || PR ---> # will be merged in default > |--- releases ---> > > BTW: I wanted to do a pass on the wiki pages of the VM repo but I think I need rights for that. do you confirm? > > Cheers, > Luc > > Le mer. 5 oct. 2022 Ã 10:58, tesonep(a)gmail.com <mailto:tesonep@gmail.com> <tesonep(a)gmail.com <mailto:tesonep@gmail.com>> a Ã©crit : > I think is a good idea, go ahead > > On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito(a)inria.fr <mailto:guillermo.polito@inria.fr>> wrote: > Hi all, > > We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. > Itâs just a convenience for dev. > Thoughts? > > What should we add in the readme to make sure people do not make mistakes? > - say that stable versions are in releases? > - say the default branch is always dev? > > cheers, > G & J > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org <mailto:pharo-vm@lists.pharo.org> > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org <mailto:pharo-vm-leave@lists.pharo.org> > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org <mailto:pharo-vm@lists.pharo.org> > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org <mailto:pharo-vm-leave@lists.pharo.org> > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org

Oct. 5, 2022

Re: Cleaning stale branches

by Luc Fabresse

Hello, Propositions: - PharoX = should be the default branch (dev branch) - Pharo9 = the current stable branch - Cog -> I would keep cog because Pharo-0 is misleading ; it looks like that it is the VM for Pharo Image v 0 :-) - pharo -> yes remove it - dev-7 -> cog-pharo7 ? - headless -> feat/headless ? to me, it is a feature branch that started on top of cog Luc Le mer. 5 oct. 2022 Ã 10:37, Guille Polito <guillermo.polito(a)inria.fr> a Ã©crit : > We have a couple of stale branches, named a bit chaotically, Iâd like to > rename them in a good way, but I donât remember what they are about :) > The numbers below (behind | ahead) are according to the current stable > pharo9 branch. > > > > - headless has already the new tree organisation with cmake > - dev-7 and pharo branches have the old tree organisation, dev-7 has some > bugfixes when comparing to `pharo` > - Cog has the original imported version from monticello > > Maybe we can have some naming convention for branches? > > - pharo-[version] to denote major development version branches > - feat/[feature] for feature branches if needed > > Then the four above should be renamed accordingly. Something on the lines > of... > > - Cog -> rename as pharo-0? > - pharo -> can be removed > - dev-7 -> pharo-1 > - headless -> pharo-2 > > ? > > G > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >

Oct. 5, 2022

Re: Making pharoX the default branch

by Luc Fabresse

+1 --+- (default) dev - Pharo X (nowadays) ---> | |--- feature || PR ---> # will be merged in default |--- releases ---> BTW: I wanted to do a pass on the wiki pages of the VM repo but I think I need rights for that. do you confirm? Cheers, Luc Le mer. 5 oct. 2022 Ã 10:58, tesonep(a)gmail.com <tesonep(a)gmail.com> a Ã©crit : > I think is a good idea, go ahead > > On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito(a)inria.fr> > wrote: > >> Hi all, >> >> We were thinking here with Jean Privat that we could make the pharoX >> branch (the dev branch) the default branch in the repository. >> Itâs just a convenience for dev. >> Thoughts? >> >> What should we add in the readme to make sure people do not make mistakes? >> - say that stable versions are in releases? >> - say the default branch is always dev? >> >> cheers, >> G & J >> _______________________________________________ >> Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org >> To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >> > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >

Oct. 5, 2022

Re: Making pharoX the default branch

by tesonep＠gmail.com

I think is a good idea, go ahead On Wed, Oct 5, 2022, 10:20 Guille Polito <guillermo.polito(a)inria.fr> wrote: > Hi all, > > We were thinking here with Jean Privat that we could make the pharoX > branch (the dev branch) the default branch in the repository. > Itâs just a convenience for dev. > Thoughts? > > What should we add in the readme to make sure people do not make mistakes? > - say that stable versions are in releases? > - say the default branch is always dev? > > cheers, > G & J > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >

Oct. 5, 2022

Cleaning stale branches

by Guille Polito

We have a couple of stale branches, named a bit chaotically, Iâd like to rename them in a good way, but I donât remember what they are about :) The numbers below (behind | ahead) are according to the current stable pharo9 branch. - headless has already the new tree organisation with cmake - dev-7 and pharo branches have the old tree organisation, dev-7 has some bugfixes when comparing to `pharo` - Cog has the original imported version from monticello Maybe we can have some naming convention for branches? - pharo-[version] to denote major development version branches - feat/[feature] for feature branches if needed Then the four above should be renamed accordingly. Something on the lines of... - Cog -> rename as pharo-0? - pharo -> can be removed - dev-7 -> pharo-1 - headless -> pharo-2 ? G

Oct. 5, 2022

Re: Making pharoX the default branch

by Norbert Hartl

I think it is good to have the main trunk being dev. The project is about developing pharo so that says it all. Furthermore tools tend to branch of the default branch mostly. So that would avoid a lot errornous PRs I guess. Stable should always branch off and receive hotfixes. My 2 cents, Norbert > Am 05.10.2022 um 10:20 schrieb Guille Polito <guillermo.polito(a)inria.fr>: > > ï»¿Hi all, > > We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. > Itâs just a convenience for dev. > Thoughts? > > What should we add in the readme to make sure people do not make mistakes? > - say that stable versions are in releases? > - say the default branch is always dev? > > cheers, > G & J > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org

Oct. 5, 2022

Making pharoX the default branch

by Guille Polito

Hi all, We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. Itâs just a convenience for dev. Thoughts? What should we add in the readme to make sure people do not make mistakes? - say that stable versions are in releases? - say the default branch is always dev? cheers, G & J

Oct. 5, 2022