unstick r1803803

Revision 1803803

Date:
2017/08/02 10:40:14
Author:
kabhwan
Revision Log:
update getting-help to include subscription for issues@
Files:

Legend:

 
Added
 
Removed
 
Modified
  • storm/site/getting-help.md

     
    2 2 layout: default
    3 3 title: Documentation
    4 4 ---
    5 ### Getting help
    5 ## Getting help
    6 6
    7 7 __NOTE:__ The google groups account storm-user@googlegroups.com is now officially deprecated in favor of the Apache-hosted user/dev mailing lists.
    8 8
    9 #### Storm Users
    9 ### Storm Users
    10 10 Storm users should send messages and subscribe to [user@storm.apache.org](mailto:user@storm.apache.org).
    11 11
    12 12 You can subscribe to this list by sending an email to [user-subscribe@storm.apache.org](mailto:user-subscribe@storm.apache.org). Likewise, you can cancel a subscription by sending an email to [user-unsubscribe@storm.apache.org](mailto:user-unsubscribe@storm.apache.org).
    13 13
    14 You can view the archives of the mailing list [here](http://mail-archives.apache.org/mod_mbox/storm-user/).
    14 You can also [browse the archives of the storm-user mailing list](http://mail-archives.apache.org/mod_mbox/storm-user/).
    15 15
    16 #### Storm Developers
    16 ### Storm Developers
    17 17 Storm developers should send messages and subscribe to [dev@storm.apache.org](mailto:dev@storm.apache.org).
    18 18
    19 19 You can subscribe to this list by sending an email to [dev-subscribe@storm.apache.org](mailto:dev-subscribe@storm.apache.org). Likewise, you can cancel a subscription by sending an email to [dev-unsubscribe@storm.apache.org](mailto:dev-unsubscribe@storm.apache.org).
    20 20
    21 You can view the archives of the mailing list [here](http://mail-archives.apache.org/mod_mbox/storm-dev/).
    21 You can also [browse the archives of the storm-dev mailing list](http://mail-archives.apache.org/mod_mbox/storm-dev/).
    22 22
    23 #### Which list should I send/subscribe to?
    24 If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to [user@storm.apache.org](user@storm.apache.org).
    23 Storm developers who would want to track the JIRA issues should subscribe to [issues@storm.apache.org](mailto:issues@storm.apache.org).
    25 24
    26 If you are building storm from source, developing new features, or otherwise hacking storm source code, then [dev@storm.apache.org](dev@storm.apache.org) is more appropriate.
    25 You can subscribe to this list by sending an email to [issues-subscribe@storm.apache.org](mailto:issues-subscribe@storm.apache.org). Likewise, you can cancel a subscription by sending an email to [issues-unsubscribe@storm.apache.org](mailto:issues-unsubscribe@storm.apache.org).
    27 26
    27 You can view the archives of the mailing list [here](http://mail-archives.apache.org/mod_mbox/storm-issues/).
    28
    29 ### Which list should I send/subscribe to?
    30 If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to [user@storm.apache.org](mailto:user@storm.apache.org).
    31
    32 If you are building storm from source, developing new features, or otherwise hacking storm source code, then [dev@storm.apache.org](mailto:dev@storm.apache.org) is more appropriate.
    33
    34 If you are committers and/or PMCs, or contributors looking for following up and participating development of Storm, then you would want to also subscribe [issues@storm.apache.org](issues@storm.apache.org) in addition to [dev@storm.apache.org](dev@storm.apache.org).
    35
    28 36 #### What will happen with storm-user@googlegroups.com?
    29 37 All existing messages will remain archived there, and can be accessed/searched [here](https://groups.google.com/forum/#!forum/storm-user).
    30 38
  • storm/site/publish/getting-help.html

     
    154 154 <h1 class="page-title">Documentation</h1>
    155 155 <div class="row">
    156 156 <div class="col-md-12">
    157 <h3 id="getting-help">Getting help</h3>
    157 <h2 id="getting-help">Getting help</h2>
    158 158
    159 159 <p><strong>NOTE:</strong> The google groups account <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a> is now officially deprecated in favor of the Apache-hosted user/dev mailing lists.</p>
    160 160
    161 <h4 id="storm-users">Storm Users</h4>
    161 <h3 id="storm-users">Storm Users</h3>
    162 162
    163 163 <p>Storm users should send messages and subscribe to <a href="mailto:user@storm.apache.org">user@storm.apache.org</a>.</p>
    164 164
    165 165 <p>You can subscribe to this list by sending an email to <a href="mailto:user-subscribe@storm.apache.org">user-subscribe@storm.apache.org</a>. Likewise, you can cancel a subscription by sending an email to <a href="mailto:user-unsubscribe@storm.apache.org">user-unsubscribe@storm.apache.org</a>.</p>
    166 166
    167 <p>You can view the archives of the mailing list <a href="http://mail-archives.apache.org/mod_mbox/storm-user/">here</a>.</p>
    167 <p>You can also <a href="http://mail-archives.apache.org/mod_mbox/storm-user/">browse the archives of the storm-user mailing list</a>.</p>
    168 168
    169 <h4 id="storm-developers">Storm Developers</h4>
    169 <h3 id="storm-developers">Storm Developers</h3>
    170 170
    171 171 <p>Storm developers should send messages and subscribe to <a href="mailto:dev@storm.apache.org">dev@storm.apache.org</a>.</p>
    172 172
    173 173 <p>You can subscribe to this list by sending an email to <a href="mailto:dev-subscribe@storm.apache.org">dev-subscribe@storm.apache.org</a>. Likewise, you can cancel a subscription by sending an email to <a href="mailto:dev-unsubscribe@storm.apache.org">dev-unsubscribe@storm.apache.org</a>.</p>
    174 174
    175 <p>You can view the archives of the mailing list <a href="http://mail-archives.apache.org/mod_mbox/storm-dev/">here</a>.</p>
    175 <p>You can also <a href="http://mail-archives.apache.org/mod_mbox/storm-dev/">browse the archives of the storm-dev mailing list</a>.</p>
    176 176
    177 <h4 id="which-list-should-i-send-subscribe-to">Which list should I send/subscribe to?</h4>
    177 <p>Storm developers who would want to track the JIRA issues should subscribe to <a href="mailto:issues@storm.apache.org">issues@storm.apache.org</a>.</p>
    178 178
    179 <p>If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to <a href="user@storm.apache.org">user@storm.apache.org</a>. </p>
    179 <p>You can subscribe to this list by sending an email to <a href="mailto:issues-subscribe@storm.apache.org">issues-subscribe@storm.apache.org</a>. Likewise, you can cancel a subscription by sending an email to <a href="mailto:issues-unsubscribe@storm.apache.org">issues-unsubscribe@storm.apache.org</a>.</p>
    180 180
    181 <p>If you are building storm from source, developing new features, or otherwise hacking storm source code, then <a href="dev@storm.apache.org">dev@storm.apache.org</a> is more appropriate. </p>
    181 <p>You can view the archives of the mailing list <a href="http://mail-archives.apache.org/mod_mbox/storm-issues/">here</a>.</p>
    182 182
    183 <h3 id="which-list-should-i-send-subscribe-to">Which list should I send/subscribe to?</h3>
    184
    185 <p>If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to <a href="mailto:user@storm.apache.org">user@storm.apache.org</a>.</p>
    186
    187 <p>If you are building storm from source, developing new features, or otherwise hacking storm source code, then <a href="mailto:dev@storm.apache.org">dev@storm.apache.org</a> is more appropriate.</p>
    188
    189 <p>If you are committers and/or PMCs, or contributors looking for following up and participating development of Storm, then you would want to also subscribe <a href="issues@storm.apache.org">issues@storm.apache.org</a> in addition to <a href="dev@storm.apache.org">dev@storm.apache.org</a>.</p>
    190
    183 191 <h4 id="what-will-happen-with-storm-user-googlegroups-com">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
    184 192
    185 193 <p>All existing messages will remain archived there, and can be accessed/searched <a href="https://groups.google.com/forum/#!forum/storm-user">here</a>.</p>