SSWG Notes - 2010-10-27
SSWG Notes - 2010-10-27
Web Standards and Browser Recommendations
The Web Standards document has been vetted in small, medium, and large groups and I think most of the SSWG in attendance agree it is ready to be moved to the next level. Bringing it back to the TIF at large seems like an extraneous step. Besides a tweak of language which occurs in most final documents, it seems ready to be moved into the “policy� category. I believe we discussed a link in campus policies to the confluence document was appropriate. If David is in agreement, we should present to those who can make this happen.
One issue Jeremy pointed out was applying these standards to off-the-shelf products which may be more difficult than applications developed in-house. With this document and the accompanying RFP language, I think that will explain to the review committees what standards we are trying to uphold and that they should do their best (a la Cybersafety compliance) to adhere to them when making said purchases. And I think when it comes to software for the whole campus, there should be more input from technical staff at the departmental level (ie those who work more closely with the end users) earlier on in the decision process. Don’t end with general campus input, begin with it.
Standards for .NET Applications
Adam presented the basics of UCDArch, where it is available, and how he is trying to make it the standard framework (if it’s big enough to be called that) for at least the College of Ag and its departmental .NET developers. I think we decided a few things:
- Discuss UCDArch in detail, with examples, at a future ucdotnet SIG with campus .NET programmers in attendance. This will allow campus programmers to become familiar with it, where to find it, and begin the “open source� method of improving and extending it, not to mention actually using it in future applications.
- Possibly use the ucdotnet SIG as the “committee� to vet refinements to UCD Arch. There should be one or two “Linus�-level figures who put the gavel down on new releases: not the decision makers necessarily, but the decision finalizers.
- Create a campus-wide Microsoft Team Foundation Server as a central versioning repository for .NET libraries/apps/etc.
Future Goals
Develop a model for funding and supporting applications over the long term that are campus-wide (such a Timesheets, etc) but not funded by a central source.