Port PM to Drupal 10

@pfolk,

Thanks for sharing the links. I had the opportunity to try out few of PM tools myself in the past year. The more I think about this, it feels like Drupal PM module could take an API first approach and have two modes. One, using gin admin theme where we do the most of "form oriented" operations and another with a decoupled frontend where we can have various views for our data... Gantt, Hierarchy list, Calendar, etc with basic operations to re-arrange them and change date. Going API first would allow for standard way of representing and handling the data which can be manipulated using various JavaScript library.

Making it API doesn't mean it is only available via API, but this is what I have in mind,

- we don't do any special "form validation", instead we put the constraints or validations on entities and bundle.
- we won't do any route based access, instead we implement Entity and Field access.
- Avoid dependencies on anything other than Drupal Core.
- Keep support for adding entity bundles and fields to extend the functionality

I have started pushing some code to 4.x branch, it is a rewrite from scratch. The focus is on getting base entity definitions correct and then build on top of it.

@joseph.olstad, ATM, I have kept support for Drupal 10 only. Looks like by the time we have a release, Drupal 10 should be mature enough. Maybe if its not too much of a trouble, we can have a Drupal 9 support as well once it usable. (While developing, I would like to avoid bug report surrounding 9/10 compatibility).

In parallel am also working on a decoupled UI for the project as well. This forces me to have a proper entity architecture to start with.

The code in 4.x would be highly volatile and a clean install might be needed between upgrades. So not not not recommended for any proper usage and hence not creating a release to avoid hurting anybody.

There would be a time when we bypass the feature set of burndown in 4.x. Until then, I am thinking of adding a link to https://www.drupal.org/project/burndown → in the main project homepage to help users make informed decision. Any thoughts?

@D34dMan - Exciting! I will do what I can to help/support. Will spin up a D10 test installation and install it when I have time. In the mean time if there is something specific you need feel free to ask.

As of today, 7.x branch will receive maintenance fixes only. All feature request against 7.x has been closed or moved to 4.x. The focus is now on Drupal 10 release (4.x). If you feel a closed issue is relevant for 4.x version of the project, please feel free to re-open and update the issue.

Update:

4.x-dev now has some basic entity structure in place. Am attaching a pdf 4.x-dev-20230227.pdf to give an idea where it is going. For now, am exclusively testing with gin admin theme → .

Previously, I had struggled with maintaining a demo site (the cost was just few hundred euro per year, but the time and effort to maintain it was distracting me a lot). Am open to ideas on how we can make this affordable and sustainable.

Attached wrong pdf in the previous comment... here we go.

For those interested in contributing to adding or using a Kanban board for Drupal PM (Project Management), I suggest we use this dedicated other PM ticket for Drupal 10 at https://www.drupal.org/project/pm/issues/3232552 ✨ Kanban Board Active

For those interested in contributing to adding or using a Sprints and Backlogs for Drupal PM (Project Management), I suggest we use this dedicated other PM ticket for Drupal 10 at https://www.drupal.org/project/pm/issues/607712 ✨ Sprints and Backlogs Postponed