(back to the list of all DMLT meeting minutes)

NOTE: For this meeting and future dates we are conducting the meeting on Blue Jeans (use web browser or below):

> Connecting directly from a room system?

> 1) Dial: 199.48.152.152 or bjn.vc
> 2) Enter Meeting ID: 293724745 -or- use the pairing code

 
> Just want to dial in? (all numbers)
> 1) Direct-dial with my iPhone or 
> +1 408 740 7256+1 408 740 7256 
> +1 888 240 2560+1 888 240 2560 (US Toll Free)
> +1 408 317 9253+1 408 317 9253 (Alternate Number)

> 2) Enter Meeting ID: 293724745

Date

Attendees

(sorry if I missed anyone)

Absent:

 

Goals
  • Weekly coordination meeting to discuss and resolve management items, project communications, external contacts, etc.

Discussion items

 

Item
Who
Notes
Videoconferencing 

BlueJeans vs. GoToMeeting (vs. Zoom)

BlueJeans is coming from AURA, but we've seen some negatives:

  • BlueJeans audio with phone or mobile app can be very bad
  • Connects well with Polycom but can sometimes have significant lag
  • Screensharing on BlueJeans can have artifacts/poor quality
  • Only some people will be able to create meetings

Frossie to check out quality of BJ at IPAC and see if anything can be improved.

Need to make a decision soon whether we want additional BJ features.

LSST 2015 MeetingJeff Kantor
Registration is open. Tuesday and Wednesday are devoted mostly to DM-specific sessions. Plan to use available slots on Monday and Thursday afternoon and Friday morning as possible. Some people will have conflict with Cadence workshop and hackathon. System Engineering will hold plenary/project wide session Monday afternoon on Verification and Validation and Monday 11:00  am to 12:30 pm Operations session. DM Leaders are expected at both. All suggestions for topics should be posted to confluence page:
New hires joining after the All Hands are allowed to have travel to All Hands paid by the project.
  • Tim Jenness to check with Laurie about whether we book our own hotel; if we do, it's the Hampton Inn (360) 405-0200; reserve under the name "LSST 2015 Project".

LDM-240 updates

Kian-Tat Lim

Kian-Tat Lim will review last draft this week, suggest any mandatory updates, freeze for conversion to JIRA. T/CAMs should be prepared to enter the entries in their rows of LDM-240 into JIRA the week of June 1 if possible, but no later than . This will be followed by a review of the whole picture; the deadline for completion of a new version of LDM-240 in JIRA is .

Latest integration by Gregory Dubois-Felsmann is in confluence: LDM-240 updates, Spring 2015 and uploaded as the latest (non-preferred) version on Docushare (see http://ls.st/ldm-240*). Note that the current preferred version in Docushare is internal version v26 of March 19th, 2015.

Once in JIRA, the DMLT will continue to review, identify dependencies, ensure explanations, clarity of milestones, meta-epics, epics, etc.

Xiuqin will be moving a few things into the next cycle as items are transferred to the DLP project in JIRA.

Frossie will be fleshing out SQuaRE dependencies on Thursday with GPDF (and advice from KTL).

Jim will be discussing priorities with KTL before he leaves Wed AM.

Simon will discuss priorities with KTL Wed AM.

If T/CAMs find resource issues (too much work in too little time for available personnel), they should bring those up with KTL.

Development ProcessKian-Tat Lim

Remind developers: if you're merging to master, be around to fix it if it breaks.  Force-building your branch first is recommended.  Things will get easier as the CI system improves.

Python standard will be rewritten as "PEP-8 with deltas" to make compliance and compliance checking easier.

Cross-team code reviews?

  • Code can be specialized; maybe do only within Apps and Middleware levels
  • Maybe have a program auto-select a short list of potential reviewers or else have reviews go to someone (multiple someones) to reassign
FY16 budgets and staffing assumptions

Jeff Kantor

Jeff Kantor and Kevin Long are preparing material week of May 26, for discussion with T/CAMs week of June 1.

Miscellaneous reminders to T/CAMsJeff Kantor
Please keep providing updates to hiring page, FYI, email coming that will ask for diversity stats (report in December, mid-year update)
Please submit MPR narratives, estimated actuals by June 15 this month.
We need to identify a schedule and dates for monthly "topic discussions" for T/CAMs such as documentation, JIRA - EV process updates, etc. We should pick a regular day of the month.
Jeff Kantor will be on vacation June 12 - June 28, working at UW June 29 - July 3.
Solar System Science collaboration meeting at UW last weekMario Juric

How many asteroids will we find?

NEO community is mostly concerned with finding asteroids in one night for re-observation the next night; we're looking at data from up to two weeks to discover asteroids. This has led to some erroneous conclusions about our strategy and prospects.

They seem somewhat appeased, but this may continue to be an issue.

Upcoming eventsKian-Tat Lim
  • Butler brain-dump Tuesday 12:30 PM PT
  • Qserv sprint demo Wednesday 12 noon PT
  • IVOA meeting preparation call (start to collect LSST requirements) Wednesday 2 PM PT
Technical discussions RFC-53 - Getting issue details... STATUS  

Waiting on GPDF (and any others) to confirm a time

Conference/meeting reportsTim Jenness

Where should these be placed?

Since they may include frank comments and product evaluations, they should be in a non-public place.  DocuShare seems like the best default.

  • Tim Jenness to ask Rob McKercher where to put them in DocuShare, creating a new collection if necessary.

 Action items

See above.


1 Comment

  1. LDM-240 considerations

    • Shall we make the current version (internal v33, Docushare version 19) the preferred version in Docushare?  Currently the mid-March version (v26) is the preferred version.  Issues: v33 is considerably more accurate; neither v26 nor v33 have been subjected to a full cost-impact analysis compared to the previous baseline.
    • It would be good to exercise the script process for making a spreadsheet out of the JIRA/DLP contents soon after the June 15th deadline Jeff Kantor stated for the data entry from v33 to JIRA/DLP, so that we can do some proofing of the migration.
    • The dependency information in v33 of LDM-240 is definitely in need of revision and expansion.
    • Will we be trying to generate a new baseline in Docushare around the end of June?