|
THE WEEK IN REVIEW
Another week has passed for Team GroupJive. Good news, we've made our race day plans. We are focused now on the areas most important to the "Drive to 1.5", namely, putting our car on the track.
During this last week, GroupJive specifically outlined our goals and a plan of action. This plan and Roadmap will brings us together to achieve a "stable"
GroupJive 1.5.
It's official... we are now running laps on the test track. The first and highest priority for the team is TESTING and BUG FIXING. It's number 1 !!! So please help us "tune up" GroupJive quickly. Review the:
- Stable Stack here
- Team Goals and Roadmap (our first draft) will be posted soon at GroupJive.org.
This week saw the following achievements at Team GroupJive:
- A unified plan of action on which to move forward (Stable GroupJive 1.5 and beyond)
- A division of team resonsibilities to make better use of our resources
- A Stable Stack from which to declare GroupJive 1.5 stable (here for Stable Stack)
- A redesigned Forge that takes advantages of the numerous capabilities of the GForge platform
- A "compiled-it-ourselves" SVN version of FireBoard (dated 20070708) to provide a more current FB release to the team for testing (email only - contact wwvine if you didn't receive it)
- A "latest" release of GroupJive 1.5 (rev 130) which can be downloaded from (FRS > here) -OR- (via webDAV or SVN > here)
ALSO: there is renewed energy being put into the GroupJive.org site as well as the "publicly viewable" pages at joomlacode.org/gf/project/groupjive. One of the "very important" topics discussed in our most recent leadership meeting was how to improve and sustain a "good quality and developer friendly public image" for GroupJive. Here are some of the action steps we have decided to take:
- FAQ >>> David Freund has taken leadership of developing an FAQ using EasyFAQ. It was determined that GroupJive users we're not finding help easily and sometimes not even making an effort on our Boards. To address this David volunteered to "clean up" our help and support content (please give your input to it's design) and help David here
- FAQ >>> David Freund has suggested that we inventory and clean up our Discussion Boards to help in the FAQ effort. If you are willing to give some time and contribute to that effort... please contact David.
- BUGS >>> We have redirected all BUG reporting to http://joomlacode.org/gf/project/groupjive/tracker/ (which is now publicly accessible)
- FEATURES >>> We have asked all feature requests go to http://joomlacode.org/gf/project/groupjive/tracker/ (which is now publicly accessible)
TRANSLATION
>>> We have named Hans Vos as our Translation Group Leader. If you are working in translation, please contact Hans
DEVELOPMENT
DEVELOPERS >>> Please check your BUG assignments in the GForge. All BUGS and FIXES should be tracked in GForge at Tracker.
BIG NEWS
One special turn of events deserves specific notice this week. Community Builder has given GroupJive the OK to use their plug-in system as the model for our own plugin system (beginning GroupJive 1.6+). This is a significant blessing to the GroupJive team and we would like to thank Beat and the entire Community Builder team for their generosity and genuine support of "open source". Thanks CB!
Thank you everyone.
As we complete this effort to "stabilize" GroupJive 1.5 we also look forward to development of GroupJive 1.6. Everyone has asked what the future is beyond 1.5 stable. Our Roadmap includes development of a plug-in system, compatibility with Joomla! 1.5 and more. As soon as GroupJive 1.5 is stable, we can move forward on these outstanding goals.
Thanks to everyone on the team for a great week.
Sincerely,
Team GroupJive
|
