[TYPO3-UG US] This is just about perfect...

[Jennifer Lynch]

Call me a pragmatist, or Ishmael, but I really think that the simpler we
make this process the better.  If we build the thing, "they will come".  The
point is to build it.  We can categorize the attendees and see where they're
coming from (CIO offices, lowly cubicles in the content management
department, or free lance consultants surfing the web in their pajamas), but
theorizing about our audiences or boxes vs. manual covers won't mean much if
there's no site for them to come to.

What we actually need is for volunteers to opt for their box on the Roadmap
and write the content up.  Michelle will post those boxes that are taken and
it will be easy to see what needs to be done.  When you choose a box, pick
those higher up in the outline before you pick the sub-categories.  That
way, the pages that need doing first, get done first.

Taking the time to do "assessments of progress" would take more time than
writing the content.  You can check in at the Roadmap and find out what
progress has been made.

May isn't really that far away--the holidays will eat up most people's time.
Get a few pages in before the holidays, pick up a few after you've recovered
from the Christmas eggnog.

So is there anyone out there interested in actually writing something other
than e-mail???  


Jennifer


On 11/2/05 10:50 PM, "Gregory Remington" <greg at mediatech.net> wrote:

> 
> It might be helpful to start doing weekly assessments of progress. What
> gets measured gets done. We have a great start so maybe we should take
> realistic look at what can specifically be done for deadline? What do we
> absolutely need and what can be rescheduled if it doesn't get completed?

> 
> May sounds like plenty of time to work with. What might help quicken our
> pace is an economic incentive like having our names pinned to whatever
> we do. We may also want to define what markets our collaborative
> documentation offers in terms of specific business solutions. Each of us
> has different goals for TYPO3... we need to assess a common need.
> 
> What are our skills sets here as human resources? How can we
> collaboratively utilize these skills to create documentation that serves
> our collaborative business interests?

> 
> Perhaps we need to start carving off little pieces here and finish each
> piece before moving to the next piece. Have we made a list of an
> extension group we need to document before moving to another group?
> 
> The roadmap is detailed and well structured. I think it may be a good
> idea to see just how many people can commit their time to finishing 1/3
> of it and "when" that will be. What gets measured gets done. Should we
> make a list of tasks and who's responsible for completing them. I don't
> believe I have a task(s) yet.
> I'm on my 2nd glass of Shiraz ;)
> 
> Cheers (really),
> Greg
> _______________________________________________
> Typo3-ug-us mailing list
> Typo3-ug-us at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-ug-us
> 
>