| title | author | date | category | layout |
|---|---|---|---|---|
DOCUMENTS REPOSITORY README |
Decentralized Climate Foundation |
2022-02-04 |
README |
post |
👾
The purpose of the README is to guide on how to contribute to the DCF
And not die in the process.
- You must have installed Rubygems version 2.5.0 or higher. (check your Gems version using gem -v since you may already have it installed on your machine).
- GCC 10.2.1 and Make 4.3 or higher (check versions using gcc -v, g++ -v, and make -v since you may already have it installed on your machine),
- As well as Ruby 2.5.0 (check your Ruby version using ruby -v).
Before contributing to DCF, you need to prepare your Linux system with Jekyll by following these steps.
As mentioned before, you should check that your Linux machine has Ruby version 2.5.0 or higher, including all headers. (If you are not sure if your version has Ruby, you can verify it with the command ruby -v).
$ ruby -v
$ sudo apt-get install ruby-full
Please also verify that you have the latest version of RubyGems by using the command gem -v. If it is not installed, you can proceed with the installation.
$ gem -v
$ gem update --system
# WARNING: If you need to update the gems, there are
# two options: either update them using a tool like rvm# or ruby-install, among others.
# It is not necessary to update them since Ruby is
# already up to date.
# Additionally, you can also update them using the
# following command: */
$ sudo apt update && sudo apt upgrade
# This command first updates the list of available packages and then updates the installed programs on the system to their latest versions.Make sure that you have GCC 10.2.1 and Make 4.3 or higher installed (You can check their installation by using the commands gcc -v, g++ -v, and make -v, respectively).
$ sudo apt-get update
$ sudo apt-get install gcc make
$ make -v
GNU Make 4.3
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ gcc -v
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Now we need to proceed with installing Bundle 2.4.8 or higher and its gems:
$ gem install jekyll bundler
$ bundle install
$ bindle -v
Bundler version 2.4.8
$ bundle exec jekyll b
# This command is used to gathe
the changes and clear the cache of the browser
being used.
$ bundle exec -H # IP Server & PC #
# Example: bundle exec -H 10.162.235.52
# This command helps us configure the IP of the
# server being used to run bundle. Remember to enter
# the correct IP of your server or PC.
# Remember to run this command in the root folder of
# your Git project. Otherwise, you might get warnings
# that something was compiled incorrectly, even if it's# being run in a subfolder of the project. Remember that the last command is to run the website and verify that the contribution runs correctly.
"Verify that there are no issues in Docs Project DCF that address the contribution or problem you wish to collaborate on (as it may have already been started by another user)."
You can check the issues at the following link:
If you have previously verified that the proposal or issue does not exist, you can write it following the following format:
After accessing the issues link, we must check if there is no related proposal or issue on the list. If we realize that there is none, we can add one by clicking on the + sign and assigning a brief title to it.
Img1: At the bottom of the issues, you can add a new one (Remember to check that there is no related open issue and its status).
Img2: Once you have confirmed that there is no open issue, you can click on "Create a new issue".
Img3: When contributing, you must specify a short title and also provide a description of the error that will be corrected.
👁️🗨️ To create an issue in Github, follow these steps: 👁️🗨️
- Access the repository page where you want to create the issue.
- Click on the "Issues" tab at the top of the page.
- Click on the green "New issue" button at the top right of the page.
- Write a brief and descriptive title for the issue in the "Title" field.
- Describe the problem in detail in the "Write" field.
- If applicable, use the text formatting options to add formatting, images, or links.
- Label the issue with appropriate tags to make it easier to find and organize. Tags can be customized by the repository or used from a list of common tags.
- Assign the issue to a responsible team member or leave it unassigned if not necessary.
- If applicable, set a due date for the issue.
- Click the green "Submit new issue" button to publish the issue.
It is important to provide all relevant information so that others can understand the problem and help resolve it. Additionally, it is important to label the issue correctly to make it easier to find and organize. If possible, a proposed solution or suggestions to help solve the problem can also be provided.
You must clone the docs repository to your computer (having the necessary tools and packages to run Jekyll on your computer).
If you don't have what is necessary to run the repository, you can install what is pertinent for Jekyll by clicking on the link.
When you have the repository perfectly installed and configured, you create, improve or solve your issues and send screenshots in the same issue (as responses to it) where we can see the changes and that it works.
If you need to access the Issues section of DCF again, you can click on the link.
Send a Pull Request to the Develop branch of DCF docs, filling in the requirements, such as a brief title and comments on what was done. If everything is approved, your issue will be marked as completed and the changes will be added to the project.
As DCF is a decentralized project, remember that any file, image, or document that you want to contribute needs to have a reasonable size to avoid conflicts when processing it. There are ways to compress it.
If you want to publish a post or article on https://docs.decentralizedclimate.org/, follow these steps:
the markdown post should be allocated in the _posts directory
and the post should be added to the DCF Directory index is at index.md
the markdown post should be allocated in the _posts/socialserv directory:
and the post should be added to the Social Services Directory index is at _pages/socialServices.md
Here we are simply specifying the path within the docs project, both for social services and for the docs project.
- A header with the following data in markdown format:
---
title: Monthly Activity Report of the Decentralized Climate Foundation A.C. January.
author: Decentralized Climate Foundation
date: 2023-05-10
layout: post
---
- A file name starting with the date in the format YYYY-MM-DD-myposttopic.md. Some examples already exist in the directory.
To add a link the docs project, you should go to /docs/index.md and add the link in the following format:
To add a link for social services, you neeed to got to docs/_pages/socialserv and add the link in the following format:
Note that the URL is not a permalink. It is in the format YYYY-MM-DD-myposttopic without the .md extension.
It is recommended to use tools to verify that your post is decentralized correctly, one of these tools is. EXAMPLE: Fleek
4.- Optional: You can fork the project on your user account on the develop branch and link it to hackmd.io to edit before making a commit to your own repository. Then, submit a pull request, or edit the post directly in the GitHub editor.
6.- Additionally, if you want to add images to your post, place them in the assets directory. Please refer to the README for more information.
Example:
Img4: Here is an example of how to reference the images located in the assets folder and in the folder where you host the images for your contribution (It is good to maintain this organization to know which images belong to which project).
If you want to include images, but they have a high definition and therefore are very heavy, you can use tools to reduce their size so that they load more easily on WEB3.(Keep in mind that whenever you do this, the image should not lose too much fidelity; reducing it to the appropriate size is the best option). EXAMPLE: Squoosh
Copyright (C) DECENTRALIZED CLIMATE FOUNDATION A.C.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
Decentralized Climate Foundation
Work developed in collaboration with the Decentralized Climate Foundation.
Author:
Reviewer: