Stream: fmg
Topic: Name change
Grahame Grieve (Dec 20 2019 at 20:15):
One of the committees has decided to change the name of an IG without discussing with either me or FMG. The name change has landed on @Lynn Laakso with no warning, and the publishing framework has no support for this (you can't change the canonical URL, or at least doing so is endlessly painful)
@Eric Haas can you please describe the history of this
Riki Merrick (Dec 20 2019 at 21:19):
This IG started out under CDS with the name "Alerts" - after review by several WG and FMG, it was felt that the IG is creating a pattern and thus should be sponsored by a methodology WG - so the sponsoring WG changed from CDS to INM, which resulted in a chnage in Steering Division. If I remember correctly it was during discussion at the SD that there was a strong feeling about changing alert to notification, as alert has a specific meaning to many people (from a device to medical personel), which is NOT what this IG is doing. So we agreed to change the name. I did not realize that that would result in a tooling issue - so my bad to not bing this up any sooner. I can offer to revert the name back to alerts for this ballot (though we don't have a WG call anymore to officially vote on this before the ballot opens) and then submit a ballot comment that it should be renamed to notifications - OR we can make a note to balloters, that we are aware of this issue, but due to tooling cannot change it at the moment?
Grahame Grieve (Dec 20 2019 at 21:25):
I can make this work (we've done it before moving from us to uv) but it means I publish and spend a couple of hours moving tings around by hand, and maintain this going forward.
Also, the name as it was was approved by FMG and comes out of a unique space, so I think that FMG should approve name changes like this.
Given this, I don't think that it's practical to deal with a name change right now
Riki Merrick (Dec 20 2019 at 21:27):
So should we add a note to balloters regarding that and revert the title back to alerts?
Grahame Grieve (Dec 20 2019 at 21:38):
I think so, but I'm looking for wider comment from FMG members
Lloyd McKenzie (Dec 20 2019 at 23:27):
Agree it's something that should come to the FMG, but it's also something we haven't announced as policy previously. Is this a publication request or a ballot request? For the latter, old name is best. For a publication request, it's more problematic.
Riki Merrick (Dec 20 2019 at 23:33):
It's for the DaVinci Alert ballot - so I will change the title back and add a note to balloters - ok?
Eric Haas (Dec 21 2019 at 00:11):
Can we just move the canonical base back to alerts, Just like with Grahame it is a much bigger task for me to update every name and resource id from Alerts to Notifications? I could call the title:
...Notifications (aka Alerts)...
But we have been calling it Notifications since September, which will lead to mass confusion and make us look bush league.
TSC approved the name change BTW and this is something that came up before in other iGs like DEQM at the beginning... Changing names is something we are prone to doing ... maybe we need a clear policy that the canonical and npm are forever etched in stone once you name it.
Riki Merrick (Dec 21 2019 at 00:14):
You are the main author - so barring opposition from Grahame, I am fine with whatever you decide.
Eric Haas (Dec 21 2019 at 00:20):
Then there is the issue of an orphaned or Zombie Sept 2019 Ballot publication. It got pulled from ballot after we published it. ( I don't have a first hand history of those events and obviously if i knew what was brewing we would not have published it.)
I think the best options here is i can add the a description with Deprecated in big bold letters in the ig-list.json for this version.
Grahame Grieve (Dec 21 2019 at 01:18):
I don't care what the human readable title is - call it whatever you want based on TSC agreement. What I care about is the canonical URL and package id
Grahame Grieve (Dec 21 2019 at 01:19):
that can't change without specific manual work (each time is published ongoing) for me. And since the components of these are agreed by FMG out of a unique space, changes to these very much need FMG approval
David Hay (Dec 21 2019 at 04:50):
definitely a note to balloters - minimize the changes at this point!
Eric Haas (Dec 21 2019 at 15:14):
OK I'll let Lynn know when I've made the changes.. thanks.
John Moehrke (Dec 23 2019 at 14:34):
I recall that we (FMG) asked for this name change when we approved it... but that doesn't help the current problem.
Last updated: Apr 12 2022 at 19:14 UTC
