We will sit down with Pavel.
I was thinking that we should have a process like this one:
Inbox50
-> validated for current version -> pushed into distribution 50
-> not validated -> moved into
currently not working for distribution 50
>
> Pity, it would also be nice to ensure that all submissions are marked
> with the version they have been tested against.
>
This is done by commiting to the appropriate MetaRepoXY (where XY is Pharo
version).
Although I mentioned to Esteban that having MetaRepo60 right now is a bit
broken
On 11/06/2016 10:13 AM, "Esteban Lorenzano" wrote:
>
> Hi,
>
> > On 11 Jun 2016, at 08:53, Alistair Grant wrote:
> >
> > Hi Esteban,
> >
> > On Fri, Jun 10, 2016 at 02:52:46PM +0200, Esteban Lorenzano wrote:
> >> Hi,
> >>
> >> I was doing a pass on the
On Sat, Jun 11, 2016 at 4:12 PM, Esteban Lorenzano wrote:
> Hi,
>
>> On 11 Jun 2016, at 08:53, Alistair Grant wrote:
>>
>> Hi Esteban,
>>
>> On Fri, Jun 10, 2016 at 02:52:46PM +0200, Esteban Lorenzano wrote:
>>> Hi,
>>>
>>> I was doing a pass on the
The emphasis here is "I dont think" so this is a personal assumption not a
fact based theory.
So I would not talk about evidence but indications , I have been an active
participant of the pharo community for 4 years now. There are not many
messages that I have missed in Pharo-dev or Pharo-users
>
> I don't thinks it's a huge issue because most people use catalog as an
> easy install and not to discover new packages.
Do you have any evidence to back up "most people" claim? We don't have any
good mechanisms to discover Pharo projects and catalog is frankly the most
complete one (although
First of all how many are undocumented ? Do we have any statistics ?
Personally I don't thinks it's a huge issue because most people use catalog
as an easy install and not to discover new packages. I have not even
bothered to read the ones that are documented. Frankly I don't mind because
I always
2016-06-11 10:17 GMT+02:00 Esteban Lorenzano :
>
> > On 11 Jun 2016, at 09:17, stepharo wrote:
> >
> > Esteban
> >
> > The current catalog is an inbox. We should define the rules for the real
> ones and validate the entries.
> >
> > Entries that are not
right now
We should remove the ones with no documentation.
Or let us in Pharo 60 we only accept the ones with documentation.
Le 11/6/16 à 10:17, Esteban Lorenzano a écrit :
On 11 Jun 2016, at 09:17, stepharo wrote:
Esteban
The current catalog is an inbox. We should define
> On 11 Jun 2016, at 09:17, stepharo wrote:
>
> Esteban
>
> The current catalog is an inbox. We should define the rules for the real ones
> and validate the entries.
>
> Entries that are not described should not be put in the real catalog.
yes, but validation rules is
Hi,
> On 11 Jun 2016, at 08:53, Alistair Grant wrote:
>
> Hi Esteban,
>
> On Fri, Jun 10, 2016 at 02:52:46PM +0200, Esteban Lorenzano wrote:
>> Hi,
>>
>> I was doing a pass on the catalog??? I think is very negative that
>> non-documented projects appear there???
Esteban
The current catalog is an inbox. We should define the rules for the real
ones and validate the entries.
Entries that are not described should not be put in the real catalog.
Stef
Le 10/6/16 à 14:52, Esteban Lorenzano a écrit :
Hi,
I was doing a pass on the catalog… I think is
Hi Esteban,
On Fri, Jun 10, 2016 at 02:52:46PM +0200, Esteban Lorenzano wrote:
> Hi,
>
> I was doing a pass on the catalog??? I think is very negative that
> non-documented projects appear there??? because most people does not know
> what does projects are about and newcomers will find weird
Hi,
I was doing a pass on the catalog… I think is very negative that non-documented
projects appear there… because most people does not know what does projects are
about and newcomers will find weird a project install tool with lots of
projects without any description.
So I was thinking on
14 matches
Mail list logo