[Gluster-devel] gluster_gd2-nightly-rpms - do we need to continue to build for this?

There is no practical work being done on gd2, do we need to continue to have a build job? On Tue, 18 Feb 2020 at 05:46, wrote: > > See <https://ci.centos.org/job/gluster_gd2-nightly-rpms/643/display/redirect> > -- sankarshan mukhopadhyay <https://about.me/sanka

Re: [Gluster-devel] Community Meeting: Make it more reachable

On Wed, Jan 29, 2020, 17:14 Sunny Kumar wrote: > On Wed, Jan 29, 2020 at 9:50 AM Sankarshan Mukhopadhyay > wrote: > > > > On Wed, 29 Jan 2020 at 15:03, Sunny Kumar wrote: > > > > > > Hello folks, > > > > > > I would like to propose

Re: [Gluster-devel] Community Meeting: Make it more reachable

On Wed, 29 Jan 2020 at 15:03, Sunny Kumar wrote: > > Hello folks, > > I would like to propose moving community meeting to a time which is > more suitable for EMEA/NA zone, that is merging both of the zone > specific meetings into a single one. > I am aware that there are 2 sets of meetings now -

[Gluster-devel] following up on the work underway for improvements in ls-l - looking for the data on the test runs

We talked about a set of planned work underway which bring about substantial improvements in ls-l and similar workloads. Do we have the (a) data from the test runs to be shared more widely (b) the patchsets and issues to track this work? ___ Community M

[Gluster-devel] reminder: release 8 release notes tracker

This note is a reminder to add the topics which are being proposed to be included in the release notes. As part of a previous meeting, there is now an issue which tracks this https://github.com/gluster/glusterfs/issues/813 ___ Community Meeting Calendar:

[Gluster-devel] [cross posted] Gluster Community Meeting; component updates and untriaged bugs

In a previous instance of the APAC meeting of the Gluster community I had mentioned about looking at the component update section and considering providing a report on the untriaged bug load. The rationale is to ensure that instead of a large mess of "unknown" bugs, the maintainers (and thus the pr

[Gluster-devel] Following up on the Gluster 8 conversation from the community meeting

I had mentioned that I'll reach out to Amar to urge about making progress on Gluster 8. We did have a conversation and upon reviewing the present state of the list of issues/features with the release label, Amar would be setting up a meeting to obtain a more pragmatic and reality based plan. It is

Re: [Gluster-devel] [Gluster-Maintainers] Modifying gluster's logging mechanism

On Wed, Nov 27, 2019 at 7:44 AM Amar Tumballi wrote: > Hi Barak, > > My replies inline. > > On Thu, Nov 21, 2019 at 6:34 PM Barak Sason Rofman > wrote: > >> >> [snip] > >> Initial tests, done by *removing logging from the regression testing, >> shows an improvement of about 20% in run time*. T

Re: [Gluster-devel] [Gluster-Maintainers] Modifying gluster's logging mechanism

The original proposal from Barak has merit for planning towards an alpha form to be available. Has the project moved away from writing specifications and reviewing those proposals? Earlier, we used to see those rather than discuss in multi-threaded list emails. While recorded gains in performance a

Re: [Gluster-devel] [Gluster-users] Announcing Gluster release 5.10

Would it be necessary to update the 5.10 release notes with this being a "known issue"? On Tue, Oct 29, 2019 at 11:07 AM Hari Gowtham wrote: > > Hi, > > Hubert, I can see the 5.9 folder contains 5.9 packages. > > Alan, We just made a release for 5.10.So we can take this in for 5.11. > Can you ple

Re: [Gluster-devel] [Gluster-Maintainers] Proposal: move glusterfs development to github workflow, completely

On Fri, Aug 23, 2019 at 6:42 PM Amar Tumballi wrote: > > Hi developers, > > With this email, I want to understand what is the general feeling around this > topic. > > We from gluster org (in github.com/gluster) have many projects which follow > complete github workflow, where as there are few, s

Re: [Gluster-devel] More intelligent file distribution across subvols of DHT when file size is known

On Wed, May 22, 2019 at 6:53 PM Krutika Dhananjay wrote: > > Hi, > > I've proposed a solution to the problem of space running out in some children > of DHT even when its other children have free space available, here - > https://github.com/gluster/glusterfs/issues/675. > > The proposal aims to s

Re: [Gluster-devel] tests are timing out in master branch

On Wed, May 15, 2019 at 11:24 AM Atin Mukherjee wrote: > > There're random tests which are timing out after 200 secs. My belief is this > is a major regression introduced by some commit recently or the builders have > become extremely slow which I highly doubt. I'd request that we first figure

Re: [Gluster-devel] [Gluster-Maintainers] Release 6.1: Expected tagging on April 10th

On Tue, Apr 16, 2019 at 10:27 PM Atin Mukherjee wrote: > On Tue, Apr 16, 2019 at 9:19 PM Atin Mukherjee wrote: >> On Tue, Apr 16, 2019 at 7:24 PM Shyam Ranganathan >> wrote: >>> >>> Status: Tagging pending >>> >>> Waiting on patches: >>> (Kotresh/Atin) - glusterd: fix loading ctime in client gr

Re: [Gluster-devel] Following up on the "Github teams/repo cleanup"

On Fri 29 Mar, 2019, 01:04 Vijay Bellur, wrote: > > > On Thu, Mar 28, 2019 at 11:39 AM Sankarshan Mukhopadhyay < > sankarshan.mukhopadh...@gmail.com> wrote: > >> On Thu, Mar 28, 2019 at 11:34 PM John Strunk wrote: >> > >> > Thanks for bringing this

Re: [Gluster-devel] Following up on the "Github teams/repo cleanup"

the future of the > project. > I agree. And so, I am looking forward to additional individuals/maintainers agreeing to this so that we can codify it under the Gluster.org Github org too. > > On Wed, Mar 27, 2019 at 10:21 PM Sankarshan Mukhopadhyay > wrote: >> >> The on

[Gluster-devel] Following up on the "Github teams/repo cleanup"

The one at I am not sure if the proposal from Michael was agreed to separately and it was done. Also, do we want to do this periodically? Feedback is appreciated. ___ Gluster-deve

Re: [Gluster-devel] requesting review available gluster* plugins in sos

On Wed, Mar 20, 2019 at 10:00 AM Atin Mukherjee wrote: > > From glusterd perspective couple of enhancements I'd propose to be added (a) > to capture get-state dump and make it part of sosreport . Off late, we have > seen get-state dump has been very helpful in debugging few cases apart from > i

Re: [Gluster-devel] [Gluster-Maintainers] GF_CALLOC to GF_MALLOC conversion - is it safe?

On Thu, Mar 21, 2019 at 9:24 PM Yaniv Kaul wrote: >> Smallfile is part of CI? I am happy to see it documented @ >> https://docs.gluster.org/en/latest/Administrator%20Guide/Performance%20Testing/#smallfile-distributed-io-benchmark >> , so at least one can know how to execute it manually. > > > F

Re: [Gluster-devel] Coverity scan is back

On Tue, Mar 19, 2019 at 2:48 PM Yaniv Kaul wrote: > > After a long shutdown, the upstream Coverity scan for Gluster is back[1]. There hasn't been much by the way of explaining why the service was unavailable for a reasonably long period, has there? Thanks for the update back to the list! > We w

Re: [Gluster-devel] requesting review available gluster* plugins in sos

On Tue, Mar 19, 2019 at 8:30 PM Soumya Koduri wrote: > On 3/19/19 9:49 AM, Sankarshan Mukhopadhyay wrote: > > <https://github.com/sosreport/sos> is (as might just be widely known) > > an extensible, portable, support data collection tool primarily aimed > > at Linux d

[Gluster-devel] requesting review available gluster* plugins in sos

is (as might just be widely known) an extensible, portable, support data collection tool primarily aimed at Linux distributions and other UNIX-like operating systems. At present there are 2 plugins

[Gluster-devel] Github#268 Compatibility with Alpine Linux

Saw some recent activity on - is there a plan to address this or, should the interested users be informed about other plans? /s ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.glust

Re: [Gluster-devel] [Gluster-infra] 8/10 AWS jenkins builders disconnected

1] https://review.gluster.org/#/c/glusterfs/+/22290/ -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Latency analysis of GlusterFS' network layer for pgbench

On Fri 28 Dec, 2018, 12:44 Raghavendra Gowdappa > > On Mon, Dec 24, 2018 at 6:05 PM Raghavendra Gowdappa > wrote: > >> >> >> On Mon, Dec 24, 2018 at 3:40 PM Sankarshan Mukhopadhyay < >> sankarshan.mukhopadh...@gmail.com> wrote: >> >>

Re: [Gluster-devel] Implementing multiplexing for self heal client.

On Fri, Dec 21, 2018 at 6:30 PM RAFI KC wrote: > > Hi All, > > What is the problem? > As of now self-heal client is running as one daemon per node, this means > even if there are multiple volumes, there will only be one self-heal > daemon. So to take effect of each configuration changes in the clu

Re: [Gluster-devel] Latency analysis of GlusterFS' network layer for pgbench

[pulling the conclusions up to enable better in-line] > Conclusions: > > We should never have a volume with caching-related xlators disabled. The > price we pay for it is too high. We need to make them work consistently and > aggressively to avoid as many requests as we can. Are there current i

Re: [Gluster-devel] Whats latest on Glusto + GD2 integration?

On Mon, Nov 5, 2018 at 8:35 AM Atin Mukherjee wrote: > > Thank you Rahul for the report. This does help to keep community up to date > on the effort being put up here and understand where the things stand. Some > comments inline. > > On Sun, Nov 4, 2018 at 8:01 PM Rahul Hinduja wrote: >> >> Hel

Re: [Gluster-devel] POC- Distributed regression testing framework

On Thu, Oct 4, 2018 at 6:10 AM Sanju Rakonde wrote: > On Wed, Oct 3, 2018 at 3:26 PM Deepshikha Khandelwal > wrote: >> >> Hello folks, >> >> Distributed-regression job[1] is now a part of Gluster's >> nightly-master build pipeline. The following are the issues we have >> resolved since we starte

Re: [Gluster-devel] [Gluster-Maintainers] Glusto Happenings

acc) >> >> >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-devel > > > > -- > Amye Scavarda | a...@redhat.com | Gluster Community Lead > __

Re: [Gluster-devel] Python components and test coverage

- > nigelb > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-devel -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>

Re: [Gluster-devel] [Gluster-users] Gluster Documentation Hackathon - 7/19 through 7/23

let us know if you have any questions. > > Thanks, > Amar & Vijay > > [1] > https://docs.google.com/document/d/11LLGA-bwuamPOrKunxojzAEpHEGQxv8VJ68L3aKdPns/edit?usp=sharing > -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)

ist: >> >> https://docs.google.com/spreadsheets/d/1IF9GhpKah4bto19RQLr0y_Kkw26E_-crKALHSaSjZMQ/edit?usp=sharing >> >> [4] Nightly run dashboard: https://build.gluster.org/job/nightly-master/ > > Locking master is fine, this seems like there's been ample n

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)

the tests were passing. It happened > on > both machine instances I tried. > Ugh! -infra team should have an issue to work with and resolve this. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-de

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)

; possible issues here. > > @Mohit, request you to take a look at the line coverage failures as > well, as you handle the failures in this test. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)

lists (so that duplication is avoided) to >> get this to a GREEN status. >> >> GREEN: >> 1. cpp-check >> 2. RPM builds >> >> IGNORE (for now): >> 1. clang scan (@nigel, this job requires clang warnings to be fixed to >> go green, right?) >> >> Shyam -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] How long should metrics collection on a cluster take?

metrics I assume the latest already available > would be returned and we are not going to fetch them when queried. This is > both fragile (imagine an entity that doesn't respond well) and adds latency > and will be inaccurate anyway a split second later. > > Y. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] How long should metrics collection on a cluster take?

how to come to a conclusion > about which path to take and what problems to solve. > > I will be happy to raise github issues based on our conclusions on this mail > thread. > > -- > Pranith > -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> __

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May

On Tue, Mar 13, 2018 at 1:05 PM, Pranith Kumar Karampuri wrote: > > > On Tue, Mar 13, 2018 at 7:07 AM, Shyam Ranganathan > wrote: >> >> Hi, >> >> As we wind down on 4.0 activities (waiting on docs to hit the site, and >> packages to be available in CentOS repositories before announcing the >> rel

Re: [Gluster-devel] [Gluster-Maintainers] IMP: Release 4.0: CentOS 6 packages will not be made available

luster packages. > It would be important to document a guidance for any users considering Gluster 3.x/CentOS6 --> Gluster4.x/CentOS7 It is implied that the 3.x/CentOS7 --> 4.x/CentOS7 would be tested -- sankarshan mukhopadhyay <https://about

[Gluster-devel] Fwd: [CentOS-devel] ansible in CentOS Extras

roles ( paas / cloud sig etc ) is there anything the SIG's need to validate before this content hits mirror.centos.org in a few days time ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc -- sankarshan mukho

Re: [Gluster-devel] Release 3.12: Glusto run status

On Wed, Aug 30, 2017 at 6:03 AM, Atin Mukherjee wrote: > > On Wed, 30 Aug 2017 at 00:23, Shwetha Panduranga > wrote: >> >> Hi Shyam, we are already doing it. we wait for rebalance status to be >> complete. We loop. we keep checking if the status is complete for '20' >> minutes or so. > > > Are yo

Re: [Gluster-devel] Glusterd2 - Some anticipated changes to glusterfs source

On Thu, Aug 17, 2017 at 12:46 PM, Kaushal M wrote: > On Thu, Aug 3, 2017 at 2:12 PM, Milind Changire wrote: >> >> >> On Thu, Aug 3, 2017 at 12:56 PM, Kaushal M wrote: >>> >>> On Thu, Aug 3, 2017 at 2:14 AM, Niels de Vos wrote: >>> > On Wed, Aug 02, 2017 at 05:03:35PM +0530, Prashanth Pai wrote:

Re: [Gluster-devel] Fwd: tendrl-release v1.5.0 (Milestone1) is available

On Sat, Aug 5, 2017 at 8:50 AM, Vijay Bellur wrote: > Thank you Rohan for letting us know about this release! > > I looked for screenshots of the dashboard and found a few at [1]. Are there > more screenshots that you can share with us? > The Metrics page (URL below) was intended to track the met

Re: [Gluster-devel] Questions on github

ieved is when the developers/maintainers/those-who-know respond more often. The tooling or, medium is not what is the crucial part here. However, it becomes critical when there are far too many of avenues and too little attention on a regular basis. *That* is a far from ideal situation. -- sankarshan mu

Re: [Gluster-devel] Questions on github

e over to Github issues. There are obvious advantages to using Issues. But there are also a small number of must-do things to manage this approach. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing l

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri wrote: > > > On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay > wrote: >> >> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: >> > I personally prefer github questions than mailing list, becaus

Re: [Gluster-devel] Questions on github

ake > sure at least we respond to questions which is pending. Is the on-going discussion in this thread about using <https://github.com/gluster/glusterfs/issues> as a method to have questions and responses from the community? -- sankarshan mukhopadhyay <https://a

Re: [Gluster-devel] What is the risk to upgrade glusterfs server version?

o care about upgrading glusterfs server? Thanks. Would it be possible to have more detail about the current/deployed environment and the expected upgrade targets? -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel ma

Re: [Gluster-devel] Events API new Port requirement

On Fri, Sep 9, 2016 at 3:55 AM, Niels de Vos wrote: > On Thu, Sep 08, 2016 at 10:03:03PM +0530, Sankarshan Mukhopadhyay wrote: >> On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos wrote: >> > This definitely has my preference too. I've always wanted to try to >> >

Re: [Gluster-devel] Events API new Port requirement

assignment of a new service name and port number value? -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Post mortem of features that didn't make it to 3.9.0

id others in the team suspect the developers are not focusing on things > that are of priority but didn't communicate? > 6) Were there any infra issues that delayed delivery of this > feature(regression failures etc)? > 7) Were there any big delays in reviews of patches? > >

Re: [Gluster-devel] Regular Performance Regression Testing

ithub.com/avati/perf-test/blob/master/perf-test.sh -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Backup support for GlusterFS

ies are > also accessible to the clients connected to the source. Perhaps this is when the developers of snapshot feature would need to chime in on the possible sequence of things to be done. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>

Re: [Gluster-devel] [gluster-devel] Documentation Tooling Review

of September. This is a good start. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Proposing a framework to leverage existing Python unit test standards for our testing

to Overview, and "8. Running Unit Tests"--then pick and choose from > there. I finally had a bit of time to go through the videos in sequence. And I'd like to put out a note of thanks for compiling them for everyone in the project to take a

Re: [Gluster-devel] performance issues Manoj found in EC testing

back-of-the-envelope calculations. Is it possible to provide additional detail about this exercise in terms of setup; tests executed; data sets generated? -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing

Re: [Gluster-devel] [Gluster-Maintainers] Release Management Process change - proposal

ers to ack content and stability of components by June 9th. > 4. Release 3.7.12 around June 9th after we have all acks in place. Would 3 days be sufficient to get the content for the website and a bit of PR written up? -- sankarshan mukhopadhyay <https://about.me

Re: [Gluster-devel] Idea: Alternate Release process

elease? >>>>> Should we be maintaining compatibility with LTS releases with the >>>>> latest release? >>>> >>>> Each LTS release will have seperate list of features to be >>>> enabled. If we make any breaking changes(

Re: [Gluster-devel] Suggest a feature redirect

contributing the feature idea needs to know that something was done with it and it wasn't a /dev/null -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org http://

Re: [Gluster-devel] Reducing the size of the glusterdocs git repository

ideally remain for binaries (install-ready objects) than presentations. There are specialized web properties for presentations and video which can be better ways to do this. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>

[Gluster-devel] Weekly Community Meeting [was:Re: [Gluster-users] Show and Tell sessions for Gluster 4.0]

to create space for participation - whether in the form of thinking over the agenda or, times which suit such participants. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.o

Re: [Gluster-devel] Show and Tell sessions for Gluster 4.0

On Mon, May 9, 2016 at 11:55 AM, Atin Mukherjee wrote: > 1. We use the weekly community meeting slot once in a month > or 2. Have a dedicated separate slot (probably @ 12:00 UTC, last > Thursday of each month) [2] would be nicer to set up a calendar for. -- sankarshan mukhopadhy

Re: [Gluster-devel] Google Summer of Code Application opens Feb 8th - Call For Mentors

f ideas which are also attached with (at least) one mentor. More at <https://flossmanuals.net/GSoCMentoring/making-your-ideas-page/> (as a manner of guidance) -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Gluster testing matrix

On Wed, Nov 25, 2015 at 7:37 PM, Atin Mukherjee wrote: > We'd also need IPv6 support in our infra going forward. Worth a discussion on the -infra@ list to check and verify readiness. -- sankarshan mukhopadhyay <https://about.me/sankarshan.m

Re: [Gluster-devel] removing "Target Release" from GlusterFS bug reports.

Triage process at > http://gluster.readthedocs.org/en/latest/Contributors-Guide/Bug-Triage/ > > Any objections? Has it ever been used to add context to a filed bug? -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___

Re: [Gluster-devel] Troubleshooting and Diagnostic tools for Gluster

n installed system to a possible symptom? Or, do a collection of events lead up to an observed failure (which, in turn, is recorded as a series of events on the logs)? -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___

Re: [Gluster-devel] Troubleshooting and Diagnostic tools for Gluster

rs. Diagnostics and remediation become important when a higher level abstraction (eg. a management construct for Gluster deployments are involved). What your thoughts on such frameworks being able to consume the logs; identify the possible issues and recommend a fix/solution? Does this pro

Re: [Gluster-devel] gluster readdocs unaccessible

On Wed, Oct 14, 2015 at 2:03 PM, Avra Sengupta wrote: > I am unable to access gluster.readdocs.org . Is anyone else facing the same > issue. <https://gluster.readthedocs.org/en/latest/> ? -- sankarshan mukhopadhyay <https://about.me/sankarsh

Re: [Gluster-devel] question about how to handle bugs filed against End-Of-Life versions of glusterfs

the problem persists after upgrading to the latest version of Fedora, which is available from:http://fedoraproject.org/get-fedora -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing lis

[Gluster-devel] [Cross-posted] Re: Gentle Reminder.. (Was: GlusterFS Documentation Improvements - An Update)

h is not ported, feel free to raise this by > opening an issue in [2] or if you would > like to port your documents, send a pull request. > > > > [1] https://github.com/gluster/glusterdocs > [2] https://github.com/gluster/glusterdocs/issues -- sankarshan mukhopadhyay <h

Re: [Gluster-devel] GlusterFS Documentation Improvements - An Update

gt; Plans page on GitHub. This can be an excellent way to track a document > through multiple rounds of collaborative editing in real time. This is a sound idea as well :) -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel