meta data for this page
  •  

This is an old revision of the document!

PeerHood Tasks

FIX THE PEERHOOD

There is lot of bugs, mis-usages and design faults. Misuse of the assert. Misuse of the singleton pattern. Status: very open.

Some issues are fixed, like the plugin map with external keyword → a storage for plugins protected with singleton pattern. See commit logs for more information (every change is documented in almost full detail) julaakko

Fix code for GCC 4.3

Most implicit including was cleaned up from GCC 4.3 release. Bad implicit including (relying some include file to include other header) break now building. Status: open.

Most of these were fixed, some might still exist but they do not affect the build. julaakko

Find UML Modeling Tool

As peerhood is underlying functionality providing library and communications system it requires strong design behind it. Also people are coming and going constantly through peerhood project so it is essential people get understanding of the peerhood design. There is required a new uml tool for project use. Status: open, running on background.

DOC++ into build

PeerHood in code documentation was done with doc++ format. Need to establish it into build system. Status: future.

DOC++ is ancient. Better way is to use e.g. doxygen which creates more usable and readable pages. This would require that every function and class documentation is modified to support doxygen's conventions. julaakko

Define Speficifation Document

PeerHood specification (at some degree). By creating core use cases. Candidate work. What are the requirements. Needed use of peerhood (umsic). Status: on work, hevi.

Establish Public PeerHood Web Pages

Research visibility & searchability (google). Status: On work, Porras.

Add deb building

Since there exists a public PeerHood svn (read only) where PeerHood can be downloaded from (synched with PeerHood core), url: https://www2.it.lut.fi/svn/public/peerhood , it would be nice to provide deb-packets for more easier installation of PeerHood.

An idea:

  • Every module (plugins and core) as separate deb
  • Dependencies for each module (libraries), all plugins depend on PeerHood core module
  • Provide these e.g. through public pages / public svn?

This would require that pre-built deb-packets are provided for all environments and devices.

Status: on hold