diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
deleted file mode 100644
index 1c4a239f06d1cabc4fa3c29d2b44fd285c58ba36..0000000000000000000000000000000000000000
--- a/.github/CONTRIBUTING.md
+++ /dev/null
@@ -1,10 +0,0 @@
-This project is now tracked on our hosted gitlab server at:
-https://git.duniter.org/nodes/common/dips
-
-The current github repository is a simple clone taken up to date at each push on the main gitlab repository.
-
-All contributions should be performed on the main gitlab repository.
-
-Pull requests proposed on github would generate more work for the main contributors.
-
-Issues can be submitted on github. However, all issues created on github will be duplicated on gitlab manually and closed with a link to the gitlab issue.
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index b55a807ac4b90d78bab4b4bf5cf17aca32b333b6..0000000000000000000000000000000000000000
--- a/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Please note that all issues should be preferentially opened at
-https://git.duniter.org/nodes/common/dips/issues/new?issue
-
-If you open issue here, it will be duplicated manually on our hosted gitlab and closed here with a link to our main repository.
-
-Thank you for your understanding.
\ No newline at end of file
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 32f686d1088f1867a8d136740ec65cba998a6887..0000000000000000000000000000000000000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,10 +0,0 @@
-This project is now tracked on our hosted gitlab server at:
-https://git.duniter.org/nodes/common/dips
-
-The current github repository is a simple clone taken up to date at each push on the main gitlab repository.
-
-All contributions should be performed on the main gitlab repository.
-
-Pull requests proposed on github would generate more work for the main contributors, therefore we would really appreciate if you can create instead merge requests on our hosted gitlab instance.
-
-Thank you for your understanding.
\ No newline at end of file
diff --git a/.github/github_disclaimer.md b/.github/github_disclaimer.md
deleted file mode 100644
index 03a51826d958b5f4a520209d36e8caf53ff85534..0000000000000000000000000000000000000000
--- a/.github/github_disclaimer.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Initial disclaimer
-This project is now tracked on our hosted gitlab server at:
-https://git.duniter.org/nodes/common/dips
-
-The current github repository is a simple clone taken up to date at each push on the main gitlab repository.
-
-All contributions should be performed on the main gitlab repository.
-
-Pull requests proposed on github would generate more work for the main contributors.
-
-Issues can be submitted on github. However, all issues created on github will be duplicated on gitlab manually and closed with a link to the gitlab issue.
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
deleted file mode 100644
index 0f7e73375ea39d8c1ddd00be3e35b433a5cb22a8..0000000000000000000000000000000000000000
--- a/.gitlab-ci.yml
+++ /dev/null
@@ -1,39 +0,0 @@
-stages:
- - github-sync
-
-push_to_github:
- stage: github-sync
- variables:
- GIT_STRATEGY: none
- tags:
- - github
- script:
- - rm -rf ./*
- - rm -rf .git
- - git clone --mirror $CI_REPOSITORY_URL .
- - git remote add github $GITHUB_URL_AND_KEY
- - git config --global user.email "contact@duniter.org"
- - git config --global user.name "Duniter"
- # Job would fail if we don't remove refs about pull requests
- - bash -c "cat packed-refs | grep -v 'refs/pull' > packed-refs-new; echo 'Removed pull refs.'"
- - mv packed-refs-new packed-refs
- - bash -c "git push --force --mirror github 2>&1 | grep -v duniter-gitlab; echo $?"
-
-enforce_readme:
- stage: github-sync
- variables:
- GIT_STRATEGY: none
- tags:
- - github
- script:
- - rm -rf ./*
- - rm -rf .git
- - git clone $GITHUB_URL_AND_KEY .
- - git config --global user.email "contact@duniter.org"
- - git config --global user.name "Duniter"
- - git checkout master
- - cat .github/github_disclaimer.md > README.md.new
- - cat README.md >> README.md.new
- - mv README.md.new README.md
- - git commit -am "Enforce github readme"
- - git push origin master
\ No newline at end of file
diff --git a/0000-duip-format.md b/0000-duip-format.md
deleted file mode 100644
index eff85d20552de5f77bd04fffbe7a4a66d08505b2..0000000000000000000000000000000000000000
--- a/0000-duip-format.md
+++ /dev/null
@@ -1,15 +0,0 @@
-```
-DUIP: 0
-Title: DUIP format
-Author: nanocryk <nanocryk@gmail.com>
-Status: Proposition
-Type: Process
-Created: 2017-11-22
-License: GPL-3
-```
-
-A **DU**niter **I**mprovement **P**roposal (**DUIP**) is a design document describing new feature for Duniter or its processes or environment. The DUIP should provide a concise technical specification of the feature and a ratonale for the feature.
-
-We intend DUIPs to be the primary mechanics for proposing new features, for collecing community input on an issue, and for documenting the design decisions the have gone into Duniter. The DUIP author is responsible for building consensus within the community and documenting dissenting opinions.
-
-Because the DUIPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.
\ No newline at end of file
diff --git a/LICENSE b/LICENSE.txt
similarity index 86%
rename from LICENSE
rename to LICENSE.txt
index 94a9ed024d3859793618152ea559a168bbcbb5e2..a871fcfd0f388fb04465c6c870f0c52967397ed1 100644
--- a/LICENSE
+++ b/LICENSE.txt
@@ -1,5 +1,5 @@
- GNU GENERAL PUBLIC LICENSE
- Version 3, 29 June 2007
+ GNU AFFERO GENERAL PUBLIC LICENSE
+ Version 3, 19 November 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
@@ -7,17 +7,15 @@
Preamble
- The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
+ The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
-the GNU General Public License is intended to guarantee your freedom to
+our General Public Licenses are intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
-software for all its users. We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors. You can apply it to
-your programs, too.
+software for all its users.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
@@ -26,44 +24,34 @@ them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
- To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights. Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received. You must make sure that they, too, receive
-or can get the source code. And you must show them these terms so they
-know their rights.
-
- Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
- For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software. For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
- Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so. This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software. The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products. If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
- Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary. To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
+ Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+ A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate. Many developers of free software are heartened and
+encouraged by the resulting cooperation. However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+ The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community. It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server. Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+ An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals. This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
The precise terms and conditions for copying, distribution and
modification follow.
@@ -72,7 +60,7 @@ modification follow.
0. Definitions.
- "This License" refers to version 3 of the GNU General Public License.
+ "This License" refers to version 3 of the GNU Affero General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
@@ -549,35 +537,45 @@ to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
- 13. Use with the GNU Affero General Public License.
+ 13. Remote Network Interaction; Use with the GNU General Public License.
+
+ Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software. This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
+under version 3 of the GNU General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
+the GNU Affero General Public License from time to time. Such new versions
+will be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
-Program specifies that a certain numbered version of the GNU General
+Program specifies that a certain numbered version of the GNU Affero General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
+GNU Affero General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
+versions of the GNU Affero General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
@@ -635,40 +633,30 @@ the "copyright" line and a pointer to where the full notice is found.
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
+ it under the terms of the GNU Affero General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
+ GNU Affero General Public License for more details.
- You should have received a copy of the GNU General Public License
+ You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
- If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
- <program> Copyright (C) <year> <name of author>
- This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, your program's commands
-might be different; for a GUI interface, you would use an "about box".
+ If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source. For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code. There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
+For more information on this, and how to apply and follow the GNU AGPL, see
<http://www.gnu.org/licenses/>.
- The GNU General Public License does not permit incorporating your program
-into proprietary programs. If your program is a subroutine library, you
-may consider it more useful to permit linking proprietary applications with
-the library. If this is what you want to do, use the GNU Lesser General
-Public License instead of this License. But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/README.md b/README.md
index 80144d28d9950986735668450263c42e90e088ad..6b80ebfb5843ed373b73ae448be62b6d64da481b 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,5 @@
-# DIPS
-Duniter Improvements Proposals
+# Duniter ecosystem documentations
+
+This repository is aimed to provide documentions and RFCs (Request for Changes) used in the whole Duniter ecosystem.
+
+All documents should be implementation agnostis, as specific documentations should be is a dedicated reposity (or implementation repository).
\ No newline at end of file
diff --git a/rfc/0000 RFC Format.md b/rfc/0000 RFC Format.md
new file mode 100644
index 0000000000000000000000000000000000000000..683d6ef43a7c658fb1fed544bc66e35ccece5679
--- /dev/null
+++ b/rfc/0000 RFC Format.md
@@ -0,0 +1,20 @@
+# #0 RFC Format
+
+```txt
+RFC: 0
+Title: RFC Format
+Type: Convention
+Status: WIP
+Author: nanocryk <nanocryk@gmail.com>
+Created: 2017-11-22
+Last edited: 2017-12-20
+License: AGPL-3
+```
+
+A RFC (Request for Changes) is a design document describing new feature for the Duniter ecosystem. It should provide a concise technical specification of the feature and a rationale for the feature.
+
+We intend RFCs to be the primary mechanics for proposing new features, for collecing community input on an issue, and for documenting the design decisions the have gone into Duniter. The RFC author is responsible for building consensus within the community and documenting dissenting opinions.
+
+Because RFCs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.
+
+> TODO : Provide a normalized RFC structure
\ No newline at end of file