Then you better read how populations or languages become extinct.

Hernán

2013/12/24 Esteban Lorenzano <[hidden email]>

btw that also means that we do not accept code in the form of : simple packages (without configuration or Issue/SLICE), change sets or code in mail threads (something that happens a lot more than it should).

On 24 Dec 2013, at 14:06, Esteban Lorenzano <[hidden email]> wrote:

> Yeah, that part I can understand it.
> What I don’t understand is what would be that.
>
> Packages part of pharo core are in in Pharo team in smalltalkhub
> Packages part of pharo extras are un PharoExtras team in smalltalkhub
>
> we, as core pharo developers take responsibility over the packages that resides there, and of course any contribution is welcome.
>
> For the stuff in Pharo team, you need to work in the form of “Issue report” and “SLICE provider”.
> For the stuff in PharoExtras, you can provide just the package updates + the *updated* configuration.
>
> All PharoExtras projects should have a jenkins job in https://ci.inria.fr/pharo-contribution/?
> And you should take care that job is green after you commit your packages.
>
> For contribute in any of the teams, Pharo and PharoExtras you need to be added as team member, and that can be done just requiting it in pharo-dev list (which, btw, is a better place for this discussion).
>
> Esteban
>
> On 24 Dec 2013, at 13:57, Hernán Morales Durand <[hidden email]> wrote:
>
>> El 24/12/2013 9:06, Esteban Lorenzano escribió:
>>>
>>> On 24 Dec 2013, at 12:34, Hernán Morales Durand <[hidden email]> wrote:
>>>
>>>> I am interested in how to proceed about community packages. I have previously asked and nobody replied:
>>>>
>>>> http://forum.world.st/Programmatic-Scoped-Browsing-td4724820.html
>>>
>>> what is a “community package”?
>>>
>>
>> The point of a community package is to involve as much of the community as possible.
>>
>> Hernán
>>
>>
>
>