This weekend I will attempt to locate or write a script that moves all of our core Trac issues to Github, and automates the process of obtaining nightly archives of the source.
The svn repo url for core will either be shut down or redirect to the svn mirror on Github, through which you can check out projects from Github via svn as read-only. Users that use svn to update blogs should need only execute a simple `svn switch` to continue as they have been.
We're going to need time to work out what to do with the -extras repo, but I expect that ultimately those projects will also be available via Github. This will not happen this week.
I realize that there is still a lot of uncertainty about what using git and Github means. Everyone is likely to have questions, but trust me when I say that git is just another SCM tool. At worst, you have to learn a few different commands. At best, we reap great rewards from the collaborative coding features that Github offers, gain efficiency from the features that git has that aren't present in svn, and release some of our otherwise more prolific contributors from frequent server maintenance tasks. I firmly believe that this move will benefit the project.
Please +1 this thread if you're in support. If you still have reservations to the point where you can't +1 the thread, please ask specific, positive questions that we can help answer. We should only delay this process if there is a credible reason not to move the core repo before the weekend - let's not let bureaucracy hinder innovation.
I'm hoping that a couple of folks familiar with git can step up and draft a wiki page that outlines some of the changes from svn to git, specific to our project (using our URLs and likely tasks to get things moving) and link to some good external resources for learning git from an svn user's perspective.
On Tue, Jun 21, 2011 at 11:28 PM, Owen Winkler <epit...@gmail.com> wrote: > This weekend I will attempt to locate or write a script that moves all of > our core Trac issues to Github, and automates the process of obtaining > nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the svn > mirror on Github, through which you can check out projects from Github via > svn as read-only. Users that use svn to update blogs should need only > execute a simple `svn switch` to continue as they have been.
> We're going to need time to work out what to do with the -extras repo, but > I expect that ultimately those projects will also be available via Github. > This will not happen this week.
> I realize that there is still a lot of uncertainty about what using git and > Github means. Everyone is likely to have questions, but trust me when I say > that git is just another SCM tool. At worst, you have to learn a few > different commands. At best, we reap great rewards from the collaborative > coding features that Github offers, gain efficiency from the features that > git has that aren't present in svn, and release some of our otherwise more > prolific contributors from frequent server maintenance tasks. I firmly > believe that this move will benefit the project.
> Please +1 this thread if you're in support. If you still have reservations > to the point where you can't +1 the thread, please ask specific, positive > questions that we can help answer. We should only delay this process if > there is a credible reason not to move the core repo before the weekend - > let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and draft a > wiki page that outlines some of the changes from svn to git, specific to our > project (using our URLs and likely tasks to get things moving) and link to > some good external resources for learning git from an svn user's > perspective.
> Thanks, > Owen
> -- > To post to this group, send email to habari-dev@googlegroups.com > To unsubscribe from this group, send email to habari-dev-unsubscribe@** > googlegroups.com <habari-dev-unsubscribe@googlegroups.com> > For more options, visit this group at http://groups.google.com/** > group/habari-dev <http://groups.google.com/group/habari-dev>
On Tue, Jun 21, 2011 at 4:28 PM, Owen Winkler <epit...@gmail.com> wrote: > This weekend I will attempt to locate or write a script that moves all of > our core Trac issues to Github, and automates the process of obtaining > nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the svn > mirror on Github, through which you can check out projects from Github via > svn as read-only. Users that use svn to update blogs should need only > execute a simple `svn switch` to continue as they have been.
> We're going to need time to work out what to do with the -extras repo, but > I expect that ultimately those projects will also be available via Github. > This will not happen this week.
> I realize that there is still a lot of uncertainty about what using git and > Github means. Everyone is likely to have questions, but trust me when I say > that git is just another SCM tool. At worst, you have to learn a few > different commands. At best, we reap great rewards from the collaborative > coding features that Github offers, gain efficiency from the features that > git has that aren't present in svn, and release some of our otherwise more > prolific contributors from frequent server maintenance tasks. I firmly > believe that this move will benefit the project.
> Please +1 this thread if you're in support. If you still have reservations > to the point where you can't +1 the thread, please ask specific, positive > questions that we can help answer. We should only delay this process if > there is a credible reason not to move the core repo before the weekend - > let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and draft a > wiki page that outlines some of the changes from svn to git, specific to our > project (using our URLs and likely tasks to get things moving) and link to > some good external resources for learning git from an svn user's > perspective.
> Thanks, > Owen
> -- > To post to this group, send email to habari-dev@googlegroups.com > To unsubscribe from this group, send email to habari-dev-unsubscribe@** > googlegroups.com <habari-dev-unsubscribe@googlegroups.com> > For more options, visit this group at http://groups.google.com/** > group/habari-dev <http://groups.google.com/group/habari-dev>
> Rich Bowen <mailto:rbo...@rcbowen.com> > June 21, 2011 2:23 PM
> +0.5
> An SCM is an SCM, and I suppose this is as good a way as any to figure > out whether the hype surrounding GitHub has any intersection with > reality.
> For me, the biggest selling point is the "someone else does backups", > rather than the fact that it's Git.
> Owen Winkler <mailto:epit...@gmail.com> > June 21, 2011 10:28 AM
> This weekend I will attempt to locate or write a script that moves all > of our core Trac issues to Github, and automates the process of > obtaining nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the > svn mirror on Github, through which you can check out projects from > Github via svn as read-only. Users that use svn to update blogs > should need only execute a simple `svn switch` to continue as they > have been.
> We're going to need time to work out what to do with the -extras repo, > but I expect that ultimately those projects will also be available via > Github. This will not happen this week.
> I realize that there is still a lot of uncertainty about what using > git and Github means. Everyone is likely to have questions, but trust > me when I say that git is just another SCM tool. At worst, you have > to learn a few different commands. At best, we reap great rewards > from the collaborative coding features that Github offers, gain > efficiency from the features that git has that aren't present in svn, > and release some of our otherwise more prolific contributors from > frequent server maintenance tasks. I firmly believe that this move > will benefit the project.
> Please +1 this thread if you're in support. If you still have > reservations to the point where you can't +1 the thread, please ask > specific, positive questions that we can help answer. We should only > delay this process if there is a credible reason not to move the core > repo before the weekend - let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and > draft a wiki page that outlines some of the changes from svn to git, > specific to our project (using our URLs and likely tasks to get things > moving) and link to some good external resources for learning git from > an svn user's perspective.
> Owen Winkler <mailto:epit...@gmail.com> > June 21, 2011 11:28 AM
> This weekend I will attempt to locate or write a script that moves all > of our core Trac issues to Github, and automates the process of > obtaining nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the > svn mirror on Github, through which you can check out projects from > Github via svn as read-only. Users that use svn to update blogs > should need only execute a simple `svn switch` to continue as they > have been.
> We're going to need time to work out what to do with the -extras repo, > but I expect that ultimately those projects will also be available via > Github. This will not happen this week.
> I realize that there is still a lot of uncertainty about what using > git and Github means. Everyone is likely to have questions, but trust > me when I say that git is just another SCM tool. At worst, you have > to learn a few different commands. At best, we reap great rewards > from the collaborative coding features that Github offers, gain > efficiency from the features that git has that aren't present in svn, > and release some of our otherwise more prolific contributors from > frequent server maintenance tasks. I firmly believe that this move > will benefit the project.
> Please +1 this thread if you're in support. If you still have > reservations to the point where you can't +1 the thread, please ask > specific, positive questions that we can help answer. We should only > delay this process if there is a credible reason not to move the core > repo before the weekend - let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and > draft a wiki page that outlines some of the changes from svn to git, > specific to our project (using our URLs and likely tasks to get things > moving) and link to some good external resources for learning git from > an svn user's perspective.
Once I found the (admittedly beta) feature that allows subversion
commits to a github repository, that pretty much made this a
certainty. Even without that, removing the overhead of troubleshooting
Trac or even administering it (and what administrivia comes with
running our own subversion repo) means more time we can spend moving
the project forward, instead of merely keeping it running.
mikelietz
On Jun 21, 11:28 am, Owen Winkler <epit...@gmail.com> wrote:
> This weekend I will attempt to locate or write a script that moves all
> of our core Trac issues to Github, and automates the process of
> obtaining nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the
> svn mirror on Github, through which you can check out projects from
> Github via svn as read-only. Users that use svn to update blogs should
> need only execute a simple `svn switch` to continue as they have been.
> We're going to need time to work out what to do with the -extras repo,
> but I expect that ultimately those projects will also be available via
> Github. This will not happen this week.
> I realize that there is still a lot of uncertainty about what using git
> and Github means. Everyone is likely to have questions, but trust me
> when I say that git is just another SCM tool. At worst, you have to
> learn a few different commands. At best, we reap great rewards from the
> collaborative coding features that Github offers, gain efficiency from
> the features that git has that aren't present in svn, and release some
> of our otherwise more prolific contributors from frequent server
> maintenance tasks. I firmly believe that this move will benefit the
> project.
> Please +1 this thread if you're in support. If you still have
> reservations to the point where you can't +1 the thread, please ask
> specific, positive questions that we can help answer. We should only
> delay this process if there is a credible reason not to move the core
> repo before the weekend - let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and
> draft a wiki page that outlines some of the changes from svn to git,
> specific to our project (using our URLs and likely tasks to get things
> moving) and link to some good external resources for learning git from
> an svn user's perspective.
> This weekend I will attempt to locate or write a script that moves all > of our core Trac issues to Github, and automates the process of > obtaining nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the > svn mirror on Github, through which you can check out projects from > Github via svn as read-only. Users that use svn to update blogs should > need only execute a simple `svn switch` to continue as they have been.
> We're going to need time to work out what to do with the -extras repo, > but I expect that ultimately those projects will also be available via > Github. This will not happen this week.
> I realize that there is still a lot of uncertainty about what using git > and Github means. Everyone is likely to have questions, but trust me > when I say that git is just another SCM tool. At worst, you have to > learn a few different commands. At best, we reap great rewards from the > collaborative coding features that Github offers, gain efficiency from > the features that git has that aren't present in svn, and release some > of our otherwise more prolific contributors from frequent server > maintenance tasks. I firmly believe that this move will benefit the > project.
> Please +1 this thread if you're in support. If you still have > reservations to the point where you can't +1 the thread, please ask > specific, positive questions that we can help answer. We should only > delay this process if there is a credible reason not to move the core > repo before the weekend - let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and > draft a wiki page that outlines some of the changes from svn to git, > specific to our project (using our URLs and likely tasks to get things > moving) and link to some good external resources for learning git from > an svn user's perspective.
> Thanks, > Owen
-- knowledge has no owner, only means to reveal itself
> This weekend I will attempt to locate or write a script that moves all of > our core Trac issues to Github, and automates the process of obtaining > nightly archives of the source.
> The svn repo url for core will either be shut down or redirect to the svn > mirror on Github, through which you can check out projects from Github via > svn as read-only. Users that use svn to update blogs should need only > execute a simple `svn switch` to continue as they have been.
> We're going to need time to work out what to do with the -extras repo, but > I expect that ultimately those projects will also be available via Github. > This will not happen this week.
> I realize that there is still a lot of uncertainty about what using git and > Github means. Everyone is likely to have questions, but trust me when I say > that git is just another SCM tool. At worst, you have to learn a few > different commands. At best, we reap great rewards from the collaborative > coding features that Github offers, gain efficiency from the features that > git has that aren't present in svn, and release some of our otherwise more > prolific contributors from frequent server maintenance tasks. I firmly > believe that this move will benefit the project.
> Please +1 this thread if you're in support. If you still have reservations > to the point where you can't +1 the thread, please ask specific, positive > questions that we can help answer. We should only delay this process if > there is a credible reason not to move the core repo before the weekend - > let's not let bureaucracy hinder innovation.
> I'm hoping that a couple of folks familiar with git can step up and draft a > wiki page that outlines some of the changes from svn to git, specific to our > project (using our URLs and likely tasks to get things moving) and link to > some good external resources for learning git from an svn user's > perspective.
> Thanks, > Owen
> -- > To post to this group, send email to habari-dev@googlegroups.com > To unsubscribe from this group, send email to habari-dev-unsubscribe@** > googlegroups.com <habari-dev-unsubscribe@googlegroups.com> > For more options, visit this group at http://groups.google.com/** > group/habari-dev <http://groups.google.com/group/habari-dev>
On Wed, Jun 22, 2011 at 9:52 AM, Ali B. <dmond...@gmail.com> wrote: > +1
> On 22 June 2011 01:28, Owen Winkler <epit...@gmail.com> wrote:
>> This weekend I will attempt to locate or write a script that moves all of >> our core Trac issues to Github, and automates the process of obtaining >> nightly archives of the source.
>> The svn repo url for core will either be shut down or redirect to the svn >> mirror on Github, through which you can check out projects from Github via >> svn as read-only. Users that use svn to update blogs should need only >> execute a simple `svn switch` to continue as they have been.
>> We're going to need time to work out what to do with the -extras repo, but >> I expect that ultimately those projects will also be available via Github. >> This will not happen this week.
>> I realize that there is still a lot of uncertainty about what using git >> and Github means. Everyone is likely to have questions, but trust me when I >> say that git is just another SCM tool. At worst, you have to learn a few >> different commands. At best, we reap great rewards from the collaborative >> coding features that Github offers, gain efficiency from the features that >> git has that aren't present in svn, and release some of our otherwise more >> prolific contributors from frequent server maintenance tasks. I firmly >> believe that this move will benefit the project.
>> Please +1 this thread if you're in support. If you still have >> reservations to the point where you can't +1 the thread, please ask >> specific, positive questions that we can help answer. We should only delay >> this process if there is a credible reason not to move the core repo before >> the weekend - let's not let bureaucracy hinder innovation.
>> I'm hoping that a couple of folks familiar with git can step up and draft >> a wiki page that outlines some of the changes from svn to git, specific to >> our project (using our URLs and likely tasks to get things moving) and link >> to some good external resources for learning git from an svn user's >> perspective.
>> Thanks, >> Owen
>> -- >> To post to this group, send email to habari-dev@googlegroups.com >> To unsubscribe from this group, send email to habari-dev-unsubscribe@** >> googlegroups.com <habari-dev-unsubscribe@googlegroups.com> >> For more options, visit this group at http://groups.google.com/** >> group/habari-dev <http://groups.google.com/group/habari-dev>
> -- > To post to this group, send email to habari-dev@googlegroups.com > To unsubscribe from this group, send email to > habari-dev-unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/habari-dev
> On 22 June 2011 01:28, Owen Winkler <epit...@gmail.com> wrote:
>> This weekend I will attempt to locate or write a script that moves all of >> our core Trac issues to Github, and automates the process of obtaining >> nightly archives of the source.
>> The svn repo url for core will either be shut down or redirect to the svn >> mirror on Github, through which you can check out projects from Github via >> svn as read-only. Users that use svn to update blogs should need only >> execute a simple `svn switch` to continue as they have been.
>> We're going to need time to work out what to do with the -extras repo, but >> I expect that ultimately those projects will also be available via Github. >> This will not happen this week.
>> I realize that there is still a lot of uncertainty about what using git >> and Github means. Everyone is likely to have questions, but trust me when I >> say that git is just another SCM tool. At worst, you have to learn a few >> different commands. At best, we reap great rewards from the collaborative >> coding features that Github offers, gain efficiency from the features that >> git has that aren't present in svn, and release some of our otherwise more >> prolific contributors from frequent server maintenance tasks. I firmly >> believe that this move will benefit the project.
>> Please +1 this thread if you're in support. If you still have >> reservations to the point where you can't +1 the thread, please ask >> specific, positive questions that we can help answer. We should only delay >> this process if there is a credible reason not to move the core repo before >> the weekend - let's not let bureaucracy hinder innovation.
>> I'm hoping that a couple of folks familiar with git can step up and draft >> a wiki page that outlines some of the changes from svn to git, specific to >> our project (using our URLs and likely tasks to get things moving) and link >> to some good external resources for learning git from an svn user's >> perspective.
>> Thanks, >> Owen
>> -- >> To post to this group, send email to habari-dev@googlegroups.com >> To unsubscribe from this group, send email to habari-dev-unsubscribe@** >> googlegroups.com <habari-dev-unsubscribe@googlegroups.com> >> For more options, visit this group at http://groups.google.com/** >> group/habari-dev <http://groups.google.com/group/habari-dev>
Ali B. wrote: > 2) Super nice if we can manage to map svn user to github users:
We just need the Github username and email address they registered with for anyone who wants their commits to be mapped. The email in particular is a real pain...
On 22 June 2011 15:24, Chris Meller <ch...@doesnthaveone.com> wrote:
> The email in particular is a real pain...
> If you mean because you can't tell which email they used to register, then
of course I agree. Which is why I'm now thinking that we should be adding a table to that switch-to-github wiki page for committers who WANT to have their account mapped to put in their github "Name <email>" combination, otherwise we just don't map them. Sounds like the easiest option to me.
We should also announce that table to -private just in case.
On 22 June 2011 16:55, Ali B. <dmond...@gmail.com> wrote:
> On 22 June 2011 15:24, Chris Meller <ch...@doesnthaveone.com> wrote: > Which is why I'm now thinking that we should be adding a > table to that switch-to-github wiki page for committers who WANT to have > their account mapped to put in their github "Name <email>" combination, > otherwise we just don't map them.
Sorry I've had the move to github section in your user page [1] confused with a full page :) We'll need to setup something then, I'll do that when I get home unless someone does it before me.
> On 22 June 2011 16:55, Ali B. <dmond...@gmail.com> wrote:
> > On 22 June 2011 15:24, Chris Meller <ch...@doesnthaveone.com> wrote: > > Which is why I'm now thinking that we should be adding a > > table to that switch-to-github wiki page for committers who WANT to have > > their account mapped to put in their github "Name <email>" combination, > > otherwise we just don't map them.
> -- > To post to this group, send email to habari-dev@googlegroups.com > To unsubscribe from this group, send email to > habari-dev-unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/habari-dev
and added a table of committers that I know have github accounts. Add your email address if you want it linked. Add your details if I don't know you have a github account.
> > -- > > knowledge has no owner, only means to reveal itself
> > On Tuesday 21 June 2011 21:34:29 cga wrote:
> > > hi all,
> > > I'm cga and I'm trying to help with pgsql related stuff. > > > my contribution will be litlle but as much as i can do.
> > > I use git/github for my personal code projects and I find the former a great SCM and the latter it a great service.
> > > so it is +1 for me.
> > > regarding the wiki for the move, I think that some documents have been already written and that they might be good too.
> > > for sure there are loads of references and cheatcodes on how to do basics with git.
> > > right now I have no time to look for them, may be tomorrow I can help more.
> > > cheers
> -- > To post to this group, send email to habari-dev@googlegroups.com (mailto:habari-dev@googlegroups.com) > To unsubscribe from this group, send email to habari-dev-unsubscribe@googlegroups.com (mailto:habari-dev-unsubscribe@googlegroups.com) > For more options, visit this group at http://groups.google.com/group/habari-dev
On 22 June 2011 01:28, Owen Winkler <epit...@gmail.com> wrote:
> This weekend I will attempt to locate or write a script that moves all of > our core Trac issues to Github, and automates the process of obtaining > nightly archives of the source.
To start the discussion of how we should lay things out on Github, I suggest we have a Habari repository, what we distribute, and a HabariDev (or something) repository that has things like tests, scripts and design documents that we now have in svn, and includes the Habari repo as a submodule. I've written that here:
