[jira] [Created] (IGNITE-16125) Remove LuckyOrange code from website
Mauricio Stekl created IGNITE-16125: --- Summary: Remove LuckyOrange code from website Key: IGNITE-16125 URL: https://issues.apache.org/jira/browse/IGNITE-16125 Project: Ignite Issue Type: Task Components: website Reporter: Mauricio Stekl Assignee: Erlan Aytpaev We discontinued LuckyOrange for the new website. The tracking code was removed for the main site, but not from the online documentation. Please update the Jekyll templates and rebuild the docs (latest and previous versions). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16112) New website - Missing section for "Extensions" on downloads page
Mauricio Stekl created IGNITE-16112: --- Summary: New website - Missing section for "Extensions" on downloads page Key: IGNITE-16112 URL: https://issues.apache.org/jira/browse/IGNITE-16112 Project: Ignite Issue Type: Task Components: website Reporter: Mauricio Stekl The new website is missing the "Extensions" table with downloads links. This was added by Nov 16th, and the last available code before merging new site can be found here: [https://github.com/apache/ignite-website/blob/76099809393844c11ec92ac392877fcfc096217d/download.html#L954] Please implement the table into [https://github.com/apache/ignite-website/blob/master/_src/download.pug] as soon as possible. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16112) New website - Missing section for "Extensions" on downloads page
[ https://issues.apache.org/jira/browse/IGNITE-16112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-16112: --- Assignee: Erlan Aytpaev > New website - Missing section for "Extensions" on downloads page > > > Key: IGNITE-16112 > URL: https://issues.apache.org/jira/browse/IGNITE-16112 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Mauricio Stekl >Assignee: Erlan Aytpaev >Priority: Critical > > The new website is missing the "Extensions" table with downloads links. This > was added by Nov 16th, and the last available code before merging new site > can be found here: > [https://github.com/apache/ignite-website/blob/76099809393844c11ec92ac392877fcfc096217d/download.html#L954] > Please implement the table into > [https://github.com/apache/ignite-website/blob/master/_src/download.pug] as > soon as possible. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-15821) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15821. - Resolution: Duplicate hi [~Eugenia], this is a duplicate for https://issues.apache.org/jira/browse/IGNITE-15828 I checked with Kseniya and she suggested to use her text instead. > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-15821 > URL: https://issues.apache.org/jira/browse/IGNITE-15821 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Evgenia >Priority: Trivial > > Please add an event to [https://ignite.apache.org/events.html] > Date: November,9 > h1. Apache Ignite Community Gathering > During this community gathering, we will discuss the latest Ignite releases: > Apache Ignite 2.11 and Apache Ignite 3.0, Alpha 3. > *Apache Ignite 2.11: Improvements and .NET Upgrades* > Maxim Muzafarov will present a quick overview of Apache Ignite 2.11. This > release resolved a number of issues, problems with the internal architecture > and technical bugs. > Pavel Tupitsyn, a .NET module maintainer, will talk about the Apache Ignite > 2.11 updates related to .NET. He will present examples of thin client Data > Streamer, .NET 5 support, and more. > *Apache Ignite 3 Alpha 3: The Journey Continues* > Just now, the Apache Ignite community released the latest version of Ignite > 3—Alpha 3! Val Kulichenko, the Ignite 3.0 Release manager, will discuss the > updates and demonstrate the latest API changes. > This release features the following new functionality: > - New SQL engine, based on Apache Calcite + JDBC driver > - Persistence implementation, based on RocksDB > - New binary client protocol with an implementation in Java > - Data rebalancing > Learn more: > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/281596817/] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15828) [Ignite Website] Update for events schedule + top line
[ https://issues.apache.org/jira/browse/IGNITE-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15828: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule + top line > -- > > Key: IGNITE-15828 > URL: https://issues.apache.org/jira/browse/IGNITE-15828 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > 1)Please add to the [https://ignite.apache.org/events.html] new meetup: > > Apache Ignite 2.11: Improvements and .NET Upgrades, Apache Ignite 3 Alpha 3: > The Journey Continues > Apache Ignite Community Gathering, Maxim Muzafarov, Pavel Tupitsyn, Val > Kulichenko > November 9, 2021 > A quick overview of Apache Ignite 2.11. This release resolved a number of > issues, problems with the internal architecture and technical bugs. Plus we > will discuss Apache Ignite 2.11 updates related to .NET. > Just now, the Apache Ignite community released the latest version of Ignite > 3—Alpha 3! Val Kulichenko, the Ignite 3.0 Release manager, will demonstrate > the updates and the latest API changes. > Read > more=[https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/281596817] > > 2)Please put the new event announcement to the top line of the site: > November 9, 2021: Ignite 3.0 Alpha 3 Community Gathering > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/281596817] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15828) [Ignite Website] Update for events schedule + top line
[ https://issues.apache.org/jira/browse/IGNITE-15828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15828. - Resolution: Fixed I've pushed the patch with this update. > [Ignite Website] Update for events schedule + top line > -- > > Key: IGNITE-15828 > URL: https://issues.apache.org/jira/browse/IGNITE-15828 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > 1)Please add to the [https://ignite.apache.org/events.html] new meetup: > > Apache Ignite 2.11: Improvements and .NET Upgrades, Apache Ignite 3 Alpha 3: > The Journey Continues > Apache Ignite Community Gathering, Maxim Muzafarov, Pavel Tupitsyn, Val > Kulichenko > November 9, 2021 > A quick overview of Apache Ignite 2.11. This release resolved a number of > issues, problems with the internal architecture and technical bugs. Plus we > will discuss Apache Ignite 2.11 updates related to .NET. > Just now, the Apache Ignite community released the latest version of Ignite > 3—Alpha 3! Val Kulichenko, the Ignite 3.0 Release manager, will demonstrate > the updates and the latest API changes. > Read > more=[https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/281596817] > > 2)Please put the new event announcement to the top line of the site: > November 9, 2021: Ignite 3.0 Alpha 3 Community Gathering > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/281596817] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15793) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15793. - Resolution: Fixed Schedule updated on the site. > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-15793 > URL: https://issues.apache.org/jira/browse/IGNITE-15793 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please update the page [https://ignite.apache.org/events.html] > > 1)Change the "Rebalancing in a distributed database" date for March 18, 2022 > 2)Add the new one: > Backward compatibility on the example of Apache Ignite. Why does it hurt so > much? > mergeconf, Nikolay Izhikov > November 13, 2021 > I am developing an Apache Ignite distributed database. Our product provides > backward compatibility between versions. What do you need to think about for > backward compatibility? What is Backward Compatibility for Developers? How do > I test it? > Why does it hurt so much? How to relieve pain? I will tell you about all > this with the code examples. > Learn more = [https://mergeconf.ru/development/opensource/izhikov] > > 3)Let's add the Ignite Summit to this page: > > Ignite Summit: Cloud Edition > November 15-16, 2021 > On November 15 and 16, 2021a free virtual event—Ignite Summit: Cloud Edition > will be held. The conference is for architects and developers who use or are > interested in using Apache Ignite in the cloud. > On November 15, 2021, free training sessions for EMEA and the Americas will > be offered. On November 16, 2021, Ignite experts will share architectural > insights and practical tips for solving challenges in cloud environments. > Learn more =https://ignite-summit.org -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15793) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15793: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-15793 > URL: https://issues.apache.org/jira/browse/IGNITE-15793 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please update the page [https://ignite.apache.org/events.html] > > 1)Change the "Rebalancing in a distributed database" date for March 18, 2022 > 2)Add the new one: > Backward compatibility on the example of Apache Ignite. Why does it hurt so > much? > mergeconf, Nikolay Izhikov > November 13, 2021 > I am developing an Apache Ignite distributed database. Our product provides > backward compatibility between versions. What do you need to think about for > backward compatibility? What is Backward Compatibility for Developers? How do > I test it? > Why does it hurt so much? How to relieve pain? I will tell you about all > this with the code examples. > Learn more = [https://mergeconf.ru/development/opensource/izhikov] > > 3)Let's add the Ignite Summit to this page: > > Ignite Summit: Cloud Edition > November 15-16, 2021 > On November 15 and 16, 2021a free virtual event—Ignite Summit: Cloud Edition > will be held. The conference is for architects and developers who use or are > interested in using Apache Ignite in the cloud. > On November 15, 2021, free training sessions for EMEA and the Americas will > be offered. On November 16, 2021, Ignite experts will share architectural > insights and practical tips for solving challenges in cloud environments. > Learn more =https://ignite-summit.org -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15709) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15709. - Resolution: Fixed > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-15709 > URL: https://issues.apache.org/jira/browse/IGNITE-15709 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please update the events and add the new one: > *Rebalancing in a distributed database. How to catch up with the state of the > node to the state of the cluster?* > Highload++, Vlad Pyatkov > November 25, 2021 > The report will present the concept of historical rebalancing, implemented in > the Apache Ignite distributed database. > Learn more=https://www.highload.ru/moscow/2021/abstracts/7989 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15709) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15709: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-15709 > URL: https://issues.apache.org/jira/browse/IGNITE-15709 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please update the events and add the new one: > *Rebalancing in a distributed database. How to catch up with the state of the > node to the state of the cluster?* > Highload++, Vlad Pyatkov > November 25, 2021 > The report will present the concept of historical rebalancing, implemented in > the Apache Ignite distributed database. > Learn more=https://www.highload.ru/moscow/2021/abstracts/7989 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15553) Website: the feedback button and banner cover the menu
[ https://issues.apache.org/jira/browse/IGNITE-15553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15553. - Resolution: Fixed I committed a patch that solves this problem. > Website: the feedback button and banner cover the menu > -- > > Key: IGNITE-15553 > URL: https://issues.apache.org/jira/browse/IGNITE-15553 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: error_2.png > > > See the attached picture. The button and banner cover a part of the > right-hand side navigation menu. > > Page: [https://ignite.apache.org/docs/latest/sql-reference/dml] > > Affects all resolutions on some pages, up to 4k. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15634) Ignite Website: misaligned block with stars and 2.11 promo
[ https://issues.apache.org/jira/browse/IGNITE-15634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15634. - Resolution: Fixed [~dmagda] I fixed the alignment problem and updated the promo bar. > Ignite Website: misaligned block with stars and 2.11 promo > -- > > Key: IGNITE-15634 > URL: https://issues.apache.org/jira/browse/IGNITE-15634 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screenshot 2021-09-27 142144.png > > > Mauricio, could you please help with the following: > * Issue: the block with the stars is misaligned on the home page. See the > attached picture. > * The promo banner: promote the latest release - "Apache Ignite 2.11 > Released: See Why You Need to Upgrade ->" > [https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15481) [Ignite Website] Updates for events and people
[ https://issues.apache.org/jira/browse/IGNITE-15481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15481. - Resolution: Fixed Kseniya, I made these updates on the site. By the way, congrats for becoming a PMC! :) > [Ignite Website] Updates for events and people > -- > > Key: IGNITE-15481 > URL: https://issues.apache.org/jira/browse/IGNITE-15481 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please update the pages below: > 1) Please change the promoted event for Ignite Summit: Cloud Edition - The > Call for Speakers is Open! https://ignite-summit.org/ > 2)New Events for https://ignite.apache.org/events.html > Moscow Apache Ignite Meetup > Moscow Apache Ignite Meetup, Ivan Bessonov, Maxim Muzafarov, Dmitry Gorchakov > September 23, 2021 > The Apache Ignite® community invites developers to their first offline > meeting in 2021! Ignite Committers Ivan Bessonov and Maxim Muzafarov will > talk about recently updated features (Ignite snapshots and Data > Defragmentation). Dmitry Gorchakov will introduce the case - building a > distributed system of "super services" on Apache Ignite. > Learn > more=https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/280030657/ > Organization of testing distributed systems on the example of a real Java > project > Moscow Python Conference 2021, Maxim Losevskoy > September 28, 2021 > In this talk, Maxim will share how GridGaim organized our testing > infrastructure for Apache Ignite based platform using the tools provided by > Python. > Learn more=https://conf.python.ru/moscow/2021/abstracts/7837 > 3)https://ignite.apache.org/community/resources.html#people > Please add Kseniya Romanova* GridGain (yep, PMC now, a great honor for > non-code contributor) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15481) [Ignite Website] Updates for events and people
[ https://issues.apache.org/jira/browse/IGNITE-15481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15481: --- Assignee: Mauricio Stekl > [Ignite Website] Updates for events and people > -- > > Key: IGNITE-15481 > URL: https://issues.apache.org/jira/browse/IGNITE-15481 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please update the pages below: > 1) Please change the promoted event for Ignite Summit: Cloud Edition - The > Call for Speakers is Open! https://ignite-summit.org/ > 2)New Events for https://ignite.apache.org/events.html > Moscow Apache Ignite Meetup > Moscow Apache Ignite Meetup, Ivan Bessonov, Maxim Muzafarov, Dmitry Gorchakov > September 23, 2021 > The Apache Ignite® community invites developers to their first offline > meeting in 2021! Ignite Committers Ivan Bessonov and Maxim Muzafarov will > talk about recently updated features (Ignite snapshots and Data > Defragmentation). Dmitry Gorchakov will introduce the case - building a > distributed system of "super services" on Apache Ignite. > Learn > more=https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/280030657/ > Organization of testing distributed systems on the example of a real Java > project > Moscow Python Conference 2021, Maxim Losevskoy > September 28, 2021 > In this talk, Maxim will share how GridGaim organized our testing > infrastructure for Apache Ignite based platform using the tools provided by > Python. > Learn more=https://conf.python.ru/moscow/2021/abstracts/7837 > 3)https://ignite.apache.org/community/resources.html#people > Please add Kseniya Romanova* GridGain (yep, PMC now, a great honor for > non-code contributor) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15372) Remove companies logos from the homepage
[ https://issues.apache.org/jira/browse/IGNITE-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15372. - Resolution: Fixed I updated the website with a new section replacing the companies logos. In the process I also applied a new behavior for the Github bar on the homepage, now it is fixed to the bottom of the screen and moves away when the user scrolls down. > Remove companies logos from the homepage > > > Key: IGNITE-15372 > URL: https://issues.apache.org/jira/browse/IGNITE-15372 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > We have to remove the logos of the companies that use Ignite from the > homepage (this rule doesn't apply to other pages). > WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos > on a project's home page is disallowed as it can imply "ownership" or > preferred status or otherwise imbalanced relationship. Whether this is the > case or not, it is not acceptable. The policy is the same as "thanking" > companies for their support of a project > [http://apache.org/foundation/marks/linking#projectthanks] > As an alternative, we can create a "powered by" section similar to what the > Kafka community has: http://kafka.apache.org > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15372) Remove companies logos from the homepage
[ https://issues.apache.org/jira/browse/IGNITE-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15372: --- Assignee: Mauricio Stekl > Remove companies logos from the homepage > > > Key: IGNITE-15372 > URL: https://issues.apache.org/jira/browse/IGNITE-15372 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > We have to remove the logos of the companies that use Ignite from the > homepage (this rule doesn't apply to other pages). > WHY: the ASF is strictly vendor-neutral. Listing company names and/or logos > on a project's home page is disallowed as it can imply "ownership" or > preferred status or otherwise imbalanced relationship. Whether this is the > case or not, it is not acceptable. The policy is the same as "thanking" > companies for their support of a project > [http://apache.org/foundation/marks/linking#projectthanks] > As an alternative, we can create a "powered by" section similar to what the > Kafka community has: http://kafka.apache.org > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15405) [Ignite Website] New cases + new Committers
[ https://issues.apache.org/jira/browse/IGNITE-15405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15405. - Resolution: Fixed I've updated the website with the requested changes. > [Ignite Website] New cases + new Committers > > > Key: IGNITE-15405 > URL: https://issues.apache.org/jira/browse/IGNITE-15405 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > # Please add 2 more videos on the page > [https://ignite.apache.org/use-cases/provenusecases.html] > Put this to JPMorgan Chase section > The increasing need in the finance world to apply transformations to large > datasets in real-time led the Asset Management’s portfolio management system > team to select Ignite to achieve persistence, caching and integrated compute. > [https://www.youtube.com/watch?v=B8A8yR_e6VM > |https://www.youtube.com/watch?v=B8A8yR_e6VM] > BNP Paribas > A hybrid transactional-analytical processing (HTAP) solution in BNP Paribas > is powered by Apache Ignite and enables bank to make key business decisions > in real-time. > [https://www.youtube.com/watch?v=-t-Syy9blXQ] > > 2. Please add new committers to the page > [https://ignite.apache.org/community/resources.html#people] > Alexander Shapkin GridGain > Andrey Alexandrov GridGain > Peter Ivanov GridGain > Zhenya Stanilovsky GridGain > > 3. Please update the upper line event promotion: > Join Virtual Meetup on September 2: Building a low-code BaaS platform on > Apache Ignite > https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/280030600/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15405) [Ignite Website] New cases + new Committers
[ https://issues.apache.org/jira/browse/IGNITE-15405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15405: --- Assignee: Mauricio Stekl > [Ignite Website] New cases + new Committers > > > Key: IGNITE-15405 > URL: https://issues.apache.org/jira/browse/IGNITE-15405 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > # Please add 2 more videos on the page > [https://ignite.apache.org/use-cases/provenusecases.html] > Put this to JPMorgan Chase section > The increasing need in the finance world to apply transformations to large > datasets in real-time led the Asset Management’s portfolio management system > team to select Ignite to achieve persistence, caching and integrated compute. > [https://www.youtube.com/watch?v=B8A8yR_e6VM > |https://www.youtube.com/watch?v=B8A8yR_e6VM] > BNP Paribas > A hybrid transactional-analytical processing (HTAP) solution in BNP Paribas > is powered by Apache Ignite and enables bank to make key business decisions > in real-time. > [https://www.youtube.com/watch?v=-t-Syy9blXQ] > > 2. Please add new committers to the page > [https://ignite.apache.org/community/resources.html#people] > Alexander Shapkin GridGain > Andrey Alexandrov GridGain > Peter Ivanov GridGain > Zhenya Stanilovsky GridGain > > 3. Please update the upper line event promotion: > Join Virtual Meetup on September 2: Building a low-code BaaS platform on > Apache Ignite > https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/280030600/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15311) Broken links on download page
[ https://issues.apache.org/jira/browse/IGNITE-15311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15311. - Resolution: Fixed Since the Google compute image is not available anymore, I removed the section. Something similar happens with the Build the Binaries section on this page. It was removed months ago, so I removed the references from the top section. > Broken links on download page > - > > Key: IGNITE-15311 > URL: https://issues.apache.org/jira/browse/IGNITE-15311 > Project: Ignite > Issue Type: Bug >Reporter: Sebb >Assignee: Mauricio Stekl >Priority: Major > > The following links on the download page are broken: > Building the Binaries: https://ignite.apache.org/download.cgi#build-source > DOCKER AND CLOUD IMAGES [Google Compute Image]: > https://storage.googleapis.com/ignite-media/ignite-google-image.tar.gz -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15311) Broken links on download page
[ https://issues.apache.org/jira/browse/IGNITE-15311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15311: --- Assignee: Mauricio Stekl > Broken links on download page > - > > Key: IGNITE-15311 > URL: https://issues.apache.org/jira/browse/IGNITE-15311 > Project: Ignite > Issue Type: Bug >Reporter: Sebb >Assignee: Mauricio Stekl >Priority: Major > > The following links on the download page are broken: > Building the Binaries: https://ignite.apache.org/download.cgi#build-source > DOCKER AND CLOUD IMAGES [Google Compute Image]: > https://storage.googleapis.com/ignite-media/ignite-google-image.tar.gz -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15290) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15290. - Resolution: Fixed Website updated with these events. > [Ignite Website] Update for events schedule > > > Key: IGNITE-15290 > URL: https://issues.apache.org/jira/browse/IGNITE-15290 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > # Please change the top line for Watch Ignite Summit Recordings > [https://youtube.com/playlist?list=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V] > # Please add to the Events Schedule page these events: > *Apache Ignite. Now with CDC!* > * Saint Highload++, Nikolay Izhikov > * September 20, 2021 > Nikolay Izhikov, Apache Ignite PMC, will introduce the audience to Change > Data Capture and share how it's organized in Apache Ignite. > Learn more = [https://www.highload.ru/spb/2021/abstracts/7942] > > *Python-client for Apache Ignite Distributed DataBase* > * Moscow Python Conference 2021, Ivan Daschinsky > * September 28, 2021 > Ivan Daschinsky, Apache Ignite Committer and Python Client maintainer will > present the latest version of the Client. > Learn more = [https://conf.python.ru/moscow/2021/abstracts/7815] > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15290) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15290: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > > > Key: IGNITE-15290 > URL: https://issues.apache.org/jira/browse/IGNITE-15290 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > # Please change the top line for Watch Ignite Summit Recordings > [https://youtube.com/playlist?list=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V] > # Please add to the Events Schedule page these events: > *Apache Ignite. Now with CDC!* > * Saint Highload++, Nikolay Izhikov > * September 20, 2021 > Nikolay Izhikov, Apache Ignite PMC, will introduce the audience to Change > Data Capture and share how it's organized in Apache Ignite. > Learn more = [https://www.highload.ru/spb/2021/abstracts/7942] > > *Python-client for Apache Ignite Distributed DataBase* > * Moscow Python Conference 2021, Ivan Daschinsky > * September 28, 2021 > Ivan Daschinsky, Apache Ignite Committer and Python Client maintainer will > present the latest version of the Client. > Learn more = [https://conf.python.ru/moscow/2021/abstracts/7815] > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15291) [Ignite Website] Add new proven cases
[ https://issues.apache.org/jira/browse/IGNITE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15291: --- Assignee: Mauricio Stekl > [Ignite Website] Add new proven cases > - > > Key: IGNITE-15291 > URL: https://issues.apache.org/jira/browse/IGNITE-15291 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please add new videos to the "powered by Ignite" page > [https://ignite.apache.org/use-cases/provenusecases.html] > +Please insert new cases after the 24 Fitness:+ > *JPMorgan Chase* > Exposure management poses unique technical challenges for Asset Management. > Requests involve heavy computation on top of millions of data points with > target response times of around a 1/3 second. This challenge was solved using > Apache Ignite-based platform. > [https://youtu.be/jF9T2cJB6t0] > *nference.ai* > nference.ai uses Ignite for distributed analytics in the bioinformatics > domain. Ignite as a horizontally scalable framework allows to define > different statistical analyses and execute it on TB's of numerical data in > real-time, without movement of data. > [https://youtu.be/NUxdoL-K9Ys] > +and these 2 cases let's add to the end of the list:+ > *Trimble* > Trimble built a live geospatial analytics platform for construction > productivity with Apache Ignite. Apache Ignite forms a key infrastructure > component of TRex platform. It supports real-time ingest of data from the > field along with OLTP style analytics and queries against that data such as > thematic tiling, volumes & cut/fill calculations, spatial profiling, etc. > [https://youtu.be/KLnvIiwAl2o] > *Sentienz* > Sentienz uses Apache Ignite to handle more than 1Millions Requests per > second from 10 Million devices with a single cluster IoT platform. > [https://youtu.be/_mnZQ3JDcn8] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15291) [Ignite Website] Add new proven cases
[ https://issues.apache.org/jira/browse/IGNITE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-15291. - Resolution: Fixed Updated the web page with these use cases. > [Ignite Website] Add new proven cases > - > > Key: IGNITE-15291 > URL: https://issues.apache.org/jira/browse/IGNITE-15291 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > Please add new videos to the "powered by Ignite" page > [https://ignite.apache.org/use-cases/provenusecases.html] > +Please insert new cases after the 24 Fitness:+ > *JPMorgan Chase* > Exposure management poses unique technical challenges for Asset Management. > Requests involve heavy computation on top of millions of data points with > target response times of around a 1/3 second. This challenge was solved using > Apache Ignite-based platform. > [https://youtu.be/jF9T2cJB6t0] > *nference.ai* > nference.ai uses Ignite for distributed analytics in the bioinformatics > domain. Ignite as a horizontally scalable framework allows to define > different statistical analyses and execute it on TB's of numerical data in > real-time, without movement of data. > [https://youtu.be/NUxdoL-K9Ys] > +and these 2 cases let's add to the end of the list:+ > *Trimble* > Trimble built a live geospatial analytics platform for construction > productivity with Apache Ignite. Apache Ignite forms a key infrastructure > component of TRex platform. It supports real-time ingest of data from the > field along with OLTP style analytics and queries against that data such as > thematic tiling, volumes & cut/fill calculations, spatial profiling, etc. > [https://youtu.be/KLnvIiwAl2o] > *Sentienz* > Sentienz uses Apache Ignite to handle more than 1Millions Requests per > second from 10 Million devices with a single cluster IoT platform. > [https://youtu.be/_mnZQ3JDcn8] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15106) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-15106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-15106: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-15106 > URL: https://issues.apache.org/jira/browse/IGNITE-15106 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > Please add an event to [https://ignite.apache.org/events.html] > > Apache Ignite 3.0.0 Alpha 2 Build Community Gathering > Virtual Apache Ignite Meetup, Valentin Kulichenko > June 20 > This gathering is organized to summarize feedback, share ideas, and overview > the following stages of Ignite 3.0 development. > During this session, we will: > ‒ Give an update on the Ignite 3 development - what has been completed so > far, and the next steps planned. > ‒ Discuss the latest Ignite 3 milestone: the Alpha 2 release. > ‒ Run a live demo: create an Ignite 3 Alpha 2 cluster and demonstrate the new > APIs usage by running code examples. > Learn > more=https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/279417063/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14696) [Ignite Website] Update for events schedule and more
[ https://issues.apache.org/jira/browse/IGNITE-14696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14696. - Resolution: Fixed > [Ignite Website] Update for events schedule and more > > > Key: IGNITE-14696 > URL: https://issues.apache.org/jira/browse/IGNITE-14696 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1)new even for [https://ignite.apache.org/events.html] > Apache Ignite on Kubernetes > Webinar, Colin Capriati > Running Apache Ignite on Kubernetes can help Ignite developers streamline > deployment and management of applications in cloud environments, both private > and public. Apache Ignite is Kubernetes-friendly with features that simplify > cluster provisioning and minimize the operational and management burden. > Learn more: > [https://www.gridgain.com/resources/webinars/apache-ignite-kubernetes] > > 2)Please update top line on the main page: > May 25, 2021: Don't forget to join first Ignite Summit for developers > [https://ignite-summit.org/] > > 3)Please exclude Vrbo from the logos block. > 4)Please update the Ignite Summit banner for the new one > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14696) [Ignite Website] Update for events schedule and more
[ https://issues.apache.org/jira/browse/IGNITE-14696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344190#comment-17344190 ] Mauricio Stekl commented on IGNITE-14696: - [~romanova.ks.spb], I updated the events and the Vrbo logo. About the Ignite promos, I updated the top bar, and the side bar on the docs. When I receive the image for the main section on the homepage I'll update it and let you know. > [Ignite Website] Update for events schedule and more > > > Key: IGNITE-14696 > URL: https://issues.apache.org/jira/browse/IGNITE-14696 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1)new even for [https://ignite.apache.org/events.html] > Apache Ignite on Kubernetes > Webinar, Colin Capriati > Running Apache Ignite on Kubernetes can help Ignite developers streamline > deployment and management of applications in cloud environments, both private > and public. Apache Ignite is Kubernetes-friendly with features that simplify > cluster provisioning and minimize the operational and management burden. > Learn more: > [https://www.gridgain.com/resources/webinars/apache-ignite-kubernetes] > > 2)Please update top line on the main page: > May 25, 2021: Don't forget to join first Ignite Summit for developers > [https://ignite-summit.org/] > > 3)Please exclude Vrbo from the logos block. > 4)Please update the Ignite Summit banner for the new one > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14696) [Ignite Website] Update for events schedule and more
[ https://issues.apache.org/jira/browse/IGNITE-14696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14696: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule and more > > > Key: IGNITE-14696 > URL: https://issues.apache.org/jira/browse/IGNITE-14696 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1)new even for [https://ignite.apache.org/events.html] > Apache Ignite on Kubernetes > Webinar, Colin Capriati > Running Apache Ignite on Kubernetes can help Ignite developers streamline > deployment and management of applications in cloud environments, both private > and public. Apache Ignite is Kubernetes-friendly with features that simplify > cluster provisioning and minimize the operational and management burden. > Learn more: > [https://www.gridgain.com/resources/webinars/apache-ignite-kubernetes] > > 2)Please update top line on the main page: > May 25, 2021: Don't forget to join first Ignite Summit for developers > [https://ignite-summit.org/] > > 3)Please exclude Vrbo from the logos block. > 4)Please update the Ignite Summit banner for the new one > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14626) [Ignite Website] Update for events schedule & usecases
[ https://issues.apache.org/jira/browse/IGNITE-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14626. - Resolution: Done Added Use Cases and updated list of events. > [Ignite Website] Update for events schedule & usecases > -- > > Key: IGNITE-14626 > URL: https://issues.apache.org/jira/browse/IGNITE-14626 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1) [https://ignite.apache.org/use-cases/provenusecases.html] > Please add hereBanco do Brasil [https://youtu.be/g1FcrOPXWyg] (after ING Bank) > description: Banco do Brasil is developing in-house the omnichannel Horus > platform. They implemented a complex event processing (CEP) ecosystem that is > based on Apache Ignite, JBoss Drools, and other components. The team also > built microservices and interface applications, both event-driven. > Please delete Vrbo > 2)Please update the events schedule: [https://ignite.apache.org/events.html] > How to Use Spark With Apache Ignite for Big Data Processing > Webinar, Andrey Alexandrov > April 28, 2021 > In this webinar, you learn when to use Ignite, and, using real-world > examples, you learn how to configure Spark-Ignite integration. In addition, > Andrey will tell about optimization techniques and best practices. > Learn more > https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14626) [Ignite Website] Update for events schedule & usecases
[ https://issues.apache.org/jira/browse/IGNITE-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14626: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule & usecases > -- > > Key: IGNITE-14626 > URL: https://issues.apache.org/jira/browse/IGNITE-14626 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl], please update the site: > > 1) [https://ignite.apache.org/use-cases/provenusecases.html] > Please add hereBanco do Brasil [https://youtu.be/g1FcrOPXWyg] (after ING Bank) > description: Banco do Brasil is developing in-house the omnichannel Horus > platform. They implemented a complex event processing (CEP) ecosystem that is > based on Apache Ignite, JBoss Drools, and other components. The team also > built microservices and interface applications, both event-driven. > Please delete Vrbo > 2)Please update the events schedule: [https://ignite.apache.org/events.html] > How to Use Spark With Apache Ignite for Big Data Processing > Webinar, Andrey Alexandrov > April 28, 2021 > In this webinar, you learn when to use Ignite, and, using real-world > examples, you learn how to configure Spark-Ignite integration. In addition, > Andrey will tell about optimization techniques and best practices. > Learn more > https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14598) Change the Download page reference text
[ https://issues.apache.org/jira/browse/IGNITE-14598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14598. - Resolution: Fixed > Change the Download page reference text > --- > > Key: IGNITE-14598 > URL: https://issues.apache.org/jira/browse/IGNITE-14598 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Nikita Safonov >Assignee: Mauricio Stekl >Priority: Major > > Please navigate to [https://ignite.apache.org/download.cgi] > 3RD PARTY > BINARIES and change the *GridGain Professional Edition* refernce text to > *GridGain Community Edition.* The link itself is correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14598) Change the Download page reference text
[ https://issues.apache.org/jira/browse/IGNITE-14598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14598: --- Assignee: Mauricio Stekl > Change the Download page reference text > --- > > Key: IGNITE-14598 > URL: https://issues.apache.org/jira/browse/IGNITE-14598 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Nikita Safonov >Assignee: Mauricio Stekl >Priority: Major > > Please navigate to [https://ignite.apache.org/download.cgi] > 3RD PARTY > BINARIES and change the *GridGain Professional Edition* refernce text to > *GridGain Community Edition.* The link itself is correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14533) [Ignite Website] Update for top line event promotion
[ https://issues.apache.org/jira/browse/IGNITE-14533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14533. - Resolution: Done > [Ignite Website] Update for top line event promotion > > > Key: IGNITE-14533 > URL: https://issues.apache.org/jira/browse/IGNITE-14533 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > [~mstekl], please change the topline event promotion for the next meetup: > > April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite > Developer > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14533) [Ignite Website] Update for top line event promotion
[ https://issues.apache.org/jira/browse/IGNITE-14533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14533: --- Assignee: Mauricio Stekl > [Ignite Website] Update for top line event promotion > > > Key: IGNITE-14533 > URL: https://issues.apache.org/jira/browse/IGNITE-14533 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > [~mstekl], please change the topline event promotion for the next meetup: > > April 28, 2021: Apache Ignite Native Persistence Storage. Overview by Ignite > Developer > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/277298901/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14454) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14454. - Resolution: Fixed > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-14454 > URL: https://issues.apache.org/jira/browse/IGNITE-14454 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > please update schedule [https://ignite.apache.org/events.html] with events > below: > *Distributed Java DBs Under the Hood: Components & Interactions Between Them* > London Java Community, Val Kulichenko > April 7, 2021 > During the session, we create a simple (although fully workable) distributed > cache in Java, almost from scratch. We use the cache to demonstrate basic > CRUD operations, as well as to demonstrate how scalability can be improved by > adding resources to the system. > Read > more=[https://www.eventbrite.co.uk/e/distributed-java-databases-under-the-hood-tickets-148903304793] > *Why Distributed SQL Is Not As Easy As It Looks* > Highload++, Stan Lukyanov > May 18, 2021 > In this talk, we'll cover why distributed SQL is needed, how it differs from > SQL in traditional databases, what it does well, and what doesn't. Apache > Ignite will be used as an example of distributed SQL support. > Read more = [https://www.highload.ru/spring/2021/abstracts/6686] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14454) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-14454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14454: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-14454 > URL: https://issues.apache.org/jira/browse/IGNITE-14454 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > please update schedule [https://ignite.apache.org/events.html] with events > below: > *Distributed Java DBs Under the Hood: Components & Interactions Between Them* > London Java Community, Val Kulichenko > April 7, 2021 > During the session, we create a simple (although fully workable) distributed > cache in Java, almost from scratch. We use the cache to demonstrate basic > CRUD operations, as well as to demonstrate how scalability can be improved by > adding resources to the system. > Read > more=[https://www.eventbrite.co.uk/e/distributed-java-databases-under-the-hood-tickets-148903304793] > *Why Distributed SQL Is Not As Easy As It Looks* > Highload++, Stan Lukyanov > May 18, 2021 > In this talk, we'll cover why distributed SQL is needed, how it differs from > SQL in traditional databases, what it does well, and what doesn't. Apache > Ignite will be used as an example of distributed SQL support. > Read more = [https://www.highload.ru/spring/2021/abstracts/6686] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14436. - Resolution: Fixed > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Assignee: Mauricio Stekl >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310680#comment-17310680 ] Mauricio Stekl commented on IGNITE-14436: - Hi, I renamed the dir scaladocs/ to scaladoc/ since that's the name we had used in the past and we also have lots of incoming links to that dir. > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Assignee: Mauricio Stekl >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14436: --- Assignee: Mauricio Stekl > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Assignee: Mauricio Stekl >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14387) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-14387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14387. - Resolution: Fixed [~romanova.ks.spb] I've added the event to the calendar. > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-14387 > URL: https://issues.apache.org/jira/browse/IGNITE-14387 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > [~mstekl] please add new event to [the schedule > :|https://ignite.apache.org/events.html] > Distributed Java DBs Under the Hood: Components & Interactions Between Them > Chicago PostgreSQL Meetup Group, Val Kulichenko > April 13, 2021 > During the session, we create a simple (although fully workable) distributed > cache in Java, almost from scratch. We use the cache to demonstrate basic > CRUD operations, as well as to demonstrate how scalability can be improved by > adding resources to the system. > Read more = > https://www.meetup.com/Chicago-PostgreSQL-User-Group/events/277073375/ > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14387) [Ignite Website] Update for events schedule
[ https://issues.apache.org/jira/browse/IGNITE-14387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14387: --- Assignee: Mauricio Stekl > [Ignite Website] Update for events schedule > --- > > Key: IGNITE-14387 > URL: https://issues.apache.org/jira/browse/IGNITE-14387 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Minor > > [~mstekl] please add new event to [the schedule > :|https://ignite.apache.org/events.html] > Distributed Java DBs Under the Hood: Components & Interactions Between Them > Chicago PostgreSQL Meetup Group, Val Kulichenko > April 13, 2021 > During the session, we create a simple (although fully workable) distributed > cache in Java, almost from scratch. We use the cache to demonstrate basic > CRUD operations, as well as to demonstrate how scalability can be improved by > adding resources to the system. > Read more = > https://www.meetup.com/Chicago-PostgreSQL-User-Group/events/277073375/ > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14332) Update for event schedule page
[ https://issues.apache.org/jira/browse/IGNITE-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14332. - Resolution: Fixed I've updated the list of events accordingly. > Update for event schedule page > -- > > Key: IGNITE-14332 > URL: https://issues.apache.org/jira/browse/IGNITE-14332 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl] please update [the events > schedule|https://ignite.apache.org/events.html] with the following events: > Distributed Java Databases Under the Hood: Main Components and Interactions > Seattle Java User Group, Val Kulichenko > April 20, 2021 > During the session, we create a simple (although fully workable) distributed > cache in Java, almost from scratch. We use the cache to demonstrate basic > CRUD operations, as well as to demonstrate how scalability can be improved by > adding resources to the system. > Learn more = [https://www.meetup.com/seajug/events/276324545/] > Dealing with Network Overhead in Distributed Systems: An Effective Approach > to Working with Data > DOTNEXT Russia, Pavel Tupitsyn > April 20, 21 > Modern apps consist of many subsystems: databases, caches, event brokers. > The single user request can involve multiple internal network calls. We will > talk about data locality, reducing network overhead, improving performance > and scalability. Benchmarks, demos, live coding, and practical examples await. > Read more = > [https://dotnext-piter.ru/en/2021/spb/talks/3ar6q8gmbfi86lhbduts0k/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14332) Update for event schedule page
[ https://issues.apache.org/jira/browse/IGNITE-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14332: --- Assignee: Mauricio Stekl > Update for event schedule page > -- > > Key: IGNITE-14332 > URL: https://issues.apache.org/jira/browse/IGNITE-14332 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Major > > [~mstekl] please update [the events > schedule|https://ignite.apache.org/events.html] with the following events: > Distributed Java Databases Under the Hood: Main Components and Interactions > Seattle Java User Group, Val Kulichenko > April 20, 2021 > During the session, we create a simple (although fully workable) distributed > cache in Java, almost from scratch. We use the cache to demonstrate basic > CRUD operations, as well as to demonstrate how scalability can be improved by > adding resources to the system. > Learn more = [https://www.meetup.com/seajug/events/276324545/] > Dealing with Network Overhead in Distributed Systems: An Effective Approach > to Working with Data > DOTNEXT Russia, Pavel Tupitsyn > April 20, 21 > Modern apps consist of many subsystems: databases, caches, event brokers. > The single user request can involve multiple internal network calls. We will > talk about data locality, reducing network overhead, improving performance > and scalability. Benchmarks, demos, live coding, and practical examples await. > Read more = > [https://dotnext-piter.ru/en/2021/spb/talks/3ar6q8gmbfi86lhbduts0k/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14287) Ignite Accessibility Check: Broken links
[ https://issues.apache.org/jira/browse/IGNITE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301931#comment-17301931 ] Mauricio Stekl commented on IGNITE-14287: - Submitted fixes for all of the broken links, except for the ones from docs, listed on the previous comment. > Ignite Accessibility Check: Broken links > > > Key: IGNITE-14287 > URL: https://issues.apache.org/jira/browse/IGNITE-14287 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > Attachments: Broken links (Outbound).xlsx > > > While doing Ignite's usability audit, We have figured out that there's a > small bunch of broken links on the website, leading to 404 pages. The > attached report indicates the origin of these. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14287) Ignite Accessibility Check: Broken links
[ https://issues.apache.org/jira/browse/IGNITE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301922#comment-17301922 ] Mauricio Stekl commented on IGNITE-14287: - [~nsafonov], there are 3 items from this list which belong to documentations, would you please help fixing? # On the left navigation the link for Machine Learning -> Ensemble Methods -> Bagging is pointing to /docs/latest/machine-learning/ensemble-methods/baggin (with the missing 'g' at the end of the URL) # On /docs/latest/machine-learning/machine-learning there is a link to [/docs/latest/machine-learning/binary-classification/random-forest|https://ignite.apache.org/docs/latest/machine-learning/binary-classification/random-forest] Thanks! > Ignite Accessibility Check: Broken links > > > Key: IGNITE-14287 > URL: https://issues.apache.org/jira/browse/IGNITE-14287 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > Attachments: Broken links (Outbound).xlsx > > > While doing Ignite's usability audit, We have figured out that there's a > small bunch of broken links on the website, leading to 404 pages. The > attached report indicates the origin of these. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14215. - Resolution: Fixed > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14287) Ignite Accessibility Check: Broken links
[ https://issues.apache.org/jira/browse/IGNITE-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl updated IGNITE-14287: Labels: audit (was: ) > Ignite Accessibility Check: Broken links > > > Key: IGNITE-14287 > URL: https://issues.apache.org/jira/browse/IGNITE-14287 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > Attachments: Broken links (Outbound).xlsx > > > While doing Ignite's usability audit, We have figured out that there's a > small bunch of broken links on the website, leading to 404 pages. The > attached report indicates the origin of these. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14287) Ignite Accessibility Check: Broken links
Mauricio Stekl created IGNITE-14287: --- Summary: Ignite Accessibility Check: Broken links Key: IGNITE-14287 URL: https://issues.apache.org/jira/browse/IGNITE-14287 Project: Ignite Issue Type: Bug Components: website Reporter: Mauricio Stekl Assignee: Mauricio Stekl Attachments: Broken links (Outbound).xlsx While doing Ignite's usability audit, We have figured out that there's a small bunch of broken links on the website, leading to 404 pages. The attached report indicates the origin of these. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl updated IGNITE-14215: Labels: audit (was: ) > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Labels: audit > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295749#comment-17295749 ] Mauricio Stekl commented on IGNITE-14215: - I added the tracking codes to the different API docs for latest release using a custom PHP script, similar to what we usually do to add GA tracking code. This would work as a solution instead of altering the templates used to build the docs. [~dmagda] do you think we can close this ticket? Or we should pursue the idea of altering the API docs templates? > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14268) [Ignite Website] Content updates 2021-03-02
[ https://issues.apache.org/jira/browse/IGNITE-14268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294929#comment-17294929 ] Mauricio Stekl commented on IGNITE-14268: - [~romanova.ks.spb], I made the changes to the website. Let me know if you see further updates. > [Ignite Website] Content updates 2021-03-02 > --- > > Key: IGNITE-14268 > URL: https://issues.apache.org/jira/browse/IGNITE-14268 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > Please update the following pages with new information: > *1. The text banner on the top of the website* > Please change the past meetup for the upcoming: > April 13, 2021: Using Ignite and JBoss Drools to Implement a Complex Event > Processing Solution > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] > > *2. Events Schedule* [https://ignite.apache.org/events.html] > Please update the page. New events: > *How to use Apache Ignite and Spring to build a reliable distributed web > application* > Webinar, Semyon Danilov > March 17, 2021 > Spring is a popular framework, and Apache Ignite is a fast layer for data > storage. Adding Ignite enables you to manage http sessions, cache-application > data, and so on. During this 1.5 hour session, Semyon uses the Spring > framework to create a simple web application and demonstrates how Apache > Ignite can empower the application. > [https://www.gridgain.com/resources/webinars/how-use-apache-ignite-and-spring-build-reliable-distributed-web-application] > > > *Using Ignite and JBoss Drools to Implement a Complex Event Processing > Solution* > Virtual Apache Ignite Meetup, Manoel Pereira de Lima Junior & Ney Luiz Montes > Junior > April 13, 2021 > In this talk, we describe and show how to use Apache Ignite and JBoss Drools > to design a complex event processing (CEP) solution. The solution processes > and correlates millions of events per second from a publish/subscribe message > broker and another kind of events streamer. The CEP solution that we > demonstrate has a microservices architecture with real-time automation of > CI/CD. We show how we have used this highly scalable CEP microservices > ecosystem since 2018 to support a digital-service and marketing platform for > one of the largest banks in Brazil. > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] > > *3. List of Committers and PMC members update* > [https://ignite.apache.org/community/resources.html#people] > Artem Budnikov, Igor Seliverstov, Ivan Rakov are not with GridGain anymore :( > Please make the company blank for them at the moment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14268) [Ignite Website] Content updates 2021-03-02
[ https://issues.apache.org/jira/browse/IGNITE-14268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14268. - Resolution: Fixed > [Ignite Website] Content updates 2021-03-02 > --- > > Key: IGNITE-14268 > URL: https://issues.apache.org/jira/browse/IGNITE-14268 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > Please update the following pages with new information: > *1. The text banner on the top of the website* > Please change the past meetup for the upcoming: > April 13, 2021: Using Ignite and JBoss Drools to Implement a Complex Event > Processing Solution > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] > > *2. Events Schedule* [https://ignite.apache.org/events.html] > Please update the page. New events: > *How to use Apache Ignite and Spring to build a reliable distributed web > application* > Webinar, Semyon Danilov > March 17, 2021 > Spring is a popular framework, and Apache Ignite is a fast layer for data > storage. Adding Ignite enables you to manage http sessions, cache-application > data, and so on. During this 1.5 hour session, Semyon uses the Spring > framework to create a simple web application and demonstrates how Apache > Ignite can empower the application. > [https://www.gridgain.com/resources/webinars/how-use-apache-ignite-and-spring-build-reliable-distributed-web-application] > > > *Using Ignite and JBoss Drools to Implement a Complex Event Processing > Solution* > Virtual Apache Ignite Meetup, Manoel Pereira de Lima Junior & Ney Luiz Montes > Junior > April 13, 2021 > In this talk, we describe and show how to use Apache Ignite and JBoss Drools > to design a complex event processing (CEP) solution. The solution processes > and correlates millions of events per second from a publish/subscribe message > broker and another kind of events streamer. The CEP solution that we > demonstrate has a microservices architecture with real-time automation of > CI/CD. We show how we have used this highly scalable CEP microservices > ecosystem since 2018 to support a digital-service and marketing platform for > one of the largest banks in Brazil. > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] > > *3. List of Committers and PMC members update* > [https://ignite.apache.org/community/resources.html#people] > Artem Budnikov, Igor Seliverstov, Ivan Rakov are not with GridGain anymore :( > Please make the company blank for them at the moment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14268) [Ignite Website] Content updates 2021-03-02
[ https://issues.apache.org/jira/browse/IGNITE-14268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14268: --- Assignee: Mauricio Stekl > [Ignite Website] Content updates 2021-03-02 > --- > > Key: IGNITE-14268 > URL: https://issues.apache.org/jira/browse/IGNITE-14268 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Mauricio Stekl >Priority: Trivial > > Please update the following pages with new information: > *1. The text banner on the top of the website* > Please change the past meetup for the upcoming: > April 13, 2021: Using Ignite and JBoss Drools to Implement a Complex Event > Processing Solution > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] > > *2. Events Schedule* [https://ignite.apache.org/events.html] > Please update the page. New events: > *How to use Apache Ignite and Spring to build a reliable distributed web > application* > Webinar, Semyon Danilov > March 17, 2021 > Spring is a popular framework, and Apache Ignite is a fast layer for data > storage. Adding Ignite enables you to manage http sessions, cache-application > data, and so on. During this 1.5 hour session, Semyon uses the Spring > framework to create a simple web application and demonstrates how Apache > Ignite can empower the application. > [https://www.gridgain.com/resources/webinars/how-use-apache-ignite-and-spring-build-reliable-distributed-web-application] > > > *Using Ignite and JBoss Drools to Implement a Complex Event Processing > Solution* > Virtual Apache Ignite Meetup, Manoel Pereira de Lima Junior & Ney Luiz Montes > Junior > April 13, 2021 > In this talk, we describe and show how to use Apache Ignite and JBoss Drools > to design a complex event processing (CEP) solution. The solution processes > and correlates millions of events per second from a publish/subscribe message > broker and another kind of events streamer. The CEP solution that we > demonstrate has a microservices architecture with real-time automation of > CI/CD. We show how we have used this highly scalable CEP microservices > ecosystem since 2018 to support a digital-service and marketing platform for > one of the largest banks in Brazil. > [https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276693067/] > > *3. List of Committers and PMC members update* > [https://ignite.apache.org/community/resources.html#people] > Artem Budnikov, Igor Seliverstov, Ivan Rakov are not with GridGain anymore :( > Please make the company blank for them at the moment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13978) Ignite 3 alpha Unix binary opens on click instead of being downloaded
[
https://issues.apache.org/jira/browse/IGNITE-13978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294578#comment-17294578
]
Mauricio Stekl commented on IGNITE-13978:
-
[~vkulichenko], per the response from INFRA-21332, I assume we can close this
ticket. Am I right? Thanks.
> Ignite 3 alpha Unix binary opens on click instead of being downloaded
> -
>
> Key: IGNITE-13978
> URL: https://issues.apache.org/jira/browse/IGNITE-13978
> Project: Ignite
> Issue Type: Bug
> Components: website
>Affects Versions: 3.0.0-alpha1
>Reporter: Valentin Kulichenko
>Assignee: Mauricio Stekl
>Priority: Critical
>
> 1. Go to binary downloads: https://ignite.apache.org/download.cgi#binaries
> 2. Locate the 3.0.0 alpha and click on the download for Unix.
> 3. Expected: {{ignite}} file is downloaded. Actual: the file opens up in the
> same window.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14260) Replace HomeAway picture with Vrbo
[ https://issues.apache.org/jira/browse/IGNITE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14260. - Resolution: Fixed > Replace HomeAway picture with Vrbo > -- > > Key: IGNITE-14260 > URL: https://issues.apache.org/jira/browse/IGNITE-14260 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the > main page with the Vrbo one: > https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14260) Replace HomeAway picture with Vrbo
[ https://issues.apache.org/jira/browse/IGNITE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293121#comment-17293121 ] Mauricio Stekl commented on IGNITE-14260: - [~dmagda] replaced the icon on the homepage: [https://github.com/apache/ignite-website/pull/76] > Replace HomeAway picture with Vrbo > -- > > Key: IGNITE-14260 > URL: https://issues.apache.org/jira/browse/IGNITE-14260 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the > main page with the Vrbo one: > https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14260) Replace HomeAway picture with Vrbo
[ https://issues.apache.org/jira/browse/IGNITE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14260: --- Assignee: Mauricio Stekl > Replace HomeAway picture with Vrbo > -- > > Key: IGNITE-14260 > URL: https://issues.apache.org/jira/browse/IGNITE-14260 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the > main page with the Vrbo one: > https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292889#comment-17292889 ] Mauricio Stekl commented on IGNITE-14215: - [~vveider], Denis mentioned you might be able to help with this ticket. Could you please? > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[
https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292888#comment-17292888
]
Mauricio Stekl commented on IGNITE-14215:
-
The metrics needs to be enabled on the API docs, at least on the JavaDocs we
use for the website.
These are the codes for the templates:
(function(m,e,t,r,i,k,a)\{m[i]=m[i]||function(){(m[i].a=m[i].a||[]).push(arguments)};
m[i].l=1*newDate();k=e.createElement(t),a=e.getElementsByTagName(t)[0],k.async=1,k.src=r,a.parentNode.insertBefore(k,a)})
(window, document, "script", "https://mc.yandex.ru/metrika/tag.js";, "ym");
ym(72949126, "init", {
clickmap:true,
trackLinks:true,
accurateTrackBounce:true,
webvisor:true
});
https://mc.yandex.ru/watch/72949126"style="position:absolute;
left:-px;"alt=""/>
window.__lo_site_id = 284467;
(function() {
varwa = document.createElement('script'); wa.type = 'text/javascript'; wa.async
= true;
wa.src = 'https://d10lpsik1i8c69.cloudfront.net/w.js';
vars = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(wa, s);
})();
> Website: Enable Lucky Orange and Yandex Metrics
> ---
>
> Key: IGNITE-14215
> URL: https://issues.apache.org/jira/browse/IGNITE-14215
> Project: Ignite
> Issue Type: Bug
> Components: website
>Reporter: Denis A. Magda
>Assignee: Mauricio Stekl
>Priority: Major
>
> We're conducting a usability audit of the Ignite website to better understand
> what parts of the site get more attention and what doesn't resonate with
> developers landing on the pages. The goal is to introduce and explain Ignite
> in the most concise and technical way, and to guide the users from the
> landing pages to documentation and other pages so that they can transition
> with their Ignite journey seamlessly.
>
> To better understand how the users perceive the information on the current
> web pages, we need to see heatmaps and other advanced metrics that are
> supported by the following tools:
> * [https://www.luckyorange.com|https://www.luckyorange.com/]
> * [https://metrica.yandex.com/about]?
> Let's use the tools for the time of the audit. All the data is capture and
> kept anonymous.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291918#comment-17291918 ] Mauricio Stekl commented on IGNITE-14215: - Hi, I've sent a PR with the implementation of these tools: [https://github.com/apache/ignite-website/pull/74] Please merge when you have a chance. Thanks. > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14215: --- Assignee: Mauricio Stekl > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266241#comment-17266241 ] Mauricio Stekl edited comment on IGNITE-13941 at 1/15/21, 5:49 PM: --- [~dmagda], sorry, the editor added the comma at the end as part of the link: [https://github.com/rbuchberger/jekyll_picture_tag] About the sizes, actually nowadays is a good practice to set the width/height of images to avoid layout shifts. You can read more about CLS here: [https://web.dev/cls/] and here: https://web.dev/optimize-cls/#modern-best-practice The image can still be adjusted automatically with CSS. In our doc I already set the rules to avoid images larger than available space, etc. was (Author: mstekl): [~dmagda], sorry, the editor added the comma at the end as part of the link: [https://github.com/rbuchberger/jekyll_picture_tag] About the sizes, actually nowadays is a good practice to set the width/height of images to avoid layout shifts. You can read more about CLS here: [https://web.dev/cls/] The image can still be adjusted automatically with CSS. In our doc I already set the rules to avoid images larger than available space, etc. > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-15 at 12.53.29.png > > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266241#comment-17266241 ] Mauricio Stekl commented on IGNITE-13941: - [~dmagda], sorry, the editor added the comma at the end as part of the link: [https://github.com/rbuchberger/jekyll_picture_tag] About the sizes, actually nowadays is a good practice to set the width/height of images to avoid layout shifts. You can read more about CLS here: [https://web.dev/cls/] The image can still be adjusted automatically with CSS. In our doc I already set the rules to avoid images larger than available space, etc. > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-15 at 12.53.29.png > > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[
https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266154#comment-17266154
]
Mauricio Stekl commented on IGNITE-13941:
-
[~dmagda], the good news is the fixes are being already picked up by Google.
The pages ranked as "poor" performance, are decreasing. However not all of the
issues are fully resolved yet, and that's why the 'need improvements' grew up
proportionally.
One of the issues is with embed images on the docs, and we might need help from
the documentation editors to address it. When images are included, it is
necessary to explicitly set the width/height for it. When this is done, the
browser can allocate space and the UI is not jumping around for the user. This
is one of the reasons for CLS.
I only found a way of doing this when using asciidoc, and is by separating the
sizes with commas after the title, like:
{{image::images/ijimport.png[Importing a Project in IntelliJ, 615, 480]}}
The width would be 615, and height 480.
However, the right way would be to resize the original image to be served to
different screen sizes. There is one plugin I found,
[https://github.com/rbuchberger/jekyll_picture_tag,] which does this for
Jekyll, but I couldn't make it work with asciidoc. I must say my knowledge of
Jekyll/Asciidoc is quite limited, so maybe someone else could chime in here.
!Screen Shot 2021-01-15 at 12.53.29.png!
> Poor CLS reported for multiple website pages
>
>
> Key: IGNITE-13941
> URL: https://issues.apache.org/jira/browse/IGNITE-13941
> Project: Ignite
> Issue Type: Bug
> Components: website
>Reporter: Denis A. Magda
>Assignee: Mauricio Stekl
>Priority: Major
> Attachments: Screen Shot 2021-01-15 at 12.53.29.png
>
>
> Google reported a poor CLS index for multiple pages:
> [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F]
>
> The mobile traffic is affected even more severely. Need to address the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl updated IGNITE-13941: Attachment: Screen Shot 2021-01-15 at 12.53.29.png > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Attachments: Screen Shot 2021-01-15 at 12.53.29.png > > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265295#comment-17265295 ] Mauricio Stekl commented on IGNITE-13941: - [~dmagda] I just submitted another patch, which includes optimizations for the docs templates. I optimized the templates in order reduce CLS, and to improve scoring at Lighthouse in general. It's important to rebuild the documentations for 2.9.1, and I would like to perform some measures at the docs after this patch is deployed. I will probably need to submit further optimizations. > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13941) Poor CLS reported for multiple website pages
[ https://issues.apache.org/jira/browse/IGNITE-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264416#comment-17264416 ] Mauricio Stekl commented on IGNITE-13941: - [~dmagda] I sent a patch^[1]^ which optimizes CLS for all pages under user-cases/ which were being reported. We'd need to wait how GSC indexes this and if the scoring improves. I will review CLS for the docs later this week. ^[1]^ https://github.com/apache/ignite-website/pull/68 > Poor CLS reported for multiple website pages > > > Key: IGNITE-13941 > URL: https://issues.apache.org/jira/browse/IGNITE-13941 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > Google reported a poor CLS index for multiple pages: > [https://search.google.com/search-console/core-web-vitals?resource_id=https%3A%2F%2Fignite.apache.org%2F] > > The mobile traffic is affected even more severely. Need to address the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13988) Version dropdown on docs is not aligned to the right on Safari
[ https://issues.apache.org/jira/browse/IGNITE-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264370#comment-17264370 ] Mauricio Stekl commented on IGNITE-13988: - Patch submitted: [https://github.com/apache/ignite-website/pull/67] The new css might not be picked if cached, so it's suggested to rebuild the docs in order to force cache invalidation. > Version dropdown on docs is not aligned to the right on Safari > -- > > Key: IGNITE-13988 > URL: https://issues.apache.org/jira/browse/IGNITE-13988 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Mauricio Stekl >Assignee: Mauricio Stekl >Priority: Minor > Attachments: Screen Shot 2021-01-13 at 11.10.04.png > > > This can be reproduced only on Safari. Basically caused because > 'text-align-last' doesn't work on this browser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13988) Version dropdown on docs is not aligned to the right on Safari
Mauricio Stekl created IGNITE-13988: --- Summary: Version dropdown on docs is not aligned to the right on Safari Key: IGNITE-13988 URL: https://issues.apache.org/jira/browse/IGNITE-13988 Project: Ignite Issue Type: Bug Components: website Reporter: Mauricio Stekl Assignee: Mauricio Stekl Attachments: Screen Shot 2021-01-13 at 11.10.04.png This can be reproduced only on Safari. Basically caused because 'text-align-last' doesn't work on this browser. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13978) Ignite 3 alpha Unix binary opens on click instead of being downloaded
[
https://issues.apache.org/jira/browse/IGNITE-13978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263568#comment-17263568
]
Mauricio Stekl commented on IGNITE-13978:
-
hi [~vkulichenko] , I’ve been trying a few things locally but I’m afraid I
can't find a workaround for this. The ‘download’ attribute only works with
same-origin urls, and since these are mirrors, it will be ignored.
As far as I know we can't control the headers for the mirrors, right? If we
can, I would suggest adding a rule on an .htaccess to force the mime type of
the binary file.
Another alternative could be adding an extension to the file, so the browser
can detect the mime type automatically:
[https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types]
I would suggest renaming the binary to ignite.sh. Not 100% sure it would work
though, It'd depend on the mirror server config.
> Ignite 3 alpha Unix binary opens on click instead of being downloaded
> -
>
> Key: IGNITE-13978
> URL: https://issues.apache.org/jira/browse/IGNITE-13978
> Project: Ignite
> Issue Type: Bug
> Components: website
>Reporter: Valentin Kulichenko
>Assignee: Mauricio Stekl
>Priority: Blocker
> Fix For: 3.0.0-alpha1
>
>
> 1. Go to binary downloads: https://ignite.apache.org/download.cgi#binaries
> 2. Locate the 3.0.0 alpha and click on the download for Unix.
> 3. Expected: {{ignite}} file is downloaded. Actual: the file opens up in the
> same window.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13978) Ignite 3 alpha Unix binary opens on click instead of being downloaded
[
https://issues.apache.org/jira/browse/IGNITE-13978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauricio Stekl reassigned IGNITE-13978:
---
Assignee: Mauricio Stekl
> Ignite 3 alpha Unix binary opens on click instead of being downloaded
> -
>
> Key: IGNITE-13978
> URL: https://issues.apache.org/jira/browse/IGNITE-13978
> Project: Ignite
> Issue Type: Bug
> Components: website
>Reporter: Valentin Kulichenko
>Assignee: Mauricio Stekl
>Priority: Blocker
> Fix For: 3.0.0-alpha1
>
>
> 1. Go to binary downloads: https://ignite.apache.org/download.cgi#binaries
> 2. Locate the 3.0.0 alpha and click on the download for Unix.
> 3. Expected: {{ignite}} file is downloaded. Actual: the file opens up in the
> same window.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13933) Add an ability to customize documentation source repo
[
https://issues.apache.org/jira/browse/IGNITE-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256659#comment-17256659
]
Mauricio Stekl commented on IGNITE-13933:
-
[~vkulichenko], I sent a patch to fix the issue:
[https://github.com/apache/ignite-website/pull/66]
I didn't add another parameter to the script, but I'm picking the first char of
the --version parameter. The doc can still be built using the same syntax,
like:
{{./build.sh --version=3.0.0-alpha1 --github-branch=ignite-3.0.0-alpha1}}
> Add an ability to customize documentation source repo
> -
>
> Key: IGNITE-13933
> URL: https://issues.apache.org/jira/browse/IGNITE-13933
> Project: Ignite
> Issue Type: Improvement
> Components: website
>Reporter: Valentin Kulichenko
>Assignee: Mauricio Stekl
>Priority: Critical
> Fix For: 3.0.0-alpha1
>
>
> Documentation deployment script current has the original Ignite repo
> hardcoded:
> https://github.com/apache/ignite-website/blob/master/_docs/build.sh#L42
> Ignite 3.x is located in a different repo: https://github.com/apache/ignite-3
> Suggestion: add a parameter that would allow specifying the version (2.x or
> 3.x). The script should then pick the corresponding repo URL and fetch the
> sources from there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13933) Add an ability to customize documentation source repo
[ https://issues.apache.org/jira/browse/IGNITE-13933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-13933: --- Assignee: Mauricio Stekl > Add an ability to customize documentation source repo > - > > Key: IGNITE-13933 > URL: https://issues.apache.org/jira/browse/IGNITE-13933 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Valentin Kulichenko >Assignee: Mauricio Stekl >Priority: Critical > Fix For: 3.0.0-alpha1 > > > Documentation deployment script current has the original Ignite repo > hardcoded: > https://github.com/apache/ignite-website/blob/master/_docs/build.sh#L42 > Ignite 3.x is located in a different repo: https://github.com/apache/ignite-3 > Suggestion: add a parameter that would allow specifying the version (2.x or > 3.x). The script should then pick the corresponding repo URL and fetch the > sources from there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255719#comment-17255719 ] Mauricio Stekl commented on IGNITE-13884: - [~mmuzaf], [~dmagda], The problem was with a rewrite rule in the .htaccess. I submitted a patch that resolves the issue, and also updated the instructions in the wiki with the step #7 which needs to be updated in the next release. > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254646#comment-17254646 ] Mauricio Stekl commented on IGNITE-13779: - [~dmagda], I sent a patch with these fixes. For the description alignment, I left-aligned the description and the title too because it looked very weird to have different alignments for each of the text elements. I left the button centered though, I think it looks fine as it is. On an unrelated topic, we are having too many buttons in the home page with non-descriptive text: "Learn More". Attached is a screenshot of the Lighthouse test for SEO. Might be good if the labels can be reformulated to something more descriptive, like "Learn More About XYZ". !Screen Shot 2020-12-24 at 16.57.21.png! > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: Screen Shot 2020-12-24 at 16.57.21.png, > banner_text_issue.PNG, description_alignment_issue.PNG, features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl updated IGNITE-13779: Attachment: Screen Shot 2020-12-24 at 16.57.21.png > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: Screen Shot 2020-12-24 at 16.57.21.png, > banner_text_issue.PNG, description_alignment_issue.PNG, features_issue.PNG > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254584#comment-17254584 ] Mauricio Stekl commented on IGNITE-13884: - [~YAMolochkov], I've submitted a PR with a bug fix for the versioning: https://github.com/apache/ignite-website/pull/58 Could you please merge when you have a chance? I know Denis is going to be offline for a few days. Thanks! > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254206#comment-17254206 ] Mauricio Stekl commented on IGNITE-13853: - [~dmagda], good catch. I've sent a patch for it. Thanks! > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13884) Merge docs from ignite-2.9-docs into 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253770#comment-17253770 ] Mauricio Stekl commented on IGNITE-13884: - [~dmagda], I have sent a patch to fix those 2 items you mentioned. In order to make this work in the future, it will be necessary to rebuild the previous 'latest' version without specifying the --latest parameter. [~YAMolochkov], only for this case it is necessary to rebuild both the 2.9.1 and 2.9.0 docs again. I updated the instructions on the wiki with the new steps: [https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document#HowtoDocument-PublishingNewVersion] Let me know if you need help or have any questions. > Merge docs from ignite-2.9-docs into 2.9.1 > -- > > Key: IGNITE-13884 > URL: https://issues.apache.org/jira/browse/IGNITE-13884 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Major > Fix For: 2.9.1 > > Time Spent: 20m > Remaining Estimate: 0h > > The documentation contained in ignite-2.9-docs branch needs to be merged into > 2.9.1 branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253080#comment-17253080 ] Mauricio Stekl commented on IGNITE-13853: - [~dmagda], thanks for the review. I have fixed the lang selector and split the APIs menu from the Examples. This patch also fixes some issues with navigation for mobile: [https://github.com/apache/ignite-website/pull/54] > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > Attachments: Screen Shot 2020-12-18 at 12.55.15 PM.png > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251998#comment-17251998 ] Mauricio Stekl commented on IGNITE-13853: - [~dmagda], I've sent a PR with the changes to the docs navigation as you proposed. > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.9.1 > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13853) Add APIs, examples, language selector to the docs menu
[ https://issues.apache.org/jira/browse/IGNITE-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-13853: --- Assignee: Mauricio Stekl > Add APIs, examples, language selector to the docs menu > -- > > Key: IGNITE-13853 > URL: https://issues.apache.org/jira/browse/IGNITE-13853 > Project: Ignite > Issue Type: Improvement > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > Fix For: 2.9.1 > > > There is user feedback that suggests we need to rework our navigation menus > of the website and docs to improve the discoverability of APIs and examples. > Let's do the following. > > *Ignite Website Top-Level Navigation Menu > ([https://ignite.apache.org)|https://ignite.apache.org)/]* > * Add the "Docs" menu item before the "Features" item. The "Docs" _is a > single link_ (not a dropdown menu) that directs to the root of the latest > technical documentation: [https://ignite.apache.org/docs/latest/] > * Rename "Resources" to "Learn More". Remove "Documentation", "Documentation > (Chinese)" and "APIs" from this menu section. > * Remove "Events" from the top-level menu. Add the items/links from the menu > to the "Community" > > *Technical Documentation Top-Level Navigation Menu > ([https://ignite.apache.org/docs/latest/])* > * Remove the Github icon from the menu > * Add "APIs" after the "version" selector. The menu lists "Java", "C#/.NET", > "C++", "Scala". The "version" selector defines what version of an API is to > be opened. For instance, if a user chooses version "2.9.1" (to be released > soon) then "Java" of that version is to be opened. If instead, the user wants > to see the docs and APIs for "2.9.0", he just needs to selects that version > from the version menu. > * Add "Examples" after the "APIs". Add the following menu items: > ** "Java": [https://github.com/apache/ignite/tree/master/examples] > ** "C#/.NET": > [https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/examples] > ** "C++": > [https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples] > ** "Python": > [https://github.com/apache/ignite/tree/master/modules/platforms/python/examples] > ** "Node.JS": > [https://github.com/apache/ignite/tree/master/modules/platforms/nodejs/examples] > ** "PHP": > [https://github.com/apache/ignite/tree/master/modules/platforms/php/examples] > * Add a language selector drop-down list after the "search" text box. See > how it's implemented here: > [https://www.confluent.io.|https://www.confluent.io./] We'll have just two > menu items there: > ** "English": points out to the root of the main docs > [https://ignite.apache.org/docs/latest/] > ** "Chinese": [https://www.ignite-service.cn/doc/java/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251435#comment-17251435 ] Mauricio Stekl commented on IGNITE-13779: - [~dmagda], I sent another PR with the following changes: * updated the list of logos of users * reworked 'use cases' section, adding 2 buttons on each use case * implemented accordion for features section when using from mobile * did a clean up of css, splitting it in multiple files > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: feature_white_block_adjustment.png > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248061#comment-17248061 ] Mauricio Stekl commented on IGNITE-13779: - [~dmagda], I have sent another PR with a new round of changes: * Updated diagrams for Architects section * Adjusted alignments and spacing for diagrams * Improved height for code snipped under Features section * Made the top nav sticky * Increased spacing on the main homepage banner Please review when you have a chance, and let me know your thoughts. > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > Attachments: feature_white_block_adjustment.png > > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13779) Ignite as Distributed Database: Required Website Changes
[ https://issues.apache.org/jira/browse/IGNITE-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247382#comment-17247382 ] Mauricio Stekl commented on IGNITE-13779: - [~dmagda], I sent a PR with some more changes for the homepage: [https://github.com/apache/ignite-website/pull/44] Basically it includes: * redesign of the main banner * improved the layout for Architects section and updated its diagrams * updated new icons for DIH and Continuous Queries * small css fixes > Ignite as Distributed Database: Required Website Changes > > > Key: IGNITE-13779 > URL: https://issues.apache.org/jira/browse/IGNITE-13779 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Critical > > The community > [voted|http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html] > to define Ignite as a distributed database. > This is an umbrella ticket with all required website changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13589) Ignite Docs: the docs root must open the latest version
[ https://issues.apache.org/jira/browse/IGNITE-13589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225634#comment-17225634 ] Mauricio Stekl commented on IGNITE-13589: - [~dmagda], I sent a PR to fix this one. Here: https://github.com/apache/ignite-website/pull/39 > Ignite Docs: the docs root must open the latest version > --- > > Key: IGNITE-13589 > URL: https://issues.apache.org/jira/browse/IGNITE-13589 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Critical > Labels: new-docs > Fix For: 2.10 > > > If you open the default docs URL (https://ignite.apache.org/docs/), you'll > see a structure of a directory on the server. > That default URL needs to redirect to https://ignite.apache.org/docs/latest/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13527) Ignite Docs: redirect traffic from readme.io to the new docs
[ https://issues.apache.org/jira/browse/IGNITE-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215424#comment-17215424 ] Mauricio Stekl commented on IGNITE-13527: - [~dmagda], I submitted a PR that fix the issue: [https://github.com/apache/ignite-website/pull/36] > Ignite Docs: redirect traffic from readme.io to the new docs > > > Key: IGNITE-13527 > URL: https://issues.apache.org/jira/browse/IGNITE-13527 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: Denis A. Magda >Assignee: Denis A. Magda >Priority: Critical > Labels: new-docs > Attachments: Screen Shot 2020-10-15 at 1.54.03 PM.png > > > Publish the new docs onto the website: > * Add to the navigation menu > * Remove from the APIs page > * Update the documentation references across all the website pages (no any > reference to the readme.io) > * Update documentation contribution section: > https://ignite.apache.org/community/contribute.html > Readme Shutdown: > * Readme - redirect and shut down (or make available for 2.8 and earlier > versions). Add banners to every page announcing the new docs. Keep the readme > docs untouched for several weeks and then decide how to proceed. Google > should detect the news docs. Stop the indexing of the readme.io docs (Project > Settings ->Indexing by robots is ) > * add this to Appearance -> Customer > Include tags -> header > * Update the references on the website pointing to the new documentation > instead of the readme.io one. > * copy all readme sources and store them in the Ignite repo. Just in case if > anyone needs a page that was not ported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13522) Ignite Docs: Issues with the left-side navigation bar
[ https://issues.apache.org/jira/browse/IGNITE-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208457#comment-17208457 ] Mauricio Stekl edited comment on IGNITE-13522 at 10/6/20, 6:24 PM: --- I just submitted a PR to fix all these issues: [https://github.com/apache/ignite-website/pull/35] was (Author: mstekl): I just submitted a PR to fix all these issues except for #5: [https://github.com/apache/ignite-website/pull/34] > Ignite Docs: Issues with the left-side navigation bar > - > > Key: IGNITE-13522 > URL: https://issues.apache.org/jira/browse/IGNITE-13522 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis A. Magda >Priority: Blocker > Labels: new-docs > Fix For: 2.9 > > > There are several issues related to the left-side navigation menu: > # The navigation menu folds automatically. To reproduce - click on the > "Performance and Troubleshooting" -> "Handling Exceptions" page. The menu > will fold back. > # Make sure the menu behaves properly when you open second-level pages. For > instance, try "Extensions and Integrations"->"Ignite for > Spark"->"Installation" to ensure the menu is unfolded properly. > # The navigation menu is scrolled up automatically. Select "Performance and > Troubleshooting"->"Handling Exceptions" page. The page will be opened and the > navigation menu will be scrolled up again. > # Make sure that the menu is unfolded automatically when a reader opens the > page directly using its full address. Try this page: > https://ignite.apache.org/docs/latest/extensions-and-integrations/ignite-for-spark/ignite-dataframe > # When you select any section of a page using the *right navigation menu* > then the left navigation menu's position will be changed automatically (it > will be either scrolled up or down). To reproduce, select the "Configuring > Memory" -> "Memory Architecture" page with the left-side navigation menu. > Then, select the "Memory Defragmentation" section with the right-hand side > menu. Both the left and right-side menus will be scrolled down. This > shouldn't happen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13522) Ignite Docs: Issues with the left-side navigation bar
[ https://issues.apache.org/jira/browse/IGNITE-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208457#comment-17208457 ] Mauricio Stekl commented on IGNITE-13522: - I just submitted a PR to fix all these issues except for #5: [https://github.com/apache/ignite-website/pull/34] > Ignite Docs: Issues with the left-side navigation bar > - > > Key: IGNITE-13522 > URL: https://issues.apache.org/jira/browse/IGNITE-13522 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Denis A. Magda >Priority: Blocker > Labels: new-docs > Fix For: 2.9 > > > There are several issues related to the left-side navigation menu: > # The navigation menu folds automatically. To reproduce - click on the > "Performance and Troubleshooting" -> "Handling Exceptions" page. The menu > will fold back. > # Make sure the menu behaves properly when you open second-level pages. For > instance, try "Extensions and Integrations"->"Ignite for > Spark"->"Installation" to ensure the menu is unfolded properly. > # The navigation menu is scrolled up automatically. Select "Performance and > Troubleshooting"->"Handling Exceptions" page. The page will be opened and the > navigation menu will be scrolled up again. > # Make sure that the menu is unfolded automatically when a reader opens the > page directly using its full address. Try this page: > https://ignite.apache.org/docs/latest/extensions-and-integrations/ignite-for-spark/ignite-dataframe > # When you select any section of a page using the *right navigation menu* > then the left navigation menu's position will be changed automatically (it > will be either scrolled up or down). To reproduce, select the "Configuring > Memory" -> "Memory Architecture" page with the left-side navigation menu. > Then, select the "Memory Defragmentation" section with the right-hand side > menu. Both the left and right-side menus will be scrolled down. This > shouldn't happen. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13157) Upgrade build process for Javadocs
Mauricio Stekl created IGNITE-13157: --- Summary: Upgrade build process for Javadocs Key: IGNITE-13157 URL: https://issues.apache.org/jira/browse/IGNITE-13157 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Mauricio Stekl Attachments: gsc_mobile_errors.png I am reaching out to you all to see if you could help fix some issues with mobile usability in the Javadocs sections for Ignite website. I know you might think most users will not read the API doc using their smartphones, and that is true. But as you can see in the attached screenshot gsc_mobile_errors.png, we have errors related to mobile usability reported by Google itself through GSC. Obviously this affects our performance on search results, as Google is giving more and more priority to mobile friendly websites. For Apache Ignite website we basically have the largest part of the website with issues, since we only have around 30 pages mobile friendly, and 1000+ pages which are not. Specifically with Javadocs, the main problem is it contains old html frames for layout and navigation, among other markup bad practices, and this would make impossible to update any css to be responsive for small screens. From what I was able to find [[1]|https://bugs.openjdk.java.net/browse/JDK-8215599] [[2]|https://bugs.openjdk.java.net/browse/JDK-8196202], starting with JDK 9 there is a '--no-frames' option which fixes this problem. And with version 11 this option is enabled by default and other features included. You can see here how the new layout looks: [https://docs.oracle.com/en/java/javase/11/docs/api/index.html] Would it be possible to upgrade Java to version 11 only for building the javadocs? This might be a great starting point to fix these problems. Later we could update the .css to adjust font sizes and other details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
