tx_party - Extension

[Ronald Steiner]

Hi List,

does some one happen to know the where about of the "tx_party" Extension
and the entire "party" project. David Bruehlmeier put a lot of effort in
this project.
I think the idea of having a common framework to handle data of people
like mail, name, birth date and joining together the various information
like be_users, fe_users, newsletter-lists, ... is brilliant and very
promising.
I read the Wiki and the team page of the project:
http://wiki.typo3.org/index.php/Party_Information_Framework
But it seams like there is not much change these days.

Is the project still alive? Who is working on it currently?
How can I support the project? Maybe a good defined programming task?

How about the authors of other extensions, like tt_address,
direct_mail_subscription, sp_directory, sa_adressexport,
sr_email_subscribe, gb_newsletter, sg_adress, ast_addresszipsearch,
m1address_us, cl_company_database, csextfeadr, address, rs_userimp,
dmaddredit, emailimport, dublefinder, icr_be_addr_dmail_cat,
kj_tt_address_mailflag, contactlist, feuserextrafields, sg_userdata,
eu_birthdays, bzd_staff_directory, ....
What do you think about this project? Is it promising in your eyes also?

Has anybody already tested the tx_party extension? What are your
impressions? Is it a good basis? Was it already possible to include
newsletters and other extensions to it?

greetings

Ron
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Christoph Koehler]

In article
<mailman.1.1204739130.23885.typo3-team-extension-coordination@...
fielders.de> "Dr. Ronald P. Steiner" <Ronald.Steiner@...>
wrote:
>  Hi List,

>  does some one happen to know the where about of the "tx_party"
> Extension and the entire "party" project. David Bruehlmeier put a lot
> of effort in this project.
>  I think the idea of having a common framework to handle data of
> people like mail, name, birth date and joining together the various
> information like be_users, fe_users, newsletter-lists, ... is
> brilliant and very
>  promising.
>  I read the Wiki and the team page of the project:
>  http://wiki.typo3.org/index.php/Party_Information_Framework
>  But it seams like there is not much change these days.

>  Is the project still alive? Who is working on it currently?
>  How can I support the project? Maybe a good defined programming task?

>  How about the authors of other extensions, like tt_address,
> direct_mail_subscription, sp_directory, sa_adressexport,
> sr_email_subscribe, gb_newsletter, sg_adress, ast_addresszipsearch,
> m1address_us, cl_company_database, csextfeadr, address, rs_userimp,
> dmaddredit, emailimport, dublefinder, icr_be_addr_dmail_cat,
> kj_tt_address_mailflag, contactlist, feuserextrafields, sg_userdata,
> eu_birthdays, bzd_staff_directory, ....
>  What do you think about this project? Is it promising in your eyes
>  also?

>  Has anybody already tested the tx_party extension? What are your
> impressions? Is it a good basis? Was it already possible to include
> newsletters and other extensions to it?

>  greetings

>  Ron

Ron,

David gave the development over to the Web-Empowered Church and agreed
to rename it wec_people. I am currently working on it. We are planning
on finalizing the data model next and implement the extension into a
simple application to assess what needs to be done on the API level.
The programming tasks are still largely the same as before, so if you
are interested in working on something specific, let me know, I am
sure we can make that happen.

Thanks for the interest!

Christoph

--
I'm using an evaluation license of nemo since 268 days.
You should really try it!
http://www.malcom-mac.com/nemo

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Ronald Steiner]

Hi Christoph,

nice to hear, that the project is still alive. I already know some
Web-Empowered Church extensions and they all seem really good. So the
project looks quite in good hands.
Is there any new project page?
Are there already extensions that use wec_people?
How many people are currently programming on wec_people? What is the
current status? Is there a plan when it will be released?
A good "party" extension is a really important thing for so many purposes.

greetings

Ron

>
> Ron,
>
> David gave the development over to the Web-Empowered Church and agreed
> to rename it wec_people. I am currently working on it. We are planning
> on finalizing the data model next and implement the extension into a
> simple application to assess what needs to be done on the API level.
> The programming tasks are still largely the same as before, so if you
> are interested in working on something specific, let me know, I am
> sure we can make that happen.
>
> Thanks for the interest!
>
> Christoph
>
>

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Christoph Koehler]

Ron,


In article
<mailman.1.1204747236.19514.typo3-team-extension-coordination@...
fielders.de> "Dr. Ronald P. Steiner" <Ronald.Steiner@...>
wrote:
>  Hi Christoph,

>  nice to hear, that the project is still alive. I already know some
> Web-Empowered Church extensions and they all seem really good. So the
> project looks quite in good hands.

Thanks for the compliment!
>  Is there any new project page?

There is <http://svn.webempoweredchurch.org/wec_people> which is just
the code. There is no separate project page.
>  Are there already extensions that use wec_people?

No, but there is a simple one in planning. wec_map indirectly uses
wec_people; more specifically, wec_people uses wec_map to map address
already. That stuff with some other smaller bugfixes is in SVN.
>  How many people are currently programming on wec_people?
Mainly just me. We have help offers from other people and some other
team members that will help out once it's needed.
>  What is the  current status?

Mostly still planning and strategy. It's a big project, so you can
kinda get lost in it. We are going to make an extension that will use
it and judge from that what all needs to be done. Our main goal will
be a Church Management System built on top of it and we're still
looking at all the options out there.
>  Is there a plan when it will be released?

Nope. Feel free to play with the code though. It's pretty complete as
far as records in the BE go.
>  A good "party" extension is a really important thing for so many
>  purposes.

Yep, we agree.

Christoph

--
I'm using an evaluation license of nemo since 268 days.
You should really try it!
http://www.malcom-mac.com/nemo

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[David Bruehlmeier]

Hi Ron,

my original intent for the Party Information Framework was to spark a
true team effort to create a stable base for all party-related issues.
Unfortunately, that never happened.

The Web Empowered Church came in as a rescue since they have a need to
solve this problem in order to build a church management system. That's
why they agreed to take over the project, as Christoph already explained.

I'm sorry the wiki did not reflect this information. I have just updated
the site.

I'm obviously still interested in the project and willing to help with
the design and/or testing, but I won't have time to do actual
development work.

Greetings,
Dave
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Ronald Steiner]

Hi Dave,

did you ever get some feedback of other programmers? Why do the
tt_address programmers don't join in the project? Why has no one ever
programmed a newsletter for tx_party?

Really strange to me why so view people are interested in such an system.

greetings

Ron


David Bruehlmeier schrieb:

> Hi Ron,
>
> my original intent for the Party Information Framework was to spark a
> true team effort to create a stable base for all party-related issues.
> Unfortunately, that never happened.
>
> The Web Empowered Church came in as a rescue since they have a need to
> solve this problem in order to build a church management system. That's
> why they agreed to take over the project, as Christoph already explained.
>
> I'm sorry the wiki did not reflect this information. I have just updated
> the site.
>
> I'm obviously still interested in the project and willing to help with
> the design and/or testing, but I won't have time to do actual
> development work.
>
> Greetings,
> Dave

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[David Toshack]

Christoph Koehler wrote:

> David gave the development over to the Web-Empowered Church and agreed
> to rename it wec_people.

Hi Christoph,

Would you be willing to add the WEC specific features as addon
extensions to tx_party and work with and adhere to the Extension
Coordination Team best practices for tx_party itself?

I would assume in doing so you'd receive a lot more help from all the
other party-related extension developers. But not just that, its in the
best interests of the entire TYPO3 community and we would all be
eternally grateful! :-)


Cheers,
David
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Christoph Koehler]

In article
<mailman.1.1208149697.8914.typo3-team-extension-coordination@...
ielders.de> David Toshack <david@...> wrote:
>  Christoph Koehler wrote:
>>   David gave the development over to the Web-Empowered Church and
>> agreed to rename it wec_people.

>  Hi Christoph,

>  Would you be willing to add the WEC specific features as addon
> extensions to tx_party and work with and adhere to the
> ExtensionCoordination Team best practices for tx_party itself?

>  I would assume in doing so you'd receive a lot more help from all
> the other party-related extension developers. But not just that, its
> in the best interests of the entire TYPO3 community and we would all
> beeternally grateful! :-)

David,

tx_party is now wec_people. That's all, just a naming change. It will
be very general and you'll be able to use it in other extensions.

Christoph

--
I'm using an evaluation license of nemo since 307 days.
You should really try it!
http://www.malcom-mac.com/nemo

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Daniel Bruessler-4]

Hello Christoph,

just a question about the documentation on the wiki-page:
http://wiki.typo3.org/index.php/Party_Information_Framework

what should be changed here?
Cheers!
Daniel


> David,
>
> tx_party is now wec_people. That's all, just a naming change. It will
> be very general and you'll be able to use it in other extensions.
>
> Christoph
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Franz Koch-4]

Hi guys,
>>  I would assume in doing so you'd receive a lot more help from all
>> the other party-related extension developers. But not just that, its
>> in the best interests of the entire TYPO3 community and we would all
>> beeternally grateful! :-)
>
> David,
>
> tx_party is now wec_people. That's all, just a naming change. It will
> be very general and you'll be able to use it in other extensions.

why does the extension name need to be changed? I can only speak for
myself, but if there where two extensions in TER doing the same, one
called 'tx_party' and one called 'wec_people' - I'd definitely install
'tx_party', because 'wec_people' is assuming that it's not a general
extension due to the personalized extension key (like it is for 98% of
the extensions in TER that are rubbish).

The only extension with a extension key like 'wec_whatever' that I've
tested is 'wec_maps' - and that only because of 'tx_cal' (which is also
WEC powered, but doesn't have a personalized ext key).

So I share Davids thoughts - you will get much more support if the
extension key is not 'wec_whatever'. I think everybody would benefit if
the name of the 'main' party extensions remains 'tx_party' and that
'wec_people' is a addon, preconfiguring 'tx_party' for
churches/ministrys, that are to specific for a general party extension.

That's at least for me the idea behind a ECT driven extension.

--
kind regards,
Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Christoph Koehler]

In article
<mailman.1.1208247267.11649.typo3-team-extension-coordination@...
fielders.de> Franz Koch <typo.removeformessage@...> wrote:

>  Hi guys,
>>>    I would assume in doing so you'd receive a lot more help from
>>> all the other party-related extension developers. But not just
>>> that, its in the best interests of the entire TYPO3 community and
>>> we would all beeternally grateful! :-)
>>  
>>   David,
>>  
>>   tx_party is now wec_people. That's all, just a naming change. It
>> will be very general and you'll be able to use it in other
>>  extensions.

>  why does the extension name need to be changed? I can only speak for
> myself, but if there where two extensions in TER doing the same, one
> called 'tx_party' and one called 'wec_people' - I'd definitely
> install 'tx_party', because 'wec_people' is assuming that it's not a
> general extension due to the personalized extension key (like it is
> for 98% of the extensions in TER that are rubbish).

>  The only extension with a extension key like 'wec_whatever' that
> I've tested is 'wec_maps' - and that only because of 'tx_cal' (which
> is also WEC powered, but doesn't have a personalized ext key).

>  So I share Davids thoughts - you will get much more support if the
> extension key is not 'wec_whatever'. I think everybody would benefit
> if the name of the 'main' party extensions remains 'tx_party' and
> that 'wec_people' is a addon, preconfiguring 'tx_party' for
> churches/ministrys, that are to specific for a general party
>  extension.

David asked WEC to take over tx_party because, as he saw it, there was
almost no support from anyone to help develop. There won't be a
tx_party, so you can't install it. If you want the huge data model for
managing party related information, you will install wec_people. We
renamed it because we are now the main developers, again because David
didn't see as much support from other developers as he needed. This is
really just a name change because we are developing it now, there
won't be functional changes. Cal is developed by Mario who isn't
affiliated with WEC, and Jeff, who is, so it's not a WEC extension and
thus not named wec_cal.

Christoph

--
I'm using an evaluation license of nemo since 308 days.
You should really try it!
http://www.malcom-mac.com/nemo

_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Niels Pardon-2]

Hi,

Franz Koch schrieb:

> why does the extension name need to be changed? I can only speak for
> myself, but if there where two extensions in TER doing the same, one
> called 'tx_party' and one called 'wec_people' - I'd definitely install
> 'tx_party', because 'wec_people' is assuming that it's not a general
> extension due to the personalized extension key (like it is for 98% of
> the extensions in TER that are rubbish).
>
> The only extension with a extension key like 'wec_whatever' that I've
> tested is 'wec_maps' - and that only because of 'tx_cal' (which is also
> WEC powered, but doesn't have a personalized ext key).
>
> So I share Davids thoughts - you will get much more support if the
> extension key is not 'wec_whatever'. I think everybody would benefit if
> the name of the 'main' party extensions remains 'tx_party' and that
> 'wec_people' is a addon, preconfiguring 'tx_party' for
> churches/ministrys, that are to specific for a general party extension.
>
> That's at least for me the idea behind a ECT driven extension.

First, I fully agree with Franz.

I was at David Brühlmeier's talk at T3DD07 and as far as I remember
there were some people who wanted to help in developing tx_party. There
were also some names in the TYPO3 wiki who offered there help.

But I didn't see any progress in tx_party since T3DD07 and that's still
the case since it is renamed to wec_people. One reason was may be that
for a long time the OASIS standard wasn't officially released. That
changed on 19. March 2008 and still nothing happened.

I think that, if there would have been more clearly defined tasks there
would have been more people who would have helped in developing
tx_party. I thought that David Brühlmeier as the former project leader
would have taken this step and defined some tasks.

If I had some clearly defined tasks to choose from I would have taken
one off the list and helped developing it. But I didn't know where to start.

As the demand for such a extension increases obviously (see the posts on
the mailling lists the last months asking for tx_party) I think it is
more than ever an important topic for the ECT. And I think it was a bad
idea to take tx_party out of the ECT and moving it out to the WEC.

Just my 2 cents.

Greets,

Niels
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Jeff Segars]

Hey Niels,
I'll jump in on Christoph's behalf since he's in class for a while.

> Franz Koch schrieb:
>
>> why does the extension name need to be changed? I can only speak for
>> myself, but if there where two extensions in TER doing the same, one
>> called 'tx_party' and one called 'wec_people' - I'd definitely install
>> 'tx_party', because 'wec_people' is assuming that it's not a general
>> extension due to the personalized extension key (like it is for 98% of
>> the extensions in TER that are rubbish).
>>
>> The only extension with a extension key like 'wec_whatever' that I've
>> tested is 'wec_maps' - and that only because of 'tx_cal' (which is
>> also WEC powered, but doesn't have a personalized ext key).
>>
>> So I share Davids thoughts - you will get much more support if the
>> extension key is not 'wec_whatever'. I think everybody would benefit
>> if the name of the 'main' party extensions remains 'tx_party' and that
>> 'wec_people' is a addon, preconfiguring 'tx_party' for
>> churches/ministrys, that are to specific for a general party extension.
>>
>> That's at least for me the idea behind a ECT driven extension.

I'll just offer one other bit of information on the naming change. With
the rename, the main desire wasn't to put wec in front of the extension.
  For native English speakers, calling the extension "party" has a
strange connotation. People was a more natural fit for the primary usage
so that was really the main point of the rename.  Since we were renaming
it anyway, we just brought it under the wec namespace.

If there really are major objections to having wec in front of the
extension name, we can certainly revisit that.  The WEC leadership will
be much more likely to support this if its a shared development effort
with the rest of the TYPO3 community (as in the case of Calendar Base)
as opposed to renaming something that is completely an internal project.

> First, I fully agree with Franz.
>
> I was at David Brühlmeier's talk at T3DD07 and as far as I remember
> there were some people who wanted to help in developing tx_party. There
> were also some names in the TYPO3 wiki who offered there help.
>
> But I didn't see any progress in tx_party since T3DD07 and that's still
> the case since it is renamed to wec_people. One reason was may be that
> for a long time the OASIS standard wasn't officially released. That
> changed on 19. March 2008 and still nothing happened.
>
> I think that, if there would have been more clearly defined tasks there
> would have been more people who would have helped in developing
> tx_party. I thought that David Brühlmeier as the former project leader
> would have taken this step and defined some tasks.

The wiki still has a wealth of party information, including the
components and subtasks that David originally defined.  He indicated on
several occasions that his efforts to define the roadmap and the
different components that people could work on resulted in no community
participation at all.

I don't say that to point fingers, because I'm also part of that
community. The history is just that the development community did not
get involved for whatever reason despite initial interest on the mailing
lists and at various events. David needed to move on to other things and
handed development to WEC since there wasn't another clear group that
could pick it up.

We haven't moved at the pace we'd like due to other projects, but at
least there's still a heartbeat :)

> If I had some clearly defined tasks to choose from I would have taken
> one off the list and helped developing it. But I didn't know where to
> start.

Does that offer still stand? :)

> As the demand for such a extension increases obviously (see the posts on
> the mailling lists the last months asking for tx_party) I think it is
> more than ever an important topic for the ECT. And I think it was a bad
> idea to take tx_party out of the ECT and moving it out to the WEC.


Practically speaking, I'm not sure what moving it out of ECT and into
WEC means.  The Subversion repository has moved, but is still publicly
available and we're happy to give any contributing developer write
access. We're certainly not trying to close the project to the outside
world or tailor it to only our needs.

WEC is all for partnering with others in the TYPO3 Community for
development (as we have with Calendar Base) so lets figure out what we
can do as a team to build on this discussion and push tx_party /
wec_people ahead in concrete ways.

Who is willing to commit to help?  What areas of tx_party / wec_people
are of the most interest to you (reporting, synchronization, frontend
views, etc)?

Thanks,
Jeff
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Niels Pardon-2]

Hi Jeff,

Jeff Segars schrieb:
> If there really are major objections to having wec in front of the
> extension name, we can certainly revisit that.  The WEC leadership will
> be much more likely to support this if its a shared development effort
> with the rest of the TYPO3 community (as in the case of Calendar Base)
> as opposed to renaming something that is completely an internal project.
>

I still think such a extension is of general interest and this should be
  already noticable from the extension name.

>
>> If I had some clearly defined tasks to choose from I would have taken
>> one off the list and helped developing it. But I didn't know where to
>> start.
>
> Does that offer still stand? :)

Yes. If there's a list of clearly defined tasks and I find some tasks
that I'm able to implement, then I will help.

The current TODO.txt offers a bit too less information to me. If this
entries would be described a bit more detailed I would have a better
starting point.

>> As the demand for such a extension increases obviously (see the posts
>> on the mailling lists the last months asking for tx_party) I think it
>> is more than ever an important topic for the ECT. And I think it was a
>> bad idea to take tx_party out of the ECT and moving it out to the WEC.
>
>
> Practically speaking, I'm not sure what moving it out of ECT and into
> WEC means.  The Subversion repository has moved, but is still publicly
> available and we're happy to give any contributing developer write
> access. We're certainly not trying to close the project to the outside
> world or tailor it to only our needs.

Well, that's how it looked like when this movement and renaming has
taken place.

 > Who is willing to commit to help?  What areas of tx_party / wec_people
 > are of the most interest to you (reporting, synchronization, frontend
 > views, etc)?

As you might know I'm a developer of the seminars extension where we
already handle party related data with some limitations. I'm interested
in getting the basic model of tx_party into a release so it is
officially usable in this case through an interface with seminars.

So as stated above if there are tasks that shorten the time to release
and I'm able to implement them, then I will help.

Greets,

Niels
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Steffen Kamper-2]

"Christoph Koehler" <christoph.koehler@...> schrieb im Newsbeitrag
news:mailman.1.1204744837.15138.typo3-team-extension-coordination@......

> In article
> <mailman.1.1204739130.23885.typo3-team-extension-coordination@...
> fielders.de> "Dr. Ronald P. Steiner" <Ronald.Steiner@...>
> wrote:
>>  Hi List,
>
>>  does some one happen to know the where about of the "tx_party"
>> Extension and the entire "party" project. David Bruehlmeier put a lot
>> of effort in this project.
>>  I think the idea of having a common framework to handle data of
>> people like mail, name, birth date and joining together the various
>> information like be_users, fe_users, newsletter-lists, ... is
>> brilliant and very
>>  promising.
>>  I read the Wiki and the team page of the project:
>>  http://wiki.typo3.org/index.php/Party_Information_Framework
>>  But it seams like there is not much change these days.
>
>>  Is the project still alive? Who is working on it currently?
>>  How can I support the project? Maybe a good defined programming task?
>
>>  How about the authors of other extensions, like tt_address,
>> direct_mail_subscription, sp_directory, sa_adressexport,
>> sr_email_subscribe, gb_newsletter, sg_adress, ast_addresszipsearch,
>> m1address_us, cl_company_database, csextfeadr, address, rs_userimp,
>> dmaddredit, emailimport, dublefinder, icr_be_addr_dmail_cat,
>> kj_tt_address_mailflag, contactlist, feuserextrafields, sg_userdata,
>> eu_birthdays, bzd_staff_directory, ....
>>  What do you think about this project? Is it promising in your eyes
>>  also?
>
>>  Has anybody already tested the tx_party extension? What are your
>> impressions? Is it a good basis? Was it already possible to include
>> newsletters and other extensions to it?
>
>>  greetings
>
>>  Ron
>
> Ron,
>
> David gave the development over to the Web-Empowered Church and agreed
> to rename it wec_people. I am currently working on it. We are planning
> on finalizing the data model next and implement the extension into a
> simple application to assess what needs to be done on the API level.
> The programming tasks are still largely the same as before, so if you
> are interested in working on something specific, let me know, I am
> sure we can make that happen.
>
> Thanks for the interest!
>
> Christoph
>
> --
> I'm using an evaluation license of nemo since 268 days.
> You should really try it!
> http://www.malcom-mac.com/nemo
>

hi,

i don't have a problem in renaming. This is kind of sponsoring and ensure
that the ext will be developed also if noone of ECT is involved. IMHO Wec
does a lot for the community and i'm happy that such organisation does such
great efforts for the community.

As Jeff mentioned that doesn't mean that other devs can help, so please feel
free and contact him for support.

vg Steffen


_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[David Toshack]

The Web Empowered Church do a lot for the community and their extensions
are excellent! A lot of them are even very generic and I applaud
Christoph and the team for that. Kudos to you guys!

The problem, however, is that you only have to look at the extension
repository to see that there are literally _hundreds_ of excellent,
generic extensions out there that do the same thing.

Thats why the ECT was started. To define best practises for extension
development, and coordinate the efforts of the community in developing them.

This is a _really_ tough job in such a diverse community. But when a
project that is intended to be such a generic extension doesn't follow
their best practices; what hope do we have?!

Also, I don't believe sponsorship should be scattered throughout the
code itself. In any way, shape or form. Code is hard enough to follow as
it is. There are proper channels for that and probably more efficient
ones too.

Christoph and Jeff, I don't mean to criticize. I know sometimes its a
lot easier to "do it your own way". Even if its for the benefit of
everyone. I honestly think the WEC is an invaluable contributor to the
TYPO3 community and I am often in ore of your contributions and
community spirit. We all thank you!

I also believe you deserve to be repaid in some way for your efforts.
Maybe through sponsorship or some sort of miniature Christoph or WEC
team figurines we can all worship! :-D

Seriously though, the ECT has such a huge job on its hands, we _really_
need to work with them every step of the way on this sort of development
if this team is to accomplish its goals. That includes abiding by their
best practices for coordinated extension development. You're also quite
welcome to help contribute to these.

Although it was the tx_party/wec_people extension that triggered this
argument, please don't feel ostracised. There are a multitude of
extension developers this applies to. YOU KNOW WHO YOU ARE! :-P  :-D

Even a quick glance at the extension repository will bring home the fact
that the ECT is an essential part of the TYPO3 structure and I hope this
post motivates more developers out there to work closer with the ECT and
help them accomplish their goals. They're doing it for all of us!


Cheers,
David
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Jeff Segars]

Niels Pardon wrote:
> As you might know I'm a developer of the seminars extension where we
> already handle party related data with some limitations. I'm interested
> in getting the basic model of tx_party into a release so it is
> officially usable in this case through an interface with seminars.

Right now, I'm focusing on backend usability for basic data entry. I
think the data model itself is pretty solid, but it results in a user
interface that is too complex.

I'm thinking we'll need to create some custom components so if you have
any experience with that, its certainly welcome. Another set of eyes on
the data model for any missing fields that seminars really needs could
also be good.

You can grab the latest T3X from [1].


> So as stated above if there are tasks that shorten the time to release
> and I'm able to implement them, then I will help.

David split things into 5 components originally (core, view,
syncronizing, reporting, and migration) and added work packages within
each component so that's probably the best place to grab high level
tasking.  You can find this on the wiki at [2].  Sounds like most of
your needs for seminars will be covered by the core extension.

Thanks,
Jeff




[1] http://svn.webempoweredchurch.org/wec_people
[2] http://wiki.typo3.org/index.php/Party_Information_Framework#Components
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[David Bruehlmeier]

Hi Niels,

> I think that, if there would have been more clearly defined tasks there
> would have been more people who would have helped in developing
> tx_party. I thought that David Brühlmeier as the former project leader
> would have taken this step and defined some tasks.
>
> If I had some clearly defined tasks to choose from I would have taken
> one off the list and helped developing it. But I didn't know where to
> start.

Sorry, but this is simply not true. I wanted the Party Information
Framework to be a team effort from the very beginning and stated so on
every occasion. I tried hard to split the project up into well defined
parts so it would be easy to contribute. Just have a look at the wiki:

I defined 5 components:
http://wiki.typo3.org/index.php/Party_Information_Framework#Components

and workpackages for each component, e.g.:
http://wiki.typo3.org/index.php/Tx_party#Work_Packages

Now, what else would you need to get started? If this was not enough
information, why didn't you just ask?

Yes, a lot of people were/are interested in this project, but when it
came to get things done, nobody was around. This was frustrating and so
I was more than glad when WEC agreed to take over this project. At least
not all this work had been in vain.

So if the WEC wants to rename the extension, that's their right. Whoever
makes the baby gets to name the baby.

Just my 5$...

Greetings, Dave
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Niels Pardon-2]

Hi David,

David Bruehlmeier schrieb:

> Sorry, but this is simply not true. I wanted the Party Information
> Framework to be a team effort from the very beginning and stated so on
> every occasion. I tried hard to split the project up into well defined
> parts so it would be easy to contribute. Just have a look at the wiki:
>
> I defined 5 components:
> http://wiki.typo3.org/index.php/Party_Information_Framework#Components
>
> and workpackages for each component, e.g.:
> http://wiki.typo3.org/index.php/Tx_party#Work_Packages
>
> Now, what else would you need to get started? If this was not enough
> information, why didn't you just ask?
>

First of all I really think you had a good plan. The presentation at
T3DD07 was very promising. What I described is just my opinion from my
limited point of view. So may be it is different from your or from
anybody else's point view.

I saw the information you've provided in the wiki including the work
packages. I thought the OASIS standard had to be finished first.

As I mentioned I didn't know where to start because it was still not
granular enough for me to get an idea of what to do. So I didn't feel
confident enough concerning my development skills to take a whole work
package or even only to participate in a work package.

And I'm still not confident because the tasks listed in the work
packages don't tell me anything. I would need a task (or tasks) that I
can overview and that is (are) telling me were to start. So I would need
some guidance to get into the code.

I hope this explanation helps you to understand my point although it
doesn't change the past.

Greets,

Niels
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

[Steffen Kamper-2]

"David Toshack" <david@...> schrieb im Newsbeitrag
news:mailman.1.1208309966.9495.typo3-team-extension-coordination@......

> The Web Empowered Church do a lot for the community and their extensions
> are excellent! A lot of them are even very generic and I applaud
> Christoph and the team for that. Kudos to you guys!
>
> The problem, however, is that you only have to look at the extension
> repository to see that there are literally _hundreds_ of excellent,
> generic extensions out there that do the same thing.
>
> Thats why the ECT was started. To define best practises for extension
> development, and coordinate the efforts of the community in developing
> them.
>
> This is a _really_ tough job in such a diverse community. But when a
> project that is intended to be such a generic extension doesn't follow
> their best practices; what hope do we have?!
>
> Also, I don't believe sponsorship should be scattered throughout the
> code itself. In any way, shape or form. Code is hard enough to follow as
> it is. There are proper channels for that and probably more efficient
> ones too.
>
> Christoph and Jeff, I don't mean to criticize. I know sometimes its a
> lot easier to "do it your own way". Even if its for the benefit of
> everyone. I honestly think the WEC is an invaluable contributor to the
> TYPO3 community and I am often in ore of your contributions and
> community spirit. We all thank you!
>
> I also believe you deserve to be repaid in some way for your efforts.
> Maybe through sponsorship or some sort of miniature Christoph or WEC
> team figurines we can all worship! :-D
>
> Seriously though, the ECT has such a huge job on its hands, we _really_
> need to work with them every step of the way on this sort of development
> if this team is to accomplish its goals. That includes abiding by their
> best practices for coordinated extension development. You're also quite
> welcome to help contribute to these.
>
> Although it was the tx_party/wec_people extension that triggered this
> argument, please don't feel ostracised. There are a multitude of
> extension developers this applies to. YOU KNOW WHO YOU ARE! :-P  :-D
>
> Even a quick glance at the extension repository will bring home the fact
> that the ECT is an essential part of the TYPO3 structure and I hope this
> post motivates more developers out there to work closer with the ECT and
> help them accomplish their goals. They're doing it for all of us!
>
>
> Cheers,
> David

Hi David,

i feel same. Ingo fights a long time for better extension keys as well.
IMHO there shouldn't be a prefix with name of company in extension key
itself, the key should express what extension does.
There are other information fields for extension, and i think that they
should get some new fileds like
* sponsor name
* sponsor link

So when you browser TER in future the Sponsor is more prominent which could
make it attractiv to sponsor extensions for companies, and they are happy
though the name is not in the key itself.

vg Steffen


_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination