Andreas Kuckartz wrote:
Look at http://wiki.apache.org/cocoon/CocoonDocumentationSystem and find all
my
requirements. I'm sure that all six options are good enough but as *I* have
to
do it, I'll take the road that's the fastest for *me*.
There was a misunderstanding on my side. I had
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or not, but in this case
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or
Actually, and I'm not joking, I think we should have a hero plate on our
web page and put the name and have a nomination!... some ego stimulation
goes a lng way... h
Wow, employee^H^H^H^H^H^H^H^Hcommitter of the month! Now that would
feel like working at McDonald's :-)
--
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
...
tell you what. forget about it for now. Think about going dynamic and
later we'll find a way to make a persistent copy of that (either via
forrest or simply by wget or something)
+1
Forrest - pardon my rudeness - sucks as a static site
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation system.
I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Cheers,
Andreas
Andreas Kuckartz wrote:
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation system.
I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Nothing or as less as the use of
- Daisy,
- Hippo CMS (if it is really OS
Look at http://wiki.apache.org/cocoon/CocoonDocumentationSystem and find all
my
requirements. I'm sure that all six options are good enough but as *I* have to
do it, I'll take the road that's the fastest for *me*.
There was a misunderstanding on my side. I had thought that that was to be a
Andreas Kuckartz wrote:
Look at http://wiki.apache.org/cocoon/CocoonDocumentationSystem and find all
my
requirements. I'm sure that all six options are good enough but as *I* have to
do it, I'll take the road that's the fastest for *me*.
There was a misunderstanding on my side. I had thought that
On 18 Jan 2005, at 09:59, Reinhard Poetz wrote:
Andreas Kuckartz wrote:
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation
system. I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Nothing or as less as the use of
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or not, but in this case I'm not worried ;-)
-Bertrand
smime.p7s
Description:
Steven Noels wrote:
On 18 Jan 2005, at 09:59, Reinhard Poetz wrote:
Andreas Kuckartz wrote:
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation
system. I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Nothing or
On 18 Jan 2005, at 10:59, Reinhard Poetz wrote:
I'm not in the position to change the ASF policy and I don't have the
energy to lead all the necessary discussions.
Sure. Ditto here. :-)
Besides, the ASF policy is sound, if only optimized a wee bit towards
source code governance and the risk of
Steven Noels wrote:
On 18 Jan 2005, at 10:59, Reinhard Poetz wrote:
I'm not in the position to change the ASF policy and I don't have the
energy to lead all the necessary discussions.
Sure. Ditto here. :-)
Besides, the ASF policy is sound, if only optimized a wee bit towards
source code
On Sat, Jan 15, 2005 at 02:54:33PM -0500, Stefano Mazzocchi wrote:
Torsten Curdt wrote:
People, again, let's be brave and get this of this silly pure java
nonsense. the JNI connector works. Today!
...maybe for you :-/ ...maybe now
We had so many problems with subclipse under linux that
Obviously there probably would be something wrong somewhere if Apache Lenya were
used to publish the documentation of Apache Cocoon while the Apache Lenya
website is still published using different tools.
So, this is first of all a suggestion to Apache Lenya itself:
Eat own dogfood: use Lenya to
Steven Noels wrote:
On 18 Jan 2005, at 11:49, Reinhard Poetz wrote:
Steven Noels wrote:
I'm not so optimistic about a) the chance that automated SVN commit
access using role accounts will be granted, and b) whether the
technicalities of a secure webapp which is tied to the ASF web of
trust
Reinhard Poetz wrote:
Steven Noels wrote:
On 18 Jan 2005, at 10:59, Reinhard Poetz wrote:
I'm not in the position to change the ASF policy and I don't have the
energy to lead all the necessary discussions.
Sure. Ditto here. :-)
Besides, the ASF policy is sound, if only optimized a wee bit
We had so many problems with subclipse under linux that
we finally went back to the commandline! ...maybe it's
worth giving it another try. But a few months ago subclipse
with JNI was just a PITA.
Of course using JNI will result in more pain than a pure java library
and if there was such a thing,
Reinhard Poetz wrote:
...
... and if there is no other way, I have ideas to perfectly work around
the ASF infrastructure without having to forbear from online editing.
IMHO enough bike-shedding on this thread. You know what is available,
you know what you want to do. Whatever you do or choose,
On 18 Jan 2005, at 13:20, Reinhard Poetz wrote:
... and if there is no other way, I have ideas to perfectly work
around the ASF infrastructure without having to forbear from online
editing.
Fair enough.
I'm really curious though how you're going to handle authentication
(other than running the
Steven Noels wrote:
On 18 Jan 2005, at 13:20, Reinhard Poetz wrote:
... and if there is no other way, I have ideas to perfectly work
around the ASF infrastructure without having to forbear from online
editing.
Fair enough.
I'm really curious though how you're going to handle authentication
every new/modified doc has to be approved by a committer. My plan is,
that this approval is part of the online webapp.
RT
Why not simple moderation via email?
Committers could subscribe to a special closed mailing
list. The webapp send emails with diffs and a link with
a token. If anyone clicks
Stefano Mazzocchi wrote:
As for french docs, I *strongly* think that we should do this thru
content-negotiation rather than URL design. A person accessing the page
with a french browser will get the page in french, that's all they have
to know
Can you rely that each person in France will have
Torsten Curdt wrote:
every new/modified doc has to be approved by a committer. My plan is,
that this approval is part of the online webapp.
RT
Why not simple moderation via email?
Committers could subscribe to a special closed mailing
list. The webapp send emails with diffs and a link with
a
Bertrand Delacretaz wrote:
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or not, but in this case I'm not worried ;-)
+1,
Steven Noels wrote:
On 18 Jan 2005, at 10:59, Reinhard Poetz wrote:
I'm not in the position to change the ASF policy and I don't have the
energy to lead all the necessary discussions.
Sure. Ditto here. :-)
Besides, the ASF policy is sound, if only optimized a wee bit towards
source code
Torsten Curdt wrote:
We had so many problems with subclipse under linux that
we finally went back to the commandline! ...maybe it's
worth giving it another try. But a few months ago subclipse
with JNI was just a PITA.
Of course using JNI will result in more pain than a pure java library
and if
Nicola Ken Barozzi wrote:
Reinhard Poetz wrote:
...
... and if there is no other way, I have ideas to perfectly work
around the ASF infrastructure without having to forbear from online
editing.
IMHO enough bike-shedding on this thread. You know what is available,
you know what you want to do.
Reinhard Poetz wrote:
Thank you. But as you say, it depends if it is allowed that either a webapp
or a mail server is allowed to do a commit. If yes, we have many options.
With the current situation, that is a no.
Evidently there are solutions on the way.
Spurts of discussion happen on
David Crossley wrote:
Reinhard Poetz wrote:
Thank you. But as you say, it depends if it is allowed that either a webapp
or a mail server is allowed to do a commit. If yes, we have many options.
With the current situation, that is a no.
Evidently there are solutions on the way.
Spurts of
Reinhard Poetz wrote:
David Crossley wrote:
Reinhard Poetz wrote:
Yep. I hope that I can convince at least one of them to help me. Actually I
need some Java code ;-) So here I ask officially: Who volunteers to write
the Java code that communicates with the SVN repository (read and
Reinhard Poetz wrote:
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose the
architecture of a new extensible documentation system.
I am *strongly* in favor of plain html as a source, as Forrest renders
it nicely; the Incubator website is now all using html as a source format.
Nicola Ken Barozzi wrote:
Reinhard Poetz wrote:
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose
the architecture of a new extensible documentation system.
I am *strongly* in favor of plain html
I know :-)
as a source, as Forrest renders
it nicely; the Incubator website is
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
snip/
One normaly solution is to have an english title even for
non-english pages. I dislike that, it's very anglo-centric.
Well, consider the state of Cocoon, the ASF, the opensource world and
the whole IT industry: they're all anglo-centric.
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
snip/
One normaly solution is to have an english title even for
non-english pages. I dislike that, it's very anglo-centric.
Well, consider the state of Cocoon, the ASF, the opensource world and
the whole IT industry: they're
Stefano Mazzocchi wrote:
Sun did this with the Java API did this and created a mess, people
linked to java/1.4.2/ and then 1.4.3 was created and all links broke down.
If a document shipped in 2.1.3 has a bug and was fixed in 2.1.4, why
would anybody want to see it? and if 2.1.4 removed
Reinhard Poetz wrote:
Look at http://apache.org/~reinhard/cocoon/2.2/1.html. The navigational
structure is hierarchically organzied but not the files (only 1.html,
2.html and 17.html are working). I don't see the value of having the
hierarchies in the URL.
no, but I somehow agree with Sylvain
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
Sun did this with the Java API did this and created a mess, people
linked to java/1.4.2/ and then 1.4.3 was created and all links broke
down.
If a document shipped in 2.1.3 has a bug and was fixed in 2.1.4, why
would anybody want to see it? and if
On 17 Jan 2005, at 20:36, Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
Look at http://apache.org/~reinhard/cocoon/2.2/1.html. The
navigational structure is hierarchically organzied but not the files
(only 1.html, 2.html and 17.html are working). I don't see the value
of having the hierarchies
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
Sun did this with the Java API did this and created a mess, people
linked to java/1.4.2/ and then 1.4.3 was created and all links broke
down.
If a document shipped in 2.1.3 has a bug and was fixed in 2.1.4, why
would
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
snip/
Anyway, the more I think of it, the more I think it makes sense to
follow the URL model of Wikipedia.
That's probably the best solution. I will restructure the sample repositories
following the wikipedia URL model.
--
Reinhard
Reinhard Poetz wrote:
snip/
My first goal is reusing existing functionality (SVN, Forrest,
static web pages). Writing the missing pieces (a small web
application to edit docs online) shouldn't be too difficult -
especially using CocoonForms (HTMLArea with HTMLCleaning convertor
are shining
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
snip/
good point.
I also want that every comment (not only doc changes) has to be
approved by a committer. So we have a double-barrier (hope that's
understandable English) for spamming bots.
Ok, captchas + human moderation is clearly too high of a
Sylvain Wallez wrote:
Well, consider the state of Cocoon, the ASF, the opensource world and
the whole IT industry: they're all anglo-centric. Would you have the
same concerns if this was esperanto or interlingua rather than english
(or more precisely international english)?
Furthermore,
Sylvain Wallez wrote:
Ok, captchas + human moderation is clearly too high of a barrier for
spammers and even for defacers. Even infra@ would not have a problem
with that.
There's an interesting chapter on circumventing captchas at wikipedia
[1]. Are we interesting enough in terms of google
Sylvain Wallez wrote:
Reinhard Poetz wrote:
snip/
My first goal is reusing existing functionality (SVN, Forrest,
static web pages). Writing the missing pieces (a small web
application to edit docs online) shouldn't be too difficult -
especially using CocoonForms (HTMLArea with HTMLCleaning
David Crossley wrote:
Reinhard Poetz wrote:
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose the
architecture of a new extensible documentation system.
Thanks, a brilliant step.
My first goal is
reusing existing functionality (SVN, Forrest, static web pages). Writing
the
Stefano Mazzocchi wrote:
David Crossley wrote:
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Reinhard Poetz a ?crit :
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I
propose the architecture of a new extensible documentation system...
Thanks Reinhard - to me this looks really
On Sat, 15 Jan 2005 09:42:17 +0100, Reinhard Poetz [EMAIL PROTECTED] wrote:
...
My first goal is
reusing existing functionality (SVN, Forrest, static web pages). Writing
the missing pieces (a small web application to edit docs online) shouldn't
be too difficult - especially using CocoonForms
Geoff Howard wrote:
On Sat, 15 Jan 2005 09:42:17 +0100, Reinhard Poetz [EMAIL PROTECTED] wrote:
...
My first goal is
reusing existing functionality (SVN, Forrest, static web pages). Writing
the missing pieces (a small web application to edit docs online) shouldn't
be too difficult - especially
People, again, let's be brave and get this of this silly pure java
nonsense. the JNI connector works. Today!
...maybe for you :-/ ...maybe now
We had so many problems with subclipse under linux that
we finally went back to the commandline! ...maybe it's
worth giving it another try. But a few
On Sat, 15 Jan 2005 09:17:10 -0500, Geoff Howard [EMAIL PROTECTED] wrote:
- component (Java) that reads from and commits to SVN - should work over
WebDAV, shouldn't it?
I know there are some specialist in this community who could help out
here (Unico, Gianugo, Guido)
We
Torsten Curdt wrote:
People, again, let's be brave and get this of this silly pure java
nonsense. the JNI connector works. Today!
...maybe for you :-/ ...maybe now
We had so many problems with subclipse under linux that
we finally went back to the commandline! ...maybe it's
worth giving it
Le 14 janv. 05, à 08:20, Reinhard Poetz a écrit :
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose
the architecture of a new extensible documentation system...
Thanks Reinhard - to me this looks really good, and the fact that
you're backing your proposal with actual work
Bertrand Delacretaz wrote:
Le 14 janv. 05, à 08:20, Reinhard Poetz a écrit :
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose
the architecture of a new extensible documentation system...
Thanks Reinhard - to me this looks really good, and the fact that you're
backing your
Le 14 janv. 05, à 09:35, Reinhard Poetz a écrit :
...The SimpleContentModel may solve the problems where to put
resources like images (haven't had a solution up to now for this).
Thank you!
You're welcome - the SimpleContentModel is not my idea, it's Mark
Lundquist's, but I read the page and
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Reinhard Poetz a ?crit :
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose
the architecture of a new extensible documentation system...
Thanks Reinhard - to me this looks really good, and the fact that you're
Reinhard Poetz wrote:
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose the
architecture of a new extensible documentation system.
Thanks, a brilliant step.
My first goal is
reusing existing functionality (SVN, Forrest, static web pages). Writing
the missing pieces
David Crossley wrote:
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Reinhard Poetz a ?crit :
At http://wiki.apache.org/cocoon/CocoonDocumentationSystem I propose
the architecture of a new extensible documentation system...
Thanks Reinhard - to me this looks really good, and the fact that
60 matches
Mail list logo
