Facebook Portlet

Owned by GaryG (Deactivated)
Last updated: Aug 02, 2018 by Jim HelwigVersion comment

Name

Facebook Portlet

Authors

Gary Weaver, Matt Young, Ren Provey, Jen Bourey

Issue Management

http://www.ja-sig.org/issues/browse/FACEPT

Source

https://www.ja-sig.org/svn/sandbox/FacebookPortlet

Price

Free

License

Freeware / Open Source (BSD)

Please contact Gary Weaver directly if you are interested in contributing to this portlet or have specific concerns about this portlet. For uPortal issues, contact the uPortal list.

About this JA-SIG Portlet Project

Originally written in 2007 by Matt Young and Ren Provey of Duke University and presented in the 2007 JA-SIG conference. Updated to v2 by Gary Weaver in 2011 to use the latest Facebook Javascript API.

Requirements for Usage

  • While some modification of this portlet may in use at one or more institutions running an earlier version of uPortal, it may require significant additional work in coding/configuration to be functional.

Features

  • Lets you login/logout of Facebook with a button
  • Show number of user's friend notifications and requests
  • Displays last 5 statuses from friends or followers in the user's news feed (note: may not be the same messages that the user would see in their Facebook news page)
  • Allows user to post status to Facebook

Usage Documentation

Objectives and requirements

Functional

  • Can retrieve facebook information and display information in a user friendly format

Technical

  • Needs review: Is it a standards-compliant JSR-168 portlet? - Not completely, due to Facebook Javascript SDK requirement to have a div with the id "fb-root".
  • Needs review: Does it have what JA-SIG would consider to be modular design and APIs?
  • Needs review: Uses Spring PortletMVC and appropriate Spring practices - think so
  • Builds with Maven
  • Tests: Since primarily javascript, not much benefit in unit testing

Cultural

  • A collaborative open source project under the auspices of JA-SIG
  • Can be used commercially and non-commercially
  • Produces actual production-ready releases, not just a code drop or a project that exclusively lives in SVN - Let us know where the built portlet should go, and we'll put it there. It is ready for use.

Participants

Committers

Committership is a social contract

Commitership in JA-SIG SVN is both a technical fact (having the right account set up in JA-SIG SVN configuration) and a social contract (the understanding and agreement among developers that this person will be committing to some particular portion of JA-SIG shared collaborated-upon source code.) Presently, technically, any member of the "everyone" group is able to commit changes to this portlet project in SVN. That doesn't mean everyone "is a committer" in the sense of committership on this project. Cf., technically, any member of the "everyone" group in JA-SIG SVN is able to commit changes to uPortal, but it would be a surprise and likely inappropriate for an "everyone" member who has never before committed to the uPortal project to make unexpected changes.

Here are enumerated the people believed to be committers for this project:

Open Issues

type key summary reporter status

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Action Items

Action Item

Assignee

Status

Give garysweaver svn commit access

Andrew Petro

Done

Create a sandbox SVN module https://www.ja-sig.org/svn/sandbox/FacebookPortlet

GaryG (Deactivated)

Done

Document intent to move to SVN portlets/ directory as of first RC

GaryG (Deactivated)

Ok with me to move to incubation if accepted

Create child pages of Portlets wiki space for this portlet content

GaryG (Deactivated)

Done

Build out this page with more info

GaryG (Deactivated)

Done

Document this projectlet on the JA-SIG Clearinghouse Contributions page

GaryG (Deactivated)

Is this still applicable?

Create a Jira project in the portlets group

GaryG (Deactivated)

Done

Does this need its own dev and user mailing lists?

GaryG (Deactivated)

No, can use existing portlet-dev, portlet-user, uportal-user lists