Hi,

I keep thinking how to organize us during the
hackathon week. How about something like this:

  * We start at 9:00, all together, 1h intro
    ("how qserv fits into LSST DM") by KT,
    plus few min for logistics

  * then we split into smaller groups, ideally
    2 people per group, max 3, and we work in
    parallel as described below until 4:00pm

  * 4:00-5:00pm, all back together, discuss what
    we achieved, obstacles we run into, plan for
    next day etc. After 5 - your choice :)

The parallel tracks:

  * divide into exactly 1 hour slots, keep the
    tracks in sync

  * two parallel tracks: A and B, occasionally
    add C if needed

  * track A (Daniel in charge)
    A1 outside world <--> controller
    A2 query processing module <-- all the rest (big!)
    A3 frontend <--> worker
    A4 query results: worker --> frontend

  * track B (Jacek in charge)
    B1 data loading: DDL
    B2 data loading: initial loading (into empty tables)
    B3 data loading: internal publishing
    B4 data loading: adding to non-empty tables,
       and fixing problems "found by SDQA"
    B5 data loading: publishing data

  * random topics to pick from for track C
    - admin cluster mgmt
    - access control
    - validating query syntax and result correctness
    - end to end automated testing
    - build system
    - packaging
    - unit testing
    - Python / c++

  * every hour we have a chance to reshuffle (but
    don't have to)

  * to maintain continuity, at least 1 person from
    A must stay in the next A session, and at least
    one person from B must stay in the next B session

  * We don't necessary have to finish A1 in the 1st
    hour, A2 in the 2nd hour etc, instead we switch
    when it makes sense, with a goal to go over all
    A's and B's before 4:00pm (person in charge is
    responsible to make it happen)

  * during each 1h session the first 10-15 min
    is used to catch up what was done so far
    if someone "new" just (re-)joined

  * it'd be good if we mix a bit, eg, I want Daniel
    and Serge to be in at least one B session
    (each at a different time). I will join at least
    one A session. I am not sure if Fabrice and Douglas
    want to be in A at all. If not, they can occasionally
    jump to track C and pull Daniel, Serge, KT, Bill
    or me. I want us to mix in unusual ways, eg, if
    Serge never worked with Fabrice, or Douglas with
    Bill, they should try get together!

  * After day one, we decide if we want to continue
    using that style. I'd not be surprised if we
    wanted to do another pass through all or most
    of the above topics on Tuesday

Thing about it and let me know your thoughts...
I think we can achieve really a lot in that week
if we find a way to maximize our productivity
while we are all together.

Have a nice weekend :)
Jacek

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1