ECT/Homepage
Next step for this wiki-page: check what structure the other teams have --Daniel Brüßler 14:59, 25 January 2007 (CET)
Contents
What we want to achieve with the team-homepage
- Help developers to get in contact with active ECT-projects (MVC, Forms, Party Framework, ...)
- Central overview what projects are planned/stopped/active/waiting
- Links to all active ECT-Projects
- Show developers how they optimize their code for Typo3
- Synergy effects by coordination of (extension) teams
- Show the differences and advantages of pi_base and lib/div
- link to the todo-list in the wiki
- ...
THE CONTENT
internal info:
- a light first version what can be there very FAST (FAQ and little Projects-List enough?)
- the full version with some links to the wiki-pages as step 2 what can take time
- here it will be: https://typo3.org/teams/
Extension Coordination Team - this will be the startpage
internal info:
- carries the FAQ !!!
- the advantage is that people can see the questions what they have in their head when they visit the teams-page
(DRAFT) Welcome to the pages of the TYPO3 Extension Coordination Team! Here you can check the Frequently Asked Questions, or go directly to the ProjectsTable and the Goals of each project. For project-details and contact-persons just see the ProjectsTable.
| (DRAFT) Question | Answer | maybe: illustration |
| What is ECT and what do you mean with "Extension Coordination"? | ECT is the shortname, the focus is to help all frontend-extension-developers: Good quality, good standards, nice-to-use base-features like form-handling and translation-handling, bringing ideas together | -- |
| When did you start? | 18:34, 6 December 2005 by Elmar Hinz (we can say it so detailed, because the team was founded in the TYPO3-Wiki) | -- |
| Who can I contact? | See the Projects-table - for every project we have an other coordinator. The leader of the whole ECT is Elmar Hinz | maybe: photo or a funny illustration |
| How can I help with XX in project YY ? | See the Projects-table and look who's the coordinator for it. First read the wiki-page of the project, because there are all the detail, then introduce yourself in the mailinglist + send an email as copy to the coordinator. | -- |
| Why do you focus just on Frontend-Extensions? | We can say FE extensions is our starting point. Many extensions are for the FE. BE extensions can be supported, as soon as somebody is actively organizing that field. | -- |
| Do you care about AJAX, MVC, Oracle-DB? | It depends. We coordinate it, when several solutions exist for a problem - e.g. we checked out what ajax-frameworks are best with TYPO3 and care for updates. | -- |
| Question? | Answer? | -- |
| Question? | Answer? | -- |
| Question? | Answer? | -- |
| Question? | Answer? | -- |
ProjectsTable + Goals
internal info:
- status-info-table like Projects with encryped email-mailto's (great, that this is standard on typo3.org)
- Working groups, contains links to docs and contact, here 1 explaining paragraph for every project
- The link to the wiki must use javascript or better a form, so that wiki-spam-engines cannot find the links.
- when we put the members in the list it gets longer, but we give a good motivation for people who like to help!!
Next step:
- put the missing Detail-links in (just on ECT-page to prevent broken links)
- names of coordinator/s and members (from page ECT)
- relation (see relations-part of each projects-page)
| (DRAFT) The Project | Activity | Wiki-Link | Coordinator/s and members | Relation |
| MVC Framework for Extensions | Most Active | Details | coordinators and members | relation |
| Calendar Base | Most Active | Details | coordinators and members | relation |
| Extension Comparison | Most Active | Details | coordinators and members | relation |
| Party Information Framework | Active | Details | coordinators and members | relation |
| Forms Library for FE Extensions | Active | Details | coordinators and members | relation |
| Extension Rating System and Reviews | Active | Details | coordinators and members | relation |
| Modern Extension Coding Guidelines | Active | Details | coordinators and members | relation |
| Xajax | Active | Details | coordinators and members | relation |
| ECT/Homepage | Active | Details | coordinators and members | relation |
| Content Rendering Schemes | Slumbering | wiki-Link | coordinators and members | relation |
| Library of TypoScript Snippets | Slumbering | wiki-Link | coordinators and members | relation |
| TYPO3 to go: Quickstart Packages | Slumbering | wiki-Link | coordinators and members | relation |
| TYPO3 Zengarden | Project Proposals | wiki-Link | coordinators and members | relation |
| Global Categories | Project Proposals | wiki-Link | coordinators and members | relation |
| Enhanced Rights Management | Project Proposals | wiki-Link | coordinators and members | relation |
| Mail Framework | Project Proposals | wiki-Link | coordinators and members | relation |
| FE User Registration | Project Proposals | wiki-Link | coordinators and members | relation |
| Better Error Messages by Exception-handling | Project Proposals | wiki-Link | coordinators and members | relation |
| Quicker Frontend | Corner of Inventions | wiki-Link | coordinators and members | relation |
| TS Editor with Highlighting and Code Completion for the BE | Corner of Inventions | wiki-Link | coordinators and members | relation |
| Dynamic Flexforms | Corner of Inventions | wiki-Link | coordinators and members | relation |
| Folder Specific Forms | Corner of Inventions | wiki-Link | coordinators and members | relation |
| name | activity | wiki-Link | coordinators and members | relation |
| name | activity | wiki-Link | coordinators and members | relation |
| name | activity | wiki-Link | coordinators and members | relation |
wishlist: more fields for extended version: Activity, The Goal
to prevent wiki-spam we can use something like
<form name="link"><input name="ECT-ProjectName" type="hidden"><input type="submit" value="Project Name" onClick="forward(this)"></form> pro: wiki-spam-engines cannot find the links (very important!) contra: cannot be managed by a text-CType (OK for Patrick??)
Mailing List
internal info:
- name, link, purpose of the mailinglist, info what name the test-list has
News
internal info:
- via RSS, composing of new articles via ECT/Homepage/News
(DRAFT) The Extension Coordination Team was born in the wiki - now we run a team-page on typo3.org and keep it update. Our leader is Elmar Hinz, our aim is to build a good base for extension-developers.
We have a FAQ and a table what projects are running currently. With two klicks you're there. (DanielBrüßler and Steffen Kamper)
Active Members
internal info:
- good idea for motivation
- needs a date - so it's possible to know when somebody moves out of the list
(DRAFT) People that have taken up responsibility and made mayor contributions during the last 6 months.
Current Project Members
| Steffen Kamper | content on typo3.org Team-page | contact: info/nospam/sk-typo3.de |
| Daniel Brüßler | todo: create wiki-page, template as helper for sync between wiki-content and typo3.org-content, some content on typo3.org Team-page | contact: info-nospam-danielbruessler.de |
| Patrick Gaumond | cares for the typo3.org - team areas | contact: gaumond, Patrick.Gaumond+nospam+dap.ulaval.ca |
