Notes and Action Items: Ad Hoc Advisory Call of Nov. 6, 2015

  

Attending: Ann, Nick, Nate, Keith, Emily, Tom, Ken, Paul, Jim, Jacob

Regrets: Steve

 
 

New Action Items from Nov. 6 call:

  

[AI] (Ann) update the Ad Hoc Advisory Group charter and remove the preliminary membership that applies to CAPE (DONE)

 
 

[AI] (Emily) create on the wiki start for CAPE’s charter (include a bullet for having representation at international conferences)  (see https://spaces.at.internet2.edu/display/ASWG/CAPE+Charter+Draft )

 
 

[AI] (Ann) continue to update this group on discussions with CIC around launching the Campus Success WG

  

[AI] (Emily) ask  David Walker  to give the Ad Hoc Advisory Group access to the TIER Doc Stewardship Draft proposal document (for discussion on the Friday, Nov. 20 call) (DONE)

 

[AI] (Emily) put on agenda for when SteveZ is on call:

What should the Categories be for the TIER Community Forum? The Component Architects have proposed this list.  

 
 [AI] (SteveZ) draft charter for TIER Instrumentation/Measurement working group; Jacob will also work on it (carry over action item)  
 

Discussion

1. Review TIER WG revised charters and get status updates on:

 APIs WG (Keith)

  • Inaugural Nov. 4 WG meeting agenda with inline notes (http://j.mp/1PWMCp5)

  • Doodle for a UK/EU friendly bi-weekly meeting sent to Refeds: http://doodle.com/poll/e7u5zfaat94xk839 

    • if you’re on pacific time, be sure to vote soon, as most options will require serious caffeine administration

    • two independent bi-weekly series to be as accommodative as possible; mentioned in email, intended for each track to run in parallel

      • tom curious to see how the integration between the two sub-groups will be done

      • might allocate different issues to different segments of the wg

  • University API Unconference #2, at BYU, February, 2016; TIER presence?

    • broad intent in scope: everything a university may want to do

      • seems heavily weighted towards BYU priorities

    • need to decide whether to send someone; keith suggests sending a delegate or two

      • may be ideal if we could get phil windley to report back as he is signed up as a member of the TIER Data Structures and APIS WG, but having someone who is more TIERy would be good -- large group of folks, good feedback

      • Ann: some chance TIER could fund participation

  • Use of GitLab? See https://fed-interop-wg.ligo.org/keith-hazelton/tier-api-wg SteveZ looking into getting an enterprise version for TIER. Also relates to document process. Tools for WG groups to standardize on.

 

 Packaging WG (Jim)

    Only confusion was one point in the document which was “Keep InCommon TAC Up-to-date”, but it’s clearly a TIER working group and reporting goes TIERwards. Jim is going to do a live drive-by COmanaging, and we’ll call it done.Ann & C

  • First Meeting is Monday Nov 9 at 4pm ET

  • May have weekly meetings

 
 

 Security and Audit WG (Tom)

    Tom has talked with Helen Patton. Tom and Helen will talk again next week about Helen chairing the Security and Audit WG

Instrumentation / Measurement WG (SteveZ)

2. Which charters are final and can potentially be shared with the community via pointers in the November TIER community Newsletter?  

  • Security Charter NOT ready to be published yet

  • Packaging WG charter can be published

  • Data Structures and API WG charter can be published

3. When and how should we spin up a Campus Success WG? Is this best done as the product of a technical advisory group like us, or by some other means?

  • Ann & Klara discussed: TCIC prioritized training pretty low on the list for TIER release 1

  • Call with KevinM, ChrisB, KeithW around engaging CIC as a set of core members of the TIER Campus Success WG; support for the idea in the small group on that call; KevinM will take the idea to the CIC CIOs December meeting;

    • Put IAM Assessment tool (recently updated for 2015 CAMP) what online?

  • Mission: adoption, sharing lessons learned, good practices from the adoption phase

  • Education will be part of the mission, not so much marketing & promotion

  • More like early CAMPs

  • The Campus Success should be a community-based effort; those kinds of groups fall under this ICAPE precursor group (TIER-adhoc-advisory)

 
 

4. Insights from TCIC meeting at EDUCAUSE on long-term TIER governance (Internet2 PAG approach)

  • Ann: wasn’t at the meeting but can say what they were looking at; TCIC and InC Steering; used to be a hard line between the two; growing understanding that it’s all intertwingled;

  • TomB has become a member of TCIC representing architecture

  • Internet2 T&I PAG (over Steering and TCIC) is the model that seems to be emerging;

  • Charter for the T&I PAG is in the works

  • PAGS are described here http://www.internet2.edu/vision-initiatives/governance/program-advisory-groups/

  • Challenging from outside to stay clear on what is where

  • TCIC may go away (or evolve into something different) after 3 years, when the TIER investor campuses’ 3 year seed money commitment ends

  • Tension between InCommon’s broader user community and TIERs (initial) R1 focus seems manageable. TIER will evolve to be broader community over time

 
 

5. This Ad Hoc Advisory Group is interim, but should we have a charter? If so, should it be published? Should we expand or change our ad hoc membership?  

  • Probably not needed for internal use, but important for external visibility

    • THE CHARTER FREE GROUP MAKING CHARTERS ;)

  • Suggest a few sentence paragraph Ad Hoc Advisory charter would be the best format for outreach

    • And our biggest work item deliverable is chartering ourselves out of existence

  • Deliverables for Ad Hoc Advisory

    • Act as interim community architecture review for TIER

    • Develop process for engaging the community using working groups

    • Convene initial community working groups

    • Identify TIER collaboration tools to be used across all working groups

    • Liaise with peer advisory and working groups including InCommon Technical Advisory Committee and TIER Component Architects

    • Develop charter for the standing Community Architecture Planning and Engagement - Goals: charter for CAPE in Jan 2016, end this group in March and convene CAPE.

    • [AI] (Ann) will update the charter and remove the preliminary membership (done) 

    • [AI] (Emily) create on the wiki a bullet parking lot for CAPE’s charter (include a bullet for having representation at international conferences) (Done)

 
 

6. The brand under which our lasting products should be published or known: “TIER”, or “Internet2’s TIER activities”, right?

  • TIER it is

 
 

7. What should the Categories be for the TIER Community Forum? The Component Architects have proposed this list.  [AI] (Emily) put on agenda for when SteveZ is on call.

 
 

8. What should be in the TIER Tech corner for the upcoming TIER Newsletter?

  • [AI Keith] add content on API WG include pointer to the charter (Done)

 
 

9. Review Parking Lot of Future Agenda Topics

10. Else?

    Ken: Refactoring among components - issue of local hack being used a several campuses in group management to translate group names into friendly words. How do we think about and tackle these functionalities that may span multiple components? (Note: this was discussed at the Component Architects call on Nov. 9, 2015)

 =========
 


Parking Lot of Future Agenda Topics

  1. Review of David Walker’s TIER Doc Stewardship Draft proposal? See link

  2. CAPE charter 

  3. Campus Success Charter (Ann)

  4. Update from TCIC (Tom)

  5. Local Metadata Manager component conversation should continue; if there is bandwidth in this group, we should look for tooling for consistency in how local sites do this work

  6. translate from geek speak to end user speak, e.g. common-lib-terms; OIDC ‘scope’ discussions; Some of the relevant seed material is in the domain expertise of highly skilled UI designers; common renderings and how they get transported. (note this was discussed on Nov 9 Component Architects call)



  • No labels