You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "Chitral Verma (Jira)" <ji...@apache.org> on 2020/06/17 06:46:00 UTC
[jira] [Assigned] (GRIFFIN-317) Define guidelines for Griffin
Project Improvement Proposals (GPIP)
[ https://issues.apache.org/jira/browse/GRIFFIN-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chitral Verma reassigned GRIFFIN-317:
-------------------------------------
Assignee: Chitral Verma
> Define guidelines for Griffin Project Improvement Proposals (GPIP)
> ------------------------------------------------------------------
>
> Key: GRIFFIN-317
> URL: https://issues.apache.org/jira/browse/GRIFFIN-317
> Project: Griffin
> Issue Type: Improvement
> Reporter: Chitral Verma
> Assignee: Chitral Verma
> Priority: Major
> Fix For: 0.6.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Taking inspiration from Apache Spark, this ticket aims to define guidelines for Griffin Project Improvement Proposals (GPIP).
> The purpose of a GPIP is to inform and involve the user community in major improvements to the Apache Griffin codebase throughout the development process, to increase the likelihood that user needs are met.
> A GPIP aims to discuss the design and implementation of major features and changes in a collaborative manner. These major features must not be small/ incremental/ wide-scoped, as these features can be resolved by normal Jira process.
>
> Requires thorough review from PMC members and committers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)