Denis,
I still feel that redirecting yet another notification source to dev list
without discussion with the Community is not right way to go. Especially when
significant efforts were spent to keep the list clean. I will start a
discussion.
> On 6 Aug 2021, at 22:46, Mauricio Stekl wrote:
>
Hi,
Just ss a heads up, I added the button to the online docs template and
rebuilt the latest version & 3.0.0a docs.
Please let me know if you have any questions or suggestions.
Best,
Mauricio Stekl
On Fri, Aug 6, 2021 at 12:17 PM Denis Magda wrote:
> There is no such a way. Notifications a
There is no such a way. Notifications are always sent to an email address
used by a bugyard account. Anyway, I don’t see any harm in this - usually
you’ll get a 1-2 notifications a week. Plus, many more community members
prepare documentation for features they build these days, thus, it’s good
to r
Is there an easy way to subscribe personally for such notifications? I
forsee complaints that the majority of developers are not interested
in documentation feedback notifications.
2021-08-04 12:40 GMT+03:00, Denis Magda :
> Nikita,
>
> We created a bugyard account for the Ignite community. I'm su
Nikita,
We created a bugyard account for the Ignite community. I'm suggesting using
a shared account bound to 'dev@ignite.apache.org'. That will allow everyone
on the dev list to receive and process documentation feedback.
https://svn.apache.org/repos/private/pmc/ignite/credentials/bugyard.io
Mau
Hello Igniters,
I would like to proceed with implementing the feedback service for the
Ignite documentation website.
If nobody objects, let's start the work.
The details are described here:
https://issues.apache.org/jira/browse/IGNITE-15198
With best regards,
Nikita
ср, 17 мар. 2021 г. в 15:50,
Hi,
I agree with Nikita, it would be a very simple way of getting feedback to
improve the documentation.
This tool in particular is quite easy to integrate into the online docs
template.
Best,
Mauricio
On Tue, Mar 16, 2021 at 4:46 PM Denis Magda wrote:
> Nikita, thanks for starting the conv
Nikita, thanks for starting the conversation. I'll just cast my vote for
the bugyard.io for its ability to select and comment on a specific
problematic point on a documentation page (a paragraph, sentence, picture,
code snippet, etc.). It makes it trivial to share feedback and then it's
easy to pro
Hello Igniters,
I would like to propose an enhancement that can significantly improve the
quality of our documentation.
I suggest adding a feedback button (let’s call it a «Documentation
feedback» button) to the web site documentation pages so everyone could
leave a comment to what is already pub
