HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
      • Create new note
      • Create a note from template
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        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
    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 Gist
    Import
    Dropbox 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
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    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
    # SIG Community [Meeting Notes](https://hackmd.io/RmFqiyCASaKJyWdINuo8QQ) [Calendar](tinyurl.com/Op1st-SIG-Community-cal) [Project Board](https://github.com/orgs/operate-first/projects/16) --- ## 2022-06-30 - bi-weekly meeting ### Attendees - Karsten Wade @quaid - Michael Clifford @michaelclifford - Aakanksha Duggal @aakankshaduggal ### Agenda and Notes: 1. DS Meetup Transition * Repo move done * Jupyterbook done * Michael presented future of the meetup - https://youtu.be/SsS5QvpDbdA * Need to send a "request email" for co-chair and members of the community * Setup WG meeting - thor and/or Karsten reqd in meeting. * SCaLE workshop discussing, seeing if the full-day schedule Karsten proposed can work, discussions ongoing in Slack. ## 2022-06-16 - bi-weekly meeting ### Attendees - Karsten Wade @quaid - Michael Clifford @michaelclifford - Aakanksha Duggal @aakankshaduggal - Tray Keller ### Agenda and Notes: 1. DS Meetup Transition Working Group - Next steps? 1. PR with charter that makes it clear Community SIG owns this 2. Invite to WG on community@, Slack 1. (there's already a data-science channel, need to ensure we don't have two data-science channels) 4. Group identifed, then pick a meeting time 5. Get together, plan, execute 6. Migrate templates etc. from old repo to `community` repo 7. Identify a cutover date to new repo for storing the archive of meetups 8. 1. DS SIG Charter review - is there sufficient interest in this SIG? 1. https://github.com/operate-first/community/pull/193 2. Promo it at next meetup 1. Kruize - autotune, hpo 2. Group is beginning onboarding process 1. SCaLE workshop 1. Level: intermediate? beginner? 1. AIOps workshop: How DS and SRE support each other 3. Six weeks from today (five weeks to create) 4. Possible workshop leaders: Michael, Oindrilla, Humair 3. Morning is setting up the tools environment 4. Afternoon is doing things ### Actions 1. Michael makes the WG charter PR 2. Aakanksha invites WG participation, idea of adding a general meetup 3. Karsten to attend next meetup to propose WG and SIG 4. Karsten to write workshop follow-up email ## 2022-06-02 bi-weekly meeting ### Attendees - Karsten Wade @quaid - Thorsten @schwesig - Michael Clifford @michaelclifford - Jason Brooks - Bryan Montalvan @bryanmontalvan - Aakanksha Duggal ### Agenda and Notes: 1. Data Science SIG [Charter Proposal](https://github.com/operate-first/community/pull/193) 1. Request additional reviewers 1. Needs additonal community support beyond OSG DS team 1. Move Data Science Community Meetup to Operate First 1. [Issue](https://github.com/operate-first/community/issues/192) 1. Needs a community owner to hand off to 1. Onboarding Kruize Autotune & HPO - https://github.com/kruize/autotune - https://github.com/kruize/hpo - Where is our onboarding process doc? ### Brain dump: * ... ### Actions * ... --- ## 2022-05-19 bi-weekly meeting no meeting --- ## 2022-05-05 bi-weekly meeting ### Attendees - Karsten Wade @quaid - Thorsten @schwesig - Bryan Montalvan @bryanmontalvan - Jon Weiser ### Agenda and Notes: 1. SIG Data Science 1. Goal is a stand-alone group that consists of and represents wider DS interests in project. 2. Currently recruiting for leadership and members. 3. Existing Op1st DS engineers are interested and willing to help kickstart this group, and want to see it rooted in a wider group than just their team from the start. 3. DS Meetup => Op1st meetup 4. Discussions underway with DS Meetup leadership about evolving the meetup to be a general Op1st meetup. 5. Management would move under the Community SIG, potentially moved into an Events SIG or similar in the future. 5. Mailing lists and communication channels 1. Some SIG, WG, and subprojects need ways to email their users about e.g. meetings without requiring the users to learn all of the various Op1st methods. 2. One option is to have an easy way like an email proxy 1. We may want to give every SIG, WG, and subproject their own mailing lists as a natural place for discussions, decisions, and observing-the-action can take place. 1. The main community@ mailing list may be a barrier to some userbases; there needs to be a way to choose not to be on that mailing list and still participate as a user or contributor to a part of the project. 7. Open Services Group 1. OSG as a best practice for growing a community is not fully usable, because OSG is so far more an internal group yet 8. "Operate First" as a term 2. It's a continuity, the ideal state is when you start on development, you are operating from that same instance. 3. We want developers to be thinking about how to operate from the beginning, not just pondering operations, but actually operating. 4. We want operators to by developing from the beginning. 9. Blog update 4. https://operate-first.cloud/blog is live 5. Guides, template, and process docs are in PR: 6. https://github.com/operate-first/community-handbook/pull/43 7. https://github.com/operate-first/blog/pull/5 10. Training coming: 1. Likely-to-change test: https://www.operate-first.cloud/training/operate_first_mindset/intro.html 1. First two modules loaded in, getting hooked into new navigation and normal hookup as a Jupyter Notebook 11. Improving this meeting 1. Does this meeting show good inner workings? ### Brain dump: * SIG Metrics idea (not a hot topic, just came up) ### Actions * ... --- ## 2022-04-21 bi-weekly meeting ### Attendees - Karsten Wade @quaid - Thorsten @schwesig - Bryan Montalvan @bryanmontalvan ### Agenda and Notes: 1. KubeCon Vision 2. Organic Growth of Community 3. regular check with the WG that are working with the SIG Community ### Brain dump: * Organic Growth * **48h reminder slack&email!** * **2h reminder slack&email!** * post-meeting info? * lessons learned from OSG * be open, welcome new members personally and fast * Potentionally have an #introduce channel on slack, to make a more welcoming environment * mentor? in person, virtual, a few questions to start with * real mentor at the start maybe a lot of time/work, but could lead to experiences/lessons learned how to make a better "autointroduction" * Welcome "Template", Introduce yourself, typical questions * KubeCon Vision * May, 16th * May, Thu 12th: having website/things ready * Stickers, Swag, Website * Check with the WGs * celebrate epics/bigger goals with the team ### Actions * 48h reminder slack&email * 2h reminder slack&email * Stickers/Design * Swag * May, Thu 12th: having website/things ready --- ## 2022-04-07 bi-weekly meeting ### Attendees - Karsten Wade @quaid - Thorsten @Schwesig - Bryan Montalvan @bryanmontalvan - Humair Khan @humairak ### Agenda and Notes: 1. SIG minimal required processes vs guidelines 2. Have a README that includes purpose, meeting times, people involved, etc. 3. Publicize the meetings 4. Reminder about upcoming meeting in Slack, email 5. 48 hours in email and Slack, 2 hours ahead in Slack 6. 6. Publish minutes and recording to consistent page 7. 1. Agenda creation 2. Initial agenda is announced by chair 2 days ahead with meeting announcement 3. Invitation to add agenda items, sometimes with callouts to specific groups 4. Agenda is always open for people to add items 5. Chairs are responsible for priority of agenda items, driving the agenda during the meeting 1. Post meeting work 2. Publish meeting notes into sub-folder 3. Push video to YouTube 3. SIG Community meeting purpose 3. promotion of this venue 4. Data Science SIG ### Brain dump: * Send announcement/reminders on mailinglist/slack #announcements about upcoming meetings a few days ahead of said meeting * Create a meeting structure which effectively syncs members about sub-project and working group updates * Each SIG adds their updates to the agenda pre-meeting * Each SIG shares what has been accomplished from their respective sub-project/workin-group from the time in between meetings ### Actions * @humair PR for this min required processes * Chairs: Finish and follow this new process by next SIG Community meeting --- ## 2022-03-24 bi-weekly Meeting ### Attendees: - Marcel Hild @durandom - Karsten Wade @quaid - Thorsten Schwesig @schwesig - Jeremy Eder @jeremyeder - Bryan Montalvan @bryanmontalvan ### Agenda and Notes: 1. Project blog 1. https://github.com/operate-first/community/issues/24 1. Agreed: we can use Markdown files and gitops publishing process 1. Marcel will find some folks interested in doing the tooling side of this. 1. Karsten can create the editorial process in https://github.com/operate-first/community/issues/25 1. Defining SIG practices: 2. https://github.com/operate-first/community-handbook/issues/35 #### BrainDump (unsorted thoughts) * Does a SIG meeting needs to be "prepared" * Do "members" need to prepare/be prepared * How to lead a SIG * How to organize a SIG * What should be done during a SIG meeting * What should be discussed in a SIG meeting * Finding/Using best practices can be set until new practices are needed/brought up (e.g. HackMD) * If there is a WG/SP for a topic, it doesn't need to be discussed in the SIG? * What about MUST issues? Just wait until someone "assigns" * How to deal with the situation about internal and external members * what if... internal members are the majority * what if... internal members are the only group ### Actions: * Blog ready by mid of April @schwesig * SETTING best practice e.g. use HackMD (until other best practices are found) * Bulleted list pulling out all actions from the notes into one list * Format loose but must include one or more people who are responsible.

    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 Sign in via Google

    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