-
Notifications
You must be signed in to change notification settings - Fork 17
Conversation
* Updates to 2019 roadmap * More changes * Add custom labels to scope
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
Co-Authored-By: Brett Sun <qisheng.brett.sun@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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).
Great! Thank you @LouisGrx! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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: