circles-myxogastria icon indicating copy to clipboard operation
circles-myxogastria copied to clipboard

Add image, name of trusted users in Validation process

Open mikozet opened this issue 2 years ago • 8 comments

https://www.figma.com/file/ZTqF54s6CSHTwAxp0U0JjQ/Circles-myxogastria?node-id=4350%3A42078 Zrzut ekranu 2022-04-4 o 00 38 25

mikozet avatar Apr 03 '22 22:04 mikozet

what should happen if names are long in this limited space? @triaslucia

louilinn avatar May 03 '22 06:05 louilinn

@louilinn
1.Names habe in mobile verison a max lenght of 90px. 
 2.The have a mximun of 2 lines. 
 3.If they do not fit , they are cutting by adding “...” at the end of the second line.

Design material: https://www.figma.com/file/ZTqF54s6CSHTwAxp0U0JjQ/Circles-myxogastria?node-id=5761%3A11386

Screenshot 2022-05-19 at 18 16 14

triaslucia avatar May 19 '22 16:05 triaslucia

https://github.com/CirclesUBI/circles-core/issues/124

louilinn avatar Jul 01 '22 11:07 louilinn

It does not make too much sense to do frontend here without backend as it would be almost adding an icon - we have to wait for backend

mikozet avatar Nov 21 '22 03:11 mikozet

As we want to replace the relayer and current validation system with an invitation system I would consider deprioritizing this completely

louilinn avatar Dec 02 '22 15:12 louilinn

@JacqueGM Are we moving forward with the idea of invitation system?

Anyways, Could you give an estimation of work time that you need in backend, to finalize this issue with the displaying of the pictures during the current verification process? thanks!

triaslucia avatar May 03 '23 12:05 triaslucia

Please add your planning poker estimate with Zenhub @mikozet

louilinn avatar Jun 16 '23 12:06 louilinn

@triaslucia As discussed last meeting, invitation system seems low priority at this point, revisiting next meeting.

We have an estimation of the backend work. It is something we should be able to fit into one single sprint among some other things.

Front end has a seperate estimate (this issue). Backend issue linked above has its own points estimate. In general you can start looking at the points we assign tasks (right side panel under estimate) to see how tasks compare in size. At the moment we manage to do around 30 points in the whole team per sprint under normal conditions (not vacation times) and that is including a lot of back-end maintenance. So we have capacity for maybe half of that each sprint to chose what to do. Thus, a 13 point task is around 1 sprint if we only do that and since one person only will do one thing it will take probably 2 sprints. We can talk about estimates next time. But this is a general information for transparency of our estimates :)

louilinn avatar Jun 16 '23 12:06 louilinn