cryptonetlab / retriev

Home of Retriev protocol (by CryptoNet + YOMI)
https://retriev.org
18 stars 6 forks source link

Product Design & Implementation (EPIC) #34

Closed 0xjona closed 2 years ago

0xjona commented 2 years ago

Together with @claudiofabbro https://claudio.dance , we are designing the product aspects of the data retrievability oracle protocol @Steve-Rog will initiate and maintain the code!

DESIGN PROCESS

Each Tuesday morning there will be a kick-off meeting / brief sent via email from client (@irenegia) so that @claudiofabbro knows what we are expecting from him. Each issue has a due date (one week after kick-off), in order to move to the next one and respect the overall deadline.

This process is made of 3 steps (+1) due for the #1st release milestone

CODING PROCESS

Stefano will follow up with updates from the design, plus is already intervening to make key improvements on the MVP

We'll track this work in the following issues

0xjona commented 2 years ago

@Steve-Rog you and @claudiofabbro will need to sync when moving from design to implementation of the homepage; we should start talking about this effort ASAP

0xjona commented 2 years ago

kick-off / briefing @irenegia

0xjona commented 2 years ago

Every Tuesday at 9:30 CET @irenegia will provide a briefing and some feedbacks on the work made to me and @claudiofabbro (who will share comments and questions previously on the related github issue)

0xjona commented 2 years ago

I'm aware issues related to this process will undergo maintenance and improvements for a couple of weeks more, so how to track this? Plus, given lack of proper design docs from the client, we're pivoting more than expected so issues can't be considered closed as most of the time in need of further validation.

I'm also aware we'll do this for #35 but we'll come back to this on a second release, will I need another issue? Can we consider this iterations?

Plus, do we have any threshold to monitor while developing? In terms of efforts/cost or weight?

0xjona commented 2 years ago

Working on this in #62