June 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] A question on the catalog

by stepharo

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 inboxCurrentAlphaVersion (ie 60) -> validated for current version -> pushed into distribution 60 => revalidated for each new version -> not validated -> moved into currently not working for distribution 60 Le 12/6/16 Ã 23:11, Peter UhnÃ¡k a Ã©crit : > > 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 idea, because if you commit there now and Pharo changes > later, there is no guarantee that it would even load. > > Peter

June 13, 2016

Re: [Pharo-dev] A question on the catalog

by Peter UhnÃ¡k

> > 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 idea, because if you commit there now and Pharo changes later, there is no guarantee that it would even load. Peter

June 12, 2016

Re: [Pharo-dev] A question on the catalog

by Alistair Grant

On 11/06/2016 10:13 AM, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: > > Hi, > > > On 11 Jun 2016, at 08:53, Alistair Grant <akgrant0710(a)gmail.com> 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??? 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 put an option ???show all??? and hide those projects by default??? but now I think those projects SHOULD NOT BE VISIBLE AT ALL, as a way of: > >> > >> - offer better experience to non-power users, and > >> - encourage people to actually document their projects??? is very annoying to have so much of them without any documentation. > >> > >> What do you think? > > > > Rather than hiding projects that people were legitimately allowed to add > > (at the time), why not modify the catalog to not accept projects > > that don't have sufficient metadata, including the description? > > it is not possible right now, and the hiding would work as the same. Pity, it would also be nice to ensure that all submissions are marked with the version they have been tested against. > people were legitimately allowed is also relativeâ¦ truth is that most undocumented projects comes from MetacelloRepository (the original one) and there was no catalog nor metacello toolbox :P > but most important: most of those projects are unmaintained projects are will not load anyway, so they are not just source of noise, they also can make the community looks bad, I think. By "legitimately" I just meant that the system didn't reject them when they were submitted. I also expect at least some people were unaware that a description could be added. I only found our when I switched to using Versionner. > > > > > IIRC there was some discussion about hiding or lowering the priority of > > projects that haven't been modified or confirmed as working in the > > latest versions of Pharo. That would still be useful. > > well, hiding them would certainly âlower the categoryâ. My first approach (toggle hide/show) would work... > > > > > Between the two, that would get rid of undocumented projects. Thanks! Alistair

June 12, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60078 Home: https://github.com/pharo-project/pharo-core

June 12, 2016

[pharo-project/pharo-core] fefd78: 60078

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fefd781b306ae3487f48138b73ee7d2bc4427930 https://github.com/pharo-project/pharo-core/commit/fefd781b306ae3487f48138b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-12 (Sun, 12 Jun 2016) Changed paths: A Rubric.package/RubSmalltalkCommentMode.class/instance/as yet unclassified/isCodeCompletionAllowed.st M Rubric.package/RubSmalltalkEditor.class/instance/menu messages/selectedSelector.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60077.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60078.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60077.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60078.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60078 18413 disable code completion in comment pane https://pharo.fogbugz.com/f/cases/18413 18457 Allow # to be part of the string when searching senders and implementors https://pharo.fogbugz.com/f/cases/18457 http://files.pharo.org/image/60/60078.zip

June 12, 2016

Re: [Pharo-dev] [ANN] Enterprise Pharo book is released!

by Hilaire

Thanks guys. Ordered my hard copy. Hilaire -- Dr. Geo http://drgeo.eu

June 12, 2016

Re: [Pharo-dev] A question on the catalog

by Ben Coman

On Sat, Jun 11, 2016 at 4:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > >> On 11 Jun 2016, at 08:53, Alistair Grant <akgrant0710(a)gmail.com> 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??? 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 put an option ???show all??? and hide those projects by default??? but now I think those projects SHOULD NOT BE VISIBLE AT ALL, as a way of: >>> >>> - offer better experience to non-power users, and >>> - encourage people to actually document their projects??? is very annoying to have so much of them without any documentation. >>> >>> What do you think? >> >> Rather than hiding projects that people were legitimately allowed to add >> (at the time), why not modify the catalog to not accept projects >> that don't have sufficient metadata, including the description? > > it is not possible right now, and the hiding would work as the same. > > people were legitimately allowed is also relativeâ¦ truth is that most undocumented projects comes from MetacelloRepository (the original one) and there was no catalog nor metacello toolbox :P > but most important: most of those projects are unmaintained projects are will not load anyway, so they are not just source of noise, they also can make the community looks bad, I think. I agree its discouraging to see lots of blank descriptions when browsing the catalogue. Indeed it makes me wonder "is it working", which is bad. However I see something like Aconcagua which probably is very useful to have a catalog entry for, but maybe their it has no definite "owner" in our community. A solution besides completely hiding them would be to have an [Undocumented] tab. Then if the Catalog Browser had a help topic with a recipe on how to update the description of undocumented entries (download/modify/upload) perhaps(?) it would be easier for the community to contribute to updating them, than if they never appeared. I think our community image is maintained if the undocumented projects are segregated in this way. I think mainly brand/image suffers when deficiencies turn up in "official" looking locations. Not so much if its a designated badlands. It about user expectations and surprises. The default description might advise these were imported from a time before the catalog description field was defined, and refer to the help topic to request help updating the descriptions. cheers -ben > >> >> IIRC there was some discussion about hiding or lowering the priority of >> projects that haven't been modified or confirmed as working in the >> latest versions of Pharo. That would still be useful. > > well, hiding them would certainly âlower the categoryâ. My first approach (toggle hide/show) would work... > >> >> Between the two, that would get rid of undocumented projects. >> >> Just my 2c, >> Alistair > > cheers, > Esteban > >

June 11, 2016

Re: [Pharo-dev] IMPORTANT: Proposal to create a github team for Voyage and MongoTalk

by Dimitris Chloupis

On the subject on git lets make some things clear 1) You dont need github to use git, you can use any hosting service that can share your git folder like dropbox or your own personal server running pharo 2) No pharo github tool will ever replace github and giy gui tools, they have the community to maintain them we dont and they are awesome 3) The git process with pharo is well documented and git documentation itself is one of the best documentations I have read 4) Trying to reinvent git in Pharo is an interesting journey but git already works great with pharo and has been doing so way before gitfiletree and filetree with simple fileouts. 5) Git is not a simple tool not because its badly design but because version management is not a simple subject 6) its my personal opinion that improving in other fields is far more important than reinventing the wheel just because we are obsessed with a keeping everything in the image... well .... I am not *run and hides* On Fri, Jun 10, 2016 at 8:15 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > can someone contribute a configuration and put it in catalog? > this is too cool to not having it in a visible way :) > > cheers, > Esteban > > On 10 Jun 2016, at 17:45, Chris Cunningham <cunningham.cb(a)gmail.com> > wrote: > > Redis: > > MCHttpRepository > location: 'http://www.squeaksource.com/Redis' > user: '' > password: '' > > Works nicely, too (for the little bit that I've used it). > > -cbc > > On Fri, Jun 10, 2016 at 8:18 AM, Todd Blanchard <tblanchard(a)mac.com> > wrote: > >> 'NoSQL' covers a lot of ground. >> >> I don't suppose anyone has done a redis interface? >> >> On Jun 9, 2016, at 15:54, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> >> >> On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> But wellâ¦ is done :) >>> behold the new pharo-nosql organisation! >>> >>> https://github.com/pharo-nosql >>> >>> already running with travis ci (appveyor is on the way, in fact is done, >>> I just need to modify the vm :P) >>> >>> btw, Martin: your replicaset changes broke mongotalk tests :P (first >>> immediate positive feedback from moving there) >>> >> >> pull request created! >> >> >>> >>> Esteban >>> >>> On 09 Jun 2016, at 20:20, Esteban A. Maringolo <emaringolo(a)gmail.com> >>> wrote: >>> >>> 2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias(a)gmail.com>: >>> >>> On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code(a)gmail.com> wrote: >>> >>> On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >>> wrote: >>> >>> >>> And finally, more we move, more we have encourage to improve the tools, >>> complete the missing partsâ¦ >>> >>> >>> About a year ago I tried to use git for a project, but gave up because it >>> was not clear to me what tools and processes should be used. Having an >>> active project to follow (like PharoNoSQL) would maybe fill in the >>> missing >>> git knowledge I need. >>> >>> Yes, the same happened to me. >>> >>> >>> Ditto here. >>> >>> I do use GitHub and Bitbucket for other projects, with branches, pull >>> requests and all the jazz. >>> But with Pharo I only used filetree, and I'm never know exactly how >>> the changes are handled, what's all the metadata thing about, and so >>> on. But maybe because I commited the same package to both an MC repo >>> (STHub) and Git. >>> >>> Regards! >>> >>> >>> Esteban A. Maringolo >>> >>> >>> >> >> > >

June 11, 2016

Re: [Pharo-dev] A question on the catalog

by Dimitris Chloupis

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 or even the IRC and Slack channels. Though lately it has become harder to keep, which yes its a an awesome thing ;) Nonetheless I remember a couple of times people asking info for undocumented projects. But not more. The problem with these projects is not that they dont have documented description in the catalog but they dont have any sort of documentation. I am not suprised that people dont ask for them at all, I rarely seen people willing to learn with just reading code. Sure you can do that if you really want to learn something but most of the time you just dont want to waste your time doing that. To quote another developer "documentation is not an obligation its just a necessity for success" On Sat, 11 Jun 2016 at 14:06, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > 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 a fulltext search in description would be nice). > > On Sat, Jun 11, 2016 at 12:55 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> On Sat, Jun 11, 2016 at 12:14 PM, Dimitris Chloupis < >> kilon.alios(a)gmail.com> wrote: >> >>> First of all how many are undocumented ? Do we have any statistics ? >> >> >> 252/407 (~62%) >> >> For me +1 for removing/hiding undocumented ones. >> >> I would also propose to add a method having just the link to the original >> repo, whether that's smalltalkhub or github, and show that in the catalog >> browser. >> >> Peter >> >> >

June 11, 2016

Re: [Pharo-dev] A question on the catalog

by Peter UhnÃ¡k

> > 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 a fulltext search in description would be nice). On Sat, Jun 11, 2016 at 12:55 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Sat, Jun 11, 2016 at 12:14 PM, Dimitris Chloupis <kilon.alios(a)gmail.com > > wrote: > >> First of all how many are undocumented ? Do we have any statistics ? > > > 252/407 (~62%) > > For me +1 for removing/hiding undocumented ones. > > I would also propose to add a method having just the link to the original > repo, whether that's smalltalkhub or github, and show that in the catalog > browser. > > Peter > >

June 11, 2016