[
https://issues.apache.org/jira/browse/SPARK-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493775#comment-14493775
]
Sean Owen commented on SPARK-6889:
----------------------------------
[~pwendell] Yeah, Affects Version only makes sense for bugs. I'll edit that.
Yes the JIRA changes all depend on what's possible.
[~vanzin] Yes I was hoping to think of "Target Version" as a proxy for
"accepted" then.
[~nchammas] I'm for making the contribution guide more visible. Ideally a link
to it can somehow be, say, the default Description text in a JIRA so people are
forced to encounter it on the path where it matters. Also, it can be more
prominent in the CONTRIBUTING.md which does pop up when you open a PR.
(I'm reminded to copy the "all contributions are licensed under AL2" text to
the wiki too)
Yes one feature of the new proposed text is that the "how to open a JIRA" comes
after everything else like "gain experience reading the list first". It is a
goal to push homework onto contributors.
I also agree that most projects don't say "no" enough and it's actually bad for
everyone. Yes, one goal was to also set more expectation that lots of changes
are rejected. If there is widespread agreement, I'd also like firmer language
in the guide. As you say it is also a matter of taste and culture, but, I'd
personally favor a lot more "no".
[~sree_at_ch...@yahoo.com] This content could also live on the web site, but it
means editing raw HTML. It's easier to update the wiki, so content that changes
semi-regularly is often hosted on the wiki. Since all things can be hyperlinked
together, I don't find this a problem, not one to address here.
I don't think this guide is duplicated on the main site, but, you remind me
that the "contribution" section in http://spark.apache.org/faq.html should also
simply point to this wiki.
The rest of your points are specific to Apache. The Apache web site uses SVN
and we can't change that; it's not a Spark issue. Apache requires using
Apache-hosted git but you can sync; the sync is flaky, but, when working syncs
in minutes. I also think the Apache infrastructure is a burden but it's not a
Spark issue.
I think the rest here is a bit of a broader question that's not entirely
on-topic here. Bluntly, I do not think Spark suffers from scaring away valuable
contributions, but from inviting too many uninformed contributions. I disagree
with your premise and the thrust of this change is the opposite.
> 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
>
>
> 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: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
