Looking at the Google Code shutdown timeline at http://google-opensource.blogspot.nl/2015/03/farewell-to-google-code.html, it would be best if we migrate away from Google Code before August. However, I can also put it on my personal github account for the time being. As to the steps required for migration, it would involve using tooling provided by Google to export the repository to my personal GitHub account, fixing issues like commit usernames, and then transferring ownership of the repository to the NetLogo organisation account on GitHub, then one of the owners/admins of NetLogo would need to create a write access team for this repository and assign us to that write access team.
I won't say that push rights are a hard requirement, but we (or at least I) would prefer to have some level of control over the code we created. GitHub allows for access control by creating teams, and assigning people and repositories to those teams. See https://help.github.com/articles/permission-levels-for-an-organization-repository/ So for example this could mean creating a "netlogo-sql" write access team, linking the netlogo-sql repository to that team, and assigning us to that team. This would mean that we have push rights only to the netlogo-sql repository, not to any of the other repositories on the organization account, and it would always be possible for the owners and admins of the organization account to revoke our access. As to continued updates: The project has been pretty much dormant for the last three years, and in that time hardly any issues have been raised. This project was created as part of the final project for our Bachelor degree at the Open University of The Netherlands; we don't use NetLogo in our day jobs, so we don't have a personal drive for new features/improvements. I do have some improvements in mind that I'd still like to do, but between my day job and my other open-source work I haven't made time for it yet. I guess our activity in general will be limited to reactive maintenance (in response to issues or pull requests raised). So yes, I do think we will make continued updates, but our activity will be low. Mark Op donderdag 2 april 2015 14:14:43 UTC+2 schreef Frank Duncan: > > I am following up on this. I believe this is the first request of its > kind, which is super neat! A few questions: > > * What is the timeline? > * How critical are push rights? > * Do you foresee making continued updates to it? > > Frank > > On Wed, Apr 01, 2015 at 11:46:30AM -0700, Mark Rotteveel wrote: > > I am one of the developers of the netlogo-sql extension > > (https://code.google.com/p/netlogo-sql/). With Google Code shutting > down, > > we want to migrate to github. I discussed this with the two other > original > > developers, and we came to the conclusion that we would prefer to create > > and migrate the repository under the Netlogo organization on Github > > (https://github.com/NetLogo) if possible. > > > > So my question is: would it be possible to do this, and would we be able > to > > retain push rights on this repository? > > > > If it is better to discuss this off-group, let me know. > > > > Kind regards, > > Mark Rotteveel > > -- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to netlogo-devel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
