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 habar...@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
--
To post to this group, send email to habar...@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
Rich Bowen
June 21, 2011 2:23 PM
Owen Winkler
June 21, 2011 10:28 AM
Please +1 this thread if you're in support.
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
--
knowledge has no owner, only means to reveal itself
+1
--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari
Please +1 this thread if you're in support.
Thanks,
Owen
--
To post to this group, send email to habar...@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
To unsubscribe from this group, send email to habari-dev-...@googlegroups.com
For more options, visit this group at 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...
The email in particular is a real pain...
Which wiki page?
--
To post to this group, send email to habar...@googlegroups.com
To unsubscribe from this group, send email to habari-dev-...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/habari-dev
Ah, no worries, thought I might be missing something.
I've moved it to here:
http://wiki.habariproject.org/en/Habari_on_github
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.
as promised yesterday, here I link some site/tut/guide/references.
Since the web it's full of them, I just link you to the official (and imho better) resources and leave you the choice to search for more.
git official site: http://git-scm.com/
git reference from who comes from svn: http://git-scm.com/course/svn.html
git ready (a ver good git resource: http://gitready.com/
git ready's svn ref: http://gitready.com/beginner/2009/02/04/converting-from-svn.html
git vs svn comparision: (PARENTAL ADVISORY: my dick il larger than yours kind of approach) https://git.wiki.kernel.org/index.php/GitSvnComparison
and of course github and git reference resources:
cheers.
--
knowledge has no owner, only means to reveal itself
I had very quick "vertical scrolling read" of the ebook, it looks really interesting.
thank you.
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:
http://wiki.habariproject.org/en/Habari_on_github#Habari_repositories_on_Github
Thanks,
Ali
On 23/06/2011, at 6:19 PM, "Michael C. Harris"
<mic...@twofishcreative.com> wrote:
I think that would make things more difficult for the general user,
more difficult for us to maintain, and provide no real advantage to
users familiar with git.
You should fork Habari and develop and version your user directory as
normal. Then set the official repo as a remote and update as required.
--
You should fork Habari and develop and version your user directory as
normal. Then set the official repo as a remote and update as required.
It would be very helpful if the devs who are familiar with Git could provide a sample workflow on the wiki for doing some basic tasks.
Also, there's not actually a link to the official Habari project on Github from that page.
That's definitely the plan. The move to git and Github is very much a
work in progress, and the page you mentioned is mostly crap that was
on my user page. By the end of next week, the page will be much better
:)
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 habar...@googlegroups.com
To unsubscribe from this group, send email to habari-dev-unsubscribe@googlegroups.com
The wiki is definitely a work in progress. Is there something in
particular you'd like to see? We're going to have a code sprint next
weekend and improving the github/git docs will be a priority.
--
No, you don't have to use GitHub, but:
1) We want to be rid of Trac because that's where our maintenance
headaches are. We can only do that if we have a replacement, and GitHub
provides one that integrates well with git and doesn't require
maintenance on our part.
2) Providing patches through an issue tracker is ok, but GitHub's pull
requests streamline the process and make it easier for people to
contribute, which is a better way to encourage project collaboration.
Owen
--
To post to this group, send email to habar...@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