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 <saikat.mai...@gmail.com> 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 <dma...@apache.org> wrote: > >> My top list of changes is as follows: >> >> - Feature: New lightweight Apache Ignite website with advanced search >> engine optimizations and updated technical content. Why? Much better >> discoverability of Ignite via search engines like Google to let many more >> application developers learn about Ignite existence. This change is to be >> brought to live soon: >> >> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html >> >> >> - 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. >> >> >> - Feature: complete the modularization project by defining the Ignite >> core that will be released separately from Ignite extensions. The 'why' is >> written here: >> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization >> >> - >> Denis >> >> >> On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <dma...@apache.org> 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 >>> >>
