Meeting will happen in #d10readiness on drupal.slack.com.
| Gábor Hojtsy (he/him) |
Suggested by @Kristen Pol (she/her) |
| Kristen Pol (she/her) |
It wasn't at an event but that part doesn't matter since the answer is probably the same |
| Gábor Hojtsy (he/him) |
I think the easiest to target is to look at any site you care about (you own, your company’s, your customer, etc) and look at the projects running there. Basically run Upgrade Status there. If you find bugs in Upgrade Status, that helps already :smile: Second, you can update the projects that already have updates, and make sure your site runs fine. Then look at the projects that are not yet compatible and look for their issues. |
| Kristen Pol (she/her) |
I'm just trying to point coworkers at useful contribution opportunities |
| Gábor Hojtsy (he/him) |
I think its best if there is a personal connection interest and a growth opportunity. |
| Gábor Hojtsy (he/him) |
Its easy to see the benefit of your site becoming better / more up to date :slightly_smiling_face: |
| Gábor Hojtsy (he/him) |
And there are tools to help you find the connection to where you can also contribute to the community at the same time. Upgrade Status makes this very explicit. |
| Kristen Pol (she/her) |
I was trying to steer him towards core issues that were discussed at the initiative meeting. There's plenty to do in contributed projects which he's doing |
| Kristen Pol (she/her) |
I guess it's just harder to pop into these core issues? |
| Gábor Hojtsy (he/him) |
Core issues are always on the move yeah. |
| Gábor Hojtsy (he/him) |
So its more like who is available then to discuss with, bounce ideas off on slack I think. |
| Gábor Hojtsy (he/him) |
When I had extra time, I went to the deprecated API removals issues, those usually were fine to do randomly or mostly verify when people were done with them, but those are done now. |
| Gábor Hojtsy (he/him) |
Its always easiest to find these “issues generator” areas, where the same pattern applies to various things, so you don’t need to invent a whole new thing. |
| andypost |
++ to deprecation, it's always challenging |
| andypost |
Also there's always phpcs and phpstan issues which is good starter |
| Kristen Pol (she/her) |
Thanks for the tips! I'll pass this along |
| Gábor Hojtsy (he/him) |
See the issue at #3118149: [meta] Requirements for tagging Drupal 10.0.0-beta1 |
| Björn Brala (bbrala) |
I'll stay on the deprecation track, next week I'm home again and will keep pushing a little. Although @Spokje seems to be the main engine with @longwave |
| andypost |
I will tackle remains of 8.2 test failures |
| longwave |
yeah i am primarily picking up module and theme deprecations |
| Björn Brala (bbrala) |
Looked at the meta issue, pretty big list :sweat_smile: |
| catch |
It is a long list, but apart from PHP 8.2 and ckeditor, most of the meta issues have one remaining issue on them, so it is looking pretty close overall I think. |
| dww |
Thanks so much @longwave for helping out with the QE contrib split! I’m gonna do a final round of testing, then merge that MR and tag another release (if all goes well) tomorrow. |
| catch |
RDF is very close to being possible to deprecate, but doesn't have a contrib maintainer yet. I think I saw a thread about this, but can't find it now. |
| catch |
Handful of issues that would allow us to take some things off the list:#3303787: Move core/modules/help_topics/config/optional/block.block.seven_help_search.yml to Seven |
Comments
Comment #2
gábor hojtsyComment #11
gábor hojtsySaving notes.
Comment #12
gábor hojtsy