Johannes Röder

With the API of `other_needs` a nested structure is introduced. Maybe, I did not follow all of the discussion, but the purpose with that is to implement explicitly named arguments...

PR relates to issue #734

There seems to be a problem with (all?) links to external classes in the docstring, e.g. ``pyomo.core.base.block.SimpleBlock`` I did not figure out how to solve that. Could somebody help? For...

Thanks for the summary! I think this issue is kind of important since it seems that a couple of other issues are related to that (#579 #428 #525 #579 ...)....

In #522 I have adapted the docstring forthe OffsetTransformer according to option II), see also [docstring OffsetTransformerBlock](https://oemof.readthedocs.io/en/features-improve_offset_transformer/api/oemof.solph.html#oemof.solph.components.OffsetTransformerBlock) - What do you think?

> In addition, I think it matters, if we use Version I) or II), because the table should be part of the template. Yes, I think as well that the...

> Shall we add the template to the developer documentation? I think that is a good idea and I could have a try. I am wondering which branch to use?...

As fas as I know, the gradient constraint is not implemented in the InvestmentFlow in oemof-solph yet. I think, it is not a big thing to implemented this, but maybe,...

Okay, there is already a PR. See #405 - and, maybe, it is not that easy as I just thought 😉 I just talked to @uvchik , this feature won't...

> > > I will present the general approach at the next meeting and if I do not find anybody who will support this idea I will close this issue....