D8 Rules MVP

Thanks for your proposal! It would be interesting to double check how by this approach we the milestone 3 or beta blocker tasks could be re-prioritized. #2245015: [META] Rules 8.x Roadmap

I suggest to add a third step:

* Provide basic documentation for site builders (non coders).

This issue has been open for almost two years now. It hasn't proven useful in guiding development, mainly because there has been virtually no community participation in D8 development over those years. I haven't found it useful to have a dozen different "planning" type issues open with no planning going on, so I am closing this. But let me address some of the points here first.

Both "Step 1" and "Step 2" have been finished since before this issue was opened! Tests especially - there have always been automated tests for everything, and we have required new tests for every new feature that has been added and for every bug that has been fixed.

The use case in comment #4 has also worked since before this issue was opened, but there has since been a complete example posted in the issue queue and in the rules_examples module of how to do this. See #3059008-4: Add role to user

The main remaining weaknesses are 1) documentation, and 2) UI. A lot of progress has been made on both since this issue was opened.

The issues that need to be resolved for a beta release are tagged "beta blocker", and we've made great progress on those since this issue was opened. There are only a few beta blockers left. Conceivably these could be easily closed out within a month if there were people working on them, but it will take much longer for me to do all those myself.

The issues that need to be resolved for a fixed-point release are tagged "release blocker", and although there is some leeway on what is included in that category I think it's easier and more efficient to just fix those issues than to spend time talking about what should be on that list.

How can anyone help?

1. Answer support questions in the issue queue, on slack, on stackexchange, etc.
2. Write documentation. Correct documentation. Make videos, add screenshots to the documentation, etc.
3. Review issues.
4. Submit patches.
5. Work on other contributed modules that need help with Rules integration.
6. Fund development. This includes Drupalcon attendance, which would allow the maintainers to give talks, direct code sprints, and co-ordinate development.

I am happy to discuss, in the issue queue, what needs to be done for any particular issue, and I am happy to mentor any contributors who want to help.

Over the past two years Rules has been one of the MOST active and BEST supported projects on drupal.org. If you encounter a post that says otherwise, let them know they're wrong - the facts prove it. Yes, Rules went through a low point for a few years a while back, but that time is long past and there's been a impressive record of accomplishments over the past two years that I will gladly compare to any other project. As just one example, when I started maintaining this project almost two years ago there were something like 540 bugs open. Over the past 2 years there have been an additional ~200 bugs opened. Out of those total ~740 bugs, more than 600 have been fixed (or otherwise closed as duplicates etc.), leaving us with only 130 bugs today (and only ~20 of those are in D8!) This from a 100% volunteer part-time effort with no financial or company support ... basically no support at all from a community of >250,000 users ...

So what we need is people DOING things, not so much talking about those things. Although I do spend IMO an excessive amount of time documenting in the issue queue all the things I'm doing, I do that mainly for my own benefit, to have a record of what things were done and why they were done - I almost never get a comment or feedback about any of that.

tq TR