Developer Information

The LiquidPub Project code is hosted in our Subversion repository. To browse the latest version of the project modules, point your web browser to https://dev.liquidpub.org/svn/liquidpub. You may also find useful information in the External References at the end of this page.

To simply browse through the codebase, a modern web browser is all that's required. However, if you want to checkout some or all the of the project modules we suggest you to use a Subversion compatible client (see http://wiki.liquidpub.org/mediawiki/index.php/Development_tools#SVN for a list).

You will be asked to provide account credentials for accessing the repository content: if you are not a registered LiquidPub project collaborator, simply enter guest account informations:

lp-guest

lp-password

Please keep in mind that several areas inside the repository cannot be accessed with the guest account: if you think you deserve access to some restricted areas, you will have to get a registered account. We will evaluate your request according to project access policies.

Source and documentation

The source code is open to anybody who would like to read it. To post your own modifications, you will need commit access to the repository. For instructions, see the Collaboration section, below. For the documentation on tools please see Tools section, below.

Collaboration

Please see LiquidPub Development Guidelines. Comments welcome.

There are many ways to become a project collaborator:

• You can provide us feedback about bugs, post comments, or suggest new features you would like to be added. You can do this by opening a new ticket in the project-related TRAC server, using New ticket link. Please have a look at this short manual of submitting bugs before opening a ticket.
  
• If can improve our code, either by fixing a bug or by adding a new feature, you could send us a code patch by attaching it to the corresponding TRAC ticket (see previous point).
  
• If you want to become more deeply involved in LiquidPub software development, you will need to get commit access to our repository. Please send an email to our administrator (passamani AT disi.unitn.it) asking to become a project developer.
• Subscribe to the to LiquidPub project developers mailing list to get in touch with project developers. In order to subscribe, follow the instructions at this page:
  
  
  http://disi.unitn.it/mailman/listinfo/liquidpub-dev
  
  (Subscription is free). Mailing list messages are meant to convey information about project development, i.e., requirement analysis, code writing, software configuration, etc. It's not intended as a mean to collect bug tracking related information: if this is the case, please refer to the first point of this list.
  
• You can use or help in development of one of our tools (see below)
  

Tools

• Gelee - a prototype of a tool for lifecycle management of resources 
• ResEval - a tool that allows one to calculate scientific metrics (e.g., h-index) of an author
• GroupComparison - a tool for creating and comparing groups of researchers
• Reputation module - a part of ResEval responsible for calculating reputations of researchers and contributions
• ResMan - resource space management prototype
• Karaku - LiquidPub platform core services, exposed through a REST Interface
• CET - a desktop tool for the detection and analysis of Scientific Community Structure
  
• Demo (aka scientific dashboard) - a tool for providing support for most common tasks of a researcher. Currently it is a mockup, but "Performance->Impact Analysis" tab is working and shows personal research metrics.
  

External references

• SVN and development repository (use guest account to access in read-only mode): https://dev.liquidpub.org/svn/liquidpub
• TRAC server related to the project: https://dev.liquidpub.org/trac/liquidpub
• LiquidPub Development Guidelines: http://wiki.liquidpub.org/mediawiki/index.php/Development_Guidelines 
• Startup instructions for the demo on http://wiki.liquidpub.org/mediawiki/index.php/Demo_startup_instructions