Sushicom
    • 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
      • Invitee
    • 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
    • Engagement control
    • 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 Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control 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
Invitee
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
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
**Sushi - Post Mortem on AG Whistleblow** **The Situation** On November 24th, 2021, now-former team member, AG, was terminated following a pattern of unprofessional behavior. Post-termination, she published a series of denigrating tweets in a targeted effort to damage Sushi’s reputation. We have information that leads us to suspect that previous leaks were carried out by AG as well. These problems are symptomatic of a larger issue, which is that accountability and transparency are non-trivial human resource problems in a DAO. The Core takes issues raised by AG very seriously, and is working on building a framework for those such issues can be raised and resolved without disrupting the entire Org. **Our Response** Prior to the incident at hand, we had received negative feedback on the former community member’s working relations and learned of proactive efforts to subvert Sushi. Offenses include, but are not limited to: * Negative attitude, as cited in formal complaints from several Chinese community members * Resignation of a colleague due to toxic work environment that was stoked under her oversight * Resorting to repeated personal attacks with baseless accusations on Sushi personnels following disagreements * Alleged creation of external accounts populated solely by dramatics, and denial of creating these accounts when asked, namely @makibacknow * Attempts of amicable transition of organizational-level assets and processes have failed. Certain community assets remain under her control. We had several conversations with the former community member on these offenses, eventually making clear that her behavior was in violation of our Code of Conduct and her role would be terminated should it continue. The behavior continued and the former team member was thus let go with more than 80% core team consensus. Following termination, Sushi requested archives of G Suite account information available, as is customary. This information revealed that the former community member in question may be behind a ProtonMail email address (sushijokr@protonmail.com), and attempts of reaching out to news organizations of baseless accusations in a highly public and toxic format. In addition, we are also investigating any ties to the polemic @makibacknow account. It has become clear that the actions taken by a disgruntled former community member were done so with the sole aim of undermining Sushi following her departure. Nonetheless, we take negative claims seriously and called a public forum on November 25th to address concerns to ensure clarity for community members. It can be found on [YouTube](https://www.youtube.com/watch?v=wy8X0T3AGwc). Now that the claims have been addressed and we’ve taken measures to confirm the former team member’s involvement in attacks on Sushi, we look forward to moving on and continuing to build. **Key Takeaways** Conversely, every crisis is an opportunity to fine tune how we interact with our community, and we see room for improvement. While we take any allegation against Sushi and its Core Team seriously, our response time and official response could have made this clearer. We have a responsibility to our community members to keep them informed, and we could have been more responsive quicker to ensure they knew we had the situation under control. **COURSE OF ACTION** The problems that arose created a sense of urgency to generate a more healthful and productive work environment. It concentrated energies, and provided an example of the kind of behavior that needs to be prevented, while also creating a sense of community among the members who produce without fail. An Open-source Contributor process and a human resource system are currently being sought, and a formal code of conduct is underway as well. In addition, a Sushi Gigs platform has been in development for some time, and a framework for onboarding new members is being formalized. These individual aspects are pieces of a new structure for the Sushi Org, which we have referred to conversationally as Sushi 2.0. It has become clear that the existing flat-org structure is not working. The existing structure makes it too challenging for individuals to raise genuine concerns, and on the flipside, it makes the Sushi work environment vulnerable to Sybil attacks. We agree and admit that there were mistakes made. Sushi is the largest ground-up DAO in existence, therefore we are the first to experiment many things. There will inevitably be bumps on the road, but collectively, we will strive to build smooth processes and structures that best serves our community. Going forward, we are committed to involve the community in larger decisions, and create more transparency with the community. We will soon release a second statement that provides clarity and context around some of the actionable next steps, and will address the issues raised by the community at large. Further response to the allegations can be found here: https://www.youtube.com/watch?v=wy8X0T3AGwc We will continue to respond to the community in the most appropriate formats to provide clarity and context around the current events.

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