On Mar 6, 2010, at 4:47 PM, Noah Slater wrote:
On 7 Mar 2010, at 00:38, Mikeal Rogers wrote:
We can provide the same providence and copyright assurances outside of
JIRA. It's a checkbox, it's not hard.
I agree. I don't want to be misunderstood as fighting against the initiative
of
On Mar 7, 2010, at 3:11 AM, J Chris Anderson wrote:
On Mar 6, 2010, at 4:47 PM, Noah Slater wrote:
On 7 Mar 2010, at 00:38, Mikeal Rogers wrote:
We can provide the same providence and copyright assurances outside of
JIRA. It's a checkbox, it's not hard.
I agree. I don't want to
On 6 Mar 2010, at 00:27, J Chris Anderson wrote:
Someone set us up the Couch!
Move every Futon!
On 05.03.2010, at 21:08, Noah Slater wrote:
This should be on dev@ I think, so moving there.
Please remove user@ from the address in your replies to this message.
On 5 Mar 2010, at 19:36, Sebastian Cohnen wrote:
but back to topic: MoinMoin sucks! It's unbelievably slow, throws 500s all
On 6 Mar 2010, at 15:54, Sebastian Cohnen wrote:
I think you misunderstood me on this point. I didn't want to suggest making
Github the new place for official documentation. I see git(hub) more like a
working platform. Static HTML export could be placed on
couchdb.apache.org/docs or where
On 06.03.2010, at 17:23, Noah Slater wrote:
On 6 Mar 2010, at 15:54, Sebastian Cohnen wrote:
I think you misunderstood me on this point. I didn't want to suggest making
Github the new place for official documentation. I see git(hub) more like
a working platform. Static HTML export could
On 6 Mar 2010, at 08:23, Noah Slater wrote:
On 6 Mar 2010, at 15:54, Sebastian Cohnen wrote:
I think you misunderstood me on this point. I didn't want to suggest making
Github the new place for official documentation. I see git(hub) more like
a working platform. Static HTML export
hmm, I personally like markdown. It's simple to read/write and easy to parse.
Writing HTML is much more painful and without strict conventions you get very
messy code.
+1 on markdown. I find writing docs in markdown to push to github from emacs
very productive. With markdown you only
On 6 Mar 2010, at 16:48, Jan Lehnardt wrote:
That cannot happen. The official site is kept in ASF Subversion.
This is orthogonal to the rest of the proposal.
No it's not.
The main site has to be from Subversion, and any additions or merges to
Subversion have to be provided by someone who
On 6 Mar 2010, at 17:20, Robert Dionne wrote:
+1 on markdown. I find writing docs in markdown to push to github from emacs
very productive.
It also introduces a generation step.
Static HTML files can be served up without any need to process them.
With markdown you only have to remember
On Sat, Mar 6, 2010 at 4:54 PM, Sebastian Cohnen
sebastiancoh...@googlemail.com wrote:
On 05.03.2010, at 21:08, Noah Slater wrote:
This should be on dev@ I think, so moving there.
Please remove user@ from the address in your replies to this message.
On 5 Mar 2010, at 19:36, Sebastian
On 6 Mar 2010, at 09:22, Noah Slater wrote:
On 6 Mar 2010, at 16:48, Jan Lehnardt wrote:
That cannot happen. The official site is kept in ASF Subversion.
This is orthogonal to the rest of the proposal.
No it's not.
The main site has to be from Subversion, and any additions or
On 6 Mar 2010, at 09:26, Noah Slater wrote:
On 6 Mar 2010, at 17:20, Robert Dionne wrote:
+1 on markdown. I find writing docs in markdown to push to github from emacs
very productive.
It also introduces a generation step.
Static HTML files can be served up without any need to
On 06.03.2010, at 18:22, Noah Slater wrote:
On 6 Mar 2010, at 16:48, Jan Lehnardt wrote:
That cannot happen. The official site is kept in ASF Subversion.
This is orthogonal to the rest of the proposal.
No it's not.
The main site has to be from Subversion, and any additions or merges
On 6 Mar 2010, at 18:51, Sebastian Cohnen wrote:
Where is the copyright agreement in the current wiki? Must have missed that...
Noah, what would your suggestions be for improve the wiki/documentation?
They would be far too huge for me to write up at the moment. :)
I have been thinking
If the point is to replace the wiki then it needs to be *easier* than
the wiki for people who aren't committers.
The big advantage to markdown is that you can parse it to HTML in a
strict mode that will escape any HTML in the original text makeing it
a lot easier to take contributions from people
On Sat, Mar 6, 2010 at 12:22 PM, Noah Slater nsla...@tumbolia.org wrote:
On 6 Mar 2010, at 16:48, Jan Lehnardt wrote:
That cannot happen. The official site is kept in ASF Subversion.
This is orthogonal to the rest of the proposal.
No it's not.
The main site has to be from Subversion, and
Oh, technically we could. The issue here is social and organisational.
On 6 Mar 2010, at 23:35, Paul Davis wrote:
On Sat, Mar 6, 2010 at 12:22 PM, Noah Slater nsla...@tumbolia.org wrote:
On 6 Mar 2010, at 16:48, Jan Lehnardt wrote:
That cannot happen. The official site is kept in ASF
I think for social and community reasons requiring the same process
for doc changes as we do for code contributions is a huge barrier to
documentation contributions.
On Sat, Mar 6, 2010 at 4:11 PM, Noah Slater nsla...@tumbolia.org wrote:
Oh, technically we could. The issue here is social and
Why? It's not about process per se, it's about providence and copyright
assurances.
On 7 Mar 2010, at 00:24, Mikeal Rogers wrote:
I think for social and community reasons requiring the same process
for doc changes as we do for code contributions is a huge barrier to
documentation
Because we hope that people who don't write code and don't know how to
generate diffs and use JIRA contribute to our documentation.
We can provide the same providence and copyright assurances outside of
JIRA. It's a checkbox, it's not hard.
-Mikeal
On Sat, Mar 6, 2010 at 4:29 PM, Noah Slater
On 7 Mar 2010, at 00:38, Mikeal Rogers wrote:
We can provide the same providence and copyright assurances outside of
JIRA. It's a checkbox, it's not hard.
I agree. I don't want to be misunderstood as fighting against the initiative of
improving our documentation. I just want to make sure we
Just wanted to put in another +1 for native Markdown support in whatever
solution we choose.
Adam
Hi folks,
lately I tried to improve various areas in the CouchDB Wiki. My list is getting
bigger and bigger and everyone will agree with me, that there is still a lot of
work to do. So, I'm sorry devs, you will be asked a lot of questions in the
next days and weeks ;)
but back to topic:
This should be on dev@ I think, so moving there.
Please remove user@ from the address in your replies to this message.
On 5 Mar 2010, at 19:36, Sebastian Cohnen wrote:
but back to topic: MoinMoin sucks! It's unbelievably slow, throws 500s all
the time and don't forget the syntax - pure hell
On 5 Mar 2010, at 20:15, Dirkjan Ochtman wrote:
I don't think Markdown or reST (which Sphinx uses) are fundamentally better
than the wiki markup.
The only two things any plain text HTML syntax adds are:
* An enforced set of elements a user can add
* Significant newlines
The
On Fri, Mar 5, 2010 at 3:08 PM, Noah Slater nsla...@tumbolia.org wrote:
This should be on dev@ I think, so moving there.
Please remove user@ from the address in your replies to this message.
On 5 Mar 2010, at 19:36, Sebastian Cohnen wrote:
but back to topic: MoinMoin sucks! It's
On Fri, Mar 5, 2010 at 21:34, Paul Davis paul.joseph.da...@gmail.com wrote:
To me, official isn't really that important. If a group comes along
and writes better documentation than the wiki, are we going to tell
people that they can't read them?
Surely better is better, but in the general
On 5 Mar 2010, at 20:34, Paul Davis wrote:
To me, official isn't really that important. If a group comes along
and writes better documentation than the wiki, are we going to tell
people that they can't read them?
To you, sure.
I want to make sure everyone knows what they're getting into
On Fri, Mar 5, 2010 at 3:37 PM, Dirkjan Ochtman djc.ocht...@gmail.com wrote:
On Fri, Mar 5, 2010 at 21:34, Paul Davis paul.joseph.da...@gmail.com wrote:
To me, official isn't really that important. If a group comes along
and writes better documentation than the wiki, are we going to tell
Le 05/03/10 21:42, Noah Slater a écrit :
I would like to work WITH the ASF, and not against them, where possible.
I agree as ASF is your sponsor.
If the issue is just MoinMoin and as I think that couchdb.apache.org is
plain html (or is there a CMS behind it ?), what about couchdb core dev
I'm +1 on dogfooding a couchapp doc site.
Last week Greg Stein mentioned something about a space that you can
get at apache.
Basically you get a box or VM or something that is part of apache
infrastructure but the apache infra people don't maintain it, the
people in your project do, so you can
On 5 Mar 2010, at 15:44, Mikeal Rogers wrote:
I'm +1 on dogfooding a couchapp doc site.
Last week Greg Stein mentioned something about a space that you can
get at apache.
Basically you get a box or VM or something that is part of apache
infrastructure but the apache infra people don't
On Mar 5, 2010, at 4:25 PM, Jan Lehnardt wrote:
On 5 Mar 2010, at 15:44, Mikeal Rogers wrote:
I'm +1 on dogfooding a couchapp doc site.
Last week Greg Stein mentioned something about a space that you can
get at apache.
Basically you get a box or VM or something that is part of
Hi,
I agree that the current wiki is a blocker for better documentation
but I'm not saying we should write software to replace
wiki.apache.org/couchdb.
I like the idea of writing Markdown in Github. HTML would work
for me, but Markdown is a little easier to write (for me) and using
the Github
35 matches
Mail list logo
