Stephan Hesmer and Jonathan Booth have
open sourced a new project, called Theme
PAA for IBM WebSphere Portal which
provides access to the Portal 8.5 Theme as a PAA
(Portal Application Archive) deliverable. Below is their description. Stephan
also blogged
recently about the theme enhancements in 8.5.
"This project provides access to
the IBM WebSphere Portal 8.5 Theme as a PAA deliverable.
The Theme PAA is a great tool to quickly
get started with your own theme as well as a great tool to demonstrate
how you can package up your theme in a PAA for staging to production purposes.
Additionally this Theme PAA demonstrates two theme modes: WebDAV and WAR
file. It contains two separate themes and even though they look 100% identical,
they are deployed once using the WebDAV repository and once using a second
WAR file for static resources. Both themes that come with the PAA are equivalent
in function.
Once the two themes are installed you
can start to customize them and adapt them to your needs. For more information
on theme customization please look here."
"We have created an application
called “Change Tracking for IBM Domino Directory”. As the name indicates,
the application tracks the changes in person and group documents in the
IBM Domino Directory. The application reports what has changed, who has
made the change and when the change has happened.
The application works for IBM Domino
version 6 to 9 as well as in hybrid IBM SmartCloud Notes environments."
The entire OpenNTF.org community was shocked
last week to learn about the death of Tim Tripcony. Tim was a prolific
contributor to OpenNTF.org, both with his own projects and his collaboration
on the XPages Extension Library and the OpenNTF.org Domino API. Tim was
a big supporter of open source and the IBM XPages community. His death
touches every one of us personally.
In an effort to remember Tim’s amazing
contributions to our community, the OpenNTF.org board would like to invite
everyone to share #codefortim – starting right now. What is #codefortim
? It’s an effort for everyone to contribute their knowledge and passion
– something Tim did better than anyone – as a lasting memorial. We have
a few suggestions on how you can get involved.
First, Tim has a few uncompleted projects
on Github and Bitbucket. His projects will be audited and more information
will be posted. The goal is to complete these projects and publish them
to OpenNTF.org. As these projects are published, we ask you do the following:
1. Include Tim as a contributor. The
OpenNTF.org IP Working Group Chairman will include Tim in the project
2. Include #codefortim in your project
description
3. Include Tim’s name and #codefortim
in the licensing document required for a project release.
We realize that Tim’s projects aren’t
something everyone has the time or skill to undertake, so we are asking
that anyone who wants to contribute projects or snippets use the #codefortim
tag in the project description. If you would like to contribute content
in other ways, such as recording a video for David Leedy for Notesin9 as
part of this community effort or write an entry on your own blog, that’s
great as well. The goal here isn’t to worry about the mechanism, but to
leverage Tim’s spirit. Please tag your content with #codefortim.
Tim was one of the most giving and warm
members of our community. The best way we can remember him and say goodbye
is to build on his legacy. Tim will be missed as one of the best teachers.
And as one of the best friends. We miss you Tim.
The OpenNTF.org Board
Tim’s projects on GitHub
are here. We suggest looking
at oauth4domino and his personal org.opentf.xsp.extlib.
Tim’s projects on Bitbucket
are here.
On OpenNTF: User Rename Readiness Tool for IBM SmartCloud Notes
J Rajenderan and Shankar Venkatachalam
have contributed a new project called User
Rename Readiness Tool for IBM SmartCloud Notes.
The tool helps to rename user names, for example when people got married,
in both the on premises applications and IBM SmartCloud Notes. Below is
the description from J Rajenderan and Shankar Venkatachalam. You can find
out more by reading the documentation.
"What is this tool and when is
it to be used?
This tool is programmed to look at the
relevant on-premise artifacts and report back to the customer on the readiness
for carrying out a rename for a selected user.
This tool is to be run prior to a rename
being carried out for a user by a customer, whereby the appropriate checks
are made to the customer's On Premise artifacts to ensure that the rename
does not fail at a later stage thereby, avoiding many PMRs and issues that
we and customer's face on the rename issues and avoid getting them in the
funky state they find themselves in today.
How does this help?
Ensures that rename failures are avoided
by pro-actively checking whether the user is ready for a rename before
a rename action is carried out. This means many PMRs avoided, more customer
awareness, more customer confidence of our service, lesser customer hindrances/
frustrations/ pain etc."