iced
One solution is to have a time frame within a year for submitting extensions. An example of such is between January to March. After that timeframe no submission is allowed till the following timeframe. This allows moderators/staff to work on approving extensions after the time frame... (in this example, from April to December).

This way everyone knows when they have to submit extensions and when there will be an answer. This is the strategy that "steambans" uses for gamers who submit see more demos of hackers on their website.

You can also make this solution a little bit complex.

A. Standard users get a timeframe of "first 3 months of the year"

B. Contributors/Pundits/Staff get "first 4/5 months of the year".

Also to allow for transparency, there should be a status page/display that shows how many extensions are being reviewed and how many extensions have been (or are being)

1. refused
2. accepted
3. queued for approval

This solution allows for transparancy, and incentivises ppl.

.....

Back to my lunch... :)
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.038543939590454