+1 to Darren's 'We should be careful about "no X, no commit"' One
exception though; (unit)tests. And I can live with a #!human script
like Marty describes. Even though your point is valid, David,
developers (like me) have an internal company need for a fix or a
feature, and are inclined to work on
+1 to Marty.
On Fri, Sep 6, 2013 at 2:32 AM, Marty Sweet wrote:
> My view is that when a feature is added the developer should give a short
> overview of how to use all of the items which have been added, a doc
> contributor can then write this up in a user friendly manner which is
> similar to
My view is that when a feature is added the developer should give a short
overview of how to use all of the items which have been added, a doc
contributor can then write this up in a user friendly manner which is
similar to the whole style of the rest of the documentation.
Example description of d
On 09/05/2013 07:56 AM, David Nalley wrote:
On Thu, Sep 5, 2013 at 7:00 AM, Daan Hoogland wrote:
-1 on no docs no submits.
Docs are important to people that need a contribution they didn't
write themselves. The first ones are the ones to write docs where
missing. You contribute because you nee
On Thu, Sep 5, 2013 at 7:00 AM, Daan Hoogland wrote:
> -1 on no docs no submits.
>
> Docs are important to people that need a contribution they didn't
> write themselves. The first ones are the ones to write docs where
> missing. You contribute because you need code, not because you need
> docs on
er 2013 07:14
> To: dev@cloudstack.apache.org
> Cc: aemne...@gmail.com
> Subject: Re: documentation/wiki is a mess
>
>
> On Sep 5, 2013, at 1:11 AM, Prasanna Santhanam wrote:
>
>> Radhika, what I meant was everyone should help out with docs. Esp.
>> those working on a
ubject: Re: documentation/wiki is a mess
On Sep 5, 2013, at 1:11 AM, Prasanna Santhanam wrote:
> Radhika, what I meant was everyone should help out with docs. Esp.
> those working on a feature should care most that the docs for their
> feature is perfect for an end user to understand, implem
, we need not trouble the code committers to write
>>> own docs is what I feel.
>>>
>>> Regards
>>> -Radhika
>>>
>>> -Original Message-
>>> From: Prasanna Santhanam [mailto:t...@apache.org]
>>> Sent: Thursday, Septembe
age-
> > From: Prasanna Santhanam [mailto:t...@apache.org]
> > Sent: Thursday, September 05, 2013 9:34 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: documentation/wiki is a mess
> >
> > On Tue, Sep 03, 2013 at 11:10:28AM -0700, Darren Shepherd wrote:
>
Please give us some examples ..
-Original Message-
From: Ahmad Emneina [mailto:aemne...@gmail.com]
Sent: Thursday, September 05, 2013 10:22 AM
To: dev@cloudstack.apache.org
Subject: Re: documentation/wiki is a mess
I think prasanna hit the nail on the head. I'm sure there are fea
ble the code committers to write
> own docs is what I feel.
>
> Regards
> -Radhika
>
> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org]
> Sent: Thursday, September 05, 2013 9:34 AM
> To: dev@cloudstack.apache.org
> Subject: Re: documentation
write own
docs is what I feel.
Regards
-Radhika
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Thursday, September 05, 2013 9:34 AM
To: dev@cloudstack.apache.org
Subject: Re: documentation/wiki is a mess
On Tue, Sep 03, 2013 at 11:10:28AM -0700, Darren Shepherd
On Tue, Sep 03, 2013 at 11:10:28AM -0700, Darren Shepherd wrote:
>
> The state of documentation of an open source projects says a lot
> about the community that develops it...
>
Esp. for XML documentation: I say we write our own docs if we want
our feature to be used. Or it dies a natural death
/CLOUDSTACK/How+to+build+CloudStack
http://cloudstack.apache.org/develop/environment.html
From: Chiradeep Vittal [chiradeep.vit...@citrix.com]
Sent: Tuesday, September 03, 2013 11:33 AM
To: dev@cloudstack.apache.org
Subject: Re: documentation/wiki is a mess
The
The wiki is also for users as content gets added between releases as well.
But the developer content can certainly be reorganized.
On 9/3/13 11:10 AM, "Darren Shepherd" wrote:
>The state of documentation and especially the wiki is a mess. I'd like
>to help clean this up, but I can't seem to r
The state of documentation and especially the wiki is a mess. I'd like
to help clean this up, but I can't seem to reconcile the difference
between the XML documentation and the wiki. Personally I feel the wiki
should be for development. The XML should be installation and admin
guides only.
16 matches
Mail list logo
