2006-09-28 Project-wide 3:45 BST

Agenda

• Review of last project-wide meeting notes/issues
• Week-in-review
  • Security roundup
    • ticket:365 — do we allow group members to change the permissions of group-writable objects?
    • one-to-many RWRW-- issues
    • ExternalInfo (i.e. LSIDs) — Readability (are permissions active?), updateablity (are they mutable?), deletability (do they hang around after an object is deleted?), etc.
  • Chris' fun with BufferedImages and the RenderingEngine
  • Automatically test on install?
  • Josh Status
  • Shoola Client Strategy for next few weeks
  • Singapore Visit
  • Status of Model Updates
  • Moving towards M4

Notes

• Josh as 3 questions about security and asked for everyone's opinion:
  • if an object is group-writeable should they have permission to change the object to world writeable?
    • (General consensus is to mimic the UNIX behavior).
  • when a sub-object is readable by a user but the higher level object is not, how do we handle the exception?
    • (Suggestion is that we don't allow some of the permission to be directly modified, instead some objects cascade their permissions down to lower objects - this should help to reduce this issue).
    • (We need to find a middle-ground between grouping all permissions at the image level, and allowing users to hang themselves with too many permissions).
    • (We are going to leave ticket 374 open and give Catriona's team time to look at this issue during the user testing stage).
  • Josh has added LSIDs (a details sub-object with owner/group/etc) which is contained in the ExternalInfo object. How should the permissions on this object be set up? Are they updatable? deletable?
    • (we have to define which fields can be modifiable without affecting the model).
    • (Lets table this till we get to the point where we are sharing data in a manner that required LSIDs).
    • (Currently it will remain non-updatable but deletable).
• We have a issue with the way that Java2D deals with images. Unless you deal with packed color integers (doing otherwise makes Java2D too slow). The plan right now is to extend the rendering engine in milestone 4 to give people the ability to use integer arrays to solve this problem. Overall this will effect all our import and display issues.
• Jason predicts he will become a normal person again soon!
• After this next milestone run we'll be ready to move into a new phase of designing and brainstorming!

Action Items

• Keep doing what you're doing!