| The Zaval CE promotes the development of the creative software
- i.e. the software created under the process, which facilitate and
exploit human's creative spirit to the full potential. The works of
the Zaval CE in the area of creating the environment and work process
that promotes new ideas and fresh solutions is published on the site
of the Zaval CE Group.
The bulk of ideas comes from users of the products. Such feedback
is used for enhancing product usefulness. This document describes
basic procedure of feature request communication, review, and response
from Zaval CE.
| Any person with relevant skills in using the product is eligible
to submit a new feature request.
To distinguish new feature from change request (CR), the following
definitions are used:
Change Request (CR) is a request of change of a portion
of the product that does not alter the product form.
New feature is product facility that cannot be produced
with facilities of the current product version without reasonably
substantial modifications or additions.
| The request communication can be done in any acceptable human-readable
form given that the following items are well-identified:
All submissions via electronic mail should be sent directly to the email
addresses that reside on the zaval.org. All other submissions are
not recommended on the basis that alternative means may not offer
enough reliability or may not warrantee enough credentials of sender
and receiving party.
- the sender identity;
- date of the transfer;
- response from the receiving party that a submission has been received;
| The Founders or other respective committee, functioning within
the Zaval CE, will be in charge of reviewing the request. We may reject
the request on the either or the combination of the matters, including
but not limited to, as follows:
Should the reviewing panel reject the request, it must give the reasoning,
why it has rejected it. The reviewing committee may also request additional
information from the requester.
- Requested feature can be reproducted (product learning issue);
- Requested feature is not a new feature, it should be rather
treated as a change-request;
- Requested feature is too specific and may not be of a use to
the user audience at large;
- Requested feature requires substantial development effort.
NO NEW FEATURE FOR THE PRODUCT IS ACCEPTED IF ITS IMPLEMENTITON WILL
NOT COMPLY WITH ANY OF SPECIFICATIONS, RULES AND GUIDELINES, OPENLY
PUBLISHED BY THE ZAVAL CE.
| Review results are communicated to the requested using the same
communication format as used when submitting a request. If a new feature
is accepted, it is included into the product planning. This document
does not define time frame for implementation. Acceptance communication
- Anticipated implementation period and exptected feature availability
- Other information which may be of a use to requester.
| All new features remain the intellectual property of a person(s)
that implements requested feature.