Overview of code layout

[BENR0]

Hello,
technically not really an issue, so please let me know if I should put this question somewhere else.

I tried to get an overview of the structure of the code and up to now think I got a rough idea.
But what I am still missing is the general idea of how/why the satpy package is layed out as it is,
meaning what are the ideas behind and how do the different parts of a Scene (dataset, dependency tree, readers, writers, resample, plugin_base, etc.) interplay.

I would like to enhance/add some functionality and if so desired contribute those back to the project and therefore like to understand the ideas which led to the design of the package in order to have a starting point.

I also have further questions regarding two readers. Should I post these questions as issues or contact someone directly about it?

Thanks
Benjamin

[djhoese]

Hi @BENR0, please see our contributor's guide: http://satpy.readthedocs.io/en/latest/dev_guide/CONTRIBUTING.html

There is also the overview documentation which describes what each main component does: http://satpy.readthedocs.io/en/latest/overview.html

It is probably easiest to discuss things on Slack (see contributor's guide), but as a general rule: the components of satpy exist because the problems we are solving could be broken down in to these components. SatPy is also the result of combining two previous projects, mpop and polar2grid, in to one package/design. Hope this helps a little. Let's continue the discussion on slack if possible, otherwise here is fine.