Meeting Agenda

  1. Introductions
  2. New issues
  3. #3095181: Create a list of tasks/items that can be worked on while building POC
  4. Content for the getting started guide on homepage.

Meeting Details

Time: 3pm UTC (10am Eastern)
Meeting Location: #d9-theme channel on drupal.slack.com

:zero: If you’re attending this meeting, please 1) Let us know here, and 2) comment in the meeting agenda issue above so we can give issue credit on d.o

mherchel I’m here :stuck_out_tongue:
Putra Bonaccorsi I'm attending :wave:
Gábor Hojtsy (he/him) Hey :)
Jen Witkowski I'm attending
MaddieC Hello :wave::skin-tone-2:
Kat Shaw I'm here.
mtift Hello, everyone!
felix Hi :wave:
starshaped (she/her) I’m here!
vulcanr +1
shaal Hello!
thhafner hello!
cwells here today, lurking! :slightly_smiling_face:
thejimbirch Ditto!
Bhavin Joshi (he/him) Hello!
Natalie Cainaru Hi! I'm attending!

:one: New issues

mherchel I created #3095673: Convert codebase to use CSS logical properties for RTL support
mherchel :point_up: might end up replacing some of the RTL support that we just merged in. The CSS syntax is more modern and meant for RTL. That being said, it’s not a requirement for MVP
mherchel Andrew created #3095152: Separate the focus and error styles for form elements. This is an issue to improve focus styles. He gives a very good example where our current focus styles may not be adequate
mherchel cc @Jen Witkowski on :point_up: . I can walk you through that workflow if needed
Jen Witkowski @mherchel sounds good!
mherchel If anyone has anything to add to these, or has ideas to create an issue, please either create the issue, or discuss it here
shaal @mherchel regarding CSS Logical Properties, Do we have any concerns with no IE11 support?Or the plan is to have postcss make the translation to "regular" css ?https://www.caniuse.com/#feat=css-logical-props
mherchel @shaal My thought is to evaluate it… from what I looked at, the PostCSS plugin should work to make the CSS compatible..
mherchel it’s definitely not a “plan” yet.
shaal I really like the idea!

:two: Issue: #3095181: Create a list of tasks/items that can be worked on while building POC

mherchel I want to give extra visibility to this issue, because this can give us a little opportunity to get ahead of the game. There are various tasks that we can start working on in the theme system.
mherchel I would love love love it, if people can look through, and add to task
mherchel even more helpful would be to split identified tasks out into their own issues
Putra Bonaccorsi Agreed! I think we have a good list gathered, however, I just wanted to see if folks have other ideas or thoughts. Feel free to add a comment to the issue. :slightly_smiling_face: (edited)
mherchel yes! And discuss here if you have questions, or if you think of any, feel free to ping either @Putra Bonaccorsi or I!

:three: I created #3095736: Create content for Drupal's initial "Getting started" page (after minimal or standard profile installation) a couple days ago. The tl;dr is that we have the opportunity to server helpful “getting started” text on the initial install screen. We need to figure out what will be useful

mherchel I honestly expected more feedback on this than I’ve gotten. I’ve been throwing around an idea in my head to create an informal committee. But I’m still not quite sure. Does anyone have thoughts?
mherchel If there is a committee. I want it to represent many types of Drupal users (front-end, backend, site-builders, non-US, etc)
mherchel :cricket: :cricket: :cricket:
felix this should be much more empowering than it is now! instead of presenting content I would use this site to give helpful links into the installation to get up and running – I’ll comment on the issue aswell
vulcanr For this I think would be helpful to get some people from Core Documentation to give a hand or ideas on this
Putra Bonaccorsi I agree. It think providing more context to the user about what the theme can offer or just general information about getting set up is helpful. Sounds like we need some volunteer to help with the copy and asset creation so that we have a page with text and placeholder imagery.
cwells I just threw my $0.02 into the issue. I think general onboarding for Drupal but also re: the theme is important.
Natalie Cainaru ^ I like @cwells idea. it gives someone new to Drupal and the theme a good starting point. My only concern is, with one of the limitations being "Cannot assume that an external internet connection is available (no pulling in data)", would providing links to other documentation (e.g., "More About Blocks" link included in @cwells comment on the issue) be out of the question?

:four: General status updates, etc

mherchel A note to everyone. This is Thanksgiving week in the USA. Many people will be not working, and therefore might not be very responsive. I personally will be working for the majority of the week, and hope to make a lot of progress
mherchel There are several PRs that I need to review. I will get to these today or tomorrow
mherchel I also plan on starting to work on a11y improvements to the primary navigation per Andrew’s suggestions.
Kat Shaw I was able to get my local site running at the end of last week so I'm hoping to work on some of the frontend/a11y issues this week and beyond.
mherchel yay! Let me know if you need anything!
Kat Shaw Will do!
vulcanr @mherchel lt me know if any hand is needed for that
mherchel will do!

:five: Additional issues to discuss

mherchel Thanks @shaal for the reminder :stuck_out_tongue:
shaal I remembered that from my initial experience with Claro, I wanted to get involved but it wasn't clear at all :disappointed:Questions like:What's the current statusWhat parts are ready to be themedWhat tasks can I work on nowCan I help with documentation / creating a patch / reviewing a patchIf you know how to navigate your way through d.o, it shouldn't be a problem, but I'm afraid that would limit the help we can get from so many more people.My suggestion on how we might be able to solve this - creating a status dashboard with where things are at, and categories of what tasks need what kind of help using Google Sheets.Then reference this dashboard in any Olivero related page (so it's easy to get there)
mherchel I think that’s a fantastic suggestion. If someone wants to do this, I’m 100% for it. I might even bug @mtift, as he’s doing community stuff etc (not sure of his availability, though)
shaal I asked @mglaman in the past to add "categories" (like documentation, code, theme, QA, etc) to contribkanban.comcontribkanban is awesome as a real-time dashbaord (and running sprints on it, instead of just "all Olivero issues" which will become a huge list) (edited)
Putra Bonaccorsi I think @shaal brings up a great point. It might be helpful for us to do a quick walk through of the open-source kanban board during our weekly meeting.
mherchel I tried to set contrib kanban up… it wasn’t quite as easy as I expected. But then I gave up (because i was busy w something else)
mglaman yeah the ux sucks
mherchel I blame this guy named Matt
mglaman So you can either add a project, a tag, or an issue collection board of node IDs
mglaman I hid the uber API query builder setup
shaal Here's how we managed Umami's 8.8 sprint in contribkanban -https://is.gd/ootb88 (edited)
mherchel @shaal do you have availability to set up contrib kanban?
shaal sure, it's very quick
mherchel it’s okay to say no
mherchel cool!
shaal What do you think about the "sprints" idea?
mglaman It's an issue collection board - so if you register you just need to do "Add board"
shaal instead of "everything"
mglaman and each sprint is like its own board
mherchel I’ll create an issue in Drupal.org
shaal @mglaman so sprint as a category in an issue ? (edited)
mglaman https://contribkanban.com/boards/sprint === issue tags
mglaman https://contribkanban.com/boards/project === projects (modules, themes)
mherchel #3096635: Set up Contrib Kanban for use with Olivero PoC
Putra Bonaccorsi @mherchel We have one created for the POC work - https://contribkanban.com/node-board/871176c7-4b70-476c-b89f-138eb95ca02f
mglaman https://contribkanban.com/user/25/node-boards/add (well, not with that uid) is what builds issue collections to manually collect issues in a planned sprint
mglaman :smile: problem is there is "Sprint" as in code sprint (ie: tags), and sprint as in planning work
mherchel yeah, that’s the one I was trying to do. Not sure how it was interfacing
mherchel @Putra Bonaccorsi
shaal :thinking_face:
Putra Bonaccorsi Feels like we can add on to this existing board with the new issues we're tracking.
mglaman I am more than open to suggestions to make contribkanban less of an ugly cluster mess.
mherchel @mglaman its a super valuable tool. Thanks for doing it. It’s not an ugly cluster mess :slightly_smiling_face: (edited)
Bhavin Joshi (he/him) We can use it
shaal https://drupal.slack.com/archives/CJT807H7T/p1574695996404600?thread_ts=...
shaal oooh, this is great!...how do we keep a clear "current" sprint everywhere? perhaps we should pin it to this slack channel? (edited)
Putra Bonaccorsi Feels like all of us are on the same page here. Just to verify, we're going to organize all of our existing issues in Contrib Kanban so that we it's clear on the status of everything. If that's the case, would it make sense to use the current POC board for the rest of the Olivero work or just create a new one. @shaal or @mherchel What do you both think?
mherchel I’m for that.
Putra Bonaccorsi Great! let's do it. I think we can just rename the POC board to Olivero D9 Theme and track all of the tickets there.
shaal The one concern I have, is having too many issues displayed at once.That's why I like the idea of sprints
shaal (or any way that would allow us to work with smaller boards)
mherchel that’s valid
mglaman one thing tim.plunkett did was have a board which only showed issues tagged "sprint"
mglaman I can make that for ya'll
Putra Bonaccorsi Right, that's a great point. Is there a way to group tickets into sprint on contribkanban?
mglaman project = corecomponent = oliverotags = [sprint]
mherchel my initial thought is that this sprint is the Proof of Concept
shaal right, this sprint is POC
shaal can we then name each sprint differently? so it's easy to move from sprint to sprint?(then contrib kanban "current sprint" board will be different every time we swtich to next sprint) (edited)
Putra Bonaccorsi @mherchel @shaal Right, however, I think it's helpful to see issues that can be worked on while we're finalizing the POC work. Perhaps, we can streamline those tickets in a "Backlog" column, so that everyone knows what is coming up at least. Just thinking about this discussion (#3095181: Create a list of tasks/items that can be worked on while building POC) because we are going to start to break out some of these items into issues soon.
shaal I think specifically on that case it could make sense to have '2 sprints' at the same time, because these are 2 different skills sets, poc and the Drupal-theme work that can get start.
Putra Bonaccorsi Sure! I think that sounds good!

:six: Official meeting is over, but the conversations will continue. Thank you for showing up and contributing! I know the timeline is tight, and we’re all figuring out where we fit in with the project. If you have questions or comments, please post them here, or feel free to DM me also :wave:

Putra Bonaccorsi @mherchel Thanks for running the meeting! For those who are celebrating Thanksgiving this week, I hope you all have a great turkey day! :turkey::fallen_leaf:

Comments

mtift created an issue. See original summary.

mherchel’s picture

Issue summary: View changes
mherchel’s picture

Issue summary: View changes
mherchel’s picture

Issue summary: View changes
chrisfromredfin’s picture

here

vulcanr’s picture

Attended

shaal’s picture

I attended

fhaeberle’s picture

Attended :)

beautifulmind’s picture

I attended.

MaddieC’s picture

I attended :)

mikelutz’s picture

Issue summary: View changes
mtift’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.