- 🇨🇦Canada dylan donkersgoed London, Ontario
Hi,
We use this module for many of our intranets. I would like to become a maintainer so I can help get a version with D10 + Group 2.x/3.x compatibility out. I'm not sure how much time I can dedicate to maintaining it otherwise but since we do use this module on many sites I do have a stake in making sure critical bugs are fixed and the module stays compatible with new Drupal versions.
- 🇺🇸United States pcate
@bramtenhove, any update on adding Dylan as a maintainer?
- 🇺🇸United States caesius
If there is still interest in adding maintainers to this project then it would be best to follow the instructions here:
How to become project owner, maintainer, or co-maintainer →
Note that under the first header there's the following text:
If the owner does not reply after two weeks, move the issue to the Drupal.org project ownership issue queue, by changing the issue's Project field to Drupal.org project ownership. Please include a link to the project page.
Site moderators will normally try to contact the owner as an extra safeguard unless it is evident the owner is no longer active in the Drupal community, giving to the contacted users two weeks for replying to the message they sent via the Contact tab. I have created the 2.x version of this module which is compatible with Group 2
https://github.com/naveenvalecha/gcontent_moderation/tree/2.2.xI can offer to co-maintain the project as I have got a budget from a customer who is using this module. I will use the time to improve this module.
I'm going to contact the current maintainers( https://www.drupal.org/u/jaapjan → , https://www.drupal.org/u/hernani → , and https://www.drupal.org/u/bramtenhove → ) for the co-maintainership
I have contacted @jaapjan( https://www.drupal.org/u/jaapjan → ), @hernani( https://www.drupal.org/u/hernani → ), and @bramtenhove( https://www.drupal.org/u/bramtenhove → ) via their contact form for co-maintainership
- 🇮🇳India shashank5563 New Delhi
@bramtenhove, I am ready make it fully Drupal 10 compatible.
Because, I have done it one of my project today and it is working as expcted. I have not received a response from the maintainers I contacted in #note-6 after two weeks. I'm moving this to the project ownership queue.
- 🇳🇴Norway gisle Norway
This post was created by bramtenhove, and includes this promise:
Anyone that wants to be added as maintainer can report here and they will be added.
That's fine, bramtenhove is a maintainer and he can add whoever he wants to the team.
In comment #4, it is linked to this page: How to become project owner, maintainer, or co-maintainer → with a quote suggesting that any offer to maintain will be processed by the site moderators if the project owner does not respond.after two weeks.
This is taken out of context. The site moderators will help adding new members to the team if an offer to maintain is not responded to by the project owner or any of the project's maintainer in a timely manner. However, this requires the offer to maintain to be created as a new issue by the person offering to maintain. Offers to maintain created en passant in some issue created by someone else will not be processed by the site moderators.
I am moving this back to Group Content Moderation for bramtenhove to deal with (as said in the issue summary), since there is nothing for the site moderators to do here.
If you are interested in getting help from the site moderators to be added to the project's team, please read this page: How to become project owner, maintainer, or co-maintainer → very carefully before creating your offer to maintain.
@gisle,
Thanks for the updates! I have reached out to @bramtenhove in #note-6 but didn't get any update. I'll create a separate issue to offer the maintainer-ship offer.
It should be noted that Group Content Moderation version 1.0.0-beta3 is upgraded to Drupal 10, so the project does not appear to be abandoned. The main role of the site moderators is to add new maintainers to abandoned projects. If the project has a functioning team, we prefer for the team to manage itself.
Group module( https://www.drupal.org/project/group → ) has 1.x, 2.x, and 3.x The Group Content Moderation version 1.0.0-beta3 is compatible with Group 1.x and Drupal 10. I'm after the the support of Group Content Moderation with Group 2.x and Group 3.x version. Details are in these issue 💬 Is group content moderation module compatible with Groups 2.0.0-beta3? Needs work and 📌 Make compatible with Group 3.x Active
- 🇮🇹Italy apaderno Brescia, 🇮🇹
Should not this issue be closed as outdated?
It has been opened on 2021, but none of the people who commented here to be added as co-maintainer was effectively added; even the last person who offered to become co-maintainer had to create a separate issue to be effectively added as co-maintainer. (That means he had to follow the usual way to become co-maintainer and this issue did not offer a "shortcut" to be added as co-maintainer.) - 🇮🇳India shashank5563 New Delhi
@bramtenhove, I am ready make it fully compatible with Group 3.x.
Because, I have done it one of my project today and it is working as expected.Please give me permission to update the module.
@shashank5563 It's compatible with 3.0.x branch Please help testing https://www.drupal.org/project/gcontent_moderation/releases/3.0.x-dev →
// Naveen
- 🇮🇳India shashank5563 New Delhi
@naveenvalecha, I have tested with Group 3.x module, and found it is working as expected.
Please raised the released version of 3.0.x.Thanks
@shashank5563
Thanks for testing the 3.0.x dev branch
There's an open bug which needs to be fixed for 3.0.x https://www.drupal.org/project/gcontent_moderation/issues/3398885 🐛 Fixes LatestRevisionCheck access logic Needs work
I'll roll out the stable release after the above gets fixed- 🇺🇸United States JI_Gravityworks
Hello! We are definitely going to need this for one of our clients, so I'm following this thread. I'll be using 3.0.x and will provide feedback as I go.
Thanks for taking the initiative on this!