Minutes
Attendees: Joanne Bogart, Rob Cameron, Eric Charles, Jim Chiang, Richard Dubois, Elizabeth Ferrara, Karen Heidenreich , Tony Johnson, Heather Kelly
We went through the list of items Chuck was maintaining.
Richard gave an overview of what Chuck provided beyond documentation. He provided organization and a "path through the thicket". Offline had gone through at least 3 previous attempts at documenting the software which had all failed. Chuck was very proud of the navigation tools he created where he worked to make all information available within 3 clicks.
The newsletter is done in Dreamweaver. Karen will be taking this over. Richard states that depending on what technologies we choose for other documentation we may transition away from Dreamweaver.
The Picture Gallery is now a maintanence effort and should be fairly straightforward.
ISOC web pages
Rob gave an overview of the ISOC web page status. It includes a news section which will need maintenance. Richard asked how Chuck got the news to report? Rob believes Chuck was keeping an eye on press releases and other notifications that came by. We'll have to find someone to take that on.
Rob also mentioned a pointer to a google site and goggle groups should be linked into ISOC page?
Workbook
Heather went through the items documented below. Richard stated that to his knowledge that two major areas are in flux: standard analysis and analysis threads. Richard asked if Gino or Eric had had a chance to think about where that should go?
Gino: trying to integrate the workbook to what is maintained under Confluence
Last done by Chuck were links to some COnfluence pages - well documented examples. Two main things the workboook should maintain
specific work done in papers, somethinng we discussed and started to do. IF there will be someone who will take care
of the workbook, we can continue to give input, and what is ongoing on Connfluence. To use the workbook as the main
entry point, and then from workbook, then do go into deeper into anlysis areas using Confluence links
Technology issues: will affect the who
Tony
Chuck had his way..all files in CVS, and edited in dreamweaver, and committed to web by running script that commited to web server
the advantages is that it fit his style, and plain html was easy to downloadable, and also makes it easy to mirror
the disadvantages - we don't have expertise in Dreamweaver - the nav scheme is nice and keeping it work is work
maybe consider keeping scheme but
reduce duplication - so don't have to update so many pages when there are changes
can make things more autmoated - but may make mirrors more difficult, or downloadablea
we don't often have to export - but when SLACc is down, it's nice to have.
Nice to have a remote copy available
Jim had some ideas aobut DB driven tools like django
Separate meeting for that perhaps
Could add google ad linux - and google will keep track of who's using what pages maybe whole webisite
Richard: Chuck may have mentioned this once, not sure if he ever did it.
Rob has been big fan of wikipedia approach and open up doc in Confluence and let SMEs have at it, with editorial
guidance this could work.
No real rhyme or reason - need an organizing force - would editorial board have sufficient cycles to do that
Rob: divide and conquer. IF we don't find a single individual to take on the task, then a wiki tool where a group
can maintain the doc. workbook top doesn't scroll - nearest thing confluence woudl have is expandable tree which
persists on left side of the page. A strong editorial board to prevent entropy. and would need to carefully to
consider top level structure and what you are trying to achieve. Could do some analysis of chuck's links to see
what nodes which may map to top level trunks of a tree in Confluence.
Gino - similar to what Eric tried to do with standard analysis page
Rob: maybe predefined formats
Gino: the problem will be to find the people who will take time to do this
Richard; Standard Analysis example may be the easiest example to find people willing to do the job. We also have
thelower level stuff.. scons, gr, sci analysis stuff. Maybe starting with
Connection with FSSC
Rob - see what parts are least stable to see what to tackle first, rather than choosng a single area
there are templates available - with at least soem of nav built in
Elizabeth:
updates to ST are on a specific schedule..so updates come in a single batch. Chuck would post emails to workcvs email list
and that's one way Elizabeth so she knew what changes were in, so she coould determine they affected teh FSSC pages
and if so, make the update. It's not easy from Elizabeth's side to keep track of changes, Getting lots of user
requests, that are reflected in FSSC pages, and
full drop of HTML - it was not the easiest relationship to keep track of - lots of things going on. Wouldlike a
system to communicate things to the FSSC to avoid things falling through the cracks.
The doc is somewhat independent -- new or evolution is independent paths..
outside user community - much of workbook is not addressable in that regard
Gino - commoon doc?
another meeting to allow looking at the details of content to be maintained..where do we need SMEs and identify them?
target as part of the collab meeting?
Rob: sharepoint - maps to a folder and subfolder paradigm
Richard: If we're goin the wiki route - the collab knows Confluence,
esp Microsoft one
Heather, Tony, Jim, and company to look at technologies
and separate group to see who will do it
offline we'll figure that out
complement out to the workbook to provide a way to wean off Chuck's implementation
Rob: need to get the top level view right the first time. Richard thinks Tony will have good ideas to analyze on current
state of the workboook
https://www-glast.stanford.edu/protected/mail/workcvs/
Agenda topics:
- content that needs to be curated
- who will curate
- technology to use (maybe intertwined with the who)
Newsletter
Karen will be taking this on.
Workbook
To Do
- Updates to pointlike documentation will be completed by Joshua Lande.
- New gtgrb tutorial was planned
- Pulsar Analysis tutorials and ObsSim tutorials were up next.
- site-maps need some attention
Need new liaison with FSSC to keep analysis threads updated.
Recently updated "Instrument Analysis" section for SCons. This process is still ongoing, and Joanne will have further items to add. The yellow navbar concerning "Advanced Instrument Analysis" needs to be further merged with the old CMT version.
Updating Doxygen web links for the SCons builds.
Mirror is handled via CVS tags which Berrie then uploads.
Software web pages
Home page: http://glast-ground.slac.stanford.edu/workbook/sas_Home.htm
"In the news" and "Reserve the dates" sections need to be kept up to date.
Check on "Take the workbook with you" link.
Wouldn't hurt to review the current contents to check for any items that may be somewhat obsolete.
ISOC web pages
Picture Gallery
http://www-glast.slac.stanford.edu/PictureGallery/
Seems to be in pretty good shape - perhaps we just need someone to step up to keep it up to date (and take photos?)