Outline Discussion

[gamaanderson]

outline

[gamaanderson]

I would like to present first, some points for why ARTview is important:

• ARTview has not been explored in other courses. At most there were half an hour in 2015, when it was still initial.
• ARTview is based in Py-ART, so promoting it will promote Py-ART at the same time.
• It is a GUI interface, focus in data visualization and editing. In this sense it is unique and addresses an open niche for researches doing individual work, disconnected from a bigger organization.
• We ourselves war working independently and don’t receive institutional support, therefore feedback from the community is extra important.
• We Plan to present our approach to modular GUI, that we used in bulding ARTView. So this shall be usefull for developer of other GUI softwares, not only for ARTView users.

[gamaanderson]

@danielmichelson e-mail comment: """ When it comes to the course outline, I think we need to ask ourselves what the purpose of the course is and create an outline that meets the course objective. My opinion is that the course should be geared towards introducing people to practical methods associated with Open Science in a weather radar context, where software plays a major role. But even though software is extremely important, it is still a means to an end. So, the course needs to address the big picture in order to clarify the role that OSS plays.

When we look at the course outline for ERAD last year, we see that the time spent before morning coffee, and even after (Python intro), addressed the big picture. This was done before diving into the details of radar-specific OSS. "Big picture" means things like:

• What is Open Science and OSS?
• Intro to Git as a way to address 1) version control, and 2) collaborative development. How to create/fork/contribute.
• More open collaborative methods, like writing tickets/issues, unit tests, open documentation
• Why ORVM and what OSS radar packages are on it?

When this foundation is set, the exposure to the radar software is then done in its proper context, hopefully making it easier to understand.

It is unrealistic, again in my opinion, to expect participants to attend a one-day course and walk away being able to use a given radar software package in a fully functional manner. We can introduce software packages and highlight their capabilities, leaving participants knowing how to dig deeper and how to get involved.

So I would like to see that the course outline for Chicago is adjusted to meet this approach, if you agree. """

[gamaanderson]

I agree in putting the focus on OSS development process. I even consider using the artview part to present our learning process in creating a modular GUI.

That however would means expanding the initial part by putting github and collaborative methods. This would mean time reductions to be distributed between the softwares.

[gamaanderson]

I would also like to point to the suggestion in #2 to change the presentation order.

[gamaanderson]

I just updated the outline taking the suggestions in consideration. Put an demo introduction in the beginning and also a section for Open Source Development. please comment.

@DanielMichelson I would like you to edit the Python Tools part. You have an hour to present what you want. The separation there is only because of the coffee break.