1. OSG internal review comments Jim Bottum Ewa Deelman Ian Fisk Mark Neubauer March 14, 2014

2. OSG internal review comments Strategy for engaging more users for campuses Identify stakeholders, define their needs, and how they are being met Define a glossary Where does the OSG want to be in 3 years? OSG should define what they want to evolve to and then approach the stakeholders and share the plans. This will allow to drive the effort in the next few years

3. Not clear why OSG wants to expand to campuses and do more outreach to smaller groups LHC computations are bursty, it would be good if the OSG helped deliver such periodic capabilities LHC is looking towards better data management capabilities and elastic use of resources Have focused workshops with stakeholders Feedback from users is missing Need roadmaps showing where the project is going

4. OSG Connect is a step in a good directions Find CIOs that may be interested in working with OSG Needs an advisory function that can connect to the IT department Sell OSG better to the HPC campus providers Follow the Duke model Jim Bottum can help with CIO/campus contacts

5. OSG in the classroom? (course materials and projects online) on-campus connections Improve the website to connect to various user communities/contributors Provide more online outreach/materials Make an analysis of the software stack and what is actually used/ needed

6. Ewa’s additional comments Show more clear impact on domains Success stories, measured impact, page showing publications enabled by OSG Better website, if you are user X, what can you do? Maybe also work with NSF to name OSG in solicitations