Eric,
This is a great list and just the sort of thing I wish I was doing - but
don't ever get to. Assuming these have not all been completed yet or
there are more to do... Could you post an updated list to the
unconference wiki site? It's possible I or others will have time to
knock some of them off next week.
I am also unclear as to whether there will be any formal uPortal
developers meeting next week or whether the topics will be fit in to the
self organizing portions. I am currently planning to stay through Wed.
Are other uP developers?
Susan
Eric Dalquist wrote:
There are a few bit-sized tasks that interested folks could take on for
the uPortal 3 effort and a few not so bit-sized tasks that can be done
in a fairly parallel manner.
In order from smallest to largest (in my quick review) here are some
tasks that would be great to get some help with:
Switch to stand-alone PersonDirectory library:
http://www.ja-sig.org/issues/browse/UP-1827
This is likely the easiest as it is a near drop-in replacement for the
existing Spring configured person directory code and since the PersonDir
static service will be removed little legacy support code will need to
be written.
Switch to stand-along Groups and Permissions library:
http://www.ja-sig.org/issues/browse/UP-1828
This should be a fairly straight forward replacement for the APIs but
there will be some work involved in ensuring database configurations are
correct and the GAP code has more contact points with the framework than
person directory so it will likely take a bit longer.
Switch to Spring-LDAP in place of ldap.xml/ldap.properties:
http://www.ja-sig.org/issues/browse/UP-1841
There will be some work here in determining the best way for uPortal to
utilize the DataSource style objects Spring-LDAP provides. It shouldn't
be difficult to figure out but there will be some code changes in places
that use the existing LdapServices class.
Switch to Acegi for security: http://www.ja-sig.org/issues/browse/UP-1840
This is probably one of the largest changes that can be done in a fairly
parallel effort. The goal would be to replace as much of the custom
authentication/authorization code in uPortal with Acegi. This would
completely replace security.properties and likely some of the uPortal
ties to GAP.
I will be more than happy to provide as much support as needed to anyone
who wants to take on any of this work. The PersonDirectory and GAP work
is firmly planned for 3.0 but the Spring-LDAP and Acegi work is optional
depending on available time so the more help we get with these the
better chance of them all making it into 3.0
Thanks,
-Eric
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
