View Source

The software week goal is to facilitate coordination between communication and collaboration between everyone as we move forward with the transition away from DOE funding for Fermi. FSSC members will be available at SLAC all week for group discussions and one-on-one meetings. In addition to targeted topics, we encourage attendees with broad or cross-cutting interests to join the various discussions. There will be plenty of work, so we'll need everyone to take part in this transition.

Previous Software Week: Winter Software Week 2017 and associated Notes

Dates: September 11-15, 2017

Location: SLAC: Tulare (4th floor SUSB) primary; Toluca (4th floor SUSB) parallel (unavailable Wed 9/13 1:30-2:30)

Remote access: using Zoom - https://stanford.zoom.us/j/824536403

Wifi:

eduroam
visitor network

Onsite Food:

SLAC Cafeteria - 2nd floor SUSB
Starbucks - near the Guest House

Remote Attendance: We encourage everyone to attend the meeting in person. But we are also planning to provide remote access capability for people who cannot attend, but are interested in joining the discussions. Please indicate below if you will need remote access so that we can plan effectively.

Strawman agenda

	Monday	Tuesday	Wednesday	Thursday	Friday
AM	9 AM Tulare	9 AM Tulare	9 AM Tulare	9 AM Tulare	9 AM Tulare
PM		1 PM ISOC with Steve Tether Special Event in ROB 3-4:30 Bldg 48	1:00 - 1:30 ISOC ops (Toluca)	11:15 field trip to IR2 with Tom G 1:00 - 2:30 ISOC ops (Toluca)	2:00 - 2:30 ISOC ops (Toluca)

Attendees

Name	Local or Connecting Remotely?	From	Availability	Topics of Interest
Richard Dubois	local	SLAC	All week (with lots of holes: Mon 10-11; Tues 9-10; Wed: 12:30-2:30; Thurs 8:30-10); Fri 12:30-2:30
Joe Asercion	local	FSSC	All week (and then some)
Tom Stephens	local	FSSC	All week
Heather Kelly	local	SLAC	Through Friday morning about 11 am (missing: Mon 10-11 and 11-noon?)
Alex Reustle	local	FSSC	All week	Sciencetools, Conda, CI, Github, Modularization, Data distribution, data products
Donald Horner	local	FSSC	All week
Matthew Wood	local	SLAC	All week
Tom Glanzman	local	SLAC	Intermittently all week	repro, cmd-line skimmer, and (as an interested bystander) archiver
Joanne Bogart	local	SLAC	All week, possible interruptions	Use (or not) of subrepo; future of RM
Rob Cameron	local	SLAC	All week, with lots of outages
Joe Eggen	local	FSSC	All week
Elizabeth Ferrara	local	FSSC	Through midday Friday
Regina Caputo	local	GSFC	all week
Nicola Omodei	local	SU	Tuesday -> Friday (not Monday) and leaving at 3:15 on Tuesday, Thursday and Friday	Reprocessing, pipeline
Jermey Perkins	local	GSFC	All Week
Brian Van Klaveren	local	SLAC	Unavailable Monday at 11am-12PM, Wednesday 12-2PM, Thursday 10-12PM, maybe others
Giacomo Vianello	local	Stanford	All Week	Conda release
Steve Tether	local	SLAC	All week off and on	ISOC support
Warren Focke	local	SLAC	All Week	L1

Session Blocks

Developer/Release workflow
- GitHub
  - When do we migrate and what do we do in the meantime?
  - To subrepo or not subrepo?
- Jenkins
- Package management
  - Let's try out repoman
  - Where does RM and associated tools fit in?
    - SCons Release Manager Functions and Structure
  - Scons + git integration for tag and commit auto-discovery at compile time
- Conda distributions
  - Anaconda channel
  - recipes
  - Currently using hmake
- Docker/Singularity
- OS support issues
  - Mac?
Migration to Disk Buffer at SLAC
Pipeline Ops Support (running HalfPipe, L1, ASP)
ISOC Support
- Virtualization
- Archiver
ISOC Operations Tasks and Tools
- Monitoring, Trending, Reporting
ScienceTools
- package owners/manager
- Status of ST-User
GlastRelease expertise and migration to GitHub
- External Libraries
Documentation
- Future of the existing workbook
  - Migrate to Confluence or rSt?
Skimmer support
- Skimmer at Slac
Reprocessing (Tom and Nicola)

New ideas, Tabled, to be discussed:

For Continuous Integration, find way to replace human in the loop testing with automated science validation tests (so a computer can do it for you).
- Rewrite the technical verification tests to be fast.
- Write automated Science Validation tests to be fast from the start.
Move thread format from HTML to Markdown or RST
Find better way to update the documentation. (maybe host it on github).