#2 Convert to Mercurial or Git repository
The maintainers should consider converting the Subversion repository to either Mercurial or Git (or both). I'm happy to help with the migration. I have a Mercurial clone at https://bitbucket.org/jaraco/comtypes, which I created by running 'hg convert' on the subversion root. One caveat of that simple conversion is that the 'authors' are simple subversion userids. They should probably be translated to the full syntax recommended by Mercurial (at least for thomas.heller, theller, and cfarrow). If someone can provide the proper full names and e-mails, I can re-run the conversion with that translation.
I'm also comfortable converting from Mercurial to Git, so if Git is preferred, I could push the Mercurial repository to a Git repo (although the double-conversion may be undesirable).
Related
+1 move to github/bitbucket
Excellent suggestion. I am planning on hosting a public repo on github through my employer (Enthought) very soon. I can give this higher priority now that there is demand. I'll keep this post updated as I go along.
Just wanted to let you know, we have a fork on Github (with a private branch), in case this helps in any way:
https://github.com/Infinidat/comtypes/
I've converted the project's main repository from subversion to Mercurial. I chose Mercurial to provide an easier transition for those still only familiar with Subversion. It's a fairly straightforward transition from Mercurial to Git if the need arises. I still need to update the documentation and ensure that there aren't other issues around file discovery and packaging.
Christopher, Arnon - it sounds as if you may have a preference for Git over Mercurial. What's the impact on your workflow/use cases if we stick with Mercurial? What advantages do you see for using Git instead? Do those advantages outweigh the ease of use and transition from Subversion advantages for primarily Windows users of this package?
Jason, I cannot speak to the ease of use of mercurial over git for Windows users. I favor github more than git itself. In particular, github service hooks are great, and enable things like automated continuous integration, documentation and coverage generation. I think this is something comtypes could benefit from as it is brought up to speed with python 2.7, python 3 and changes in COM itself. Based on that, and the popularity of github with other open-source projects, I think github would be a good permanent home for the project.
I struggle with this decision, because there's no clear answer. I prefer Mercurial and Bitbucket, and I suspect some Windows developers would too. However, there's Github does have a very strong following and some nice features. I've used Travis-CI, for example, on a number of projects and wish that service had Bitbucket support. On the other hand, Travis-CI provides little value for a project that must be tested on Windows.
I'm personally very comfortable using Mercurial as my Git client (using hg-git), so the git branching and workflow strategy work fine for me. So given all these considerations, I'm inclined to make Github the primary home for the project. I expect I'll keep an unofficial clone of the project in my personal Bitbucket account for convenience.
Therefore, I've created the comtypes project at https://github.com/jaraco/comtypes. I'll be working today to see if I can complete the transition by migrating the tickets to github (I found https://github.com/ttencate/sf2github tool for that). I'll also be deleting the Mercurial repository as it is now entirely mirrored at https://bitbucket.org/jaraco/comtypes.
I'll report back here when the work is finalized.
After exploring sf2github, I've decided not to migrate the tickets. The migration doesn't include proper attribution or dates, which makes the migration less than ideal. Instead, I'll plan to resolve all tickets in sourceforge, linking to manually-created tickets for any ongoing issues.
The repository at gh://jaraco/comtypes is now the official repository.
Christopher, what's your GitHub username?
Christopher, what's your GitHub username?
About the Windows testing, Enthought has some infrastructure in place for testing on various platforms. The offer still stands to host comtypes under the enthought organization (http://github.com/enthought). If this is not agreeable, I propose that we create a comtypes organization on github.
In any case, I appreciate that you have taken the initiative on this.
My github user name is cfarrow.
I had forgotten/missed that offer. Yes, hosting under Enthought seems like a suitable organization. I didn't want to create a 'comtypes' organization, as I'm opposed in principle to per-project organizations.
I've submitted the request to transfer comtypes to enthought. Please accept the request and add me as an admin on the project if you please.
And thanks.
From: Christopher L Farrow [mailto:cfarrow@users.sf.net]
Sent: Sunday, 16 February, 2014 21:52
To: [comtypes:feature-requests]
Subject: [comtypes:feature-requests] #2 Convert to Mercurial or Git repository
About the Windows testing, Enthought has some infrastructure in place for testing on various platforms. The offer still stands to host comtypes under the enthought organization (http://github.com/enthought). If this is not agreeable, I propose that we create a comtypes organization on github.
In any case, I appreciate that you have taken the initiative on this.
My github user name is cfarrow.
[feature-requests:#2]http://sourceforge.net/p/comtypes/feature-requests/2/ Convert to Mercurial or Git repository
Status: closed
Created: Sat Aug 10, 2013 12:34 PM UTC by Jason R. Coombs
Last Updated: Mon Feb 17, 2014 12:18 AM UTC
Owner: nobody
The maintainers should consider converting the Subversion repository to either Mercurial or Git (or both). I'm happy to help with the migration. I have a Mercurial clone at https://bitbucket.org/jaraco/comtypes, which I created by running 'hg convert' on the subversion root. One caveat of that simple conversion is that the 'authors' are simple subversion userids. They should probably be translated to the full syntax recommended by Mercurial (at least for thomas.heller, theller, and cfarrow). If someone can provide the proper full names and e-mails, I can re-run the conversion with that translation.
I'm also comfortable converting from Mercurial to Git, so if Git is preferred, I could push the Mercurial repository to a Git repo (although the double-conversion may be undesirable).
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/comtypes/feature-requests/2/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
I see the request to transfer the project was denied as I don't have admin to enthought. I've added cfarrow as a collaborator on jaraco/comtypes, though I suspect that also doesn't give suitable privilege to transfer the repo.
So at this point, I say let's just punt and create the repo in the Enthought organization and I'll push the changes there.
From: Jason R. Coombs [mailto:jaraco@users.sf.net]
Sent: Monday, 17 February, 2014 09:55
To: [comtypes:feature-requests]
Subject: [comtypes:feature-requests] Re: #2 Convert to Mercurial or Git repository
I had forgotten/missed that offer. Yes, hosting under Enthought seems like a suitable organization. I didn't want to create a 'comtypes' organization, as I'm opposed in principle to per-project organizations.
I've submitted the request to transfer comtypes to enthought. Please accept the request and add me as an admin on the project if you please.
And thanks.
From: Christopher L Farrow [mailto:cfarrow@users.sf.net]
Sent: Sunday, 16 February, 2014 21:52
To: [comtypes:feature-requests]
Subject: [comtypes:feature-requests] #2 Convert to Mercurial or Git repository
About the Windows testing, Enthought has some infrastructure in place for testing on various platforms. The offer still stands to host comtypes under the enthought organization (http://github.com/enthought). If this is not agreeable, I propose that we create a comtypes organization on github.
In any case, I appreciate that you have taken the initiative on this.
My github user name is cfarrow.
[feature-requests:#2]http://sourceforge.net/p/openxava/feature-requests/2/http://sourceforge.net/p/comtypes/feature-requests/2/ Convert to Mercurial or Git repository
Status: closed
Created: Sat Aug 10, 2013 12:34 PM UTC by Jason R. Coombs
Last Updated: Mon Feb 17, 2014 12:18 AM UTC
Owner: nobody
The maintainers should consider converting the Subversion repository to either Mercurial or Git (or both). I'm happy to help with the migration. I have a Mercurial clone at https://bitbucket.org/jaraco/comtypes, which I created by running 'hg convert' on the subversion root. One caveat of that simple conversion is that the 'authors' are simple subversion userids. They should probably be translated to the full syntax recommended by Mercurial (at least for thomas.heller, theller, and cfarrow). If someone can provide the proper full names and e-mails, I can re-run the conversion with that translation.
I'm also comfortable converting from Mercurial to Git, so if Git is preferred, I could push the Mercurial repository to a Git repo (although the double-conversion may be undesirable).
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/comtypes/feature-requests/2/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
[feature-requests:#2]http://sourceforge.net/p/openxava/feature-requests/2/ Convert to Mercurial or Git repository
Status: closed
Created: Sat Aug 10, 2013 12:34 PM UTC by Jason R. Coombs
Last Updated: Mon Feb 17, 2014 02:52 AM UTC
Owner: nobody
The maintainers should consider converting the Subversion repository to either Mercurial or Git (or both). I'm happy to help with the migration. I have a Mercurial clone at https://bitbucket.org/jaraco/comtypes, which I created by running 'hg convert' on the subversion root. One caveat of that simple conversion is that the 'authors' are simple subversion userids. They should probably be translated to the full syntax recommended by Mercurial (at least for thomas.heller, theller, and cfarrow). If someone can provide the proper full names and e-mails, I can re-run the conversion with that translation.
I'm also comfortable converting from Mercurial to Git, so if Git is preferred, I could push the Mercurial repository to a Git repo (although the double-conversion may be undesirable).
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/comtypes/feature-requests/2/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Feature Requests:
#2Thanks, Jason. We are currently maintaining a private repo named "comtypes" for a client, and that may be why the transfer failed. I am working on either making that public or freeing up the "comtypes" name for transfer of your repo. (In either case, the final repo will inherit some enhancements from the other.)
For now, lets keep your repo while I work on the transfer issues. I'll send an update later in the week.
Here's that update I promised. The comtypes repo under the Enthought organization on github is now public (https://github.com/enthought/comtypes). There are still a few hurdles to jump over to complete migration.
As the repo currently exists, there are some changes that never made it back to the sourceforge repo. Those are open for public scrutiny now. Furthermore, the changes made by Jason since January of this year do not yet appear in this repo (aside from a few things I plucked recently).
The plan going forward is to migrate the changes made by Jason into the enthought repo. I will do this by creating pull requests for those changes. Meanwhile, I am working on getting Jason on the repo as a collaborator.
Once this is complete, I think it will be safe to remove the source from sourceforge.
I've already removed the code from sourceforge (to minimize surprise and synchronicity issues). Instead, the code as I converted it from the canonical Subversion repo plus changes which I recently contributed are now hosted on Github and Mercurial under the jaraco name (these two repos are matched). I would recommend using that source tree and grafting/merging the changes from the Enthought repo onto those, as others may have already cloned those repos as they were at the time consider the official conversions from Subversion. Those repos do also include the changes which I rolled into the 1.0 release, which is now public, so the tags should at least reflect that release.
I won't be offended if the Enthought repo is used as the canonical base - I just think it will be more trouble than using the jaraco repo(s).
Somehow my last post got dropped. In short, I agree that the public history should be considered official. The enthought/comtypes repo is a clone of jaraco/comtypes, with some added commits from the private enthought repo.
I have also transferred all the bugs from sourceforge to enthought/comtypes. I propose we shut off the bug tracker and make a clear redirect on the front page.