On 04/21/2012 04:15 PM, Ed Heron wrote: > On Sat, 2012-04-21 at 16:05 +0100, Karanbir Singh wrote: >> ... >> But, most of it can be automated isnt it ? and the docs are only ever >> updated once every 6 to 8 months. Its more of a case of someone taking >> the task up, and spending the day or two needed to get to grips with >> whats involved and doing 1 doc. We can then scale up the effort from >> there. Breaking inertia is key. > > I would say the RHEL docs are a starting point. The first step is to > remove the RHEL logos and such. The next step is to change the pieces > that don't apply and add any sections for stuff that isn't close. At > that point, the docs become an animal completely separate from the RHEL > docs. > > Future RHEL docs would then have to be diff'd to discover what changes > they've made and decide if we wish to add their changes to CentOS docs. > > I can fantasize that RHEL might even check out our docs and see if any > of our changes are worth adding back into their docs. One thing to be very careful of is to meet all the licensing requirements to change to documents. The earlier documents were not allowed to be changed ... see this link: http://www.centos.org/docs/4/4.5/rhel-ig-x8664-multi-en-4/ln-id2778852.html The newer documentation is not licensed that way, but like this: "The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version." That would mean that people should look at each individual license of any documentation .. and in this case, one should be able to make changes and just point to the original. We should likely make the changes in some kind of Version Control System ... git seems to be the best to use now. Then people can see what is changed from the original at any point in time ... and we might be able to more easily change updated versions in the future.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS-docs mailing list CentOS-docs@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-docs
