[Gluster-devel] [Gluster-users] Proposal: Changes in Gluster Community meetings
Amar Tumballi Suryanarayan
atumball at redhat.com
Thu Apr 11 08:54:14 UTC 2019
Hi All,
Below is the final details of our community meeting, and I will be sending
invites to mailing list following this email. You can add Gluster Community
Calendar so you can get notifications on the meetings.
We are starting the meetings from next week. For the first meeting, we need
1 volunteer from users to discuss the use case / what went well, and what
went bad, etc. preferrably in APAC region. NA/EMEA region, next week.
Draft Content: https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g
----
Gluster Community Meeting
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Previous-Meeting-minutes>Previous
Meeting minutes:
- http://github.com/gluster/community
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#DateTime-Check-the-community-calendar>Date/Time:
Check the community calendar
<https://calendar.google.com/calendar/b/1?cid=dmViajVibDBrbnNiOWQwY205ZWg5cGJsaTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ>
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Bridge>Bridge
- APAC friendly hours
- Bridge: https://bluejeans.com/836554017
- NA/EMEA
- Bridge: https://bluejeans.com/486278655
------------------------------
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Attendance>Attendance
- Name, Company<Optional>
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Host>Host
- Who will host next meeting?
- Host will need to send out the agenda 24hr - 12hrs in advance to
mailing list, and also make sure to send the meeting minutes.
- Host will need to reach out to one user at least who can talk about
their usecase, their experience, and their needs.
- Host needs to send meeting minutes as PR to
http://github.com/gluster/community
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#User-stories>User stories
- Discuss 1 usecase from a user.
- How was the architecture derived, what volume type used, options,
etc?
- What were the major issues faced ? How to improve them?
- What worked good?
- How can we all collaborate well, so it is win-win for the community
and the user? How can we
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Community>Community
-
Any release updates?
-
Blocker issues across the project?
-
Metrics
- Number of new bugs since previous meeting. How many are not triaged?
- Number of emails, anything unanswered?
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Conferences--Meetups>Conferences
/ Meetups
- Any conference in next 1 month where gluster-developers are going?
gluster-users are going? So we can meet and discuss.
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#Developer-focus>Developer
focus
-
Any design specs to discuss?
-
Metrics of the week?
- Coverity
- Clang-Scan
- Number of patches from new developers.
- Did we increase test coverage?
- [Atin] Also talk about most frequent test failures in the CI and
carve out an AI to get them fixed.
<https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both#RoundTable>RoundTable
- <Open for anything which is not covered in agenda>
----
Regards,
Amar
On Mon, Mar 25, 2019 at 8:53 PM Amar Tumballi Suryanarayan <
atumball at redhat.com> wrote:
> Thanks for the feedback Darrell,
>
> The new proposal is to have one in North America 'morning' time. (10AM
> PST), And another in ASIA day time, which is evening 7pm/6pm in Australia,
> 9pm Newzealand, 5pm Tokyo, 4pm Beijing.
>
> For example, if we choose Every other Tuesday for meeting, and 1st of the
> month is Tuesday, we would have North America time for 1st, and on 15th it
> would be ASIA/Pacific time.
>
> Hopefully, this way, we can cover all the timezones, and meeting minutes
> would be committed to github repo, so that way, it will be easier for
> everyone to be aware of what is happening.
>
> Regards,
> Amar
>
> On Mon, Mar 25, 2019 at 8:40 PM Darrell Budic <budic at onholyground.com>
> wrote:
>
>> As a user, I’d like to visit more of these, but the time slot is my 3AM.
>> Any possibility for a rolling schedule (move meeting +6 hours each week
>> with rolling attendance from maintainers?) or an occasional regional
>> meeting 12 hours opposed to the one you’re proposing?
>>
>> -Darrell
>>
>> On Mar 25, 2019, at 4:25 AM, Amar Tumballi Suryanarayan <
>> atumball at redhat.com> wrote:
>>
>> All,
>>
>> We currently have 3 meetings which are public:
>>
>> 1. Maintainer's Meeting
>>
>> - Runs once in 2 weeks (on Mondays), and current attendance is around 3-5
>> on an avg, and not much is discussed.
>> - Without majority attendance, we can't take any decisions too.
>>
>> 2. Community meeting
>>
>> - Supposed to happen on #gluster-meeting, every 2 weeks, and is the only
>> meeting which is for 'Community/Users'. Others are for developers as of
>> now.
>> Sadly attendance is getting closer to 0 in recent times.
>>
>> 3. GCS meeting
>>
>> - We started it as an effort inside Red Hat gluster team, and opened it
>> up for community from Jan 2019, but the attendance was always from RHT
>> members, and haven't seen any traction from wider group.
>>
>> So, I have a proposal to call out for cancelling all these meeting, and
>> keeping just 1 weekly 'Community' meeting, where even topics related to
>> maintainers and GCS and other projects can be discussed.
>>
>> I have a template of a draft template @
>> https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g
>>
>> Please feel free to suggest improvements, both in agenda and in timings.
>> So, we can have more participation from members of community, which allows
>> more user - developer interactions, and hence quality of project.
>>
>> Waiting for feedbacks,
>>
>> Regards,
>> Amar
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>
>>
>>
>
> --
> Amar Tumballi (amarts)
>
--
Amar Tumballi (amarts)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20190411/43f4d414/attachment-0001.html>
More information about the Gluster-devel
mailing list