WWDC Detroit Syllabus Ideas

This page is a collection of ideas regarding the topics we would/could/should talk about at the Detroit OF conference. Edit away, add what you think it important.

The "official" topic of the conference is:

The goal for this developers conference is to focus on documentation, tutorials and examples - trying to find better entry points for beginners, more advanced users, teachers, etc. The conference will be a chance to develop examples to truly show off what is possible in OF as well a chance to discuss the roadmap for the next few OF releases.

So, regarding documentation, tutorials and examples, it makes sense to identify specific areas which need some love.

Topic collection:

Documentation

Pretty much everything can be improved here. Any specific ideas?

Tutorials

What kinds of tutorials are needed or need to be improved?

• Git workflow: How/why do I work with git? How can I accomplish specific OF-related tasks with git? ([Christoph]: I intend to tackle at least part of this)

• more

Examples

Which examples are in dire need of improvement? Which core functionality needs examples in the first place?

• a

• b

Roadmap

Where will OF go in the (near) future? Release cycles?

Contributing to OF

I [Christoph] think it's very important that we streamline the process of people contributing to OF. Therefore, the following interconnected topics should get some time to be discussed:

• PR workflow/policies streamlining: How can we ensure we do not waste code/effort and frustrate people away from contributing code to OF?

• How will we integrate the newly elected section leaders into the whole process?

• Issues processing: How do we reduce the number of open issues/PR's, and treat issues/PR's in a timely fashion?

• Improve information flow: How can we make sure effort we all spend in improving OF goes in the right direction, as envisioned by the core devs?