[meta] D8 release roadmap

I'm trying to figure out how to expose permissions from other modules. It doesn't look like you have any hooks that I can use to create a submodule.

- I want to add the ability for Admins to manage their own menus or add other permissions from other modules. Do you have a tutorial on how to extend this module or point me in the right direction to do this?
- Are these permissions within the module separate from the Drupal core permissions or are you hooking into those somehow?

Have you planned email invitation as in drupal version 8. And the possibility for a group to accept or reject an application to join?

I think you should have Documentation as a blocker for release. At a minimum, you should have a README to tell a system administrator how to setup the module. The YouTube video links in the additional resources are for a version of the module over a year ago, the module has changed and those are not 100% applicable.

In my opinion this is a blocker also:

#2842630: Empty page when trying to create group node

Any idea on whether #2752603: Request Membership feature should be part of this roadmap?

In #6 kristiaanvandeneynde said:

All in all, the idea is good. I definitely want to see this land before a 1.0 is released.

Also note that in #2718195-40: Add a computed field for entity's group(s) a group selector widget has gotten low hanging fruit. ;-)

I'd like to advocate for getting #2829966: Support for Revisions on groups in the mix here. Seems like revisions should have been considered out of the box as a core competency. Revisions should be baked into everything that relates to or behaves like content, especially as core introduces stable Workflows and Layout Builder modules. Being able to track changes made to a group and its content seems like critical (8.1) functionality to me, but happily settle for seeing it at least in the roadmap for 8.2?

+1 for Revisions.

+1 for Revisions.

Are you talking about config entities needing revisioning support? If so, I have created a module "Config Entity Revisions" that implements an API module for revisioning content entities. I started with support for Webforms, and am currently doing a big rewrite / cleanup as part of implementing support for Views. I'll happily support Groups too if that will help you.

Hi NigelCunningham,

The group entity type is a Content entity type, so your module is not applicable in this case.

Now #2829966: Support for Revisions on groups is ready for review and it was splitted in three child issues to make it easier to review.

Great; thanks!

Thanks, this is exciting progress!

Curious if/where you see #2813405: Add a field to view and edit content's groups fitting into this roadmap. @axel.rutz mentioned #2718195: Add a computed field for entity's group(s) in #38 but that's now duplicate and merged into the work at #2813405. This seems like a really important and useful feature. Any chance we could try to get that in before 8.x-1.0 final?

Have attached (IMO critical) bug #3061321: Uncaught exception in Nodes and Members tabs in rc3, which breaks Group displays on sites with existing content.

Re: #49: Okay, fair enough. Let me know if this is out of scope and we should discuss this elsewhere...

The latest patch for #2813405: Add a field to view and edit content's groups is about 98% a whole new sub module. So I don't see any BC-break or API change issues. The only real "API changes" as such are in:
src/Form/GroupSettingsForm.php (injects the moduleHandler service and implements a constructor and create() method).
src/Plugin/GroupContentEnablerManagerInterface.php (adds a new method: public function getPluginIdByEntityType()).
src/Plugin/GroupContentEnablerManager.php (implements the new getPluginIdByEntityType() method).

It would be really nice to have this working in the 8.x-1.x series. Looks like you're going to need another RC, anyway. Any chance you'd be willing to get this into the RC so we don't have to worry about the API changes to the main module listed above?

Thoughts?

Thanks!
-Derek

I think #2752603: Request Membership feature is the only outstanding item remaining on this issue. Does that sound right to anyone else or are there lurking issues not tagged to this meta that also need to land?

I think #2771065: Group Node: Only authors should be able to create Gnodes for their nodes needs to be done to prevent node authors from loosing access to their nodes.

@heddn I still think #2813405: Add a field to view and edit content's groups could be somewhere on the plan. ;)

Also, the summary is making interesting use of semver-esque versions, but this project is still using BespokeVer (8.x-Y.Z) version numbers. Please note that Y in the above maps to SemVer Major and Z maps to Minor. So "Differentiate between 8.1.1 and 8.2.x" is a kinda wonky way to express things.

We should consider if it makes sense to actually move to semver for this project, now that that's supported. If so, the official release would actually be "2.0.0", and then we'd be differentiating between "2.0.x patch-level bug fixes vs. 2.1.x minor-level new features vs. 3.0.x API-breaking changes".

If not, we'd probably benefit from being more specific and accurate in the summary. E.g. "Differentiate between 8.x-1.1 and 8.x-2.x".

Thanks,
-Derek

Since #2813405: Add a field to view and edit content's groups has been moved to a separate submodule, couldn't you build an official 8.1 release now? Is there anything missing here?