Tim Williams wrote:
> How can one get the menu to maintain some context with no entry in
> site.xml?
With the current system, i don't think we can.
That is specifically mentioned at [1] below.
> For example, if the uri is "/category/News/entry1.html" and
> the site.xml was:
>
>
>
>
Anil Ramnanan wrote:
>
> Now that we have come to the end of the Summer of Code, I would like to
> thank my mentor, Ross Gardler as well as the entire community for
> helping me with this project. It has truly been a great learning
> experience and has not only allowed me to contribute code to
Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
> >David Crossley wrote:
> >
> >>We would rather use Forrest in dynamic mode
> >>so that we do not need to worry about the
> >>filename extensions in the output space and
> >>take more advantage of the Cocoon facilities
> >>like "Cocoon views" etc.
>
Thorsten Scherler wrote:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> > >
> > > Maybe we should think about a basic structure of *our* lenya pub, this
> > > way I can setup the instance with our structure and get rid of the
> > > sample.
> >
> > We just want a flat directory structure a
On Thu, 2005-09-01 at 17:55 +1000, David Crossley wrote:
> Thorsten Scherler wrote:
> >
> > Maybe we should think about a basic structure of *our* lenya pub, this
> > way I can setup the instance with our structure and get rid of the
> > sample.
>
> We just want a flat directory structure at the
How can one get the menu to maintain some context with no entry in
site.xml? For example, if the uri is "/category/News/entry1.html" and
the site.xml was:
Since entry1.html is logically subordinate to the 'News' site.xml
label, it seems like I
On Thu, 2005-09-01 at 18:25 +0100, Ross Gardler wrote:
> Juan Jose Pablos wrote:
> > Anil Ramnanan wrote:
> >
> >> Again thank you for your help and support. Although the Summer of Code
> >> is finished, I am not and I intend to continue contributing.
> >
> >
> > Nice to know Anil :-)
>
> +100
Nicola Ken Barozzi wrote:
Tim Williams wrote:
...
So are we now saying that "merit" applies across the ASF?
In a sense, WRT trust, IMO, yes.
+1, with respect to trust. If someone in Apache trusts them, that is
good enough for me.
With respect to having the *technical* skills to contrib
Juan Jose Pablos wrote:
Anil Ramnanan wrote:
Again thank you for your help and support. Although the Summer of Code
is finished, I am not and I intend to continue contributing.
Nice to know Anil :-)
+1000
I'm travelling again, with intermittent access, however, at some point
over the nex
Nicola Ken Barozzi wrote:
David Crossley wrote:
We would rather use Forrest in dynamic mode
so that we do not need to worry about the
filename extensions in the output space and
take more advantage of the Cocoon facilities
like "Cocoon views" etc.
However, we must be able to produce a static
s
Tim Williams wrote:
...
> So are we now saying that "merit" applies across the ASF?
In a sense, WRT trust, IMO, yes.
> That just
> doesn't make sense to me given the diversity of projects here. I mean
> my own interpretation is that there are two parts to merit: 1)
> Technical and 2) Community
Anil Ramnanan wrote:
Again thank you for your help and support. Although the Summer of Code
is finished, I am not and I intend to continue contributing.
Nice to know Anil :-)
Since I've learned most of what I know from reading words from you
guys, it surprises me that I come to a different conclusion.
As I understand it, committership is based on merit and one earns
merit only *after* consistently making good contributions
demonstrating that they've earned it.
I also,
Now that we have come to the end of the Summer of Code, I would like to
thank my mentor, Ross Gardler as well as the entire community for
helping me with this project. It has truly been a great learning
experience and has not only allowed me to contribute code to the project
but allowed me to
David Crossley wrote:
> We would rather use Forrest in dynamic mode
> so that we do not need to worry about the
> filename extensions in the output space and
> take more advantage of the Cocoon facilities
> like "Cocoon views" etc.
>
> However, we must be able to produce a static
> set of document
Thorsten Scherler wrote:
On Thu, 2005-09-01 at 02:12 +0100, Ross Gardler wrote:
I did some work this evening on an "old" site that was using views (i.e.
before the refactoring for project.theme and project.theme-fv properties).
I've added these properties am told the resource is not found. No
We would rather use Forrest in dynamic mode
so that we do not need to worry about the
filename extensions in the output space and
take more advantage of the Cocoon facilities
like "Cocoon views" etc.
However, we must be able to produce a static
set of documents. That constrains us to the
filename
[copied to the Forrest dev list for information, there is nothing new in
here for Forrest devs, but a decision has been made that affects Forrest
so I'm copying this "end of discussion" type mail]
Andreas Hartmann wrote:
Michael Wechner wrote:
Thorsten Scherler wrote:
On Wed, 2005-08-31 at
On Thu, 2005-09-01 at 02:12 +0100, Ross Gardler wrote:
> I did some work this evening on an "old" site that was using views (i.e.
> before the refactoring for project.theme and project.theme-fv properties).
>
> I've added these properties am told the resource is not found. Now, this
> resource i
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
I revised the list, taking the replies into account
and adding some new queries.
I've now put these into Jira as sub-tasks. Thanks for your input.
http://issues.apache.org/jira/browse/FOR-184
So are we still going to attemp
Nicola Ken Barozzi wrote:
Ross Gardler wrote:
...
I don't have the time to find that discussion right now. Anyone have a
clearer recollection to be able to search for it quickly (my first few
attempts failed so it's back to the deadline beating)...
Ok, found it... how stupid of me, I had wri
David Crossley wrote:
> Nicola Ken Barozzi wrote:
...
>>I would propose that commit access is given to all Apache committers; I
>>don't see why Lenya or Cocoon committers have more "merit" than any
>>other at Apache.
>>
>>I would like to remind all that Gump has the same pattern of access, and
>>no
David Crossley wrote:
Nicola Ken Barozzi wrote:
David Crossley wrote:
...
The main effect that i see is that we would be
opening up the Forrest repository to people that
we do not know and are not familiar with.
Is everyone happy with that.
Yes.
Being Apache committers they should and will
addi wrote:
From plugin page
(http://forrest.apache.org/pluginDocs/plugins_0_70/index.html#Whiteboard+Plugins)
trying to go to view plugin page...
Not Found
The requested URL /pluginDocs/plugins_0_70/org.apache.forrest.plugin.view was
not found on this server.
Either the plugin has to be d
Thorsten Scherler wrote:
>
> Maybe we should think about a basic structure of *our* lenya pub, this
> way I can setup the instance with our structure and get rid of the
> sample.
We just want a flat directory structure at the moment.
This is a "whiteboard" wiki-like thingy for us to
experiment wi
Thorsten Scherler wrote:
> David Crossley wrote:
>
> > Then why doesn't that publication remain in the
> > Lenya repository?
>
> ...because it is our (like in forrest) custom lenya publication, it is
> our code that has nothing to do with lenya. That is like asking why the
> lenya docu is not in
Ross Gardler wrote:
> >>>David Crossley wrote:
> I revised the list, taking the replies into account
> and adding some new queries.
>
> I've now put these into Jira as sub-tasks. Thanks for your input.
http://issues.apache.org/jira/browse/FOR-184
So are we still going to attempt to make
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> ...
> > The main effect that i see is that we would be
> > opening up the Forrest repository to people that
> > we do not know and are not familiar with.
> > Is everyone happy with that.
>
> Yes.
>
> Being Apache committers they should and will
On Thu, 2005-09-01 at 14:36 +1000, David Crossley wrote:
> Then why doesn't that publication remain in the
> Lenya repository?
...because it is our (like in forrest) custom lenya publication, it is
our code that has nothing to do with lenya. That is like asking why the
lenya docu is not in forres
Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
> ...
> > I don't have the time to find that discussion right now. Anyone have a
> > clearer recollection to be able to search for it quickly (my first few
> > attempts failed so it's back to the deadline beating)...
>
> Ok, found it... how stupid of
David Crossley wrote:
...
> The main effect that i see is that we would be
> opening up the Forrest repository to people that
> we do not know and are not familiar with.
> Is everyone happy with that.
Yes.
Being Apache committers they should and will behave with all the needed
respect to our proj
[
http://issues.apache.org/jira/browse/FOR-184?page=comments#action_12320761 ]
David Crossley commented on FOR-184:
See the description of the processing pipeline in
trunk/site-author/content/xdocs/TR/2004/WD-forrest10.html
> Switch to XHTML2
> ---
Ross Gardler wrote:
> Thorsten Scherler wrote:
>
>>> I think the Lenya community should give commit access to the Forrest
>>> community
>>> if people agree to enhance the default publication of Lenya. If it is
>>> going
>>> to be a specific Forrest-Lenya publication, then I think it doesn't
>>> re
33 matches
Mail list logo
