The general idea here is to finally make Field Groups a native feature, but when doing so:

• Make Field Groups native, to be managed from UI via API's
• Introduce Field Groups permissions (content/read and content/edit / content/create? )
• TBD: Make sure one content type can reuse a group from another one
  • Use this to help force content modeling cleanup