Hi Esteban, On 12 December 2017 at 14:02, Esteban Lorenzano <esteba...@gmail.com> wrote: > > >> On 11 Dec 2017, at 15:52, Alistair Grant <akgrant0...@gmail.com> wrote: >> >> On 11 December 2017 at 14:13, Esteban Lorenzano <esteba...@gmail.com> wrote: >>> hi, >>> >>> this migration was already made to: >>> >>> https://github.com/pharo-rdbms >>> >>> don’t you prefer to join that team and contribute to enhance there? >> >> Aaarrrgghh!!! I didn't know this existed! >> >> I had a look through my email archive and couldn't find any reference to >> it (pharo-user, pharo-dev and glorp-group). Was it announced somewhere? > > yes, I remember Guille sent a mail.
OK. I should have checked on github anyway. >> 1. pharo-rdbms loses all the commit history of Glorp, while my version >> keeps it all. >> >> Would you prefer to keep the history, or don't think it matters? If you >> want to keep the history I'm happy to put in the effort to move it >> across to pharo-rdbms. > > of course this is better, but essentially we do not care much. > There is a huge impedance between git repositories and mcz files so we just > preferred to put it there like that. > If you want to take the effort of moving to it, it will be fine :) At the moment it looks like I can't create a new repository (see below). >> 2. I have write permissions for smalltalkhub/DBXtalk. Is it possible to >> get commit permission to pharo-rdbms? > > > done :) Thanks! I'm not familiar with github privileges, so my apologies in advance if I'm confused. I can see that I'm a team member, but it looks like I don't have write privilege, e.g. if I try to create a development branch and push it: $ git push --set-upstream origin development ERROR: Permission to pharo-rdbms/glorp.git denied to akgrant43. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Also, trying to edit the readme from the github website has a "Propose the change", rather than a "Commit changes" button. Based on https://help.github.com/articles/repository-permission-levels-for-an-organization/ if I'm going to load the history, which I'd do by creating a new repository, then I'd also need Admin rights (I'm fine if you don't want to grant this, I'll just stick to the existing repository). >> 3. Is there a reason why ConfigurationOfGlorp on smalltalkhub hasn't >> been updated to use pharo-rdbms (or raise an error pointing to >> pharo-rdbms)? > > not really, just lack of time. OK. After I've updated the repository I'll add a deprecation warning in ConfigurationOfGlorp. Thanks! Alistair
