search

btcpayserver / organization

Open-organization, meetings, calendars, project management
https://btcpayserver.org
17 stars 3 forks source link

Design Call #12 #42

Closed Zaxounette closed 3 years ago

Zaxounette commented 3 years ago 
Date: 2021-07-01
Time: 5:00pm
Timezone: UTC
Duration: 1h
UTCTime: 2021-07-01 17:00 UTC

Agenda

Comment below to add items to the agenda.

Check your timezone

https://everytimezone.com/s/70c0fca0

Join the call

https://meet.jit.si/IAmHappyYouAreHappyWereAllHappy

Calendar invite

Subscribe to the BTCPay Server calendar. More info here.

dstrukt commented 3 years ago

Now that I'm digging into more details, and starting to touch other parts of the app, I wanted us to be able to discuss some high level product discussions about things so we can keep thing consistent / get multiple POVs.

Actionable topics of discussion:

Short:

Medium to LOng:

Not immediately actionable topics, lower priority:

Concrete work, anything to discuss:

*will update

Zaxounette commented 3 years ago
  • When should we educate a user what a feature is.. in the empty list view state

Throwing this idea out so as to not forget it while we discuss it: Education items can be nested in the empty states views. Those views currently have a lot of white emptiness that can be used, so why not use that space for education? TBD.

Additional items for future reference. Not necessarily to be discussed on next call, but to be kept in the backlog.

dstrukt commented 3 years ago

Agreed, I think that was my first inclination as well, and we decide to roll with this direction, we can determine how much or little to share, definitely a few things to consider, but it's a great point, and something I thought you'd have quite a few thoughts on!

dennisreimann commented 3 years ago

Topics list from my side:

Zaxounette commented 3 years ago

Hey!

With all the UI related discussions, issues, PR's and such having a "let's talk about that in our next call", i'm proposing we extend this meeting by an hour, for a total of 2 hours. One hour flies by and will probably not be enough.

@dennisreimann @dstrukt @woutersamaey Thoughts?

dennisreimann commented 3 years ago

Sorry, but I'm against extending the duration. We will have some pair programming sessions in which we can address the PRs and issues in depth -- I'd rather use these to discuss things further and limit things to what actually needs to be decided on in the design meetings.

Also: If there are too many things on the plate we should focus on what's gonna be worked on during the two weeks until the next design meeting. My impression is that we should not spread ourselves too thin and sometimes changes emerge because of something we implement.

TL;DR/My 2 sats: Let's not plan too much in advance but focus on the upcoming two weeks.

dstrukt commented 3 years ago

That's perfectly reasonable, probably a good call to try to keep it as short as we feasibly can, I don't personally mind 5-15 min spill over, but an additional hour might be a bit much.

I'll go through my post and isolate what/if any deserves a team discussion vs. pair programming / addressable at that time, and if the list is still long, will prioritize accordingly based on what's current on all our plates.

Zaxounette commented 3 years ago

@dennisreimann @dstrukt You don't like me enough to hang around for 2 hours, noted!

Thanks for the feedback :)

dstrukt commented 3 years ago

I never said I wouldn't <3 .. just trying to be respectful of everyone's time.

I definitely think a session or separate call where we discuss higher level ideas, etc.. a little more overall product / roadmap focused, vs. more specific design and dev, would be awesome though. We're deep in the weeds, but I always enjoy hearing what's inspiring all of you, and taking a view above water to bring it all into context.

woutersamaey commented 3 years ago

For discussion:

Should we not add text-danger to all Delete links? Like so?

image

Seeing "Remove" links in green upsets me a little bit, and it is a dangerous link so text-danger lives for this.

Zaxounette commented 3 years ago

Design Call N°12 Notes:

Attendees: Dennis, Dstrukt, Pavlenex, Zaxounette, Woutersamaey

Footer & Credits: Discussion about refactoring the footer and removing altogether the logo credits. Consensus is found on the credit deletion. Pavlenex has discussed this with Nicolas a few months ago.

Payment request changes: Discussion on payment request modal changes:

Icons and buttons: Discussion on the styles of icons. Some of our icons lack consistency. Should explore using and leveraging icons that bitcoin.design have produced. or icon formatting.

Fields and columns: Discussing work in progress changes in fields and columns:

Crowdfund creation page changes: Discussions about horizontal tables and mobile wrapping. Solution will be explored. A downside is discussed:

Custom fields: The idea of having custom fields (Company Name, Customer fields, etc ...) is discussed. A solution is exposed:

It is mentioned that there are a lot of issues around this particular topic and that:

Solution will be researched.

Hiding/showing options based on checkbox select in Point of Sale view

Point of Sale redirect / invoice functionality clarification Is discussed the fact that any option that relates remotely to an option that wouldn't be usable by a regular user could be tucked into an "Advanced Option" menu at the bottom of the view.

Delete confirmation modal: https://github.com/btcpayserver/btcpayserver/pull/2614 Consensus on the approach. Can be the subject of one of Dennis and Dstrukt's pair programming sessions.

App intermediate creation view Discussion around the idea of deleting intermediate view and replacing with a dropdown with clicking Create App.

Pair programming session scheduling: Sessions will be scheduled along the next weeks between Dennis, Dstrukt and Woutersamaey.

Alerts and errors: Mocks will be prepared for next scheduled call.

All other items are postponed for next calls.