Alert.png 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"

From EGIWiki
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 6: Line 6:
*Status:  In progress
*Status:  In progress
*Start Date: April 2013  
*Start Date: April 2013  
*Duration: 6 months
*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)


Line 30: Line 30:
== Tasks  ==
== Tasks  ==


List and describe the specific tasks with target dates for completion.
* 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 1 description and target date
* [https://documents.egi.eu/document/1737 Deliverable]
* Deliverable 2 description
 


== Members  ==
== Members  ==


* Member 1 Name and Role in team
Members:
* Member 2 Name and Role in team
* CESNET: mini-project coordinator, EGI central IT services
* SZTAKI: SCI-BUS/SHIWA portal developers
* INFN: IGI portal developers


* Stake holder 1 and reason for interest
* Stake holder 1 and reason for interest




== Emerging Information  ==
== Emerging Information  ==


if relevant - may change the nature and objectives of the project
 
   
   


== Resources  ==
== 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 ==
== 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).
Progress reports are described in [[Overview of Funded Virtual Team projects#(Weekly) Reporting|Weekly reporting]].
 
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.
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
  • 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
Retrieved from "https://wiki.egi.eu/w/index.php?title=VT_Liferay&oldid=59032"