Description
An opportunity for the exchange of ideas as well as suggestions for future directions for OSG with respect to the collective VO's.
Please see below for the topics of discussion:
- How does your VO provide dynamic and ad hoc requirements to OSG, and is this process effective?
- How should OSG get engaged for sustaining your VO?
- Is your VO's interest well represented in OSG? If not, any suggestions for improvement?
- Best practices for attracting and retaining users. E.g., how to engage users of local HPC for using the grid.
- Resource discovery tools
- Tools/techniques to better allow troubleshooting and resolution of the many components of the OSG software stack
- How can we improve installation and end user documentation?
- Accounting tools
- What does "supporting a particular VO" mean for a site?
- How can a VO ensure that a particular site supports the needs of its users?
- What is the required list of software? (There are several "optional" components that are actually required to run, so
why are they optional)
- Potential funding opportunities