Please enable JavaScript.
Coggle requires JavaScript to display documents.
Open Sourcing a Software Product (community (benefits, e.g. Open Source…
Open Sourcing a
Software Product
License
Review
GNU
opensource.org
double license
(e.g. Apache + Commercial)
GPL or AGPL
Apache License 2.0
MIT or BSD
JBoss approach: different level of maturity
for community and commercial version
messages
"this project is maintained"
"this project is mature"
"this project follows principles"
"we feel responsible for the code"
"we provide constantly new features"
support and
maintenance
can we make money here?
what is the best model?
what is the right message to customers?
community
benefits,
e.g.
Open Source Assurance
we accept contributions from the community
public issue tracker
public roadmap
define contributions workflow
open the build process
marketing
:check:
branding different from
supporting company
:question: protection of brand and trademark
elevator pitch
AIDA Formel
Nutzen zeigen
Interesse und Motivation wecken
Easy step in / Demo
product vs. project:
"People don't want quarter-inch drills.
They want quarter-inch holes."
goal
:check: build a community of users
:check: build a community of contributors
:check: seed the market for your business
:check: build a business on the code itself
questions
What is my core value?
Am I willing to work with competitors?
What are additional commercial
software packages I am providing?
Is it a go to merge with other projects?
Will you stay active and
commit to the project?
links
opensource.com
what to know
how to transition
myths
threads
do we violate software patents?
do we use libraries that is not freely available
or not compatible with our license?
may some other company take our code and make it theirs?