FEP-1b12: Group federation

[silverpill]

@SorteKanin

If we go with the boolean approach, the change would not even be breaking.

Depends on how this requirement will be specified. If it is something like “…MAY add a property to Group actor”, it can be added:

A proposal with status FINAL can not be changed or updated in a way that would lead to adjustments to implementations. Minor corrections are allowed.

But I think it would be better to publish a revised version of this FEP, because it is not up to date. For example, it describes audience field, which is not used by Lemmy anymore.

@SorteKanin

Why aren’t FEPs versioned with semantic versioning, for instance? Then we could use 1.0.0 instead of “FINAL” and this extra enhancement on top could be version 1.1.0.

FINAL is supposed to be a signal that FEP is safe to implement. A new FEP can easily be published if changes are necessary, so there is no need for 2.0 versions.