Stefano Bernardi
    • 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
# Some feedback re Flock / AA / A1 Hey guys, saw both of your posts and just wanted to express some views about the whole situation before the call on Tuesday which I would like to only be focused on solutions - I think they are best provided here, but I'm happy to post them online should you think that's the best avenue. I very much love the spirit of optimism that @luis expressed on Flock in https://forum.aragon.org/t/an-optimists-take-on-flock/1299, but what I think is not particularly realistic is the optimist feeling that it can sort itself out (in the bazaar framing of @jorge), or can do so nudged by a little bit of oversight by the AA. I think what is clear by now is that the wider network doesn't particularly care about the day-to-day dynamics of Flock. Or, let me rephrase: it seems clear that there is no voter participation on Flock proposals, and that literally ALL of the Flock discussions come from members of the Flock teams, or the AA, plus 2, maximum 3 people that are not involved in the day to day (and for those I am thankful). Now, that's not a bad thing by itself, it's just stating a fact. I really wouldn't know who could have the time to stay up to date on this. I think that it becomes a useful fact in addressing what the problem is for Flock, and that in my opinion is a lack of leadership. To me, it seems clear that the Aragon Network is operating without a CEO or leadership figure. I find that very worrying, as I've never seen anything work without that. I assume that at Flock's inception, it was imagined that the role could be itself decentralized to the community, but that has not materialized - and thus we need to course correct. If instead the thought was that the AA would have been that leadership role, then we might have had some miscommunication as that is not how I saw it. While decentralizing the development is an awesome trailblazing experiment, it can't happen without some strong, committed leadership to make it happen - and for what it's worth I don't think it's something that you can hire away. The AA is still a 2 people operation (as the board felt it premature to scale faster), and has a host of tasks to manage - most operational - that leave very little time or mental cycles to think in a strategic way and execute on these topics. The AA has legal, accounting, events, Nest, coordination of Flock AGPs, AGP process in general with execution, managing a host of payments and DAOs, handling all of the security auditing processes, and more. Therefore I'd like to clarify what has become apparent to me at this point. I do not think: - the AA has currently the capacity to take on that leadership role - the AA is the best entity to take it on anyways, as it would remove centralization from one part and create it on another, while also creating a high cost structure at the AA level, which would need to duplicate a lot of efforts that are already implemented inside the core development teams. Additionally, in the past year it was never mentioned specifically that the AA should have taken on such a role. Our current stance, communicated a few times to the board, has been to provide the lump sums (in quarterly or bi-annual payments) without retracting funding. The safeguarding mechanism is in the network being the ultimate judge if a Flock team worked or not by not renewing their membership. The underlying root cause, is the fact that A1 continues on its strong development path, as it should, but holds similar expectations from Flock teams, without some sort of active process to get them there. All while at some level kind of wanting to dictate a bit who gets to stay and who doesn't. I think that is actually a good way to make it work - but it conflicts with how the program is structured and communicated. Now, we clearly have some responsibilities and are to be blamed at the AA, because we really have not been able to pick up the pace on the reporting - and our efforts in aiding communication between Flock teams, including the working groups, have definitely not yielded the results that we would have hoped. But one of the few mistakes you might have done was to think that you could somehow form the AA, and outsource two full-time jobs (Alexa and Maria) and then pile on a lot more stuff (Flock, AGP process, treasury, etc.) and clearing that from your minds without being in charge of it. I think that a decentralized governance framework works very well, but mostly for oversight - not for maximum operational efficiency. I think we need to clearly identify who the "CEO of the network" is. It could be a person, a team, or even an organization - but it needs to clearly be communicated, have the right skin in the game, and skills for it. It definitely can fit in a decentralized governance scenario and can be voted in and removed by the ANT tokenholders. My personal opinion is that it is very hard to make it work if that's not (plural) you (founders) - but if I were to see some different potential paths, I could definitely be convinced otherwise. I hope this feedback is useful. This year has been extremely formative for everyone including myself and the whole Aragon Community, plus in general the whole decentralized governance space. I like to see it as a needed investment in the direction we want to take, but also see it very worthwhile to reflect on the things that have worked and things that didn't in order to make it a better process for the coming years. Looking forward to chatting on Tuesday to see how we can immediately address the current situation, and then maybe having a deeper conversation about the structure of Flock and the role of the AA! 🦅 Ste

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