Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of hzbarcea@gmail.com designates
 74.125.83.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=EQnJJDy/wur1R8Ftp1mzBEEfna94wmpWQP/rVnLM2GU9uJdNGyAnIY4EIEtHCJEowp
         qui6AaW40Irfn+6nq59AMxfA94Zi3UpvT3rf3MZmOkCtnWNZ9XmA4ozJzQGGgG8MAYjO
         zoWSv58HjhD0ADLMmXzqMVahjgPMxflzF3fEU=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: helping out with the Web site
From: Hadrian Zbarcea <hzbarcea@gmail.com>
In-Reply-To: <ED9CE29F-443B-430B-97E2-787022AF6995@gmail.com>
Date: Wed, 10 Nov 2010 11:14:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE022121-E70F-4EE4-AD43-F0DAC263189A@gmail.com>
References: <AANLkTi=0wd4xY21QzqkzBwe-h0mu9z36WvPKX_WqWeP5@mail.gmail.com>
 <201011100951.27827.dkulp@apache.org>
 <AANLkTinj2ruN_SyHpNxyeVviBBDQLSaOXJgcbw1sGD_s@mail.gmail.com>
 <201011101015.08081.dkulp@apache.org>
 <AANLkTinWLthUMAq0R=RPUJ4JjxwJxm=bUQ-8TBaVFDHL@mail.gmail.com>
 <3569A3F5-6FF4-4C0A-8DA3-0F913E3CE75C@gmail.com>
 <ED9CE29F-443B-430B-97E2-787022AF6995@gmail.com>
To: dev@camel.apache.org

Just for the record. I like scalate too, it's f*** awesome s*** :).
Hadrian

On Nov 10, 2010, at 11:04 AM, Johan Edstrom wrote:

> I actually really liked the scalate project and writing the docs in =
IDEA,=20
> making a patch and tossing it in github.
>=20
> Offline editing also seems really nice for when you are on planes, in =
airports or hotels.
> Not to mention if you actually fix a bug and submit a patch you could =
fix documentation in one feel swoop.
>=20
> And with the possibility of editing and running Jetty locally - it was =
really easy.
>=20
> Just my .02, i'm one of those that like irc for the quick informal =
style over forums for example,
> I also really like svn/git since I have tooling around versioning et =
al.
>=20
> And yeah, making patches is "klunky" using diff and things like that.
>=20
> /je
> On Nov 10, 2010, at 8:52 AM, Hadrian Zbarcea wrote:
>=20
>>=20
>> On Nov 10, 2010, at 10:28 AM, James Strachan wrote:
>>=20
>>> On 10 November 2010 15:15, Daniel Kulp <dkulp@apache.org> wrote:
>>>> On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
>>>>> On 10 November 2010 14:51, Daniel Kulp <dkulp@apache.org> wrote:
>>>>>>=20
>>>>>> For most of the people on this list, it ISN'T a big deal.   We =
deal with
>>>>>> svn and mvn every day.   For others, it could be.
>>>>>=20
>>>>> Given 99% of all our documentation and web content is developed by
>>>>> committers or folks who are capable of editing text files and =
using
>>>>> git/svn, I'd rather use a system that helps the 99% be more =
effective.
>>>>>=20
>>>>> Maybe you should just help out this one CXF person & show them how =
to
>>>>> fork & commit to github (its very easy), then you can easily pull
>>>>> their commits from there?
>>>>=20
>>>> Umm..  no.   Pulling branches from github is NOT, at this point, an =
acceptable
>>>> way of getting content into an Apache product.   They would still =
need to
>>>> create a patch and attach it to  JIRA with the "grant" checkbox =
checked.
>>>=20
>>> Whatever happens folks have to raise a JIRA and click the "grant" =
checkbox.
>>>=20
>>> I fail to see why a link to a specific commit (i.e. a link to a =
number
>>> of patches) is any less suitable than a number of patch files being
>>> attached in place to the JIRA. Got anything specific to back this up
>>> or is it just that we've not done it before?
>>>=20
>>> Patch files are a total PITA for both the person contributing and =
the
>>> person applying the patch. (They usually break, get out of sync, =
have
>>> whitespace issues and frequently have the wrong path information in
>>> them & often have problems with new/renamed/deleted files).
>>>=20
>>> If this discussion really is about being a "community issue" and
>>> making it easy for both folks to contribute and for committers to
>>> apply those contributions, I'd rather we figure out this issue of
>>> using links to git commits as an alternative to patch files on JIRAs =
-
>>> this could make a *massive* difference to both getting contributions
>>> and more effectively applying them IMHO. Helping scm-novices
>>> contribute to documentation (which they've never really done so far =
on
>>> Camel anyway) seems quite irrelevant in comparison.
>> I don't know if this is a scm-novices issues. We had contributions =
from not committers in the past.
>> Johan (before his commiter days) is one example, Steve Bate is =
another. I would rather ask them how likely would it be to contribute to =
doc if they had to co/edit/submit-patch, vs edit in-place wiki style.
>> I know they are not scm-novices.
>>=20
>> I am open to any alternative that would not raise the barrier to =
entry for documentation contributors and that's acceptable to the ASF.
>>=20
>> Hadrian
>>=20
>>>=20
>>> --=20
>>> James
>>> -------
>>> FuseSource
>>> Email: james@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: jstrachan
>>> Blog: http://macstrac.blogspot.com/
>>>=20
>>> Open Source Integration
>>=20
>=20