Could someone please decrypt "NRVE"? Thanks a lot! :)

@Aklapper Sorry, it's 'Named References in VE,' which is one of the wishes from the 2019 Wishlist. We have not launched the project yet, but we are beginning the early stages of planning & investigation. Sorry for the cryptic name!

@Prtksxna I discussed these mockups with @Mooeypoo today. In particular, we discussed the ability to edit auto-generated reference names in VE. Unfortunately, there are some technical issues. The technical work to allow such behavior would be complex and substantial; the engineers have advised against it. Most likely, it would be very time-consuming for the team. For this reason, we may need to steer clear of allowing the editing of reference names in VE. If users want to edit or change the reference names, they'll be able to do that in source editing. We should discuss this in greater detail, so I'll schedule a meeting for us to talk about it together. Thanks!

Sorry, it's 'Named References in VE,' which is one of the wishes from the 2019 Wishlist. We have not launched the project yet, but we are beginning the early stages of planning & investigation. --ifried, Feb 26 2020, 2:14 PM

@ifried: For the record, also appears to be one of the wishes from the 2017 wish list, with unanimous support. Is there an update on the status?

@Mathglot Hello! I am no longer on the Community Tech team. Questions about the status of the work can directed to the team product manager, @NRodriguez. Thanks!

@NRodriguez can you explain what the status ‘ Open, Needs Triage’ listed at the top means, and what the next steps are?

@Mathglot: See https://www.mediawiki.org/wiki/Bug_management/Development_prioritization and https://www.mediawiki.org/wiki/Bug_management/Bug_report_life_cycle - thanks! (Also note that this task is only about design topics; not for general inqueries)

Removing the Community-Tech tag - we have reprioritized our work based on a new scoring process, and are in the process of cleaning up our backlog to provide a more accurate view of our focus areas this year.
For additional background, see the status report for 2019 wishlist. cc @NRodriguez

I did some fiddling with this at the last hackathon, and found that it was surprisingly painful to get the internallist to change the name of a reference after it was created, for structural reasons. There's been a bunch of refactoring of Cite + the internallist in the ~6 months since then because of WMDE's subreferences work, so I should check whether that still holds true.

That said, insofar as changing the name was the problem, I should dig up that code and see how simple it is to just restrict it to setting the name on initial creation.

(Supporting changing the name of a reference is also probably gated behind T405155 (or similar), because we'd want to be able to detect if we're going to break references reused inside a template by changing the name. I don't think we're going to be able to support making that edit to the reference-in-the-template, but at a minimum we should be able to grey out the input or suchlike in order to stop a user from breaking things inadvertently.)