Requesting Suggestions For Maintaining Gemini Integrity (random people putting junk into Gemini)
The way CounterSoft runs their installation of Gemini, is
that any user can create an account and create issues. In our situation, we
would like to emulate that, except add one additional step. The additional step
would be to allow somebody local to "review" the new issue before it
is made public. That way, if somebody creates a bogus or flaming issue, it will
not be made public immediately because it will be deleted by the
"moderator" or project manager.
As it's currently configured, I'm not sure of any way to force an issue to be private, and then somebody with enough privileges changes it to public once they've validated that it is legit.
Any suggestions for implementing a workflow like the above mentioned in Gemini?
dnezamfar
· 1 |
|
Thursday, August 2, 2007, 11:03:51 PM |