Gregor J. Rothfuss wrote:
doug chestnut is working on WebDAV integration right now, which might
help with this. as a start, people could do their docs offline, and then
add them to lenya through webdav. lenya then takes care of checking
them in to the lenya revision control, doing workflow in
Ross Gardler wrote:
Yes, this is my biggest complaint about Daisy right now. Every single
change gets the same "priority" in the version management system. So if
I change a single letter, it create a new version and generates a commit
mail.
Wiki's deal with this by allowing you to mark somet
Gregor J. Rothfuss wrote:
Nicola Ken Barozzi wrote:
Hmmm... wait a second. Let's say that I add myfile.xml to SVN... can
it be later edited in Lenya?
that could be made to work. needs some initialization though, because
lenya creates worfklow histories etc for each document.
Nicola raise
Nicola Ken Barozzi wrote:
Hmmm... wait a second. Let's say that I add myfile.xml to SVN... can it
be later edited in Lenya?
that could be made to work. needs some initialization though, because
lenya creates worfklow histories etc for each document.
Also, is it good to bypass all the publi
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
committers . . Non-Committers ---
| |
| |
+-++-++---++--+
| Forrest |<---| SVN |<---| Lenya |--->|Lenya Repo|
+-
Ross Gardler wrote:
committers . . Non-Committers ---
| |
| |
+-++-++---++--+
| Forrest |<---| SVN |<---| Lenya |--->|Lenya Repo|
+-++-++--
David Crossley wrote:
Nicola Ken Barozzi wrote:
David Crossley wrote:
Ross Gardler wrote:
...
Does this sound OK?
It sounds brilliant.
Indeed!
The part that i like most is that each project
is focussing on their own tools, we are not duplicating, and we are
collaborating.
David,
Nicola Ken Barozzi wrote:
(cc'd to Lenya Dev for their comments as well - please reply-all)
...
Looking at the Doco document [1] I see that Lenya and Forrest are not
directly interacting, as both talk to a common repository.
Right now, what we have is:
--- committers ---. . Non-Commi
On Wed, 2005-06-08 at 11:11 +0100, Ross Gardler wrote:
> Thorsten Scherler wrote:
> > On Wed, 2005-06-08 at 10:08 +0100, Ross Gardler wrote:
> >
> >>Thorsten Scherler wrote:
> >>
>
> ...
>
> >>>:) Yeah, that is simply a contract that contains a link to
> >>>daisy/lenya/anyOtherCms edit page. I w
Thorsten Scherler wrote:
On Wed, 2005-06-08 at 10:08 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
...
:) Yeah, that is simply a contract that contains a link to
daisy/lenya/anyOtherCms edit page. I will make an example as soon I have
updated the locationmap branch on my harddrive an
On Wed, 2005-06-08 at 10:08 +0100, Ross Gardler wrote:
> Thorsten Scherler wrote:
> > On Wed, 2005-06-08 at 09:21 +0100, Ross Gardler wrote:
> >
> >>Nicola Ken Barozzi wrote:
>
> ...
>
> >>>Aditionally, what we would need is just to add an _edit_ link to each
> >>>Forrest page that points to th
Thorsten Scherler wrote:
On Wed, 2005-06-08 at 09:21 +0100, Ross Gardler wrote:
Nicola Ken Barozzi wrote:
...
Aditionally, what we would need is just to add an _edit_ link to each
Forrest page that points to the url Lenya uses for editing.
Currently this is done through filter XSL's (see
On Wed, 2005-06-08 at 09:21 +0100, Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
> > Gregor J. Rothfuss wrote:
> > ...
> >
> >> so initially, people could write documents in lenya, publish them, and
> >> then head over to forrest(bot?) to slurp all these pages in?
> >
> >
> > My personal vie
Nicola Ken Barozzi wrote:
Gregor J. Rothfuss wrote:
...
so initially, people could write documents in lenya, publish them, and
then head over to forrest(bot?) to slurp all these pages in?
My personal view is not to use the Forrestbot, but to
mod_proxy/mod_cache a live Forrest instance that
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> >Ross Gardler wrote:
> ...
> >>Does this sound OK?
> >
> >It sounds brilliant.
>
> Indeed!
>
> >The part that i like most is that each project
> >is focussing on their own tools, we are not duplicating, and we are
> >collaborating.
>
> David,
Gregor J. Rothfuss wrote:
...
so initially, people could write documents in lenya, publish them, and
then head over to forrest(bot?) to slurp all these pages in?
My personal view is not to use the Forrestbot, but to
mod_proxy/mod_cache a live Forrest instance that gets files from a
published
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
OK, along the same theme of quick hacks I've put a simple demo
together for you. To see it you need to checkout the
locationmap_branch of Forrest. Seed a fresh site, do "forrest run" and
look at the locaitonmap sample (last item in the samples men
David Crossley wrote:
Ross Gardler wrote:
...
Does this sound OK?
It sounds brilliant.
Indeed!
The part that i like most is that each project
is focussing on their own tools, we are not duplicating, and we are
collaborating.
David, it seems Ross cracked open the coconut [1] and we now
Gregor J. Rothfuss wrote:
> Ross Gardler wrote:
>
> >OK, along the same theme of quick hacks I've put a simple demo together
> >for you. To see it you need to checkout the locationmap_branch of
> >Forrest. Seed a fresh site, do "forrest run" and look at the locaitonmap
> >sample (last item in t
Ross Gardler wrote:
> Gregor J. Rothfuss wrote:
> >Ross Gardler wrote:
> >
> >>As mentioned I want to see the ability to work offline in the users
> >>preferred tool (a requirement of my work on the Digital Divide). Maybe
> >>we can make your wish come true eventually, the way I see it is we
> >
Ross Gardler wrote:
OK, along the same theme of quick hacks I've put a simple demo together
for you. To see it you need to checkout the locationmap_branch of
Forrest. Seed a fresh site, do "forrest run" and look at the locaitonmap
sample (last item in the samples menu).
cool, seems to work f
On Tue, 2005-06-07 at 16:12 -0400, Gregor J. Rothfuss wrote:
> Ross Gardler wrote:
>
> > Excellent. I think I can try and summarise this thread and lay out a
> > course of action.
> >
> > a) The Lenya team host a version of Lenya in their Zone for the use of
> > Forrest (whether this means a se
Ross Gardler wrote:
Excellent. I think I can try and summarise this thread and lay out a
course of action.
a) The Lenya team host a version of Lenya in their Zone for the use of
Forrest (whether this means a separate instance or a publication within
your own documentation instance is up to y
Torsten Schlabach wrote:
Thorsten Scherler wrote:
> Generally I would favor lenya over daisy but I will not be in the way
> of daisy either because I do not have the time to give the requested
> support for lenya.
I might be able to help! Depending on what the plan is.
Cool, Cocoon is usin
Thorsten Scherler wrote:
> Generally I would favor lenya over daisy but I will not be in the way
> of daisy either because I do not have the time to give the requested
> support for lenya.
I might be able to help! Depending on what the plan is.
Regards,
Torsten
Thorsten Scherler schrieb:
On Mo
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
As mentioned I want to see the ability to work offline in the users
preferred tool (a requirement of my work on the Digital Divide). Maybe
we can make your wish come true eventually, the way I see it is we
need to make Lenya use SVN as a repositor
Ross Gardler wrote:
The CMS is a "super wiki" - loosely controlled, low barrier to entry -
most importantly *not* published as official docs
lenya does have the authoring and live view for this purpose (and
workflow), so presumably the barrier for editing / submitting for
approval would be l
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
...
Although a long way from perfect I hope this is enough to illustrate
how to do the integration (see I told you it was easy with the
locationmap :-))
thanks for this, this definitely helps.
I've rejoined the Lenya dev list so will try and
Ross Gardler wrote:
As mentioned I want to see the ability to work offline in the users
preferred tool (a requirement of my work on the Digital Divide). Maybe
we can make your wish come true eventually, the way I see it is we need
to make Lenya use SVN as a repository. But that will come much
Ross Gardler wrote:
OK, along the same theme of quick hacks I've put a simple demo together
for you. To see it you need to checkout the locationmap_branch of
Forrest. Seed a fresh site, do "forrest run" and look at the locaitonmap
sample (last item in the samples menu).
There are a few thing
David Crossley wrote:
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
When you have a little demo going pass me a URL for a demo page that has
no navigation, I'll add it to the sample in the locationmap branch (we
don't have images working yet, but it should only be a sitemap addition).
htt
David Crossley wrote:
> I have another issue with being forced to do all editing via a
> web interface. With the current method of editing the source using
> whatever text-editor/xml-editor, i can be much more productive.
> I use UNIX tools like find and grep to search for certain occurences
> of
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
When you have a little demo going pass me a URL for a demo page that
has no navigation, I'll add it to the sample in the locationmap branch
(we don't have images working yet, but it should only be a sitemap
addition).
http://lenya.zones.apache.
David Crossley wrote:
Ross Gardler wrote:
Ferdinand Soethe wrote:
I still don't like the fact that it is online editing only but
perhaps I'm the only one still on a dial up line ...
I don't think you are the only one. Even if you are, many of us work
while traveling, so it is still an iss
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
How will the changed content get back into our SVN?
For development, it doesn't. Daisy is fully version controlled (and I
think Lenya is). For publishing we do just as we are doing now.
I don't yet see the distinction. ASF
Ross Gardler wrote:
> David Crossley wrote:
> >
> >How will the changed content get back into our SVN?
>
> For development, it doesn't. Daisy is fully version controlled (and I
> think Lenya is). For publishing we do just as we are doing now.
I don't yet see the distinction. ASF projects have as
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> >Nicola Ken Barozzi wrote:
> >>David Crossley wrote:
> >>...
> >>>I find this very alarming. Some people at Infrastructure are
> >>>trying to get a cross-project environment established for managing
> >>>documentation tools and site-building. All
David Crossley wrote:
Nicola Ken Barozzi wrote:
David Crossley wrote:
...
I find this very alarming. Some people at Infrastructure are
trying to get a cross-project environment established for managing
documentation tools and site-building. All PMCs were asked to
join and discuss this. Some pe
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> ...
> >I find this very alarming. Some people at Infrastructure are
> >trying to get a cross-project environment established for managing
> >documentation tools and site-building. All PMCs were asked to
> >join and discuss this. Some people have,
Ross Gardler wrote:
> Ferdinand Soethe wrote:
>
> >I still don't like the fact that it is online editing only but
> >perhaps I'm the only one still on a dial up line ...
>
> I don't think you are the only one. Even if you are, many of us work
> while traveling, so it is still an issue.
Until rec
Gregor J. Rothfuss wrote:
> Ross Gardler wrote:
>
> >When you have a little demo going pass me a URL for a demo page that has
> >no navigation, I'll add it to the sample in the locationmap branch (we
> >don't have images working yet, but it should only be a sitemap addition).
>
> http://lenya.z
Ross Gardler wrote:
When you have a little demo going pass me a URL for a demo page that has
no navigation, I'll add it to the sample in the locationmap branch (we
don't have images working yet, but it should only be a sitemap addition).
http://lenya.zones.apache.org:/default/live/index.h
Ross Gardler wrote:
> In other words with the locationmap our source documentation is no
> longer limited to being on the local file system, nor is it limited from
> being from a single remote repository. We can go as far as to have every
> page come from a different source.
Thanks for expl
Ferdinand Soethe wrote:
Ross Gardler wrote:
Ahh, but that is the "smart" part of my proposal.
Hey, are you saying there are sometimes not so smart parts in your
proposals :-)
Well I think my recent fresh-site fix for raw HTML that completely
removed the current 0.7 behaviour is a pretty
On Mon, 2005-06-06 at 16:12 +0100, Ross Gardler wrote:
>
> I'm offering some of my time (post 0.7) to get this going.
>
> Can we count on the Lenya team to assist?
>
> Thorsten, do you still need to create the Forrest Lenya integration? Can
> we count on some of your time for that part of it?
Ferdinand Soethe wrote:
edit ->> review changes -> publish/reject
I like the idea to trial run this for a while w/o touching the real
docs. Seems like the best way to explore all the dimensions of this
complex change.
+1
I still don't like the fact that it is online editing only but
perhaps
Ross Gardler wrote:
> Ahh, but that is the "smart" part of my proposal.
Hey, are you saying there are sometimes not so smart parts in your
proposals :-)
> There is no need to
> move existing docs if we don't want to. With the locationmap branch we
> can use content form multiple locations.
Can
edit ->> review changes -> publish/reject
I like the idea to trial run this for a while w/o touching the real
docs. Seems like the best way to explore all the dimensions of this
complex change.
Designing the outline for our manual would be great to thoroughly test
this.
I still don't like the f
Gregor J. Rothfuss wrote:
Ross Gardler wrote:
How difficult is it to provide a version of a page without the
navigation stuff, just the raw content? If you can do this then you
are already integrated (if you use the locationmap branch of Forrest).
fairly trivial. i had no idea integration w
Nicola Ken Barozzi wrote:
David Crossley wrote:
...
...
I find it very constructive that people are rushing to make it work.
Consolidation can come later.
Would it be better just to see this as an experiment, and not (yet)
really move the docs there till we have a vote with a working syst
Nicola Ken Barozzi wrote:
I find it very constructive that people are rushing to make it work.
Consolidation can come later.
i see the site-dev@ list mostly for setting policy at this time, less so
for development given the diverse nature of tools on that list (forrest,
maven, anakia, htmlma
David Crossley wrote:
...
I find this very alarming. Some people at Infrastructure are
trying to get a cross-project environment established for managing
documentation tools and site-building. All PMCs were asked to
join and discuss this. Some people have, but mainly the process
has stalled again
Gregor J. Rothfuss wrote:
Thorsten Scherler wrote:
Just a quick remark on that, I guess gregor, andreas, michi and other
would happily help us with that, but my time is too limited to actually
being a big help for doing it.
install is easy enough, and i would gladly do that. we need some he
Ross Gardler wrote:
How difficult is it to provide a version of a page without the
navigation stuff, just the raw content? If you can do this then you are
already integrated (if you use the locationmap branch of Forrest).
fairly trivial. i had no idea integration would be that easy :) let me
Ross Gardler wrote:
Yes (at least for Daisy, don't know about Lenya). You can play around by
looking at the versions on Daisy home page at CocoonDev.org
http://www.cocoondev.org/daisy/index/versions.html
lenya doesn't have such a nice diff view yet, so it would have to be an
external diff to
Gregor J. Rothfuss wrote:
Thorsten Scherler wrote:
Just a quick remark on that, I guess gregor, andreas, michi and other
would happily help us with that, but my time is too limited to actually
being a big help for doing it.
install is easy enough, and i would gladly do that. we need some he
Ferdinand Soethe wrote:
I guess the whole issue might come down to a question of philosophy.
And while I have fears for our content, I must admit that some wikis
such as Wikipedia have evolved into high quality content without a
controlling hand.
What seems hard to achieve will be to maintain a
David Crossley wrote:
Ross Gardler wrote:
Over at Cocoon they are starting to use Daisy for their docs. I propose
we do the same.
I have too many questions at this stage.
How will the changed content get back into our SVN?
For development, it doesn't. Daisy is fully version controlled (an
I guess the whole issue might come down to a question of philosophy.
And while I have fears for our content, I must admit that some wikis
such as Wikipedia have evolved into high quality content without a
controlling hand.
What seems hard to achieve will be to maintain a bit of control. We
can e
Ross Gardler wrote:
> Over at Cocoon they are starting to use Daisy for their docs. I propose
> we do the same.
I have too many questions at this stage.
How will the changed content get back into our SVN?
How is the workflow managed to get the content reviewed
and then published onto the websit
Thorsten Scherler wrote:
Just a quick remark on that, I guess gregor, andreas, michi and other
would happily help us with that, but my time is too limited to actually
being a big help for doing it.
install is easy enough, and i would gladly do that. we need some help to
mimic the daisy inte
On Mon, 2005-06-06 at 12:28 +0100, Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
> > Ross Gardler wrote:
> >
> >> Over at Cocoon they are starting to use Daisy for their docs. I
> >> propose we do the same.
> >
> >
> > I would prefer to use Lenya, as Cocoon will already stress test the
> > D
Ross Gardler wrote:
> Ferdinand Soethe wrote:
>> As far as new docs are concerned, it would be nice if we could provide
>> a basic structure for new docs to snap in. The ability to freely add
>> new docs in my experience leads to a maze rather then a web of
>> documentation and is not soo des
Ferdinand Soethe wrote:
I think this is worth considering.
It certainly would make corrections and minor adjustments a lot
easier.
As far as new docs are concerned, it would be nice if we could provide
a basic structure for new docs to snap in. The ability to freely add
new docs in my experienc
Nicola Ken Barozzi wrote:
Ross Gardler wrote:
Over at Cocoon they are starting to use Daisy for their docs. I
propose we do the same.
I would prefer to use Lenya, as Cocoon will already stress test the
Daisy integration aplenty. On the other hand, I have no will nor time to
help, and Daisy
Ross Gardler wrote:
Over at Cocoon they are starting to use Daisy for their docs. I propose
we do the same.
I would prefer to use Lenya, as Cocoon will already stress test the
Daisy integration aplenty. On the other hand, I have no will nor time to
help, and Daisy is good too.
+0 for the pr
I think this is worth considering.
It certainly would make corrections and minor adjustments a lot
easier.
As far as new docs are concerned, it would be nice if we could provide
a basic structure for new docs to snap in. The ability to freely add
new docs in my experience leads to a maze rather
Over at Cocoon they are starting to use Daisy for their docs. I propose
we do the same.
We recently voted Ferdinand in as a committer because of his efforts on
the docs and we have had a flurry of new users providing docs patches of
great value too. I think we need to make it easier for these
68 matches
Mail list logo
