Wisc has an overlay on that (the MyUW Notifications Portlet) • Each tier has an overlay • Declaring version of the MyUW Notifications Portlet • Tier-specific special sauce, configuration, etc.
done. • But it’s not done for some other meaning of done. • (Note that this is necessarily true no matter what you decide done means for you.) • So now you have technical debt. Maybe a little. Maybe a lot. • And eventually Codethulu awakes from its deep slumber and eats you and your team.
uPortal • Merge Jasig/uPortal/master to MyUW/uPortal/uw- master as needed and at Jasig tags • MUM changes also usually go into Jasig/uPortal/ master, and then need merged / conflict-resolved back into uw-master • Even with git magic, this is kind of painful and friction-adding
requests are good. • How many to do where? • Pull requests within the team are good. • Pull requests in the context of the open source project are good.
Dependencies and overlays (?) rather than forking • Engineer the uPortal source and build • Smaller, cohesive components with well-defined relationships via APIs • Automation, frequency for releases • Monthly patch release and yearly feature release?