Skip to content
This repository has been archived by the owner on May 26, 2022. It is now read-only.

Commit

Permalink
Merge pull request #629 from RichardLitt/feat/edit-docs
Browse files Browse the repository at this point in the history
Edit entry documentation
  • Loading branch information
jamesray1 authored Oct 17, 2018
2 parents a082178 + eb10288 commit 6aee544
Show file tree
Hide file tree
Showing 5 changed files with 27 additions and 7 deletions.
8 changes: 6 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,14 @@ Users signed in with GitHub can edit and add pages using a [browser](https://hel
Wikipedia has [five pillars](https://en.wikipedia.org/wiki/Wikipedia:Five_pillars) which provide a good standard for contributing that we can adapt for our needs. If you have experience with editing on Wikipedia, then that will help with knowing how to edit this wiki, although the contribution rules are less strict. Referencing facts is a key writing and proofreading task, as well as checking that information is up-to-date (and updating it if otherwise), correcting grammar, typos, and spelling; and making the wiki comprehensive and easy to understand. Other rules, such as a neutral point of view and no original research are desirable, but may be hard to maintain. Notability is less relevant, this wiki is about all things Ethereum.

### Translating
The title of the page should start with [Language]: title, e.g. "[German] White Paper" or "[中文] 以太坊Wiki目录". Then add a Table of Contents (ToC) page linking for the language, linking to all pages of that language, and add a link to it in the [footer](https://github.com/ethereum/wiki/wiki/_Footer/_edit).
The title of the page should start with [Language]: title, e.g. "[German] White Paper" or "[中文] 以太坊Wiki目录". Then add a Table of Contents (ToC) page linking for the language, linking to all pages of that language, and add a link to it in the [footer](https://github.com/ethereum/wiki/wiki/_Footer/_edit).

### License and [contributor license agreement](https://github.com/ethereum/wiki/wiki/CC0-license#list-of-contributors)

Please permit your contributions to be under the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/legalcode) [1](https://creativecommons.org/share-your-work/public-domain/cc0/), which makes your contributions have no rights reserved, putting them in the public domain. This will help to allow for the dissemination of information about Ethereum, the Ethereum ecosystem and Web 3 to the public, in a completely permissive manner. To state that you accept your contributions to be under a CC0 license, please add yourself to the list of external contributors [here](https://github.com/ethereum/wiki/wiki/CC0-license#list-of-contributors). Otherwise, without adding yourself to the list, your contributions will be all rights reserved. Some previous contributions may have all rights reserved (by contributors that have not agreed to a CC0 license [at pull request 528](https://github.com/ethereum/wiki/pull/528)), since no copyright permission was stated explicitly. Until all previous contributors agree to a CC0 license, and to provide clarity of licensing, you may also wish to add a HTML comment to the top of pages or sections that you contribute to, like so: `<!--*Name Surname*, Github username, **email@domain** and/or other contact methods-->`.
Please permit your contributions to be under the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/legalcode) [1](https://creativecommons.org/share-your-work/public-domain/cc0/), which makes your contributions have no rights reserved, putting them in the public domain. This will help to allow for the dissemination of information about Ethereum, the Ethereum ecosystem and Web 3 to the public, in a completely permissive manner. To state that you accept your contributions to be under a CC0 license, please add yourself to the list of external contributors [here](https://github.com/ethereum/wiki/wiki/CC0-license#list-of-contributors). Otherwise, without adding yourself to the list, your contributions will be all rights reserved. Some previous contributions may have all rights reserved (by contributors that have not agreed to a CC0 license [at pull request 528](https://github.com/ethereum/wiki/pull/528)), since no copyright permission was stated explicitly. Until all previous contributors agree to a CC0 license, and to provide clarity of licensing, you may also wish to add a HTML comment to the top of pages or sections that you contribute to, like so: `<!--*Name Surname*, Github username, **email@domain** and/or other contact methods-->`.

For more information, see https://github.com/ethereum/wiki/wiki.

## Closed Issues

If you had an issue that has been closed, and feel that it could be reopened after following the above steps, feel free to request to reopen it. About 180 issues and 30 PRs were closed on May 29 2018, due to deleting the codebase and referring people to this wiki, in order to reduce the burden on maintenance by following the above steps. This fits well with Ethereum's ethos of decentralization, which includes minimising bureaucracies, and gives contributors more time to build Ethereum and satisfy the long-term interests of current and future users. If you had an issue or PR that was closed without explanation, I apologize, but it is time-consuming to reply to every one.
12 changes: 9 additions & 3 deletions ISSUE_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
If you have a technical issue with a specific client, application or tool, e.g. those listed [here](https://github.com/ethereum/wiki/wiki/Clients,-tools,-dapp-browsers,-wallets-and-other-projects), please ask in the Gitter room of that project, and if your issue is still not resolved, post an issue in the repo for that project. Please only create an issue if you can't fix it by editing yourself, it doesn't get resolved via the [Gitter documentation room](https://gitter.im/ethereum/documentation) (including pinging someone who knows how to handle the issue, or asking/finding out who knows then pinging them) and only if it is related to the wiki.
Hello! Chances are you're in the wrong place.

If you had an issue that has been closed, and feel that it could be reopened after following the above steps, feel free to request to reopen it. About 180 issues and 30 PRs were closed on May 29 2018, due to deleting the codebase and referring people to this wiki, in order to reduce the burden on maintenance by following the above steps. This fits well with Ethereum's ethos of decentralization, which includes minimising bureaucracies, and gives contributors more time to build Ethereum and satisfy the long-term interests of current and future users. If you had an issue or PR that was closed without explanation, I apologize, but it is time-consuming to reply to every one; I'm hoping that people will see the updated readme and this section.
If you have a technical issue with a specific client, application or tool, e.g. those listed [here](https://github.com/ethereum/wiki/wiki/Clients,-tools,-dapp-browsers,-wallets-and-other-projects), please ask in the Gitter room of that project, and if your issue is still not resolved, post an issue in the repo for that project. This repository is only used for the wiki, and issues here are only relevant if they are directly about the wiki.

While having good documentation is certainly important to help onboard new people including users and contributors of all kinds, there is a lot to do at the moment in terms of design and implementation, and editing documentation is something that seems best to be done when you are reading or learning about something, using something, building upon something, etc., not usually just for the sake of reading and editing for other users, although reviewing one's own writing is certainly a good practice.
Please only create an issue here if:
- You've spotted something in the wiki that you can't fix it by editing it yourself
- Your problem hasn't been resolved on the [Gitter documentation room](https://gitter.im/ethereum/documentation). You've tried pinging someone who knows how to handle the issue, or asking who this might be, and then asking them.
- You've waited at least a couple of days for responses on Gitter.
- And **only** if it is related to the wiki.

Thank you. If your issue was previously closed, see the [Contributing Guide](CONTRIBUTING.md) for more information on closed issues.
6 changes: 5 additions & 1 deletion PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1 +1,5 @@
Do not make a pull request; chances are that all PRs will be ignored, since any content in the codebase can be in this [wiki](https://github.com/ethereum/wiki/wiki) instead.
**Please do not open a pull request.**

This repository no longer contains any code or documentation; please edit the [wiki](https://github.com/ethereum/wiki/wiki) directly, instead.

If you're having issues editing the wiki, you could try reading the introduction to GitHub wikis, [here](https://help.github.com/articles/about-github-wikis/).
8 changes: 7 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1 +1,7 @@
Please use [wiki/wiki](https://github.com/ethereum/wiki/wiki), since that is freely maintainable.
# Wiki

All of the content in this repository lives in the [Wiki](https://github.com/ethereum/wiki/wiki).

[![Screenshot](screenshot.png)](https://github.com/ethereum/wiki/wiki)

There is no longer any code or documentation stored in this repository.
Binary file added screenshot.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

2 comments on commit 6aee544

@frankfuttderBlogmitBanane

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Salve, users!

Sorry... ich git ignore, that these holy halls are not my "random-exercision-football-place"...
But I get so happy that day, that I recognize (5 years after first visit here), what is the matter about "merging & forking" and I just wanted to try try try...
And what a pitty: as an old female human //notU-man//, I was glad that day, to understand small, small, small more & more...
I learnt the last weeks an lot of "github-a-like" and

THEN suddenly I spoke to an small, red mephistopelian - lurging on my shoulder and whispering NONSENSE in my ear, and I just became wild to "test my nonsense-certificated cerebral rubbish" with the integer aim, to enjoy that little, red devil on my shoulder...
I SWEAR, I won´t do again such nonsensual diversifications and hope to become "random-access-gran´Ma" soon....
Next object-orientated joy I will sublimate better into a simple, small ernergy-App, if I will be able to ...
Thx for fitback ;-)
and greetz from an Internet Dinosaur on his long and last way to VULcANs or comets..

Sabine Puttins

@frankfuttderBlogmitBanane

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Salve, enterum Ethereum!
Reading your github-name, my Rest-Api associated promptly the entitarian connotations of ether hovering between...

I think, that was my reason to "disrupt your files into emptiness" and gave U the bad experience, to burp loudly like a complaint of a creepy, sweezy internet dinosaur //since 1987: ONLINE// to do OFF: the ether.net fix abba fix frei - von Logik... ;-)

I WILL NEVER DO again such heavy nonsense open again and give U the

Please sign in to comment.