[documentation] does this seem funny to anyone else?

[Steve Dondley]

Right. No need to change everything because of a few shortcomings. The
task has to be list the shortcomings and find the person who has the
technical ability/authority to make the actual improvements.

On Wed, Apr 2, 2008 at 11:55 AM, Alan Palazzolo <me at alanpalazzolo.com> wrote:
> First post to documentation list.
>
>  I think this is a very valid point.  I don't like learning new markup.
>  It can or cannot make things easier.
>
>  Still, I really hope this discussion is not about syntax.  It should be
>  about structure, accountability, and empowering.
>
>  People that have been here awhile have to realize that things are not
>  perfect and change needs to happen.  New people need to realize that
>  change cannot happen overnight.  There needs to be compromise.
>  Creditability and good ideas are not the same.  Please do not fork the
>  documentation.
>
>  My personal thoughts: I think it should be more like wiki, but with some
>  well structured navigation.
>
>  --
>  Alan
>
>
>
>
>
>  On 4/2/08 10:33 AM, Joshua Brauer wrote:
>  > I'd thought about this off and on over the years. Then recently Larry
>  > Garfield wrote a piece that encapsulated the situation brilliantly
>  > pointing out that Drupal.org effectively *has* a wiki:
>  >
>  > http://www.garfieldtech.com/drupal-org-wiki
>  >
>  > As Larry suggests in his article, for me the idea of adding non-HTML
>  > markup to the documentation of a system that is all about building and
>  > serving HTML is counter-productive. Users with the desire need only ask
>  > and they can have edit rights on content and they need to know very
>  > rudimentary HTML. If someone doesn't know the most basic of HTML perhaps
>  > a few hours spent learning it would be a worthwhile pre-requisite to
>  > contributing to the documentation of a system that is all about HTML.
>  >
>  > Josh
>  >
>  > ---------------------------
>  > Joshua Brauer
>  >
>  > Brauer Ranch Ltd. Co.
>  > http://BrauerRanch.com
>  >
>  > Making the world better through Drupal.
>  >
>  > On Apr 2, 2008, at 8:56 AM, Steve Dondley wrote:
>  >
>  >> Walter,
>  >>
>  >> This proves that following the "Build it and they will come" is a
>  >> gamble. You need buy-in and agreement from others most of the time.
>  >>
>  >> To get buy-in, you need karma. To get karma, you need to contribute.
>  >> To contribute, you need to work within the system as it is.
>  >>
>  >> Call it politics or whatever, but that is how humans haved tended to
>  >> operate for the last 3 million years. I don't think it's likely to
>  >> change anytime soon.
>  >>
>  >> That is why my advice to ricco is to not ask the community to bend to
>  >> his needs but to have him bend to the community's needs. If the
>  >> community jumped at every request from every person, no matter how
>  >> worth, nothing would get done. You need to first earn the reputation
>  >> to be able to persuade others that your way is superior.
>  >>
>  >> On Wed, Apr 2, 2008 at 10:28 AM, Walter GR <waltergr at aol.com> wrote:
>  >>> ricco at webulite.com wrote:
>  >>>> lol... this kind of cracks me up. In a frustrating kind of way :)
>  >>>> <snip>
>  >>>>
>  >>>> Cheers! Ricco
>  >>>
>  >>> In June of last year, I suggested that doing documentation-as-a-wiki
>  >>> might be a good idea.
>  >>>
>  >>> I created one, much to others' chagrin.  They suggested I join the
>  >>> documentation team.  I decided to pursue that route.
>  >>>
>  >>> As I had a wiki at my disposal, I decided to use it for proposing some
>  >>> changes to the documentation.  I spent *hours* making improvements, and
>  >>> then posted a link requesting feedback:
>  >>>
>  >>> http://lists.drupal.org/pipermail/documentation/2007-June/005657.html
>  >>>
>  >>> Nobody gave any feedback.  I don't even know if anyone looked at my
>  >>> proposed changes.
>  >>>
>  >>> Best of luck, Ricco.
>  >>>
>  >>>
>  >>> --
>  >>> The Online Slang Dictionary - Now with a thesaurus!
>  >>> http://onlineslangdictionary.com/
>  >>>
>  >>>
>  >>> --
>  >>> Pending work: http://drupal.org/project/issues/documentation/
>  >>> List archives: http://lists.drupal.org/pipermail/documentation/
>  >>>
>  >>
>  >>
>  >>
>  >> --
>  >> Prometheus Labor Communications, Inc.
>  >> http://prometheuslabor.com
>  >> 413-572-1300
>  >>
>  >> Communicate or Die: American Labor Unions and the Internet
>  >> http://communicateordie.com
>  >> --
>  >> Pending work: http://drupal.org/project/issues/documentation/
>  >> List archives: http://lists.drupal.org/pipermail/documentation/
>  >
>  >
>  > ------------------------------------------------------------------------
>
>
> >
>  > --
>  > Pending work: http://drupal.org/project/issues/documentation/
>  > List archives: http://lists.drupal.org/pipermail/documentation/
>  --
>  Pending work: http://drupal.org/project/issues/documentation/
>  List archives: http://lists.drupal.org/pipermail/documentation/
>



-- 
Prometheus Labor Communications, Inc.
http://prometheuslabor.com
413-572-1300

Communicate or Die: American Labor Unions and the Internet
http://communicateordie.com