So, we will add new issues in there as appropriate. There’s a new “olivero theme” component created for core issues Which leads us into to working on issues going forward! Moving issues from the contrib project doesn’t take much time so it would be good if someone could keep an eye on the issue queue and move any issues from there to the core queueīTW the replaced by snippet is a message generated by d.o if you fill in the specific “replaced by” entity reference field on the project edit form :slightly_smiling_face:Ĥ️⃣ Working on issues going forward mherchel I also get notifications for new issues, so I can reply when necessary.
Partyparrot thumbsup slack update#
We’ll need to update the project page for Olivero and docs My concern is now there are 2 places where people can post issues. I want to make sure the issue is still happening etcĪnd I want to make sure that the title of the issue is updated to indicate that it is for and I will be meeting this Wednesday to go through all of the existing issues and triage them accordingly.
I want to look at the issues individually, and then triage them into priorities, etc. We should deprecate Bartik as part of making it not the default or shortly afterģ️⃣ Plan for moving Olivero issues to core created #3177364: Open Olivero issues should be moved to Drupal core's new "Olivero theme" component, but I don’t want to just start moving stuff over… Yeah Bartik should be deprecated, I think deprecating Bartik would not be a pre-requisite of making Olivero the default, otherwise we may end up with a default theme that is itself deprecated :wink: That would probably be the first issue that you should mark as a requirement for becoming the default theme :smile: Perhaps, we should open up an issue to discuss this further? As for your question, I would think that we would want to deprecate Bartik once Olivero is the default FE theme. Is the plan to deprecate Bartik once Olivero becomes default? We should triage them to see if there are issues that would be requirements for Olivero to be the default theme of Standard Some of them could be but presumably not all. Also, is the “Post-stable” criteria (see link - #3177296: Make Olivero stable) considered as the roadmap that will get the theme set as default? :thumbsup: so that’s what we’ll shoot That's good to know. That is a good guideline IMHO, there may be some possibility into beta of 9.2 but not sue. Getting to stable is usually easier than getting something the default experienceĭo we need to have it be the default by then to have it be the default for the 9.2 release? There could be different requirements for two of those milestones You might want to have separate steps for making it stable and making it the default Still a lot of work to do to be marked stable before 9.2, but it’s totally doable! We have until April or May to do so (someone correct me if I’m wrong) We’ve completed the second of what I consider to be our largest three milestonesacceptance of designCommit to core as betaMark as stable and make it the default To take a comment or thread off the record, start with a :no_entry_sign: emoji.0️⃣ 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ġ️⃣ Status and whats next (edited) mherchelĬONGRATS EVERYONE!!! :partyparrot: :partyparrot: :partyparrot: :partyparrot: :partyparrot: For anonymous comments, start with a :bust_in_silhouette: emoji. :star: The transcript of this meeting will be exported and posted to the agenda issue.the agenda is public and anyone can add to it:.there are about 5-10 minutes between topics for people who are multitasking to follow along.happens in threads so keep an eye on those notifications.
happens every Monday at 2pm GMT (10am ET). Meeting Location: #d9-theme channel on Meeting Minutes Hello, welcome to this week’s Front-end theme Olivero meeting!This meeting: Plan for moving Olivero issues to core: #3177364: Open Olivero issues should be moved to Drupal core's new "Olivero theme" component.