June 2012 - Esug-list - lists.esug.org

Re: [Esug-list] [Pharo-project] **IMPORTANT** MUST READ: Pharo Association and Consortium

by Stéphane Ducasse

On Jun 30, 2012, at 12:46 PM, Herve Verjus wrote: > Hi All, > > thank you Stef for this piece of information. > > I will subscribe as individual member. > > Let's say, you're doing a good job, I enjoy a lot using Pharo, that let's me permit do/use funny and usefull things, teaching students, make some research software prototypes, etc. > I have to say I would probably not succeed in convincing my university staff to subscribe to the consortium. I personnaly vote for that, I will try and will do my best but I'am not optimistic :-( > I understand that the fees are intended for enterprises or organizations that aim to make business arround and/or with Pharo. I and my lab are not in such a perspective. Maybe I would succeed in convincing IAE director for some hundred euros for supporting your work...not for 1000 or more. Nevertheless, I will try. Thanks there is also the sponsoring possibility and the association can provide a bill for a pharo "distribution" So you can try to play with different budgets. > > All the best, > > Herve

June 30, 2012

Re: [Esug-list] [Pharo-users] **IMPORTANT** MUST READ: Pharo Association and Consortium

by stephane ducasse

Thanks marcus Having many golden individual members is also important because at the end many small contributors can change the world. I will be a gold member and RMOD will be either a golden consortium member or a silver one. For the first year RMOD will probably put more than golden consortium fees to support the consortium. The consortium for us a key for the future effort and community credibility so we will do as much as we can to support it. Stef >> ===================== >> *** Support and Answer needed*** >> ===================== >> >> To be able to pay an engineer by the consortium, INRIA needs to make projection, build budget, pay attention to visa >> and other important administrative tasks. To deal with the risk that the consortium may not collect enough to pay a full salary >> we are considering to ask INRIA to help us financially. To do so we have to give some concrete figures to >> INRIA and motivate our request. In addition, our team (RMOD) on its own budget will try to compensate by allocating extra resources >> However, this will be only a one shot. In addition, some of our team members have been approached by google to work on chrome and dart >> Virtual Machines. So if we really get a future we should build it now. >> > > I will be a personal golden member (99EUR/year) > > And with Norbert and Christian, we decided that http://2denker.de (2Denker GmbH) will be a Silver Member of the consortium. > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

June 30, 2012

Early registration deadline ESUG is *TODAY*

by Marcus Denker

The early registration deadline for this year's ESUG conference in Gent, Belgium, is **TODAY** More information about ESUG 2012: http://www.esug.org/Conferences/2012 A first schedule is available here: http://esug.org/wiki/pier/Conferences/2012/Conference-Schedule You can register for the conference at http://registration.esug.org -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker GmbH

June 30, 2012

Re: [Esug-list] [Pharo-users] **IMPORTANT** MUST READ: Pharo Association and Consortium

by Marcus Denker

On Jun 28, 2012, at 2:19 PM, Stéphane Ducasse wrote: > > ===================== > *** Support and Answer needed*** > ===================== > > To be able to pay an engineer by the consortium, INRIA needs to make projection, build budget, pay attention to visa > and other important administrative tasks. To deal with the risk that the consortium may not collect enough to pay a full salary > we are considering to ask INRIA to help us financially. To do so we have to give some concrete figures to > INRIA and motivate our request. In addition, our team (RMOD) on its own budget will try to compensate by allocating extra resources > However, this will be only a one shot. In addition, some of our team members have been approached by google to work on chrome and dart > Virtual Machines. So if we really get a future we should build it now. > I will be a personal golden member (99EUR/year) And with Norbert and Christian, we decided that http://2denker.de (2Denker GmbH) will be a Silver Member of the consortium. Marcus -- Marcus Denker -- http://marcusdenker.de

June 30, 2012

Re: [Esug-list] [Pharo-users] **IMPORTANT** MUST READ: Pharo Association and Consortium

by laurent laffont

On Thu, Jun 28, 2012 at 7:53 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi laurent > > > how do we subscribe to the consortium ? > > for now only company, institution, research group, labs, ... (non > individual people) can be member of the consortium > because of administrative details. INRIA lawyers are checking what can be > done. > We decided to make it simpler so that we can move on. The idea is that if > we want to avoid that a guy like igor got hired by google :( > we should make sure that we get some money for the consortium. Now to hire > somebody we have to plan in advance. > > Now you can be an Pharo association member. > In the future, if (I really hope) the consortium can sustain itself, it > will leave INRIA and be managed by the association > and in that case individual pharo members will be member of the consortium > with the same status as individual will get (because we cannot > really give the same to somebody paying 40 euros and a company paying > 1000/2000 Euros). > After since the consortium can offer payed engineer hours, everything is > possible. > > Esteban is working on the association web site right now. We are filling > up all the papers to get a bank account for the association. > > Does it answer your question? > Yes, thank you. Laurent > > Stef > > > > > > Laurent Laffont > > > > On Thu, Jun 28, 2012 at 7:38 PM, stephane ducasse < > stephane.ducasse(a)free.fr> wrote: > > I can open a wiki page to maintain the list of consortium member I > received. > > Let me know if it makes sense to you. > > > > Stef > > > > On Jun 28, 2012, at 2:19 PM, Stéphane Ducasse wrote: > > > > > Dear Pharoers and Smalltalkers > > > > > > This mail is really important so read it carefully. Especially the > last part of the mail is important for the > > > immediate future: we need your support and input. Read section > ***Support*** at the end of this mail. > > > > > > Context > > > ======= > > > After taking into account feedback from companies and pharo users in > different occasions and > > > discussing with the INRIA lawyers and the team in charge of the > administrative aspect of the consoritum > > > here is the setup we finally want for the consortium. We will have two > separated entities: > > > - one french law 1901 association for individuals and > > > - one consortium for institutions (companies, research groups, > laboratories, universities...) managed by INRIA > > > > > > We hope that in the long run the consortium will be fully managed by > the association > > > but in the current bootstrap phase INRIA is a good solution. > > > > > > ============== > > > The Pharo Association > > > ============== > > > The goal of the association is to promote Pharo. It will have its own > web site. > > > > > > Individual Memberships (managed by the Pharo Association) > > > ---------------------- > > > There are two individual memberships > > > - Individual Pharo Association Member: Yearly fee 40 > Euros > > > - Golden Individual Pharo Association Member: Yearly fee > 99 Euros > > > > > > You will get > > > a nice goody, > > > reduction access to conferences, > > > reduction for training and access to teaching material, > > > be part of the pharo groups on social networks, > > > be part of the pharoAssociation-individual-members > mailing-list, > > > get access and registered to the pharo association web > site. > > > > > > Others (managed by the Pharo Association) > > > ---------------------- > > > The association will be able to issues bills so you will be able > to buy a Pharo distribution > > > when your organization cannot be a member, a sponsor or doing a > donation to the Pharo consortium. > > > > > > End of Pharo Association Description > > > > > > > > > > > > =========================== > > > The Pharo Consortium (managed by INRIA) > > > =========================== > > > The goal of the consortium is to structure and build an umbrella to > foster business around Pharo and to promote Pharo. > > > > > > A company, user group, research group, team or institution can be a > consortium member, not individual member. > > > > > > There are three levels of fees and corresponding benefits. You decide > your degree of support. > > > The annual fees are > > > - Bronze 1000 Euros > > > - Silver 2000 Euros > > > - Gold 4000 Euros > > > > > > Consortium members main advantages are > > > ---------------------------------------- > > > Non individual members of the consortium get the following > advantages: > > > > > > - privileged access to the core development team via a > specific mailing-list > > > > pharo-core-team-for-members(a)lists.gforge.inria.fr > > > > > > - influence priorities of the next development. The > member will be able to propose > > > agenda points and items for the executive team. They > will be requested one month in > > > advance before the committee meeting. > > > > > > - get access to privileged core engineer time (to > address pharo core problems) > > > > > > - Bronze member gets > > > one day of engineering time > > > + is automatically a diamond > sponsor. > > > > > > - Silver > > > + two days of engineering time > > > + one job description for job > dashboard > > > + is automatically a diamond > sponsor.. > > > > > > - Gold four > > > + 4 days of engineering time > > > + multiple job description for > job dashboard > > > + is automatically a diamond > sponsor. > > > > > > - Training special prices and possibility to become > pharo trainer > > > - Pharo consortium member can also ask and pay for extra > support days at INRIA engineer prices (around 600 Euros) per day. > > > - Member can offer to their client access to the > possibility to pay for extra support days at INRIA engineer prices (around > 600 Euros) per day. > > > - The core team can provide contact with experts for > certain areas of development. > > > > > > Pharo Consortium Gouvernance: steering committee > > > ---------------------------------------- > > > The consortium will be managed as follows: There will be a > steering committee and an Executive Team. > > > > > > * A steering committee is composed of one representative > of each member (except individuals). > > > > > > * The chairman of this committee will be Inria > > > > > > * Steering Committee Role : > > > - The Steering Committee follows the execution > of the PHARO R&D Team > > > - It validates and gives input about the task > list of the Executive Team. > > > - It can propose members of the executive team. > > > - It prepares, organizes conferences, seminars > or other animations to promote PHARO and have new members > > > - It revises the annual fee > > > * Decisions taking: after consultation and collect of > representative member points of views, Inria takes the final decision. > > > > > > * The steering committee will communicate via a private > mailing-list. It may meet physical once a year. > > > > > > * An agenda to reach conclusion will be established by > Inria on proposals of the members (the members will be queried a month in > advance). > > > > > > Technical Executive Committee (akaR&D task) > > > ---------------------------------------- > > > * The Executive Team is composed of members proposed by > the steering board and RMOD Team > > > * Its roles is to > > > * Study, analyze and validate external > contributions for PHARO > > > * Report to the steering committee > > > * Present a task list to the steering committee. > > > * Propose, schedule and implement tasks in > conformance with the tasks list. > > > * Coordinate the release Pharo and its VMs > > > > > > Pharo consortium Sponsoring > > > --------------------------- > > > Orthogonally to memberships, an entity can be a sponsor > of the consortium without being a pharo consortium member. > > > Pharo consortium are de factor platinium sponsor. > Sponsors will get their logos name exposed to the consortium web site. > > > There are two kinds of sponsors: > > > - normal 500 Euros > > > - diamond 1000 Euros > > > > > > Job board > > > --------- > > > Non consortium member companies will be able to pay a > fee (1000 Euros) to post job offers to the job board. > > > > > > End of Pharo Consortium Description > > > > > > > > > ===================== > > > *** Support and Answer needed*** > > > ===================== > > > > > > To be able to pay an engineer by the consortium, INRIA needs to make > projection, build budget, pay attention to visa > > > and other important administrative tasks. To deal with the risk that > the consortium may not collect enough to pay a full salary > > > we are considering to ask INRIA to help us financially. To do so we > have to give some concrete figures to > > > INRIA and motivate our request. In addition, our team (RMOD) on its > own budget will try to compensate by allocating extra resources > > > However, this will be only a one shot. In addition, some of our team > members have been approached by google to work on chrome and dart > > > Virtual Machines. So if we really get a future we should build it now. > > > > > > Many of you told us that they want to support the consortium, now we > need to know what would be amount of membership, sponsoring > > > you could give. So please read carefully this mail and send us a mail > at stephane.ducasse(a)inria.fr with the same subject than this one. > > > We will collect the information and build a case to present to INRIA. > > > Thanks in advance for Pharo and for the future that we are building > together. > > > > > > The RMOD team and the Pharo board > > > > > > > > _______________________________________________ > > Esug-list mailing list > > Esug-list(a)lists.esug.org > > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > >

June 28, 2012

Re: [Esug-list] [Pharo-users] **IMPORTANT** MUST READ: Pharo Association and Consortium

by Stéphane Ducasse

Hi laurent > how do we subscribe to the consortium ? for now only company, institution, research group, labs, ... (non individual people) can be member of the consortium because of administrative details. INRIA lawyers are checking what can be done. We decided to make it simpler so that we can move on. The idea is that if we want to avoid that a guy like igor got hired by google :( we should make sure that we get some money for the consortium. Now to hire somebody we have to plan in advance. Now you can be an Pharo association member. In the future, if (I really hope) the consortium can sustain itself, it will leave INRIA and be managed by the association and in that case individual pharo members will be member of the consortium with the same status as individual will get (because we cannot really give the same to somebody paying 40 euros and a company paying 1000/2000 Euros). After since the consortium can offer payed engineer hours, everything is possible. Esteban is working on the association web site right now. We are filling up all the papers to get a bank account for the association. Does it answer your question? Stef > > Laurent Laffont > > On Thu, Jun 28, 2012 at 7:38 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > I can open a wiki page to maintain the list of consortium member I received. > Let me know if it makes sense to you. > > Stef > > On Jun 28, 2012, at 2:19 PM, Stéphane Ducasse wrote: > > > Dear Pharoers and Smalltalkers > > > > This mail is really important so read it carefully. Especially the last part of the mail is important for the > > immediate future: we need your support and input. Read section ***Support*** at the end of this mail. > > > > Context > > ======= > > After taking into account feedback from companies and pharo users in different occasions and > > discussing with the INRIA lawyers and the team in charge of the administrative aspect of the consoritum > > here is the setup we finally want for the consortium. We will have two separated entities: > > - one french law 1901 association for individuals and > > - one consortium for institutions (companies, research groups, laboratories, universities...) managed by INRIA > > > > We hope that in the long run the consortium will be fully managed by the association > > but in the current bootstrap phase INRIA is a good solution. > > > > ============== > > The Pharo Association > > ============== > > The goal of the association is to promote Pharo. It will have its own web site. > > > > Individual Memberships (managed by the Pharo Association) > > ---------------------- > > There are two individual memberships > > - Individual Pharo Association Member: Yearly fee 40 Euros > > - Golden Individual Pharo Association Member: Yearly fee 99 Euros > > > > You will get > > a nice goody, > > reduction access to conferences, > > reduction for training and access to teaching material, > > be part of the pharo groups on social networks, > > be part of the pharoAssociation-individual-members mailing-list, > > get access and registered to the pharo association web site. > > > > Others (managed by the Pharo Association) > > ---------------------- > > The association will be able to issues bills so you will be able to buy a Pharo distribution > > when your organization cannot be a member, a sponsor or doing a donation to the Pharo consortium. > > > > End of Pharo Association Description > > > > > > > > =========================== > > The Pharo Consortium (managed by INRIA) > > =========================== > > The goal of the consortium is to structure and build an umbrella to foster business around Pharo and to promote Pharo. > > > > A company, user group, research group, team or institution can be a consortium member, not individual member. > > > > There are three levels of fees and corresponding benefits. You decide your degree of support. > > The annual fees are > > - Bronze 1000 Euros > > - Silver 2000 Euros > > - Gold 4000 Euros > > > > Consortium members main advantages are > > ---------------------------------------- > > Non individual members of the consortium get the following advantages: > > > > - privileged access to the core development team via a specific mailing-list > > pharo-core-team-for-members(a)lists.gforge.inria.fr > > > > - influence priorities of the next development. The member will be able to propose > > agenda points and items for the executive team. They will be requested one month in > > advance before the committee meeting. > > > > - get access to privileged core engineer time (to address pharo core problems) > > > > - Bronze member gets > > one day of engineering time > > + is automatically a diamond sponsor. > > > > - Silver > > + two days of engineering time > > + one job description for job dashboard > > + is automatically a diamond sponsor.. > > > > - Gold four > > + 4 days of engineering time > > + multiple job description for job dashboard > > + is automatically a diamond sponsor. > > > > - Training special prices and possibility to become pharo trainer > > - Pharo consortium member can also ask and pay for extra support days at INRIA engineer prices (around 600 Euros) per day. > > - Member can offer to their client access to the possibility to pay for extra support days at INRIA engineer prices (around 600 Euros) per day. > > - The core team can provide contact with experts for certain areas of development. > > > > Pharo Consortium Gouvernance: steering committee > > ---------------------------------------- > > The consortium will be managed as follows: There will be a steering committee and an Executive Team. > > > > * A steering committee is composed of one representative of each member (except individuals). > > > > * The chairman of this committee will be Inria > > > > * Steering Committee Role : > > - The Steering Committee follows the execution of the PHARO R&D Team > > - It validates and gives input about the task list of the Executive Team. > > - It can propose members of the executive team. > > - It prepares, organizes conferences, seminars or other animations to promote PHARO and have new members > > - It revises the annual fee > > * Decisions taking: after consultation and collect of representative member points of views, Inria takes the final decision. > > > > * The steering committee will communicate via a private mailing-list. It may meet physical once a year. > > > > * An agenda to reach conclusion will be established by Inria on proposals of the members (the members will be queried a month in advance). > > > > Technical Executive Committee (akaR&D task) > > ---------------------------------------- > > * The Executive Team is composed of members proposed by the steering board and RMOD Team > > * Its roles is to > > * Study, analyze and validate external contributions for PHARO > > * Report to the steering committee > > * Present a task list to the steering committee. > > * Propose, schedule and implement tasks in conformance with the tasks list. > > * Coordinate the release Pharo and its VMs > > > > Pharo consortium Sponsoring > > --------------------------- > > Orthogonally to memberships, an entity can be a sponsor of the consortium without being a pharo consortium member. > > Pharo consortium are de factor platinium sponsor. Sponsors will get their logos name exposed to the consortium web site. > > There are two kinds of sponsors: > > - normal 500 Euros > > - diamond 1000 Euros > > > > Job board > > --------- > > Non consortium member companies will be able to pay a fee (1000 Euros) to post job offers to the job board. > > > > End of Pharo Consortium Description > > > > > > ===================== > > *** Support and Answer needed*** > > ===================== > > > > To be able to pay an engineer by the consortium, INRIA needs to make projection, build budget, pay attention to visa > > and other important administrative tasks. To deal with the risk that the consortium may not collect enough to pay a full salary > > we are considering to ask INRIA to help us financially. To do so we have to give some concrete figures to > > INRIA and motivate our request. In addition, our team (RMOD) on its own budget will try to compensate by allocating extra resources > > However, this will be only a one shot. In addition, some of our team members have been approached by google to work on chrome and dart > > Virtual Machines. So if we really get a future we should build it now. > > > > Many of you told us that they want to support the consortium, now we need to know what would be amount of membership, sponsoring > > you could give. So please read carefully this mail and send us a mail at stephane.ducasse(a)inria.fr with the same subject than this one. > > We will collect the information and build a case to present to INRIA. > > Thanks in advance for Pharo and for the future that we are building together. > > > > The RMOD team and the Pharo board > > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

June 28, 2012

Re: [Esug-list] [Pharo-users] **IMPORTANT** MUST READ: Pharo Association and Consortium

by laurent laffont

Hi Stef, how do we subscribe to the consortium ? Laurent Laffont On Thu, Jun 28, 2012 at 7:38 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > I can open a wiki page to maintain the list of consortium member I > received. > Let me know if it makes sense to you. > > Stef > > On Jun 28, 2012, at 2:19 PM, Stéphane Ducasse wrote: > > > Dear Pharoers and Smalltalkers > > > > This mail is really important so read it carefully. Especially the last > part of the mail is important for the > > immediate future: we need your support and input. Read section > ***Support*** at the end of this mail. > > > > Context > > ======= > > After taking into account feedback from companies and pharo users in > different occasions and > > discussing with the INRIA lawyers and the team in charge of the > administrative aspect of the consoritum > > here is the setup we finally want for the consortium. We will have two > separated entities: > > - one french law 1901 association for individuals and > > - one consortium for institutions (companies, research groups, > laboratories, universities...) managed by INRIA > > > > We hope that in the long run the consortium will be fully managed by the > association > > but in the current bootstrap phase INRIA is a good solution. > > > > ============== > > The Pharo Association > > ============== > > The goal of the association is to promote Pharo. It will have its own > web site. > > > > Individual Memberships (managed by the Pharo Association) > > ---------------------- > > There are two individual memberships > > - Individual Pharo Association Member: Yearly fee 40 Euros > > - Golden Individual Pharo Association Member: Yearly fee > 99 Euros > > > > You will get > > a nice goody, > > reduction access to conferences, > > reduction for training and access to teaching material, > > be part of the pharo groups on social networks, > > be part of the pharoAssociation-individual-members > mailing-list, > > get access and registered to the pharo association web > site. > > > > Others (managed by the Pharo Association) > > ---------------------- > > The association will be able to issues bills so you will be able > to buy a Pharo distribution > > when your organization cannot be a member, a sponsor or doing a > donation to the Pharo consortium. > > > > End of Pharo Association Description > > > > > > > > =========================== > > The Pharo Consortium (managed by INRIA) > > =========================== > > The goal of the consortium is to structure and build an umbrella to > foster business around Pharo and to promote Pharo. > > > > A company, user group, research group, team or institution can be a > consortium member, not individual member. > > > > There are three levels of fees and corresponding benefits. You decide > your degree of support. > > The annual fees are > > - Bronze 1000 Euros > > - Silver 2000 Euros > > - Gold 4000 Euros > > > > Consortium members main advantages are > > ---------------------------------------- > > Non individual members of the consortium get the following > advantages: > > > > - privileged access to the core development team via a > specific mailing-list > > pharo-core-team-for-members(a)lists.gforge.inria.fr > > > > - influence priorities of the next development. The member > will be able to propose > > agenda points and items for the executive team. They will > be requested one month in > > advance before the committee meeting. > > > > - get access to privileged core engineer time (to address > pharo core problems) > > > > - Bronze member gets > > one day of engineering time > > + is automatically a diamond > sponsor. > > > > - Silver > > + two days of engineering time > > + one job description for job > dashboard > > + is automatically a diamond > sponsor.. > > > > - Gold four > > + 4 days of engineering time > > + multiple job description for job > dashboard > > + is automatically a diamond > sponsor. > > > > - Training special prices and possibility to become pharo > trainer > > - Pharo consortium member can also ask and pay for extra > support days at INRIA engineer prices (around 600 Euros) per day. > > - Member can offer to their client access to the > possibility to pay for extra support days at INRIA engineer prices (around > 600 Euros) per day. > > - The core team can provide contact with experts for > certain areas of development. > > > > Pharo Consortium Gouvernance: steering committee > > ---------------------------------------- > > The consortium will be managed as follows: There will be a > steering committee and an Executive Team. > > > > * A steering committee is composed of one representative > of each member (except individuals). > > > > * The chairman of this committee will be Inria > > > > * Steering Committee Role : > > - The Steering Committee follows the execution of > the PHARO R&D Team > > - It validates and gives input about the task list > of the Executive Team. > > - It can propose members of the executive team. > > - It prepares, organizes conferences, seminars or > other animations to promote PHARO and have new members > > - It revises the annual fee > > * Decisions taking: after consultation and collect of > representative member points of views, Inria takes the final decision. > > > > * The steering committee will communicate via a private > mailing-list. It may meet physical once a year. > > > > * An agenda to reach conclusion will be established by > Inria on proposals of the members (the members will be queried a month in > advance). > > > > Technical Executive Committee (akaR&D task) > > ---------------------------------------- > > * The Executive Team is composed of members proposed by > the steering board and RMOD Team > > * Its roles is to > > * Study, analyze and validate external > contributions for PHARO > > * Report to the steering committee > > * Present a task list to the steering committee. > > * Propose, schedule and implement tasks in > conformance with the tasks list. > > * Coordinate the release Pharo and its VMs > > > > Pharo consortium Sponsoring > > --------------------------- > > Orthogonally to memberships, an entity can be a sponsor of > the consortium without being a pharo consortium member. > > Pharo consortium are de factor platinium sponsor. Sponsors > will get their logos name exposed to the consortium web site. > > There are two kinds of sponsors: > > - normal 500 Euros > > - diamond 1000 Euros > > > > Job board > > --------- > > Non consortium member companies will be able to pay a fee > (1000 Euros) to post job offers to the job board. > > > > End of Pharo Consortium Description > > > > > > ===================== > > *** Support and Answer needed*** > > ===================== > > > > To be able to pay an engineer by the consortium, INRIA needs to make > projection, build budget, pay attention to visa > > and other important administrative tasks. To deal with the risk that the > consortium may not collect enough to pay a full salary > > we are considering to ask INRIA to help us financially. To do so we have > to give some concrete figures to > > INRIA and motivate our request. In addition, our team (RMOD) on its own > budget will try to compensate by allocating extra resources > > However, this will be only a one shot. In addition, some of our team > members have been approached by google to work on chrome and dart > > Virtual Machines. So if we really get a future we should build it now. > > > > Many of you told us that they want to support the consortium, now we > need to know what would be amount of membership, sponsoring > > you could give. So please read carefully this mail and send us a mail at > stephane.ducasse(a)inria.fr with the same subject than this one. > > We will collect the information and build a case to present to INRIA. > > Thanks in advance for Pharo and for the future that we are building > together. > > > > The RMOD team and the Pharo board > > >

June 28, 2012

looking for a Smalltalker

by Nowak, Helge

Dear all, I am looking for one of our German customers for Smalltalkers in permanent position. Please send me your profile and contact data. NO freelancers and remote workers please! Please forward this message to anybody interested. TIA Helge ************************************************************** Helge Nowak Technical Account Manager Cincom Smalltalk Cincom Systems GmbH & Co. oHG Am Kronberger Hang 4 D-65824 Schwalbach/Ts. Tel.: +49-(0)89-89664494 Mobil: +49-(0)172-7400402 Fax: +49-(0)89-89664495 Email: mailto:hnowak@cincom.com <mailto:hnowak@cincom.com> Twitter: @nowagil Web: http://www.cincom.com <http://www.cincom.com/> All about Cincom Smalltalk: http://www.cincomsmalltalk.com <http://www.cincomsmalltalk.com/> Vorträge und Workshops zu Real-Time Collaboration: GI Karlsruhe (4.7. und 11.7.) http://rg-karlsruhe.gi.de/veranstaltungen/2012.html <http://rg-karlsruhe.gi.de/veranstaltungen/2012.html> Agile World München (12.7.) http://agileworld.de/ <http://agileworld.de/> A standpoint is an intellectual horizon of radius zero. -- Albert Einstein Geschäftsführer/Managing Directors: Thomas M. Nies, Gerald L. Shawhan oHG mit Sitz/based in Schwalbach/Ts. (Amtsgericht Königstein/Ts. HRA 2653) Pers. haftender Gesellschafter/Partner liable to unlimited extent: Cincom Systems Verwaltungsgesellschaft mbH (Amtsgericht Königstein/Ts. HRB 5069) **************************************************************

June 28, 2012

**IMPORTANT** MUST READ: Pharo Association and Consortium

by Stéphane Ducasse

Dear Pharoers and Smalltalkers This mail is really important so read it carefully. Especially the last part of the mail is important for the immediate future: we need your support and input. Read section ***Support*** at the end of this mail. Context ======= After taking into account feedback from companies and pharo users in different occasions and discussing with the INRIA lawyers and the team in charge of the administrative aspect of the consoritum here is the setup we finally want for the consortium. We will have two separated entities: - one french law 1901 association for individuals and - one consortium for institutions (companies, research groups, laboratories, universities...) managed by INRIA We hope that in the long run the consortium will be fully managed by the association but in the current bootstrap phase INRIA is a good solution. ============== The Pharo Association ============== The goal of the association is to promote Pharo. It will have its own web site. Individual Memberships (managed by the Pharo Association) ---------------------- There are two individual memberships - Individual Pharo Association Member: Yearly fee 40 Euros - Golden Individual Pharo Association Member: Yearly fee 99 Euros You will get a nice goody, reduction access to conferences, reduction for training and access to teaching material, be part of the pharo groups on social networks, be part of the pharoAssociation-individual-members mailing-list, get access and registered to the pharo association web site. Others (managed by the Pharo Association) ---------------------- The association will be able to issues bills so you will be able to buy a Pharo distribution when your organization cannot be a member, a sponsor or doing a donation to the Pharo consortium. End of Pharo Association Description =========================== The Pharo Consortium (managed by INRIA) =========================== The goal of the consortium is to structure and build an umbrella to foster business around Pharo and to promote Pharo. A company, user group, research group, team or institution can be a consortium member, not individual member. There are three levels of fees and corresponding benefits. You decide your degree of support. The annual fees are - Bronze 1000 Euros - Silver 2000 Euros - Gold 4000 Euros Consortium members main advantages are ---------------------------------------- Non individual members of the consortium get the following advantages: - privileged access to the core development team via a specific mailing-list pharo-core-team-for-members(a)lists.gforge.inria.fr - influence priorities of the next development. The member will be able to propose agenda points and items for the executive team. They will be requested one month in advance before the committee meeting. - get access to privileged core engineer time (to address pharo core problems) - Bronze member gets one day of engineering time + is automatically a diamond sponsor. - Silver + two days of engineering time + one job description for job dashboard + is automatically a diamond sponsor.. - Gold four + 4 days of engineering time + multiple job description for job dashboard + is automatically a diamond sponsor. - Training special prices and possibility to become pharo trainer - Pharo consortium member can also ask and pay for extra support days at INRIA engineer prices (around 600 Euros) per day. - Member can offer to their client access to the possibility to pay for extra support days at INRIA engineer prices (around 600 Euros) per day. - The core team can provide contact with experts for certain areas of development. Pharo Consortium Gouvernance: steering committee ---------------------------------------- The consortium will be managed as follows: There will be a steering committee and an Executive Team. * A steering committee is composed of one representative of each member (except individuals). * The chairman of this committee will be Inria * Steering Committee Role : - The Steering Committee follows the execution of the PHARO R&D Team - It validates and gives input about the task list of the Executive Team. - It can propose members of the executive team. - It prepares, organizes conferences, seminars or other animations to promote PHARO and have new members - It revises the annual fee * Decisions taking: after consultation and collect of representative member points of views, Inria takes the final decision. * The steering committee will communicate via a private mailing-list. It may meet physical once a year. * An agenda to reach conclusion will be established by Inria on proposals of the members (the members will be queried a month in advance). Technical Executive Committee (akaR&D task) ---------------------------------------- * The Executive Team is composed of members proposed by the steering board and RMOD Team * Its roles is to * Study, analyze and validate external contributions for PHARO * Report to the steering committee * Present a task list to the steering committee. * Propose, schedule and implement tasks in conformance with the tasks list. * Coordinate the release Pharo and its VMs Pharo consortium Sponsoring --------------------------- Orthogonally to memberships, an entity can be a sponsor of the consortium without being a pharo consortium member. Pharo consortium are de factor platinium sponsor. Sponsors will get their logos name exposed to the consortium web site. There are two kinds of sponsors: - normal 500 Euros - diamond 1000 Euros Job board --------- Non consortium member companies will be able to pay a fee (1000 Euros) to post job offers to the job board. End of Pharo Consortium Description ===================== *** Support and Answer needed*** ===================== To be able to pay an engineer by the consortium, INRIA needs to make projection, build budget, pay attention to visa and other important administrative tasks. To deal with the risk that the consortium may not collect enough to pay a full salary we are considering to ask INRIA to help us financially. To do so we have to give some concrete figures to INRIA and motivate our request. In addition, our team (RMOD) on its own budget will try to compensate by allocating extra resources However, this will be only a one shot. In addition, some of our team members have been approached by google to work on chrome and dart Virtual Machines. So if we really get a future we should build it now. Many of you told us that they want to support the consortium, now we need to know what would be amount of membership, sponsoring you could give. So please read carefully this mail and send us a mail at stephane.ducasse(a)inria.fr with the same subject than this one. We will collect the information and build a case to present to INRIA. Thanks in advance for Pharo and for the future that we are building together. The RMOD team and the Pharo board

June 28, 2012

Re: [Esug-list] Silver Anniversary

by Niall Ross

Dear Georg, thanks for all you've achieved for Smalltalk over the years. Yours with high respect Niall Ross ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________

June 28, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Richard Sargent

I can recall seeing a problem similar to this some years ago in VisualAge Smalltalk. VisualAge Smalltalk uses the ENVY version control system (I think very highly of it!). I was able to determine what the developer had done "wrong", so it is possible that something similar exists with Pharo. Specifically, if one browses the differences between the currently loaded edition and another version, one could have an opportunity to load the alternate edition of the class definition itself through the Differences Browser. I found that this failed to recompile the methods, and resulted in methods referring to wrong the wrong instance variable offsets. I know nothing about Pharo, what version control it has, and what change browsing capabilities it has. So, I cannot say that it is the same problem, just that it is a possibility. Good luck, Richard _____ From: Graham McLeod [mailto:mcleod@iafrica.com] Sent: June-27-12 1:34 AM To: Philippe Marschall Cc: ESUG Mailing list; Andrew P. Black Subject: Re: [Esug-list] Worrying issue re compilation in Pharo 1.4 Thanks all. I have not been able to reproduce the problem. It may have been a unique sequence of actions unlikely to recur. The new strategy sounds good. KR Graham Philippe Marschall wrote: On Tue, Jun 26, 2012 at 7:49 PM, Marcus Denker <mailto:marcus.denker@inria.fr> <marcus.denker(a)inria.fr> wrote: On Jun 26, 2012, at 7:04 PM, Andrew P. Black wrote: On 25 Jun 2012, at 08:50 , Graham McLeod wrote: There still remains the question of how the system allowed the situation to arise in the first place tho.. Indeed: this should never happen. So, if you can reproduce the problem, you should report it as a bug in the 1.4 bug tracker. http://code.google.com/p/pharo/issues/list Yes! As far as I know, there is no bug reported regarding any problems with this... we are, though, completely rewriting this part of the system for 2.0: -> the old system change notifycation mechanism will be replaced with a new system base on Announcements. -> the old class builder will be replaced by one based on the work in the context of first class Slots (see the OOPSLA Paper of Toon and Camillo: http://scg.unibe.ch/scgbib?query=Verw11b <http://scg.unibe.ch/scgbib?query=Verw11b&display=abstract> &display=abstract ) -> instead of recompiling, we will just change the offsets of the iVars on the level of the bytecode intermediate representation of the new pharo compiler. Nice! Cheers Philippe _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

June 27, 2012

German Squeakers meeting July, 7th in Potsdam

by Rita Freudenberg

Dear Squeakers, here comes the invitation for the annual meeting of Squeak Germany e.V. on July, 7th at HPI in Potsdam. http://www.squeak.de/events-squeaktreffen-2012/squeaktreffen-2012 Greetings, Rita ------------------------------------------------------------------------------------------------------------------------------ Liebe Squeaker, auch dieses Jahr laden wir Euch wieder herzliche zum Squeak-Treffen mit Vorträgen und zur Mitgliederversammlung ein Wo? Dank Robert Hirschfeld und seinem Team wieder am Hasso Plattner Institut bei der Software-Architektur Gruppe in Potsdam. Den Raum geben wir noch bekannt. Anfahrt: http://www.hpi.uni-potsdam.de/hpi/campus/anfahrt.html S a m s t a g, 07.07.2012 Vorträge (Beginn 13:00 Uhr) Themen sind gern gesehen bzw. in Planung. Wenn Ihr Ideen habt, bitte melden! Bitte meldet Euch rechtzeitig! Vereinsversammlung (17:00 Uhr - 18:00 Uhr) - Bestimmung des Protokollführers und der Kassenprüfer - Feststellung der Beschlussfähigkeit - Vorstellung / Änderung der Tagesordnung - Aktivitäten des Vereins 2011-2012 - Bericht des Schatzmeisters und der Kassenprüfer - Künftige Aktivitäten - Sonstiges Wer noch Ideen für Tagesordnungspunkte hat, bitte satzungsgemäß innerhalb von zwei Wochen melden. Anschließend Ausklang in gemütlicher Runde in Potsdam. Bitte antwortet an uns oder an die Liste, wenn Ihr kommen könnt, so dass wir ein wenig planen können, vor allem wegen des abendlichen Treffens! Wir hoffen Euch wieder zahlreich in Potsdam treffen zu können. Viele Grüße Enno, Esther und Rita Rita Freudenberg rita.freudenberg(a)ovgu.de

June 27, 2012

Re: [Esug-list] Silver Anniversary

by giorgio ferraris

Hi, Georg, happy anniversary and best wishes for a brilliant future. ciao Giorgio On Wed, Jun 27, 2012 at 2:36 PM, Georg Heeg <georg(a)heeg.de> wrote: > Dear Smalltalkers, > > 7/7/1987 I founded my company, thus we will celebrate our silver > anniversary 7/7/2012. > > Hereby I invite you and your friends and colleagues to celebrate with us. > > Saturday, 7/7/2012, an open day will take place from 10 am to 4 pm in our > house in Wallstr. 22 in Köthen under the motto "Actually what does the > company Heeg do?". > > We will begin at 10 am with a devotion led by Reverend Armin Kensbock. > This will be followed by welcome addresses: the Mayor of our city Mr. > Kurt-Jürgen Zander, Ms. Brigitte Take, Member of the Landtag, Mr. Minister > (Ret.) Dr. Werner Sobetzko have announced addresses so far. A colorful > programme follows, where anyone can learn, what we have done in the past 25 > years and what the focus of our work has been. > > Who is prevented, for example by the Saxony Anhalt day in Dessau on > Saturday or just wants to party with us on the eve, is invited Friday > evening 6.7.2012 to an informal barbecue. > > Instead of presents, we ask for donations for the restoration of the > Steinway grand piano of Music School Johann Sebastian Bach in Cöthen. > Keyboard buttons can be purchased symbolically where the price is depending > on the pitch from 55 € to 150 € (the a1 (440 Hz) is already sold to the > string wind Orchestra and today the money transfer will take place). We ask > that payments to the account of the Association of friends of the school of > music at the Kreissparkasse Anhalt-Bitterfeld, bank code 80053722, account > number 310000807. We'll have also a violin case. > > We ask you a short feedback, with how many people you plan to come. > > Georg > > Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812 Wallstraße 22, > 06366 Köthen Tel. +49-3496-214328, Fax +49-3496-214712 > > > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >

June 27, 2012

Re: [Esug-list] Silver Anniversary

by Janko Mivšek

Happy anniversary Georg and many many more fruitful Smalltalk years ahead! Janko On 27. 06. 2012 14:36, Georg Heeg wrote: > Dear Smalltalkers, > > 7/7/1987 I founded my company, thus we will celebrate our silver anniversary 7/7/2012. > > Hereby I invite you and your friends and colleagues to celebrate with us. > > Saturday, 7/7/2012, an open day will take place from 10 am to 4 pm in our house in Wallstr. 22 in Köthen under the motto "Actually what does the company Heeg do?". > > We will begin at 10 am with a devotion led by Reverend Armin Kensbock. This will be followed by welcome addresses: the Mayor of our city Mr. Kurt-Jürgen Zander, Ms. Brigitte Take, Member of the Landtag, Mr. Minister (Ret.) Dr. Werner Sobetzko have announced addresses so far. A colorful programme follows, where anyone can learn, what we have done in the past 25 years and what the focus of our work has been. > > Who is prevented, for example by the Saxony Anhalt day in Dessau on Saturday or just wants to party with us on the eve, is invited Friday evening 6.7.2012 to an informal barbecue. > > Instead of presents, we ask for donations for the restoration of the Steinway grand piano of Music School Johann Sebastian Bach in Cöthen. Keyboard buttons can be purchased symbolically where the price is depending on the pitch from 55 € to 150 € (the a1 (440 Hz) is already sold to the string wind Orchestra and today the money transfer will take place). We ask that payments to the account of the Association of friends of the school of music at the Kreissparkasse Anhalt-Bitterfeld, bank code 80053722, account number 310000807. We'll have also a violin case. > > We ask you a short feedback, with how many people you plan to come. > > Georg > > Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812 Wallstraße 22, 06366 Köthen Tel. +49-3496-214328, Fax +49-3496-214712 > > > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

June 27, 2012

Re: [Esug-list] Silver Anniversary

by Bert Freudenberg

Congratulations on your anniversary! Unfortunately, on 7/7 there is the annual German Squeak get-together at HPI in Potsdam. But maybe I can drop by for the barbecue. Sounds like a bit more fun, too ;) - Bert - On 27.06.2012, at 14:36, Georg Heeg wrote: > Dear Smalltalkers, > > 7/7/1987 I founded my company, thus we will celebrate our silver anniversary 7/7/2012. > > Hereby I invite you and your friends and colleagues to celebrate with us. > > Saturday, 7/7/2012, an open day will take place from 10 am to 4 pm in our house in Wallstr. 22 in Köthen under the motto "Actually what does the company Heeg do?". > > We will begin at 10 am with a devotion led by Reverend Armin Kensbock. This will be followed by welcome addresses: the Mayor of our city Mr. Kurt-Jürgen Zander, Ms. Brigitte Take, Member of the Landtag, Mr. Minister (Ret.) Dr. Werner Sobetzko have announced addresses so far. A colorful programme follows, where anyone can learn, what we have done in the past 25 years and what the focus of our work has been. > > Who is prevented, for example by the Saxony Anhalt day in Dessau on Saturday or just wants to party with us on the eve, is invited Friday evening 6.7.2012 to an informal barbecue. > > Instead of presents, we ask for donations for the restoration of the Steinway grand piano of Music School Johann Sebastian Bach in Cöthen. Keyboard buttons can be purchased symbolically where the price is depending on the pitch from 55 € to 150 € (the a1 (440 Hz) is already sold to the string wind Orchestra and today the money transfer will take place). We ask that payments to the account of the Association of friends of the school of music at the Kreissparkasse Anhalt-Bitterfeld, bank code 80053722, account number 310000807. We'll have also a violin case. > > We ask you a short feedback, with how many people you plan to come. > > Georg > > Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812 Wallstraße 22, 06366 Köthen Tel. +49-3496-214328, Fax +49-3496-214712 > > > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

June 27, 2012

Silver Anniversary

by Georg Heeg

Dear Smalltalkers, 7/7/1987 I founded my company, thus we will celebrate our silver anniversary 7/7/2012. Hereby I invite you and your friends and colleagues to celebrate with us. Saturday, 7/7/2012, an open day will take place from 10 am to 4 pm in our house in Wallstr. 22 in Köthen under the motto "Actually what does the company Heeg do?". We will begin at 10 am with a devotion led by Reverend Armin Kensbock. This will be followed by welcome addresses: the Mayor of our city Mr. Kurt-Jürgen Zander, Ms. Brigitte Take, Member of the Landtag, Mr. Minister (Ret.) Dr. Werner Sobetzko have announced addresses so far. A colorful programme follows, where anyone can learn, what we have done in the past 25 years and what the focus of our work has been. Who is prevented, for example by the Saxony Anhalt day in Dessau on Saturday or just wants to party with us on the eve, is invited Friday evening 6.7.2012 to an informal barbecue. Instead of presents, we ask for donations for the restoration of the Steinway grand piano of Music School Johann Sebastian Bach in Cöthen. Keyboard buttons can be purchased symbolically where the price is depending on the pitch from 55 € to 150 € (the a1 (440 Hz) is already sold to the string wind Orchestra and today the money transfer will take place). We ask that payments to the account of the Association of friends of the school of music at the Kreissparkasse Anhalt-Bitterfeld, bank code 80053722, account number 310000807. We'll have also a violin case. We ask you a short feedback, with how many people you plan to come. Georg Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812 Wallstraße 22, 06366 Köthen Tel. +49-3496-214328, Fax +49-3496-214712

June 27, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Graham McLeod

Thanks all. I have not been able to reproduce the problem. It may have been a unique sequence of actions unlikely to recur. The new strategy sounds good. KR Graham Philippe Marschall wrote: > On Tue, Jun 26, 2012 at 7:49 PM, Marcus Denker<marcus.denker(a)inria.fr> wrote: >> On Jun 26, 2012, at 7:04 PM, Andrew P. Black wrote: >> >>> On 25 Jun 2012, at 08:50 , Graham McLeod wrote: >>> >>>> There still remains the question of how the system allowed the situation to arise in the first place tho.. >>> Indeed: this should never happen. So, if you can reproduce the problem, you should report it as a bug in the 1.4 bug tracker. >>> >>> http://code.google.com/p/pharo/issues/list >>> >> Yes! As far as I know, there is no bug reported regarding any problems with this... we are, though, completely rewriting this >> part of the system for 2.0: >> -> the old system change notifycation mechanism will be replaced with a new system base on Announcements. >> -> the old class builder will be replaced by one based on the work in the context of first class Slots >> (see the OOPSLA Paper of Toon and Camillo: http://scg.unibe.ch/scgbib?query=Verw11b&display=abstract ) >> -> instead of recompiling, we will just change the offsets of the iVars on the level of the bytecode intermediate representation >> of the new pharo compiler. > > Nice! > > Cheers > Philippe > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

June 26, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Philippe Marschall

On Tue, Jun 26, 2012 at 7:49 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 26, 2012, at 7:04 PM, Andrew P. Black wrote: > >> >> On 25 Jun 2012, at 08:50 , Graham McLeod wrote: >> >>> There still remains the question of how the system allowed the situation to arise in the first place tho.. >> >> Indeed: this should never happen. So, if you can reproduce the problem, you should report it as a bug in the 1.4 bug tracker. >> >> http://code.google.com/p/pharo/issues/list >> > Yes! As far as I know, there is no bug reported regarding any problems with this... we are, though, completely rewriting this > part of the system for 2.0: > -> the old system change notifycation mechanism will be replaced with a new system base on Announcements. > -> the old class builder will be replaced by one based on the work in the context of first class Slots > (see the OOPSLA Paper of Toon and Camillo: http://scg.unibe.ch/scgbib?query=Verw11b&display=abstract ) > -> instead of recompiling, we will just change the offsets of the iVars on the level of the bytecode intermediate representation > of the new pharo compiler. Nice! Cheers Philippe

June 26, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Marcus Denker

On Jun 26, 2012, at 7:04 PM, Andrew P. Black wrote: > > On 25 Jun 2012, at 08:50 , Graham McLeod wrote: > >> There still remains the question of how the system allowed the situation to arise in the first place tho.. > > Indeed: this should never happen. So, if you can reproduce the problem, you should report it as a bug in the 1.4 bug tracker. > > http://code.google.com/p/pharo/issues/list > Yes! As far as I know, there is no bug reported regarding any problems with this... we are, though, completely rewriting this part of the system for 2.0: -> the old system change notifycation mechanism will be replaced with a new system base on Announcements. -> the old class builder will be replaced by one based on the work in the context of first class Slots (see the OOPSLA Paper of Toon and Camillo: http://scg.unibe.ch/scgbib?query=Verw11b&display=abstract ) -> instead of recompiling, we will just change the offsets of the iVars on the level of the bytecode intermediate representation of the new pharo compiler. This is not yet in 2.0... but we are woking on it. Marcus -- Marcus Denker -- http://marcusdenker.de

June 26, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Andrew P. Black

On 25 Jun 2012, at 08:50 , Graham McLeod wrote: > There still remains the question of how the system allowed the situation to arise in the first place tho.. Indeed: this should never happen. So, if you can reproduce the problem, you should report it as a bug in the 1.4 bug tracker. http://code.google.com/p/pharo/issues/list Andrew

June 26, 2012

IWST 2012 Best Papers special issue

by Loïc Lagadec

Dear smalltalkers, We are pround to announce that the authors of the best accepted papers of IWST 2012, will also be invited to submit extended versions of their papers for publication in a special issue of Elsevier "Science of Computer Programming : Methods of Software Design: Techniques and Applications" (Impact factor 1.82) IWST 2012 web page: http://www.esug.org/wiki/pier/Conferences/2012/International-Workshop---IWS… Best regards, Program Co-chairs Loïc Lagadec, Alain Plantec Lab-STICC, Université de Bretagne Occidentale

June 26, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Graham McLeod

Hi Marcus, Your answer is as I suspected. The suggestion to add an instance variable, forcing a recompile, from Andrew P Black, seems to resolve the problem.. There still remains the question of how the system allowed the situation to arise in the first place tho.. Thanks for the help. KR Graham Marcus Denker wrote: > On Jun 25, 2012, at 1:22 AM, Graham McLeod wrote: >> Here is an example: >> >> Class definition: >> Thing subclass: #Relationship >> instanceVariableNames: 'context fromNode properties relType toNode' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Sapiento' >> >> Source Code: >> relType: anObject >> relType := anObject >> Byte Codes: >> 13<10> pushTemp: 0 >> 14<62> popIntoRcvr: 2 >> 15<78> returnSelf >> Decompiled Code: >> relType: anObject >> properties := anObject >> >> NOTE: properties is updated instead of relType. >> > > It seems that the method has not been recompiled correctly when you added instance variables. > > The decompiled code and the bytecode are in sync: 14<62> popIntoRcvr: 2 is storing into > the properties instance variable, and the decompiled code shows it correctly. > But the bytecode should have been regenerated and do 14<62> popIntoRcvr: 3 > > So the bug is definitly related to not recompiling the methods after the shape of the class was changed. > > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > >

June 25, 2012

Re: [Esug-list] Worrying issue re compilation in Pharo 1.4

by Marcus Denker

On Jun 25, 2012, at 1:22 AM, Graham McLeod wrote: > > Here is an example: > > Class definition: > Thing subclass: #Relationship > instanceVariableNames: 'context fromNode properties relType toNode' > classVariableNames: '' > poolDictionaries: '' > category: 'Sapiento' > > Source Code: > relType: anObject > relType := anObject > Byte Codes: > 13 <10> pushTemp: 0 > 14 <62> popIntoRcvr: 2 > 15 <78> returnSelf > Decompiled Code: > relType: anObject > properties := anObject > > NOTE: properties is updated instead of relType. > It seems that the method has not been recompiled correctly when you added instance variables. The decompiled code and the bytecode are in sync: 14 <62> popIntoRcvr: 2 is storing into the properties instance variable, and the decompiled code shows it correctly. But the bytecode should have been regenerated and do 14 <62> popIntoRcvr: 3 So the bug is definitly related to not recompiling the methods after the shape of the class was changed. Marcus -- Marcus Denker -- http://marcusdenker.de

June 25, 2012

Worrying issue re compilation in Pharo 1.4

by Graham McLeod

Hi Guys I am trying to use Pharo1.4 Latest update: #14438 as downloaded in the Moose 4.7 image. I am loving most of the changes and system tools - well done all! But I am coming up with a worrying bug where there is a difference between Source code and decompiled source code. Specifically, this occurs with two set methods which point to the wrong instance variable slot. So, when the code runs, the wrong variables are updated. Here is an example: Class definition: Thing subclass: #Relationship instanceVariableNames: 'context fromNode properties relType toNode' classVariableNames: '' poolDictionaries: '' category: 'Sapiento' Source Code: relType: anObject relType := anObject Byte Codes: 13 <10> pushTemp: 0 14 <62> popIntoRcvr: 2 15 <78> returnSelf Decompiled Code: relType: anObject properties := anObject NOTE: properties is updated instead of relType. I may have added a new instance variable since the original class definition. Are there known issues / available fixes around this? Please advise Thanks in advance. Graham

June 24, 2012

REMINDER: early registration deadline for ESUG is next Saturday (June 30th)

by Johan Brichau

Dear Smalltalkers, The early registration deadline for this year's ESUG conference in Gent, Belgium, is next Saturday (June 30th). Please register for the conference on http://registration.esug.org ! If you have not booked your accomodation yet, please do so before June 30th (all our options at the various hotels expire at that date). Do not hesitate to contact me for further inquiries. Hope to see you in Gent! Johan Brichau

June 23, 2012