[OH-Dev] calagator work on github

[Chris Sims]

Thanks, I tried to emulate the main site.

As far as the whole github conversation is concerned, the branch is on
github because calagator is on there, and it's what I use, but no other
reason.  To be honest, it would probably be best to package the openhatch
theme as a separate entity.  My work is contained in one (new) folder, along
with copying over the favicon, and adding a single text file with the theme
name in it.

I'm cleaning out the repo and consolidating the changes into one commit for
clarity's sake, since there's quite a few garbage commits and reverts due to
trying to get it to work on heroku.  There's only one watcher at the moment
- tehviking, but the repo will be removed, and a new fork created with the
same name, so links should still work just fine.

What about just keeping the theme as a patch?  That way, you could just
clone the latest calagator, apply the patch, and be ready to roll with the
new theme.  We could keep the patch in something like a gist?
--Chris


On Tue, Aug 9, 2011 at 12:27 AM, Asheesh Laroia <asheesh at asheesh.org> wrote:

> On Mon, 8 Aug 2011, Chris Sims wrote:
>
>  Just a quick note about what I've done on the fork - it's all just
>> changing the design.  I only had a day or two to look at it, and I don't
>> know enough about ruby yet to really dive into the current work being done
>> moving it to rails 3.
>>
>> The fork was created before they started the rails_3 branch.
>>
>
> Your branch looks great. It's kind of remarkable how great it looks.


>
>  I'm more than willing to add collaborators on the repo if that's what we
>> want to use, just let me know.  I will work on pulling in the rails_3
>> branch.
>>
>
> Pulling in the rails_3 branch seems great!
>
> <rambling topic="github">
> You said, "if that's what we want to use" -- I'm kind of torn on the
> process.
>
> On one hand, I like our git workflow involving sending format-patch files
> around by email. I don't really like the 'git merge' command. Our code is on
> Gitorious, not Github. I lik that we don't require OpenHatch contributors to
> have a Github account.
>
> On the other hand, if we base our Calagator work off the upstream
> Calagator, we should probably use the same workflow as they use.
>
> For now, more collaborators on your personal Github repo seems like a good
> plan. In the future, maybe we should also copy the main repository onto
> Github, and keep Gitorious and Github in sync, and create an OpenHatch group
> on Github?
> </rambling>
>
> Also, to make things easier for us, I wonder if we can get Calagator to
> accept our OpenHatch theme as part of upstream. (or if there's an easy way
> to modify just the theme, so we don't have to modify the main codebase)
> Chris, do you think they might do that?
>
> -- Asheesh.
>
> ______________________________**_________________
> Devel mailing list
> Devel at lists.openhatch.org
> http://lists.openhatch.org/**mailman/listinfo/devel<http://lists.openhatch.org/mailman/listinfo/devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/devel/attachments/20110809/917956f4/attachment.html>