[Typo3-typo3org] The next steps

[Jan-Hendrik Heuing [NF]]

>   - TER: Let's discuss the remaining details of the concept and update
>     the document. We should work on this as much as possible so we soon
>     have a guideline for implementing the new TER. Some sub-tasks:

After discussing this, I'll update our Brainstorming-document about 
local-dev-ter and publish it this week, in the worst case at the weekend.

>       - For refactoring the current TER we need a testing / development
>         platform. Who creates and maintains such a platform?

You always have access to the virtuozzo-nodes, you can always add a virtual 
server for it. If that's interesting, we can always handle it if you do not 
feel comfortable with it doing it yourself. But as offers are already 
available, it might not be needed anyway.

>       - For refactoring the current TER we also need unit tests. Who can
>         compile all the neccessary information so we can quickly integrate
>         unit tests in the current extrep_mgm extension?

If I remember right Sven did already do something like this, but I might be 
wrong. The other thing is Butsch is into unit-tests, but on Java-Level. I 
can ask him if he wants to take care of it.

>       - Who extracts the suggestions and decisions from the discussions
>         and prepares a summary which we can include into the general
>         concept?

I couldn't do that before the weekend. I'd wait until I publish my document, 
if noone did it until then, I could take over that task.

>   - documentation.typo3.org: We need a fresh concept for separating the
>     documentation section from the extension repository. That concept
>     should allow for features like automatic generation of multiple output
>     formats (online, single HTML, multiple HTML, SXW, PDF, ...), being
>     mirrorable, failsafe connection to other parts of TYPO3.org etc.

Michael already pointed out docbook, which I think is a good idea. Beside 
that I like the idea of being able to update things online while you'd 
generate common documents out of it for replicating if you also plan 
replication for docs.

>  - teams.typo3.org: We need a concept and development guidelines for
>    the collaboration part of TYPO3.org. There are many ideas how we
>    can improve communication and collaboration for the community,
>    these include workspaces, team-wikis (timtaw), team-news and more.

It's part of the doc I am sending. But it includes a couple of things, so it 
might not be a good idea to separate those into a lot of subdomains.

>  - news.typo3.org: 10% work is left for deploying the centralized news
>    repository. Who would like to administer and take responsibility for 
> the
>    news site in the long run? Who organizes recruitment of editors and
>    assures quality of the articles? Team up with DocTeam?

As long as it's not editing content, we can do it. It's already hosted on a 
virtual server, so that's no problem I guess. What tasks would be included 
here ?

>  - users.typo3.org: In the long run we need a centralized management of
>    frontend users for the TYPO3 sites. René already created a technical
>    solution using SOAP, but it has to be refined, documented and tested.

Generaly yes, it sounds like a good idea. LDAP in the other mail (Sven) 
seems to be a good idea also, but in this case, I am not too much into LDAP 
to be sure that you can control access to it. The main problem is that not 
everyone should be able to update users, but only check rights against a 
common place. As long as it's only used for internal projects, that's no 
problem anyway.

> As you can imagine, there is much more to do. An essential requirement for
> the success of these projects is having project leaders who take care of
> their area in the long run. Unfortunately, this is currently not the case
> in the DocTeam so it seems like much time and work is wasted with finding 
> a
> project leader, redesigning the wiki frontpage and finding a new project
> leader again - let's learn from that.
>
> For the TYPO3 sites we are currently four people who are officially in
> charge:
>
>  - Robert Lemke, T3 sites team leader, webmaster at typo3.org
>  - Christian Jul Jensen, T3 sites team leader substitute,
> webmaster at typo3.org
>  - Karsten Dambekalns, webmaster at typo3.org
>  - Michael Stucki, mailing list admin
>
> Let's team up, structurize and organize our working power and let's join
> forces for the spring cleaning 2005!

Jan-Hendrik