[TYPO3-ect] Status of the party extension?

David Bruehlmeier typo3 at bruehlmeier.com
Sat Aug 4 09:28:36 CEST 2007


Hi all,

just got back from vacation.

The development of the Party Information Framework has come to a halt 
for the past few months due to personal reasons: I simply have too much 
on my agenda. Beside my full-time job, which is not related to TYPO3 and 
usually requires well beyond 100%, I'm in the last year of a master 
study, I'm the webmaster of our church, and I'm even trying to have a 
private life. My engagement for TYPO3 must fit in there somewhere 
between. Sometimes that works fine, recently it hasn't.

When I started the Party Information Framework, I have clearly stated 
that I want this to be a team effort. Why? Because I knew that I won't 
be able to sustain it myself. Still it seems that as of today, I'm the 
only active contributor. There have been a lot of interested people and 
also some feedback which I'm thankful for. But other than that, I feel 
I'm still a one-man-show.

This leaves me with a tough decision. I'm not able to continue like 
that. IMO, there are some options:

1. Drop it all together. The current situation with party related issues 
seems not perfect, but there are working solutions. So why bother?

2. Reduce the project to become a 5.0 initiative only. That would take 
some weight off my shoulders since I could concentrate on implementing 
the model without having to bother with view issues, be it in the 
backend or the frontend. Still, the problem remains that I will have 
very little time to spend on this. I need at least one committed 
co-developer.

3. Continue both, development for 4.x and 5.0. This scenario takes at 
least two committed developers. I would either drop out completely or 
reduce my engagement to coordination and modeling.

Before I make my decision, I would like to ask you for your opinion. And 
if you suggest option 2 or 3: Who is willing and has enough time to 
become a committed developer?

Regards,
Dave


More information about the TYPO3-team-extension-coordination mailing list