Weird paragraph about chef-web-docs-2016 HOT 5 CLOSED

Also, you already cover this in a link from the page where that paragraph was found. It leads here:

http://docs.opscode.com/essentials_repository_create.html

from chef-web-docs-2016.

#16

from chef-web-docs-2016.

Hi Jeff,

What if those two sentences were combined, like this:

"The |chef| repository is located on a workstation and should be treated like source code. The |chef| repository can be cloned directly from |github| or it can be downloaded from |github| as a |tar gz| file, and then associated with another version source control system, such as |svn|, |mercurial|, or |bazaar|."

Thoughts?

James

From: Jeff Blaine [[email protected]]
Sent: Tuesday, December 04, 2012 10:36 AM
To: opscode/chef-docs
Subject: Re: [chef-docs] Weird paragraph (#15)

#16#16

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-11009190.

from chef-web-docs-2016.

Hi James.

IMO, it's redundant and should really just be removed from that particular page (PR #16 above).

Somewhat separately, assuming you keep it, it is vague in that it refers to "THE chef repository can be cloned directly from..." (emphasis mine). It poses it as if there is only one canonical place to start from, but doesn't explain up front that you're talking about "the Opscode boilerplate chef repository" ... that most people clone for starters.

It's very Hosted-Chef-Customer-centric which doesn't seem right (my opinion) given that Chef is a lot more than just Hosted Chef.

Just my 2 opinionated cents!

from chef-web-docs-2016.

OK. Thanks Jeff. I will take the pull requests that you have suggested and merge them.

At some point, I intend to have Hosted-, Private-, and Open Source-specific docs so I'll save this revised paragraph stuff for the future.

James

From: Jeff Blaine [[email protected]]
Sent: Tuesday, December 04, 2012 12:00 PM
To: opscode/chef-docs
Cc: James Scott
Subject: Re: [chef-docs] Weird paragraph (#15)

Hi James.

IMO, it's redundant and should really just be removed from that particular page (PR #16#16 above).

Somewhat separately, assuming you keep it, it is vague in that it refers to "THE chef repository can be cloned directly from..." (emphasis mine). It poses it as if there is only one canonical place to start from, but doesn't explain up front that you're talking about "the Opscode boilerplate chef repository" ... that most people clone for starters.

It's very Hosted-Chef-Customer-centric which doesn't seem right (my opinion) given that Chef is a lot more than just Hosted Chef.

Just my 2 opinionated cents!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-11013082.

from chef-web-docs-2016.