Re: Documenting Ignite

Hi Artem, Could you please check if you can edit now. Sincerely, Dmitriy Pavlov ср, 25 июл. 2018 г. в 14:03, Artem Budnikov : > Hi Dmitry, > > I've added a comment to the issue. > > My Confluence ID is a.budnikov. Could you please grant me permissions > required to edit pages. Thanks! > > >

Re: Documenting Ignite

Hi Dmitry, I've added a comment to the issue. My Confluence ID is a.budnikov. Could you please grant me permissions required to edit pages. Thanks! Artem On 24.07.2018 16:58, Dmitry Pavlov wrote: I've noticed now INFRA asks for feedback from us. Artem, will you provide feedback on done

Re: Documenting Ignite

I've noticed now INFRA asks for feedback from us. Artem, will you provide feedback on done change in https://issues.apache.org/jira/browse/INFRA-16803 вт, 24 июл. 2018 г. в 11:01, Dmitry Pavlov : > Hi Artem, > > This is page in Ignite space, so you could do updates. Of course, if you > have

Re: Documenting Ignite

Hi Artem, This is page in Ignite space, so you could do updates. Of course, if you have access to Ignite space in wiki. If not, please sign up and share your wiki login (id). Sincerely, Dmitriy Pavlov вт, 24 июл. 2018 г. в 10:25, Artem Budnikov : > Hi everyone, > > Despite what I've been told

Re: Documenting Ignite

Hi everyone, Despite what I've been told about INFRA, it responded exceptionally quickly and added the field :-) I think the page describing the process of creating IGNITE issues needs to

Re: Documenting Ignite

Hi everyone, I created an issue in the Apache INFRA project: https://issues.apache.org/jira/browse/INFRA-16803 Cheers, Artem On 19.07.2018 22:58, Dmitry Pavlov wrote: I appologize, initially I misundersood proposal. I've concluded that new doc issue will be created automatically by

Re: Documenting Ignite

I appologize, initially I misundersood proposal. I've concluded that new doc issue will be created automatically by closing original ticket, - this can be done by plugin only. If we just introduce flag or combobox for indicate doc is required, there is no technical issues, it is defenetely

Re: Documenting Ignite

Ok, if all our doc writers are in the agreement then let's give a couple of days to our fellow Igniters to share alternate opinions. Artem, if you don't hear back by Monday then feel free to create an INFRA ticket. -- Denis On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg wrote: > I totally agree

Re: Documenting Ignite

I totally agree with Denis's point - "Another benefit of having "Docs Required" flag enabled by default, is that Artem and Prachi can see all such tickets months and weeks before a release, figure out details from source code contributors and complete the docs in advance." On Wed, Jul 18, 2018

Re: Documenting Ignite

Yes, I agree. My concern is related only to process implementation aspect, I wonder if it is technically possible. Generally I like idea of automatic control. ср, 18 июл. 2018 г. в 23:21, Denis Magda : > Hi folks, > > Artem's proposal might simplify and make our doc tickets tracking less >

Re: Documenting Ignite

Hi folks, Artem's proposal might simplify and make our doc tickets tracking less error-prone. The current approach implies that a contributor keeps in mind what needs to go to the docs. If he/she has a good memory, a doc JIRA counterpart will be created once the contribution is accepted. But the

Re: Documenting Ignite

Dmitry, The goal I had in mind by proposing that suggestion was to rectify the fact that JIRA issues for documentation are created on an ad-hoc basis, and often issues are created when the lack of documentation becomes an issue for somebody. So we need to be more proactive. I think manual

Re: Documenting Ignite

Hi Artem, I sometimes receive feedback that Ignite docs has potential for improvement, while I found our docs quite intuitive and simple to understand. So if experienced tech writer will join community it could benefit all of us, and users, of course. So you're very welcome to the community!

Documenting Ignite

Hi Igniters, Being a technical writer, I'm going to contribute to Ignite's documentation, and I believe documentation is an important part of every product, especially such a complex product as Apache Ignite. I'd like to put forward a suggestion on how to increase our chances of making