- 625
- 205
I thought about a more organized way to manage the Request Threads: The one who does a calculation, evaluates a calculation or renders an image should give a Kudo to a request in order to say to others persons that he is doing the service requested. This way, the others members of the Calculation Group and Image Helpers won't waste their time doing a request that is going to be done and they will be able to distinguish more easily what request hasn't been taken into account.
This improvement would apply for the process to respond at the following Request Threads:
Calculation Request: A member ask for a calculation. By giving a Kudo to this request, everyone can see who has done or who is going to do the calculation and take another request that has no Kudos.
Calculation Evaluation Request: A member ask for a evaluation. By giving a Kudo to this request, everyone can see who has evaluated the calculation and viewing the number of Kudos on a request as the number of evaluations (one Kudo means one evaluation from a Calculation Group member, two Kudos mean two evaluations from a Calculation Group member, etc...).
Image Renders Request: A member ask for a render of an image. By giving a Kudo to this request, everyone can see who is going to do or who has done the render and take another render request that has no Kudos.
If this idea is approved, then a new rule would potentially be needed concerning Kudos on Request Threads: Only people who intend to respond to a request can give a Kudo to this same request in order to distinguish who is working on the request.
This improvement would apply for the process to respond at the following Request Threads:
Calculation Request: A member ask for a calculation. By giving a Kudo to this request, everyone can see who has done or who is going to do the calculation and take another request that has no Kudos.
Calculation Evaluation Request: A member ask for a evaluation. By giving a Kudo to this request, everyone can see who has evaluated the calculation and viewing the number of Kudos on a request as the number of evaluations (one Kudo means one evaluation from a Calculation Group member, two Kudos mean two evaluations from a Calculation Group member, etc...).
Image Renders Request: A member ask for a render of an image. By giving a Kudo to this request, everyone can see who is going to do or who has done the render and take another render request that has no Kudos.
If this idea is approved, then a new rule would potentially be needed concerning Kudos on Request Threads: Only people who intend to respond to a request can give a Kudo to this same request in order to distinguish who is working on the request.