- Pharo-dev - lists.pharo.org

Re: [Pharo-project] EvaluateCommandLineHandler changes

by Camillo Bruni

On 2012-06-28, at 22:01, Camillo Bruni wrote: > > On 2012-06-28, at 21:31, Guillermo Polito wrote: > >> Hi Camillo, >> >> the latest introduction of this: >> >> "check if we have an opened stdin" >> FileStream stdin ifNotNilDo:[ :stream| >> stream atEnd ifFalse: [ ^ true ]]. >> >> (I assume for piping?) > > exactly.... > >> Is messing with my other command line args... lets say I have another >> command line argument that runs tests and I do: >> >> Vm image --tests >> >> It tries to open it with the EvaluateCommandLineHandler :S... >> >> Args is: >> >> an OrderedCollection('--test') >> >> And the command line handlers after selecting the responsibles are: >> >> an OrderedCollection(EvaluateCommandLineHandler >> RunTestsCommandLineHandler DefaultCommandLineHandler) >> >> By now I'll try putting my handler a higher priority (1 :P), but, is >> this the expected behavior? > > > > you're right, that's broken (AKA we should add some tests there :P) > > I wanted to write something different there... maybe the filestream test should simply be removed, then piping in commands only works when explicitely specifying the "eval" handler

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 > > 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. > Only two 1.4 bugs left to review. Act fast before they all disappear and you get left out! http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.4+is%3Aope… -- 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

Re: [Pharo-project] EvaluateCommandLineHandler changes

by Camillo Bruni

On 2012-06-28, at 21:31, Guillermo Polito wrote: > Hi Camillo, > > the latest introduction of this: > > "check if we have an opened stdin" > FileStream stdin ifNotNilDo:[ :stream| > stream atEnd ifFalse: [ ^ true ]]. > > (I assume for piping?) exactly.... > Is messing with my other command line args... lets say I have another > command line argument that runs tests and I do: > > Vm image --tests > > It tries to open it with the EvaluateCommandLineHandler :S... > > Args is: > > an OrderedCollection('--test') > > And the command line handlers after selecting the responsibles are: > > an OrderedCollection(EvaluateCommandLineHandler > RunTestsCommandLineHandler DefaultCommandLineHandler) > > By now I'll try putting my handler a higher priority (1 :P), but, is > this the expected behavior? you're right, that's broken (AKA we should add some tests there :P) I wanted to write something different there... (super isResponsibleFor: args)

June 28, 2012

[Pharo-project] EvaluateCommandLineHandler changes

by Guillermo Polito

Hi Camillo, the latest introduction of this: "check if we have an opened stdin" FileStream stdin ifNotNilDo:[ :stream| stream atEnd ifFalse: [ ^ true ]]. (I assume for piping?) Is messing with my other command line args... lets say I have another command line argument that runs tests and I do: Vm image --tests It tries to open it with the EvaluateCommandLineHandler :S... Args is: an OrderedCollection('--test') And the command line handlers after selecting the responsibles are: an OrderedCollection(EvaluateCommandLineHandler RunTestsCommandLineHandler DefaultCommandLineHandler) By now I'll try putting my handler a higher priority (1 :P), but, is this the expected behavior?

June 28, 2012

[Pharo-project] Magritte / XML bridge

by StÃ©phane Ducasse

Hi guys I would like to show in the magritte chapter I'm revisiting a bit more meat. I'm playing with magritte 30 and I would like to know if there is a way to save objects based on their magritte description. Stef

June 28, 2012

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

by Dale Henrichs

Igor, As you may or may not know, I am currently in the process of teaching Metacello to work with git/github and one of the pieces involves downloading and unzipping directory structure ... at the moment Metacello only works with package dependencies, but it wouldn't be a big leap to be able to manage non-source related dependencies so it might be possible for a configuration to declare a dependency upon a plugin which could be downloaded and moved to the appropriate location via Metacello ... If that type of facility would be useful, now is a good time to let me know, since I'm hip deep in that code as we speak:) Dale ----- Original Message ----- | From: "Igor Stasenko" <siguctua(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Thursday, June 28, 2012 11:36:21 AM | Subject: Re: [Pharo-project] VM , modules, packages and plugins | | On 28 June 2012 06:43, Torsten Bergmann <astares(a)gmx.de> wrote: | >>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 " | > | > The first problem is that there is no consolidated way to find | > the plugins. Or am I'm missing something. | | Yes. But we should not tolerate a current status quo.. | it starting really pedaling our efforts to improve the situation. | | > | > Remember this: | > | > http://code.google.com/p/pharo/wiki/VMPluginOverview | > http://web.archiveorange.com/archive/v/omFiNcYAwvI6GB8z7r1j | > | yes, thanks for reminder. | | > As ever it is a question of time to define and implement a | > working process. | > | | So, my vision that it should not be something external which user(s) | must download | and install separately and manually. Does everyone knows that page | exists? | Or, actually, why users must be concerned about those details: if | they | found a way to load | the code which using plugin, the rest should be NOT of their concern, | a system must | do the rest automatically. | | The code, which using the plugin SHOULD have the knowledge about how | to locate the plugin | and install it, and of course, which version of it to use. | This , i think, could kill many hurdles in distribution process and | improve user's experience. | | > Bye | > T. | > -- | > NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! | > Jetzt informieren: | > http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a | > | | | | -- | Best regards, | Igor Stasenko. | |

June 28, 2012

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

by Igor Stasenko

On 28 June 2012 06:43, Torsten Bergmann <astares(a)gmx.de> wrote: >>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 " > > The first problem is that there is no consolidated way to find > the plugins. Or am I'm missing something. Yes. But we should not tolerate a current status quo.. it starting really pedaling our efforts to improve the situation. > > Remember this: > > http://code.google.com/p/pharo/wiki/VMPluginOverview > http://web.archiveorange.com/archive/v/omFiNcYAwvI6GB8z7r1j > yes, thanks for reminder. > As ever it is a question of time to define and implement a > working process. > So, my vision that it should not be something external which user(s) must download and install separately and manually. Does everyone knows that page exists? Or, actually, why users must be concerned about those details: if they found a way to load the code which using plugin, the rest should be NOT of their concern, a system must do the rest automatically. The code, which using the plugin SHOULD have the knowledge about how to locate the plugin and install it, and of course, which version of it to use. This , i think, could kill many hurdles in distribution process and improve user's experience. > Bye > T. > -- > NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! > Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a > -- Best regards, Igor Stasenko.

June 28, 2012

Re: [Pharo-project] [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: [Pharo-project] [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: [Pharo-project] [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