You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (Created) (JIRA)" <ji...@apache.org> on 2012/03/11 20:32:40 UTC
[jira] [Created] (GORA-106) Migrate Gora website documentation to
Apache CMS
Migrate Gora website documentation to Apache CMS
------------------------------------------------
Key: GORA-106
URL: https://issues.apache.org/jira/browse/GORA-106
Project: Apache Gora
Issue Type: Improvement
Components: documentation, website
Affects Versions: 0.2
Reporter: Lewis John McGibbney
Priority: Minor
Fix For: 0.3
I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
{quote}
So, right now, there's no README.
build.xml suggests I use ant, so I did
But no readme means the first ``ant'' will complain
about forrest missing, and I'll say:
Meh. All I wanted is fix a typo.
You have to make it easy for people to contribute,
and you're not!
If you're living in a happy java world, everyone will
have maven, so maven might be the way to go. If 277
packages is all I need, then so be it, but I'll already
have them installed.
I fired up this email when I started the forrest checkout
it's only done now, after 3:26.53.
Let's see what else breaks :)
AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
BUILD FAILED
/home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
I touch author, but that doesn't bring me anywhere.
Of course the error is that ant or forrest can't deal with relative paths,
so I run it again as:
igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
And it fails again, because I didn't build forrest.
By now I wonder if there's a forrest package in Fedora, but
of course there isn't. So let's build forrest.
Which in turn fails because Fedora has some weird
JAVA_HOME pointing to an OpenJDK JRE.
Back to building gora-site.
It builds in 19s and I'm impressed, or hope I have reason to be.
I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
expecting it to break horribly because it's using fixed URLs
but it works. I'm impressed. I'm also impressed by its ugly,
but that's beside the point. It works. And it only took me
30 minutes to get there.
{quote}
At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
We need to "make it easy"
* for people to contribute a small fix
* for developers to actually write docs
For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
http://www.apache.org/dev/cms
https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261912#comment-13261912 ]
Enis Soztutar commented on GORA-106:
------------------------------------
How about just using Twitter's Bootstrap. http://twitter.github.com/bootstrap/
It provides slick looking project web sites, and is very easy to use.
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Henry Saputra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259011#comment-13259011 ]
Henry Saputra commented on GORA-106:
------------------------------------
Website builder company?
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Andrew Hart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261779#comment-13261779 ]
Andrew Hart commented on GORA-106:
----------------------------------
Hey Lewis, I like it! (All except the Flash carousel ;), there are plenty of alternatives though)
If you want a hand with this, I'd be happy to help out here! How would you see things breaking down, is there something we could do in parallel?
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Lewis John McGibbney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258845#comment-13258845 ]
Lewis John McGibbney commented on GORA-106:
-------------------------------------------
I was looking for a quick and easy, yet impressive look for the new site. On my journey's I came across
http://www.templatemo.com/templates/templatemo_281_chrome/
What do you guys think?
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Lewis John McGibbney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259621#comment-13259621 ]
Lewis John McGibbney commented on GORA-106:
-------------------------------------------
Hi Henry,
All of this content will be changed to ASF and Apache Gora including the graphics :0)
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Lewis John McGibbney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262211#comment-13262211 ]
Lewis John McGibbney commented on GORA-106:
-------------------------------------------
Aye keeping it simple is the aim of the game (from my pov anyway) with this one. I'm very happy to get the gora CMS up and running.
Hi Andrew, I've been working on a patch for this, which in its current form is nothing more than a simple phasing of html to markdown, so if you give me until tomorrow then I'll upload what I've got OK... and yeah it would be great if we could work on this together.
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Andrew Hart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262001#comment-13262001 ]
Andrew Hart commented on GORA-106:
----------------------------------
Big +1 for using Bootstrap! The flexibility is incredible. And, if you're turned off by the millions of similar-looking bootstrap sites, sites like http://lavishbootstrap.com make it dead simple to quickly customize the stock Bootstrap CSS.
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Lewis John McGibbney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney updated GORA-106:
--------------------------------------
Attachment: GORA-106.patch
Hi Andrew. OK this is the patch I was talking about. As you'll see it's a WIP and needs ALOT of work.
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
> Attachments: GORA-106.patch
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-106) Migrate Gora website documentation to
Apache CMS
Posted by "Lewis John McGibbney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266767#comment-13266767 ]
Lewis John McGibbney commented on GORA-106:
-------------------------------------------
OK troops, managed to locate some nice time saving resources for us to use to map the legacy forrest xdoc's to markdown.
https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/
In particular the xslt written by Sam Ruby
https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/anakia2markdown.xslt
> Migrate Gora website documentation to Apache CMS
> ------------------------------------------------
>
> Key: GORA-106
> URL: https://issues.apache.org/jira/browse/GORA-106
> Project: Apache Gora
> Issue Type: Improvement
> Components: documentation, website
> Affects Versions: 0.2
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.3
>
> Attachments: GORA-106.patch
>
>
> I know in the past we've discussed the pro's and con's of the website etc. However, currently it is a bit of a pain to actually edit/update, build and commit/publish web content. This is a pain for committers never-mind any newer Gora users who may just wish to contribute documentation in a pain/hassle free manner. To illustrate this point I've pasted a conversation with a pro-Apache CMS ASF guy, whom I asked to look into the Gora documentation.
> {quote}
> So, right now, there's no README.
> build.xml suggests I use ant, so I did
> But no readme means the first ``ant'' will complain
> about forrest missing, and I'll say:
> Meh. All I wanted is fix a typo.
> You have to make it easy for people to contribute,
> and you're not!
> If you're living in a happy java world, everyone will
> have maven, so maven might be the way to go. If 277
> packages is all I need, then so be it, but I'll already
> have them installed.
> I fired up this email when I started the forrest checkout
> it's only done now, after 3:26.53.
> Let's see what else breaks :)
> AN EXCEPTION! And a backtrace! OH I LOVE THOSE!
> BUILD FAILED
> /home/igalic/src/asf/gora-site/build.xml:27: Execute failed: java.io.IOException: Cannot run program "../forrest/bin/forrest" (in directory "/home/igalic/src/asf/gora-site/author"): java.io.IOException: error=2, No such file or directory
> I touch author, but that doesn't bring me anywhere.
> Of course the error is that ant or forrest can't deal with relative paths,
> so I run it again as:
> igalic@tynix ~/src/asf/gora-site (svn)-[site:1240598] % ant -Dforrest.home=$( readlink -f ../forrest)
> And it fails again, because I didn't build forrest.
> By now I wonder if there's a forrest package in Fedora, but
> of course there isn't. So let's build forrest.
> Which in turn fails because Fedora has some weird
> JAVA_HOME pointing to an OpenJDK JRE.
> Back to building gora-site.
> It builds in 19s and I'm impressed, or hope I have reason to be.
> I go in my browser to /home/igalic/src/asf/gora-site/author/build/site
> expecting it to break horribly because it's using fixed URLs
> but it works. I'm impressed. I'm also impressed by its ugly,
> but that's beside the point. It works. And it only took me
> 30 minutes to get there.
> {quote}
> At this stage I let out a long sigh, and thought that it was about time to open this issue, taking the following into account.
> We need to "make it easy"
> * for people to contribute a small fix
> * for developers to actually write docs
> For the latter it should be in a form and a format they are used to, something that doesn't break their habits. If anyone has the habit of writing stuff down in notepad then markdown might be ideal... therefore we arrive @ APACHE CMS.
> http://www.apache.org/dev/cms
> https://blogs.apache.org/infra/entry/the_asf_cms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira