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

Version 1 Next »

Date

Monday, July 18

3:00 - 4:00 PM ET, 2:00 - 3:00 PM CT, 1:00 - 2:00 PM MT, 12:00 PM - 1:00 PM PT

Call-in info is:

Number: 888-354-0094

Access code: 731627

Notetaker: any volunteers?

Attendees: 

Not able to attend:

Goals:

  • Discussion of Github re-organization proposal
  • Choose a chair for 16 -17
  • Update from sub-teams & Program Manager

Agenda items:

Time

Item

Who

Notes

5 min

Roll call and actions from previous meetings

All

Actions:

  • Max Eckard and Patrick Galligan (Unlicensed) - Integrations sub-team to examine the two Github common script repository options a bit further and if they feel ready, set one up.
  • All TAC members  - encouraged to review the draft FAQ document and share your thoughts on an appropriate platform for this type of FAQ.
  • Sally Vermaaten (Unlicensed) - send out Doodle poll for 16/17 call time
  • All TAC members - if you'd like switch sub-teams, email Sally
5 min

Thanks to TAC members for recent listserv contributions:

  • Listserv
  • Code, documentation and bug reporting
Sally Vermaaten (Unlicensed), all

Listserv:

Code and documentation:

Bug reporting:

 

5 minProgram update
BradleyW (Unlicensed)

 

 

5 minChoosing a chair

 

Verbal call for interest in chair position and vote / confirmation. Duties of the chair are described in the bylaws.

30 minDiscussion - ArchivesSpace Github re-organization proposal 
ArchivesSpace Github re-org - draft proposal

Proposed reorganization, which is represented in this spreadsheet and in summary below:

  • archivesspace = as is
  • archivesspace-plugins = official plugin, supported (kept up to date)
  • archivesspace-labs = proof of concepts, examples, experiments etc. no support (may not be up to date). may also be the "community" org?
  • archivesspace-deprecated = was official, now do not use, obsolete 

This structure is used by Fedora, Hydra, and Islandora. Reasons for a plugin org:

  • Single location for all "official" (supported) plugins -- avoids duplication in and out of core.
  • Minor benefit: reduce size of distribution (it's getting over 100mb).
  • Make it obvious what is a plugin.
  • Can have more "open" policy for commit access. Policy TBD (start conversation in committer oversight group).

Also TBD: 

 

1. Promoting developers to committer status. Criteria for core / plugins (labs can be very open).

2. Promoting projects / plugins to official. Criteria needed ...

3. Criteria for deprecating a repo.

Discussion notes:

 

10 minCommitter Oversight sub-team update
Terry Reese (Unlicensed)
 
Technical documentation sub-team update

Ann Cooper (Unlicensed)

 

Features Prioritization sub-team update

Kari S. (Unlicensed) or Christopher Prom (Unlicensed)?

 
Testing sub-team update

Scott Hanrath (Unlicensed) or Noah Huffman?

 
Migration sub-team update
Noah Huffman

 

Bug Wrangler sub-team update
Mark Cooper (Unlicensed)
 
Integrations sub-team update
Max Eckard

 

 Next meeting timeSeptember - date tbc

Please fill out Doodle poll if you have not already done so.

Actions: 

  •  
  • No labels