Hi Calvin,
this is a great discussion, we need more people to jump in.
I put some comments inline.
Calvin Austin wrote:
Hernan Cunico wrote:
Hi Calvin,
I saw your prev note, good follow up. It is in my TO DO list to reply :)
I had planned to cover not just JBoss but also WebLogic, iPlanet,
Oracle AS and Websphere. Again, that was my original plan but then I
saw the need for expanding to other topics and I could not keep up the
pace with my original idea for migration.
I was also expecting to get more people involved in the doc.
JBoss would have been my first choice too, I've met a few JBoss users
who would like to move if they had the opportunity.
It would be great if we can continue the work on the migration area.
I've done several migrations in the past (across vendors and
platforms) and would really like to continue develoing this section
but I am not having the time. I am now trying to focus on the hot
topics discussed on the dev list.
Just reading the dev list is a task!
What is your idea to take back on the migration section
I have a couple of ideas, 1) Help fill in any gaps in your current
migration docs 2) I have 'access' for a better choice of words to a
partner who is going to go through some real life migrations, I want to
capture all that information and propose a tool if the work is too
manual 3) start placeholders for the other apps servers and work through
at least two
What platform are you planning to start migrating from?
I wrote a book based on a migration experience from a customer, it was a great experience for
everybody but I would count customer migrations as "Case studies" instead of adding them to a
subsection in the general "Migrating to Apahe Geronimo" section.
Migration tools/plugins are another great idea. I have used a few plugins in Rational for migrating
CMPs but could not find a way to automate the migration for the rest of the sample apps.
Feel free to add the place holders (and content) :) in the migration section. Let me know if you
need a hand with confluence.
Cheers!
Hernan
regards
calvin
Cheers!
Hernan
Calvin Austin wrote:
Hi Hernan
Have you considered migrations from other app servers too, obviously
IBM has their own roadmap with websphere, but what about weblogic,
sun/iplanet/sunone, oracle app server? I know when I tried to move
petstore over originally I ended up trying to automate as much as I
could
regards
calvin
------------------------------------------------------------------------
Subject:
Re: Roadmap, tasks and things to do?
From:
Calvin Austin <[EMAIL PROTECTED]>
Date:
Wed, 15 Feb 2006 09:27:13 -0800
To:
[email protected]
To:
[email protected]
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
After following the discussions about project donations over the past
week and the sometimes difficult questions each donation raises. I
think its a good time to revisit this wishlist to see how it all fits
together in a bigger picture.
What would be the top 3 things that would make Geronimo successful
and the de-facto choice for open source J2EE app developers?
My personal choice would be
1. To make it easy for developers to start or migrate to Geronimo,
that could be migration tools/deployment, how to documentation (there
are some good examples so far, Hernan and others are very focused on
JBoss :*), feature set leveling (obviously in process), testing that
your app still works!. Some donations may fit here.
2. Make the release/build process more agile, resilient (eg maven2/ant)
3. First place to come for latest J2EE technology.
If anyone else is interesting in 1) migration activities then let me
know, I think with Hernans great start we can divide the workload up
and finish this task sooner than later
regards
calvin
