Can we look at the format followed by Kafka: 
https://cwiki.apache.org/confluence/display/KAFKA/Index 
<https://cwiki.apache.org/confluence/display/KAFKA/Index> and Hive: 
https://cwiki.apache.org/confluence/display/Hive/Home 
<https://cwiki.apache.org/confluence/display/Hive/Home>

Both seem to be well organized and easy to follow. With wiki, it will be also 
easy for anyone to give comments/feedbacks.

Thanks

Bosco



> On Dec 8, 2014, at 6:29 AM, Kevin Minder <[email protected]> wrote:
> 
> Just as a data point, for Knox we went with keeping the docs in the site svn 
> repo for many of the reasons outlined by Bosco.
> 
> 
> On 12/8/14 3:26 AM, Don Bosco Durai wrote:
>> These are the following I had my list:
>> 1. Examples for REST API for policies
>> 2. Script to create HDFS folders for Audit
>> 3. Script to create policies in Ranger to allow components to write to HDFS 
>> audit folders
>> 
>> In future, we might more such tutorials and sample codes. Can you suggest a 
>> directory structure in GIT where we should add these?
>> 
>> Also, most of these are also applicable for the previous release (0.4), so 
>> which branches do you recommend to commit these?
>> 
>> Thanks
>> 
>> Bosco
>> 
>> 
>>> On Dec 7, 2014, at 4:23 PM, Selvamohan Neethiraj 
>>> <[email protected]> wrote:
>>> 
>>> 
>>> I prefer to keep the Structure/Docs in the Apache Ranger GIT Repo itself 
>>> (Already checked in in to git://git.apache.org/incubator-ranger.git/docs) 
>>> and
>>> have it updated to the doc site, http://ranger.incubator.apache.org.
>>> However, some of the dynamic content about the project could be done in the 
>>> wiki directly.
>>> 
>>> Selva-
>>> 
>>> 
>>> 
>>> On Dec 5, 2014, at 10:21 PM, Don Bosco Durai <[email protected]> wrote:
>>> 
>>>> Need suggestions where we can keep example codes, tutorials, best 
>>>> practices, etc for Apache Ranger.
>>>> 
>>>> One option is to store in GIT and have the location pointed from Wiki 
>>>> page. Or have it uploaded to Wiki page itself. We also have SVN for the 
>>>> Web site...
>>>> 
>>>> With GIT, the concern is the additional steps of review/commit and also 
>>>> the examples and tutorials might come post release, so updating the 
>>>> release branch might not be advisable.
>>>> 
>>>> FYI, those who are not aware, there were some nice contributions done to 
>>>> jump start the website and wiki page. Looking forward for more 
>>>> contributions/feedbacks/suggestions to clean this up and add more content.
>>>> 
>>>> https://cwiki.apache.org/confluence/display/RANGER/Index 
>>>> <https://cwiki.apache.org/confluence/display/RANGER/Index>
>>>> http://ranger.incubator.apache.org/ <http://ranger.incubator.apache.org/>
>>>> 
>>>> Feel free to create JIRAs for any typos or incorrectness. Also if you need 
>>>> any additional information.
>>>> 
>>>> Thank you
>>>> 
>>>> Bosco
>>>> 
>>>> 
>>>> 
>>> 
>>> -- 
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender immediately
>>> and delete it from your system. Thank You.
> 
> 
> -- 
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to 
> which it is addressed and may contain information that is confidential, 
> privileged and exempt from disclosure under applicable law. If the reader of 
> this message is not the intended recipient, you are hereby notified that any 
> printing, copying, dissemination, distribution, disclosure or forwarding of 
> this communication is strictly prohibited. If you have received this 
> communication in error, please contact the sender immediately and delete it 
> from your system. Thank You.

Reply via email to