Absolutely ALL information about EVERY blockchain project in a comparison tool that ANYONE can understand.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.meteor
client
docs
i18n
imports Problem :- Redirect to 404 page when click on logout button Oct 23, 2018
lib
production_scripts
public Problem: Incorrect image directory used in codebase (#1969) Sep 19, 2018
server
.babelrc
.eslintignore
.eslintrc.yml Problem : Eslint not configured for meteor #1882 Sep 11, 2018
.gitignore
.gitignore.orig
.keep
.travis.yml
AUTHORS
CONTRIBUTING.MD problem: dead link in C4 Mar 11, 2018
DESCRIPTIVE_C4.MD
ISSUE_TEMPLATE.md Problem: no issue template Jan 14, 2018
LICENSE Initial commit Oct 22, 2017
MAINTAINERS
README.md Problem : Guide on Readme needs update #2052 Oct 12, 2018
STYLES.md
auctions.de.i18n.json
auctions.sr.i18n.json Problem: Blockrazor strings are not translated Sep 27, 2018
messages.sr.i18n.json
package-lock.json
package.json
wdio.conf.js

README.md

Blockrazor

Absolutely all information about every blockchain project in a comparison tool that anyone can understand.

Build Status
https://blockrazor.org builds directly from Master with every merge.
Sample login credentials:
moderator: frank:rodviv
user: simply create a new account for yourself.

How to run Blockrazor locally

Install Meteor

curl https://install.meteor.com/ | sh

Clone repository

git clone https://github.com/Blockrazor/blockrazor.git

Note: if you want to edit things and send a pull request you should fork this project on Github first and clone your fork instead of https://github.com/Blockrazor/blockrazor.git.

Install Dependencies

meteor npm install

Run meteor

npm start (use npm run prod to minify everything and simulate production speeds) (use npm run debug to start Meteor in debug mode)

If Meteor starts but you get a white screen:

meteor npm install --save core-js

Environment Variables

Create .env file on home directory and add your variables

Email Setup

Add MAIL_URL to .env file.

Example : For sendgrid email

MAIL_URL=smtp://username:password@smtp.sendgrid.net:587

Insert the database if running locally (never for production)

While meteor is running, in a new shell from outside of the Blockrazor directory run:

wget https://blockrazor.org/static/dump.tar.gz && tar -xvf dump.tar.gz && mongorestore -h 127.0.0.1 --port 3001 -d meteor dump/meteor

(You will need Mongo to be installed on your system).

If you already have the database but want to update it to the latest version, do a meteor reset before running the above.

Mongo errors

If Mongo exists with status 1: Quick fix: export LC_ALL=C
Proper fix: something is wrong with your OS locales, good luck.

Meteor errors

If you do a git pull and Meteor doesn't start, the first thing to do is run meteor npm install as there may be package updates.

Contributing to Blockrazor

A cardinal sin that many open source developers make is to place themselves above others. "I founded this project thus my intellect is superior to that of others". It's immodest and rude, and usually inaccurate. The contribution policy we use at Blockrazor applies equally to everyone, without distinction.

The contribution policy we follow is the Collective Code Construction Contract (C4)

If you're wondering why any of the rules in the C4 are there, take a look at the line by line explanation of everything in the C4, this explains the rationale and history behind everything in the protocol and makes it easier to understand.

Take a look at past pull requests to see how we usually do things. You may also want to look at the bad pull request role of honour to see how not to send a pull request.

Want to see server logs? Go here.

The project style guide is here.

Step-by-step guide to sending a pull request

  1. Read the contribution protocol and the line by line explanation of the protocol.
  2. Fork this github repository under your own github account.
  3. Clone your fork locally on your development machine.
  4. Choose one problem to solve. If you aren't solving a problem that's already in the issue tracker you should describe the problem there (and your idea of the solution) first to see if anyone else has something to say about it (maybe someone is already working on a solution, or maybe you're doing somthing wrong).

It is important to claim the issue you want to work on so that others don't work on the same thing. Make a comment in the issue: @emurgobot claim before you start working on the issue.

If at some point you want to abandon the issue and let someone else have a go, comment: @emurgobot abandon.

  1. Add the Blockrazor repository as an upstream source and pull any changes:
@: git remote add upstream git://github.com/blockrazor/blockrazor //only needs to be done once
@: git checkout master //just to make sure you're on the correct branch
@: git pull upstream master //this grabs any code that has changed, you want to be working on the latest 'version'
@: git push //update your remote fork with the changes you just pulled from upstream master
  1. Create a local branch on your machine git checkout -b branch_name (it's usually a good idea to call the branch something that describes the problem you are solving). Never develop on the master branch, as the master branch is exclusively used to accept incoming changes from upstream:master and you'll run into problems if you try to use it for anything else.
  2. Solve the problem in the absolute most simple and fastest possible way with the smallest number of changes humanly possible. Tell other people what you're doing by putting very clear and descriptive comments in your code every 2-3 lines.
    Add your name to the AUTHORS file so that you become a part owner of Blockrazor.
  3. Commit your changes to your own fork: Before you commit changes, you should check if you are working on the latest version (again). Go to the github website and open your fork of Blockrazor, it should say This branch is even with Blockrazor:master.
    If not, you need to pull the latest changes from the upstream Blockrazor repository and replay your changes on top of the latest version:
@: git stash //save your work locally
@: git checkout master
@: git pull upstream master
@: git push
@: git checkout -b branch_name_stash
@: git stash pop //_replay_ your work on the new branch which is now fully up to date with the Blockrazor repository

Note: after running git stash pop you should run Meteor and look over your code again and check that everything still works as sometimes a file you worked on was changed in the meantime.

Now you can add your changes:

@: git add changed_file.js //repeat for each file you changed

And then commit your changes:

@: git commit -m 'problem: <50 characters describing the problem //do not close the '', press ENTER two (2) times
>
>solution: short description of how you solved the problem.' //Now you can close the ''. Be sure to mention the issue number if there is one (e.g. #6)    
@: git push //this will send your changes to _your_ fork on Github
  1. Go to your fork on Github and select the branch you just worked on. Click "pull request" to send a pull request back to the Blockrazor repository.
  2. Send the pull request, be sure to mention the issue number with a # symbol at the front (e.g. #1014).
  3. Go back to the issue, and make a comment:
  Done in #(PR_NUMBER)
  @emurgobot done

This will label this issue as complete, and everyone can test your solution and close the issue if it solves the problem.

What happens after I send a pull request?

If your pull request contains a correct patch (read the C4) a maintainer will merge it. If you want to work on another problem while you are waiting for it to merge simply repeat the above steps starting at:

@: git checkout master

Tests

To run tests:

meteor test --driver-package practicalmeteor:mocha

You should generally write a test for anything you don't want to break later, otherwise it will probably end up being broken by someone. We use Mocha + Chai for testing. You can see an example in this pull request.

Can I be paid to contribute to Blockrazor?

Yes, this is sometimes possible.

Your first step is to very carefully read and understand everything above, including the linked files, then start fixing problems and sending pull requests!

If your code is amazing and brilliant but you don't understand the contribution process we cannot consider you for a paid position.

Make sure you follow the project on Github so you get updates.

Contact Blockrazor's BDFL (Benevolent Dictator For Life): gareth.hayes AT gmail.com if you've been contributing code to Blockrazor and want to keep doing it but you are hungry.

Rules for paid contributors

  1. Write tests for your code so that people don't break it later. We use We use Mocha + Chai for testing. You can see an example in this pull request.

  2. Engage in discussion about problems even if you aren't working on them yourself. Be helpful to other contributors, many are volunteers who just want to be part of the project. You (should) have a pretty good understanding of the codebase and can probably save others a lot of time.

  3. Your code should be very well commented and easy to read. It should be immediately clear what your code is doing. You should be able to look at your code a year later, in the morning before coffee, and immediately know what it's doing. Write code and comments like you are teaching someone else how to do what you're doing.

  4. Your pull requests should be a glowing example to others of how to work with the C4. Each one should be a model that others can refer to.

  5. In an ideal world, you would be able to work on any issue you want and there would be no need to assign tasks so that our budget is kept under control. This would be possible because you would always work on the the problems that are really worth solving right now to get to some form of MVP. We can't predict the future, there are no plans or roadmaps (these are not compatible with the C4). Blockrazor grows through evolution not intelligent design or central planning. So if something isn't an in-your-face problem right now, it may never be, we could end up going down a totally different road before we get to it. While we want to avoid technical debt, we also don't want to be working on things that will someday maybe become a problem if Blockrazor becomes a thing. Demonstrate that we can trust your own judgement on what you should be working on and what's worth spending time on.

License

The license and contribution policy are two halves of the same puzzle. This project is licensed under the MPL v2.0 license. The code is owned (and Copyright) by all contributors. Contributors are listed in the AUTHORS file. Please add your name to the end of this file in your first pull request so that you also become an owner.

This license ensures that:

  1. Contributors to Blockrazor cannot have their code stolen and used by closed-source projects without their permission. It's very common for corporate software merchants to steal code from open source projects and use it in their closed source or even patented products and services in direct competition with the original project. For example, anyone who contributes code to a project released under a BSD/MIT style license effectively has no rights to their own code or any improvements made upon it.
  2. Anyone using any code from Blockrazor must also share their work under a share-alike license so that anyone else can use their improvements.
  3. No one can change the above, without explicit written permission from all contributors, which is essentially impossible to get. That means even the founder of this project cannot ever relicense and sell Blockrazor and its code. It belongs to everyone who contributed to it (and it always will).

It is not permissible to use any code from this codebase in anything that isn't using a share-alike license. Violations of the license will absolutely not be tolerated, and the terms of this license will be brutally enforced through a variety of very creative methods.