ECT - teamleaders
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
ECT - teamleaders
by Franz Holzinger
::
Rate this Message:
Hello,
is this page http://typo3.org/teams/extension-coordination-team/ still correct? Or is this outdated info? lib/div, xajax (Elmar Hinz) ... As fas as I have seen Elmar Hinz is not available. Party Information Framework (David Brühlmeier) ... Doesn't the WEC do this? - Franz _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Daniel Bruessler-4
::
Rate this Message:
Hello Franz and all,
yes, shure, Elmar didn't react since many months. And we cannot blame him, because he always said that his leaderships would end at 31th of December 2007. We just didn't believe it ;-) So after 6 months it would be good to vote for a new team-leader and create a forge-teampage. In my team (DocTeam) the forge-page is helping us very much. As candidates I see: * you, Franz Holzinger * David Toshack (Enhanced Rights Management in the wiki, Mail Framework) * Søren Andersen * Christoph Koehler from WEC * Christian Welzel (kickstarter__mvc) Cheers! Daniel > Hello, > > is this page > http://typo3.org/teams/extension-coordination-team/ > still correct? Or is this outdated info? > > lib/div, xajax (Elmar Hinz) ... As fas as I have seen Elmar Hinz is not > available. > > Party Information Framework (David Brühlmeier) ... Doesn't the WEC do this? > > > - Franz TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Christoph Koehler
::
Rate this Message:
In article
<mailman.1.1214208408.13172.typo3-team-extension-coordination@... fielders.de> Franz Holzinger <franz@...> wrote: > Hello, > is this page > http://typo3.org/teams/extension-coordination-team/ > still correct? Or is this outdated info? > lib/div, xajax (Elmar Hinz) ... As fas as I have seen Elmar Hinz is > notavailable. > Party Information Framework (David Brühlmeier) ... Doesn't the WEC > do this? > - Franz Wow, didn't know my name was still on the Forms library. I haven't worked on that in years. I think Jerome Schneider's formidable is a good forms lib and used by many, with active development. So if you can please take my name off, that would be nice. There hasn't been any activity for a long time. And WEC is indeed doing the Party Information Framework. Thanks! Christoph -- I'm using an evaluation license of nemo since 377 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 |
|
|
Re: ECT - teamleaders
by Daniel Bruessler-4
::
Rate this Message:
Hello,
what do you think, if I start next week creating a forge-project for ECT? ;-) But to clarify: I would not be the leader, just a member. Cheers! Daniel > In article > <mailman.1.1214208408.13172.typo3-team-extension-coordination@... > fielders.de> Franz Holzinger <franz@...> wrote: >> Hello, > >> is this page >> http://typo3.org/teams/extension-coordination-team/ >> still correct? Or is this outdated info? > >> lib/div, xajax (Elmar Hinz) ... As fas as I have seen Elmar Hinz is >> notavailable. > >> Party Information Framework (David Brühlmeier) ... Doesn't the WEC >> do this? > >> - Franz > > Wow, didn't know my name was still on the Forms library. I haven't > worked on that in years. I think Jerome Schneider's formidable is a > good forms lib and used by many, with active development. So if you > can please take my name off, that would be nice. There hasn't been any > activity for a long time. > > And WEC is indeed doing the Party Information Framework. > > Thanks! > > Christoph > TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by omic
::
Rate this Message:
It would be worth to redefine the goals of the ECT.
I found 2 pages about that: http://wiki.typo3.org/index.php/ECT/Homepage http://typo3.org/teams/extension-coordination-team/ Which projects are still alive? Some project could be remove from the list. http://wiki.typo3.org/index.php/ECT/Homepage#ProjectsTable_.2B_Goals As it seems to have no more energy going into the lib/div framework, I would suggest to help Jochen's effort with http://forge.typo3.org/projects/show/extension-gimmefive > what do you think, if I start next week creating a forge-project for > ECT? ;-) And what project are you thinking about? regards, Fabien > > Cheers! > Daniel > > >> In article >> <mailman.1.1214208408.13172.typo3-team-extension-coordination@... >> fielders.de> Franz Holzinger <franz@...> wrote: >>> Hello, >> >>> is this page >>> http://typo3.org/teams/extension-coordination-team/ >>> still correct? Or is this outdated info? >> >>> lib/div, xajax (Elmar Hinz) ... As fas as I have seen Elmar Hinz is >>> notavailable. >> >>> Party Information Framework (David Brühlmeier) ... Doesn't the WEC >>> do this? >> >>> - Franz >> >> Wow, didn't know my name was still on the Forms library. I haven't >> worked on that in years. I think Jerome Schneider's formidable is a >> good forms lib and used by many, with active development. So if you >> can please take my name off, that would be nice. There hasn't been any >> activity for a long time. >> >> And WEC is indeed doing the Party Information Framework. >> >> Thanks! >> >> Christoph >> TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Steffen Kamper-2
::
Rate this Message:
Hi,
the goal of ECT was to have a platform, where teams are build to develop extensions instead of 10 extensions doing all the same. I don't see ECT as a project for forge, it's more a communication channel. In the past ECT was more a support forum for lib/div, what wasn't the purpose of ECT. So imho ECT can live without a declared leader, it should be ruled by the devs here. vg Steffen _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Daniel Bruessler-4
::
Rate this Message:
Hello,
in my view a moderator is needed, maybe that's the best word for it. ECT has started as an OVERVIEW of current ongoings - and a mailinglist (I mean technically) cannot do this. lib/div was ONE project of ECT, one of several ones. For me forge is not "SVN with a bugtracker", out of my view it's a team-platform. fabien: * "It would be worth to redefine the goals of the ECT." * http://wiki.typo3.org/index.php/ECT/Homepage * Which projects are still alive? * I would suggest to help Jochen's effort with extension-gimmefive * forge-project for ECT? And what project are you thinking about? steffen: * the goal of ECT was to have a platform, where teams are build to develop extensions instead of 10 extensions doing all the same * communication channel * ECT can live without a declared leader, it should be ruled by the devs here Cheers! Daniel > Hi, > > the goal of ECT was to have a platform, where teams are build to develop > extensions instead of 10 extensions doing all the same. > I don't see ECT as a project for forge, it's more a communication channel. > > In the past ECT was more a support forum for lib/div, what wasn't the > purpose of ECT. > > So imho ECT can live without a declared leader, it should be ruled by the > devs here. > > vg Steffen > > TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Benjamin Mack-4
::
Rate this Message:
Hey all,
I'm not 100% in the ECT and what's going on there, but for me it seems like the ECT, mainly div/lib, missed its goal. I thought it should also be a starting point for migrating to 5.x, but there seems no communication between the teams. Also, I would love to have the ECT team work closer with the 4.x core team, so we can maybe integrate some cool things. Then, there are IMHO some crazy ideas like "div2007" that I think are just plainly wrong, as it is another dependency and some more extra you have to juggle around with versions, incompatibilities and the extensions (hard enough with TYPO3 4.1 and 4.2 already after updating). Developing extensions make it even harder then. "This extension only runs with TYPO3 4.0 and div2007 and lib2008" ;-) Why not finish div/lib and that's it then? It's been long enough in alpha/beta state now. However, "cal" from the ECT is great, but as you see, it also defined its own MVC framework again --- why reinvent the wheel again and again and not collaborate? (no offense to the cal guys, I just think communication is important). Again, no offense guys, but the ECT should not just coordinate extensions but also the development of the core teams with the extensions, instead of defining its own core (div/lib). Maybe one guy could be in 4.x, 5.x and the ECT to coordinate? So, that's just my 2 cents -- sorry for being so direct. Now you can hold forth of me :) greetings, benni. -SDG- Daniel Bruessler wrote: > Hello, > > in my view a moderator is needed, maybe that's the best word for it. ECT > has started as an OVERVIEW of current ongoings - and a mailinglist (I > mean technically) cannot do this. lib/div was ONE project of ECT, one of > several ones. For me forge is not "SVN with a bugtracker", out of my > view it's a team-platform. > > fabien: > * "It would be worth to redefine the goals of the ECT." > * http://wiki.typo3.org/index.php/ECT/Homepage > * Which projects are still alive? > * I would suggest to help Jochen's effort with extension-gimmefive > * forge-project for ECT? And what project are you thinking about? > > steffen: > * the goal of ECT was to have a platform, where teams are build to develop > extensions instead of 10 extensions doing all the same > * communication channel > * ECT can live without a declared leader, it should be ruled by the > devs here > > Cheers! > Daniel > > >> Hi, >> >> the goal of ECT was to have a platform, where teams are build to >> develop extensions instead of 10 extensions doing all the same. >> I don't see ECT as a project for forge, it's more a communication >> channel. >> >> In the past ECT was more a support forum for lib/div, what wasn't the >> purpose of ECT. >> >> So imho ECT can live without a declared leader, it should be ruled by >> the devs here. >> >> vg Steffen >> TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by omic
::
Rate this Message:
> Daniel Bruessler wrote: in my view a moderator is needed, maybe that's the best word for it.
What is the scope of such a role? Some suggestions about tasks assigned to the moderator / ECT leader : - have a global overview of the different team and projects, - encourage developers to coordinate their effort, - maintain the different wiki / typo3.org pages up to date. http://wiki.typo3.org/index.php/ECT/Homepage http://typo3.org/teams/extension-coordination-team/ http://... It looks like the moderator needs some good communication skills more than technical! > Steffen Kamper wrote : the goal of ECT was to have a platform, where teams are build to develop > extensions instead of 10 extensions doing all the same. That's my opinion too... and the benefit goes to everyone. > Benjamin Mack wrote: Why not finish div/lib and that's it then? It's been long enough in > alpha/beta state now. Well... for many, it's often a question of time. Unfortunately, at the moment, I don't have enough realistic time to invest. Furthermore, I see a lot of potential in gimmefive http://forge.typo3.org/projects/show/extension-gimmefive > I would love to have the ECT team work closer with the 4.x core team, so we can maybe integrate > some cool things. Yes, but this kind of work is certainly harder. As I far as I have understood, lib/div is supposed to be a light framework without dependency with the past. > However, "cal" from the ECT is great, but as you see, it also defined its own MVC framework again > --- why reinvent the wheel again and again and not collaborate? (no offense to the cal guys, I > just think communication is important). That's maybe for some historical reasons. At the time, I am not sure lib/div existed. kind regards, Fabien _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Daniel Bruessler-4
::
Rate this Message:
Helllo Fabien,
== moderator/team-leader/editor == >> Daniel Bruessler wrote: in my view a moderator is needed, maybe that's >> the best word for it. > > What is the scope of such a role? > > Some suggestions about tasks assigned to the moderator / ECT leader : > > - have a global overview of the different team and projects, > - encourage developers to coordinate their effort, > - maintain the different wiki / typo3.org pages up to date. in forge we can use several categories for the coordination-efforts: * coord. MVC-frameworks and standards * coord. Ajax-frameworks and standards * coord. templating-renderers * coord. general libraries (e.g. div2007) * coord. Calendars * coord. Form-libraries * coord. export/import (PDF, ODF, DocBook) * coord. payment-libraries * coord. auth-libraries These categories would NOT be coding-efforts, this would be coordination-efforts. ##Who does see the point that I mean? == content == > http://wiki.typo3.org/index.php/ECT/Homepage > http://typo3.org/teams/extension-coordination-team/ > http://... > > It looks like the moderator needs some good communication skills more > than technical! it's easy: the ECT was born in the wiki because the wiki was the only usable platform at that time. And I really know what is in the wiki. The team-page on typo3.org was made by Steffen and me and is a excerpt from the wiki-pages. => in my view as wiki-maintainer it IS important to move from wiki to forge. and again: lib/div is just ONE project of ECT. == lib/div, FLOW3-MVC aka gimmefive == >> Steffen Kamper wrote : the goal of ECT was to have a platform, where >> teams are build to develop extensions instead of 10 extensions doing >> all the same. > > That's my opinion too... and the benefit goes to everyone. > >> Benjamin Mack wrote: Why not finish div/lib and that's it then? It's >> been long enough in alpha/beta state now. > > Well... for many, it's often a question of time. Unfortunately, at the > moment, I don't have enough > realistic time to invest. > > Furthermore, I see a lot of potential in gimmefive > http://forge.typo3.org/projects/show/extension-gimmefive > >> I would love to have the ECT team work closer with the 4.x core team, >> so we can maybe integrate >> some cool things. > > Yes, but this kind of work is certainly harder. As I far as I have > understood, lib/div is supposed to be a light framework without > dependency with the past. >> However, "cal" from the ECT is great, but as you see, it also defined >> its own MVC framework again >> --- why reinvent the wheel again and again and not collaborate? (no >> offense to the cal guys, I just think communication is important). > > That's maybe for some historical reasons. At the time, I am not sure > lib/div existed. Yes, cal was earlier, and lib/div had the view to be extremely flexible. > kind regards, > > Fabien Cheers! Daniel _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by David Toshack
::
Rate this Message:
Daniel Bruessler wrote:
> Helllo Fabien, > > == moderator/team-leader/editor == >>> Daniel Bruessler wrote: in my view a moderator is needed, maybe >>> that's the best word for it. I think we need a number of roles to fully complement the responsibilities of extension coordination. Organization of roles and responsibilities within the ECT will hopefully bring more pull in getting the quality up and the quantity down of TYPO3 extensions. What I would like to propose is that we start with some brainstorming of possible ECT responsibilities based on the mission statement[1]. Remember, this is brainstorming so don't be shy. Feel free to throw something, even just to see if it sticks. If its not suitable enough for ECT it can always be suggested to the Association team for delegation. Once we have a list of responsibilities we can group them into roles to manage them. Possibly with some sort of hierarchy so that we can have even the smallest (managed) roles leaving nothing to slip between the cracks of these voluntary limited roles. >> Some suggestions about tasks assigned to the moderator / ECT leader : >> >> - have a global overview of the different team and projects, >> - encourage developers to coordinate their effort, >> - maintain the different wiki / typo3.org pages up to date. This is a great start. I'll create a new thread for these responsibilities. > in forge we can use several categories for the coordination-efforts: > * coord. MVC-frameworks and standards > * coord. Ajax-frameworks and standards > * coord. templating-renderers > * coord. general libraries (e.g. div2007) > * coord. Calendars > * coord. Form-libraries > * coord. export/import (PDF, ODF, DocBook) > * coord. payment-libraries > * coord. auth-libraries > > These categories would NOT be coding-efforts, this would be > coordination-efforts. > > ##Who does see the point that I mean? I do. I definitely believe there should be an ECT team(s) and projects on the forge site. It would also be nice to encapsulate T3N's Extension Comparison team[2] into the ECT which could benefit both teams. I think this would require the forge site to be better organized. Maybe with more project hierarchy. I like the idea of specific project categories like Drupal's module categories[3]. Although it may require a bit of recruiting; I believe there are enough TYPO3 _users_ out there to assign people to roles and responsibilities for each and every one of these extension categories. Even if the assignment of these roles change often I think with the right role hierarchy we can manage to keep many of these type of minor roles filled by TYPO3 users of _any_ capacity. > => in my view as wiki-maintainer it IS important to move from wiki to > forge. and again: lib/div is just ONE project of ECT. +1 In fact I see great benefit in moving a lot of the content from the TYPO3 wiki in general into the forge site. > == lib/div, FLOW3-MVC aka gimmefive == >>> Steffen Kamper wrote : the goal of ECT was to have a platform, where >>> teams are build to develop extensions instead of 10 extensions doing >>> all the same. >> >> That's my opinion too... and the benefit goes to everyone. >> >>> Benjamin Mack wrote: Why not finish div/lib and that's it then? It's >>> been long enough in alpha/beta state now. >> >> Well... for many, it's often a question of time. Unfortunately, at the >> moment, I don't have enough >> realistic time to invest. >> >> Furthermore, I see a lot of potential in gimmefive >> http://forge.typo3.org/projects/show/extension-gimmefive Me too. Fabien, what do you think about incorporating gimmefive functionality into lib/div? So that lib/div functionality can be used for v. 4 and simply ignored to use FLOW3 functionality in v. 5? This would be an even better intermediary than gimmefive alone, but I fear this may complicate more than it simplifies. What do you think about this? >> >>> I would love to have the ECT team work closer with the 4.x core team, >>> so we can maybe integrate >>> some cool things. +1! I would like to see the day when the "official typo3" extensions are treated with similar importance as core extensions. >> >> Yes, but this kind of work is certainly harder. As I far as I have >> understood, lib/div is supposed to be a light framework without >> dependency with the past. >>> However, "cal" from the ECT is great, but as you see, it also defined >>> its own MVC framework again >>> --- why reinvent the wheel again and again and not collaborate? (no >>> offense to the cal guys, I just think communication is important). >> >> That's maybe for some historical reasons. At the time, I am not sure >> lib/div existed. > > Yes, cal was earlier, and lib/div had the view to be extremely flexible. I would also like to see the day when projects like cal are handled completely through the ECT. Including delegating tasks to other TYPO3 teams[4]. This is definitely within our grasp and I for one would like to help make this a reality. Cheers, David [1] http://wiki.typo3.org/index.php/Mission_Statements#Extension_Coordination [2] http://forge.typo3.org/projects/show/team-extcomp [3] http://drupal.org/project/Modules [4] http://wiki.typo3.org/index.php/Teams _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by Daniel Bruessler-4
::
Rate this Message:
Hello David,
yes, a number of roles is a very good idea, so it's no problem when somebody has to leave for a while and others want to help. what's with that: * care for documentation & forge-team-area * moderator * connector for each topic ("encourage developers", see my last list + team-extcomp, core4, core5, news-team, T3N, association-team) Important: just ONE forge-project because we would loose overview if we had a bunch of ECT-forge-projects. Just one forge-project within the list "Others". Every coordination-effort can exist in it's own category. This works very well in DocTeam! http://forge.typo3.org/projects/show/other The drupal website is offline this morning, so I could not look at this. http://drupal.org/project/Modules Cheers! Daniel >> == moderator/team-leader/editor == >>>> Daniel Bruessler wrote: in my view a moderator is needed, maybe >>>> that's the best word for it. > > I think we need a number of roles to fully complement the > responsibilities of extension coordination. Organization of roles and > responsibilities within the ECT will hopefully bring more pull in > getting the quality up and the quantity down of TYPO3 extensions. > > What I would like to propose is that we start with some brainstorming of > possible ECT responsibilities based on the mission statement[1]. TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by omic
::
Rate this Message:
>> => in my view as wiki-maintainer it IS important to move from wiki to
>> forge. and again: lib/div is just ONE project of ECT. > > +1 In fact I see great benefit in moving a lot of the content from the > TYPO3 wiki in general into the forge site. +1 It offers a good opportunity for people that are working with lib/div to get involved. >>> Furthermore, I see a lot of potential in gimmefive >>> http://forge.typo3.org/projects/show/extension-gimmefive > > Me too. Fabien, what do you think about incorporating gimmefive > functionality into lib/div? So that lib/div functionality can be used > for v. 4 and simply ignored to use FLOW3 functionality in v. 5? > > This would be an even better intermediary than gimmefive alone, but I > fear this may complicate more than it simplifies. What do you think > about this? Well... it does not make sense for me. Gimmefive and lib/div are different framework and have different approaches. Gimmefive has a top/down construction and is going to change (a lot?) since it has a strong relation with FLOW3. For example, both use the MVC pattern but their implementation are different. (file organization, file loading etc...) > http://wiki.typo3.org/index.php/Mission_Statements#Extension_Coordination > [2] http://forge.typo3.org/projects/show/team-extcomp > [3] http://drupal.org/project/Modules > [4] http://wiki.typo3.org/index.php/Teams _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Franz Holzinger
::
Rate this Message:
Hello Benjamin,
> I'm not 100% in the ECT and what's going on there, but for me it seems > like the ECT, mainly div/lib, missed its goal. I thought it should also > be a starting point for migrating to 5.x, but there seems no > communication between the teams. Also, I would love to have the ECT team > work closer with the 4.x core team, so we can maybe integrate some cool > things. Only a ECT teamleader could do so. div/lib is for providing a class collection to replace the _pibase_ class which is not developed any further by the TYPO3 Core team. And of course it goes to PHP5 and provides a MVC. However it has stuck in alpha phase. > Then, there are IMHO some crazy ideas like "div2007" that I think are > just plainly wrong, as it is another dependency and some more extra you > have to juggle around with versions, incompatibilities and the > extensions (hard enough with TYPO3 4.1 and 4.2 already after updating). > Developing extensions make it even harder then. "This extension only > runs with TYPO3 4.0 and div2007 and lib2008" ;-) No this is wrong. The div2007 has become necessary because the API of div might still change a lot. And TYPO3 is not able to have more than one version of an extension installed at the same time. Otherwise it would not be possible to use 2 different extensions which relied on different div APIs. So you could not download the latest version of an extension if you need other extensions depending on div which have not been updated any more. > Why not finish div/lib and that's it then? It's been long enough in > alpha/beta state now. There seems to be no developer group any more for div/lib. And I think that div/lib should still be changed a lot. More functionality should come into it. > Again, no offense guys, but the ECT should not just coordinate > extensions but also the development of the core teams with the > extensions, instead of defining its own core (div/lib). Maybe one guy > could be in 4.x, 5.x and the ECT to coordinate? What do you mean exactly? Should the FLOW3 be used instead of lib/div in the future? But where should the functions of lib/div come then? Will new requirements of extensions and patches come into TYPO3 Core, but where? The response time in the Core list is very long in some cases. And the time between new TYPO3 versions with an enhanced API is very long. It takes many months until a new class would be put into the next TYPO3 version. But if you develop an extension than you require that a new function is available after a very short time. So I fear that no coordinated development of extensions would be possible, because everyone would still continue to write his own function API and classes. Franz _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - teamleaders
by Ingo Renner-2
::
Rate this Message:
Franz Holzinger wrote:
Franz, > div/lib is for providing a class > collection to replace the _pibase_ class which is not developed any > further by the TYPO3 Core team. I'm not sure what you had in your coffee this morning, but I suggest you don't put it in there tomorrow again... Ingo -- Ingo Renner TYPO3 Core Developer, Release Manager TYPO3 4.2 _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by Franz Holzinger
::
Rate this Message:
David Toshack a écrit :
> Daniel Bruessler wrote: >> Helllo Fabien, >> >> == moderator/team-leader/editor == >>>> Daniel Bruessler wrote: in my view a moderator is needed, maybe >>>> that's the best word for it. > > I think we need a number of roles to fully complement the > responsibilities of extension coordination. Organization of roles and > responsibilities within the ECT will hopefully bring more pull in > getting the quality up and the quantity down of TYPO3 extensions. Yes, that is the point. We need a library extension like lib/div to where all code can be put which is needed in most extensions and which will be used instead of the pibase TYPO3 class. We can add more specific extension libraries which are needed by a smaller number of exensions. > What I would like to propose is that we start with some brainstorming of > possible ECT responsibilities based on the mission statement[1]. - contact all extension developers to contribute to the ECT extensions. They shall give up their own extension libraries and move their written code into these ECT library extensions. The ECT coordinator should do this move or give the guidelines how to do so. - Also copy and improve code from the TYPO3 core on which the further development has been frozen. - Change the code and API and release new versions of the library extensions. (refactoring) Make many releases, because the developers want to see their methods very soon in the TYPO3 TER. >> in forge we can use several categories for the coordination-efforts: >> * coord. MVC-frameworks and standards >> * coord. Ajax-frameworks and standards >> * coord. templating-renderers >> * coord. general libraries (e.g. div2007) >> * coord. Calendars >> * coord. Form-libraries >> * coord. export/import (PDF, ODF, DocBook) >> * coord. payment-libraries >> * coord. auth-libraries >> >> These categories would NOT be coding-efforts, this would be >> coordination-efforts. >> >> ##Who does see the point that I mean? So a separate ECT code decisions and code review team will be needed. > Although it may require a bit of recruiting; I believe there are enough > TYPO3 _users_ out there to assign people to roles and responsibilities > for each and every one of these extension categories. A ECT coordinator must survey on these teams. If no work is done and a leader disappears then another one must be found after a short time. >> Yes, cal was earlier, and lib/div had the view to be extremely flexible. > > I would also like to see the day when projects like cal are handled > completely through the ECT. Including delegating tasks to other TYPO3 > teams[4]. This is definitely within our grasp and I for one would like > to help make this a reality. Some decision must be made which MVC extension sto use. So maybe a redesign of lib/div should be started to fit all needs. Then this should be used as the base MVC sytem for most TYPO3 extensions. cal should be one of the exensions which use this. Franz _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by Daniel Bruessler-4
::
Rate this Message:
Hello Franz,
I think we need several coordinators. You're the best for the lib/div framework. Seems so that nobody can coordinate all TYPO3-projects what needs any kind of common API. ;-) Do we reach a consensus on it now? by the way: A nice trip-hop radio-station is this: TripHop MonkeyRadio SanFranzisco http://groove.monkeyradio.org/ Cheers! Daniel Franz Holzinger schrieb: > David Toshack a écrit : >> Daniel Bruessler wrote: >>> Helllo Fabien, >>> >>> == moderator/team-leader/editor == >>>>> Daniel Bruessler wrote: in my view a moderator is needed, maybe >>>>> that's the best word for it. >> I think we need a number of roles to fully complement the >> responsibilities of extension coordination. Organization of roles and >> responsibilities within the ECT will hopefully bring more pull in >> getting the quality up and the quantity down of TYPO3 extensions. > > Yes, that is the point. > We need a library extension like lib/div to where all code can be put > which is needed in most extensions and which will be used instead of the > pibase TYPO3 class. > We can add more specific extension libraries which are needed by a > smaller number of exensions. > >> What I would like to propose is that we start with some brainstorming of >> possible ECT responsibilities based on the mission statement[1]. > - contact all extension developers to contribute to the ECT extensions. > They shall give up their own extension libraries and move their written > code into these ECT library extensions. The ECT coordinator should do > this move or give the guidelines how to do so. > > - Also copy and improve code from the TYPO3 core on which the further > development has been frozen. > > - Change the code and API and release new versions of the library > extensions. (refactoring) Make many releases, because the developers > want to see their methods very soon in the TYPO3 TER. > >>> in forge we can use several categories for the coordination-efforts: >>> * coord. MVC-frameworks and standards >>> * coord. Ajax-frameworks and standards >>> * coord. templating-renderers >>> * coord. general libraries (e.g. div2007) >>> * coord. Calendars >>> * coord. Form-libraries >>> * coord. export/import (PDF, ODF, DocBook) >>> * coord. payment-libraries >>> * coord. auth-libraries >>> >>> These categories would NOT be coding-efforts, this would be >>> coordination-efforts. >>> >>> ##Who does see the point that I mean? > But you would also need a group of persons who take care of the code. > So a separate ECT code decisions and code review team will be needed. > >> Although it may require a bit of recruiting; I believe there are enough >> TYPO3 _users_ out there to assign people to roles and responsibilities >> for each and every one of these extension categories. > A ECT coordinator must survey on these teams. If no work is done and a > leader disappears then another one must be found after a short time. > >>> Yes, cal was earlier, and lib/div had the view to be extremely flexible. >> I would also like to see the day when projects like cal are handled >> completely through the ECT. Including delegating tasks to other TYPO3 >> teams[4]. This is definitely within our grasp and I for one would like >> to help make this a reality. > Some decision must be made which MVC extension sto use. So maybe a > redesign of lib/div should be started to fit all needs. Then this should > be used as the base MVC sytem for most TYPO3 extensions. cal should be > one of the exensions which use this. > > Franz > TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by Franz Holzinger
::
Rate this Message:
Hello Daniel,
> I think we need several coordinators. You're the best for the lib/div > framework. Seems so that nobody can coordinate all TYPO3-projects what > needs any kind of common API. ;-) > > Do we reach a consensus on it now? So what is the common opinion of the extension developers? 1) The div/lib should still be developed in the ECT. It will be refactored as much as needed and considered usefull. 2) The div/lib should be moved now into TYPO3 Core and only Core developers will make decisions on it. 3) A completely new MVC framework shall be developed instead of lib/div. 4) Another MVC framework extension shall be taken und developed instead of lib/div. All current code of lib/div will be put there. I vote for 1) if no good proposal for another already working MVC extension is made. I would leave it in alpha state. The API is open to changes with losing compatibility amongst different versions if the second version number is different. It is necessary to see if there is still interest on lib/div as a ECT extension. Is there anyone else who wants to coordinate it under the ECT? > by the way: A nice trip-hop radio-station is this: > TripHop MonkeyRadio SanFranzisco http://groove.monkeyradio.org/ This sounds good, - Franz _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
Re: ECT - roles and responsibilities
by Daniel Bruessler-4
::
Rate this Message:
Hello Franz,
>> I think we need several coordinators. You're the best for the lib/div >> framework. Seems so that nobody can coordinate all TYPO3-projects what >> needs any kind of common API. ;-) >> >> Do we reach a consensus on it now? > > So what is the common opinion of the extension developers? > > 1) The div/lib should still be developed in the ECT. It will be > refactored as much as needed and considered usefull. > 2) The div/lib should be moved now into TYPO3 Core and only Core > developers will make decisions on it. > 3) A completely new MVC framework shall be developed instead of lib/div. > 4) Another MVC framework extension shall be taken und developed instead > of lib/div. All current code of lib/div will be put there. > > I vote for 1) if no good proposal for another already working MVC > extension is made. I would leave it in alpha state. The API is open to > changes with losing compatibility amongst different versions if the > second version number is different. please ask this in a NEW thread, because it's an important question. my opinion: NOW for the current extensions: 1) for FUTURE extensions (in 1 year?) as alternative: 4) FORGE-MVC >> by the way: A nice trip-hop radio-station is this: >> TripHop MonkeyRadio SanFranzisco http://groove.monkeyradio.org/ > This sounds good, yeah :-) > - Franz HaveANiceDay! Daniel _______________________________________________ TYPO3-team-extension-coordination mailing list TYPO3-team-extension-coordination@... http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination |
|
|
|
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
