Skip to content

Home

Jump to bottom
arivero edited this page May 13, 2011 · 18 revisions

Objetive

Ibervicis Furnivall is an open source framework for distributed volunteer science. It helps to organize batches of tasks, collect them form volunteers and do all the related housekeeping.

A popular similar work is Bossa. Also, Furnivall is heavily inspired in BOINC.

The name

Dr Frederick James Furnivall organized a team of distributed volunteer work to build the Oxford dictionary. Incidentally, he was also the founder of the Furnivall Sculling Club.

Expected output

Furnivall will have:

  • a system of plugins separated from the core, to allow both for expansions and for customisations
  • a way to distribute the core system across sites, allowing for high availability
  • whatever you want. Simply ask a Issue to the tracker, under milestone Improvements.

Development Plan

Stages

  1. Ability to Run single site, with Asociative Paths.
  2. Ability to Run single site, with Vivienda and Sentimiento.
  3. Multiple Site, redundancy, ...
  4. Pluggable. Apps para mapeo de enfermedades (deteccion via twitter?), para migraciones de pájaros, para mapas de ermitas, ....

branch plan. Curators.

Main branch is curated by David until it branches to Associative Paths. Then by Alejandro. Associative Paths is curated by David. Redundancy branch (later in phase 3) is curated by Dario. Sentiment by Francisco. Vivienda by Celestino.

All branches should fuse to master for 1.0 release, sometime in October 2011?

work method

  • A public activity page is to be at http://ibercivis.github.com/Furnivall/ Yes, it is edited in the gh-pages branch.
  • Github issue tracker https://github.com/Ibercivis/Furnivall/issues is to be used for main discussions, up to the level of user histories
  • The core development will use PivotalTracker https://www.pivotaltracker.com/projects/274169 for finer work.
    • Ideally, a Discuss issue (and most others) should move to "Assigned" only when its implications have been translated to the IceBox of Pivotal. Then the Assigned person should be reponsible for the closing in Pivotal and eventually the Closing in Github issue tracker.
    • Pivotal esta enlazado con github de forma que los commit se pueden marcar para que muevan tareas en el pivotal.
  • Documentation, if not in the source code, goes here

Proposals for organization of the system

Interaction between objects

If not marked otherwise, the objects are Instances. Not to be confused with modules nor class objects.

(TO DO: some diagram)

Base Class Diagram

At the moment, inheritance is very basic.

(TO DO: some diagram)

Help

Building UML Diagrams

(for examples of the the YUML tool, hosted at http://yuml.me, see

http://yuml.me/diagram/scruffy/activity/draw http://yuml.me/diagram/scruffy/class/samples http://yuml.me/diagram/scruffy/usecase/draw )

git recipes

git -> pivotal interaction.

Clone this wiki locally