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@xxxxxxxxxxxxxxxx> 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?-DarrellOn Mar 25, 2019, at 4:25 AM, Amar Tumballi Suryanarayan <atumball@xxxxxxxxxx> 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/OqZbh7gfQe6uvVUXUVKJ5gPlease 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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
