[jira] [Assigned] (BEAM-7532) Beam Website Publish workflow is consistently timing out since last week.
[
https://issues.apache.org/jira/browse/BEAM-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Melissa Pashniak reassigned BEAM-7532:
--
Assignee: Udi Meiri (was: Melissa Pashniak)
> Beam Website Publish workflow is consistently timing out since last week.
> --
>
> Key: BEAM-7532
> URL: https://issues.apache.org/jira/browse/BEAM-7532
> Project: Beam
> Issue Type: Bug
> Components: website
>Reporter: Valentyn Tymofieiev
>Assignee: Udi Meiri
>Priority: Major
>
> https://builds.apache.org/job/beam_PostCommit_Website_Publish/2868/console
> {noformat}
> 09:50:57 > Task :website:createDockerContainer
> 09:50:58
> 09:50:58 > Task :website:startDockerContainer
> 09:50:58 71b54f49f9766072cae5130debe4eb71088226929c62ad42b4bef7df99b48a7e
> 09:51:28
> 09:51:28 > Task :website:setupDockerContainer
> 10:20:45 Build timed out (after 30 minutes). Marking the build as aborted.
> 10:20:45 Build was aborted
> 10:20:45 > Task :website:setupDockerContainer FAILED
> {noformat}
> Hi [~alanmyrvold], do you think you could help triage this?
> Thank you!
>
> cc: [~kenn] [~altay] [~lcwik]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (BEAM-7532) Beam Website Publish workflow is consistently timing out since last week.
[
https://issues.apache.org/jira/browse/BEAM-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863247#comment-16863247
]
Melissa Pashniak commented on BEAM-7532:
I'm afraid I have no idea, I wasn't involved in building the container stuff.
[~udim] do you remember who set this up?
> Beam Website Publish workflow is consistently timing out since last week.
> --
>
> Key: BEAM-7532
> URL: https://issues.apache.org/jira/browse/BEAM-7532
> Project: Beam
> Issue Type: Bug
> Components: website
>Reporter: Valentyn Tymofieiev
>Assignee: Melissa Pashniak
>Priority: Major
>
> https://builds.apache.org/job/beam_PostCommit_Website_Publish/2868/console
> {noformat}
> 09:50:57 > Task :website:createDockerContainer
> 09:50:58
> 09:50:58 > Task :website:startDockerContainer
> 09:50:58 71b54f49f9766072cae5130debe4eb71088226929c62ad42b4bef7df99b48a7e
> 09:51:28
> 09:51:28 > Task :website:setupDockerContainer
> 10:20:45 Build timed out (after 30 minutes). Marking the build as aborted.
> 10:20:45 Build was aborted
> 10:20:45 > Task :website:setupDockerContainer FAILED
> {noformat}
> Hi [~alanmyrvold], do you think you could help triage this?
> Thank you!
>
> cc: [~kenn] [~altay] [~lcwik]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (BEAM-2103) Document Python 3 support in Beam starting from 2.14.0
[ https://issues.apache.org/jira/browse/BEAM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858083#comment-16858083 ] Melissa Pashniak commented on BEAM-2103: The docs are generally updated just after the release is officially out (as to not confuse people with website changes that only apply to a version that isn't released yet), so setting it blocking to 2.14.0 might cause issues during the blocking issue check for release. Rose can help change this for 2.14.0. > Document Python 3 support in Beam starting from 2.14.0 > -- > > Key: BEAM-2103 > URL: https://issues.apache.org/jira/browse/BEAM-2103 > Project: Beam > Issue Type: Sub-task > Components: sdk-py-core, website >Affects Versions: 0.6.0 >Reporter: Tobias Kaymak >Assignee: Rose Nguyen >Priority: Blocker > Fix For: 2.14.0 > > > Beam website documentation should mention Python 3.5 - 3.7 support in > addition to Python 2.7. Available user documentation (e.g. quickstarts) > should be adjusted where needed, to accommodate for Beam Python 3 users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-2103) Document Python 3 support in Beam starting from 2.14.0
[ https://issues.apache.org/jira/browse/BEAM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-2103: -- Assignee: Rose Nguyen (was: Melissa Pashniak) > Document Python 3 support in Beam starting from 2.14.0 > -- > > Key: BEAM-2103 > URL: https://issues.apache.org/jira/browse/BEAM-2103 > Project: Beam > Issue Type: Sub-task > Components: sdk-py-core, website >Affects Versions: 0.6.0 >Reporter: Tobias Kaymak >Assignee: Rose Nguyen >Priority: Blocker > Fix For: 2.14.0 > > > Beam website documentation should mention Python 3.5 - 3.7 support in > addition to Python 2.7. Available user documentation (e.g. quickstarts) > should be adjusted where needed, to accommodate for Beam Python 3 users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-7456) Expand Link next to tables in capability matrix hard to see
[ https://issues.apache.org/jira/browse/BEAM-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855328#comment-16855328 ] Melissa Pashniak commented on BEAM-7456: >From email, as a possible pointer of where to look to change this: Yeah, people's eyes likely jump to the big "What is being computed?" header first and skip the small font "expand details" (that's what my eyes did anyway!) Even just moving the expand/collapse to be AFTER the header of the table (or down to the next line) and making the font bigger might help a lot. And maybe making the text more explicit: "Click to expand for more details". I'm traveling right now so can't take an in-depth look, but this might be doable by changing the order of things in [1] and the font size in [2]. I'll add this info to the JIRA also. [1] [https://github.com/apache/beam/blame/master/website/src/_includes/capability-matrix.md#L18] [2] [https://github.com/apache/beam/blob/master/website/src/_sass/capability-matrix.scss#L130] > Expand Link next to tables in capability matrix hard to see > --- > > Key: BEAM-7456 > URL: https://issues.apache.org/jira/browse/BEAM-7456 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Reza ardeshir rokni >Priority: Trivial > > Expand Link next to tables in capability matrix hard to see. Would be great > to make it easier to see that it is a clickable link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7456) Expand Link next to tables in capability matrix hard to see
[ https://issues.apache.org/jira/browse/BEAM-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7456: --- Status: Open (was: Triage Needed) > Expand Link next to tables in capability matrix hard to see > --- > > Key: BEAM-7456 > URL: https://issues.apache.org/jira/browse/BEAM-7456 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Reza ardeshir rokni >Priority: Trivial > > Expand Link next to tables in capability matrix hard to see. Would be great > to make it easier to see that it is a clickable link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7399) Publishing a blog post about looping timers.
[ https://issues.apache.org/jira/browse/BEAM-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7399: --- Status: Open (was: Triage Needed) > Publishing a blog post about looping timers. > - > > Key: BEAM-7399 > URL: https://issues.apache.org/jira/browse/BEAM-7399 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Reza ardeshir rokni >Assignee: Reza ardeshir rokni >Priority: Trivial > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7391) Colab examples for other transforms (Python)
[ https://issues.apache.org/jira/browse/BEAM-7391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7391: --- Status: Open (was: Triage Needed) > Colab examples for other transforms (Python) > > > Key: BEAM-7391 > URL: https://issues.apache.org/jira/browse/BEAM-7391 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Rose Nguyen >Assignee: David Cavazos >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7392) Colab examples for connector transforms (Python)
[ https://issues.apache.org/jira/browse/BEAM-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7392: --- Status: Open (was: Triage Needed) > Colab examples for connector transforms (Python) > > > Key: BEAM-7392 > URL: https://issues.apache.org/jira/browse/BEAM-7392 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Rose Nguyen >Assignee: David Cavazos >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7390) Colab examples for aggregation transforms (Python)
[ https://issues.apache.org/jira/browse/BEAM-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7390: --- Status: Open (was: Triage Needed) > Colab examples for aggregation transforms (Python) > -- > > Key: BEAM-7390 > URL: https://issues.apache.org/jira/browse/BEAM-7390 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Rose Nguyen >Assignee: David Cavazos >Priority: Minor > > Merge aggregation Colabs into the transform catalog -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7389) Colab examples for element-wise transforms (Python)
[ https://issues.apache.org/jira/browse/BEAM-7389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7389: --- Status: Open (was: Triage Needed) > Colab examples for element-wise transforms (Python) > --- > > Key: BEAM-7389 > URL: https://issues.apache.org/jira/browse/BEAM-7389 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Rose Nguyen >Assignee: David Cavazos >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7419) Add steps to run the examples in mobile gaming walkthrough
[ https://issues.apache.org/jira/browse/BEAM-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7419: --- Status: Open (was: Triage Needed) > Add steps to run the examples in mobile gaming walkthrough > -- > > Key: BEAM-7419 > URL: https://issues.apache.org/jira/browse/BEAM-7419 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Priority: Minor > > Good info here: > [https://stackoverflow.com/questions/56269102/whats-the-commands-to-run-the-apache-beam-mobile-gaming-tutorials/56283823#56283823] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-7419) Add steps to run the examples in mobile gaming walkthrough
Melissa Pashniak created BEAM-7419: -- Summary: Add steps to run the examples in mobile gaming walkthrough Key: BEAM-7419 URL: https://issues.apache.org/jira/browse/BEAM-7419 Project: Beam Issue Type: Improvement Components: website Reporter: Melissa Pashniak Good info here: [https://stackoverflow.com/questions/56269102/whats-the-commands-to-run-the-apache-beam-mobile-gaming-tutorials/56283823#56283823] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-7034) Add sample code for reading query results with the BigQuery storage API
[ https://issues.apache.org/jira/browse/BEAM-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-7034: -- Assignee: David Cavazos (was: Melissa Pashniak) > Add sample code for reading query results with the BigQuery storage API > --- > > Key: BEAM-7034 > URL: https://issues.apache.org/jira/browse/BEAM-7034 > Project: Beam > Issue Type: Task > Components: io-java-gcp >Affects Versions: 2.13.0 >Reporter: Kenneth Jung >Assignee: David Cavazos >Priority: Minor > > Now that BigQueryIO supports reading BigQuery query results using the storage > API, we should add sample code to illustrate this use case. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-7281) Update Python dependencies page
[ https://issues.apache.org/jira/browse/BEAM-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-7281. Resolution: Fixed Fix Version/s: Not applicable > Update Python dependencies page > --- > > Key: BEAM-7281 > URL: https://issues.apache.org/jira/browse/BEAM-7281 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-7281) Update Python dependencies page
Melissa Pashniak created BEAM-7281: -- Summary: Update Python dependencies page Key: BEAM-7281 URL: https://issues.apache.org/jira/browse/BEAM-7281 Project: Beam Issue Type: Improvement Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7281) Update Python dependencies page
[ https://issues.apache.org/jira/browse/BEAM-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7281: --- Status: Open (was: Triage Needed) > Update Python dependencies page > --- > > Key: BEAM-7281 > URL: https://issues.apache.org/jira/browse/BEAM-7281 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-7231) Add Bigtable to Python supported Beam connectors doc
[ https://issues.apache.org/jira/browse/BEAM-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-7231. Resolution: Fixed Fix Version/s: Not applicable > Add Bigtable to Python supported Beam connectors doc > > > Key: BEAM-7231 > URL: https://issues.apache.org/jira/browse/BEAM-7231 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Rose Nguyen >Assignee: Rose Nguyen >Priority: Minor > Fix For: Not applicable > > Time Spent: 10m > Remaining Estimate: 0h > > Adding Bigtable to Python supported Beam connectors -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-7231) Add Bigtable to Python supported Beam connectors doc
[ https://issues.apache.org/jira/browse/BEAM-7231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-7231: --- Status: Open (was: Triage Needed) > Add Bigtable to Python supported Beam connectors doc > > > Key: BEAM-7231 > URL: https://issues.apache.org/jira/browse/BEAM-7231 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Rose Nguyen >Assignee: Rose Nguyen >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Adding Bigtable to Python supported Beam connectors -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-7119) Nexmark link broken (404)
[ https://issues.apache.org/jira/browse/BEAM-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16822157#comment-16822157 ] Melissa Pashniak commented on BEAM-7119: [~iemejia] oh, I missed that PR, thanks for the heads up! shall I go ahead and close this issue, or do you want to reuse it for that PR? > Nexmark link broken (404) > - > > Key: BEAM-7119 > URL: https://issues.apache.org/jira/browse/BEAM-7119 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > > Page: /documentation/sdks/java/testing/nexmark/ > Link: [http://datalab.cs.pdx.edu/niagaraST/NEXMark/] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-7119) Nexmark link broken (404)
[ https://issues.apache.org/jira/browse/BEAM-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16822150#comment-16822150 ] Melissa Pashniak commented on BEAM-7119: Hi [~echauchot] - [http://datalab.cs.pdx.edu/niagaraST/NEXMark/] has disappeared (seems the whole datalab.cs.pdx.edu site actually is gone) . Do you have any suggestions on what to change it to? I could just remove the link, but am wondering if changing it to something like this might be more useful, if it is applicable? [https://www.academia.edu/20262751/NEXMark_-_A_Benchmark_for_Queries_over_Data_Streams_DRAFT] > Nexmark link broken (404) > - > > Key: BEAM-7119 > URL: https://issues.apache.org/jira/browse/BEAM-7119 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > > Page: /documentation/sdks/java/testing/nexmark/ > Link: [http://datalab.cs.pdx.edu/niagaraST/NEXMark/] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-7119) Nexmark link broken (404)
[ https://issues.apache.org/jira/browse/BEAM-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-7119: -- Assignee: Melissa Pashniak > Nexmark link broken (404) > - > > Key: BEAM-7119 > URL: https://issues.apache.org/jira/browse/BEAM-7119 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > > Page: /documentation/sdks/java/testing/nexmark/ > Link: [http://datalab.cs.pdx.edu/niagaraST/NEXMark/] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-7119) Nexmark link broken (404)
Melissa Pashniak created BEAM-7119: -- Summary: Nexmark link broken (404) Key: BEAM-7119 URL: https://issues.apache.org/jira/browse/BEAM-7119 Project: Beam Issue Type: Bug Components: website Reporter: Melissa Pashniak Page: /documentation/sdks/java/testing/nexmark/ Link: [http://datalab.cs.pdx.edu/niagaraST/NEXMark/] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-5278) feature-branches.md orphaned
[ https://issues.apache.org/jira/browse/BEAM-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-5278. Resolution: Fixed Fix Version/s: Not applicable Got it, going to resolve this then > feature-branches.md orphaned > > > Key: BEAM-5278 > URL: https://issues.apache.org/jira/browse/BEAM-5278 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Udi Meiri >Priority: Critical > Fix For: Not applicable > > > https://github.com/apache/beam-site/blob/asf-site/src/contribute/feature-branches.md > References to this page were removed in > https://github.com/apache/beam-site/pull/438 > It seems it should have been deleted in that PR, but there's no other > explanation of feature branches on the website, while the main contribution > page (https://beam.apache.org/contribute/) lists 4 feature branches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-4373) Inconsistent unit of time references
[ https://issues.apache.org/jira/browse/BEAM-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-4373: -- Assignee: Cyrus Maden > Inconsistent unit of time references > > > Key: BEAM-4373 > URL: https://issues.apache.org/jira/browse/BEAM-4373 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Joseph Toth >Assignee: Cyrus Maden >Priority: Major > > h3. [https://beam.apache.org/documentation/programming-guide/#windowing] > The documentation here reference units in minutes when it should be seconds > everywhere. > 7.3. Setting your PCollection’s windowing function > > I took a look at to see the doc says units are seconds. > https://github.com/apache/beam/blob/bbabb4202cdbe234ab7be9a1cda57f0e8e226357/sdks/python/apache_beam/transforms/window.py#L378 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-5278) feature-branches.md orphaned
[ https://issues.apache.org/jira/browse/BEAM-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819469#comment-16819469 ] Melissa Pashniak commented on BEAM-5278: I can't see the page in the old repo anymore, but is [https://beam.apache.org/contribute/feature-branches/] (that's linked from contribute) the same thing? unsure if this is fixed or still needs more work. > feature-branches.md orphaned > > > Key: BEAM-5278 > URL: https://issues.apache.org/jira/browse/BEAM-5278 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Udi Meiri >Priority: Critical > > https://github.com/apache/beam-site/blob/asf-site/src/contribute/feature-branches.md > References to this page were removed in > https://github.com/apache/beam-site/pull/438 > It seems it should have been deleted in that PR, but there's no other > explanation of feature branches on the website, while the main contribution > page (https://beam.apache.org/contribute/) lists 4 feature branches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-666) Add accurate "How to Run" instructions for each of the WC examples
[ https://issues.apache.org/jira/browse/BEAM-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-666. --- Resolution: Fixed Fix Version/s: Not applicable Closing out old fixed issues > Add accurate "How to Run" instructions for each of the WC examples > -- > > Key: BEAM-666 > URL: https://issues.apache.org/jira/browse/BEAM-666 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Hadar Hod >Assignee: Hadar Hod >Priority: Major > Labels: triaged > Fix For: Not applicable > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-2350) Instructions for how to run WordCount using Spark runner
[ https://issues.apache.org/jira/browse/BEAM-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-2350. Resolution: Fixed Fix Version/s: Not applicable Closing out old fixed issues > Instructions for how to run WordCount using Spark runner > > > Key: BEAM-2350 > URL: https://issues.apache.org/jira/browse/BEAM-2350 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Hadar Hod >Priority: Major > Fix For: Not applicable > > > See https://beam.apache.org/get-started/wordcount-example/ > Verify correctness or provide directions for "How to run using Spark runner" > for ALL 4 WordCount examples in Java and (if applicable) in Python. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-2349) Instructions for how to run WordCount using Apex runner
[ https://issues.apache.org/jira/browse/BEAM-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-2349. Resolution: Fixed Fix Version/s: Not applicable Closing out old fixed issues > Instructions for how to run WordCount using Apex runner > --- > > Key: BEAM-2349 > URL: https://issues.apache.org/jira/browse/BEAM-2349 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Hadar Hod >Priority: Major > Fix For: Not applicable > > > See https://beam.apache.org/get-started/wordcount-example/ > Verify correctness or provide directions for "How to run using Apex runner" > for ALL 4 WordCount examples in Java and (if applicable) in Python. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-2976) investigate/add WordCount walkthrough testing section for Python
[ https://issues.apache.org/jira/browse/BEAM-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-2976: -- Assignee: (was: Melissa Pashniak) > investigate/add WordCount walkthrough testing section for Python > > > Key: BEAM-2976 > URL: https://issues.apache.org/jira/browse/BEAM-2976 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Priority: Major > Labels: triaged > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-2978) add custom window Fn section in programming guide
[ https://issues.apache.org/jira/browse/BEAM-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-2978: -- Assignee: (was: Melissa Pashniak) > add custom window Fn section in programming guide > - > > Key: BEAM-2978 > URL: https://issues.apache.org/jira/browse/BEAM-2978 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Priority: Major > Labels: triaged > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-6975) Merge portability status into capability matrix
[ https://issues.apache.org/jira/browse/BEAM-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816790#comment-16816790 ] Melissa Pashniak commented on BEAM-6975: Unassigning as I'm not actively working on this > Merge portability status into capability matrix > --- > > Key: BEAM-6975 > URL: https://issues.apache.org/jira/browse/BEAM-6975 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Ahmet Altay >Priority: Major > > Should the portability status: > https://s.apache.org/apache-beam-portability-support-table > be merged into capability matrix > https://beam.apache.org/documentation/runners/capability-matrix/ ? > (That is add portable runners to the list of runners as columns in the > capability matrix.) > cc: [~kenn] [~lcwik] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-6975) Merge portability status into capability matrix
[ https://issues.apache.org/jira/browse/BEAM-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-6975: -- Assignee: (was: Melissa Pashniak) > Merge portability status into capability matrix > --- > > Key: BEAM-6975 > URL: https://issues.apache.org/jira/browse/BEAM-6975 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Ahmet Altay >Priority: Major > > Should the portability status: > https://s.apache.org/apache-beam-portability-support-table > be merged into capability matrix > https://beam.apache.org/documentation/runners/capability-matrix/ ? > (That is add portable runners to the list of runners as columns in the > capability matrix.) > cc: [~kenn] [~lcwik] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-2348) Instructions for how to run WordCount using direct runner
[ https://issues.apache.org/jira/browse/BEAM-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-2348. Resolution: Fixed Fix Version/s: Not applicable > Instructions for how to run WordCount using direct runner > - > > Key: BEAM-2348 > URL: https://issues.apache.org/jira/browse/BEAM-2348 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Hadar Hod >Assignee: Melissa Pashniak >Priority: Major > Fix For: Not applicable > > > See https://beam.apache.org/get-started/wordcount-example/ > Verify correctness or provide directions for "How to run using direct runner" > for ALL 4 WordCount examples in Java and (if applicable) in Python. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-2351) Instructions for how to run WordCount using Dataflow runner
[ https://issues.apache.org/jira/browse/BEAM-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-2351. Resolution: Fixed Fix Version/s: Not applicable All Dataflow tabs have commands now > Instructions for how to run WordCount using Dataflow runner > --- > > Key: BEAM-2351 > URL: https://issues.apache.org/jira/browse/BEAM-2351 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Hadar Hod >Assignee: Melissa Pashniak >Priority: Major > Fix For: Not applicable > > > See https://beam.apache.org/get-started/wordcount-example/ > Verify correctness or provide directions for "How to run using Dataflow > runner" for ALL 4 WordCount examples in Java and (if applicable) in Python. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-2348) Instructions for how to run WordCount using direct runner
[ https://issues.apache.org/jira/browse/BEAM-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-2348: -- Assignee: Melissa Pashniak > Instructions for how to run WordCount using direct runner > - > > Key: BEAM-2348 > URL: https://issues.apache.org/jira/browse/BEAM-2348 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Hadar Hod >Assignee: Melissa Pashniak >Priority: Major > > See https://beam.apache.org/get-started/wordcount-example/ > Verify correctness or provide directions for "How to run using direct runner" > for ALL 4 WordCount examples in Java and (if applicable) in Python. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-2351) Instructions for how to run WordCount using Dataflow runner
[ https://issues.apache.org/jira/browse/BEAM-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-2351: -- Assignee: Melissa Pashniak > Instructions for how to run WordCount using Dataflow runner > --- > > Key: BEAM-2351 > URL: https://issues.apache.org/jira/browse/BEAM-2351 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Hadar Hod >Assignee: Melissa Pashniak >Priority: Major > > See https://beam.apache.org/get-started/wordcount-example/ > Verify correctness or provide directions for "How to run using Dataflow > runner" for ALL 4 WordCount examples in Java and (if applicable) in Python. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-6827) Update Python dependencies page for 2.10.0, 2.11.0
[ https://issues.apache.org/jira/browse/BEAM-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-6827. Resolution: Fixed Fix Version/s: Not applicable > Update Python dependencies page for 2.10.0, 2.11.0 > -- > > Key: BEAM-6827 > URL: https://issues.apache.org/jira/browse/BEAM-6827 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-6749) Add BigQuery Storage API info to docs
[ https://issues.apache.org/jira/browse/BEAM-6749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-6749. Resolution: Fixed Fix Version/s: Not applicable > Add BigQuery Storage API info to docs > - > > Key: BEAM-6749 > URL: https://issues.apache.org/jira/browse/BEAM-6749 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 3h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-5174) Website feed is broken due to license header
[ https://issues.apache.org/jira/browse/BEAM-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-5174. Resolution: Fixed Fix Version/s: Not applicable > Website feed is broken due to license header > > > Key: BEAM-5174 > URL: https://issues.apache.org/jira/browse/BEAM-5174 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Maximilian Michels >Priority: Minor > Fix For: Not applicable > > Time Spent: 40m > Remaining Estimate: 0h > > The feed at https://beam.apache.org/feed.xml starts out with a license header > which breaks the XML support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-6827) Update Python dependencies page for 2.10.0, 2.11.0
Melissa Pashniak created BEAM-6827: -- Summary: Update Python dependencies page for 2.10.0, 2.11.0 Key: BEAM-6827 URL: https://issues.apache.org/jira/browse/BEAM-6827 Project: Beam Issue Type: Bug Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-6749) Add BigQuery Storage API info to docs
Melissa Pashniak created BEAM-6749: -- Summary: Add BigQuery Storage API info to docs Key: BEAM-6749 URL: https://issues.apache.org/jira/browse/BEAM-6749 Project: Beam Issue Type: Improvement Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-6530) Strange character on website (contact page)
[ https://issues.apache.org/jira/browse/BEAM-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773363#comment-16773363 ] Melissa Pashniak commented on BEAM-6530: Those are the footnotes that point to the definition – all of them point to the same definition, so they are all listed on the same line. [https://kramdown.gettalong.org/quickref.html#footnotes] I agree it looks a bit odd and I'm open to ideas on how to improve it. I believe Rafael added the footnotes because there was feedback that it was not clear how to subscribe/unsubscribe. > Strange character on website (contact page) > --- > > Key: BEAM-6530 > URL: https://issues.apache.org/jira/browse/BEAM-6530 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Ruoyun Huang >Priority: Minor > Attachments: Screen Shot 2019-01-28 at 6.22.11 PM.png > > > see screen shot as attached. > > Looks like an html error somewhere, Looking at the code though don't see > strange redundant characters: > [https://github.com/apache/beam/blob/master/website/src/community/contact-us.md] > > Some one know more about how the web pages organized might want to take a > look. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-2983) separate docs for constructing WindowFn from applying WindowFn to PCollection
[ https://issues.apache.org/jira/browse/BEAM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak reassigned BEAM-2983: -- Assignee: (was: Melissa Pashniak) > separate docs for constructing WindowFn from applying WindowFn to PCollection > - > > Key: BEAM-2983 > URL: https://issues.apache.org/jira/browse/BEAM-2983 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Priority: Minor > > tgroh request: condense the "How to construct a window fn" parts to the > provided windowing functions section, and have this be just how to apply a > WindowFn to a PCollection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-3338) Update left navs to bubble up buried pages
[ https://issues.apache.org/jira/browse/BEAM-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-3338. Resolution: Fixed Fix Version/s: Not applicable > Update left navs to bubble up buried pages > -- > > Key: BEAM-3338 > URL: https://issues.apache.org/jira/browse/BEAM-3338 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-3643) Remove documentation for creating custom sinks
[ https://issues.apache.org/jira/browse/BEAM-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737586#comment-16737586 ] Melissa Pashniak commented on BEAM-3643: The doc page has been updated to not use plain Sink in PR 7397, it now recommends using a ParDo, or a FileBasedSink specifically. Removal of snippets still needs to be done. > Remove documentation for creating custom sinks > -- > > Key: BEAM-3643 > URL: https://issues.apache.org/jira/browse/BEAM-3643 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Udi Meiri >Assignee: Melissa Pashniak >Priority: Minor > > I believe this whole section should be removed: > [https://beam.apache.org/documentation/sdks/python-custom-io/#creating-a-new-sink] > The reason is that class Sink is deprecated: > [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/io/iobase.py#L578] > Associated code snippets should also be removed: > [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/examples/snippets/snippets.py#L782] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-6347) Add page for developing I/O connectors for Java
[ https://issues.apache.org/jira/browse/BEAM-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-6347. Resolution: Fixed Fix Version/s: Not applicable > Add page for developing I/O connectors for Java > --- > > Key: BEAM-6347 > URL: https://issues.apache.org/jira/browse/BEAM-6347 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 3h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-6347) Add page for developing I/O connectors for Java
Melissa Pashniak created BEAM-6347: -- Summary: Add page for developing I/O connectors for Java Key: BEAM-6347 URL: https://issues.apache.org/jira/browse/BEAM-6347 Project: Beam Issue Type: Bug Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-6295) Fix some versions in 2.7.0 and 2.8.0 Java dependencies tables
[ https://issues.apache.org/jira/browse/BEAM-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-6295. Resolution: Fixed Fix Version/s: Not applicable > Fix some versions in 2.7.0 and 2.8.0 Java dependencies tables > - > > Key: BEAM-6295 > URL: https://issues.apache.org/jira/browse/BEAM-6295 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (BEAM-4188) Release notes link for version 2.4.0 is broken
[ https://issues.apache.org/jira/browse/BEAM-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak closed BEAM-4188. -- Resolution: Fixed Fix Version/s: Not applicable > Release notes link for version 2.4.0 is broken > -- > > Key: BEAM-4188 > URL: https://issues.apache.org/jira/browse/BEAM-4188 > Project: Beam > Issue Type: Bug > Components: website >Affects Versions: 2.4.0 >Reporter: Simon Kitching >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 50m > Remaining Estimate: 0h > > On the Beam downloads page, the html link to release notes for 2.4.0 points > to the same URL as the release notes for 2.3.0. > Downloads page: > [https://beam.apache.org/get-started/downloads/#240-2018-03-20] > Release notes for 2.3.0 correctly link to: > [https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608] > Release notes for 2.4.0 should link to: > [https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12342682] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (BEAM-6295) Fix some versions in 2.7.0 and 2.8.0 Java dependencies tables
[ https://issues.apache.org/jira/browse/BEAM-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak updated BEAM-6295: --- Summary: Fix some versions in 2.7.0 and 2.8.0 Java dependencies tables (was: Fix some versions in 2.8.0 Java dependencies table) > Fix some versions in 2.7.0 and 2.8.0 Java dependencies tables > - > > Key: BEAM-6295 > URL: https://issues.apache.org/jira/browse/BEAM-6295 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-6295) Fix some versions in 2.8.0 Java dependencies table
Melissa Pashniak created BEAM-6295: -- Summary: Fix some versions in 2.8.0 Java dependencies table Key: BEAM-6295 URL: https://issues.apache.org/jira/browse/BEAM-6295 Project: Beam Issue Type: Bug Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (BEAM-6273) Update SDK dependencies page with 2.9.0
[ https://issues.apache.org/jira/browse/BEAM-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak closed BEAM-6273. -- Resolution: Fixed Fix Version/s: Not applicable > Update SDK dependencies page with 2.9.0 > --- > > Key: BEAM-6273 > URL: https://issues.apache.org/jira/browse/BEAM-6273 > Project: Beam > Issue Type: Bug > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-6273) Update SDK dependencies page with 2.9.0
Melissa Pashniak created BEAM-6273: -- Summary: Update SDK dependencies page with 2.9.0 Key: BEAM-6273 URL: https://issues.apache.org/jira/browse/BEAM-6273 Project: Beam Issue Type: Bug Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-6026) Add new pages that list SDK dependencies
[ https://issues.apache.org/jira/browse/BEAM-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melissa Pashniak resolved BEAM-6026. Resolution: Fixed Fix Version/s: Not applicable > Add new pages that list SDK dependencies > > > Key: BEAM-6026 > URL: https://issues.apache.org/jira/browse/BEAM-6026 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Melissa Pashniak >Assignee: Melissa Pashniak >Priority: Minor > Fix For: Not applicable > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-6026) Add new pages that list SDK dependencies
Melissa Pashniak created BEAM-6026: -- Summary: Add new pages that list SDK dependencies Key: BEAM-6026 URL: https://issues.apache.org/jira/browse/BEAM-6026 Project: Beam Issue Type: Improvement Components: website Reporter: Melissa Pashniak Assignee: Melissa Pashniak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-5741) Move "Contact Us" to a top-level link
[ https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653805#comment-16653805 ] Melissa Pashniak commented on BEAM-5741: Another thought, could add the same Finding help section at the very bottom of the guide also, for folks who worked their way down to the bottom and forgot about the help section at the top. Could rename the bottom section slightly if there's repetition concern. "Have questions?" or something. > Move "Contact Us" to a top-level link > - > > Key: BEAM-5741 > URL: https://issues.apache.org/jira/browse/BEAM-5741 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Scott Wegner >Priority: Major > > It should be very easy to figure out how to get in touch with community. > "Contact Us" should be a top-level link on the page. > The page can also be improved with: > * Some basic text on how to use subscribe / unsubscribe links > * Recommendations on how to use various communications channels (Slack for > quick questions, dev@ for longer conversations. And all decisions should make > it back to dev@) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-5741) Move "Contact Us" to a top-level link
[ https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652719#comment-16652719 ] Melissa Pashniak commented on BEAM-5741: Another possible option is removing or combining existing nav item(s)? But I'm not sure which we'd want to remove/combine as they all seem useful. > Move "Contact Us" to a top-level link > - > > Key: BEAM-5741 > URL: https://issues.apache.org/jira/browse/BEAM-5741 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Scott Wegner >Priority: Major > > It should be very easy to figure out how to get in touch with community. > "Contact Us" should be a top-level link on the page. > The page can also be improved with: > * Some basic text on how to use subscribe / unsubscribe links > * Recommendations on how to use various communications channels (Slack for > quick questions, dev@ for longer conversations. And all decisions should make > it back to dev@) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (BEAM-5741) Move "Contact Us" to a top-level link
[ https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652712#comment-16652712 ] Melissa Pashniak edited comment on BEAM-5741 at 10/17/18 12:15 AM: --- Would this be an addition section, or replace the Community section? I don't really agree with adding yet another item, there are two aspects here: 1) We have done a lot of rearranging of the navigation on the site, and as part of this, we looked at many sites when we landed on our current breakdown. On a majority of the sites that use a top nav structure, the contact us/mailing list pages are in a nav item "Community" (for example many Apache sites - Spark, Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes, etc.) Because of this, we used the same "Community" terminology for consistency, and made the contact us page the default page that shows up when someone chooses Community. We used to have pull-down menus on the top nav, but we received feedback that it caused trouble for mobile devices because the menus were too long. We could attempt to put that back and only have a small subset of options, though it might be confusing to show some things but not all unless they click on the item. We could also move to a permanent static left nav structure to show more items at once (such as Flink, which has a "Getting help" page that is always visible), but then we'd lose the section-specific left nav when you choose a top nav item. 2) The other issue is one of remaining horizontal space. I am looking into adding searching capability/a search bar for the site, which would take up a big chunk of the remaining space after the top nav items. we are already nearing (imo) too many top level nav items. (some actually weren't enthused with how many are there even now) was (Author: melap): Would this replace the Community section? I don't really agree with this, there are two aspects here: 1) We have done a lot of rearranging of the navigation on the site, and as part of this, we looked at many sites when we landed on our current breakdown. On a majority of the sites that use a top nav structure, the contact us/mailing list pages are in a nav item "Community" (for example many Apache sites - Spark, Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes, etc.) Because of this, we used the same "Community" terminology for consistency, and made the contact us page the default page that shows up when someone chooses Community. We used to have pull-down menus on the top nav, but we received feedback that it caused trouble for mobile devices because the menus were too long. We could attempt to put that back and only have a small subset of options, though it might be confusing to show some things but not all unless they click on the item. We could also move to a permanent static left nav structure to show more items at once (such as Flink, which has a "Getting help" page that is always visible), but then we'd lose the section-specific left nav when you choose a top nav item. 2) The other issue is one of remaining horizontal space. I am looking into adding searching capability/a search bar for the site, which would take up a big chunk of the remaining space after the top nav items. we are already nearing (imo) too many top level nav items. (some actually weren't enthused with how many are there even now) > Move "Contact Us" to a top-level link > - > > Key: BEAM-5741 > URL: https://issues.apache.org/jira/browse/BEAM-5741 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Scott Wegner >Priority: Major > > It should be very easy to figure out how to get in touch with community. > "Contact Us" should be a top-level link on the page. > The page can also be improved with: > * Some basic text on how to use subscribe / unsubscribe links > * Recommendations on how to use various communications channels (Slack for > quick questions, dev@ for longer conversations. And all decisions should make > it back to dev@) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (BEAM-5741) Move "Contact Us" to a top-level link
[ https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652712#comment-16652712 ] Melissa Pashniak edited comment on BEAM-5741 at 10/17/18 12:15 AM: --- Would this be an additional section, or replace the Community section? I don't really agree with adding yet another item, there are two aspects here: 1) We have done a lot of rearranging of the navigation on the site, and as part of this, we looked at many sites when we landed on our current breakdown. On a majority of the sites that use a top nav structure, the contact us/mailing list pages are in a nav item "Community" (for example many Apache sites - Spark, Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes, etc.) Because of this, we used the same "Community" terminology for consistency, and made the contact us page the default page that shows up when someone chooses Community. We used to have pull-down menus on the top nav, but we received feedback that it caused trouble for mobile devices because the menus were too long. We could attempt to put that back and only have a small subset of options, though it might be confusing to show some things but not all unless they click on the item. We could also move to a permanent static left nav structure to show more items at once (such as Flink, which has a "Getting help" page that is always visible), but then we'd lose the section-specific left nav when you choose a top nav item. 2) The other issue is one of remaining horizontal space. I am looking into adding searching capability/a search bar for the site, which would take up a big chunk of the remaining space after the top nav items. we are already nearing (imo) too many top level nav items. (some actually weren't enthused with how many are there even now) was (Author: melap): Would this be an addition section, or replace the Community section? I don't really agree with adding yet another item, there are two aspects here: 1) We have done a lot of rearranging of the navigation on the site, and as part of this, we looked at many sites when we landed on our current breakdown. On a majority of the sites that use a top nav structure, the contact us/mailing list pages are in a nav item "Community" (for example many Apache sites - Spark, Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes, etc.) Because of this, we used the same "Community" terminology for consistency, and made the contact us page the default page that shows up when someone chooses Community. We used to have pull-down menus on the top nav, but we received feedback that it caused trouble for mobile devices because the menus were too long. We could attempt to put that back and only have a small subset of options, though it might be confusing to show some things but not all unless they click on the item. We could also move to a permanent static left nav structure to show more items at once (such as Flink, which has a "Getting help" page that is always visible), but then we'd lose the section-specific left nav when you choose a top nav item. 2) The other issue is one of remaining horizontal space. I am looking into adding searching capability/a search bar for the site, which would take up a big chunk of the remaining space after the top nav items. we are already nearing (imo) too many top level nav items. (some actually weren't enthused with how many are there even now) > Move "Contact Us" to a top-level link > - > > Key: BEAM-5741 > URL: https://issues.apache.org/jira/browse/BEAM-5741 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Scott Wegner >Priority: Major > > It should be very easy to figure out how to get in touch with community. > "Contact Us" should be a top-level link on the page. > The page can also be improved with: > * Some basic text on how to use subscribe / unsubscribe links > * Recommendations on how to use various communications channels (Slack for > quick questions, dev@ for longer conversations. And all decisions should make > it back to dev@) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-5741) Move "Contact Us" to a top-level link
[ https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652712#comment-16652712 ] Melissa Pashniak commented on BEAM-5741: Would this replace the Community section? I don't really agree with this, there are two aspects here: 1) We have done a lot of rearranging of the navigation on the site, and as part of this, we looked at many sites when we landed on our current breakdown. On a majority of the sites that use a top nav structure, the contact us/mailing list pages are in a nav item "Community" (for example many Apache sites - Spark, Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes, etc.) Because of this, we used the same "Community" terminology for consistency, and made the contact us page the default page that shows up when someone chooses Community. We used to have pull-down menus on the top nav, but we received feedback that it caused trouble for mobile devices because the menus were too long. We could attempt to put that back and only have a small subset of options, though it might be confusing to show some things but not all unless they click on the item. We could also move to a permanent static left nav structure to show more items at once (such as Flink, which has a "Getting help" page that is always visible), but then we'd lose the section-specific left nav when you choose a top nav item. 2) The other issue is one of remaining horizontal space. I am looking into adding searching capability/a search bar for the site, which would take up a big chunk of the remaining space after the top nav items. we are already nearing (imo) too many top level nav items. (some actually weren't enthused with how many are there even now) > Move "Contact Us" to a top-level link > - > > Key: BEAM-5741 > URL: https://issues.apache.org/jira/browse/BEAM-5741 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Scott Wegner >Priority: Major > > It should be very easy to figure out how to get in touch with community. > "Contact Us" should be a top-level link on the page. > The page can also be improved with: > * Some basic text on how to use subscribe / unsubscribe links > * Recommendations on how to use various communications channels (Slack for > quick questions, dev@ for longer conversations. And all decisions should make > it back to dev@) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (BEAM-5741) Move "Contact Us" to a top-level link
[ https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652569#comment-16652569 ] Melissa Pashniak commented on BEAM-5741: what do you mean by top-level link here? as in another item in the top items (documentation, SDKs, community, etc.)? > Move "Contact Us" to a top-level link > - > > Key: BEAM-5741 > URL: https://issues.apache.org/jira/browse/BEAM-5741 > Project: Beam > Issue Type: Sub-task > Components: website >Reporter: Scott Wegner >Priority: Major > > It should be very easy to figure out how to get in touch with community. > "Contact Us" should be a top-level link on the page. > The page can also be improved with: > * Some basic text on how to use subscribe / unsubscribe links > * Recommendations on how to use various communications channels (Slack for > quick questions, dev@ for longer conversations. And all decisions should make > it back to dev@) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
