Guest lecture at "Advanced Design: Innovation and Trans-disciplinary in Architectural Design" Post-Graduate programme of studies, School of Architecture, Aristotle University of Thessaloniki. SUMMARY: An introduction to Free/Libre Open Source Software development philosophy and the essential tools / processes needed to evolve from individually creating F/LOSS code to social coding as part of a F/LOSS community.

1. SAY AYE IF
YOU ♥ THE 90s

2. https://en.wikipedia.org/wiki/St._Peter%27s_Basilica

3. https://en.wikipedia.org/wiki/Bazaar

4. DOING F/LOSSDOING F/LOSS
the Cathedral & the Bazaarthe Cathedral & the Bazaar
Apostolos Kritikos, PhD Candidate
Informatics Dept., Aristotle University of Thessaloniki
@ TRANSMYTHOLOGIES IN ARCHITECTURE
School of Architecture, Aristotle University of Thessaloniki
Advanced Design: Innovation and Transdisciplinary in Architectural Design
Post-Graduate programme of studies
Unless otherwise expressly stated, all original material in
Doing F/LOSS. The Cathedral and the Bazaar by Apostolos Kritikos, ©2015,
is licensed under Attribution-ShareAlike 4.0 International and CAN BE REUSED!

5. C o d i n g ! ! !
A personal journey!
[ HINT: The elements are clickable ;) ]
2000ish
2003 2008 2010
HELLO
WORLD
BSc MSc
2011
PhD
2016
2014
Social Mind

6. .: I :.
“it will not be possible to be
and not to be the same thing”
-- Aristotle
(law of excluded middle)

7. via Wiktionary.org

8. via Wiktionary.org

9. via Wiktionary.org

10. via Wiktionary.org

11. via Wiktionary.org

12. .: II :.
“The fact that this bazaar style seemed to work, and work
well, came as a distinct shock. As I learned my way around, I
worked hard not just at individual projects, but also at trying
to understand why the Linux world not only didn't fly apart in
confusion but seemed to go from strength to strength at a
speed barely imaginable to cathedral-builders.”
-- Eric Raymond
(the cathedral and the bazaar)

13. WHAT DO THE FOLLOWING
MEAN TO YOU?
-- Eric Raymond
(the cathedral and the bazaar)

14. “Every good work of software starts by scratching a
developer's personal itch.”

15. “Good programmers know what to write.
Great ones know what to rewrite (and reuse).”

16. “Plan to throw one away; you will, anyhow.”
(Fred Brooks, The Mythical Man-Month, Chapter 11)

17. “ If you have the right attitude,
interesting problems will find you.”

18. “When you lose interest in a program, your last duty
to it is to hand it off to a competent successor.”

19. “Treating your users as co-developers is your
least-hassle route to rapid code improvement
and effective debugging.”

20. “ Release early. Release often.
And listen to your customers.”

21. “Given a large enough beta-tester and co-developer
base, almost every problem will be characterized
quickly and the fix obvious to someone.”

22. “Smart data structures and dumb code works a lot
better than the other way around.”

23. “If you treat your beta-testers as if they're your most
valuable resource, they will respond by becoming your
most valuable resource.”

24. “The next best thing to having good ideas is
recognizing good ideas from your users. Sometimes
the latter is better..”

25. “Often, the most striking and innovative solutions
come from realizing that your concept of the problem
was wrong.”

26. “Perfection (in design) is achieved not when there is
nothing more to add, but rather when there is nothing
more to take away.''”

27. “Any tool should be useful in the expected way, but a
truly great tool lends itself to uses you never
expected.”

28. “When writing gateway software of any kind, take
pains to disturb the data stream as little as possible—
and never throw away information unless the recipient
forces you to!”

29. “When your language is nowhere near Turing-
complete, syntactic sugar can be your friend.”

30. “A security system is only as secure as its secret.
Beware of pseudo-secrets.”

31. “To solve an interesting problem, start by finding a
problem that is interesting to you.”

32. “ Provided the development coordinator has a
communications medium at least as good as the
Internet, and knows how to lead without coercion,
many heads are inevitably better than one.”

33. .: III :.
“I think a good rule of thumb that will scale with the
community as it continues to grow is that organizations that
want to grow the WordPress pie (and not just their piece of
it) should dedicate 5% of their people to working on
something to do with core — be it development,
documentation, security, support forums, theme reviews,
training, testing, translation or whatever it might be that
helps move WordPress mission forward.”
-- Matt Mullenweg

34. HOW DO YOU WORK?
(SYSTEM)

36. Scrum
https://en.wikipedia.org/wiki/Scrum_%28software_development%29

37. +CONVENTIONS
https://en.wikipedia.org/wiki/Scrum_%28software_development%29
- requirements
- coding standards
- documentation standards
- testing
- naming
- versioning

38. WHERE DOES
YOUR CODE LIVE?

40. HOW DO YOU
COMMUNICATE?

41. ( All trademarks, service marks, trade names, trade dress, product names and logos
appearing on the slide are the property of their respective owners )

43. U R COMMUNITY!
NOW WHAT?
(THE FLOOR IS YOURS)

44. Apostolos Kritikos
/akritiko
/in/apostoloskritikos
akritiko@gmail.com
Check www.socialmind.gr
we ♥ working with F/LOSS
thanks :)