Hi,
What works well for team updates (in addition to the wiki and email)
at Eclipse are weekly calls and I am going to start holding one each
week. Those who want to participate can, and the call will be recorded
so people can listen at their leisure and follow up with questions on
the mailing list. I find this to be very effective for some of the
Eclipse projects as it's almost like a weekly scrum meeting.
Benjamin, Igor and myself have been doing a lot of work to get 3.x
fixed up, integrated well with m2eclipse (and all embedded cases can
follow in our footsteps) and getting to the point where 3.x can
behave as a real replacement for 2.x. If folks want to get involved
now is the time, and the call will be a good way for people to assess
where we are. The following week there will be a mild deluge of wiki
entries and emails regarding 3.x but the call will be a good initiation.
I'll propose this as a time:
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=6&day=4&hour=15&min=0&sec=0&p1=250&p2=224&p3=195&p4=240
Call will probably be 60-90 minutes.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more
examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
