[MAGNOLIA-587] concept for future magnolia (possibly 3.5) Created: 31/Oct/05  Updated: 03/Dec/13  Due: 07/Nov/05  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PDF File Magnolia3.0.pdf    
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-588 Refactoring vs JSF with Facelets vs W... Sub-task Closed  
MAGNOLIA-589 Admin interface: XML-RPC vs SOAP Sub-task Closed  
MAGNOLIA-593 Command architecture Sub-task Closed  
MAGNOLIA-608 Spring integration? Sub-task Closed  
MAGNOLIA-619 MgnlContext Sub-task Closed Sameer Charles  
MAGNOLIA-620 Javascript: clean up Sub-task Closed  
MAGNOLIA-635 Using rhino (javascript) for configur... Sub-task Closed  
MAGNOLIA-637 JMX integration Sub-task Closed Magnolia International  
MAGNOLIA-761 Modules Sub-task Closed Philipp Bärfuss  
MAGNOLIA-811 Workflow Sub-task Closed  
MAGNOLIA-812 Easy Configuration Sub-task Closed Philipp Bärfuss  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

There were a lot of discussions about the future of magnolia. For example you may remember the discussions about which framework we should use or about new features like references, workflow...

I wrote a concept draft to restart this process in a more professional way. It contains a lot of the conclusions we made in this list. We discussed this document internally at obinary and it were reviewed by some others of this list too. After all we are ready to start a last public discussion before we make a final decision. This will lead us then step by step to a really cool enterprise enabled magnolia.

Since the proposed changes are of a bigger nature we call it magnolia 3.0 suggesting that this work will not be done in a few weeks There is already a 2.2 planed and maybe there will be a 2.3 before the bombastic 3.0 show.

How ever, we make the important decisions now so that we have a clear roadmap afterward. Doing this we hope that we can gain the one or the other from here to help us during the implementation process since we can not do all that work by our own.

We will proceed as follow:
1. We start the final discussion on the list. Doing this we will use JIRA (Subtasks for specific topics)
2. If there is no consensus after one week we will vote.
3. We build a project team (who would participate, who takes responsibilities)
4. The team (maybe sub teams) makes a more detailed concept or prototype implementations.
5. We plan the work (priorities, milestones, resource assessment). We will use centrics as the integral tool.

The details about voting etc are written down in the document which I will attache to the JIRA task.



 Comments   
Comment by Philipp Bracher [ 31/Oct/05 ]

The document to discuss

Comment by Philipp Bracher [ 31/Oct/05 ]

Feel free to add subtask if you start a discussion about a subaspect

Comment by Philipp Bracher [ 13/Feb/06 ]

the most of the proposed issues will be part of 3.1 not 3.0

Generated at Mon Feb 12 03:18:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.