Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aragon One: 2019 mid update #15

Merged
merged 12 commits into from May 30, 2019

Conversation

Projects
None yet
4 participants
@luisivan
Copy link
Member

commented May 15, 2019

Note: This is a follow up to the previous PR that was accidentally unilaterally merged

We want to update Aragon One's roadmap for 2019 to reflect on the following:

  • Items that have been already delivered, and items that are on its way for the next quarter
  • Removing a native mobile app from the scope for focus sake
  • Removing Aragon app monetization since we first need users for the platform to be interesting for devs
  • Adding caching, fundraising, notifications and Aragon client re-design to the scope
  • Updating the team info

luisivan added some commits May 15, 2019

2019 mid update (#2)
* Updates to 2019 roadmap

* More changes

* Add custom labels to scope

@luisivan luisivan added the review label May 15, 2019

@luisivan luisivan requested review from stefanobernardi and LouisGrx May 15, 2019

@luisivan luisivan changed the title 2019 mid update Aragon One: 2019 mid update May 15, 2019

luisivan added some commits May 16, 2019

Show resolved Hide resolved teams/Aragon One/2019.md Outdated
Show resolved Hide resolved teams/Aragon One/2019.md Outdated
Show resolved Hide resolved teams/Aragon One/2019.md Outdated
Show resolved Hide resolved teams/Aragon One/2019.md Outdated

luisivan and others added some commits May 16, 2019

Typo
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
Update teams/Aragon One/2019.md
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
Update teams/Aragon One/2019.md
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
Update teams/Aragon One/2019.md
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
@LouisGrx
Copy link
Member

left a comment

Hey there,

This mid-Flock roadmap update seems on point. On my side I see no reason why it shouldn't be approved from an Aragon Association's stand point.

As it is pretty substantial and also for transparency standards, the Aragon Association would still make it mandatory for Aragon One to disclose a very explicit "roadmap update report" to the rest of the community. This would have to be posted at least on the Aragon Forum.

Once the report in question is out, the Aragon Association will take care of merging this PR.

Available if you have questions.

On Roadmap updates

It is the first event of this kind and we will probably have to formalize the roadmap update process somewhere in the Flock repo. Roadmap updates could probably be issued by Flock teams once or twice during their Flock mandate depending on the duration of their funding (hear 2 times for a year, 1 time for 6 months).

@luisivan

This comment has been minimized.

Copy link
Member Author

commented May 28, 2019

Great! Thank you @LouisGrx!

@stefanobernardi
Copy link
Contributor

left a comment

Thanks for the update to the Aragon One team.

Roadmaps are impossible to strictly follow: the world and our specific ecosystem are complex, and it's normal that priorities change leading to a different final roadmap.

Given the changes remove some parts but add others, I think this is a fair change and approve it.
In situations like these, we might still issue some statements with our opinion as to wether the changes are reasonable under the scope of the relevant approved AGP proposal.

@stefanobernardi stefanobernardi merged commit e6d9275 into aragon:master May 30, 2019

1 check passed

license/cla Contributor License Agreement is signed.
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.