The MFCF -> CSCF Split - Who Does What

The Transition

One's work transition will handled by one's new manager. The following (at least) will need to be determined:

what work is so far along that there's no point in assigning to the person now responsible ?
who will help with new duties ?
who will need help with old duties ?

The Who Does What List

We currently document Who Does What which, for example, is used to help assign incoming work requests. Some updates to the list have been made, influenced by the for

combined with knowing which group people are in; (MFCF or CSCF). More remain. Areas of doubt are emphasized by ?.

The Ongoing Work List (RT)

In addition, we have the practical reality of existing assigned work that will have to be reassigned. The so-called run-on sentence has a selection of anomalies, which now include

are MFCF work not assigned to MFCF
are CS work not assigned to CSCF
are CS non-research work not assigned to a point of contact
are CS research work not assigned to research support

the intent being to make it practical to find the items that will need to be reassigned, typically by picking the appropriate anomaly and selecting a specific person's list.

Our work list is unrealistically long. So when reviewing anomalies to reassign. it's most useful to start with the most recent items. Most of the older items are less relevant, or are done.

Problem Report Handling

Assigning

As we learn who will be doing what in each group, we should start assigning work to the appropriate person. For work that involves a transfer of skills, the person with the needed skills will be second on the list.

For CS, a point of contact (once we know them all) will be the first person on requests directly from faculty.

Newsgroups

It's expected that the

uw.cscf.gripe

and

uw.cscf.announce

newsgroups will exist. uw.cscf.gripe will be used by the `gripe` command on CS machines. Whether additional groups will be created remains to be seen. See RT #40521 for details.