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.

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 <[hidden email]>:

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 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

Good news, I agree in special to move mongotalk. I will appreciate to have mongotalk in github to commit changes in a fork or branch until the changes are reviewed/stable.
Martin

Hi,

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
>
>

yes, this is one of my intentions: MongoTalk and Voyage are very co-dependent tools and needs to be close. 

2016-06-09 13:21 GMT-03:00 Martin Dias <[hidden email]>:
> On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <[hidden email]> wrote:
>> On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <[hidden email]>
>> 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 :)

'NoSQL' covers a lot of ground.

'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 <[hidden email]> wrote:

On Thu, Jun 9, 2016 at 3:26 PM, Esteban Lorenzano <[hidden email]> 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 <[hidden email]> wrote:

2016-06-09 13:21 GMT-03:00 Martin Dias <[hidden email]>:

On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <[hidden email]> wrote:

On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <[hidden email]>
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? 

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.