You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2005/08/13 12:15:54 UTC

[jira] Created: (FOR-630) Forrest strategy and direction

Forrest strategy and direction
------------------------------

         Key: FOR-630
         URL: http://issues.apache.org/jira/browse/FOR-630
     Project: Forrest
        Type: Task
    Reporter: Ross Gardler
    Priority: Critical
     Fix For: 0.8-dev


Topics for discussion gathered at ApacheCon EU 2005.

WARNING: Only reply to the general theme of this
topics list. Please create separate threads for
each specific topic.

Actually we should be using Jira for some of this.
How about discussing on the mailing list, and
putting summaries into Jira.

I have the scraps of paper that Nicola Ken wrote.
Photographs are in:
http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
Ross helped me to interpret some of the sqwiggles,
but there are still some obscure parts (marked
with #? below). The items are raw, i have not tried
to explain any or add others.

List of topics is in no particular order and
it is not complete. We spent maybe 15 minutes
brainstorming. We had a first quick pass at
assigning some priority.

I don't understand NKBs priority symbols.
Anyway some items where marked with
 circle ... [C]
 square ... [S]

Then we went straight on to the top topic:
"configuration" and spent the rest of the day.

--------------

* Create lenya/forrest publication.

* [C] Naming convention for "views".

* Roadmap specifically for views.

* [S] i18n support with locationmap.

* Locationmap - what is needed to complete it.

* [C] Configuration |=> apache      #? arrow apache #?

* TraversableSource ...

  * Source resolving for locationmap.

  * [C] How views are interacting with locationmap?

* [S] Documentation mismatch. Docs are distributed in
  various places: site, plugins, seed.

* Block documentation for Cocoon (/Forrest).

* [C] Pre-processing plugins.

* Flow of the plugin process.
  plugins - locationmap / flow   #? this line obscure #?

* Memory profiling.

* Better use of Jira.

* [S] XHTML2 transition.

* [S] Live Forrest for Apache.
  (a configuration usecase)

* [S] New skins for views.

* Views ... body="true|false" head="true|false"

* The *.ft files in a plugin (one-to-many).

* Move into Java -> 0.9.5 or when needed.  #? no idea what #?
    
* [C] View / doctypes.
  (view in view)

* [C] Content directory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (FOR-630) Forrest strategy and direction

Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-630?page=all ]

Ross Gardler updated FOR-630:
-----------------------------

    Fix Version:     (was: 0.8-dev)

> Forrest strategy and direction
> ------------------------------
>
>          Key: FOR-630
>          URL: http://issues.apache.org/jira/browse/FOR-630
>      Project: Forrest
>         Type: Task
>   Components: Other
>     Reporter: Ross Gardler
>     Priority: Critical

>
> Topics for discussion gathered at ApacheCon EU 2005.
> WARNING: Only reply to the general theme of this
> topics list. Please create separate threads for
> each specific topic.
> Actually we should be using Jira for some of this.
> How about discussing on the mailing list, and
> putting summaries into Jira.
> I have the scraps of paper that Nicola Ken wrote.
> Photographs are in:
> http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
> Ross helped me to interpret some of the sqwiggles,
> but there are still some obscure parts (marked
> with #? below). The items are raw, i have not tried
> to explain any or add others.
> List of topics is in no particular order and
> it is not complete. We spent maybe 15 minutes
> brainstorming. We had a first quick pass at
> assigning some priority.
> I don't understand NKBs priority symbols.
> Anyway some items where marked with
>  circle ... [C]
>  square ... [S]
> Then we went straight on to the top topic:
> "configuration" and spent the rest of the day.
> --------------
> * Create lenya/forrest publication.
> * [C] Naming convention for "views".
> * Roadmap specifically for views.
> * [S] i18n support with locationmap.
> * Locationmap - what is needed to complete it.
> * [C] Configuration |=> apache      #? arrow apache #?
> * TraversableSource ...
>   * Source resolving for locationmap.
>   * [C] How views are interacting with locationmap?
> * [S] Documentation mismatch. Docs are distributed in
>   various places: site, plugins, seed.
> * Block documentation for Cocoon (/Forrest).
> * [C] Pre-processing plugins.
> * Flow of the plugin process.
>   plugins - locationmap / flow   #? this line obscure #?
> * Memory profiling.
> * Better use of Jira.
> * [S] XHTML2 transition.
> * [S] Live Forrest for Apache.
>   (a configuration usecase)
> * [S] New skins for views.
> * Views ... body="true|false" head="true|false"
> * The *.ft files in a plugin (one-to-many).
> * Move into Java -> 0.9.5 or when needed.  #? no idea what #?
>     
> * [C] View / doctypes.
>   (view in view)
> * [C] Content directory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (FOR-630) Forrest strategy and direction

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-630:
-------------------------------

    Priority: Major  (was: Critical)

I disagree. I see many items that are still relevant. But don't need to be addressed at the moment.

Anyway, i reduced the Issue Priority.

> Forrest strategy and direction
> ------------------------------
>
>                 Key: FOR-630
>                 URL: https://issues.apache.org/jira/browse/FOR-630
>             Project: Forrest
>          Issue Type: Task
>          Components: Other
>            Reporter: Ross Gardler
>
> Topics for discussion gathered at ApacheCon EU 2005.
> WARNING: Only reply to the general theme of this
> topics list. Please create separate threads for
> each specific topic.
> Actually we should be using Jira for some of this.
> How about discussing on the mailing list, and
> putting summaries into Jira.
> I have the scraps of paper that Nicola Ken wrote.
> Photographs are in:
> http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
> Ross helped me to interpret some of the sqwiggles,
> but there are still some obscure parts (marked
> with #? below). The items are raw, i have not tried
> to explain any or add others.
> List of topics is in no particular order and
> it is not complete. We spent maybe 15 minutes
> brainstorming. We had a first quick pass at
> assigning some priority.
> I don't understand NKBs priority symbols.
> Anyway some items where marked with
>  circle ... [C]
>  square ... [S]
> Then we went straight on to the top topic:
> "configuration" and spent the rest of the day.
> --------------
> * Create lenya/forrest publication.
> * [C] Naming convention for "views".
> * Roadmap specifically for views.
> * [S] i18n support with locationmap.
> * Locationmap - what is needed to complete it.
> * [C] Configuration |=> apache      #? arrow apache #?
> * TraversableSource ...
>   * Source resolving for locationmap.
>   * [C] How views are interacting with locationmap?
> * [S] Documentation mismatch. Docs are distributed in
>   various places: site, plugins, seed.
> * Block documentation for Cocoon (/Forrest).
> * [C] Pre-processing plugins.
> * Flow of the plugin process.
>   plugins - locationmap / flow   #? this line obscure #?
> * Memory profiling.
> * Better use of Jira.
> * [S] XHTML2 transition.
> * [S] Live Forrest for Apache.
>   (a configuration usecase)
> * [S] New skins for views.
> * Views ... body="true|false" head="true|false"
> * The *.ft files in a plugin (one-to-many).
> * Move into Java -> 0.9.5 or when needed.  #? no idea what #?
>     
> * [C] View / doctypes.
>   (view in view)
> * [C] Content directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FOR-630) Forrest strategy and direction

Posted by "Gavin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781340#action_12781340 ] 

Gavin commented on FOR-630:
---------------------------

I'd like to close this 4 year old critical issue.

It looks like everything has either been addressed or is not relevant any more.

> Forrest strategy and direction
> ------------------------------
>
>                 Key: FOR-630
>                 URL: https://issues.apache.org/jira/browse/FOR-630
>             Project: Forrest
>          Issue Type: Task
>          Components: Other
>            Reporter: Ross Gardler
>            Priority: Critical
>
> Topics for discussion gathered at ApacheCon EU 2005.
> WARNING: Only reply to the general theme of this
> topics list. Please create separate threads for
> each specific topic.
> Actually we should be using Jira for some of this.
> How about discussing on the mailing list, and
> putting summaries into Jira.
> I have the scraps of paper that Nicola Ken wrote.
> Photographs are in:
> http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
> Ross helped me to interpret some of the sqwiggles,
> but there are still some obscure parts (marked
> with #? below). The items are raw, i have not tried
> to explain any or add others.
> List of topics is in no particular order and
> it is not complete. We spent maybe 15 minutes
> brainstorming. We had a first quick pass at
> assigning some priority.
> I don't understand NKBs priority symbols.
> Anyway some items where marked with
>  circle ... [C]
>  square ... [S]
> Then we went straight on to the top topic:
> "configuration" and spent the rest of the day.
> --------------
> * Create lenya/forrest publication.
> * [C] Naming convention for "views".
> * Roadmap specifically for views.
> * [S] i18n support with locationmap.
> * Locationmap - what is needed to complete it.
> * [C] Configuration |=> apache      #? arrow apache #?
> * TraversableSource ...
>   * Source resolving for locationmap.
>   * [C] How views are interacting with locationmap?
> * [S] Documentation mismatch. Docs are distributed in
>   various places: site, plugins, seed.
> * Block documentation for Cocoon (/Forrest).
> * [C] Pre-processing plugins.
> * Flow of the plugin process.
>   plugins - locationmap / flow   #? this line obscure #?
> * Memory profiling.
> * Better use of Jira.
> * [S] XHTML2 transition.
> * [S] Live Forrest for Apache.
>   (a configuration usecase)
> * [S] New skins for views.
> * Views ... body="true|false" head="true|false"
> * The *.ft files in a plugin (one-to-many).
> * Move into Java -> 0.9.5 or when needed.  #? no idea what #?
>     
> * [C] View / doctypes.
>   (view in view)
> * [C] Content directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FOR-630) Forrest strategy and direction

Posted by "Tim Williams (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-630?page=all ]

Tim Williams updated FOR-630:
-----------------------------

    Component: Other

> Forrest strategy and direction
> ------------------------------
>
>          Key: FOR-630
>          URL: http://issues.apache.org/jira/browse/FOR-630
>      Project: Forrest
>         Type: Task
>   Components: Other
>     Reporter: Ross Gardler
>     Priority: Critical
>      Fix For: 0.8-dev

>
> Topics for discussion gathered at ApacheCon EU 2005.
> WARNING: Only reply to the general theme of this
> topics list. Please create separate threads for
> each specific topic.
> Actually we should be using Jira for some of this.
> How about discussing on the mailing list, and
> putting summaries into Jira.
> I have the scraps of paper that Nicola Ken wrote.
> Photographs are in:
> http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
> Ross helped me to interpret some of the sqwiggles,
> but there are still some obscure parts (marked
> with #? below). The items are raw, i have not tried
> to explain any or add others.
> List of topics is in no particular order and
> it is not complete. We spent maybe 15 minutes
> brainstorming. We had a first quick pass at
> assigning some priority.
> I don't understand NKBs priority symbols.
> Anyway some items where marked with
>  circle ... [C]
>  square ... [S]
> Then we went straight on to the top topic:
> "configuration" and spent the rest of the day.
> --------------
> * Create lenya/forrest publication.
> * [C] Naming convention for "views".
> * Roadmap specifically for views.
> * [S] i18n support with locationmap.
> * Locationmap - what is needed to complete it.
> * [C] Configuration |=> apache      #? arrow apache #?
> * TraversableSource ...
>   * Source resolving for locationmap.
>   * [C] How views are interacting with locationmap?
> * [S] Documentation mismatch. Docs are distributed in
>   various places: site, plugins, seed.
> * Block documentation for Cocoon (/Forrest).
> * [C] Pre-processing plugins.
> * Flow of the plugin process.
>   plugins - locationmap / flow   #? this line obscure #?
> * Memory profiling.
> * Better use of Jira.
> * [S] XHTML2 transition.
> * [S] Live Forrest for Apache.
>   (a configuration usecase)
> * [S] New skins for views.
> * Views ... body="true|false" head="true|false"
> * The *.ft files in a plugin (one-to-many).
> * Move into Java -> 0.9.5 or when needed.  #? no idea what #?
>     
> * [C] View / doctypes.
>   (view in view)
> * [C] Content directory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira