Here is one of the proposal from my end:
"Gluster maintainers responsibilities"Theme - Process & Infrastructure
- Tracking incoming reviews and managing pending review backlogs with the help of peer reviews/review marathon on a weekly basis
- Bug triaging & prioritization - Current form of community bugzilla triaging is all about putting a keyword "triaged" and assigning the BZ to right people and at most asking for further logs/information, while this helps in the initial screening but maintainers need to further look into them from their component and come up with a plan on "when to fix what" sort of model for bug fix updates.
- Addressing community users issues on a regular basis (both over email & IRC)
- Keeping a track on overall component health (cumulation of above three)
- Bug triaging & prioritization - Current form of community bugzilla triaging is all about putting a keyword "triaged" and assigning the BZ to right people and at most asking for further logs/information, while this helps in the initial screening but maintainers need to further look into them from their component and come up with a plan on "when to fix what" sort of model for bug fix updates.
- Addressing community users issues on a regular basis (both over email & IRC)
- Keeping a track on overall component health (cumulation of above three)
The key point to discuss with touching upon all the above points is how to balance out all of these activities with the other commitments (mostly development) you have for the project deliverables.
On Sat, Aug 13, 2016 at 1:18 AM, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
Hey All,
Gluster Developer Summit 2016 is fast approaching [1] on us. We are looking to have talks and discussions related to the following themes in the summit:
1. Gluster.Next - focusing on features shaping the future of Gluster
2. Experience - Description of real world experience and feedback from:
a> Devops and Users deploying Gluster in production
b> Developers integrating Gluster with other ecosystems
3. Use cases - focusing on key use cases that drive Gluster.today and Gluster.Next
4. Stability & Performance - focusing on current improvements to reduce our technical debt backlog
5. Process & infrastructure - focusing on improving current workflow, infrastructure to make life easier for all of us!
If you have a talk/discussion proposal that can be part of these themes, please send out your proposal(s) by replying to this thread. Please clearly mention the theme for which your proposal is relevant when you do so. We will be ending the CFP by 12 midnight PDT on August 31st, 2016.
If you have other topics that do not fit in the themes listed, please feel free to propose and we might be able to accommodate some of them as lightening talks or something similar.
Please do reach out to me or Amye if you have any questions.
Thanks!
Vijay
[1] https://www.gluster.org/events/summit2016/
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
--
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
