similar to: Adding a slack for communication?

@Amye +1 for this great Idea, I am 100% for it. @Vijay for archiving purposes maybe it will be possible to use free service as https://slackarchive.io/ <https://slackarchive.io/> BR, Martin > On 9 Nov 2017, at 00:09, Vijay Bellur <vbellur at redhat.com> wrote: > > > > On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com <mailto:amye at

> On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com <mailto:amye at redhat.com>> wrote: > From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 <https://github.com/gluster/community/issues/13> > > Should we have a Gluster Community slack team? I'm interested in >

It's great idea! :) But think about creating Slack for all RedHat provided opensource projects. For example one Slack workspace with separated Gluster, Ceph, Fedora etc. channels. I can't wait for it! Bartosz On 08.11.2017 22:22, Amye Scavarda wrote: > From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13

On Wed, Nov 8, 2017 at 3:23 PM, Jim Kinney <jim.kinney at gmail.com> wrote: > The archival process of the mailing list makes searching for past issues > possible. Slack, and irc in general, is a more closed garden than a public > archived mailing list. > > That said, irc/slack is good for immediate interaction between people, say, > gluster user with a nightmare and a

The archival process of the mailing list makes searching for past issues possible. Slack, and irc in general, is a more closed garden than a public archived mailing list. That said, irc/slack is good for immediate interaction between people, say, gluster user with a nightmare and a knowledgeable developer with deep understanding and willingness to assist. If there's a way to make a

On Wed, Nov 8, 2017 at 3:09 PM, Vijay Bellur <vbellur at redhat.com> wrote: > > > On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com> wrote: >> >> From today's community meeting, we had an item from the issue queue: >> https://github.com/gluster/community/issues/13 >> >> Should we have a Gluster Community slack team? I'm

Awesome! You're on the list. Anyone else want to present? - amye On Fri, Nov 3, 2017 at 3:01 AM, Raghavendra Talur <rtalur at redhat.com> wrote: > I propose a talk > > "Life of a gluster client process" > > We will have a look at one complete life cycle of a client process > which includes: > * mount script and parsing of args > * contacting glusterd

On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com> wrote: > From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 > > Should we have a Gluster Community slack team? I'm interested in > everyone's thoughts on this. > > +1 to the idea. One of the limitations I have encountered in

Resolved! Try it again. - amye On Mon, Jun 5, 2017 at 5:07 PM, Mohammed Rafi K C <rkavunga at redhat.com> wrote: > Hi Amye, > > The form is not accessible, it says > > Feedback for Gluster 3.11 release > The form Feedback for Gluster 3.11 release is no longer accepting > responses. > Try contacting the owner of the form if you think this is a mistake. > > >

Hi all! Based on the popularity of wanting more lightning talks at Gluster Summit, we'll be trying something new: Gluster Developer Conversations. This will be a one hour meeting on November 28th at UTC 15:00, with five 5 minute lightning talks and time for discussion in between. The meeting will be recorded, and I'll be posting the individual talks separately in our community channels.

I propose a talk "Life of a gluster client process" We will have a look at one complete life cycle of a client process which includes: * mount script and parsing of args * contacting glusterd and fetching volfile * loading and initializing the xlators * how glusterd sends updates of volume options * brick disconnection/reconnection * glusterd disconnection/reconnection * termination of

Hi Amye, The form is not accessible, it says Feedback for Gluster 3.11 release The form Feedback for Gluster 3.11 release is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake. Regards Rafi KC On 06/05/2017 01:25 PM, Amye Scavarda wrote: > We're doing something new now with releases, running a retrospective > on what things we as a

We're doing something new now with releases, running a retrospective on what things we as a community should stop, what we should start, and what we should continue. With last week's release, here's our quick form for 3.11 https://goo.gl/forms/OkhNZDFspYqdN00g2 We'll keep this open until June 15th to give everyone time to give us feedback. Thanks! -- Amye Scavarda | amye at

Hey all! In the spirit of trying something new with the Community Meeting, this next one is changing a bit. I'm calling it 'Gluster Global Meetup' for lack of a better name (names welcomed) - and we're putting it on a video call. Same time as the community meeting, but a little different on the format. Here's a video call link for this that I'll add to the community

> > Not enthused with slack. And here's a real question: were you talking > about *instead* of this mailing list? No, certainly not instead of. A mailing list is essential. I'm part of a few slack communities and it seems an excellent platform for realtime discourse and noob baiting. Very sadly the #centos and #rhel freenode irc channels seem to be rather quiet these days and

Hallo, Considering the relative decline of IRC (sorry folks) I have set up a Slack for Enterprise Linux. I've been using "pythondev.slack.com" and honestly, its a fantastic tool for community support with really nice features for computer centric discussion. https://enterpriselinux.slack.com/shared_invite/MTY4MTM5NjQ2NTc5LTE0OTE5OTkyNTctMjkyNGU1NWQzOA My hope is that those running

On 11/01/2018 18:32, Shyam Ranganathan wrote: > Gluster Users, > > This is to inform you that from the 4.0 release onward, packages for > CentOS 6 will not be built by the gluster community. This also means > that the CentOS SIG will not receive updates for 4.0 gluster packages. > > Gluster release 3.12 and its predecessors will receive CentOS 6 updates > till Release 4.3

Gluster Users, This is to inform you that from the 4.0 release onward, packages for CentOS 6 will not be built by the gluster community. This also means that the CentOS SIG will not receive updates for 4.0 gluster packages. Gluster release 3.12 and its predecessors will receive CentOS 6 updates till Release 4.3 of gluster (which is slated around Dec, 2018). The decision is due to the following,

To be honest Freenode is nice and I'd be sad to see it replaced with anything. So cool to be a "/join #project" away from getting help. If we go Mattermost, can we have a searchable public archive of the chats? Something search engines can index and we can point people to? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- >

On Fri, Sep 1, 2017 at 9:42 AM, Michael Scherer <mscherer at redhat.com> wrote: > Le vendredi 01 septembre 2017 ? 14:02 +0100, Michael Scherer a ?crit : >> Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit : >> > Hello, >> > >> > To reduce confusion, we've setup docs.gluster.org pointing to >> > gluster.readthedocs.org. Both URLs will