One of my projects this week is writing the proposal for what our group looks like next year, two years out, five years out, etc. What services we're providing, who the primary consumer of these services are (devs, administrative users, other scientists, external collaborators? Which divisions use which share?), what services we can introduce, what extra support we can provide, etc.
As part of this, I'm identifying what services we should move to CIS (some of this driven by pressure from above), what services we can look at moving to external hosting providers (RT, for instance, should ALCF want to stick with it), and what we'll continue to provide internally because it's simply the best option.
While I enthusiastically welcome input on all of this, there's one area where I'm actively seeking input: what services do we want to simply retire? The one that comes immediately to mind is Bugzilla. What else is there? And, for anything you suggest, please give me a skeleton of an idea as to how we retire it? For instance, is it something we retire because there's just not enough usage to justify the effort? Is it something for which there's a better service we already provide that handles it (Bugzilla falls in this camp.)? What do you think the transition looks like?
Let me know, thanks!
--
Craig
