organizing libreplan free software project
DESCRIPTION
TRANSCRIPT
Organization
● It will be explained how LibrePlan is coordinated and
how is developed:
● The tools
● The human practices (methodology)
● The purpose of these slides is to explain the project
execution stage.
www.libreplan.com
The tools - Wiki
● The project wiki: http://wiki.libreplan.org
● The wiki contains:
● Developer documentation.
● Analysis of the project tasks (it is a very well
documented free sw project regarding requirements).
● The development iterations (XP is used)
www.libreplan.com
The tools - Wiki
● The wiki contains:
● Release log
● Roadmap
● Meeting minutes
● Wiki is public (read-only) for everybody.
● Contributors can have an account with write privileges.
www.libreplan.com
Sourceforge.net
● Sourceforge.net is a website to host resources of
open source projects.
● It was the first site to offer resources for free for
open source projects.
● Resources: Repository, mailing lists, forums, visit
statistics, downloads and stats, documentation,
open source directory, issue tracking
www.libreplan.com
Sourceforge.net
● LibrePlan uses Sourceforge.net currently for:
● Source Code Management and Revision control: Git
● Downloads and stats. LibrePlan releases can be
downloaded there, as well as, other published files.
● Mailing lists
● User forum (They will be closed soon)
● Address: http://sourceforge.net/projects/libreplan
www.libreplan.com
Mailing lists
● At LibrePlan we use mailing lists for communications
about the project.
● Several mailing lists depending on the topic and
language.
● They are public and everybody interested can
subscribe.
www.libreplan.com
Mailing lists
● Three mailing lists:
● [email protected]: List for
developers. For analysis debates, patch reviewing,
doubts, recommendations...
● [email protected] : List thought for all
the LibrePlan users in English language. For doubts,
pieces of news...
● [email protected] : List thought
for LibrePlan users who talk Spanish. www.libreplan.com
User forums
● LibrePlan uses the Sourceforge.net forums, but they will
be closed soon. Two forums:
● Help and Support forum. The same purpose as libreplan-
users mailing list.
● Foro de Ayuda y Soporte. The same purpose as
libreplan-users-es mailing list.
● LibrePlan Question & Answer forum (preferred way for
communication among users): http://ask.libreplan.org
www.libreplan.com
Other media
● Freenode IRC channel #libreplan
● Igalia LibrePlan team members are always
connected there.
● Live communications about LibrePlan: Feedback
about the project, doubts, feature requests, design
and implementation questions...
www.libreplan.com
Other media
● @libreplan user at Twitter. Follow us!
● LibrePlan page at Facebook.
● LibrePlan Planet. Community members posts at
http://planet.libreplan.org
www.libreplan.com
Bugzilla
● LibrePlan uses bugzilla as issue tracker
● Address: http://bugs.libreplan.org
● Bugs and issues that are not part of a new feature.
● Everybody can register and file a bug about the
project.
● Number of issues since the project start:1553
● Number of bugs open:181
www.libreplan.com
Development in wiki
● We use Twiki with a XPTracker plugin.
● We create two projects: AnalysisLibrePlan and
LibrePlan
● AnalysisLibrePlan XPTracker project:
● http://wiki.libreplan.org/twiki/bin/view/LibrePlan/AnalysisLibrePlan
● The requirements of the features organized by
modules
www.libreplan.com
Development in wiki
● LibrePlan XPTracker project
● Iterations in time.
● We use 1 iteration per release.
● In each iteration the set of user stories developed ongoing.
● Each developers does a public log of his programming work
at the user stories he takes part.
www.libreplan.com
Development in wiki
● LibrePlan XPTracker project
● Each user storie has a set of tasks with an
estimation of time to do, and the developer tracks
the time he devotes.
● Each user story is linked with the analysis story of
the AnalysisLibrePlan XPTracker project where the
requirements and analysis has been written.
www.libreplan.com
Development in wiki
● In LibrePlan the patches have a code referencing:
● If they are a bug fix, the bug number of the ticket in
LibrePlan Bugzilla.
● If they are patches which implement a user story, a
unique code of the user story.
www.libreplan.com
Development in wiki
● LibrePlan XPTracker project
www.libreplan.com
commit dee3588280a22a48411053d06fae1c6627ecad93Author: Manuel Rego Casasnovas <[email protected]>Date: Tue Sep 11 13:25:06 2012 +0200
Implement first version of project status report * Using a DTO to manage the information in the report (ProjectStatusReportDTO) * Add filter by projects in the UI FEA: ItEr77S09WBSReport
Development in wiki
● In the user story in LibrePlan we have programmed a
plugin which gathers automatically all the patches
which implement a user story (query done with the
code in the commit message)
● In LibrePlan we are able to have traceability:
● From commits up to the requirements.
● From the requirement down to the patches.
www.libreplan.com
Meetings
● In LibrePlan community we held periodic twice-
weekly coordination meeting in the #libreplan IRC
channel.
● We review the work done.
● We talk and make the decisions of the next work to
do.
● They are public and the meeting are available for
everybody.www.libreplan.com
Meetings
● Meeting minutes at
http://wiki.libreplan.org/twiki/bin/view/LibrePlan/Meetings
www.libreplan.com
Meetings
● In LibrePlan community we held extraordinary
meetings after each release to define the roadmap for
the next one.
● They are also public
● Everybody interested in the project (contributor or not)
can attend.
www.libreplan.com
Roadmap
● LibrePlan roadmap is public and can be looked up
for everybody interested.
www.libreplan.com