Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 58 Next »

Meeting moderated by ~edalquist

The following agenda is a rough schedule for the meeting. The times are meant to give a guide for the flow of the meeting and will probably change slightly during the course of the meeting to account for differing levels of interest in the topics.

Monday, March 21

08:15am

Unicon Office Open

 

09:00am

Introduction

~edalquist

09:15am

uPortal 2.4 Performance and Memory

~battags

09:55am

uPortal 2.4.x, Future Releases, Branch Maintenance

~awp9

10:10am

uPortal 2.x and Spring

~awp9

10:30am

Morning Break

 

10:45am

DLM Integration

~mboyd

11:25am

uPortal 2.5 Release Issues

~edalquist

11:45am

Release QA

~edalquist

12:00pm

Lunch Break

 

01:00pm

Clearinghouse Involvment and direction

~edalquist

01:20pm

Documentation

~jaf30@cornell.edu

01:50pm

Sakai Integration

~awp9 and
Chuck Severance

02:40pm

Afternoon Break

 

02:45pm

uPortal 2.6 presentation

~awp9

03:25pm

Permissions Framework

~kstacks

04:00pm

End of day

 

Tuesday, March 22

Wednesday, March 23

schedule TDB

Coding session

Thursday, March 24

schedule TDB

Coding session

Friday, March 25

schedule TDB

Coding session

General Topic Outline:

  • uPortal 2.4.x Status
    • Performance Issues - ~battags
      • Memory Leaks
      • Profiling
    • More 2.4.x releases? - ~awp9
      • Discuss the possibility of maintaining more than one patched branch.
  • uPortal 2.5 Status - ~edalquist
    • Features of this release and status of those features
      • PersonDirectory Service re-factoring and the use of Spring in 2.X - ~awp9
      • DLM Integration - ~mboyd
      • RDBMServices
      • XML API move to JAXP
      • Portlet support enhancements
        • Expiration based caching
        • Render parameter persistence
        • Redirect & WindowState changes during action
    • Release happens within a couple weeks after this meeting
      • Are there any critical issues blocking the release?
      • Are there issues we need to push back to make our release?
      • Who will be in charge of the release?
      • Thread pool re-write using JDK1.5 compatability library
  • Release quality assurance
    • Status of JUnit tests in 2
    • JUnit standards and documentation
    • Status of running the HEAD
  • Documentation - ~jaf30@cornell.edu
  • Role of the JASIG Clearing House
  • uPortal 2.6 - ~awp9
    • Yes, there will be a uPortal 2.6
      • October 2005 expected release
    • Release theme - uPortal 2.5 has as its theme "Aggregated Layouts revisited" and by the time of this meeting we will know what kind of success that theme has been. What will the theme be for the 2.6 release?
      • Marrying Aggregated Layouts and DLM?
      • Product Maturity: making uPortal more stable, better documented, easier to configure and deploy?
      • Other ideas?
    • Release content
      • uPortal 2.6 will contain resolution of issues that are posted into JIRA, scheduled for 2.6, and resolved before the 2.6 cut date.
      • What bug fixes and local enhancements are you maintaining that you'd like to see in baseline uPortal?
    • Permissions - ~kstacks
      • Fine-grained permission grants and grant restrictions (user attributes and groups)
      • Runtime updates to PAGS
  • uPortal 3 Progress - ~pkharchenko
    • Project Roadmap is on Jira
    • Rendering components and contexts
      • Trees: structuring rendering paths
      • Filters: building up content
      • Context component pattern
      • uP2 context configuration example
    • Pluto implementation - ~edalquist
    • Layout Managers
      • Simple user layout manager
      • ALM plans
    • WSRP consumer & producer - ~mvi@immagic.com
    • Navigation & State
      • Back button support: what is the desired functionality?
      • Session Replication
    • Development items & responsibility
      • Authentication (acegi, OSID)
      • integration of uP2 modules
        • Groups & permissions
        • Directory service
        • DbLoader
      • Channel adapter
      • Portlet development
        • Providing portal services to portlets
        • general approach: existing frameworks, current developments, custom options
        • administrative portlet(s): developing flexible and uniform management UIs
      • QA & Testing
        • Need to get time commitments from community to participate in QA and testing efforts
  • Leadership Responsibilities
    • Release manager(s)
    • jasig-dev mailing list approval
    • CVS commit access approval
    • Decision making
  • No labels