Add the JS modernization initiative to MAINTAINERS.txt

➕1️⃣ for @justafish

Additionally, I'm good with this, and accept the responsibility. ✌️

+1!

👍 🎉

+++ b/core/MAINTAINERS.txt
@@ -479,6 +479,10 @@ API-first Initiative
+JavaScript Framework Initiative

Is it possible to generalize this, maybe? Something like Drupal JavaScript Initiatives?

FWIW, my $0.02 is that for initiatives, more specific/focused is better. So I propose renaming to "React initiative" (since that's the chosen library) or "Reactive admin UIs initiative" (if we want to focus on the product benefit rather than the technology).

For reflecting other JS work in Drupal, we already have a "JavaScript" subsystem in MAINTAINERS.txt. But if we want initiatives for certain efforts (e.g., ES6), what about proposing those as separate initiatives?

+1 to "JavaScript Modernization Initiative". I'm also happy to defer the final choice of name to @drpal, @justafish, and @Dries.

@xjm asked me to explain why I dislike the term "React initiative".

a) React is not a self-goal, as in, the value is not in react, its in having a better user experience, better integration with modern JS etc.
b) The hard problems will not be in using react, it will probably be in the integration with PHP, and the general problem space of having modules inside the more full control JS world. Other problems will be defining a component library for example. Nothing is intrinsic a react problem.

+1 for JavaScript Modernisation Initiative

@justafish s or z? Either way, ➕1️⃣ from me.

Initiative name change per #12, but with a "z".

Also, signing off on this as framework manager.

@drpal asked me to join the team as an initiative coordinator, to handle communication-style tasks in order to free up he and @justafish and others to rock out on JS, and just wanted to leave a note here that I'm both honoured to be asked and happy to play this role. :)

This was blocked on having an initiative coordinator (based on conversations with all core committers, drpl and justafish). Big +1 for the drpl + justafish + webchick combination. I'm excited to see this move forward! Feel free to commit and updated version of this patch.

Here it is.
I've added @webchick

Thank you, @ApacheEx! :)

From a product management POV, I guess one thing we want to ensure isn't lost is that the end goal of this initiative isn't to modernize Drupal's JavaScript, nor is it to ship Drupal with React. It's rather to do those things in service of utilizing the kinds of interactive interactions provided by a JS library like React for the purpose of making Drupal administration easier to use.

However, as we were discussing in UX meeting today, we don't yet have a real clear idea of what that "end game" looks like. #2902399: Redesign the Admin UI is the closest place we have for a brainstorming place on this, so we can continue to discuss over there in the coming weeks.

This should not hold up the initiative from kicking off, though, since there's quite a lot of "foundational" things on the plate listed at #2926656: [plan] Modernize Drupal's JavaScript. Just a general plea to keep the end goal in mind throughout. :)

Not marking RTBC yet, since framework manager review tag is still on it, but removing ours.

@Cottser +1'd this in #4, so I think we can remove the "Needs frontend framework manager review" tag now.

Well all righty then!

haha did not see that one go through.