Hi,
I'm going to go out on limb here.
What do you guys think, if we'd set up a "issue tracking" system for AIDA education. I quickly prototyped one here:
http://jome.homelinux.net/codetrack/
for login use instructor/feedback
Now the idea is simply that instructors would be able to create "issues" in education. Then the ec will pick them up and update the life cycle status as they process the issue.
It will save a history of changes and display the status of each issue.
It's actually an software used for tracking bugs in software projects, but I think with a little tweaking should work fine for things like:
-education system/material
-rules
-mistakes in AIDA web page (wrong name spelling etc)
Please consider this absolutely unofficial, but give it a try and comment?
I think something like this would offer some transparency.
Ie. all instructors would at least know that:
-the issue was raised
-it was or was not processed by the ec (if the status is unchanged for very long, they can kindly remind us to do something about it)
-what the outcome was and how the ec reached that conclusion
-and the whole thing would be stored and a history of issues maintained, so in 2 years for example we might face the same request so we can show directly that this was already processed - and if needed open it up again.
P.S - I thought it to be such a grand idea I created a similar bug tracking thingy on the AIDA ranking page. So if you have issues with it, please use that (link is on the bottom of the page).