[User-Story] naming

[Eknir]

Rationale

The SWAP source code is continuously in development. Issues such as (proper) naming, error handling, and logging must be up to high-quality standards, in order to improve the maintainability of the code.

User-Story

As a developer of the Swarm source code, I want the variables and functions to be properly named, such that by just looking at the variable and function names, I intuitively understand what their function is.

Epic links

Stable SWAP

Acceptance criteria

• Consensus among all Swarm incentives developers about the proposal to update names and a PR which implements this proposal

Requirements

Work estimate

Related Issues

ethersphere/swarm#1822

[santicomp2014]

Maybe a simple way of consensus is a poll (form).
On different naming schemes, so we can all agree on it.

Write Guidelines of naming for SWAP

[janos]

When in doubt, it is the best to consult first https://github.com/golang/go/wiki/CodeReviewComments and https://golang.org/doc/effective_go.html.