[TYPO3-UG US] Wiki

[Gregory Remington]

Alex Heizer wrote:
>> Very interested. Can we first tally up what needs to be done and time
> 
> 
> 
> That would be determined by the needs of the job. 

A minimalist approach may hwlp us calculate how much time it will take 
each week to maintain the new architecture once we have defined it on 
the wiki.

Do we have a wiki yet? I've been out of the loop for a day :)

> Other jobs will require different amounts of time to keep the project working 
> the way it's supposed to, and the amount of time each team member will 
> need to spend depends on the number of team members and their skills.

Should we define our final infrustructure based on member availability 
and commitment hours in the begining? Also breaking down week days into 
tasks lists might help us define our infrastructure better in terms of 
application usage. Can we post a list applications used to manage and 
coordinate activities, tasks and goals for new member orientation?

Example:

* newsreader
* TYPO3 extensions (wiki, workflow, groupware, etc.)


> Scheduling tasks and time commitments is part of the team leader's 
> responsibilities, so the wiki team leader should probably have some 
> experience with maintaining a wiki so they can anticipate some of the 
> things that are going to need to be done. 

Have we selected a wiki team leader yet? We could use several backup 
leaders too for times when we run short of time :)

> The impression I got from 
> people maintaining the typo3 wiki is that it's something that needs to 
> be constantly monitored, since anyone can post at any time. 

Is there no possibility to assign read only permissions for users not 
logged in under a group ID or better yet maybe we could have 2 wikis. 
One for collecting new data and a public version once the data has 
passed inspection.

> It was even 
> recommended that you grab the RSS feed so you can instantly tell what's 
> been updated each day and either delete or approve it. But making a task 
> list and delegating time commitments is something the team leader is 
> going to have to determine.

I nominate Alex as team leader... hehe :)

> Has anyone on the list maintained an active (busy) wiki that can give a 
> quick estimate of the time that a team might need to spend?

No wiki experience here. Ask me about maintaining a forum sometime ;)

Cheers,
Greg