Add a paragraph about attribute takeover

[heiglandreas]

It mmight happen that already existing attributes shall be taken over by the FIG to allow greater reach or provide better maintenance. This is in general something that we allow and already thought about. Such attributes can be published on one central page to make people more aware of them once the process has been started of taking the attribute over.

[jrfnl]

Is this really an issue ? Wouldn't attributes which would be "taken over"/adopted by the FIG project automatically get the Fig\Attributes namespace, making them essentially a different attribute anyway ?

If the namespace would not change to Fig\Attributes, I think it would be prudent to define a procedure around this, i.e. will the namespace change ? if so, when will the namespace change (next major) ? will there be an alias to the old namespace ? and if so, for how long ? etc etc

[heiglandreas]

The namespace will change! But depending on how long it'll take people might want to impmement it right now.

When the taken over attribute then extends the new fig one implementations will still work, so people can use it immediately.

[jaapio]

Maybe a heading would give it a bit more attention?

[Crell]

I'm not sure this needs a call out at this point. Any new attribute we include would be in this repo, in our namespace, and may or may not be identical to something that previously exists. So from the POV of our downstreams, there's no difference.

If we do end up with attributes that are heavily inspired or cloned from some existing use case, we can add a document or section or something for it at that time, as a courtesy. But I don't think it needs a formal call out at this point.