[TYPO3-ect] ECT becomes member of R&D

[David Toshack]

Elmar Hinz wrote:
> David Toshack wrote:
>> Hi Elmar,
>>
>> Many times I have been tempted to get in contact with extension
>> developers of similar extension functionality. Which I have done if
>> there is something simple I can do, but I would love to become more
>> involved in bringing these projects together from a slightly higher
>> level. Rather than code all these extension mergers myself I would like
>> the opportunity to get the ball rolling between the extension developers
>> themselves. As there are public extension release requirements that
>> state that you must be able to continue to support your extension, this
>> should not be an unrealistic goal.
>>
>> I have been tentative in doing so in the past. "Who am I to make work
>> for others?" Although there is a greater good, if it comes from a group
>> discussion in the ECT I would feel more justified in my approach.
>>
>> In an attempt to not tread on any toes, I am making myself available for
>> this type of cross extension coordination if these roles have not
>> already been filled. Or if they have, I would like to help wherever ECT
>> help is needed.
>>
>>
>> Cheers,
>> David
> 
> 
> Hallo David,
> 
> thank you for your offer of help. You see that nobody has directly answerd
> to your posting so far. I think that this is because your description of a
> role of cross extension coordination is unspecific for most people.
> Obviously you have a personal vision of this, because you speak of it.
> Maybe you can give some flesh to this term to enlighten what it is, what it
> is good for and how it would work.
> 
> Cheers
> 
> Elmar
> 

Hi Elmar,

I was thinking the same thing. This is my vision of the problem.

Too many times I see new extensions coming out that really shouldn't be
separate extensions. Maybe they are created with intent to be merged and
become obsolete, I don't know. But very often this _should_ be the case
and is not.


My vision of the process required would be to streamline extension
mergers and acquisitions as follows.

In the event of a new extension uploaded to the repository that extends
the functionality of another extension, I would contact the extension
developers directly involved and invite them to a discussion with the
ECT to get a basic consensus of a merge action required. Here would
probably be the best place for that, along with some irc or skype time.

Whether the outcome is that a new project is needed, or the developers
directly involved simply work it out between themselves. I would remain
involved enough to ensuring the wiki page keeps track of the progress,
and to keep the ball rolling. Not as an individual project leader, but
as an overall project coordinator. Maybe there could be a few of us
assigned to this role.

I would like to take on this role with the approval of the ECT. With a
bit of persistence we should be able to make many extensions in the
repository obsolete without losing any backward compatibility or
combined functionality.

I'm sure we could define a much more specific process than what I
described but I would love to get the ball rolling on this asap.

I look forward to hearing all your thoughts on this abstract process,
and maybe even refine it before commencement.


Cheers,
David