2. Subjective requirements
Below are some subjective requirements that should be taken into consideration. You may want to discuss some them on the dev_list.
2.1 Is this feature useful?
Consider whether this feature is useful to the current or future WebGUI users. If there are relatively few people for who this is useful: what other reasons are there to include this? If this feature is useful only to some, can it be made in a way that it can be switched off or easily removed, so that it's out of the way of the average user.
2.2 Is this feature usable by the target audience?
Consider who is the target audience? Is it user-friendly for regular users, does a content manager in an avarage business environment have the skills to use it? Or is this directed to system administrators?
2.3 Does it give WebGUI a competitive advantage?
Consider here if you, Plain Black or WebGUI integrators have increased sales or another monetary incentive to include it. And if so: how?
2.4. What are the maintenance costs of it?
Do you expect Plain Black to maintain it after you have contributed this feature or are you going to do that yourself? If you expect Plain Black to maintain it, this weights heavily.
2.5 Does this fit in the direction WebGUI is going?
This may be something you want to discuss on the dev_list, but you can also read the Black Blog, and have a look at the roadmap.
2.6 Is there a similar feature in WebGUI?
If so: could this similar feature be adapted to suit you needs? Or does your contribution have all the features of the existing feature? And if so, is there a way to upgrade?