[Python.NET] github migration

[David Anthoff]

Hi everyone,

maybe now, after the holidays, is a better time to try to migrate python.net
to github. Really what would need to happen is that the original maintainers
take a look at my migration efforts and give feedback whether they want to
do that or not. Here is the link to the github repo:

https://github.com/pythonnet/pythonnet

Feel free to read my previous email below to see some of the details of the
migration.

Of course any other feedback from anyone else would also be welcome!

Thanks,
David

-----Original Message-----
From: PythonDotNet
[mailto:pythondotnet-bounces+davidacoder=hotmail.com at python.org] On Behalf
Of davidacoder
Sent: Wednesday, December 4, 2013 6:39 AM
To: pythondotnet at python.org
Subject: Re: [Python.NET] github migration

[I sent this yesterday already to the list but it looks like it didn't go
through, sorry if this is now the second mail...]

Every previous committer got back to me and agreed to be included in the git
history with name and email, thanks to everyone!

I now have an experimental git repo at
https://github.com/pythonnet/pythonnet. PLEASE don’t use that for anything
real yet, I expect more rebases before the migration is done! I’ll let
everyone know when the repo is ready for real work.

My current plan for next steps is this:
1. Please look at the repo and let me know if there are things you think
went wrong in the migration. If you think it looks good, please also let us
know 2. I’ve got one question on the migration for the list (see below)
please give feedback 3. Once we have sorted out anything that came up in 1
or 2, we should decide whether the migration should actually take place. My
sense is that Brian and Barton should probably make that call, but hopefully
everyone will just agree and we don’t have to come up with some formal
voting mechanism 4. If we decide to go with the migrated repo on github, I
have a number of very smallish things I want to do (add things like
.gitignore, readme etc) 5. We declare it the new home and people can start
submitting pull requests
:)

The main question I have is what to do about the branch
clr-2.0-python-2.5-branch that you can see on github. That branch existed at
some point in the svn repo (not anymore). It now has no parent and is not
merged in the git repo, i.e. it is entirely independent of anything else. I
believe the content of that branch was merged back into the main line way,
way back and then this branch was deleted in svn, but that merge is not
recorded as such in the git history. My sense is we should just delete the
branch in the git repo, mainly because I think the content is already in the
main line. But it does mean that we would lose the individual commits in
that branch. Any thoughts?

What follows below is a detailed description of what I did for the
migration, feel free to ignore.

- I started with the instructions here http://stackoverflow.com/a/3972103.
You can look at the repo that I got from that step at
https://github.com/pythonnet/pythonnet-rawsvnmig
- I deleted the branches clr-2.0-python-2.5-branch at 11,
clr-2.0-python-2.5-branch at 12 and clr-2.0-python-2.5-branch at 42, they weren’t
heads of anything and clearly just a migration artifact
- I deleted the branch barton-work-branch: it was empty
- I deleted the start tag and jrandom branch, they were clearly some initial
irrelevant experiments uncovered from git svn clone
- I deleted the Pythonnet-1_0-branch branch, it also seemed a dead end with
nothing on it, i.e. the real 1.0 work was on 1.0-branch
- The 1.0-branch had an unnecessary (empty) merge, I did a rebase that made
that part of the history cleaner without loss of any info
- The Brian-work-branch had been merged into the main line in such a way
that git would have fast-forwarded that. I did a rebase of the trunk for
that part, so that the individual commits are just in the history of trunk
and then deleted the now obsolete Brian-work-branch branch
- I renamed the trunk branch to develop (a la git flow)
- I renamed the 1.0-branch to release-1.0 (again a la git flow convention)
- I tagged the 1.0 release
- I set the master branch to point to the 1.0 tag (assuming that the 1.0
release is the last officially released version, again a la git flow
convention)
- The rebases had added my name to every commit as the committer (but of
course left the author field intact), I ran a script that equaled the
committer to the author for every commit. Long story short: the history
looks like it should without my name anywhere
- I created https://github.com/pythonnet/pythonnet.github.io that has the
documentation and updated the links in it, so that
http://pythonnet.github.io works

Any feedback welcome!

Cheers,
David


From: PythonDotNet
[mailto:pythondotnet-bounces+davidacoder=hotmail.com at python.org] On Behalf
Of davidacoder
Sent: Wednesday, November 27, 2013 2:13 PM
To: pythondotnet at python.org
Subject: Re: [Python.NET] github migration

I’m trying to create an as pretty history conversion as possible. Ideally I
want to convert the user names in the svn history to the standard git format
of “Firstname Lastname <email>”. To that extend I’ve contacted all the
people that have ever committed to the svn repo to ask for their permission
to include their email address in the new git history. My current plan is to
wait a couple of days to see who responds. If I don’t get a respond, I
intend to just use the “svnusername <unknown>” for those people.

I also created another repo that can host the homepage for the project, so
that http://pythonnet.github.io works.

So, nothing will happen for a couple of days until I hear back from previous
contributors, and then I’ll update you all again.

Best,
David

From: PythonDotNet
[mailto:pythondotnet-bounces+davidacoder=hotmail.com at python.org] On Behalf
Of davidacoder
Sent: Wednesday, November 27, 2013 2:13 PM
To: pythondotnet at python.org
Subject: Re: [Python.NET] github migration

I’m trying to create an as pretty history conversion as possible. Ideally I
want to convert the user names in the svn history to the standard git format
of “Firstname Lastname <email>”. To that extend I’ve contacted all the
people that have ever committed to the svn repo to ask for their permission
to include their email address in the new git history. My current plan is to
wait a couple of days to see who responds. If I don’t get a respond, I
intend to just use the “svnusername <unknown>” for those people.

I also created another repo that can host the homepage for the project, so
that http://pythonnet.github.io works.

So, nothing will happen for a couple of days until I hear back from previous
contributors, and then I’ll update you all again.

Best,
David

From: PythonDotNet
[mailto:pythondotnet-bounces+davidacoder=hotmail.com at python.org] On Behalf
Of davidacoder
Sent: Wednesday, November 27, 2013 9:07 AM
To: 'Tony Roberts'; pythondotnet at python.org
Subject: [Python.NET] github migration

Alright, I started this now. I created the github organization and the repo.
I will also have a stab at migrating the svn history.

I’ve marked the github repo as experimental for now so that it is clear that
at this point it is not the official source (yet).

I’ll keep the list updated as I make progress.

Cheers,
David

From: PythonDotNet
[mailto:pythondotnet-bounces+davidacoder=hotmail.com at python.org] On Behalf
Of Tony Roberts
Sent: Wednesday, November 27, 2013 6:04 AM
To: pythondotnet at python.org
Subject: Re: [Python.NET] PTVS and python.NET

Hi David,

that would seem to fit with the way most other projects work, and should
make it easier for anyone looking for the project on github to find it.

I'm happy to help out with the migration and maintenance if it is decided to
go ahead with this. The fork I created doesn't have the history from svn, so
I think it would be better to start again with the sourceforge project and
pull it into git with all the history and then merge in the various changes
already in github.

cheers,
Tony


On Wed, Nov 27, 2013 at 3:21 AM, davidacoder <davidacoder at hotmail.com>
wrote:
I guess my preferred option would be to create a github organization and
host the repo there. So something like github.com/pythonnet/pythonnet. In
that case the organization can have multiple owners, so the whole thing is
also less dependent on one person.
 
If, on the other hand, one of the original maintainers wanted to host it
under their account, I would also understand that, i.e. if this is really
someone’s baby.
 
Finally, I guess the official short name is “pythonnet”, right? Or
“pythondotnet”, like the mailing list alias?
 
Cheers,
David
 
From: Tribble, Brett [mailto:btribble at ea.com]
Sent: Tuesday, November 26, 2013 5:36 PM
To: davidacoder; pythondotnet at python.org; brian.lloyd at revolution.com
Subject: RE: [Python.NET] PTVS and python.NET
 
So, who is willing to be the primary maintainer of the github repository? I
think we should wait for a little while to see if Brian or Barton respond. I
see that tiran has a github account as well: https://github.com/tiran
 
From: PythonDotNet [mailto:pythondotnet-bounces+btribble=ea.com at python.org]
On Behalf Of davidacoder
Sent: Tuesday, November 26, 2013 6:37 AM
To: pythondotnet at python.org
Subject: Re: [Python.NET] PTVS and python.NET
 
Great idea!
 
Best,
David
 
From: PythonDotNet
[mailto:pythondotnet-bounces+davidacoder=hotmail.com at python.org] On Behalf
Of John Gill
Sent: Tuesday, November 26, 2013 7:47 AM
To: pythondotnet at python.org
Subject: [Python.NET] PTVS and python.NET
 
Related to a move to github, I have been in touch with the maintainer of
PTVS asking if they are aware of this project.  It seems such a natural fit.
 
He would be happy to:
 
1.       Put a link on our “Related projects” page 2.       Identify some
interesting scenarios and do a blog post 3.       Add a dedicated doc page
4.       Etc.
 
Subject to:
 
1.       The project is actively maintained 2.       Up to date docs
3.       It “works”
a.       Reliable & robust
b.      Works with PTVS (eg PTVS doesn’t crash, 
)
 
It would be great if PTVS was able to install python .NET for people (the
current install process “copy these dll’s” is simple and effective, but a
direct install from PTVS would be good.
 
I think we would need to resolve the current situation with the code split
between github and sourceforge before we could get the endorsement from
PTVS.
 
John
This communication and any attachments contain information which is
confidential and may also be legally privileged. It is for the exclusive use
of the intended recipient(s). If you are not the intended recipient(s)
please note that any form of disclosure, distribution, copying, printing or
use of this communication or the information in it or in any attachments is
strictly prohibited and may be unlawful. If you have received this
communication in error, please return it with the title "received in error"
to postmaster at tokiomillennium.com and then permanently delete the email and
any attachments from your system.
 
E-mail communications cannot be guaranteed to be secure or error free, as
information could be intercepted, corrupted, amended, lost, destroyed,
arrive late or incomplete, or contain viruses. It is the recipient's
responsibility to ensure that e-mail transmissions and any attachments are
virus free. We do not accept liability for any damages or other consequences
caused by information that is intercepted, corrupted, amended, lost,
destroyed, arrives late or incomplete or contains viruses.
******************************************

_________________________________________________
Python.NET mailing list - PythonDotNet at python.org
https://mail.python.org/mailman/listinfo/pythondotnet

_________________________________________________
Python.NET mailing list - PythonDotNet at python.org
https://mail.python.org/mailman/listinfo/pythondotnet