Skip to content

Conversation

@felixarntz
Copy link
Member

This PR adds a REQUIREMENTS.md, outlining the overall objective for this project, as well as its key requirements. For easier consumption as Markdown, see the file in the branch.

It also adds a GLOSSARY.md with common terms, which can be helpful to align communication and discussion.

@@ -0,0 +1,101 @@
# Requirements
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: could also list some constraints such as PHP version requirements

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like for this to be only focused on functional requirements for the project, so that ideally it can be evergreen. Just clarified that in the description.

You raise an important point though, we also need to define a few technical requirements like PHP version support. I just opened #3 for that.

@felixarntz felixarntz added [Type] Developer Documentation Documentation for developers and removed documentation labels Jun 18, 2025
@felixarntz felixarntz merged commit 2bcbf9d into trunk Jun 20, 2025
@felixarntz felixarntz deleted the add/requirements-definition branch June 30, 2025 21:21
@jeffpaul jeffpaul added this to the 0.1.0 milestone Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Developer Documentation Documentation for developers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants