[TYPO3-dam-devel] Concerning DAM / Releases / Team / Workflow

[Benjamin Mack]

Hey guys,

I have a few general notes about the DAM and how we should proceed.

=== DAM Team ===

Either way, if we open up the DAM Team List or not, how is the commiting 
and fixing handled? Do we have something like in the core list, where 
there need to be +1, one by a DAM Team Developer and one other? And 
then: Who is in the DAM Team anyway? Who is allowed to commit things 
etc? I think we should clarify stuff like that before we open up the 
list. Maybe we need a DAM Team, some general guidelines on how the whole 
workflow of sending patches in etc. is handled.

=== DAM Releases ===

One thing I struggled with a bit is the way how DAM releases are 
handled. Obviously I'm not too long in the game yet, but seriously, we 
do we need to fix 1.0 bugs if there is a 1.1 release coming that is only 
fixing bugs? To be honest, this blocks me from fixing bugs since I need 
to have a working 1.0 installation, 1.1 installation etc. So I propose this:

* We leave 1.0, and go with 1.1 as the main foundation. Why? everyone 
who uses 1.0 for the last 2 years obviously can either upgrade if he 
wants to use our work or stay with 1.0... because: 1.0 worked for him 
for two years so far ;-).

* We start planning 1.2 with having a minimal requirement of TYPO3 4.2 
(or 4.1) in mind, so we can really start on integrating the DAM better 
in the rest of the TYPO3 package (I'm not talking about having the DAM 
as a sysext, but I think you all know what I mean). Everyone who does 
not or cannot upgrade to 4.2 still can use DAM 1.1 which DOES work, right?

We gotta make decisions here, and if we don't move forward here, we'll 
be doomed for eternity and further development won't speed up as fast as 
it could. Remember, we're not in the core here, so 
backwards-compatibility is important, but not TOO important.

Just my thoughts here...

-- 
greetings,
benni.
-SDG-