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 - Group 3 :::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 Objective: Provide a single entry point to the international RSE community. This may potentially be based on previous work by which the website https://researchsoftware.org/ was established. Main aims: Make all relevant information on RSE findable and accessible both to insiders and outsiders, and develop a digital marketplace where 1) people and institutions can find the RSE support that they require and 2) invididual RSEs and RSE groups can acquire projects. ::: :::danger - **Group name: Single Entry Point and Marketplace for the RSE Community** - **Participants:** - Julia Damerow - Stephan Druskat - Martin Thomas Horsch - Stephan Janosch - **Outcome(s):** - **Presenter(s) Day 3:** ::: # Day 2 (16th September) discussion ## **RSE profile map** - map (landscape) and metadata standard for profiles of individual RSEs and RSE groups - standardized description of topics (based on pre-existing taxonomies?) and of competencies (previous work exists) - catalogue of topics in computing, http://taxonomies.labs.crossref.org/?p=109 - description of competencies, work in progress from VIMMP, https://home.bawue.de/~horsch/pdt/material/otras.pdf - similar: Open Knowledge Maps - https://openknowledgemaps.org - Idea: Conduct a very brief survey among the workshop participants, evaluate until 30th September and present a possible landscape/self-description standard on this basis ![](https://i.imgur.com/ZPnuHlL.png) - Eingruppierungshilfen (management responsibily) (Stephan Janosch) list tasks and so on, maybe take inspiration from there - ris: research information systems - Q: Could there be an optional "login via ORCID," etc.? - include geographic & affiliation information, e.g., as already available for the DE-RSE Society members ## **Technical implementation** - possible git-based solution: jekyll + netlify, # Work plan, tasks & assignees - **Website Updates (ask community for required updates by Sept. 23, 2020 via thread in workshop channel)** - can we be added to [the GitHub repo](https://github.com/RSE-leaders/researchsoftware.org ) please :) - Things to update : - Association list update - Things to add: - Domain specific RSE communities - Event section that lists past events (RSE Leadership workshops, conferences) and future events - add email contact to website? - syndication of other RSE blogs? - resource section - **Organizational aspects** - Can a group be formed that reliably takes care of the single entry point/marketplace? What is the institutional framework? - Relation to group 2, 11, 12 output. - To be discussed on 30th September. - have other workshop members who will form a new RSE community email group 3 the info. - **Technology**: - Make a list and evaluate possible implementations and hosting options - **Marketplace** - Let users create profiles to be searchable. - Add map of people/groups? - Task as extension of the RSE profile overarching survey: Evaluate set of representative use cases based on information given in job advertisements - Take this as a basis for data ingest on use cases - Description of RSE profiles + description of use cases => marketplace as part of the single entry point - **Survey for RSE profile map** - Link Collection: - http://taxonomies.labs.crossref.org/?p=109 - https://home.bawue.de/~horsch/pdt/material/otras.pdf - https://openresearchsoftware.metajnl.com/articles/10.5334/jors.242/ - https://pad.gwdg.de/dKcY6QmRS4yCnKCFVOglng?view - https://software-carpentry.org/blog/2015/06/what-is-a-research-software-engineer.html - doi.org/10.5281/zenodo.495360 - Until 30th September, let us do an "overarching survey" e.g. as a "survey of surveys (metastudy)" - Plan: Evaluate the corpus of advertised job descriptions, since these descriptions will match what is looked for in practice - To be included: Work done by the Software Sustainability Institute - However, we need to look more broadly than "explicit RSE advertisements" - **Technical implementation and host** - To be discussed # Notes - Questions for the community: - Who is responsible for the website (outcome of question 2?) - Where could the website be hosted if we need something else than Jekyll? # RSE Map ## RSE tasks/topics ### international RSE survey https://github.com/softwaresaved/international-survey/tree/master/analysis/2018 - Areas of activity - SW dev - Research - Review - Grant writing - Methods section - Management - Project - Grants - Team - Teaching - - Other - dissemination/communication - operations/dev Ops/CI/CD/sys admin ### From ACM (https://dl.acm.org/ccs) - Software Architecture - Embedded software - Distributed systems organizing principles - Cloud computing - Client-server architectures - Grid computing - Real-time systems software - Extra-functional properties - Interoperability - Software performance - Software reliability - Software fault tolerance - Software safety - Software usability - Software post-development issues - Documentation - System administration - Theory of computation - Formal languages and automata theory - Computational complexity and cryptography - Logic - Design and analysis of algorithms - Randomness, geometry and discrete structures - Theory and algorithms for application domains (e.g. ML theory, DB theory,...) - Semantics and reasoning - Data management systems - Database design and models - Data structures - Query languages - Database administration - Information storage systems - Data Mining - Web applications/services - Information retrieval ### From Sammlung von RSE Arbeitsvorgängen (https://pad.gwdg.de/dKcY6QmRS4yCnKCFVOglng?view) - Lobbying - Mangagement/Organization - People - Software (user feedback/communication) - Funding/grants - Education - Teaching - Consulting - Software Development - Requirements analysis - Development - Frontend - Backend - Database - Maintainance - Bug fixing - Version upgrades ### From job postings - 16 postings total Links to postings: https://www.indeed.com/viewjob?jk=cf195f54bfb68d1a&tk=1ejagpbsh34t8000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=0405639589f5a213&tk=1ejagpbsh34t8000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=c53c9870e00a5163&tk=1ejagpbsh34t8000&from=serp&vjs=3 https://www.media.mit.edu/about/job-opportunities/research-software-engineer-laboratory-for-social-machines-1/ https://www.indeed.com/viewjob?jk=d924227387514873&tk=1ejagpbsh34t8000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=8e61800e5365577a&tk=1ejagpbsh34t8000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=d863e26eb03ffb21&tk=1ejafndrp0ggi000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=91974d82e1a52077&tk=1ejafndrp0ggi000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=3943247beb19f6ba&tk=1ejafndrp0ggi000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=f58b163a5bb1ebbe&tk=1ejai6s4u34op001&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=2bdebd7d89a467a4&tk=1ejai6s4u34op001&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=242e6569f06aa28a&tk=1ejai6s4u34op001&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=f163a82468bfd488&tk=1ejaj14do34mi000&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=50294c9845c56233&tk=1ejaj8b8r34mi001&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=e65f1c5355907c41&tk=1ejajohursa2k800&from=serp&vjs=3 https://www.indeed.com/viewjob?jk=d227ea4a2b10d896&tk=1ejajohursa2k800&from=serp&vjs=3 --- - Programming - Machine Learning - Deep learning - Computer vision - Signal detection/processing - Distributed computing - Cloud computing - Technical leadership - Cryptography - Blockchain - Building software systems - Architecture design - Technology evaluation - Web application development - Distributed systems - Algorithm - development - evaluation - Framework development - Software testing - Support - User support - Maintenance of support systems - Training - Mentoring - Code reviews - Funding/Grants - Communication - Reporting - Grant writing - Cross-platform development - Documentation - Developer - End-user - Reports (stats, progress reports, etc) - Requirement analysis/formulation - Presentation of results - Scientific writing - System administration - Stakeholder communication - Incident response - (Human) networking/communcation - Oral - Written - Code quality and performance - User interface design - API development - Continuous Integration/Deployment - High performance computing - Data - Data visualization - Data management - Data analysis - Bioinformatics - Genomics databases - Scientific computing - Containerization - Database - Management - Relational - NoSQL - Compiler construction/design - Software verication - Statistical methods - Project management - Domain-specific knowledge - Software security - Operating systems - Computer networking - Computer systems and architecture - Industrial control sytems - GPU programming - Simulation - Open source development - GIS - Geospacial databases - Performance analysis - Process development - Best practices - Software quality - Use analysis software - Frontend development - JS frameworks - UX (HTML, CSS, and related technology) - JS testing - UX design - Graphic design + other tasks as assigned # Use-case matrix (based on the above) - http://home.bawue.de/~horsch/pdt/material/rse-use-case-description.odt - http://home.bawue.de/~horsch/pdt/material/rse-use-case-description.pdf # Combined competencies - Software Development (2018 survey: developing software) - Requirements gathering/analysis/formulation - Technology evaluation - Programming/implementation - Software Architecture - Cross-platform development - Maintenance - Bug fixing - Version upgrades - Testing - Distributed systems - Cloud computing - Grid computing - Client-server architectures/web applications - Frontend - Frameworks - UX - Testing - Backend - Web services (API development) - Desktop applications - Embedded systems/software - Real-time systems software - User interface - UX design - Graphic design - Areas of CS - Algorithm - development - evaluation - Framework development - Formal languages and automata theory - Logic - Randomness, geometry and discrete structures - Semantics and reasoning - Agent-based modelling - Artificial intelligence - Machine Learning (Deep learning, neural nets, etc.) - Computer vision - Information retrieval - Data mining - High performance computing - Signal detection/processing - Cryptography - Blockchain - Compiler construction/design - GPU programming - Scientific computing - Computer networking - Operating systems - Domain-specific topics - GIS - Bioinformatics - Industrial control systems - Simulation - Around Software - Project management - Software aspects - Interoperability - Quality - Performance - Reliability - Fault tolerance - Safety - Usability - Operating - System administration - Incident response - Continuous Integration/Deployment - DevOps - Containerization - Process development (best practices, software quality, etc.) - Support - End-user support - Maintenance of support systems - Documentation - Developer documentation - End-user documentation - Reports (stats, progress reports, etc.) - Data management systems/information storage systems - Database design and models - Relational - NoSQL - Document Repositories - Data structures - Query languages - Database administration - Data - Data visualization - Data management - Data analysis - People-related - People management (2018 survey: Management?)(2018 survey: Management) - Technical leadership (2018 survey: Management) - Software advertising - Software feedback gathering - Training (2018 survey: Teaching) - Teaching - Consulting - Mentoring - Funding/Grants - Communication - Reporting - Grant writing - Networking/communication - Stakeholders - Collaborators - Users - General public - Research output (2018 survey: Research) - Presentation of results (e.g. meetings, workshops, conferences, …) - Scientific writing - Community (2018 survey: other activities) - Lobbying - Open source development - Other (2018 survey: other activities) - Domain-specific knowledge - Domains according to DFG.de - Geistes- und Sozialwissenschaften - Lebenswissenschaften - Naturwissenschaften - Ingenieurwissenschaften - [Domains according to nature](https://www.nature.com/srep/browse-subjects) - Statistical methods - Use of analysis software - Other tasks as assigned --- # Blog post draft - **Title: Working Group: Single Entry Point and Marketplace for the RSE Community & RSE Profile Map** - **Subtitle** (if applicable): An RSE Leadership Workshop 2020 working group report - **Authors:** Julia Damerow, Martin Thomas Horsch, Stephan Janosch - **Image link (400+ px width) + image credits (as needed, CC-BY or your own):** At the RSE Leadership Workshop in September 2020, this working group came together to discuss two main objectives. Part of the time, we talked about plans to provide a single entry point to the international RSE community. This discussion was based on previous work by which the website [https://researchsoftware.org/](https://researchsoftware.org/) was established. The main goals were to make all relevant information on RSE communities around the world findable and accessible both to insiders and outsiders, and to explore the idea of a digital marketplace. Such a marketplace was envisioned to be a place where people and institutions could find the RSE support that they require and that would let individual RSEs and RSE groups acquire new projects. The other topic, we discussed was the idea of creating an RSE “profile map” that could serve as a tool for RSEs and non-RSEs alike to describe the different tasks and skill sets of an RSE. Since such a profile map would need a home, we considered this being part of the single entry point discussion. ## Single Entry Point and Marketplace for the RSE Community Previous work has already created a website at [https://researchsoftware.org/](https://researchsoftware.org/) that serves as an umbrella for the different RSE communities around the world. However, the general opinion seems to be that this website could be more than what it currently is. It could (and possibly should) become the single entry point for the RSE community. The website could serve as a gateway for anyone interested in RSE work or the RSE job profile to find geographically or intellectually relevant RSE communities. It could also map out how the different communities relate to each other, and to communicate communities-spanning activities (such as the RSE Leadership workshop or the RSE conference). We explored several possible changes and additions to the existing website and categorized them as either realizable immediately, realizable in the medium- to long-term, or as needing decisions/discussion from other groups. Below is the list of items we discussed and crowd-sourced with the rest of the workshop participants. ### Realizable immediately - The list of associations should be checked and updated as necessary. - A list of domain-specific RSE communities should be added. - An event section that lists past events (RSE Leadership workshops, conferences) and future events should be added. - A resource section could be added that would link to other relevant RSE sources (e.g. journals where RSEs can submit their work). - Recommendations of a [standardized description for RSE use cases](http://home.bawue.de/~horsch/pdt/material/rse-use-case-description.pdf) (draft) could be provided. ### Realizable in the medium- to long-term - The website could aggregate other RSE blogs, or at least pull blog posts that are of interest to the wider RSE community. - The website could host a crowd-sourced map of RSEs and RSE groups around the world. - Similar to the aggregated blog, the website could aggregate the Twitter feeds and event calendars from the different RSE communities. - The resource section could also contain information on ongoing (large) projects, open source initiatives that seek contributions, relevant funding agencies, etc. ### Needing discussion/decisions from other groups - It would be useful if the website had some concrete ways to get in touch with someone, e.g. through an email address. This however raises the question of who will be responsible for the website and its maintenance (in which “who” might refer to an organization/association and not necessarily to a person). - Another question is the implementation of the website. Jekyll, while easy to use, does put certain limitations on the functionality. If, for example, the community would like to add a forum to the site, another solution might be better suited. For this though, questions about who will ultimately be responsible for the site and its maintenance need to be decided. - Some social aspects might be nice to have. If users could create searchable profiles and add projects they would like to collaborate on, the community could use such a “marketplace” to connect across countries and disciplines. ## RSE Profile Map The profession of an RSE, as rapidly growing as it is, is still not as widely known as we might like it to be. There are probably many people out there that do RSE work but do not realize that there is a whole community for them. Similarly, the message of the importance of RSEs in science has still not reached every corner of the world. One possible reason (even if it is a minor one) is that RSEs do many different tasks, have many different responsibilities, and have very different skill sets. This makes it on the one hand hard to find the community in the first place (just recently someone told me: “Thank you! I didn’t know what to call the job I want to do until you said Research Software Engineer!”), and on the other hand, it makes it difficult for people who are not RSEs but who would like to work with one to define and communicate the expertise they are looking for. To help with these issues, we discussed creating a map (which might be a list at first) that would try to give a broad overview of all the different skills and competencies an RSE might have. Such a map would allow people doing RSE work to identify with the community, but also give “outsiders” an idea of all the different skills an RSE might have or require. From our experiences, we agreed that it does seem like most RSEs have a wide range of responsibilities from programming over operations to project and people management often paired with research tasks, while many (or even most?) software engineers in the industry only have to focus on one or maybe two of these areas. As a first step towards our end goal of an RSE Profile map, we compiled a list of tasks and competencies that we gathered from other categorizations and by going through job postings. The resulting list is meant as a starting point for a discussion. It needs the input from the community to make it as comprehensive and useful as possible. We are obviously not all-knowing, so this list is bound to be incomplete and there are most likely categorizations that should be discussed. Over the next couple of weeks, we would like the community to engage in a discussion that will lead to a more complete list that can then be published on the RSE website and hopefully be turned into some kind of map. We left out many things and specific technologies in order to keep the list manageable but we are open to making this list more specific if the community finds this useful. If you have any suggestions on how to change this list, please join the Slack channel ``#rse-profile-map`` for any in-depth discussion or leave a comment in [this Google Doc](https://docs.google.com/document/d/18GPSEn-CnsoAKo9TbI7nD6A00drbqH9cCNCUqR41vVQ/edit?usp=sharing). ### RSE Tasks and Competencies - Software Development (in the 2018 survey called “developing software”) - Requirements gathering/analysis/formulation - Technology evaluation - Programming/implementation - Software Architecture - Cross-platform development - Maintenance - Bug fixing - Version upgrades - Testing - Distributed systems - Cloud computing - Grid computing - Client-server architectures/web applications - Frontend - Frameworks - UX - Testing - Backend - Web services (API development) - Desktop applications - Embedded systems/software - Real-time systems software - User interface - UX design - Graphic design - Areas of CS - Algorithm - development - evaluation - Framework development - Formal languages and automata theory - Logic - Randomness, geometry and discrete structures - Semantics and reasoning - Agent-based modelling - Artificial intelligence - Machine Learning (Deep learning, neural nets, etc.) - Computer vision - Information retrieval - Data mining - High performance computing - Signal detection/processing - Cryptography - Blockchain - Compiler construction/design - GPU programming - Scientific computing - Computer networking - Operating systems - Domain-specific topics - GIS - Bioinformatics - Industrial control systems - Simulation - Around Software - Project management - Software aspects - Interoperability - Quality - Performance - Reliability - Fault tolerance - Safety - Usability - Operating - System administration - Incident response - Continuous Integration/Deployment - DevOps - Containerization - Process development (best practices, software quality, etc.) - Support - End-user support - Maintenance of support systems - Documentation - Developer documentation - End-user documentation - Reports (stats, progress reports, etc.) - Data management systems/information storage systems - Database design and models - Relational - NoSQL - Document Repositories - Data structures - Query languages - Database administration - Data - Data visualization - Data management - Data analysis - People-related - People management (2018 survey: Management?)(2018 survey: Management) - Technical leadership (2018 survey: Management) - Software advertising - Software feedback gathering - Training (2018 survey: Teaching) - Teaching - Consulting - Mentoring - Funding/Grants - Communication - Reporting - Grant writing - Networking/communication - Stakeholders - Collaborators - Users - General public - Research output (2018 survey: Research) - Presentation of results (e.g. meetings, workshops, conferences, …) - Scientific writing - Community (2018 survey: other activities) - Lobbying - Open source development - Other (2018 survey: other activities) - Domain-specific knowledge - Domains according to DFG.de - Geistes- und Sozialwissenschaften - Lebenswissenschaften - Naturwissenschaften - Ingenieurwissenschaften - [Domains according to nature](https://www.nature.com/srep/browse-subjects) - Statistical methods - Use of analysis software - Other tasks as assigned

    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