Hi, glusterdocs repo[1] has been cleaned of presentation files. Contributors please discard your existing forks and clones. Repo description on github has been updated to indicate the same.
[1]: https://github.com/gluster/glusterdocs Regards, -Prashanth Pai ----- Original Message ----- > From: "Prashanth Pai" <[email protected]> > To: "Amye Scavarda" <[email protected]> > Cc: "Gluster Devel" <[email protected]>, "Humble Chirammal" > <[email protected]> > Sent: Thursday, May 19, 2016 12:35:35 PM > Subject: Re: [Gluster-devel] Reducing the size of the glusterdocs git > repository > > > ----- Original Message ----- > > From: "Amye Scavarda" <[email protected]> > > To: "Kaushal M" <[email protected]>, "Prashanth Pai" <[email protected]> > > Cc: "Raghavendra Talur" <[email protected]>, "Gluster Devel" > > <[email protected]>, "Humble Chirammal" > > <[email protected]> > > Sent: Thursday, May 19, 2016 12:31:34 PM > > Subject: Re: [Gluster-devel] Reducing the size of the glusterdocs git > > repository > > > > Prashanth, > > Is this something you can take on? > > Will do. Now that we have consensus. > > > Thanks! > > - amye > > > > > > On Thu, May 19, 2016 at 11:18 AM, Kaushal M <[email protected]> wrote: > > > > > As the majority seem to favour Prashanth's approach, I vote for it as > > > well. > > > > > > Just to make it clearer for all users, please add a **highlighted** > > > note in the README that informs any visitor to the github page of the > > > change. > > > > > > On Thu, May 19, 2016 at 11:15 AM, Raghavendra Talur <[email protected]> > > > wrote: > > > > > > > > > > > > On Thu, May 19, 2016 at 9:46 AM, Aravinda <[email protected]> wrote: > > > >> > > > >> +1 for Prashanth's approach. > > > > > > > > > > > > +1 > > > >> > > > >> regards > > > >> Aravinda > > > >> > > > >> On 05/18/2016 03:55 PM, Kaushal M wrote: > > > >> > > > >> On Wed, May 18, 2016 at 3:29 PM, Humble Devassy Chirammal > > > >> <[email protected]> wrote: > > > >> > > > >> On Wed, May 18, 2016 at 3:26 PM, Amye Scavarda <[email protected]> > > > >> wrote: > > > >> > > > >> All in favor of the 'everyone working on this should clone again' > > > >> approach. > > > >> > > > >> Both approaches require cloning again, so which on are we voting for? > > > >> > > > >> 1. Prashanth's approach > > > >> - modify existing repo > > > >> - users re clone > > > >> - push force to their forks on github > > > >> > > > >> 2. Misc's approach > > > >> - create a new minified repo > > > >> - users clone/fork the new repo > > > >> > > > >> I don't mind either. > > > >> > > > >> +2 on the same thought. :) > > > >> > > > >> _______________________________________________ > > > >> Gluster-devel mailing list > > > >> [email protected] > > > >> http://www.gluster.org/mailman/listinfo/gluster-devel > > > >> > > > >> _______________________________________________ > > > >> Gluster-devel mailing list > > > >> [email protected] > > > >> http://www.gluster.org/mailman/listinfo/gluster-devel > > > >> > > > >> > > > >> > > > >> _______________________________________________ > > > >> Gluster-devel mailing list > > > >> [email protected] > > > >> http://www.gluster.org/mailman/listinfo/gluster-devel > > > > > > > > > > > _______________________________________________ > > > Gluster-devel mailing list > > > [email protected] > > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > > > > > > > > > -- > > Amye Scavarda | [email protected] | Gluster Community Lead > > > _______________________________________________ > Gluster-devel mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-devel
