Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
From: Vladimir Ozerov <vozerov@gridgain.com>
Date: Tue, 19 Sep 2017 12:50:42 +0300
Message-ID: <CAGt6o8nwKfxpn1XXR5mnLY6KXyp96xT5YL+15TpO=pRKXxVhPw@mail.gmail.com>
Subject: Ignite Enhancement Proposal process
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="001a11439dacdbc945055987ca27"
archived-at: Tue, 19 Sep 2017 09:50:47 -0000

--001a11439dacdbc945055987ca27
Content-Type: text/plain; charset="UTF-8"

Igniters,

I'd like to discuss an idea of adding "Enhancement Proposal" concept to our
process. Many other OSS vendors use it with great success ([1], [2], [3],
[4]), so I think we can also benefit from it.

**Motivation**
Ignite project lacks transparency. We have a lot of thoughts and plans in
our heads. Some of them are materialized to tickets and discussions, some
don't. And yet there is no single place where one can understand major
features and challenges of the product for the nearest perspective. We do
not understand our own roadmap.

Another problem is that our WIKI is full of trash - lots and lots of
outdated design documents and discussions.

With Ignite Enhancement Proposal (IEP) process we can move all major
changes to a single place, thus increasing our understanding of the product
and community involvement.

**Proposal**
1) Create separate page on WIKI [5] where process flow will be defined
2) Create sections for active and inactive/rejected proposals
3) Every proposal should have separate page with the following fields:
- ID
- Summary
- Author
- Sponsor/shepherd/etc - committer or PMC member who will help author drive
the process
- Status (DRAFT, ACTIVE, COMPLETED, REJECTED)
- "Motivation" section
- "Description" section where actual design will reside
- "Risks and Assumptions" section
- Links to external resources, dev-list discussions and JIRA tickets
4) Sponsor is responsible for keeping the page up to date
5) Discussions should happen outside of WIKI - on the dev-list or inside
JIRA tickets
6) Relevant JIRA tickets will be tracked with special labels, e.g. "iep-N"
[6]

I created sample page for binary format improvements (still raw enough) [7].

Please share your thoughts.

Vladimir.

[1] https://www.python.org/dev/peps/
[2]
https://hazelcast.atlassian.net/wiki/spaces/COM/pages/27558010/Hazelcast+Enhancement+Proposals
[3] https://github.com/Kotlin/KEEP
[4] https://spark.apache.org/improvement-proposals.html
[5]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73638545
[6] https://issues.apache.org/jira/browse/IGNITE-6057
[7]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-1%3A+Bulk+data+loading+performance+improvements

--001a11439dacdbc945055987ca27--