Autark: Rolling Status Updates

This is a rolling thread to discuss and present what Autark and its partner for AGP-73, Open Work Labs, are developing.

We plan to release new features and enhancements every month, with the next target release at the end of December. Note: Cadence for mainnet releases may change in the future, when we start focusing on developing newer contracts that require audits.

Work in progress

  • Integrate deep linking into Open Enterprise apps
  • Alternative Open Enterprise template for a two-token DAO, which integrates with the experimental token manager.
    • We finished the contract based on early ideas, but our template doesn’t have the Agent app in it, and we are getting multiple user requests to add it, so we are going to re-evaluate to current architecture to make it more flexible.
      • We are also rethinking the front-end to determine the best way to either create a one token or two token DAO, so we can only maintain one template.
  • Projects: Allow work to be submitted to bounties without requiring an application. Improve how we handle bounty statuses. Optimize filtering.
  • Allocations: Ability to edit budgets. Ability to view a detail page for an allocation. Summary metrics on Allocations landing page. See Figma designs
  • Implement “quick win” accessibility enhancements to Open Enterprise.
  • Open Enterprise Maintenance: polishing up the frontend and fixing small bugs. Implement end-to-end testing and improve our general release management processes.
  • The security audit was completed for an experimental Token Manager that supports quasi-transferable tokens. We made changes and it was re-reviewed and given the green light. We plan to do some final testing and then publish to hatch.aragonpm.eth. We will use this token for our Autark community DAO.
  • Address Book identity resolution (showing names from the Address Book app instead of ethereum addresses throughout Aragon) is pending review from A1

Next

Besides the WIP items described above, some of our top priority items for the next 4 weeks:

Enabling Organization Insights

  • True up our Home app to be in line with the aragonDS, and release it to mainnet as the “About app”. This will allow organizations to start using the features, even if it’s not part of the client yet.
  • Write up technical specifications and perform design explorations for the AGP-73 Organization Insights initiative

aragonSDK & Aragon client

Not covered in AGP // contributing to the commons

  • Improve onboarding UX: Enhance how the onboarding UI conveys that a transaction is in progress and add help references to mitigate failures.
  • Token API and token dropdown component for aragonUI, to make it easier for Aragon App developers to adopt the standards in how to render tokens in a dropdown.
  • Radspec helpers for grabbing a date based on block number (historic or estimate) and for json files stored on IPFS

Expanding Projects

  • Continue adding new features to expand bounty capabilities and optimize the UX
  • Initial MVP feature set for decentralized projects app that allows creating projects and issues without needing Github

Experimental Open Enterprise Version

A big thanks to Aragon One for keeping up with the constant flow of incoming PRs to Aragon repositories. We’ve been working on a number of new features that are ready (or just about!) for Aragon One’s review, but we’re not sure in which order to prioritize them. To submit them all at once would be overwhelming for core maintainers. Here is the feature list and their current status:

Feature Link Status
3Box identity resolution github We’re waiting on new 3box profile API changes to get merged and released, which will solve a few bugs that we need in order for this to work bug-free.
Smart contract based discussions in Dot Voting Discussions app

Relies on the forwarded actions API enhancements
Open Enterprise’s template has an option for including DIscussions in Dot-Voting, but Discussion’s can’t operate with 100% flexibility until the forwarded actions API is merged and working.
Native aragon profiles (built on 3box) Aragon client branch We’re still evaluating when/how to merge this native profile into the aragon client:

- 3Box is an extremely heavy package that nearly doubles the size of the aragon client
- The profile designs were made before the new AragonUI release, so their designs are old
- We haven’t fully validated the demand for aragon profiles from real user groups
Custom organization profiles Figma design Design feedback from Aragon One was received last week and the comments will be addressed by Autark this week.
Indexing org profiles on the web and Google (SEO) - Forum discussion
- GitHub issue
Work is currently being spec’d out.
Aragon IPFS data stores for user generated content. - Motivation
- Quasar
- Custom aragon client with Quasar support
Being tested with a custom aragon client version. Will be used for saving organization profile data (once that feature is built)
Aragon.js support for interacting with smart contract governed IPFS nodes No relevant link yet Work has started this week. We will be testing this feature with the Projects app.

We’d like to start conducting usability studies for all these features, so we are planning to deploy a version of Open Enterprise to test them. We’d love to get feedback from the community to understand which features are most important and which can be improved, so we can evaluate our priorities and dev resources with the community in mind.

We hope to have this deployed end of this year, or early 2020. We’re really excited to hear from you!

Product Roadmap Update

Current target quarters are as follows for when each product initiative is estimated to reach completion. There will always be regular maintenance and upkeep, and there may be a potential shift in priorities based on user research or other demands. We will update this roadmap in subsequent updates, in the situation where we have new projections.

Target Quarter Initiative
Q4 2019 - Maintaining Open Enterprise
Q1 2020 - Expanding Projects
- Enabling Organization Insights
- Facilitating Smart Contract Based IPFS Pinning
Q2 2020 - Expanding Finance / Allocations
- Expanding Social
Late July 2020 - Enabling New Governance Mechanisms
- Making Aragon More Inclusive

Note: The Making Aragon More Inclusive initiative has open questions about priorities, based on @sohkai’s feedback in our AGP-73 forum thread. Internationalization may not be a top priority and this would have to be prioritized into Aragon One’s roadmap due to how many different Aragon One managed repos it touches.

Review AGP-73 for more details on each of the initiatives

7 Likes

Wow really like this Status Update format!!! Concrete and comprehensive.

About discussions: is it something that developers would be able to add to any app? How is UX flow going to look like? Can this be tested now?

Hello Louis! Glad you like the format.

Regarding discussions, yes developers will be able to add it to any app. But as mentioned in the update above, it requires the forwarder API.

We shared the demo URL a few months ago when we added it to our older Dot Voting app: https://preview.autark.xyz/#/dune/0x796ce2aa4d42316f4ad0b365a3d90d0743edcfb7

We will add it to our current Dot Voting app once the Forwarder API is merged.

Status Update: December 9th, 2019

Last two weeks

  • In the last two weeks we have more specifically been working on:

    • Integrating deep linking in Projects, Dot Voting and Rewards.

    • Expanding projects to allow Open Submission bounties and improve the UX around the bounty status

    • Started frontend development for adding a budget detail page for the Allocations app

    • The alternative two-token enterprise template. We had user requests to also add agent, so we are revising it to accommodate for that. We are working on a new front-end where once the user clicks on “use this template”, they can choose between a one-token or two-token organization. The Tokens screen is enhanced to be able to customize the token configuration on that screen. This allows us to just maintain a single onboarding flow, and our contract was written in a way to provide the flexibility around the token configuration.

      • The contract is almost ready to audit
      • The frontend is a WIP
    • Updating the screen during the Onboarding flow where it shows the signature transaction progress - https://github.com/AutarkLabs/aragon/issues/29

    • Forwarder API - 1hive has been interested in testing this for their work, so we were bringing the PR up to date with the latest aragon.js code and testing it in our apps again

    • Token API - almost done with the implementation, but paused work to get the spec reviewed and to understand the priorities around getting it merged into SDK. we can resume work on it once that is more clear.

    • Radspec - wrote a helper to get timestamp based on block number. Have the PR ready for internal review - https://github.com/AutarkLabs/radspec/pull/1/files

    • Token manager - Pulled code into main OE branch and started work on testing in our branch, almost ready for Rinkeby deploy.

    • DAO recovery script - https://github.com/AutarkLabs/open-enterprise/pull/1742

      This script provides the ability to generate a custom data string which can be given to users to recover their DAO if they’re unable to complete the second transaction when deploying a DAO from the Open Enterprise Template. The command is:

      npm run recoverTemplate

  • Experimental OE:

    • We have a version of OE working with several moving parts:
      • contextual discussions working in dot voting
      • aragon.js methods for interacting with the “organization data store” (quasar). Projects app is working with quasar, and is doing so (mostly) through the aragon.js methods.
      • aragon wrapper support for automatically registering apps with quasar that are marked as storage: true in their arap.json
      • 3box identity resolution is working
      • profiles built natively into aragon client
      • organization data store support build directly into aragon client

Higher level

We spent a lot of time improving our product development processes such as organizing our sprints more clearly in Github, using an epic system to manage feature sets, doing more detailed points estimates, and documenting processes around how to streamline the publishing process. Check out some of the Github organization work here.

Next two weeks

Continue the items mentioned here and in the original post of this thread, so as much of it can be included in our next mainnet push which will happen late next week.

3 Likes

Starting January 1, 2020, Open Work Labs (OWL) is no longer going to be working so closely with Autark. The culmination of the work OWL has lead will be showcased by the end of the year in an experimental Open Enterprise. The summary of this work is detailed in the earlier posts above.

For AGP-73, Open Work Labs was subcontracted by Autark to work on the IPFS pinning, social (profiles, contextual discussions), and internationalization deliverables. These initiatives are held up for various reasons, and continuously building on them is not an efficient use of capital given the expected changes to the Flock program, where grant teams like Autark are expected to focus more on app development vs. aragonSDK or client work.

As leads for AGP-73 product development, it’s mine and Jon’s responsibility to realize when the things we’re working on aren’t the highest priority and make the required adjustments. Putting these initiatives on ice allows Autark to focus on apps and tools that are more in demand. This also takes some pressure off Aragon One for reviewing these features and making immediate decisions about them (or risk wasting time and money). To both myself and Jon, it is the obvious decision.

Until the new year, OWL will be in a handoff period where they are providing in-depth documentation and example integrations for everything they worked on. It should be extremely easy for other members of Autark, Aragon One or anyone else to pick up where OWL left off. Additionally, OWL can be contracted in the future again if those initiatives become higher priority and they have the bandwidth.

Resource allocation changes

Per AGP-73, we had budgeted for 11 full-time resources, which was a combination of Autark and OWL’s labor. We ended up taking Autark’s headcount to 10, with the addition of Peter Phillips. Instead of hiring an additional developer, we plan on allocating that portion of the budget toward marketing and operations consultants. We have contracted Maly Ly, a professional with over 18 years of experience taking products to market for CMO consulting. With the addition of an operations consultant, I will have more time to focus on user adoption and growth, as opposed to administrative duties.

Next steps

In the meantime, Autark will continue marching forward with the initiatives planned out in AGP-73 that are being highlighted in this thread. We are starting to find the sweet spot between catering toward the demands of our early adopters in addition to designing new tools and functionality that can bring greater adoption to Aragon. We are currently undergoing market and user research and will be sharing the results of this work in early February, as our 6 month check-in for AGP-73. It’s exciting to see our vision of open and collaborative futures come to life.

If you have any questions, let me know!

5 Likes

January 9th, 2020 Updates

Since we launched on November 12th, Open Enterprise has become the #1 configuration for new mainnet DAOs on Aragon.

From November 12th until December 31st, there have been a total of 99 organizations created, and 39* of those are Open Enterprise organizations. We feel pretty excited that the new users are most interested in using the software we have developed to power their open organizations.

*Note: this number was updated from what we initially published (60), after determining that the counts on https://scout.cool/aragon/mainnet/ included failed transactions that occurred due to gas issues that the user had. This value of 39 has been determined based on the number of app installs on Apiary, and then deducting the count of new orgs in 2020.

New Features on Mainnet - Released in December 2019

1. We’ve introduced a new budget detail view in the Allocations app

2. We’ve created an Allocations summary region, introduced new and improved budget card designs, and enabled the ability to edit and deactivate budgets

3. The bounties experience was redesigned and now supports bounties that don’t require applications

4. We’ve introduced a revamped UX for the Projects app issue detail view, to make bounty details and actions more intuitive

5. You can now enjoy deep links across all apps

Expect more by the end of the month - stay tuned here for those updates :slight_smile:

4 Likes