- Pharo-dev - lists.pharo.org

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

by stephane ducasse

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

[Pharo-project] [update 2.0] #20171

by Marcus Denker

20171 ----- Issue 6199: ListDialogWindow http://code.google.com/p/pharo/issues/detail?id=6199 Issue 6198: Extension missing http://code.google.com/p/pharo/issues/detail?id=6198 Issue 6117: SimplifiedChineseEnvironment should implement leadingChar http://code.google.com/p/pharo/issues/detail?id=6117 -- Marcus Denker -- http://marcusdenker.de

June 28, 2012

[Pharo-project] [update 2.0] #20170

by Marcus Denker

20170 ----- Issue 6197: Nautilus global shortcuts http://code.google.com/p/pharo/issues/detail?id=6197 Issue 6196: KMDescription fixed http://code.google.com/p/pharo/issues/detail?id=6196 Issue 6195: Change in AbstractTool http://code.google.com/p/pharo/issues/detail?id=6195 Issue 6194: Failing test: #testDialectLocalizedException http://code.google.com/p/pharo/issues/detail?id=6194 Issue 6151: Get rid of "Objects pointing to this value" http://code.google.com/p/pharo/issues/detail?id=6151 -- Marcus Denker -- http://marcusdenker.de

June 28, 2012

[Pharo-project] [update 2.0] #20169

by Marcus Denker

20169 ----- Issue 6132: Memory FileSystem should support ModificationTime and CreationTime http://code.google.com/p/pharo/issues/detail?id=6132 -- Marcus Denker -- http://marcusdenker.de

June 28, 2012

Re: [Pharo-project] NBCog and FileSystem

by Igor Stasenko

On 28 June 2012 15:00, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi Igor, > > I tried to create a next bootable Pharo image based on TinyCore, this > time not dependent on framebuffer but with full XOrg (the basic distro > is of course bigger, the iso image has 23MB without Pharo). With CogVM > everything works well but I wanted to use NBCog and I had problems > with directory access. I guess it's because the NBCog currently > doesn't contains latests VM patches for the FileSystem support. Can > you confirm that? > Yes, the builds did not updated yet. I want to make an update once we will integrate the changes i did for libraries bundling. What i like is to bundle NBGog VM with cairo and freetype libs by default. > Cheers, > -- Pavel > -- Best regards, Igor Stasenko.

June 28, 2012

[Pharo-project] NBCog and FileSystem

by Pavel Krivanek

Hi Igor, I tried to create a next bootable Pharo image based on TinyCore, this time not dependent on framebuffer but with full XOrg (the basic distro is of course bigger, the iso image has 23MB without Pharo). With CogVM everything works well but I wanted to use NBCog and I had problems with directory access. I guess it's because the NBCog currently doesn't contains latests VM patches for the FileSystem support. Can you confirm that? Cheers, -- Pavel

June 28, 2012

[Pharo-project] **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: [Pharo-project] Let's Get Pharo 1.4 Ready for the Summer Release!

by Sean P. DeNigris

Sean P. DeNigris wrote > > There are half a dozen 1.4 bug fixes in the inbox that need to be > reviewed: > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.4+is%3Aope… > > 4 of them are EASY (mostly one-liners or close): > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.4+is%3Aope… > We're almost halfway there!! 5 fixes have been integrated and 6 remain in the inbox. Who will review one of those left, so we have a rock-solid *release this week*?! Reviewing is simple ( http://forum.world.st/Backporting-fixes-tp4633625p4633680.html per Steph ): - we go to the issue list - try to load the code - read the code - check if there is a test - check that all the tests are working (or that new ones are not broken So any input is important. Cheers, Sean -- View this message in context: http://forum.world.st/Let-s-Get-Pharo-1-4-Ready-for-the-Summer-Release-tp46… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 28, 2012

[Pharo-project] [update 2.0] #20168

by Marcus Denker

20168 ----- Issue 6193: Nautilus fix according to ClassSearch http://code.google.com/p/pharo/issues/detail?id=6193 Issue 6082: Missed translated selector for the dialog title in the ColorChooserMorph http://code.google.com/p/pharo/issues/detail?id=6082 Issue 6153: Nautilus: Can not get menu on apple trackpad http://code.google.com/p/pharo/issues/detail?id=6153 Issue 6180: fix #skipSeparators packaging http://code.google.com/p/pharo/issues/detail?id=6180 Issue 6142: Support pipeing in scripts to the image http://code.google.com/p/pharo/issues/detail?id=6142 -- Marcus Denker -- http://marcusdenker.de

June 28, 2012

Re: [Pharo-project] VM , modules, packages and plugins

by Igor Stasenko

On 28 June 2012 04:03, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > I agree, except for silent updates. Â One should at know what is happening, and further be able to run a "broken" mixture, if only for debugging. > i just mentioned silent updates to demonstrate what current practices are, and where we are comparing to it by throwing errors with no information, leaving users clueless what might be causing it. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua(a)gmail.com] > Sent: Wednesday, June 27, 2012 6:48 PM > To: Pharo Development > Subject: [Pharo-project] VM , modules, packages and plugins > > Seeing another thread about "is XYZ plugin there or not" or "what may > cause prim fail" > i REALLY suggest that we should stop and think.. > This plugin's usage logic is inherently flawed.. (or i would say outdated) > > What i would like to see one day is when i installing new code into > image, it pops up a message: > "Your VM missing an XYZ plugin for running this cool code, would you > like to download and install it? Yes No " > > In case of Pharo, we should really start thinking about delivering > quality grade solutions, not something > which might work if you properly jump 2 times and whistle 7 times > while faced North"... > > Look at what the practices which become common today in modern > browsers, and OSes - they updating themselves without a notice > and just asking you to restart it time to time. Why we cannot do the same? > > -- > Best regards, > Igor Stasenko. > > -- Best regards, Igor Stasenko.

June 28, 2012