Re: [Gluster-devel] [Gluster-Maintainers] Maintainers 2.0 Proposal
Following up on this, this revision cycle is meant to be more clear about owners + peers, and less focused on the Red Hat shorthand for levels of responsibility. As far as further goals, I think we can outline Architects and Leads responsibility in a further cycle. I'll let Vijay respond to a further governance document. -amye On Fri, Apr 14, 2017 at 3:51 AM, Niels de Vos wrote: > On Fri, Apr 14, 2017 at 11:40:35AM +0200, Michael Scherer wrote: > > Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit : > > > In light of community conversations, I've put some revisions on the > > > Maintainers changes, outlined in the hackmd pad: > > > https://hackmd.io/s/SkwiZd4qe > > > > > > Feedback welcomed! > > > > > > Note that the goals of this are to expand out our reach as a project > > > (Gluster.org) and make it easy to define who's a maintainer for what > > > feature. > > > I'll highlight the goals in the document here: > > > > > > * Refine how we declare component owners in Gluster > > > * Create a deeper sense of ownership throughout the open source project > > > * Welcome more contibutors at a project impacting level > > > > > > We've clarified what the levels of 'owners' and 'peers' are in terms of > > > responsibility, and we'll look to implement this in the 3.12 cycle. > > > Thanks! > > > > So, I realize that the concept of component is not defined in the > > document. I assume everybody have a shared understanding about what it > > is, but maybe not, so wouldn't it make sense to define it more clearly ? > > > > Is this planned to be done later as part of "We will be working on > > carving out new components for things that make logical sense." ? > > > > As for example, with regard to my previous comment, would > > "infrastructure" be a component, would "documentation" be a component ? > > Indeed, that is one of the things that I mentioned in a similar way on > the previous version of the document. Because the document is aimed at > the Gluster Community, it should address not only the main GlusterFS > project, but also other "components maintained by the community". There > are many different projects in the Gluster Community, of which the > GlusterFS project is one, infrastructure, documentation and probably all > repositories under https://github.com/gluster are others. Modules for > Samba, NFS-Ganesha and other "external" projects probably do not count > towards "Gluster proper" and are not included in the "Maintainers 2.0" > approach (mentioning the excluded kinds of projects would be a good > thing too). > > Also, the other relevant "roles" like "Project Lead", "Community Lead" > and "Project Architect" need to be explained with their > responsibilities. A paragraph of their description should probably be > added to the MAINTAINERS [0] file when that gets updated too. A single > naming for the roles would be best (no more "maintainers" anywhere?). > Where would it be listed who has which role in the Gluster Community? > > When I click through the previous conversation, much of the feedback > that was given on an earlier version [1] has not been included or > addressed it seems. In one of the emails Vijay mentioned a "project > governance document" is being written, and that should probably give > more clarity when reading the Maintainers 2.0 proposal. A link to that > document would be helpful. > > Thanks, > Niels > > > 0. https://github.com/gluster/glusterfs/blob/master/MAINTAINERS > 1. http://lists.gluster.org/pipermail/maintainers/2017-March/002368.html > -- Amye Scavarda | a...@redhat.com | Gluster Community Lead ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Maintainers 2.0 Proposal
On Fri, Apr 14, 2017 at 2:40 AM, Michael Scherer wrote: > Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit : > > In light of community conversations, I've put some revisions on the > > Maintainers changes, outlined in the hackmd pad: > > https://hackmd.io/s/SkwiZd4qe > > > > Feedback welcomed! > > > > Note that the goals of this are to expand out our reach as a project > > (Gluster.org) and make it easy to define who's a maintainer for what > > feature. > > I'll highlight the goals in the document here: > > > > * Refine how we declare component owners in Gluster > > * Create a deeper sense of ownership throughout the open source project > > * Welcome more contibutors at a project impacting level > > > > We've clarified what the levels of 'owners' and 'peers' are in terms of > > responsibility, and we'll look to implement this in the 3.12 cycle. > > Thanks! > > So, I realize that the concept of component is not defined in the > document. I assume everybody have a shared understanding about what it > is, but maybe not, so wouldn't it make sense to define it more clearly ? > > Is this planned to be done later as part of "We will be working on > carving out new components for things that make logical sense." ? > > As for example, with regard to my previous comment, would > "infrastructure" be a component, would "documentation" be a component ? > > My understanding is that there's a working spreadsheet being refined to sort out what's an area that needs a maintainer defined, and what's something that maybe doesn't need a named maintainer. Documentation is a tricky place to get to, because that's something that you do just naturally so that future-you doesn't hate current-you. However, I'll see if I can't find that spreadsheet because the above document is more guidelines than practical reality. Anything else? - amye > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > > > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > > -- Amye Scavarda | a...@redhat.com | Gluster Community Lead ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking
On 04/17/2017 05:56 AM, Poornima Gurusiddaiah wrote: Further to the above, we are also considering the following features for this release, request feature owners to let us know if these are actively being worked on and if these will make the branching dates. (calling out folks that I think are the current feature owners for the same) 1) Halo - Initial Cut (@pranith) 2) IPv6 support (@kaushal) 3) Negative lookup (@poornima) Issue: https://github.com/gluster/glusterfs/issues/82 Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1442569 Patch: https://review.gluster.org/#/c/16952/ This feature is targeted for 3.11 as an experimental feature and mostly for SMB users only. Added to the 3.11 board. 4) Parallel Readdirp - More changes to default settings. (@poornima, @du) I think we should let it be optional for another release, until it stabilizes. However, for this release we would like to make it production feature (not experimental). I have raised the issue for the same: https://github.com/gluster/glusterfs/issues/166 Added some queries on the github issue, to understand the work, and we can target it for the release accordingly. Also for 3.11, one more item would be to make the md-cache improvements production feature, it is experimental currently. Issue for the same: https://github.com/gluster/glusterfs/issues/167 Same as above. Will add the release notes for all these features in the issues. I do not have permissions to add labels though. Release notes for 3.11 will be drafted post branching, at which point a request to all will be posted to update the same. Please update the same, using a review via gerrit, referencing your github issue #. Release notes are part of the glusterfs repository, hence updates to the same are like doc/code changes to the repository, hence require a submission via gerrit and not updates to the github issue. Hope this is clear, else please ask for more clarifications. Thanks, Poornima ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Coverity covscan for 2017-04-17-a9b5333d (master branch)
GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-04-17-a9b5333d ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Is anyone else having trouble authenticating with review.gluster.org over ssh?
h On Mon, Apr 17, 2017 at 12:48 AM, Nigel Babu wrote: > This should be fixed now: https://bugzilla.redhat.com/sh > ow_bug.cgi?id=1442672 > Thank you Nigel. > > > Vijay, can you link me to your failed Jenkins job? Jenkins should have > been able to clone since it uses the git protocol and not SSH. > This is a private jenkins instance that I use for running tests and it uses a ssh clone. Regards, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking
- Original Message - > From: "Shyam" > To: "Gluster Devel" > Cc: gluster-us...@gluster.org > Sent: Thursday, April 13, 2017 8:17:34 PM > Subject: Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and > feature tracking > > On 02/28/2017 10:17 AM, Shyam wrote: > > Hi, > > > > With release 3.10 shipped [1], it is time to set the dates for release > > 3.11 (and subsequently 4.0). > > > > This mail has the following sections, so please read or revisit as needed, > > - Release 3.11 dates (the schedule) > > - 3.11 focus areas > > Pinging the list on the above 2 items. > > > *Release 3.11 dates:* > > Based on our release schedule [2], 3.11 would be 3 months from the 3.10 > > release and would be a Short Term Maintenance (STM) release. > > > > This puts 3.11 schedule as (working from the release date backwards): > > - Release: May 30th, 2017 > > - Branching: April 27th, 2017 > > Branching is about 2 weeks away, other than the initial set of overflow > features from 3.10 nothing else has been raised on the lists and in > github as requests for 3.11. > > So, a reminder to folks who are working on features, to raise the > relevant github issue for the same, and post it to devel list for > consideration in 3.11 (also this helps tracking and ensuring we are > waiting for the right things at the time of branching). > > > > > *3.11 focus areas:* > > As maintainers of gluster, we want to harden testing around the various > > gluster features in this release. Towards this the focus area for this > > release are, > > > > 1) Testing improvements in Gluster > > - Primary focus would be to get automated test cases to determine > > release health, rather than repeating a manual exercise every 3 months > > - Further, we would also attempt to focus on maturing Glusto[7] for > > this, and other needs (as much as possible) > > > > 2) Merge all (or as much as possible) Facebook patches into master, and > > hence into release 3.11 > > - Facebook has (as announced earlier [3]) started posting their > > patches mainline, and this needs some attention to make it into master > > > > Further to the above, we are also considering the following features for > this release, request feature owners to let us know if these are > actively being worked on and if these will make the branching dates. > (calling out folks that I think are the current feature owners for the same) > > 1) Halo - Initial Cut (@pranith) > 2) IPv6 support (@kaushal) > 3) Negative lookup (@poornima) Issue: https://github.com/gluster/glusterfs/issues/82 Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1442569 Patch: https://review.gluster.org/#/c/16952/ This feature is targeted for 3.11 as an experimental feature and mostly for SMB users only. > 4) Parallel Readdirp - More changes to default settings. (@poornima, @du) I think we should let it be optional for another release, until it stabilizes. However, for this release we would like to make it production feature (not experimental). I have raised the issue for the same: https://github.com/gluster/glusterfs/issues/166 Also for 3.11, one more item would be to make the md-cache improvements production feature, it is experimental currently. Issue for the same: https://github.com/gluster/glusterfs/issues/167 Will add the release notes for all these features in the issues. I do not have permissions to add labels though. Thanks, Poornima > > > [1] 3.10 release announcement: > > http://lists.gluster.org/pipermail/gluster-devel/2017-February/052188.html > > > > [2] Gluster release schedule: > > https://www.gluster.org/community/release-schedule/ > > > > [3] Mail regarding facebook patches: > > http://lists.gluster.org/pipermail/gluster-devel/2016-December/051784.html > > > > [4] Release scope: https://github.com/gluster/glusterfs/projects/1 > > > > [5] glusterfs github issues: https://github.com/gluster/glusterfs/issues > > > > [6] github issues for features and major fixes: > > https://hackmd.io/s/BkgH8sdtg# > > > > [7] Glusto tests: https://github.com/gluster/glusto-tests > > ___ > > Gluster-devel mailing list > > Gluster-devel@gluster.org > > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
