[DISCUSSION] Major changes in Ignite in 2020

classic Classic list List threaded Threaded
4 messages Options
dmagda dmagda
Reply | Threaded
Open this post in threaded view
|

[DISCUSSION] Major changes in Ignite in 2020

Dear Ignite community,

Many of us want to see where Ignite is heading and ask for some sort of a 2020 course/plan/roadmap and a predictable schedule of major releases. Also, there are intentions to enhance some internal processes and collaboration approaches.

Let's start moving in that direction by defining 3-5 major changes you would like to contribute this year personally or will be glad to drive (like processes changes) and work together with someone else. Dear, Ignite user community, please share your suggestions as well.

Note, let's use this thread to collect major topics/directions/features/changes. Just respond with your proposals. Don't go into arguments if you don't agree with someone's opinions. Once the topics are collected, we'll create a wiki page and, most likely, will start working through specific items in focus groups and only then lay out a cohesive plan with some dates.
  
-
Denis
dmagda dmagda
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] Major changes in Ignite in 2020

My top list of changes is as follows:
  • Feature: New Ignite documentation on a new platform and with a new structure. Why? Ignite documentation has to help new application developers to get up and running as quickly as possible, it also has to become a primary source that answers most of the questions. Our current docs have a lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
  • Process Change: to be successful with the point above, documentation should be created/updated before we close a JIRA ticket for code/API/feature contribution. Why? First, application developers learn Ignite and create their Ignite-apps referring to API reference and technical documentation (and not to the source code), thus, documentation needs to be treated as an integral part of the whole project. Second, while writing a new documentation paragraph we could discover incompleteness of a fix/feature or usability issues before the change is released publicly.
-
Denis


On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
Dear Ignite community,

Many of us want to see where Ignite is heading and ask for some sort of a 2020 course/plan/roadmap and a predictable schedule of major releases. Also, there are intentions to enhance some internal processes and collaboration approaches.

Let's start moving in that direction by defining 3-5 major changes you would like to contribute this year personally or will be glad to drive (like processes changes) and work together with someone else. Dear, Ignite user community, please share your suggestions as well.

Note, let's use this thread to collect major topics/directions/features/changes. Just respond with your proposals. Don't go into arguments if you don't agree with someone's opinions. Once the topics are collected, we'll create a wiki page and, most likely, will start working through specific items in focus groups and only then lay out a cohesive plan with some dates.
  
-
Denis
Saikat Maitra Saikat Maitra
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] Major changes in Ignite in 2020

Hi Denis,

Thank you for sharing the list of top changes. The list looks good.

I wanted to share that efforts regarding IEP-36 is already underway and there are also open PRs under review and working through review feedback. One of the area that we are focussing is first we will merge changes in ignite-extensions repo before removing the specific migrated module from ignite repo.

There are also contribution from community on bug fixes in ignite-extensions repo as well which we are verifying and merging in ignite-extensions repo after running through CI pipeline in teamcity.

I like the focus area on docs and I really like the Apache Ignite Usecases page https://ignite.apache.org/provenusecases.html,  I would like to suggest if we can add a page like powered by Apache Ignite and list few Org who are already using Apache Ignite in prod.

Something similar to this page https://flink.apache.org/poweredby.html 
 
Regards,
Saikat






On Thu, Mar 19, 2020 at 1:44 PM Denis Magda <[hidden email]> wrote:
My top list of changes is as follows:
  • Feature: New Ignite documentation on a new platform and with a new structure. Why? Ignite documentation has to help new application developers to get up and running as quickly as possible, it also has to become a primary source that answers most of the questions. Our current docs have a lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
  • Process Change: to be successful with the point above, documentation should be created/updated before we close a JIRA ticket for code/API/feature contribution. Why? First, application developers learn Ignite and create their Ignite-apps referring to API reference and technical documentation (and not to the source code), thus, documentation needs to be treated as an integral part of the whole project. Second, while writing a new documentation paragraph we could discover incompleteness of a fix/feature or usability issues before the change is released publicly.
-
Denis


On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
Dear Ignite community,

Many of us want to see where Ignite is heading and ask for some sort of a 2020 course/plan/roadmap and a predictable schedule of major releases. Also, there are intentions to enhance some internal processes and collaboration approaches.

Let's start moving in that direction by defining 3-5 major changes you would like to contribute this year personally or will be glad to drive (like processes changes) and work together with someone else. Dear, Ignite user community, please share your suggestions as well.

Note, let's use this thread to collect major topics/directions/features/changes. Just respond with your proposals. Don't go into arguments if you don't agree with someone's opinions. Once the topics are collected, we'll create a wiki page and, most likely, will start working through specific items in focus groups and only then lay out a cohesive plan with some dates.
  
-
Denis
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] Major changes in Ignite in 2020

My top priorities:
  • Thin Client API extension: Compute, Continuous Queries, Services
  • .NET Near Cache: soon to come in Thick API, to be investigated for Thin Clients
  • .NET Modernization for Ignite 3.0: drop legacy .NET Framework support, target .NET Standard 2.0, add nullable annotations to the API

On Fri, Mar 20, 2020 at 5:23 AM Saikat Maitra <[hidden email]> wrote:
Hi Denis,

Thank you for sharing the list of top changes. The list looks good.

I wanted to share that efforts regarding IEP-36 is already underway and there are also open PRs under review and working through review feedback. One of the area that we are focussing is first we will merge changes in ignite-extensions repo before removing the specific migrated module from ignite repo.

There are also contribution from community on bug fixes in ignite-extensions repo as well which we are verifying and merging in ignite-extensions repo after running through CI pipeline in teamcity.

I like the focus area on docs and I really like the Apache Ignite Usecases page https://ignite.apache.org/provenusecases.html,  I would like to suggest if we can add a page like powered by Apache Ignite and list few Org who are already using Apache Ignite in prod.

Something similar to this page https://flink.apache.org/poweredby.html 
 
Regards,
Saikat






On Thu, Mar 19, 2020 at 1:44 PM Denis Magda <[hidden email]> wrote:
My top list of changes is as follows:
  • Feature: New Ignite documentation on a new platform and with a new structure. Why? Ignite documentation has to help new application developers to get up and running as quickly as possible, it also has to become a primary source that answers most of the questions. Our current docs have a lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
  • Process Change: to be successful with the point above, documentation should be created/updated before we close a JIRA ticket for code/API/feature contribution. Why? First, application developers learn Ignite and create their Ignite-apps referring to API reference and technical documentation (and not to the source code), thus, documentation needs to be treated as an integral part of the whole project. Second, while writing a new documentation paragraph we could discover incompleteness of a fix/feature or usability issues before the change is released publicly.
-
Denis


On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
Dear Ignite community,

Many of us want to see where Ignite is heading and ask for some sort of a 2020 course/plan/roadmap and a predictable schedule of major releases. Also, there are intentions to enhance some internal processes and collaboration approaches.

Let's start moving in that direction by defining 3-5 major changes you would like to contribute this year personally or will be glad to drive (like processes changes) and work together with someone else. Dear, Ignite user community, please share your suggestions as well.

Note, let's use this thread to collect major topics/directions/features/changes. Just respond with your proposals. Don't go into arguments if you don't agree with someone's opinions. Once the topics are collected, we'll create a wiki page and, most likely, will start working through specific items in focus groups and only then lay out a cohesive plan with some dates.
  
-
Denis