[
https://issues.apache.org/jira/browse/STORM-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325144#comment-16325144
]
ASF GitHub Bot commented on STORM-2899:
---------------------------------------
GitHub user srdo opened a pull request:
https://github.com/apache/storm-site/pull/4
STORM-2899: Remove contributors list from people page
See https://issues.apache.org/jira/browse/STORM-2899
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srdo/storm-site STORM-2899
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm-site/pull/4.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4
----
commit 8d66f75a4c6ffb9e505a203aaf514bae877d5f7f
Author: Stig Rohde Døssing <stigdoessing@...>
Date: 2018-01-13T14:05:21Z
STORM-2899: Remove contributors list from people page
----
> Remove/replace the contributors lists in the README and on
> https://storm.apache.org/contribute/People.html
> ----------------------------------------------------------------------------------------------------------
>
> Key: STORM-2899
> URL: https://issues.apache.org/jira/browse/STORM-2899
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Stig Rohde Døssing
> Assignee: Stig Rohde Døssing
> Priority: Trivial
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We've talked a few times on the mailing list about removing or replacing the
> contributors lists, because they are not really being maintained because
> keeping them up to date is a manual process.
> The last time this was discussed
> http://mail-archives.apache.org/mod_mbox/storm-dev/201712.mbox/browser, there
> seemed to be some consensus for using Spark's scripted solution to generate
> the contributors list. It was also suggested that having the contributors
> list at all was maybe unnecessary.
> In order to avoid having this discussion again in a few months, I'll submit a
> PR that removes the contributors list from the README and site, because it's
> the simplest solution in terms of release process (no extra step to generate
> the contributors list).
> If there are strong feelings for using Spark's solution to generate a
> contributors list instead, people will hopefully chime in on the PR review,
> and we can make changes as necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)