Production Leadership Meeting Agenda November 28/29, 2009 00:00:00 UTC

[Mark Dexter]

Chairman, Mark Dexter
Attendees,
* Chris Davenport
* Ole Bang Ottosen
* Sam Moffatt
* Mark Dexter
* Ron Severdia
* Louis Landry

Apologies,
* Ian MacLennan

Topics
1. Previous Meeting Followup
A. Joomla! 1.6 Release Schedule and Process

* Update on progress and discussion on timing.
o Release is moving along slow but steady.
* Is Release Team approach working? Current Release Team members
have either resigned or don't appear to have the time or interest to
continue.
o We need to think about whether the approach is the right
approach and we just need different members or whether we need a new
approach.
o Will try to update the Google doc with complete list of
tasks to be done for 1.6.
* Should we change the name to 2.0 and clarify goals for this
release? Specifically, is 1.6/2.0 an "interim" release or do we expect
it to be the major Joomla! version that everyone should upgrade to?
(related to Amy's post in Mootools 1.2 discussion)
o Name change related to MT decision. Tabled for now.
Concern about all of the discussions and docs about version 1.6 and
the impact of changing this.
o We agreed that 1.6 is not an "interim" release.

B. Production Working Group Budget for 2010

* Are we ready to finalize this?
o Chris and Mark will prepare a final budget proposal and
post to the list.

C. Developer Site / Joomla! Labs Planning

* Sam is upgrading servers over next 2 weeks -- progress report
o SVN moved to new site. Still working out minor kinks.
* Near-term plan
o Goal to have it live by 12/4 (NYC conference)
* Announcement for NYC?
o Hopefully will be functioning by then.

2. New Business or Topics
A. Mootools 1.2 for Joomla! Version 1.5 discussion of options:

We discussed the following options and agreed that we weren't ready to
make the decision yet. Maybe in NY.

1. Do nothing in 1.5
1. Pros: simple, easy, doesn't break current sites
2. Cons: doesn't address the problem. Ignores the current
situation with MT 1.1 causing compatibility and support issues.
2. Create a new 1.5 branch that supports 1.2
1. Pros: allows existing users to continue with MT 1.1
2. Cons: Major confusion in the community about competing 1.5
versions. Caused major headaches when Mambo did something similar.
3. Add 1.2 library to 1.5.16 (alongside 1.1) but continue to use
1.1 in core
1. Pros: trying to be "best of both worlds"
2. Cons: puts onus on website admins instead of devs. Could
cause confusion and support problems when sites break.
4. Create an "official" extension to add 1.2
1. We discussed the possibility of combining this with option
#5 to create an interim solution until option #5 was ready to go.
Perhaps in the form of a plugin extension.
5. Go "all in" and user MT 1.2 for next 1.5 version (1.5.16 or
whatever)
1. Pros: Clear, simple, provides devs with latest MT version,
fixes current compatibility issues with other JS libraries.
2. Cons: Could cause problems for existing users who upgrade
and have problems. Could make users stay at 1.5.15 version and cause a
problem if there is a security issue with 1.5.15. (Could be addressed
by option to provide a security patch for 1.5.15 in this scenario.)
6. Do a 1.6 release that includes MT 1.2 and some other
enhancements as a bridge to the next major release (formerly known as
1.6).
1. Pros: Provides a way forward with MT 1.2 and potentially
an improved Joomla! version sooner than current 1.6.
2. Cons: Could draw effort away from current 1.6 release and
further delay that release.