Contrib.social

Offering to co-maintain the module

Open on Drupal.org →
Created on 21 February 2025, 3 months ago

Problem/Motivation

It came up in 📌 Add destination query parameter to duplicate operation link Active so here is a separate issue to properly discuss it: I would like to offer to co-maintain the module. I am still pursuing the goal of reducing boilerplate of custom entity types in particular (but not limited to) the UI scaffolding and I see this module as a great vessel to achieve that. The long-term goal of upstreaming everything into core has - from my very personal point of view - become more and more theoretical given the slow development pace and not always very productive but often very lengthy discussions in core at the very least when it comes to these things. So while I will always still push things in core where I do see an opportunity for movement, I would like Entity API to become a more powerful tool belt for people with custom entity types and (unfortunately or not) I personally don't see that need going away anytime soon.

Not sure in how far that aligns with the vision of the current maintainers and, in fact, I'm not quite sure who would actually be the set of current maintainers, but, yeah, pretty much willing to hop on board under whatever terms are deemed best by the current maintainers if that means I can take some steps towards the goals stated above.

Steps to reproduce

-

Proposed resolution

Make tstoeckler a maintainer. ;-)

Remaining tasks

User interface changes

-

API changes

-

Data model changes

-

📌 Task
Status

Active

Version

1.0

Component

Core integration

Created by

🇩🇪Germany tstoeckler Essen, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tstoeckler
  • Comment 3 months ago →
    🇨🇭Switzerland berdir Switzerland

    Added you with full maintainer rights.

  • Comment 3 months ago →
    🇩🇪Germany tstoeckler Essen, Germany

    Oh, wow, thanks very much!

  • Comment 3 months ago →
    🇨🇭Switzerland berdir Switzerland

    Thank you.

    For the record, I'd also fully support it if you want to become a core entity API and improve some things there. I think you're more than qualified to do that. I've actually been able to make _some_ improvements recently, such as $entity->getOriginal(), the duplicate hook, entity attributes finally landed in 11.1 and so on. The way to get past endless circular discussions is to have more maintainers.

    And I'd love to get reviews on some of of my issues (such as 🐛 Disallow saving the current default revision as a non-default revision Active ).

  • Comment 2 months ago →
    🇩🇪Germany tstoeckler Essen, Germany

    Not exactly sure what you mean, per your endorsement I was → a core Entity API maintainer for quite a number of years but then stepped down 📌 Remove tstoeckler from MAINTAINERS.txt Fixed a while back in part due to just being less involved in general, but in part also because of the slow traction of even seemingly simple issues and also me not agreeing with the some of the focus/direction that things are headed in. Neither of those things have changed, so going back to being a maintainer is not really in question for me right now.

  • Comment about 2 months ago →
    System Message

    Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024