Hi team! Fotios Petropoulos has contacted us again...
# support
y
Hi team! Fotios Petropoulos has contacted us again regarding the copyright issue in our documentation. Should we reply him directly?
Hello Max and Marianna Despite our previous communications, Nixtla’s documentation still has serious issues (to the degree of copyright infringement). I have to say that I am not very happy that these issues have not yet been resolved despite our previous communications. Below are issues that I found by spending 15 minutes on your documentation - I am worried that many more similar problems exist, including the use of material without permission, and incorrect or missing citations. Given the seriousness of these issues (and the fact that this is the second time I contacted you regarding this), I am sorry to say that I find your approach to correcting these very sloppy. 1) This page contains a very large portion (1300 words) directly taken without any permission from my copyrighted paper (see sections “Optimized Theta Model (OTM)” and “More on Optimised Theta models” in your webpage). Additionally, as the webpage presents methods and models based on my paper, that paper needs to be cited at the beginning of the page (such as “Fiorucci et al. (2016) proposed that...” as well as appear in the list of references of that webpage. Additionally, the references cited at the beginning of the page are completely irrelevant and wrong. The theta method was not proposed by Box and Jenkins (1976)!!! https://nixtlaverse.nixtla.io/statsforecast/docs/models/optimizedtheta.html 2) This page contains a very large portion (1200 words) directly taken without any permission from my copyrighted paper. https://nixtlaverse.nixtla.io/statsforecast/docs/models/standardtheta.html 3) This webpage presents methods and models based on my paper, that paper needs to be cited at the beginning of the page (such as “Fiorucci et al. (2016) proposed that...“. While this paper is cited at the end of the webpage, it needs to be very clear from the beginning where these methods are coming from. https://nixtlaverse.nixtla.io/statsforecast/docs/models/dynamicstandardtheta.html 4) The exact above applies also to this webpage. https://nixtlaverse.nixtla.io/statsforecast/docs/models/dynamicoptimizedtheta.html 5) This page is missing references to my work where iMAPA originates. These should appear both at the beginning of the page as well as at the list of references. https://nixtlaverse.nixtla.io/statsforecast/docs/models/imapa.html I do hope that these and all other issues are resolved very soon. I am extremely disappointed to see that my work is not only properly recognised and cited but also virtually plagiarised. If these issues are not resolved as soon as possible, you will force me to consider taking legal action. Best wishes, Fotios Petropoulos
m
Oh, no!
🤦‍♀️ 1
But we did check that! Is he looking at an older version?
m
No, it's current version, I see the same
m
because I did a PR back in April: https://github.com/Nixtla/statsforecast/pull/1005
m
Hmm, then maybe there was an issue with Mintlify
In the meantime, we could send him the closed PR to tell him that the issue is resolved, but a problem occured with the rendering of the docs, and that we'll solve this shortly
m
yes, I think that's a good plan. Since the message mentions me directly, I'll answer Fotios.
was this message sent to us via LinkedIn @Yibei?
y
Nope the message is sent through intercom. I can do the reply, no worries.
I just want to confirm, since he mentioned “Optimized Theta Model (OTM)” and “More on Optimised Theta models”, we have changed these sessions already right?
m
Yes, in the PR, everything is changed, but the changes are not reflected online
thank you 1
I launched the
build-docs
action, again, let's see if that fixes it
m
thanks Marco, that's correct
thank you 1
👀 1
(The PR changes all the theta tutorials)
m
Well, running
build-docs
didn't help...
🫠 2
h
it must pin the version, otherwise it should change, right?
m
I don't see where it can pin the version...
h
then where is the old content from
@Mariana Menchero you should send him a direct email as well, stating the problem and cc max
m
Of course, I'll do that right now. I can also see some of Fotio's comments are already addressed in the GitHub version of the docs.
m
I feel it's an issue with Mintlify, and not our CI. Something similar happened with TimeGPT docs (PR was merged, but the docs did not update, even after many days) and Edu fixed it. I just don't know what he did to fix it 🫠
m
For example, comment #3 in GitHub does show the proper attribution: https://github.com/Nixtla/statsforecast/blob/main/nbs/docs/models/DynamicOptimizedTheta.ipynb
for sure @Marco see my comment above
h
First acknowledge the problem is on our side, second, tell him it is one of the platforms we use causing the issue, show him the closed pr and the places where the content has been fixed long time ago
m
for sure @Han Wang
to prevent duplicate responses, have you answered him on Intercom @Yibei?
y
Yes! I included what we mentioned, the PR and the issue with rendering
m
that's fine
h
I think a bit duplication is fine, that emphasizes we are serious about it
m
yes
y
This is my reply. I can delete the message if it’s more convenient: Dear Fotios, Thank you for reaching to us. We deeply regret that the documentation on our website continues to reflect issues you’ve previously flagged. We want to personally acknowledge the seriousness of your message and offer our sincere apologies for the distress this has caused. To clarify, we did make the necessary changes back in April through PR #1005, which included removing copied text and adding appropriate citations outlined in your email. Unfortunately, due to a documentation rendering issue with our documentation platform (Mintlify), these updates were not published correctly. This was unintentional, and we understand your frustration. We’ve just re-triggered the documentation build to ensure the corrected versions go live. Once this is done, we’ll confirm with you and share the updated pages. We’re also auditing the rest of the content to prevent any similar issues elsewhere. We deeply respect your work and are committed to resolving this promptly and ensuring it doesn’t happen again. Best regards, Nixtla Team
👍 1
m
I think that's a very good message @Yibei I'm writing something similar and addressing his comments one by one with the corresponding links.
thank you 1