[
https://issues.apache.org/jira/browse/SPARK-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496373#comment-14496373
]
Nicholas Chammas commented on SPARK-6889:
-----------------------------------------
{quote}
I think that really the most important change is the cultural one, of pushing
back a little more on jiras & prs, which we'll all need to work on collectively.
{quote}
Completely agreed.
While this work here to get everything down in writing is the first step, I'm
concerned that these docs will be "write-only" docs--as in, they help those of
us here discussing things to organize our thoughts, but they do little to
affect the behaviors we are actually concerned about.
Hence I'd like to re-emphasize the importance of the 2 points from [my previous
comment|https://issues.apache.org/jira/browse/SPARK-6889?focusedCommentId=14493394&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14493394]:
# People will not read all of these docs upfront before contributing. That's a
given. That means we will need to refer people to specific parts of the docs
over and over. This needs to be easy, and that means we need to be able to link
to specific parts as necessary. (With the correct use of headings in the wiki,
this should be easy to do.)
# Reviewers and committers need to buy into the idea of pushing back explicitly
and quickly on changes that aren't a good fit. Things won't actually change
without this. Specifically, we need to see people explicitly voice support for
this change. Sean kinda already started a discussion on the dev list about
this, but it was spun off from the update thread from this JIRA issue. I think
we need a fresh thread dedicated just to this point.
> Streamline contribution process with update to Contribution wiki, JIRA rules
> ----------------------------------------------------------------------------
>
> Key: SPARK-6889
> URL: https://issues.apache.org/jira/browse/SPARK-6889
> Project: Spark
> Issue Type: Improvement
> Components: Documentation
> Reporter: Sean Owen
> Assignee: Sean Owen
> Attachments: ContributingtoSpark.pdf,
> SparkProjectMechanicsChallenges.pdf, faq.html.patch
>
>
> From about 6 months of intimate experience with the Spark JIRA and the
> reality of the JIRA / PR flow, I've observed some challenges, problems and
> growing pains that have begun to encumber the project mechanics. In the
> attached SparkProjectMechanicsChallenges.pdf document, I've collected these
> observations and a few statistics that summarize much of what I've seen. From
> side conversations with several of you, I think some of these will resonate.
> (Read it first for this to make sense.)
> I'd like to improve just one aspect to start: the contribution process. A lot
> of inbound contribution effort gets misdirected, and can burn a lot of cycles
> for everyone, and that's a barrier to scaling up further and to general
> happiness. I'd like to propose for discussion a change to the wiki pages, and
> a change to some JIRA settings.
> *Wiki*
> - Replace
> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark with
> proposed text (NewContributingToSpark.pdf)
> - Delete
> https://cwiki.apache.org/confluence/display/SPARK/Reviewing+and+Merging+Patches
> as it is subsumed by the new text
> - Move the "IDE Setup" section to
> https://cwiki.apache.org/confluence/display/SPARK/Useful+Developer+Tools
> - Delete
> https://cwiki.apache.org/confluence/display/SPARK/Jira+Permissions+Scheme as
> it's a bit out of date and not all that useful
> *JIRA*
> Now:
> Start by removing everyone from the 'Developer' role and add them to
> 'Contributor'. Right now Developer has no permission that Contributor
> doesn't. We may reuse Developer later for some level between Committer and
> Contributor.
> Later, with Apache admin assistance:
> - Make Component and Affects Version required for new JIRAs
> - Set default priority to Minor and type to Question for new JIRAs. If
> defaults aren't changed, by default it can't be that important
> - Only let Committers set Target Version and Fix Version
> - Only let Committers set Blocker Priority
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
