Subject: | |
From: | |
Reply To: | |
Date: | Thu, 18 Nov 2010 11:49:26 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Bruce,
I think that this is a great idea. Doing this has great potential for Pilot participants and for those working on Sakai for the roll-out and future.
Amy
-----Original Message-----
From: IT Services Sakai Team [mailto:[log in to unmask]] On Behalf Of Bruce D'Arcus
Sent: Thursday, November 18, 2010 11:04 AM
To: [log in to unmask]
Subject: on use cases, best practices, etc.
So I know I'm not the only one that has wondered about this, but ...
In the course of discussions on the new pilot list, it strikes me that
some questions are presenting "this is what I need to do" use cases
and requirements of sorts, and asking for how best to achieve those
goals in Sakai now.
I'm wondering if this doesn't provide an opportunity to kill two birds
with one stone:
1. documenting best practices now
2. gathering more forward looking requirements language that we can
feed into the OAE development process to make sure it covers our needs
longer term
So is there plan for documenting these? For example, should there be
an issue in Jira for "peer review best practices"? Should we use the
confluence wiki to document these? Should we use the forum?
Bruce
--
Bruce D'Arcus
Associate Professor, Graduate Director
Department of Geography
Miami University
234 Shideler Hall
Oxford, Ohio 45056
|
|
|