Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3771008163

   I think it should be put in website? We have like md files teaching you how 
to develop already


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3771007387

   On the website I see Getting Started, API reference and all pages are empty. 
I'm gonna write content for those
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3771005349

   Juust tell me where this has to be updated, like on the website or on GitHub 
page


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3771003580

   Yeah I think that'd be better
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3771000319

   Or we can just review the PR and tell you which part is wrong when you 
upload it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770993217

   https://github.com/apache/mahout/issues/799


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770991602

   issue number?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770989533

   Oh right that one is a bit old, we have also implemented some features in 
which we wrote that it will be in post PoC. See the QDP Roadmap issue may be 
more precise.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770978312

   Sure sure. I'm using the Apache Mahout Roadmap document that you shared i 
think a month ago


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770974753

   Feel free to ask questions if you don't know why something is designed this 
way or why we implemented some feature.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770970144

   QDP


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770969408

   QDP or qumat?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770967686

   > > [@ryankert01](https://github.com/ryankert01) I'm working on the 
documentation. Will update you on the slack channel soon.
   > 
   > Which part are you working on btw, just want to ask in case we are doing 
the same part.
   
   I'm working on starting like introduction, architecture and structure part


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770942695

   > @ryankert01 I'm working on the documentation. Will update you on the slack 
channel soon.
   
   Which part are you working on btw, just want to ask in case we are doing the 
same part.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-19 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3770923487

   @ryankert01 I'm working on the documentation. Will update you on the slack 
channel soon.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-15 Thread via GitHub


guan404ming commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3756167234

   Sorry about removing the content directly. I understand the concern and I’ve 
already proposed some remediation steps to address the impact, including adding 
proper redirects and a custom 404 page so existing links don’t break. I’ve 
opened #835 to fix this and make sure we handle the legacy documentation more 
gracefully.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-15 Thread via GitHub


rawkintrevo commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3754453109

   There's a lot happening here, and i've been out the last couple of days.
   
   We use jekyll because it lowers the friction to developers writing and 
maintaining talks (via markdown), which we value higher than latest wiz-bang 
front end. If you can build the content from the markdown files (like jekyll 
does) then awesome, go for it. But that is why we're using jekyll. 
   
   Removing the outdated documentation- the project has existed for over 15 
years, there are links all over the internet to admittedly outdated docs- the 
better solution is to first set up redirects and/or deprication bannes (i 
believe this was done a while ago). If y'all already nuked the docs (it looks 
like you have) please set up redirects / better 404 ASAP.
   
   I'm back in pocket now, dm me direct on slack for more info. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-12 Thread via GitHub


400Ping commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3741830640

   > @ryankert01 As we discussed, I'm up for writing documentation for QDP, 
with that being a frontend guy, I'd also love to style the website. Shall we 
discuss and start implementing this in this week's meet? Till that I'm gonna 
explore things about QDP so that I can help in its documentation
   
   I can also help with some of it as well.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-12 Thread via GitHub


krishna-dave206 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3741777308

   @ryankert01 As we discussed, I'm up for writing documentation for QDP, with 
that being a frontend guy, I'd also love to style the website. Shall we discuss 
and start implementing this in this week's meet?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-12 Thread via GitHub


guan404ming commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3741510829

   I think this makes sense overall 👍
   A more modern framework could definitely help with CSR and the styling 
issues we’re seeing. That said, I agree we should do a bit more investigation 
first (e.g. evaluate a few candidates, migration cost, risks).
   
   Maybe a good approach is:
   
   - Short term: continue filling out and stabilizing the content.
   - In parallel: research and compare modern doc frameworks (features, 
theming, migration path).
   - Then decide on timing and scope for a migration.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Feature] Document improvement [mahout]

2026-01-12 Thread via GitHub


ryankert01 commented on issue #811:
URL: https://github.com/apache/mahout/issues/811#issuecomment-3739890308

   I noticed the documentation framework we’re using is pretty old and doesn’t 
support modern features like client-side rendering. It might be a good time to 
explore a more modern framework, which could also help with some of the styling 
issues we’re seeing.
   WDYT? @guan404ming @krishna-dave206 @rawkintrevo 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]