Copying/migrating languages repository to Github

[Andrew Whitworth]

That's a good point. I probably shouldn't have used the term "proof of
concept" in the previous email. Assuming there are no problems and no
complaints, these repos will stay where they are and will become the
primary points for future development of these projects. These are
basically smaller versions of the full migration of the main Parrot
repo to github, though are no less real.

If any developers would like to take personal stewardship over any of
these projects we can certainly move them out of the Parrot
organization umbrella. I put them under Parrot because they are in the
Parrot repo now, and are not personal projects (mostly because they
were not adopted by anybody when they were moved out of the primary
repo several months back). Until somebody does adopt them and take
personal stewardship over them, there really is no other suitable home
besides under the Parrot organization.

--Andrew Whitworth



On Thu, Sep 30, 2010 at 11:40 AM, Patrick R. Michaud <pmichaud at pobox.com> wrote:
> On Thu, Sep 30, 2010 at 11:12:59AM -0400, Andrew Whitworth wrote:
>> This is mostly a proof-of-concept migration to show that we can move
>> from svn to git on github without any headaches. I am not planning to
>> delete the languages repository or make it read-only or anything like
>> that. If I've screwed up the migration in anyway, we can delete things
>> on github and start over.
>
> FWIW, I think that "proof of concept" migrations are best done in
> personal GitHub repositories rather than the shared "parrot"
> repository.  That way the question of "official repository location"
> doesn't even come up.  Then, when a decision is made to actually
> switch things over, it's easy to re-migrate to the parrot account
> (or, if the personal migration worked out okay, to simply fork the
> personal repo into the parrot account).
>
> I'm not saying we need to eliminate the work that has already been
> done -- it's just a thought for the future.
>
> Pm
>