Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Let's talk about the future

Received: by 10.224.184.137 with SMTP id ck9mr3818939qab.1.1334499955809;
        Sun, 15 Apr 2012 07:25:55 -0700 (PDT)
X-BeenThere: joomla-dev-cms@googlegroups.com
Received: by 10.229.229.2 with SMTP id jg2ls3801340qcb.9.gmail; Sun, 15 Apr
 2012 07:25:51 -0700 (PDT)
Received: by 10.224.72.211 with SMTP id n19mr3797641qaj.7.1334499951230;
        Sun, 15 Apr 2012 07:25:51 -0700 (PDT)
Received: by 10.224.72.211 with SMTP id n19mr3797640qaj.7.1334499951221;
        Sun, 15 Apr 2012 07:25:51 -0700 (PDT)
Return-Path: <garyam...@gmail.com>
Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com [209.85.216.176])
        by gmr-mx.google.com with ESMTPS id ez28si928118qcb.1.2012.04.15.07.25.51
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 15 Apr 2012 07:25:51 -0700 (PDT)
Received-SPF: pass (google.com: domain of garyam...@gmail.com designates 209.85.216.176 as permitted sender) client-ip=209.85.216.176;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of garyam...@gmail.com designates 209.85.216.176 as permitted sender) smtp.mail=garyam...@gmail.com; dkim=pass header...@gmail.com
Received: by qcsd1 with SMTP id d1so3410505qcs.21
        for <joomla-dev-cms@googlegroups.com>; Sun, 15 Apr 2012 07:25:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=ZJwWXaXIXG5zjroxYa+IkVmeunHFP1iwwd2hw++uohI=;
        b=QeGFy9t7r4WjZEiAUuDW/7Rw+XVKkFdnYETYiMnS4V9zvIWnB5RVG/I+eSnOTNdVwe
         mVu27mMEFHrnvrtG5g2oDcMnWLnF7t6VXbryDhKEFYxbMP3J73eGXgNoGHP4Fc8hWfpr
         CVpQMWmDh9kmID5HAeXi6MfdnSb+uuE/28P3xyc40nr2F3V7d3rl5TVunUwyqfd3dAxj
         Iw5Y82Pk7U7QcApEhV0rbX/eGR6Om9MIPVjsw+VwBGXNzyFdaJg/S6uIpTBPNoOPDsDl
         agccXG2klK5m8Lt7BhMNQc8h8seGnkM7eCxV0FRukseOmv0i89LIWpLfuO/Sdjx8DpcV
         UNPA==
Received: by 10.224.193.8 with SMTP id ds8mr2884904qab.1.1334499951121;
        Sun, 15 Apr 2012 07:25:51 -0700 (PDT)
Return-Path: <garyam...@gmail.com>
Received: from [192.168.56.1] (ool-45757819.dyn.optonline.net. [69.117.120.25])
        by mx.google.com with ESMTPS id cs10sm28872420qab.8.2012.04.15.07.25.49
        (version=SSLv3 cipher=OTHER);
        Sun, 15 Apr 2012 07:25:49 -0700 (PDT)
Message-ID: <4F8ADA6C.9000...@gmail.com>
Date: Sun, 15 Apr 2012 10:25:48 -0400
From: Gary Mort <garyam...@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: joomla-dev-cms@googlegroups.com
Subject: Re: [jcms] Let's talk about the future
References: <15117797.193.1334312569735.JavaMail.geo-discussion-forums@ynvv7> <926271.919.1334420338977.JavaMail.geo-discussion-forums@ynbq18> <5548448.428.1334428708438.JavaMail.geo-discussion-forums@vbbfj25> <20294941.1161.1334429275085.JavaMail.geo-discussion-forums@ynlp3> <20422728.1248.1334435394598.JavaMail.geo-discussion-forums@ynlp2> <18190432.1580.1334436232747.JavaMail.geo-discussion-forums@vbiz13> <7C3B491C-733E-4930-9227-A428141DA...@rouvenwessling.de> <CANdmvYsxxCFr6suFRw8ANasDiEvjD0s-mMKhPmmJeABbiaY...@mail.gmail.com> <12084812.786.1334441308690.JavaMail.geo-discussion-forums@ynbr30> <CADPtAkRzLLjr9=RKpmAhAZCwBW4TQzW0k=wh8y1+6cAMLKG...@mail.gmail.com> <32399510.1609.1334446131890.JavaMail.geo-discussion-forums@vbyz30> <CADPtAkTr5GJ07V2d-ZZtU4TBwJ5keMb==eHTBMmCwW2a=Rq...@mail.gmail.com> <CAC-5JBHHXPXNhVi-TvxW+JVdM4vj0L6+pf0Y_mU=b9OLQUv...@mail.gmail.com> <11258031.97.1334490532943.JavaMail.geo-discussion-forums@ynbr30>
In-Reply-To: <11258031.97.1334490532943.JavaMail.geo-discussion-forums@ynbr30>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 4/15/2012 7:48 AM, Nils R�ckmann wrote:
> One big problem on http://docs.joomla.org/Developers might be the 
> different Joomla versions.
>
> And like i said, i don't want to enforce developers to write 
> documentations. But a small note on a todo-list or something where 
> people which wants to write documentations can pick a topic and start 
> writing. And if the list grows we can start a documentation sprint.
>

There is a flipside, if documentation contains links to the platform 
classes and methods they utilize - then you can automate the process of 
determining which pages a new release impacts.  Since a lot of changes 
are to things which were depreciated or are adding a new and improved 
method to do something[while maintaining the other for backwards 
compatibility] - it would be very hard for someone working on the 
platform to know whether or not any documentation needs to be updated..