Sandra Gesing
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • 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
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
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
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Announcing the US-RSE Local and Regional Working Group Authors: Rafael Mudafort, Sandra Gesing, Jordan Perr-Sauer, Mahmood Shad, Abbey Roelofs Date: 7/2022 Venue: FOR PUBLICATION ON THE US-RSE BLOG The US-RSE Association has grown to become a major resource for people in a variety of RSE-like roles and provides support through monthly community calls and working groups. Because of the distributed nature of the research software engineering community across the United States, exaggerated by the COVID-19 pandemic and the shift to remote working styles, most US-RSE activities now take place online. However, co-location and face-to-face meetings have certain advantages for local community building and in fostering social interactions. During the [2022 US-RSE Community Building Workshop](https://us-rse.org/first-community-workshop/), a working group was established to identify pathways for creating a network of RSE groups based on geographic areas rather than institutions or companies. The working group aims at building a localized social community structure for RSEs, both in person and online, with the aim of connecting research software engineers within local and regional communities. The Local and Regional Working Group are conducting an ongoing experiment in establishing groups in their own areas while also sharing resources, successes and failures. If you are interested in creating a local or regional RSE group, or you have already done so and would like to share your experiences with colleagues nation-wide, please reach out through the US-RSE Slack channel and share your experience! The members of this working group and their RSE group location are listed below | Name | Organization | Area | | ----------------- | -------------------------------- | --------------- | | Jordan Perr-Sauer | National Renewable Energy Lab | Front Range, CO | | Mahmood Shad | Harvard University | New England | | Rafael Mudafort | National Renewable Energy Lab | New Orleans, LA | | Sandra Gesing | University of Illinois - Chicago | Chicago, IL | ## Considerations ### Why start a local group? Why would anyone participate? In a recent informal poll of the members of the `#rg-frontrange` channel in the US-RSE Slack, the following reasons were identified: - Get to know other RSE's in my area. - Build my network and make connections. - Venue for recruiting. - Learn how to build RSE community at my own institution. - Opportunities for collaboration, co-working, or a hackerspace. - Learning from others These reasons show one theme in common: RSEs desire to be more connected with a professional community. The need comes from the reality that RSEs are often isolated in their organization. A local group can provide an outlet for sharing technical knowledge and resources while bringing people together from those cities and from surrounding cities and affiliations. For example, it can be helpful to learn about how other people use a particular tool like an IDE or which processes are particularly useful at another institution. Even when an organization does have a healthy network of RSEs, socializing with co-workers can have particular limitations. A local RSE group can provide an opportunity to socialize with other people that have a shared experience without the "co-worker" label. A local RSE group is a great way to stay connected to who is doing what in the area. It's an opportunity to create a local community of RSEs who support each other throughout their careers. ## Activities The US-RSE Association is well-established and has many resources to help in advertising and coordinating local RSE groups. Since the US-RSE community building workshop, the local and regional working group has met regularly and identified the following activities: ### Formation of the Local and Regional Working Group The working group has been formed and is using the private Slack channel `#wg-local-regional` for organization. The working group meets monthly. If you are interested in joining the working group, reach out to Rafael, Sandra, or Jordan via Slack. ### Support for Local Groups by the Members of the Working Group Each member of the working group will experiment by forming a local group in their own community. Since this is a new step for US-RSE, we intend to experiment ourselves and share our experience in a future post. Additionally, we will engage with anyone starting their own local group to offer resources and guidance. ### Regional Group Prefixes on Slack The general US-RSE Slack can be used to host a local-group Slack channel. By convention, these all are prefixed with `#rg-` and then have the name of the location; for example, `#rg-nola` for the New Orleans regional group. Each local group should have an associated Slack channel in the [US-RSE Slack](usrse.slack.com) team with a `#rg-` prefix. ### Regional Groups Added to US-RSE Map TODO: - Add picture of map - Local groups are displayed in the membership map in XX color. - Wide reach to the full community - Digital storage space through Google Drive through US RSE ### Regional Group Listing The following local and regional groups have been identified through the US-RSE slack channel: | Location | Slack Channel | Membership | |---|---|---| | Arizona | `#arizona-rse` | 17 | | California | `#california-rse` | 38 | | Chicago Area, Illinois | `#rg-chicago-rse` | 8 | | Denver Area, Colorado (Front Range) | `#rg-frontrange` | 29 | | New England | `#rg-new-england` | 13 | | New Mexico | `#new-mexico-rse` | 9 | | New Orleans, LA (NOLA) | `#rg-nola` | 3 | | Pennsylvania | `#pennsylvania-rse` | 7 |

    Import from clipboard

    Paste your markdown or webpage here...

    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 lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    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 with Wallet
    Wallet ( )
    Connect another wallet

    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

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    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 and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    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.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        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
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

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

        Syncing

        Push failed

        Push successfully