Open source software

Question 1

Issues with open source

Answer 1

unrealistic expectations about the benefits of open source
- too few active developers
- open code needs to be understandable by strangers
- needs a development site and communication tools
Barriers to entry for new devs
Falacy that little or no PM is required for open source

Question 2

Onion model of OS community structure

Answer 2

passive user
active user
peripheral dev
active dev
committers
core team

Question 3

onion model core team

Answer 3

consists of one or two developers who make decisions about the software direction and contributions to the code base

Question 4

onion model committers

Answer 4

commit rights that allow admission of the code into the main code base

Question 5

onion model active developers

Answer 5

regularly contribute to code repo

Question 6

onion model peripheral developer

Answer 6

submit code as patches meaning that their code does not enter the main code base until a review from the core team

Question 7

onion model active user

Answer 7

contribute to the documentation, localization, supporting user in discussion forums or filing bug reports

Question 8

passive users (onion model)

Answer 8

download and use software without connecting to the community

Question 9

advantages of open source

Answer 9

speed of development and time saving
more people fixing bugs and security flaws
open standards and standard interfaces - enables use of different solutions
less likely to have a vendor lock

Question 10

basic open-source project components

Answer 10

community of software developers
software license
tools for project hosting and communicating
governance model

Question 11

goal of open source foundations

Answer 11

help devs establish open source projects - doubt this is examinable

Question 12

what are open source software licenses

Answer 12

license protects contributers and users
outlines the terms of use
can limit liability
important to understand legalities

Question 13

some examples of popular software licenses

Answer 13

Apache license
BSD 3 clause new
BSD 3 clause simplified
GNU general public

Question 14

Example of open source governance models

Answer 14

do-ocracy
Founder-leader
self-appointing council or board
electorial
corporate-backed
foundation backed

Question 15

what a project needs

Answer 15

web site
mailing lists
real time chat
version control
bug tracking

Question 16

how to transform private vision into public one

Answer 16

choose good name
register domain
set up the website

Question 17

Project homepage

Answer 17

mission statement

state that project is free

Question 18

project communication

Answer 18

communication channels

developer guidelines

Question 19

Project requirements, features and status

Answer 19

features - what does it do, list of features
Requirements - computing environment required to run the software
development status - goals and needs

Question 20

project - accurate accounting of deficiencies

Answer 20

Identify issues in context

Question 21

project distribution

Answer 21

downloads?
distribution channel should be convenient, standard and as low overhead as possible
Standardize build and installation procedures

Question 22

project documentation - minimal criterea

Answer 22

tell reader how much technical knowledge and expertise they should have
basically - user manual
tutorial style example

Question 23

Do anything vs GPL

Answer 23

do anything - if you’re okay with code being used i n propriety programs
GPL - dont want code to be used in propriety programs

Question 24

How to apply software license

Answer 24

tell public about you intende to license (on web page)
for legal purposes, the software must contain the license.
- Full license text “Copying” or “License”

Question 25

Setting team dynamics - how to set the tone

Answer 25

avoid private discussions - no inner circle
public discussion
Never let bad behaviour slide by unnoticed

Question 26

issue life cycle

Answer 26

submission
open
diagnose
resolution
closed

Question 27

Important things when setting up a new project

Answer 27

setting the tone
practicing conspicuous code review
version control (devs need access to realtime updates)
bug or issue tracker