yes, this is one of my intentions: MongoTalk and Voyage are very co-dependent tools and needs to be close. for example, we have a new MongoTalk version and Voyage depends on it, but there is no stable configuration so people is having a lot of problems. Of course this is easy fixable, but if they are close we can handle it better. … and the possibility of keeping a branch and going back to trunk when ready is an important plus :) cheers, Esteban

On 09 Jun 2016, at 05:43, Martin Dias <tinchodias@gmail.com> wrote:

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

El 8/6/2016 6:54, "Esteban Lorenzano" <estebanlm@gmail.com <mailto:estebanlm@gmail.com>> escribió: 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