We've decided to make a few changes to the leadership of the Seam and Weld projects, the reasons for which I'll outline in this blog post. First however, let me give you the headline changes!
Shane Bryzak will be at the helm of Seam 3, driving it to a 3.0 release in Q1 2011. Shane has worked on Seam since Seam 1.0 (in fact since February 2006), and has proven himself time and again - he is the author of Seam Security, perhaps Seam's most important feature and he worked tirelessly on the CDI TCK giving him a great knowledge of the foundations of Seam 3.
Marek Novotny, who has responsibility for Seam in the JBoss EAP platform, will take the reins for making sure Seam 2 runs on JBoss AS 6, in effect he's been doing this for months now!
Ales Justin will take on Weld. Ales led the development effort for the kernel of JBoss AS 5 and 6, meaning he has a very strong understanding of bean containers and also of how app servers fit together - which are certainly the two key skills needed. I can't think of anyone better suited to take Weld to the next level.
I'll be moving to Infinispan, an area I've always been interested in; starting on the 10th January.
Shane and Ales will blog soon to give you a flavour of where they intend to take the projects, so keep an eye out for that.
Seam's sister projects such as Arquillian, and our recent efforts around Forge are both future stars, and I trust both Aslak (Arquillian) and Lincoln (Forge) at their helm.
So, why are we doing this? It's quite simple really. After 4 years on the Seam project (my first commit was January 2007 I've reached the point where I am ready to tackle some new challenges. My move rippled through, causing us to look at each of the projects I have had a hand in and consider who would be best to take on each one.
I'll also be keeping my hand in with Seam and Weld; Red Hat plans to submit a JSR for CDI 1.1 shortly (with myself as EG lead), aligned with the Java EE timeframe (functionality complete in Q1 2011, with the final in Q3 2011). In general we're very happy with CDI 1.0 and don't feel there's a need for extensive new functionality in CDI 1.1. Instead, we'll be focusing on improvements and clarifications to areas of the spec we've identified as hurdles for both application developers and those writing portable extensions. Watch this space for more on this topic in the next month or so.
Congrats and have fun with Infinispan. Would Dan Allen says in the same role as well?
Thanks for the great work so far, and good luck with Infinispan!
I guess we can count on good integration of Infinispan with Seam ;)
Thanks. Yes, Dan will be staying put, working on Seam 3 and on Arquillian :-D
Congratulations! And a good thing that you're not leaving the company altogether so no-one gets any -associations ;-)
Congratulations Pete. You've done a great job and I'm glad we can offer you something as equally challenging and interesting to move into. Plus Seam/Weld will remain in very capable hands!
Congratulations to both of you.
The fact there were so many leadership changes is testament to how much Pete has done for Seam over the years and how many leadership roles he's cultivated. I'm sure we can expect Infinispan (and the integration with Seam) to be top notch (as if it weren't already) ;)
Congrats and good luck Pete! And I agree with Nicklas, we are psyched you're still at JBoss.
Now back to full steam ahead on Seam 3!
I think this is a great new role for you, Pete! But I don't think you can say, at BOFs anymore ;)
Congrats Pete, it was truly a pleasure working with you on Seam for all those years. I'm certain that the Infinispan team will greatly benefit from your experience.
Now more importantly, how on earth as Seam project lead did you deal with all the extra e-mails??
Let's get Seam 3 released or at least Seam 2 running with JSF 2.0. Hopefully the leadership change will make this happen. With all the changes in the Java world and the snail pace that Seam 3 is moving at we are seriously considering moving to a more agile platform such as RoR. Our developers love Java and loved Seam, but now they feel constrained and held hostage to old technology as other technology passes us by. We can't even take advantages of new components or improved components in our Primefaces component library because of the JSF 2.0 barrier. It seems to us that the focus in on the projects and not on the core Seam 3.
Seam 2 with JSF 2 and facelets 2.0 compatibility would be much appreciated. Without facelets 2 we are still stalled.
+1 for Seam2 working on JBoss 6.
I don't care if it's Seam 3 or Seam 2 as long as it works with JSF 2.0 and PrimeFaces.
Indeed, we are stumbled upon the gap between Seam 2 and JSF2, yet we cannot leverage the new shiny PrimeFaces... Now have to re-think original intent to use Seam in our enterprise level project.
I agree, we need Seam 2 running on JSF 2 soon as we are stuck in JSF 1.2...we can then move to JSF 2 and RF 3.3 and then switch to RF 4 when it will be ready...
Thanks
Demetrio
You can already more to RF3.3.
Anyway the problem here, is that we need Seam3 but also RichFaces 4 to leverage the advantage of JSF2. Both projects didn't respect the early timetable (we thought that a first releases of Seam and Richfaces were ready for late summer...!).
I'm already using RF 3.3, I'd like to use JSF2 (supported by RF 3.3) but there are still problems with Seam 2...
Demetrio
Thanks .. Pete!
The latest plans for Richfaces 4.0 are here - http://community.jboss.org/wiki/RichFaces40ReleaseCenter
We are already working on the first CR release, and are shooting for an early March release of Final,
You'll be missed, Pete! Thanks for all your hard work on Weld.