sounds good to me :-)

Would you like me to do a pull request or will you copy the README.md yourself?

Thanks

Michael

Am 30.04.21 um 16:59 schrieb Robert Muir:
I'll throw out the idea of moving the README.md to
https://github.com/apache/lucene/tree/main/lucene/luke

That way it is in the main source tree, versioned, and pushed as part
of the release process. We could then fix the gradle documentation
task to incorporate any module's README.md into the main release
documentation file (such as
https://lucene.apache.org/core/8_8_2/index.html). Also for now at
least, it would be visible from github too.

On Fri, Apr 30, 2021 at 10:32 AM Jan Høydahl <[email protected]> wrote:
Hi

That could be feasible. Have a look at the website git repo at 
https://github.com/apache/lucene-site.
Should be fairly easy to move the Markdown files from github to this site, 
which also accepts Markdown...

Jan

30. apr. 2021 kl. 08:41 skrev Michael Wechner <[email protected]>:

Hi

I just noticed that Luke became a Lucene Module

https://github.com/DmitryKey/luke#important-notice
https://mocobeta.medium.com/luke-become-an-apache-lucene-module-as-of-lucene-8-1-7d139c998b2
https://lucene.apache.org/core/8_8_2/luke/index.html

Wouldn't it make sense to move the "Usage documentation of Luke" from 
https://github.com/DmitryKey/luke#luke to somewhere inside lucene.apache.org?

Thanks

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to