Right now, if someone wants to be able to get their code into the main Gluster github project, there's no set process for this.
We need:

• A way for people to communicate their feature to us as well as where they'd like it to live
• License (or variants)
• A process for moving this code over
• Who should sign off on it.

It has been pointed out that the one thing slack has going for it that IRC does not is the ease-of-use as a mobile application. Sure, it can be done with IRC but it requires configuring and hosting external services where slack does not have that requirement.

Currently a "gluster" slack exists. We do not know who registered it.

I propose we just create "gluster-community" slack and use slackin to have a more friendly url at slack.gluster.org.

Something that we should review is how many translators we're including that maybe are no longer active.
We should review for 4.1 and see what the current state is.

Recently I discovered that many communities are using "Discourse"
forum instead of the mailing list. Is it worth to evaluate that for
Gluster community as well?

https://www.discourse.org/

Features compared to the mailing list

• Open source
• One page per topic makes it easy to read replies and comments for a
  topic
• Shows interesting metrics like Number of Views, number of replies
  etc
• Admin dashboard
• and many more https://payments.discourse.org/features
• Mobile friendly

Who is using? (Not complete list, Just added a few)

• Docker https://forums.docker.com/
• Rust Community https://users.rust-lang.org/
• Elixir community https://elixirforum.com/
• Twitter https://twittercommunity.com/
• Codecademy https://discuss.codecademy.com/

Challenges(or Unknowns):

• Migration of mailing list archive if required.
• Migration of users

Date: October 27 - 28
Gluster Summit
We're at the last tail end of this, but I want to track what goes into a Gluster Summit planning anyways.

• Venue: complete
• Schedule: this process will need a separate ticket to track, but complete.
• Catering: review week of October 9
• Evening event: review week of October 9
• Website updated: complete
• Emails to attendees: week of October 9, October 16 x2
  -- Final email with details October 25
• Slide deadline: October 13 for rough draft, October 20th for final draft
• Swag: ordered, included custom lanyards from CZ supplier
• Badges: at printer's as of October 4th
• A/V filming: emails need to go out today, October 6th to find volunteers
• Registration: 56 as of October 6, ask in attendee email to confirm

For example, searching for the setting performance.parallel-readdir returns nothing:

Neither does parallel-readdir:

Although this is a valid configuration option:

gluster volume get test_static parallel-readdir
Option                                  Value
------                                  -----
performance.parallel-readdir            true

By contrast, searching for the setting network.ping-timeout does return something:

This issue is to track events planning from Feb 2018 through Feb 2019.

To do:

• Events Scoring spreadsheet to community, week of October 9, with cutoff by October 30 for feedback.
• Review on Community meeting what feedback provided?
• Put out a call for volunteers for staffing for events for 2018-2019 events schedule, week of November 6th
• Profit?
  (This is a rough placeholder outlining Gluster events for the next year, relying on community volunteers to staff majority of events for the year.)

The new website has content from the old website.
This issue is to track progress on an initiative to make the new website content's more inviting for users and contributors.

Tagging with both board and project, because this will need input from a wide variety of people.

Date: Jan 26-28, 2018
DevConfCZ

• Attending?
• Speaking?

The current active branch is master. Requesting it to be changes to main.

https://docs.gluster.org/en/latest/ needs a correct certificate installed for the domain, it's currently using the readthedocs wildcard cert.

Determine if one is needed.

Answer these questions first:

• What would a board be responsible for?
• What are some examples of the duties of other boards?
• Would Red Hat support this or hinder it?

Answer these questions second:

• What should the makeup of the board be?
• How can we measure success?
• Hopefully more questions to come from the comments.

BioDec will host a Gluster-community meeting in Bologna (Italy) on March 8th 2018, back-to-back with Incontro Devops Italia (http://2018.incontrodevops.it) and in the same venue as the conference.

We are aiming for a half-a-day event, ATM, but can grow in length., since we have already got a reservation for a 50-people room all-day.

Tentative program:

• 1-2 good tech talks;
• use-case presentation from Biodec.it/Datalab.es + proposed talks;
• QA/BOF

Things to discuss:

CfP: beginning just before Christmas?.
Ticketing: we usually use Eventbrite w. a tiny subscription fee too weed out time-waster and spammers. Number of putative attendees gets much more realistic.

This is a to-do to open the community survey, week of October 9th.
Include previous date from 2015 and 2016, if we have data from 2014, include that too.

This is a meta issue to handle the Gluster community working group setup. I'm modeling this after https://github.com/ansible/community/issues - with modifications as more people are available to help.

Labels:
events
newsletter
meetups
board
project

To do:

• Create templates for labels to make sure we've got good checklists for each thing we're doing. Project is the nebulous label that might be dropped, but it's a way to track things that are important to the project that might need a separate label in the future if we have a big enough initiative.

In the future, I would like to steal from Fedora's excellent contributor pathways and build out a 'what can I do for gluster':
http://whatcanidoforfedora.org/

It does not have to be nearly as flashy as this. It's on the projects tag until I figure out a better place to put this.

Instead of doing a community user survey in October-November, we'll move it up to June-July timeframe with some different questions and outcomes.

Date: Feb 3-4, 2018
FOSDEM

• Stand: applied for, sharing with Ceph
• DevRoom: @nixpanic with Thiago da Silva

Date: October 23-26
Open Source Summit Europe 2017

• who's attending?
• space at the Red Hat booth will be limited
• who's speaking?
• want to organize a group dinner?
• submit your event conversation reports! What'd you learn?

Just noticed a problem with the Gluster.org website... all of the links on the Consultants page are busted/nonfunctional.

Not sure where to file the bug though. Didn't see anything obvious on the website, so figured someone would at least see it here. 😄

Side note - the website for Datalab (www.datalab.com) appears to be offline. Not sure if that's a temp thing, or if their entry should be removed.

Our notes about 'who supports Gluster commercially' are out of date.
We should:

• Put out a call on the mailing list and social channels to have people identify who's supporting Gluster
• Confirm this is actually the case and that they want to be listed
• Update the website.

Adding this to the Fall/Winter tracker so that there's a deadline of end of Feb on this.

With the new website, we're able to track 404s a lot better, and I'm seeing a ton of hits for old /community documentation that's not been redirected properly.
This issue is to track progress to resolve these 404s: either by making a choice to redirect to docs.gluster.org, move content into docs.gluster.org, or something else that I haven't thought of yet.

May be add to ReadMe ?:

Location : #gluster-meeting on Freenode (webchat)

Somewhat related to #16, and while it might sound petty - it does make it hard to find good documentation, slides, talks, etc... when they're often bumped so far down on search engines.

The easiest way for me to demonstrate this was with a screenshot, I'm sorry it's not ideal (I've added a little humour to one of the points to make it up to you):

The upcoming release of Gluster 4.0 would require the users to upgrade systems from a possible set of 3.x series. It would be ideal to put together a matrix of the combination of client and server which lend themselves to easy upgrade. This matrix can be included in the documentation notes/section specifically pertaining to an upgrade.

Additionally, with the declared intent to discontinue the server RPMs for CentOS6 (due to Golang programming language run-time unavailability), it is likely that users would seek to standardize their operating infrastructures on a CentOS7 based deployment. Thus, a known good method or, a process that has been qualified would be needed for documentation.

Date: December 6-8
KubeCon NA

• Who's attending?
• Speakers?
• Booth demo (as space allows)

According to the minutes of the last Gluster Community Meeting on 08/03/2022,

• [Saju] Release updates
  • 9.x will receive updates once in 6 month
  • 10.x will receive update once in 3 month

Please clarify whether this will already affect maintenance releases 9.6 and 10.2 (and in that case modify RN 9.5 and RN 10.1).

For each major release, we'd like to have a retrospective. I'm creating a milestone for 3.13 and attaching this to it.
https://www.gluster.org/3-12-retrospectives/ - 3.12 is the first one built out as a form in the new website.

@amye suggested I post this here (good idea!).

For example, I'm giving a talk next week at Infracoders Melbourne called something like 'Clustered, Distributed File & Volume Storage' demonstrating how we're implementing Gluster for use with our Kubernetes volumes.

It would be nice to have some tshirts and stickers to give away to promote GlusterFS.

Another thing I thought of would be a small fridge magnet with a link / QR to the GlusterFS website.

It's not always clear what we mean by architects, maintainers and peers in our Maintainers file.

https://github.com/gluster/glusterfs/blob/master/MAINTAINERS

We have section entries, but we don't really outline the level of effort for each role. This could use more words.