The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "VT Liferay"
Jump to navigation
Jump to search
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== General Project Information == | == General Project Information == | ||
*Leader: | *Leader: Martin Kuba (makub@egi.eu) | ||
*Mailing List: liferay-mp-all@mailman.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 | *Meetings: See agendas in this Indico container: https://indico.egi.eu/indico/categoryDisplay.py?categId=95 | ||
*Status: In progress | *Status: In progress | ||
*Start Date: April 2013 | *Start Date: April 2013 | ||
*Duration: | *Duration: 12 months | ||
*Customer: EGI portal community (developers, operators and users of portals that interact with EGI services) | *Customer: EGI portal community (developers, operators and users of portals that interact with EGI services) | ||
== Motivation == | == Motivation == | ||
The introduction should explain what the issue/problem that needs to be addressed is, the background to the project, the motivation as to why something is being done about it. Go on to explain any other relevant points, including the project mandate - who has directed the formation of the project, what has been defined as the project objective. Who is the project leader/manager, who are the stake holders (this is vitally important as you need to be clear on what it is that is expected of you), who are the recipients of the project output and when is this required by. Describe the formation of the project team (how why and where), the allotted resources (time, people, stuff, money etc). There could be a number of sub paras. You should also make clear that the scope of the task is realistic and that you can achieve it – as such, complete this introduction at the start of the project and re-check it periodically as you progress. | 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. | ||
<!-- The introduction should explain what the issue/problem that needs to be addressed is, the background to the project, the motivation as to why something is being done about it. Go on to explain any other relevant points, including the project mandate - who has directed the formation of the project, what has been defined as the project objective. Who is the project leader/manager, who are the stake holders (this is vitally important as you need to be clear on what it is that is expected of you), who are the recipients of the project output and when is this required by. Describe the formation of the project team (how why and where), the allotted resources (time, people, stuff, money etc). There could be a number of sub paras. You should also make clear that the scope of the task is realistic and that you can achieve it – as such, complete this introduction at the start of the project and re-check it periodically as you progress. --> | |||
== 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 == | ||
* Solution for VRC, VO, NGI, project websites? | |||
* Interoperability with EGI SSO? | |||
* Interoperability with AAI solutions? (e.g. eduGAIN, IDEM-GARR, Umbrella) | |||
* Interoperability with portlets from the community? (SCI-BUS and SHIWA portlets) | |||
* Interoperability with portlets from the community? (IGI portlets) | |||
* Interoperability and alternative to EGI Helpdesk? | |||
* Interoperability and alternative for AppDB? | |||
* Interoperability and alternative for Indico? | |||
* Interoperability and alternative for Wiki? | |||
* Interoperability and alternative for DocDB? (Liferay Sync module) | |||
* Interoperability and alternative for EGI Blog? | |||
==Outcomes/Deliverables == | ==Outcomes/Deliverables == | ||
* Deliverable | * [https://documents.egi.eu/document/1737 Deliverable] | ||
== Members == | == Members == | ||
* | Members: | ||
* | * CESNET: mini-project coordinator, EGI central IT services | ||
* SZTAKI: SCI-BUS/SHIWA portal developers | |||
* INFN: IGI portal developers | |||
== Emerging Information == | == Emerging Information == | ||
== Resources == | == Resources == | ||
== Progress Reporting == | == Progress Reporting == | ||
Progress reports are described in [[Overview of Funded Virtual Team projects#(Weekly) Reporting|Weekly reporting]]. | |||
Progress so far: | |||
* created document temlpate for deliverable | |||
* INFN | |||
** tested the interoperability between Liferay Social Module and their portlets [[File:Liferay-miniproject-IGI-SocialOffice-test.pdf]] | |||
** first tests of integration of Liferay Office module with the portlet developed for IGI Portal | |||
* SZTAKI | |||
** installed a Liferay instance and the social plugin | |||
** started to examine the normal behaviour of the social plugins | |||
** some discussions about future plans | |||
* CESNET | |||
** installed a Liferay instance | |||
** examined interoperabiliy with EGI SSO | |||
** started evaluation for project web sites | |||
[[Category:Virtual_Teams]] | [[Category:Virtual_Teams]] | ||
Latest revision as of 16:22, 12 August 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: 12 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
- Solution for VRC, VO, NGI, project websites?
- Interoperability with EGI SSO?
- Interoperability with AAI solutions? (e.g. eduGAIN, IDEM-GARR, Umbrella)
- Interoperability with portlets from the community? (SCI-BUS and SHIWA portlets)
- Interoperability with portlets from the community? (IGI portlets)
- Interoperability and alternative to EGI Helpdesk?
- Interoperability and alternative for AppDB?
- Interoperability and alternative for Indico?
- Interoperability and alternative for Wiki?
- Interoperability and alternative for DocDB? (Liferay Sync module)
- Interoperability and alternative for EGI Blog?
Outcomes/Deliverables
Members
Members:
- CESNET: mini-project coordinator, EGI central IT services
- SZTAKI: SCI-BUS/SHIWA portal developers
- INFN: IGI portal developers
Emerging Information
Resources
Progress Reporting
Progress reports are described in Weekly reporting.
Progress so far:
- created document temlpate for deliverable
- INFN
- tested the interoperability between Liferay Social Module and their portlets File:Liferay-miniproject-IGI-SocialOffice-test.pdf
- first tests of integration of Liferay Office module with the portlet developed for IGI Portal
- SZTAKI
- installed a Liferay instance and the social plugin
- started to examine the normal behaviour of the social plugins
- some discussions about future plans
- CESNET
- installed a Liferay instance
- examined interoperabiliy with EGI SSO
- started evaluation for project web sites