On Sat, Dec 15, 2012 at 10:28 PM, Steven Silvester < [email protected]> wrote:
> Hey all, I hacked at spyderlib/plugins/inspector.py to create the rich > text doc strings in a QThread, to avoid the annoying lockup while editing. > I tested it and it works great. Let me know if there is a better way to > submit these changes. > > I know you all talked about switching to GitHub earlier, and I would like > to echo that sentiment. I have contributed to scikit-image and enaml, and > it has been as simple as sending them a pull request, having inline > discussions on the site, and them absorbing the changes directly. The > folks at scikit-image have posted an excellent workflow description, > modeled after the one used by the IPython developers: > http://scikit-image.org/docs/dev/gitwash/index.html. I was using > mercurial prior to working with them, but GitHub has completely sold me, > and the minor differences have not been troubling. > > Regards, > Steve Silvester Hi, Steve. As an aside, the github workflow you are looking for is possible with Google Code. It's just not as well known. The notion of "fork" is replaced with personal server-side "clones" of the project: http://code.google.com/p/spyderlib/source/clones You can push changes to these clones to share them. Once you have created a clone, you can enable code review in the clone under the "Administer...Source..." tab of the clone settings. Make sure both "Enable code reviews" and "Allow non-members to review code" are checked if you want to let others make comments on your proposed changes. The basic idea behind a git "feature branch" can be replicated in Hg by using Hg bookmarks. Hg named branches carry a bit more weight than bookmarking since they can't really be deleted. Hg bookmarks are a better analog to git branches. There is no specific "pull request" mechanism on Google Code, but just create a new case in the issue tracker (or edit the existing case if you're working on an already reported issue) and make reference to the fact that you are looking for a code review and a pull from your clone. Make sure you include a link to your clone and the name of the bookmark in your clone somewhere in the case text so it's easier to find the changes. -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
