<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Oct 17, 2015 4:30 PM, "Humble Devassy Chirammal" <<a href="mailto:humble.devassy@gmail.com">humble.devassy@gmail.com</a>> wrote:<br>
><br>
><br>
> HI All,<br>
><br>
><br>
> >><br>
> I thought all specifications and design documented were supposed to get<br>
> pushed into Gerrit for glusterfs-specs?<br>
><br>
> <a href="https://github.com/gluster/glusterfs-specs">https://github.com/gluster/glusterfs-specs</a><br>
><br>
> >><br>
><br>
> glusterfs-specs in github is READONLY mirror of <a href="http://review.gluster.org/#/q/project:glusterfs-specs">http://review.gluster.org/#/q/project:glusterfs-specs</a> project in gerrit, same as glusterfs project.<br>
><br>
> So, the feature spec should land in gerrit first and review can happen from there. <br>
><br>
> ><br>
> My understanding is that someone (Humble?) was working on getting the<br>
> merged documents included on the readthedocs page.<br>
> ><br>
><br>
> Its not there yet.<br>
><br>
> To conclude: <br>
><br>
> The admin docs patches has to go in <a href="https://github.com/gluster/glusterdocs">https://github.com/gluster/glusterdocs</a> as PRs . As soon as the patch is merged it will reflect in <a href="http://gluster.readthedocs.org">gluster.readthedocs.org</a>.<br>
><br>
> The feature spec or design in <a href="http://review.gluster.org/#/q/project:glusterfs-specs">http://review.gluster.org/#/q/project:glusterfs-specs</a> project in gerrit and its auto synced to <a href="https://github.com/gluster/glusterfs-specs/">https://github.com/gluster/glusterfs-specs/</a><br>
><br>
> The developer doc is inside GlusterFS source code repo ( <a href="https://github.com/gluster/glusterfs/tree/master/doc/developer-guide">https://github.com/gluster/glusterfs/tree/master/doc/developer-guide</a> ). <br>
Thanks Humble, I believe everyone will adhere to it in terms of sending doc patches.<br>
><br>
> --Humble<br>
><br>
><br>
> On Fri, Oct 16, 2015 at 11:19 PM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
>><br>
>> On Fri, Oct 16, 2015 at 02:29:22PM +0000, Jeff Darcy wrote:<br>
>> > October 14 2015 11:02 PM, "Atin Mukherjee" <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br>
>> > > Could you push the design document along with the journal spec to<br>
>> > > <a href="http://gluster.readthedocs.org">gluster.readthedocs.org</a> as PRs?<br>
>> ><br>
>> > It's not clear where in the hierarchy these should go. I would have<br>
>> > guessed "Developer-guide" but that's back in the main source tree now.<br>
>> > Should I create a new directory for design specs?<br>
>><br>
>> I thought all specifications and design documented were supposed to get<br>
>> pushed into Gerrit for glusterfs-specs?<br>
>><br>
>> <a href="https://github.com/gluster/glusterfs-specs">https://github.com/gluster/glusterfs-specs</a><br>
>><br>
>> My understanding is that someone (Humble?) was working on getting the<br>
>> merged documents included on the readthedocs page. Not sure when we can<br>
>> expact that...<br>
>><br>
>> Niels<br>
>><br>
>> _______________________________________________<br>
>> Gluster-devel mailing list<br>
>> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
>> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br></p>
<p dir="ltr">-Atin<br>
Sent from one plus one</p>