Release Management
Upcoming SlideShare
Loading in...5
×
 

Release Management

on

  • 2,424 views

 

Statistics

Views

Total Views
2,424
Views on SlideShare
2,421
Embed Views
3

Actions

Likes
0
Downloads
35
Comments
0

1 Embed 3

http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Release Management Release Management Presentation Transcript

    • Release Managemente in Free Software Projects Master on Free Software Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a {jjamor,grex,jgb}@gsyc.escet.urjc.es GSyC/Libresoft 2-3 November 2007 Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • (cc) 2007 Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Some rights reserved. This work licensed under Creative Commons Attribution-ShareAlike License. To view a copy of full license, see http://creativecommons.org/licenses/by-sa/2.0/ or write to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Legal aspects Usually, we already have a (maybe small) program Select a license (taking into account the software to be reused), including documentation Decide who has the copyright (authors, institution, etc.) Include the license and copyright information in all source code files Distribute at least a single copy (the process starts) Follow the license “as if the software does not have copyright” Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Good practices when releasing (I) Put the software in a place where it can be downloaded (including the sources) Announce the software (Freshmeat and other specific sites) Simplify the compilation and installation process (maybe including packaging) Documenting the distribution Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Good practices when releasing (and II) Clean the code (including translation into English) Prepare software so that it can be easily translated into other languages Open feedback channels (lists, bug reports, comments in phorums) Build an insfrastructe that makes collaboration not only possible, but also easy Manage contributions, patches, modifications and suggestions Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • The reference site What do we want? Visibility (so that people know that the project exists) User base (that people use the software) Occasional collaborators (make help by users possible) Co-developers (make possible that others get involved) Promote and support a business model Depending on our goals, the required infrastructure will be different Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Working out a good image First impression: the web Second impression: the installation Third impression: the demos Only then we will really evaluate the product It is not a bad idea to have related material: articles, usage videos, etc. It is important that all the impressions are good Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Work on a day to day basis If we want to keep on being the “reference site”: Users have to be motivated to use the resources put for them Updated information Information about related tools Documentation, documentation, documentation That users may express themselves easily; and that they receive convenient feedback Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • The web site Presentation of the project Project download pages (binaries and sources) Page for news Documentation (on-line and downloadable) Usage examples, tricks, etc. Space for contributions (bug reports, patches, etc.) Related tools Support information Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Useful tools Software repository (ftp, http) CVS / Subversion, CVS-Web, Bonsai: if we want to make the latest of the latest available Gnats, BugZilla: report management (bugs, requests, etc.) Phorum (Postnuke, Drupla): helps creating a community Developer blogs Mailman: mailing lists, with the archives (very important) SourceForge, Savannah, BerliOS: all this together (GForge: free software forge) Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • The Software Packaging: tar.gz Debian package RPM package Sources Goal: as easy as possible to install Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Distributing the binary License (COPYING) General Info (README). Very important: cite web site and documentation Installation information (INSTALL) Documentation (maybe in an extra package) Binary for a specific platform (in doubt, static) Packages with their version clearly marked Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Marketing Congresses, etc. Related web sites (especially news sites) News groups Mailing lists Important: generate news every once, but avoid spamming! Very important: Be ready when the announcements are made Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Human resources In addition to development, we need Infrastructure management (100 / 20) Development coordinator, including QA (40-200 / 20) Attention to the bug tracking system (?? / 10-15) Maintaining documentation and on-line information (60 / 10) Public relations (?? / 20) A project with mean complexity (hours at the beginning / hours per week) Sources: “Open Source as a Business Strategy”, Brian Behlendorf Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • Conclusions It is very important to attract users to our site (“marketing campaign”) It is very important to keep the users “with us” (competitive advantage) The main goal is to create a community We have to make life easy to our users Very important: automatize everything that can be made automatically Of course, all this depends on the goals... Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects
    • References “Open Source as a Bussiness Strategy”, por Brian Behlendorf (en Open Sources, Voices from the Open Source Revolution) http://www.oreilly.com/catalog/opensources “Whether and How To Publish Software Under an Open Source License”, por Sebastien Blondeel http://publish.idealx.org/ Juanjo Amor, Gregorio Robles, Jes´s M. Gonz´lez-Barahona u a Release Managemente in Free Software Projects