GSoC_2017_low_hanging_fruit

The low hanging fruit

Let's face it, Shogun is not in a healthy state. Recent research suggests that taking part in a 5-a-day-scheme offer various health-benefits. This project is about getting your hands on fruits -- low hanging fruits. Let's pick them all!

It is most likely that we will organise a group-harvest this GSoC -- all students will be involved in identifying, collection, and picking/pickling.

Mentors

• Heiko (github: karlnapf, IRC: HeikoS)
• Viktor (github: vigsterkr, IRC: wiking)
• Sergey (github: lisitsyn, IRC: lisitsyn)

What is a low hanging fruit?

Low-hanging fruits can take many shapes. Some appear in the form of compiler warnings, others dress as memory leaks, race conditions or uninitialised members. Some pretend to be cookable, some mimic cmake madness, and there are also some that behave as entrance tasks. Definitely all of them are easily pickable with few code changes, or even no code changes, and lead to a reduction of unhealthy organs. There are even low-hanging fruits that just involve closing an ancient github issue. This is not a bug, it is a low-hanging fruit!

Is this project for you?

This project requires serious duct tape-programming-skills. Low hanging fruits have been sighted all over Shogun's code base. So this is for you if you:

• can spot them, and
• and get the job done.

Note that low-hanging fruits can also be picked by non-rockstars.

Waypoints and initial work

1. Collect a list of low-hanging fruits (how many can you find?)
2. Fix them, using minimalist style patches
3. World domination.