incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yohei Shimomae <>
Subject Re: Cordova Website
Date Tue, 14 Feb 2012 00:39:28 GMT
Hey everyone,

So Michael has been pretty busy with client project and I was wondering if anyone else would
like to take a stab at writing up the content.

I'm looking for the content to go into the "Want to Contribute?" (
section explaining how one can get involved in Apache Cordova. Ideally description would be
less than 3 paragraphs. I don't fully understand the contribution process so it would be nice
to have it written by someone who has better insight on these.


On 2012-01-31, at 10:37 AM, Michael Brooks wrote:

Awesome work Yohei! I'd be happy to sit down with you (and anyone else) to
write up the content.

I agree with Brian, keep it simple and separate. In the longer-term, it
would be nice to see the site running from a Git repository instead of SVN
- for consistency and pushing along the Git infrastructure experiment.


On Tue, Jan 31, 2012 at 10:27 AM, Brian LeRoux <<>>

I say we go w/ your first option Patrick. Its not going to be under
heavy dev by many folk anyhow.

On Tue, Jan 31, 2012 at 8:17 AM, Patrick Mueller <<>>
On Tue, Jan 31, 2012 at 09:36, Yohei Shimomae <<>>

So here is a preview of the site:

Nice!  Love that it's a single page.

I've temporary put the codebase up on but we should setup a
repo for that under apache-cordova and move everything there.

It appears we can edit the content by editing
cordova-website/www/template.html and then re-gen'ing.  Nice.

It turns out, we already have a "repo" for the main web site - it's an
repo though [1][2].  So, here are some options, sorted in increasing
of pain (my opinion):

- commit your code to the SVN repo; presumably we'd essentially nullify
"build" that's going on with whatever templating they're currently using.
We'd be committing the actual, final, genned files into the SVN repo,
then publishing that.  Not sure how to nullify the "build", but shouldn't
be difficult.

- move your code to a new Apache Git repo, or maybe put it in the docs
repo; I think I'd prefer to reuse docs instead of creating a new one.
we want to update the main site, we "build" the site into the checked out
SVN repo, then check in the SVN bits.  Still need to figure out how to
nullify the "build".

- get SVN completely out of the picture - the problem is that I have no
idea how to do this; the "front page" staging and publishing story looks
non-trivial to me; not clear how we could have it work off a Git repo
instead of SVN, have it do our build, etc.  Maybe it's trivial, maybe
unpossible; I have no idea.

I'd be happy to figure out the staging and publishing steps for the first
two options.  I don't have the time or patience for the third option.


Patrick Mueller

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message