I'm often asked to identify what projects I'm working on at Red Hat, or what group I'm a part of. My response reads like a laundry list:
- Seam
- Weld
- CDI TCK
- Arquillian
...and sometimes I'm really not sure if I can classify myself as a member of a certain project (e.g., RichFaces). Other developers that hang around here likely have a similar story. Eventually, we just settle on the response, I'm part of the in.relation.to crowd.
However, for people that don't know this blog, or its history, this description makes no sense whatsoever. Which made me come to the realization that we lack a true identity within the JBoss Community. I believe this detracts from the spirit of integration and coordination between projects. As my first order as Community Liaison, I set out to fix that.
Seam is often described as the glue that brings together a myriad of standard and third-party Java EE technologies. The glue that brings us together is that we are all working on creating tools and frameworks for the application developer (some use the term enterprise web developer
). This purpose not only unites those of us creating these technologies, but also unites us with the folks that consume these technologies. So, to align the name of our group with the common organizational group name of our community members, we have chosen this name for our group:
Application Developer Projects Group (or the more casual name, App Dev Group)
This group is a loose knit collection of projects which people often view as their development stack:
- Seam
- JBoss Tools
- Weld (CDI)
- RichFaces (JSF)
- Hibernate Validator (Bean Validation)
- Hibernate (JPA)
- Hibernate Search
- ...perhaps others
We also recently formed the JBoss Testing Group that encompasses Arquillian, ShrinkWrap, JSFUnit, and other testing tools. Some of us are a part of that group too, myself included.
When we address this audience, or seek to describe where we fit in the JBoss community, we can really establish the connectedness by using the term App Dev
, or Application Developer Projects, to show we are thinking about the concerns across technologies. So there you have it, our group name.