Hi everyone! This is the 14:00z JS menu component initiative meeting. The conversation will take place across various threads.0️⃣ let us know who's here (please include your d.o username)
| gabesullice | Hello! Gabe here in :flag-us: It's time for the 1400z "focus time"Friendly reminders for:@justafish @baddysonja @nod_ @e0ipso @lauriii @Gábor Hojtsy (he/him) @gabesullice @Liam Hockley @e0ipso @yoroy @Raúl Garcia Canet @nod_Please DM me if you would like to be added/removed from the reminder list. |
| baddysonja | Hi @baddysonja is here :smile: - just finishing a meeting (edited) |
| nod_ | hello |
| e0ipso | Hello all! |
| baddysonja | @Liam Hockley can you share with me your d.o. username for the credit assignment :slightly_smiling_face: |
| e0ipso | @baddysonja https://www.drupal.org/u/lhockley :slightly_smiling_face: |
1️⃣ Last week, we had a productive meeting with core committers and Dries. We discussed the initiative idea issue. Specifically, its scope and what we want to achieve. We got buy-in on the idea and were left with a couple to-dos (to be posted separately)An issue we've been focused on is how to ship a JS library to consume menu data. Since it doesn't make sense to ship that library with core itself, we need to propose some policy changes to accommodate that. I think it's getting close to completion, but there is still a place where you can help: https://drupal.slack.com/archives/C016N3HTHRD/p1604683613423400
| gabesullice | @Liam Hockley took some great notes during that meeting. You can find them here: https://drupal.slack.com/archives/C016N3HTHRD/p1604679103417200 |
2️⃣ Our first and most major to-do for completing the initiative idea issue is to decide on who our initiative coordinator(s) will be. We started that discussion here: https://drupal.slack.com/archives/C016N3HTHRD/p1604680708420800
| baddysonja | I want to make a suggestion to have @gabesullice and @nod_ as official initiative coordinators. As a backup, I can always jump in and help (we can think about it like being on the bench in a sport team, when someone gets hurt/sick I jump in and take the place) - ok maybe not the best metaphor but you get my point :slightly_smiling_face: |
| nod_ | That works for me, let's wrap this subject up. We can always revisit later. :+1: |
| e0ipso | LOLNo devs were hurt during the intitiative. |
| e0ipso | Thanks to all that volunteered. It's not easy to take a commitment. You rock! |
| baddysonja | #3170260: Decoupled Menus Initiative#comment-13898403No more blockers :slightly_smiling_face: |
| gabesullice | I formalized roles in the ideas queue issue. I added an "Appointees" section for @baddysonja @Liam Hockley and @Ashutosh Gupta. Feel free to rename your titles to something that better reflects what you hope to do. I just made them up off the top of my head. (edited) |
| Liam Hockley | Works for me. :thumbsup: |
3️⃣ A second todo, and this is not necessarily require (it's a nice-to-have) would be an FAQ for the initiative that explains the decisions we've made. For example, why are we not building actual components with markup and styles? Would someone like to own this?
| mirom | what is difference between library and the component? just styling and markup? |
| gabesullice | A library would be agnostic WRT to React/Vue/Angular. It would help fetch/parse the data that one would use to hydrate a component. |
| gabesullice | Since most sites are going to have unique styling and markup for their navigation component, we didn't think it makes a lot of sense to provide something that will have to be overridden if your design deviates from what we provide |
| gabesullice | Instead, we can put all the data handling into a library and let people reuse that no matter what markup they need. (edited) |
| e0ipso | I have seen decision logs in other free software communities. |
| e0ipso | Some times it serves as an avenue for a lurker to reopen a painful decision you thought put to bed. |
| e0ipso | But in general I'd say that it is a great tool |
| gabesullice | @baddysonja created this project, I think it makes sense for use to record things there: https://www.drupal.org/project/issues/js_menu_component_initiative?categ... |
| e0ipso | :raised_hand::skin-tone-4: I offer myself to build and host a Drupal instance for the coordination of the initiative.We can have a content type for decisions. |
| e0ipso | oops |
| e0ipso | we can use that as well. |
| e0ipso | I was over engineering things |
| e0ipso | My focus is to use Drupal tools, and your proposal is :first_place_medal: (edited) |
| nod_ | too bad for the namespace though :stuck_out_tongue: |
| e0ipso | didn't even notice it xD (edited) |
| baddysonja | yes, the project as created before we changed the name :disappointed:Maybe some of our master webmasters can change the machine name? |
| baddysonja | #3181747: Create FAQ |
| nod_ | decoupled_menus_initiative that works for everyone for the machine name? |
| gabesullice | I don't have the ability to change it. |
| mirom | I have seen decision logs in other free software communities.I think it's more important to have FAQ at this point. Something we can publish on https://www.drupal.org/about/strategic-initiatives/javascript-menu :slightly_smiling_face: |
| nod_ | moved the 2 issues over the new project: https://www.drupal.org/project/decoupled_menus_initiative |
4️⃣ I think @Liam Hockley and @shaal were going to look into what the most used menu components are in React/Vue, respectively. If I remember that correctly, any updates?
| nod_ | I'd be interested to see if there is an expected data format for the different components that exists |
| Liam Hockley | It was my understanding that someone who was more involved with Decoupled Drupal, would be asking around? Unless we are looking for menu components of outside of the Decoupled Drupal ecosystem. |
| gabesullice | Ah, I thought we were going to look outside the Drupal world |
| Liam Hockley | That's cool. On that front, I am familiar with Vuetify, and have heard of Bootstrap Vue. I will say that Vuetify is much more "thought out", and makes extensive use of props and slots where as Vue Bootstrap is simply a wrapper for Bootstrap.https://vuetifyjs.com/en/components/menus/#menushttps://bootstrap-vue.or... (edited) |
| Liam Hockley | Aside from that, I think we really should look for some decoupled Drupal code. Since we know that a lot of agencies have had ample experience addressing this for clients. Perhaps @baddysonja and/or @e0ipso has some input? |
| baddysonja | We do a lot with React and Next.Js -> I will ask my colleagues and check if they have some components that we could use |
| shaal | @Deciphered - do you have some examples you can share? |
| Deciphered | @Liam Hockley you should ensure that the component is UI framework agnostic.Vue components can pass through to dynamic components via the :is directive, allowing you to give the choice to the user. |
| Liam Hockley | Right. Which is why I suggest us looking specifically at decoupled Drupal menus, with an interest in the API adapter logic. And how teams have addressed the challenges of internal/external routing.Vuetify and VueBootstrap don't tell us much, except for the fact that we are likely going to want to deliver an object of some sort.A format like this:{ label: , uri: , internal: ,} |
| Deciphered | Here’s an example of DruxtJS Menu being themed using BootstrapVue using both props and named templates: https://github.com/druxt/demo.druxtjs.org/blob/develop/components/druxt/... |
5️⃣ Drupal core ideas issue: #3170260: Decoupled Menus Initiative - does anyone know when this will be approved? Are we waiting for anything?
| gabesullice | Yes, we are waiting for 2️⃣ above. |
| baddysonja | Is there a documentation on d.o. how this process works? What does it mean when an issue in Drupal core ideas is approved? Should the issue queue for the initiative still be in our community project or does it move to somewhere else? |
| gabesullice | https://www.drupal.org/project/ideas is the closest thing to documentation we have I think. @yoroy, correct me if I'm wrong, but that documentation is not exactly up-to-date or accurate though? (edited) |
| baddysonja | this is great - thanks :slightly_smiling_face: |
| nod_ | The roadmap in the google doc should probably be put in the issue summary as well |
| yoroy | @gabesullice I'd have to look at it to remind myself. In general, the team decides where, how to collaborate. We need a highlevel issue on d.o. as a way in for finding out about the initiative. |
| yoroy | Although the library part is not "core", you'll eventually want a meta issue in the js or json core queue(s) to keep track of the work there. I'll find some examples when not on the phone :-) |
| yoroy | For example, this is the idea for Claro as posted to the Ideas queue: #2902399: Redesign the Admin UI (edited) |
| yoroy | After some back and forth on that, the Plan is this: #3017785: Designs for a new admin theme |
| yoroy | And the implementation roadmap/meta issue is #3066007: Roadmap to stabilize Claro |
| yoroy | ^^ @gabesullice and @nod_ |
| nod_ | thanks i'll look that up tomorrow |
6️⃣ Should we rename the slack channel soon?
| timplunkett (he/him) | Feel free to ping me if you need help renaming it |
| gabesullice | Done. Updating issue now. |
| timplunkett (he/him) | Oh nice, yay for reasonable Slack permissions |
| gabesullice | Might be because I created this channel. |
7️⃣ Similarities and differences between this initiative and ContentaCMS.org
| e0ipso | This question has come up a couple times already and this initiative is in its infancy. |
| e0ipso | Do we want to add this to the FAQ mentioned in 3️⃣ ? |
| nod_ | yes |
8️⃣ "Ressources" possibly missing from current team:Technical writing, anyone has experience in that space? as in writting technical doc for clients and allDocumentation maintainer: there is nobody in Maintainers.txt for the documentation and we will have some pretty big needs around documentation interactivity (I would think) or even stying to be on par with the rest of the industry
| Liam Hockley | I am cool to help documentation, but my lack of experience may be a concern. I do like the idea of structured commits feeding into an automated changelog. |
| baddysonja | Does anyone know a simple way to copy the meeting text + thread from Slack to a textformat? |
| e0ipso | @gabesullice does know a tool |
| gabesullice | @baddysonja https://github.com/mdlutz24/drupal-meeting-parser |
🔟 Who can set up https://www.drupal.org/about/strategic-initiatives/javascript-menu or is it waiting for sign off? It's referenced from https://www.drupal.org/about/core/strategic-initiatives.
| hestenet (he/him) | A number of existing DA staff and core maintainers have permissions right now - and I can add any other initiative maintainer - just need the right user name :slightly_smiling_face: |
| yoroy | https://www.drupal.org/about/strategic-initiatives/admin-ui-js probably needs some updating too then |
| yoroy | or repurposing? |
| e0ipso | cc @justafish |
| justafish | +1 to re-purposing the existing one. I can edit that if there's no objections |
1️⃣ 1️⃣ I’m trying to organize a meeting with the committers on the governance changes. Please fill this doodle to find suitable time https://doodle.com/poll/mehgusncgxscsfpt
| Deciphered | @lauriii All of those time slots are too early for me. |
| lauriii | @Deciphered By how much are those too early? I could try to find a better time when we schedule next meeting |
| Deciphered | They're 3-5am AEDT, I wouldn't be of much use. Maybe 6am. |
| Deciphered | I'm also unsure of my need to be present though, as my role is outside of the scope of this initiative. |
Thanks to @baddysonja for the suggestion, and @mglaman for his work building the tool. I have set up Kanban boards to track our issues for the Decoupled menus component project, as well as a board for the external blockers for the project.Main Project Board: https://contribkanban.com/board/decoupled_menus_initiativeBlockers: https://contribkanban.com/node-board/a5e435b3-84c8-4b37-a45f-527c77dfafcdIf you have any additional blocker issues, please let me know so I can add them to the custom board. (edited)
| Gábor Hojtsy (he/him) | Would be great to put the links into the channel topic / description. |
| baddysonja | I will take care of it :+1::skin-tone-2: |
Hi everyone! This is the 4:00z Decoupled menu component initiative meeting. The conversation will take place across various threads.0️⃣ let us know who's here (please include your d.o username)
| Deciphered | Hi, Stuart here. Going to be looking at DruxtJS Menu related work. PM me if you want to chat. |
| Ashutosh Gupta | hi stuart this is Ashutosh |
| e0ipso | Mateu :desert_island: |
Participants:
gabesullice, baddysonja, nod_, e0ipso, Liam Hockley, mirom, shaal, Deciphered, yoroy, timplunkett (he/him), hestenet, justafish, lauriii, Gábor Hojtsy, Ashutosh Gupta
Comments
Comment #11
baddysonjaComment #14
baddysonjaComment #17
baddysonjaComment #18
baddysonjaComment #19
gabesulliceComment #20
baddysonjaComment #21
baddysonja