HackMD
  • Beta
    Beta  Get a sneak peek of HackMD’s new design
    Turn on the feature preview and give us feedback.
    Go → Got it
      • Create new note
      • Create a note from template
    • Beta  Get a sneak peek of HackMD’s new design
      Beta  Get a sneak peek of HackMD’s new design
      Turn on the feature preview and give us feedback.
      Go → Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Please check the box to agree to the Community Guidelines.
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive Export to Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive Import from Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Export to Google Drive Gist
    Import
    Dropbox Google Drive Import from Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    Write
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Please check the box to agree to the Community Guidelines.
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Revised Maintainers - AKA Maintainers 2.0 AI from Community Meeting, March 1: amye to work on revised maintainers draft with vbellur to get out for next maintainer's meeting. We'll approve it 'formally' there, see how it works for 3.11. ## Goals: * 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 ## Definition of Owners + Peers * Commit access to the project is not dependent on being a maintainer. A maintainer is a leadership role within the project to help drive the project forward. Commit access is granted to people who’ve been contributing for a while. We will grant this more freely going forward. We definitely want more contributors! ### Owner / Maintainer - * Subject matter expert. * Designs and approves large feature changes and decide overall goal of the component. * Works with other component owners for features and bugs. * **Responsibilities:** - **Reviews:** actively participate in reviews, approve changes. [Can request for component specific dashboard by creating a infra ticket] - **Bugzilla:** manage and triage bugs. Makes sure component health is getting better from release to release (by reducing total bugs on component) - **github issues:** manage and triage the labels and lanes for components. - **Peers:** recruiting, assisting / mentoring. - **Testing / Quality:** contribute and participate in building quality improvements, like glusto, .t tests, and other initiatives - **Meetings:** Participate in maintainers, bug triage and community meetings. - **Releases:** Adhere to release calendar, and make sure the features land in time for the release. Propose early to help release maintainers. - **Documentation:** Keep documentation up-to-date. Write more blogs, and review documentation. ### Peers * Assists the owner by reviewing and merging patches on a day-to-day basis. * Helps the owners design features. * Growing into subject matter expert, but not required to be engaged in the overall design of the component. * Able to work largely without day-to-day supervision. ## Additional changes: * We will be working on carving out new components for things that make logical sense. * A component can have multiple owners and peers. * The differences between the two roles are the technical leadership expected of them. * We recommend that owners and peers both review and merge patches for their component. * Project Lead and Community Lead should watch out for people owning lots of components with no peers. This may lead to burn out. Identify these owners and assist them in getting new peers. * Owners can pick peers for their components with just an announcement. ## Transition * Current maintainers get to choose between ownership/peer of components they're listed as owners. * Have people focus on maximum of two components as an owner. If they have more, they should be strongly suggested to invite new people as peers to be trained as future owners. * If current owners consider somebody as being ready to take over as owner of a component that they are managing, please announce new owners with appropriate justification on maintainers ML. * It's okay to drop a component if they are not able to find time/energy. Owners are requested to minimize disruption to the project by helping with transitions and announcing their intentions. * For all the components which fall out of active maintaience, any one from community can volunteer to become owner. This can be approved by council, depending on their overall contribution to the project. * Project Lead and Community Lead are responsible for maintaining the health of the community. This includes balancing work for component owners or choosing which components aren't included in the cycle in a way that minimizes disruption to the project. ### Other Questions: * How do I become maintainer / peer ? -- For active component which is already having a maintainer(s) As long as an active component in the project is well represented, we would not be changing the existing maintainers. -- For components which are not actively maintained. Any one can 'volunteer' to become maintainer for components which are not actively maintained. Upon getting the request, based on the contribution to the component in next 6 weeks, the maintainer status would be granted for the component. Note that, immediate inactivity (inactivity within next 6 weeks) on component by the new maintainer would lead to revoking the title. * How can there be 'non'-maintained components at all? There are multiple reasons why a component would have no-maintainers at a given time. 1. Voluntary retirement: Current maintainer would send a notification (due to personal reasons, like job change, can't spend enough time due to changes in family status etc etc), that he is not going to actively maintain the component. 2. Inactivity: If the maintainer is in-active for more than 6 months, the tech board (or call it tech council) would call out for action of removing the maintainer status for someone. 3. Giving up position for someone more eligible This can happen when the current maintainer thinks there is another peer, who is putting in lot of effort and deserves the maintainer status for the good of the component. This would be optional, and technical council can 'recommend' the action here, but would not force. References: Mozilla: https://www.mozilla.org/en-US/about/governance/policies/module-ownership/ Drupal: https://www.drupal.org/dcoc Kernel Graphics Community: https://www.youtube.com/watch?v=KJ9Y0midtW4

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully