Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
G
gargantext-rfc
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
gargantext
gargantext-rfc
Commits
d2b76e45
Commit
d2b76e45
authored
Feb 21, 2019
by
Alexandre Delanoë
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[README] dysfun explanation of how using this RFC repo, copy/pasted from IRC.
parents
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
18 additions
and
0 deletions
+18
-0
README.md
README.md
+18
-0
No files found.
README.md
0 → 100644
View file @
d2b76e45
# HOW TO USE THIS RFC REPO
All major structural changes to Gargantext code base (Backend and
Frontend) go through an RFC, a request for comment, much like IETF
standards for the internet
These are actually stored as documents in a repo (in markdown iirc).
Adding a feature to Gargantext typically starts with filing an issue to
discuss it.
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
through discussion, eventually a satisfactory text is arrived at PR is
merged feature can then be written.
## Credits
-
thanks to dysfun for this idea of RFC repo (stolen from Rust-RFC ;)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment