Roadmap to 0.2.0

There are some changes in the pipe that may change the API.

What about heading v0.2.0 (when?) and collect all API changes. Is it possible to release 0.1.5 with a bunch of FutureWarnings?

• Replacing all transformer class by one Transformer (see #351)

• Changing the results API: see #329

• Adding periods (Breaks the API only if you use additional constraints)

• Adding custom components

• Doing some polishing: see. #330 and #328

• Removing hidden magic e.g. making automatic instatiation like Source(....) without a reference impossible or at least hide the possibility within the examples

• Use __init__.pys consistently

• Move everything except sink, source, transformer and bus to custom components

• Remove redundancies of EnergySystem and OperationModel

• Introduce Basic Model for Multi-Period introduction

• Move some classes to EnergySystem (according to: #315)

• Removing the csv-reader (see #355)!

• How to import consistently e.g. import oemof.solph with solph.my_component() or from oemof.solph import (comps) with my_component ?

• Integrating a license in all files. See: #262 and https://github.com/oemof/organisation/issues/9

• Add API examples to all solph components e.g. https://github.com/oemof/oemof/blob/dev/oemof/solph/components.py consistently (like for network classes) @ckaldemeyer

[ckaldemeyer]

I have added and linked some todos and issues

[uvchik]

I moved obvious stuff to the last todo list #382.

@simnh , @ckaldemeyer : Please make suggestions how to handle your last open topics.