hi, > On 20 Apr 2018, at 09:09, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > The underlying questions (sorry for people that need subtitles) are: > > - how do we have a central place to declare projects > - right now in Smalltalkhub/list is a nice way to find projects > with the move to github > we should get a central place > > Christophe has been working on project repository and we should check > what he has. > @Christophe? > > - how do we make sure that we can validated (I can load this version > of XMLParser in that version of Pharo) > -- in this version of Pharo what is the latest working version of this package > > - if people do not maintain/add "configuration" into the catalog what > is the point? > -- How can we ease the participation to the catalog? Esteban I do not > care about the format. > Do you think that editing STON is easier than a class? I think that we > should have a button.
STON is easier because : - you do not need to load a package to know a project spec. - you can edit it from outside, then participation is easier (in particular, people can add PRs and one can edit an STON file even in github site). yet, yes… regardless the choice we should have a “publish” plugin in iceberg. > Look people do not care about posting their project into the repo. but if they do not care to put their project in the cataog (whatever it is), is mostly sure they will not care to make it loadable (then validation is futile). btw… this query will give us all projects on github that with filetree format: https://github.com/search?q=filename%3A.filetree+.package&type=Code&ref=advsearch <https://github.com/search?q=filename:.filetree+.package&type=Code&ref=advsearch> (1531, but it will match each .filetree appearance so they are a lot less… ) and this one in tonel: https://github.com/search?q=filename%3A.properties+tonel&type=Code&ref=advsearch <https://github.com/search?q=filename:.properties+tonel&type=Code&ref=advsearch> (just 49 for now :(, but unique repositories :P) we can put those links in pharo README to make them easier to find… but of course this does not covers bitbucket or gitlab (they may have a public search API, but I don’t know it)… best approach is to have a catalog. > May be we need a crawler? we can, but we cannot know what is there in fact. btw… before we had sthub, but also ss, ss3 and others, so it was never clear about not published projects. > > @Peter no cargo is not dead now christophe cannot fix all the time the > PharoLauncher and make progress > on Cargo -> Pakbot > And yes I really want to have something that we can use soon. Cargo is orthogonal to the need of a centralised repository. Yes, its idea is to provide one… but we will need a central repo, always. cheers, Esteban > > - Needed immediate actions: > -- support baselineOf > -- how could we make sure that we can publish in multiple repo? (After > this is just a copy so I click on the package > and say copy to). > > What else. > @thierry the story I do not use the catalog because the icons are not > understandable is not really good to me. > > > Stef > > > On Thu, Apr 19, 2018 at 8:46 AM, Esteban Lorenzano <esteba...@gmail.com> > wrote: >> why to kill it? >> right now we do not have a replacement. >> >> Esteban >> >>> On 19 Apr 2018, at 08:42, Stephane Ducasse <stepharo.s...@gmail.com> wrote: >>> >>> Hi guys >>> >>> What do we do with it? >>> What alternatives? >>> >>> Stef >>> >> >> >
