Grouper Developers Forum

["GW Brown, Information Systems and Computing" <>]

--On 08 February 2005 08:21 -0800 blair christensen <> 
wrote:

> Grouper Call, Wednesday, 09 February 2005, 1200EST (1700Z), 60 minutes
>
>   +1-866-411-0013 (toll free US/Canada Only), or
>   +1-800-392-6130 (alternate toll free US/Canada Only)
>   +1-734-615-7474 (Non-US/CA, non-toll free, no dialout)
>   http://edial.internet2.edu/call/0109331 for SIP
>   PIN: 0109331 (followed by "#")
>
> Agenda:
>
> 1. Intellectual Property Rights Awareness: Internet2 Intellectual
> Property Framework
> <http://members.internet2.edu/intellectualproperty.html>
>
> 2. Agenda Bash
>
> 3. Scheduling Grouper 0.5.1 release
>
>   Tentatively scheduled for the end of February.
>
> 4. Scheduling initial UI release
>
> 5. Grouper 0.6 feature freeze/prioritization and release scheduling
>
>   I will be sending out an updated roadmap (of feature possibilities)
>   before the call.  I believe Gary is working on a minimal 0.6
>   feature set necessary to support the initial UI release.

Below are my priorities for Grouper 0.6. It is based on the assumption that 
0.6 is a pre-production release which would carry a health warning that 
what goes on under the covers is subject to change  - so play but don't get 
too serious just yet.

1) Subject implementation for group and person (including getAttributes() 
or other Signet enhancements). I currently work with a Bristol Subject 
implementation.

2) Search / browse (part 1):
For searching I can live with only searching extension or displayExtension.
Thought needs to be given to how the full search capability is made 
available to the SearchTypeAdapter - a query language? - as this will be 
how other I2MI projects will 'see' groups. It may even be how Grouper 
searches groups?

Numbers below are those from the 'Grouper API Search & Browse Capabilities' 
document

1.      The name, extension, or displayName attributes of groups can be
       searched.

2.      The name, extension, or displayName attributes of namespaces can be
       searched.

7.      A search of the name, extension, or displayName attributes of 
groups
       can be scoped to groups within a namespace subordinate to a given
       stem.

8.      A search of the name, extension, or displayName attributes of
       namespaces can be scoped to namespaces subordinate to a given stem.



3) Delete groups - should delete members for you
4) Remove selected members

5) Full privilege implementation

I think items above are essential. Items below are nice-to-haves, but could 
be included in a later release

6) Rename group

7) Custom group types

8) Search / browse (part 2):

I have put 3 & 4 here because I have a workaround through GrouperBackend
3.      All groups with a given stem can be listed.
4.      All namespaces with a given stem can be listed.

I can live without this initially as I can list groups for which a Subject 
has a privilege and that is sufficient to begin with.
12.  The set of groups or namespaces created or modified by a specified
    subject can be listed.

I think most often I will want to search through the hierarchy from a 
particular point
5.      A search of the extension or displayExtension attributes of groups 

       can be scoped to groups with a given stem.
6.      A search of the extension or displayExtension attributes of
       namespaces can be scoped to namespaces with a given stem.

Searching across names and displayNames.


>   We need to prioritize what goes in when, what needs to be in, what
>   we'd like to have in and what is saved for a later date.
>
> 6. Your Items Here



----------------------
GW Brown, Information Systems and Computing