[
https://issues.apache.org/jira/browse/SPARK-6889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493651#comment-14493651
]
Sree Vaddi commented on SPARK-6889:
-----------------------------------
That is a lot of text to go through and understand.
The pain points are relevant, only to heavy actives/committers/veterans.
What cannot we possibly have in wiki
(https://cwiki.apache.org/confluence/display/Spark/Wiki+Homepage) than in web
site (http://spark.apache.org) ?
If we look back in Apache's history and how Wiki added to it.
Pain: adding web content is hard and maintaining all those links, etc....
Resolution: Fine, let us have a Wiki.
Not for a moment it was thought nor brought up later, why don't we get rid of
the web page and have wiki, for everything. It would be hard to avoid
duplicate content and confusing to the new comers.
Today, we have duplicate content across the both. Mostly they are out of sync,
all apache projects. {I have been doing at the least, a hello world, on every
apache project, starting from the very first web server}
Similarly, when introducing Git, adding Github and sync both. Even to date,
Github is not an immediate sync with Apache Git. (Sync happens 8hrs, I guess -
correct me, if this changed lately).
And SVN still exists for the web content. Do we need two/three versioning
systems ?
It is not a easy start for any new comer on the apache and other open sources.
If you introduce a long list of reading to them, you are chasing them away.
I would suggest we go 'LEAN' on this.
New Comers Page 1:
Are you a comer ?
- download binary
- install and run
- is hello world successful ?
Good job!
New Comers Page 2:
Do you want to 'try' contribute ? (Yes / I'm feeling lucky)
1.
- web/wiki
spelling this out, attracts the ui/ux, non java and breaks the common notion
that apache is for java people
...here goes a list of tasks under this
2.
- code
...here goes a list of tasks under this
...
...
{time is up. i will provide more details, later.}
> 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
