Skip to content

G
gargantext-rfc
Commit 4a5fa3a1 authored by Alexandre Delanoë's avatar Alexandre Delanoë
Browse files
Options

[COSMETICS] minor change to readme.

parent d2b76e45
Hide whitespace changes
Inline Side-by-side
Showing with 4 additions and 4 deletions
README.md
View file @ 4a5fa3a1
...@@ -2,11 +2,11 @@ ...@@ -2,11 +2,11 @@
All major structural changes to Gargantext code base (Backend and All major structural changes to Gargantext code base (Backend and
Frontend) go through an RFC, a request for comment, much like IETF Frontend) go through an RFC, a request for comment, much like IETF
standards for the internet standards for the internet.
These are actually stored as documents in a repo (in markdown iirc). These are actually stored as documents in a repository (format to be
Adding a feature to Gargantext typically starts with filing an issue to decided). Adding a feature to Gargantext typically starts with filing
discuss it. an issue to discuss it.
If it's not decided it's a bad idea, the originator will typically If it's not decided it's a bad idea, the originator will typically
create a PR to add a formal specification for the feature to the repo create a PR to add a formal specification for the feature to the repo
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment