Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=kACdHBfqDocy20wrnN6I4Wkd7iJH8bDtGd6i95XFJF7MhKEKqHHMxQRxgRzVoliT;
  h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <43DA3650.7060207@earthlink.net>
Date: Fri, 27 Jan 2006 10:03:44 -0500
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: Roadmap, tasks and things to do?
References: <2BCE7882-D6CD-4362-B5B6-916AAFCB0F89@iq80.com>
In-Reply-To: <2BCE7882-D6CD-4362-B5B6-916AAFCB0F89@iq80.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Some web console/portal items:

o Support competing Portal servers (JetSpeed, Pluto Simple Portal, 
others?)... Pluto would be great for those needing a very lightweight 
Portal server.  I see this similar to multiple Web Container support.

o Remove embedded Pluto Portal Server in console provide external 
dependency for "a Portal" (could be any of those from the previous item).

o Pluggable console component structure so that the admin functions are 
only included if the managed component is included in the assembly (ex. 
only include EJB management if an EJB container is included).

o Role based authorization for individual console activities (not just 
one size fits all).

o Clean up admin portlets for programming best practices.

o Extend console to keep up with new features (mgmt. of Portal Appls., 
clusters, etc...)

o Web Console configuration for clustered environment (one console with 
remote management?)

o Greater use of AJAX for more interactive admin on the console.

Joe

Dain Sundstrom wrote:
> Ever since we shipped 1.0, I have been getting a surprising number of  
> private emails from old fiends, old Geronimo contributers, companies,  
> and just random people telling me that the are excited about Geronimo  
> and want to join in.  They all inevitably ask me for advise on what  to 
> work on, and I really have no idea other than "look at JIRA". So  I'd 
> like to solicit the community to help me create a roadmap, tasks,  
> things to do list, what ever we call it.
> 
> Before we get into building this, I'd like to focus the discussion,  so 
> we don't end up in mailing-list fantasy land :)  Lets agree to not  talk 
> about the technology used to track the tasks; once we have the  content 
> we can discuss using JIRA, wiki, html or creating a Gopher  site.  
> Secondly, lets focus on things that are reasonable to do in  the next 9 
> months.  Finally, don't worry about someone else working  on something 
> you want to work on.  With open communication on the  mailing list, I 
> think everyone will be able to work something they  find interesting 
> without stepping on toes.  Oh, one final thing,  please don't try to 
> "take a task" until we have this list complete.
> 
> Without further delay, here are some things off the top of my head:
> 
> o Conversion to Maven 2 - Very important and a huge task
> 
> o Ant versions of the Geronimo plugins
> 
> o  XDoclet for all configurations
> 
> o Integration tests that cover servlets, webservices and jms
> 
> o Little-G - Geronimo with a small foot print
> 
> o Global non-persistent JNDI implementation
> 
> o EJB 2.x - Once I get my refractor committed, it will be obvious  where 
> the 2.x implementation needs work like better caching
> 
> o JEE 5 - There is a ton of stuff under this, but it would be good to  
> start with a list of what is required for JEE 5
> 
> 
> 
> I don't want to speak for the other ares of Geronimo I don't work on  
> regularly, but I am sure that there are good opportunities to help in  
> the console, jms, javamail, ejb, clustering, esb/jbi/bpm, tooling,  
> performance, build, testing, samples, documentation, so if you are  more 
> familiar with one of those areas, please post.
> 
> I think this is a "once in a project chance" to build a big vibrant  
> community of developers, and let's not let it pass us by.
> 
> Thanks in advance,
> 
> -dain
> 
> 

-- 
Joe Bohn
joe.bohn at earthlink.net

"He is no fool who gives what he cannot keep, to gain what he cannot 
lose."   -- Jim Elliot