IMPORTANT: Proposal to create a github team for Voyage and MongoTalk
Hi, (this mail is intended to Voyage/MongoTalk users and collaborators) Iâm spending a couple of days in Cologne, at 2Denker offices and I was talking Norbert about organisation of Voyage and the NoSQL drivers⦠As a conclusion, we want to propose to move the Voyage and MongoTalk development to github, into a common team where other NoSQL drivers can eventually arrive (Voyage will incorporate other backends that might well be there). One reason from this is that I do not consider appropriate to keep Voyage into my repository, because is more a community project than a personal one. I want others to be able to participate more and I think this is the right step (also Dale is porting it to Gemstone soâ¦) Using github we can benefit of their tools to improve our process (issue tracker, travis and appveyor, etc.) and we will improve project visibility. So, we wanted to create âPharoNoSQL" team, and move all there⦠then we will close sthub projects to avoid confusion and we will handle configurations and baselines same way as Yuriy does with QualityAssistance (so it will be available through catalog as always). Opinions? Esteban
Hi Esteban, a few days ago, I started reading about Pharo/Github because I am interested in administering my code in github, too. I stopped then, because I loose time, which I can not spend in development of my application. I thought, I will do that later - when there will be more automated support for github within Pharo. Also, from the beginning of administering my code in github, I have to pay for it, because my project is not public. But in the long run, I have to do this and learn it and I am looking forward to it. And getting code for mongo from github does not mean, putting my stuff there immediately, too. For me it would be the first github learning step. It would help to have a description, what to do to get the code then from github instead of sthub, but I am sure you will do that. I mean not only get code from catalog but also through my configurationOf.... I would be happy to help if I can. Regards Sabine 2016-06-08 11:54 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
Hi,
(this mail is intended to Voyage/MongoTalk users and collaborators)
Iâm spending a couple of days in Cologne, at 2Denker offices and I was talking Norbert about organisation of Voyage and the NoSQL drivers⦠As a conclusion, we want to propose to move the Voyage and MongoTalk development to github, into a common team where other NoSQL drivers can eventually arrive (Voyage will incorporate other backends that might well be there).
One reason from this is that I do not consider appropriate to keep Voyage into my repository, because is more a community project than a personal one. I want others to be able to participate more and I think this is the right step (also Dale is porting it to Gemstone soâ¦)
Using github we can benefit of their tools to improve our process (issue tracker, travis and appveyor, etc.) and we will improve project visibility.
So, we wanted to create âPharoNoSQL" team, and move all there⦠then we will close sthub projects to avoid confusion and we will handle configurations and baselines same way as Yuriy does with QualityAssistance (so it will be available through catalog as always).
Opinions?
Esteban
Le 8/6/16 à 12:12, Sabine Manaa a écrit :
Hi Esteban,
a few days ago, I started reading about Pharo/Github because I am interested in administering my code in github, too. I stopped then, because I loose time, which I can not spend in development of my application. I thought, I will do that later - when there will be more automated support for github within Pharo. Also, from the beginning of administering my code in github, I have to pay for it, because my project is not public.
use bitbucket Now Pharo will move to git so it is just a question of time.
But in the long run, I have to do this and learn it and I am looking forward to it. And getting code for mongo from github does not mean, putting my stuff there immediately, too. For me it would be the first github learning step.
But this will be transparent for you. Just load the configuration from the Catalog and nothing to change.
It would help to have a description, what to do to get the code then from github instead of sthub, but I am sure you will do that. I mean not only get code from catalog but also through my configurationOf....
I would be happy to help if I can.
Regards Sabine
2016-06-08 11:54 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
Hi,
(this mail is intended to Voyage/MongoTalk users and collaborators)
Iâm spending a couple of days in Cologne, at 2Denker offices and I was talking Norbert about organisation of Voyage and the NoSQL drivers⦠As a conclusion, we want to propose to move the Voyage and MongoTalk development to github, into a common team where other NoSQL drivers can eventually arrive (Voyage will incorporate other backends that might well be there).
One reason from this is that I do not consider appropriate to keep Voyage into my repository, because is more a community project than a personal one. I want others to be able to participate more and I think this is the right step (also Dale is porting it to Gemstone soâ¦)
Using github we can benefit of their tools to improve our process (issue tracker, travis and appveyor, etc.) and we will improve project visibility.
So, we wanted to create âPharoNoSQL" team, and move all there⦠then we will close sthub projects to avoid confusion and we will handle configurations and baselines same way as Yuriy does with QualityAssistance (so it will be available through catalog as always).
Opinions?
Esteban
On Wed, Jun 8, 2016 at 5:54 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
So, we wanted to create âPharoNoSQL" team, and move all thereâ¦
Opinions?
Excellent idea, for all the reasons you pointed out. Having Voyage/GemStone is a great idea too. -- Yanni
On 08/06/16 11:54, Esteban Lorenzano wrote:
Using github we can benefit of their tools to improve our process (issue tracker, travis and appveyor, etc.) and we will improve project visibility.
I fear that without the in-image tooling, it will be difficult to actually get other people to contribute at the code level. I have, and have seen others, struggled to use git-based tooling for Pharo. Stephan
Hi,
On 09 Jun 2016, at 00:51, Stephan Eggermont <stephan@stack.nl> wrote:
On 08/06/16 11:54, Esteban Lorenzano wrote:
Using github we can benefit of their tools to improve our process (issue tracker, travis and appveyor, etc.) and we will improve project visibility.
I fear that without the in-image tooling, it will be difficult to actually get other people to contribute at the code level. I have, and have seen others, struggled to use git-based tooling for Pharo.
well, I think is the opposite: at this moment all active voyage developers are already using git/github (because voyage is being developed there, just in mine repository)⦠and it happens they are also the MongoTalk active developers. Also, filetree and gitfiletree are becoming more and more popular, at the point most ânewâ projects (specially those made by new people) I know are made with git as storage. And finally, more we move, more we have encourage to improve the tools, complete the missing parts⦠Esteban
Stephan
On 09 Jun 2016, at 08:58, Esteban Lorenzano <estebanlm@gmail.com> wrote:
well, I think is the opposite: at this moment all active voyage developers are already using git/github (because voyage is being developed there, just in mine repository)⦠and it happens they are also the MongoTalk active developers.
I must have said: except you ;)
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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.
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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.
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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
But well⦠is done :) behold the new pharo-nosql organisation! https://github.com/pharo-nosql <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) Esteban
On 09 Jun 2016, at 20:20, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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
On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@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@gmail.com> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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
'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@gmail.com> wrote:
On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote: But well⦠is done :) behold the new pharo-nosql organisation!
https://github.com/pharo-nosql <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@gmail.com <mailto:emaringolo@gmail.com>> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com <mailto:tinchodias@gmail.com>>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com <mailto:yanni.code@gmail.com>> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@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
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@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@gmail.com> wrote:
On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@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@gmail.com> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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
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@gmail.com> wrote:
Redis:
MCHttpRepository location: 'http://www.squeaksource.com/Redis <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@mac.com <mailto:tblanchard@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@gmail.com <mailto:tinchodias@gmail.com>> wrote:
On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> wrote: But well⦠is done :) behold the new pharo-nosql organisation!
https://github.com/pharo-nosql <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@gmail.com <mailto:emaringolo@gmail.com>> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com <mailto:tinchodias@gmail.com>>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com <mailto:yanni.code@gmail.com>> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@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
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@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@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@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@gmail.com> wrote:
On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@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@gmail.com> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote:
On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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
Well, yes there is one somewhere around. Search in sthub or around :)
On 10 Jun 2016, at 17:18, Todd Blanchard <tblanchard@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@gmail.com> wrote:
On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <estebanlm@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@gmail.com> wrote:
2016-06-09 13:21 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <yanni.code@gmail.com> wrote: On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <estebanlm@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
On Fri, Jun 10, 2016 at 08:18:51AM -0700, Todd Blanchard wrote:
'NoSQL' covers a lot of ground.
Excerpted from an old blog post of mine: Riak: - Runar Jordahl's [EpigentRiakInterface](http://squeaksource.com/EpigentRiakInterface). - Goran Krampe's fork, [Phriak](http://www.smalltalkhub.com/#!/~gokr/Phriak). HBase runs on JVM. It supports a RESTful HTTP API, [Thrift](http://thrift.apache.org/), and a Java API. The first is probably the easiest way to write a Smalltalk interface. MongoDB: - Esteban Lorenzano's [Voyage](http://smallworks.com.ar/web/projects/voyage) is an object persistence layer that works with MongoDB. - [MongoTalk](http://www.squeaksource.com/MongoTalk/), by Kent Beck and others. CouchDB: - [SCouchDB](http://squeaksource.com/SCouchDB/) by Igor Stasenko. - [SCouchDBViewServer](http://ss3.gemstone.com/ss/SCouchViewServer.html), by Jesus Mari Aguirre, a fork and superset that includes other functionality.
participants (11)
-
Chris Cunningham -
Dimitris Chloupis -
Esteban A. Maringolo -
Esteban Lorenzano -
Martin Dias -
Pierce Ng -
Sabine Manaa -
Stephan Eggermont -
stepharo -
Todd Blanchard -
Yanni Chiu