[Gluster-Maintainers] Maintainer Meeting notes and AIs - 5th Apr

[Atin Mukherjee]

GlusterD RFEs/backlog github population is completed now and can be tracked
at [1].


[1]
https://github.com/gluster/glusterfs/issues?q=is%3Aissue+is%3Aopen+label%3A%22CB%3A+glusterd%22

On Tue, Apr 11, 2017 at 9:27 PM, Shyam <srangana at redhat.com> wrote:

> On 04/11/2017 01:46 AM, Amar Tumballi wrote:
>
>>
>>
>> On Tue, Apr 11, 2017 at 3:52 AM, Vijay Bellur <vbellur at redhat.com
>> <mailto:vbellur at redhat.com>> wrote:
>>
>>     Hey All,
>>
>>     We had a good discussion in last week's maintainers meeting. Meeting
>>     notes can be found at [1] and the recording is available at [2].
>>
>>     We have the following AIs from last meeting:
>>
>>     a> All maintainers to publish backlog in github issues [3] by next
>>     meeting (4/19).
>>
>>
>> Let me know the proper labels required for each of this issues. @Shyam,
>> can we target getting proper labels also by 4/19 ?
>>
>
> Current labels are:
>   - CB: *, where * are the component names, if anything is missing, send a
> note here (on maintainers) or otherwise and the label will be created (or
> contact a maintainer in your TZ for quicker turnaround)
>   - Exp: *, for experimental big changes (GD2, DHT2, I have block there
> but not sure if there is anything in that to add to Gluster, and a more
> generic "Feature Wishlist")
>   - FA: *, which are focus areas, I added "Usability" to this list (just
> now).
>   - Type: {Bug|Enhancement|ReleaseActivity)
>   - Prio: {High|Medium|Low} but we can ignore this for now, we are not
> prioritizing the issues yet
>
> We should not need anymore at the moment (till we get to tracking bugs as
> well as github issues).
>
> Boards:
>   We have the following boards,
>     - Releases, for 3.11, 3.12, 4.0 releases
>     - Focus Areas, for focus area owners to give a birds eye (or detailed)
> work planned and in action at the moment
>
>   I would like to add,
>     - Component: *, boards so that we can also show "work planned and in
> action" for components, but this needs maintainer action
>     - Same for experimental features
>
>
>>
>>
>>     b> Publish 4.0 proposal by 4/19. Amar - can you please circulate the
>>     document that you have been curating when it is ready?
>>
>>
>> It is ready,
>> https://docs.google.com/a/redhat.com/document/d/1bF8xXSsBjcX
>> 2QogfvXWk1dG5fQZLhOBWYt79uUYTT3g/edit?usp=sharing
>>
>> If there is an issue accessing the document, let me know, will either
>> move it to hackmd or personal google drive.
>>
>
> I will take this and put it out in a mail separating things into 3.11 and
> 3.12/4.0 and ask owners to add issues for the same, and populate the
> release board. Just so that we refer to the scope in github and not a
> document and github.
>
>
>> Regards,
>> Amar
>>
>>
>>
>>     Please respond here if you need any assistance with the AIs. Let us
>>     do a round table and review respective  github issue backlogs in
>>     next week's meeting.
>>
>>     Thanks,
>>     Vijay
>>
>>     [1] https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQ
>> CMCYIQA===?both
>>     <https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarB
>> QCMCYIQA===?both>
>>
>>     [2] https://bluejeans.com/s/Nx4MS <https://bluejeans.com/s/Nx4MS>
>>
>>     [3] https://github.com/gluster/glusterfs/issues
>>     <https://github.com/gluster/glusterfs/issues>
>>
>>
>>
>>
>> --
>> Amar Tumballi (amarts)
>>
>>
>> _______________________________________________
>> maintainers mailing list
>> maintainers at gluster.org
>> http://lists.gluster.org/mailman/listinfo/maintainers
>>
>> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers
>



-- 

ATin Mukherjee

Associate Manager, RHGS Development

Red Hat

<https://www.redhat.com>

amukherj at redhat.com    M: +919739491377
<http://redhatemailsignature-marketing.itos.redhat.com/>     IM: IRC:
atinm, twitter: @mukherjee_atin
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20170411/8e82cfe2/attachment.html>