[Typo3-documentation] Follow-up: I know there is a team structure already... what I meant was...

[Coby Pachmayr]

Re-reading my post I realize that I ended it abrubtly (because I was going
to start a new post)... I want to be clear... I know there is a team
structure... I am referring to an organziational structure for discussion,
adoption, documentation, and implementation of these new ideas.  It is that
that I will post a new thread on.

"Coby Pachmayr" <coby at _remove_ideaspring.com> wrote in message
news:mailman.1.1091077732.18902.typo3-project-documentation at lists.netfielders.de...
> Okay... So I'm ready to start contributing on the Wiki...
>
> I went back and read every message in this NG... very motivated I went to
> the Wiki page... and then...
>
> I have no idea where I am *supposed* to start filling things in...
>
> For example, I thought an easy addition/contribution would be my update to
> make the MTB - Part 1 actually work... this created (for me) some dilemas:
>
> #1.) Where do I add this to the Wiki?  There is seemingly no obvious place
> to add this to the "Documentation Guide" setup by Johannes (which I agree
> seems like a great structure to fill in!) And if I go to the Administrator
> Tutorials, the MTB document is "Finished" (appears to me like "no more
info
> needed") -- clicking on the link, I get the document currently in the
> Document Matrix... so do I "annotate" this document?
>
> #2.) Assuming that I resolve *where* to put my correction/addition to the
> code, who is available from this team or another team to verify that my
> *fix* isn't something that only made it work for me, or to validate that
it
> is in fact a problem or change that needs to be made?
>
> #3.) If I follow through with my suggestions from my earlier posts, it is
> unclear where I should actually place these... since I only saw one vote
> *for* my (perhaps overly structured) vision ... my guess is I will need to
> create my own wiki, and document repository.. which is the way I'm leaning
> now...
>
> All of this reminds me of common saying... that if you want an
organization
> to go nowhere... run it by committee... :-)
>
> Perhaps what we need as a group is to set up an organizational
structure --- 
> since nobody likes my long posts, I will start a new thread on this.
>
> "Jean-Marie Schweizer" <jms at marktauftritte.ch> wrote in message
>
news:mailman.1.1091073180.11682.typo3-project-documentation at lists.netfielders.de...
> > So, now that we have some sort of an agreement that we all know that
> > something needs to be done to help TYPO3 go to the next level and we
> > like to do that with REALLY GOOD documentations let's put it into
action.
> >
> > Although we might not agree on what the Wiki is for and how we use it,
> > by actually trying instead of talking about it we'll find it out fairly
> > quickly.
> >
> > A last word about the structure (at least from my side):
> >
> > I like Jonathans structure and wouldn't want it to be hidden somewhere
> > but I acknowledge the work of Peter and others that have come up with
> > the existing structure.
> >
> > I really think you guys should resolve the problem once and for all now
> > with the clear picture in mind that in a few months we might think
> > differently and have different needs. If it must be: vote.
> >
> > I will not however take part in that discussion and put my focus back on
> > the installation document and hope that some people in this group will
> > think along the same way and start writing because although structure is
> > important, writing the documentation is it too.
> >
> > Jean-Marie
>
>