Add project goals/roadmap.

Author: ThomasFrans

CONTRIBUTING.md

@@ -0,0 +1,6 @@
+Contributions of any kind are welcome. The current guidelines are listed below.
+
+## Guidelines
+- It is best to open an issue before adding new features to ask for input.
+- Adhere to the project style. Style enforced by CI is mandatory and violations won't be accepted.
+  For other filetypes, use common sense and follow the current style as much as possible.

GOALS.md

@@ -0,0 +1,37 @@
+# Project Goals
+I believe strongly in being verbose about the goals and long term roadmap of a project. The goals
+below should stay the same in the future. New ones that are compatible with the current ones can be
+added.
+
+# Goals
+- Strictly follow [semantic versioning 2.0.0](https://semver.org/spec/v2.0.0.html).
+- Dependencies should only be added if they provide considerable benefit.
+- Depencencies should be maintained at the point in time they are added.
+- Filetypes with available formatting tools are checked for style by CI. Code that doesn't follow
+  this style is rejected. This keeps the codebase clean and nice for everyone to work on.
+- Correctness of the code, both in the sense of the code doing what it is supposed to do, and in the
+  sense of the library following the specifications that are listed in the goals.
+
+## Before 1.0.0
+- Refine/reconsider the public API so it can become stable.
+- Add tests to the public API to avoid breaking changes.
+- Aim for a first release. I don't want this project to stay in 'unstable limbo' indefinitely. This
+  doesn't mean the first release will be rushed, but having a first major release and stabilizing
+  the public API is a goal.
+
+# Other Goals
+> These goals are hard to formally write down or check.
+- After the first major release, extra care has to be taken to prevent breaking changes to the
+  public API.
+- Follow [the Rust API Design
+  Guidelines](https://rust-lang.github.io/api-guidelines/checklist.html).
+- The flexbox implementation tries to adhere to the [CSS3 flexbox
+  specification](https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/) where it makes sense in a
+  TUI context.
+
+# Non-goals
+> Things that aren't goals right now and arent considered to become goals in the near future.
+- Optimize for performance. While the library should be performant and I try to make things go fast,
+  it is not a main goal of this project.
+- Optimize for memory usage. The dependency limitation goal should keep memory usage low, but low
+  memory usage is not a main goal.

README.md

@@ -1,13 +1,8 @@
 # Cursive Flexbox ![Maintenance](https://img.shields.io/maintenance/yes/2023?style=flat-square) [![crates.io](https://img.shields.io/badge/crates.io-cursive--flexbox-brightgreen.svg?style=flat-square)](https://crates.io/crates/cursive-flexbox) [![docs.rs](https://img.shields.io/badge/docs.rs-cursive--flexbox-brightgreen.svg?style=flat-square)](https://docs.rs/cursive-flexbox/latest/cursive_flexbox/)
-> This library is not stable yet. It is under development and the API will change before the first
-> release. Starting from major version 1 (1.x.x), this library can be considered stable and
-> generally usable.
-
 A correct, complete flexbox implementation for the [Cursive TUI
-library](https://github.com/gyscos/cursive). The implementation follows the CSS3 specification where
-it makes sense for a TUI. All implemented functionality should be exactly the same as for the CSS3
-flexbox.
+library](https://github.com/gyscos/cursive). The implementation follows [the CSS3
+specification](https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/) where it makes sense for a
+TUI. All implemented functionality should be exactly the same as for the CSS3 flexbox.
 
-## Contributions
-Contributions are very much welcome. Keep in mind that the project just started so there isn't much
-implemented yet.
+- [Project Goals](GOALS.md)
+- [Contributing](CONTRIBUTING.md)