sdruskat
    • 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
    # Intl RSE Leaders Workshop (UN-RSE)- Group 2 *Working title: The United Nations Council of RSE Asossocations* :::info Hello! This is your group's very own collaborative document, which you can use for taking notes, drafting a blog post about the work of your group, etc. **Please complete the fields in the red box.** You can also use another medium, such as a document in OnlyOffice of a Google Doc. In this case, please **copy the link to your group/pitch section** in the main collaborative document, and **copy the fields from this one** to make sure everything is there. Thanks! ::: :::success ### Blog post We ask every group to write a short blog post about the group's idea, or the issue they are working on, and what the outcome of their work is. The final draft of this blog post should be ready by **Day 3 (30 Sep)**. The organizers will prepare it for publication in the blog on https://researchsoftware.org. This may involve some light editing (fixing typos, formatting, etc.), but they'll get back to the group before making changes beyond that. You can find the **template at the bottom of this document**. ::: :::danger - **Group name:** (2) Regular Meeting of International RSE Leaders - (1) Annual International RSE Conference - **Participants:** - Ian Cosden (US RSE) - Paul Richmond (SOC RSE) - Mateusz Kuzak, this sounds like *the RSE leaders community of practice* - David Yuan: Perhaps, one of the regular meeting can be at the same time and place as (1) Annual International RSE Conference? - Alejandra Gonzalez- (I'd like to help with this, but initially will work on international survey and playbook) - Anne Fouilloux (Nordic RSE) - Stephan Druskat (de-RSE) (*will try to share between this and (3), and elicit requirements from this group for (3)*) - Jeremy Cohen (keen to be part of this group but will be in group 5 - will join later if possible) - Florencia D'Andrea (I am chair of a conference in LatAm, I will be working in group 12) - Stephan Janosch (de-RSE) - **Outcome(s):** Not to solve all international problems but to provide a committee to discuss issues and propose solutions. Outcome shoudl be a description of remit and an event in the calendar. - **Presenter(s) Day 3:** ::: # Goals for 15th/16th September 2020 (todo, done) - Agree on high level idea (done) - Set goals for working session (i.e. by the meeting on the 30th we’ll have X,Y,Z) - Decide on succinct purpose of the International RSE Association Leadership group - Remit/mission statement - Name for group: United Nations Council of Research Software Engineering (UN-RSE) Associations - Membership criteria - Who should be included as of today - List organizations (contact: todo, approached, agreed) - Soc RSE - Contact: Paul Richmond (agreed) - US-RSE - Contact: Ian Cosden (agreed) - DE-RSE - Contact: Frank Löffler, Stephan Druskat, Stephan Janosch (TODO Stephan D: Get back to board and ask them for informal buy-in) - NL-RSE - Contact: Ben van Werkhoven (todo) - NORDIC-RSE - Contact: Anne Fouilloux (agreed) - RSE Association of Autralia and New Zealand - Contact: Nooriyah Poonawala-Lohani, Manodeep Sinha (todo) - Be RSE - Contact: contact@be-rse.org or Johan Philips (todo) - African RSSE - Contact: Peter van Heusden (todo), - persons attending 1st intl RSE Leadership meeting from Africa? - Make contact with someone from each organization - Ask for support - Aim for commitment to send 1-2 people to meeting - Are there membership tiers? Voting/non-voting etc? - Future members - What defines a “national organization” - Who makes contact, approves new members - condition list for maturity - taking part in international survey/run a national survey - have an open mailing list - have a website - - International Events - Partial list of what is and isn’t under the purview of this group - Structure of group - Governance and roles - Chair, committee, voting, etc - Financial considerations - Immediate next steps - Initialize a first meeting - Date, attendees - IC: Proposal for first agenda - formalize (or continue working) on content we set up here - Home for documentation of group. E.g. website with details and membership - Advertising/Announcement? - Steps for the not immediate future - Are we taking governance of the GitHub repo for researchsoftware.org? # Goals for 30th September 2020 - Draft proposal for associations to take back to their commitees - Document which can be shared - Identified committee members from each organisation (and the organisations) - Have a meeting date proposed in the diary - Informal buy in and feedback from attendess on the 30th - To send out 2 weeks after - Ask attendees to provide links to committee members of organisations # Proposal Document # Proposal Document ## Background **Context:** Establish formal meetings and/or communication lines between the leadership of national RSE associations. ### The problem There are a number of national RSE organizations (societies, associations and informal communities) but no formal mechanism to ensure that we collaborate internationally. There is no clear view on who should be running international branded events such as an "International RSE Conference" and no active planning to ensure that we do not complete for conferecne dates. In addition to organisational aspects, each of the associations are often stuck with the same governance and policy challenges as well as potentially duplicating initiatives which could be run across associations. ### The proposal We (the founding national associations) would all benefit from a forum to communicate and formally meet to ensure cohesion between associations and to provide a platform for open discussion around international issues and affairs. This would provide a platform for collective decision making, collaboration among national associations as well as peer support. What is specifically proposed is the "United Nations Council of RSE Associations" (or UN-RSE). This document outlines the remit and proposed model for UN-RSE with the expecation that each national association discusses the proposal with their existing committees with the intention of agreeing to participate. This proposal has been designed as part of the 2nd International RSE Leaders Workshop and has informal support from; **Associations:** * The Society of RSE (UK) - Approved by Paul Richmond * US RSE - Approved by **add name by the 30th** * Nordic RSE - Approved by **add name by the 30th** * de RSE - Approved by **add name by the 30th** The proposal has also recived input from * David Yuan (European Molecular Biology Laboratory) ## Suggestions for Remit * Founding members * future membership is upto the founding members * suggestion at this point * International conference E.g. * Who should run it * Should there be a float * “International” branded events * Financial rules for international events. E.g. * a policy to prevent profiteering and competition * Rule on floats to ensure other organisations could run events. * A general forum to discuss/raise international RSE issues * Do we think this fits * Balance between formal group and informal discussion * E.g. This month "we will discuss how to run elections" * Clarify the Role of Soc RSE with respect to International things * Perhaps a placeholder for new international associations * Expectation of supporting new associations to start * Sponsorship of events for new associations through the (soon to be published) events sponsorship policy. * E.g. Formal forum for discussion on this if an issue arises * Best practice for international members within associations * Support for latin america? * We interact with ReSA [how?] * Formally support SORSE * Membership * Start with founding members from established groups * Extend out established groups once it's reached a community * E.g. participating in the RSE survey * Incubator - would be great to help them but would be too much to ask * Specifically address how to grow * Need to combine with playbook ## What we want from the Associations (AF/IC) ### How to participate? Membership in the the UN-RSE is open to any National RSE Association. Each member association is expected to send two (2) representatives to the council. Representatives will be expected to attend the UN-RSE meetings. There is no membership fee. Membership will be open to any national or larger (e.g. continental) association of research software engineers/engineering. Meetings will be held 2-4 times per year. Roles: Rotating chair - sets agenda and hosts meeting Secretary - responsible for taking notes and ensuring publication Roles will be held for 12 months and voted on in the first meeting of the year. * identify a commitee member to take forwards * agreement to discuss within your national committee * agreement to nominate 2 members * 2 people nominated from each association? * Can these change if people are not available * Community feed in via your own membership association * Other organisations (SSI etc) * When do new communities get to join? * Are there a set of conditions for the community? * agreement to attend and participate * 2-4 meetings per year * slack channel * agreement to take some ownership of this * Not just planning an governance, this is place for discussion and to facilitate collaboration. ## Forward look **Vision, mission and charter, which may eventually lead to the formationation of an international RSE organisation in some shape or form** # Tasks & assignees prior to 30th # Notes How does this group fit with SORSE, ReSA? --- # Blog post draft - **Title:** - **Authors:** - **Image link (400+ px width) + image credits (as needed, CC-BY or your own):** Text (600-800 words)

    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