Le 27 mai 05, à 03:24, Antonio Gallardo a écrit :
...If I becomes the root of our zone,
then I will be glad to provide all the necessary support to materialize
this effort...
Great, thanks!
I've not used solaris yet but I've worked with many different unixes,
if you can give me access I
1- Current released version
2- Daily SVN 2.1.x
3- Daily SVN 2.2.x..
Good idea, but I'm not sure if we want to have three versions there,
maybe we should start with the release and go from there?
YES! YES! YES!
I mean: good idea to start with the current released version and go from
On May 25, 2005, at 8:49 AM, Linden H van der (MI) wrote:
Well, since there are no rules for documentation right now, everyone
wanting to write documentation is free to use whatever tool they like.
Sorry, but I haven't seen (apart from Upayavira and Ralph) anyone
posting here's some
On May 26, 2005, at 1:00 PM, Ross Gardler wrote:
Glen Ezkovich wrote:
Since documentation is best gathered in a CMS, because there
will likely
(hopefully) be more than one person working on it, this
inevitably means
that everyone should use THAT CMS to avoid scattering
documentation
On May 26, 2005, at 3:05 PM, Linden H van der (MI) wrote:
Glen and Ross,
Before duplicating my thoughts in similar replies I want to state this
(replies in random order):
I work in a university department, doing research, so I'm fully aware
what it takes to go through the process of putting
On 27 May 2005, at 03:24, Antonio Gallardo wrote:
I believe, I am reading this mail with a time delay. What is clear to
me
is that I don't received a root password of the cocoon Solaris zone.
And I
don't know if the zone is already up. If I becomes the root of our
zone,
then I will be glad
Glen Ezkovich wrote:
...
I'm tired of the discussion about tool vs. people. We need people to
write docs, we need tools to help them write docs.
It is not an either or argument, why are people so polarised?
I don't think we're polarized. I just think we each emphasis different
Le 27 mai 05, à 14:47, Steven Noels a écrit :
...People interested in co-administering Daisy (users, creation of
variants, ACL rules, sites): please stand up...
I haven't used Daisy seriously yet, but if it's small things here and
there you can count me in.
-Bertrand
smime.p7s
Le 27 mai 05, à 14:47, Steven Noels a écrit :
...People interested in co-administering Daisy (users, creation of
variants, ACL rules, sites): please stand up...
My coworker and local Daisy expert, Patrick Ahles, agrees with helping out in
user-administration provided it requires a limited
Bertrand Delacretaz wrote:
Le 27 mai 05, à 14:47, Steven Noels a écrit :
...People interested in co-administering Daisy (users, creation of
variants, ACL rules, sites): please stand up...
I haven't used Daisy seriously yet, but if it's small things here and
there you can count me in.
I'm
On 24 May 2005, at 22:42, Upayavira wrote:
If someone else can offer an existing CMS that has the features they
need, and can be installed and operational within a reasonable amount
of time, then we'd be asking different questions.
I'm at a conference this week, so e-mail access is erratic.
Le 26 mai 05, à 15:35, Steven Noels a écrit :
...That said, next week I'll be back, and if we have our Solaris zone
set up and I have access to it (Antonio?), I'll set up MySQL 4.1 +
Daisy 1.3M2 on that zone...
Cool. I cannot help ATM but this sounds good.
...I wouldn't bother too much with
Bertrand Delacretaz wrote:
Le 26 mai 05, à 15:35, Steven Noels a écrit :
...That said, next week I'll be back, and if we have our Solaris zone
set up and I have access to it (Antonio?), I'll set up MySQL 4.1 +
Daisy 1.3M2 on that zone...
Cool. I cannot help ATM but this sounds good.
+1
Steven Noels wrote:
On 24 May 2005, at 22:42, Upayavira wrote:
If someone else can offer an existing CMS that has the features they
need, and can be installed and operational within a reasonable amount
of time, then we'd be asking different questions.
I'm at a conference this week, so
Helma,
I don't want to discourage the effort to create a or deploy a Cocoon
based CMS. I think its important that it gets done. My point is that
no mater how easy and automated the process becomes, good
documentation requires a great deal of human collaborative effort.
On May 25, 2005,
Glen Ezkovich wrote:
Since documentation is best gathered in a CMS, because there will likely
(hopefully) be more than one person working on it, this inevitably means
that everyone should use THAT CMS to avoid scattering documentation all
over the place (wiki, website, mailing list, blogs,
-Original Message-
From: Glen Ezkovich [mailto:[EMAIL PROTECTED]
Sent: Thursday, 26 May 2005 19:06
To: dev@cocoon.apache.org
Subject: Re: Planet Cocoon license and reuse of docs
Helma,
I don't want to discourage the effort to create a or deploy a Cocoon
based CMS. I think its
On Jue, 26 de Mayo de 2005, 8:35, Steven Noels dijo:
On 24 May 2005, at 22:42, Upayavira wrote:
If someone else can offer an existing CMS that has the features they
need, and can be installed and operational within a reasonable amount
of time, then we'd be asking different questions.
I'm at
On May 26, 2005, at 3:05 PM, Linden H van der (MI) wrote:
Glen and Ross,
Before duplicating my thoughts in similar replies I want to state this
(replies in random order):
I work in a university department, doing research, so I'm fully aware
what it takes to go through the process of putting
-
From: Ross Gardler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 25 May, 2005 01:11
To: dev@cocoon.apache.org
Subject: Re: Planet Cocoon license and reuse of docs
Upayavira wrote:
Antonio Gallardo wrote:
...
With the new apache zones, I think there is posible in a rasonable
Gardler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 25 May, 2005 01:11
To: dev@cocoon.apache.org
Subject: Re: Planet Cocoon license and reuse of docs
Upayavira wrote:
Antonio Gallardo wrote:
...
With the new apache zones, I think there is posible in a rasonable
amount of time
I think that they are many people around here that can do the
dirty job to create well formed files (xml, xhtml, etc) but
few that can write documentation.
Well, I think you might be wrong there in the numbers. I've seen a post,
at least once, where someone writes something like I'd like to
On May 25, 2005, at 4:40 AM, Linden H van der (MI) wrote:
Let me propose an entirely different strategy:
- pick a tool, any tool that meets the criteria I mentioned above and
start a new set of documentation there. I suggest Daisy.
What you should be concerned about is managing new and
Hi everyone,
As someone who has written a fair amount of both code and
documentation I would just like to make a few comments. First, I
applaud your effort to manage Cocoon's documentation with a Cocoon
based CMS. I'm sure the Lenya and Daisy proponents will chime in
shortly with offers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefano Mazzocchi wrote:
Unico Hommes wrote:
BTW. Where *is* Linotype? I found this
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=110705988801725w=2 but
looking at http://simile.mit.edu/ I can't seem to find it. Linotype in
the 2.1 branch
- pick a tool, any tool that meets the criteria I mentioned
above and
start a new set of documentation there. I suggest Daisy.
What you should be concerned about is managing new and existing
content. This includes some process for accepting vetting, editing/
correcting and
even a simple text editor. The one thing I have learned over the
years is that using the correct tool for the job makes the job
True.
Third, Cocoon's documentation is not as bad as people think. I was
able to put together a fairly complex e-commerce site that included
custom
On Mie, 25 de Mayo de 2005, 8:49, Linden H van der (MI) dijo:
I do agree with your arguments but what you propose means we need a
setup that could pass for a publisher's office. This community has no
means to set up something like this and AFAIK no members that can do the
job. So, let's work
Hi Ross,
On 24 May 2005, at 00:48, Ross Gardler wrote:
I can't find any copyright or license information on the planetcocoon
site. Can you please point me at the relevant page.
I'm concerned as much of the documentation content appears to be
direct duplicates of materials in Cocoons
Sebastien Arbogast wrote:
2005/5/23, Ross Gardler [EMAIL PROTECTED]:
I can't find any copyright or license information on the planetcocoon
site. Can you please point me at the relevant page.
Actually so far there is no such thing. As it is said in our
disclaimer, Planet Cocoon is an
Mark Leicester wrote:
I want to resolve the
licensing issues ASAP. With the ASF license, am I correct in thinking
that I need to simply attribute the documentation to Apache, noting
changes as necessary? What would be a suitable wording? This document
is derived from, and contains portions of
Le 24 mai 05, à 11:36, Ross Gardler a écrit :
...For example:
http://www.planetcocoon.com/node/1209
is
http://cocoon.apache.org/2.1/tutorial/tutorial-generator.html
Which I find very disappointing: I fail to see the point of copying
content from our docs on other websites.
If the goal
Hello Bertrand,
On 24 May 2005, at 12:20, Bertrand Delacretaz wrote:
Le 24 mai 05, à 11:36, Ross Gardler a écrit :
...For example:
http://www.planetcocoon.com/node/1209
is
http://cocoon.apache.org/2.1/tutorial/tutorial-generator.html
Which I find very disappointing: I fail to see the
Mark Leicester wrote:
Hello Bertrand,
On 24 May 2005, at 12:20, Bertrand Delacretaz wrote:
Le 24 mai 05, à 11:36, Ross Gardler a écrit :
...For example:
http://www.planetcocoon.com/node/1209
is
http://cocoon.apache.org/2.1/tutorial/tutorial-generator.html
Which I find very
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
Mark Leicester wrote:
Hello Bertrand,
On 24 May 2005, at 12:20, Bertrand Delacretaz wrote:
Le 24 mai 05, à 11:36, Ross Gardler a écrit :
...For example:
http://www.planetcocoon.com/node/1209
is
Sebastien Arbogast wrote:
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
Mark Leicester wrote:
Hello Bertrand,
On 24 May 2005, at 12:20, Bertrand Delacretaz wrote:
Le 24 mai 05, à 11:36, Ross Gardler a écrit :
...For example:
http://www.planetcocoon.com/node/1209
is
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
Sebastien Arbogast wrote:
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
Mark Leicester wrote:
Hello Bertrand,
On 24 May 2005, at 12:20, Bertrand Delacretaz wrote:
Le 24 mai 05, à 11:36, Ross Gardler a écrit :
...For example:
Hi Ross,
Thank you very much for you offer, and for your interest in helping us
achieve our goals. I shall renew my membership of the Forrest mailing
list and we can continue this potentially very fruitful discussion
there. Sébastien, it sounds like Ross is more than willing to help us
Sebastien Arbogast wrote:
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
...
It is called integration.
...
OK I'm sorry Ross. I'm really sorry. You're right I completely missed
your point and I apologize for that.
No harm done, quite the opposite in fact, your post made me consider
what
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
Sebastien Arbogast wrote:
2005/5/24, Ross Gardler [EMAIL PROTECTED]:
...
It is called integration.
...
OK I'm sorry Ross. I'm really sorry. You're right I completely missed
your point and I apologize for that.
No harm done, quite
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
we don't think Cocoon documentation should remain between Cocoon
developers and that's also why we chose a PHP based CMS : because
Sylvain Wallez wrote:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
we don't think Cocoon documentation should remain between Cocoon
developers and that's also why we chose a
On Mar, 24 de Mayo de 2005, 15:35, Sylvain Wallez dijo:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
we don't think Cocoon documentation should remain between Cocoon
developers
On Mar, 24 de Mayo de 2005, 15:42, Upayavira dijo:
Sylvain Wallez wrote:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
we don't think Cocoon documentation should remain
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:42, Upayavira dijo:
Sylvain Wallez wrote:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
we don't think Cocoon
On Mar, 24 de Mayo de 2005, 16:09, Upayavira dijo:
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:35, Sylvain Wallez dijo:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point
2005/5/24, Upayavira [EMAIL PROTECTED]:
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:35, Sylvain Wallez dijo:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
On Mar, 24 de Mayo de 2005, 16:16, Upayavira dijo:
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:42, Upayavira dijo:
Sylvain Wallez wrote:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:35, Sylvain Wallez dijo:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know Cocoon but not PHP. But it's exactly our point :
we don't think Cocoon documentation
On Mar, 24 de Mayo de 2005, 16:18, Sebastien Arbogast dijo:
2005/5/24, Upayavira [EMAIL PROTECTED]:
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:35, Sylvain Wallez dijo:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people
Sebastien Arbogast wrote:
2005/5/24, Upayavira [EMAIL PROTECTED]:
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:35, Sylvain Wallez dijo:
Sebastien Arbogast wrote:
The second important thing I notice in your remark is the argument
that people here know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sylvain Wallez wrote:
snip/
Yes it *is* about the technology. Why don't we have cool docs? Because
writing them in XML is a major PITA. That's why I dislike writing docs
so much.
Give me an htmlarea in a webapp and I'll be happy to dump my
Upayavira wrote:
Antonio Gallardo wrote:
...
With the new apache zones, I think there is posible in a rasonable amount
of time (hours?) to setup a CMS to do the job.
WDYT?
Then someone should do it, and we will see where that takes us. I'll
volunteer for the part of doing any document
Unico Hommes wrote:
BTW. Where *is* Linotype? I found this
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=110705988801725w=2 but
looking at http://simile.mit.edu/ I can't seem to find it. Linotype in
the 2.1 branch seems to be somewhat broken.
on betaversion.org svn I host the version that
I can't find any copyright or license information on the planetcocoon
site. Can you please point me at the relevant page.
I'm concerned as much of the documentation content appears to be direct
duplicates of materials in Cocoons official documentation or mailing
lists but I cannot find the
2005/5/23, Ross Gardler [EMAIL PROTECTED]:
I can't find any copyright or license information on the planetcocoon
site. Can you please point me at the relevant page.
Actually so far there is no such thing. As it is said in our
disclaimer, Planet Cocoon is an unofficial experiment in online
56 matches
Mail list logo
