Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider deprecating metainfo.creator #193

Open
benkiel opened this issue Sep 29, 2021 · 1 comment
Open

Consider deprecating metainfo.creator #193

benkiel opened this issue Sep 29, 2021 · 1 comment

Comments

@benkiel
Copy link
Contributor

benkiel commented Sep 29, 2021

See discussion in #192. This is now optional, it may not have value or a clear "what counts as a creator when a tool may just touch a subset of a UFO" anymore.

Discuss pro/con below

@madig
Copy link
Contributor

madig commented Sep 30, 2021

I suppose there are three use-cases:

  1. A tool saves a fresh UFO (different location or by erasing the existing UFO completely)
  2. A tool saves a subset of a UFO
  3. A tool just reformats a UFO partially or completely, potentially rewriting some data (e.g. floating point precision)

For case 1, the creator is obviously the tool. For case 2, I don't think there can be a clear answer. Maybe the field degrades to "creator of the initial UFO", whatever that means? For 3. I suppose the creator can stay unchanged if all the tool changes is whitespace. For rewritten data, we are potentially back at case 2...

One hard-and-fast rule that somewhat makes sense is to have whatever tool last touched the UFO in any way have set itself as the creator, making it more like a lastModifiedBy.

Another is to only change the field when writing out the metainfo.plist file. So creator would be "last tool to write this UFO out fresh".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants