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