Difference between revisions of "VT Liferay"
Line 18: | Line 18: | ||
== Objectives == | == Objectives == | ||
This section should be short – it will be limited to stating exactly what the objectives of the project are to be. Ideally it will be aligned which the outcome of the project though frequently the results of a project differ significantly from what was originally intended (and that is not necessarily a bad thing). But a good project will set out with a clear idea of what it is that someone wants the project team to achieve. Note that there may be an ultimate Aim or Goal which is important to know and understand but may not be the aim of this project (eg a study to identify a cause of a disease may be a full project but the ultimate goal is to develop a cure or a prevention). If there is a series of specific deliverables, these can be detailed later. | * A systematic evaluation of Liferay Social Office and Sync | ||
=== Outcomes === | |||
* Best practices and recommendations for the EGI community (particularly for portal-community@mailman.egi.eu) | |||
* Broader uptake of Liferay within EGI: NGIs, projects, institutes, ... | |||
* Updated EGI portals (by mini-project members) | |||
<!-- This section should be short – it will be limited to stating exactly what the objectives of the project are to be. Ideally it will be aligned which the outcome of the project though frequently the results of a project differ significantly from what was originally intended (and that is not necessarily a bad thing). But a good project will set out with a clear idea of what it is that someone wants the project team to achieve. Note that there may be an ultimate Aim or Goal which is important to know and understand but may not be the aim of this project (eg a study to identify a cause of a disease may be a full project but the ultimate goal is to develop a cure or a prevention). If there is a series of specific deliverables, these can be detailed later. --> | |||
== Tasks == | == Tasks == |
Revision as of 15:08, 9 May 2013
General Project Information
- Leader: Martin Kuba (makub@egi.eu)
- Mailing List: liferay-mp-all@mailman.egi.eu
- Meetings: See agendas in this Indico container: https://indico.egi.eu/indico/categoryDisplay.py?categId=95
- Status: In progress
- Start Date: April 2013
- Duration: 6 months
- Customer: EGI portal community (developers, operators and users of portals that interact with EGI services)
Motivation
Web portals, and particularly Liferay based web portals, became the prime choice over the years within EGI when it comes to providing user friendly access to infrastructure services. GLite, Unicore, ARC and desktop grid resources, as well as some of the operational tools are now routinely used via Liferay portals. The first Liferay portals for EGI’s most recent platform, the Cloud Platform, are expected to become available in 2013. The open source Liferay framework also found to be useful by the community for the development of portlets that are portable across various portal frameworks. This mini-project would answer the question "how could Liferay contribute to the success and the sustainability of EGI even more through new, innovative scenarios enabled by the Liferay Social Office and Sync modules?". Based on the project findings the members will extend their Liferay portals with new capabilities outside of the project.
Objectives
- A systematic evaluation of Liferay Social Office and Sync
Outcomes
- Best practices and recommendations for the EGI community (particularly for portal-community@mailman.egi.eu)
- Broader uptake of Liferay within EGI: NGIs, projects, institutes, ...
- Updated EGI portals (by mini-project members)
Tasks
List and describe the specific tasks with target dates for completion.
Outcomes/Deliverables
- Deliverable 1 description and target date
- Deliverable 2 description
Members
- Member 1 Name and Role in team
- Member 2 Name and Role in team
- Stake holder 1 and reason for interest
- Stake holder 1 and reason for interest
Emerging Information
if relevant - may change the nature and objectives of the project
Resources
How is the Project Team to be resourced and how will members work? How much effort will be required from each individual, how will this effort impact contributing organisations? – do not confuse VT participants with stakeholders. VT participants do work for the project – others don’t have to do any work for the project. How will your funds be consumed?
Progress Reporting
How will you measure your progress and how will you report this? To whom? The objective here is to assure others that your project is on track, but if there are problems then this is the path to getting help and more resources (time, funding, effort).
The Project Leader will provide a short emailed progress report on a weekly basis. The report will be due by 17:00 on Fridays and is to contain details of:
- Work achieved that week
- Work planned for next week
- Progress against the goals in the project plan
- Issues that the virtual team leader needs help with (e.g. non-responsive partners, more resources, support from EGI.eu teams, etc.)
The Team project manager will also provide a more comprehensive input for the EGI InSPIRE quarterly reporting.