Re: Stewardship of Docker-Solr
Essentially, Shalin or you can provide ownership of the github org to the next RM to do the release of the image. On Mon, Nov 11, 2019 at 12:53 PM Ishan Chattopadhyaya wrote: > > I think we should transfer it to Apache's ownership and modify the > release TODO to also release the docker images for the newly released > version. > > On Mon, Nov 11, 2019 at 10:13 AM David Smiley > wrote: > > > > FYI Martijn Koster, the owner of the docker-solr project invited me to help > > maintain docker-solr going forward. His work doesn't involve Solr anymore > > and so he's looking for other who have been involved to take the reigns. I > > accepted. I suspect Shalin might have accepted as well because, like me, > > we are both "Owners" of this GitHub org, along with Martijn. > > > > https://github.com/docker-solr > > > > ~ David Smiley > > Apache Lucene/Solr Search Developer > > http://www.linkedin.com/in/davidwsmiley - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Stewardship of Docker-Solr
I think we should transfer it to Apache's ownership and modify the release TODO to also release the docker images for the newly released version. On Mon, Nov 11, 2019 at 10:13 AM David Smiley wrote: > > FYI Martijn Koster, the owner of the docker-solr project invited me to help > maintain docker-solr going forward. His work doesn't involve Solr anymore > and so he's looking for other who have been involved to take the reigns. I > accepted. I suspect Shalin might have accepted as well because, like me, we > are both "Owners" of this GitHub org, along with Martijn. > > https://github.com/docker-solr > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Printing NULL character in log files.
Hello, Solr Community:
I am using Solr7.4.0 which uses log4j (version 2.11 from Solr's Chanes.txt)
as its component.
Some of the log files that Solr generated contain <0x00> (null characters)
in log files (like below)
Because of this issue, it is difficult for me to trace what
actually happened to the Solr.
Does anyone have the same issue before?
If anyone knows a way to fix this issue or a cause of this issue, could you
please let me know?
Any clue will be very appreciated.
[Example Log 1]
2019-10-20 06:02:03.643 INFO (coreCloseExecutor-140-thread-4) [
x:corename1] o.a.s.m.SolrMetricManager Closing metric reporters for
registry=solr.core.corename,
tag=4c16<0x00><0x00><0x00><0x00>...<0x00><0x00>00ff
2019-10-20 06:02:03.643 INFO (coreCloseExecutor-140-thread-4) [
x:corename1] o.a.s.m.r.SolrJmxReporter Closing reporter
[org.apache.solr.metrics.reporters.SolrJmxReporter@17281659: rootName =
null, domain = solr.core.corename, service url = null, agent id = null] for
registry solr.core.corename1/
com.codahale.metrics.MetricRegistry@6c9f45cc<0x00><0x00><0x00><0x00>..(continue
printing <0x00> untill the end of file.)
[Example Log 2]
2019-10-27 06:02:02.891 INFO (coreCloseExecutor-140-thread-17) [
x:core2] o.a.s.m.r.SolrJmxReporter Closing reporter
[org.apache.solr.metrics.reporters.SolrJmxReporter@35e76d2e: rootName =
null, domain = solr.core.core2, service url = null, agent id = null] for
registry solr.core.core2 / com.codahale.metrics.MetricRegistry@76be90f4
2019-10-27 06:02:02.891 INFO (coreCloseExecutor-140-thread-26) [
x:core3]<0x00><0x00><0x00><0x00><0x00><0x00><0x00><0x00>...<0x00><0x00>
o.a.s.m.SolrMetricManager Closing metric reporters for
registry=solr.core.TUN000, tag=34f04984
2019-10-27 06:02:02.891 INFO (coreCloseExecutor-140-thread-26) [
x:TUN000] o.a.s.m.r.SolrJmxReporter Closing reporter
[org.apache.solr.metrics.reporters.SolrJmxReporter@378cecb: rootName =
null, domain = solr.core.TUN000, service url = null, agent id = null] for
registry solr.core.TUN000 / com.codahale.metrics.MetricRegistry@9c3410c
2019-10-27 06:02:05.063 INFO (Thread-1) [ ] o.e.j.s.h.ContextHandler
Stopped o.e.j.w.WebAppContext@5fbe4146
{/solr,null,UNAVAILABLE}{file:///E:/apatchSolr/RCSS-basic-4.0.1/LUSOLR/solr/server//solr-webapp/webapp}
<0x00><0x00><0x00><0x00><0x00><0x00>...(printing <0x00> until the end of
the file)..<0x00><0x00>
Sincerely,
Kaya Ota
Stewardship of Docker-Solr
FYI Martijn Koster, the owner of the docker-solr project invited me to help maintain docker-solr going forward. His work doesn't involve Solr anymore and so he's looking for other who have been involved to take the reigns. I accepted. I suspect Shalin might have accepted as well because, like me, we are both "Owners" of this GitHub org, along with Martijn. https://github.com/docker-solr ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
Re: And we have amazing user doc!!
I love Cassandra and she does amazing work :) yes and and I know others are key to doc too. On Sun, Nov 10, 2019 at 7:29 PM Mark Miller wrote: > Don’t you dare ever question that. Don’t be sad you missed the twitter > fun. > -- > - Mark > > http://about.me/markrmiller > -- - Mark http://about.me/markrmiller
And we have amazing user doc!!
Don’t you dare ever question that. Don’t be sad you missed the twitter fun. -- - Mark http://about.me/markrmiller
Re: Solr/SolrCloud
Finally. You will not lose my knowledge. I am and will share as much as I can with my teammates. And if you want to talk to me about Solr and Lucene I will talk your ear off. I’m not against anyone here. Mark On Sun, Nov 10, 2019 at 6:04 PM Mark Miller wrote: > And I don't know you were on Twitter :) Bravo, because I should be able to > guess. Like that actually is going haunt me a little and it shouldn't. It > should be easy. And like I have a guess and then doesn't seem to quite > fit...I mean I didn't read everything towards the end, but good job. It's > like 3 of you where doing that. > > - Mark > > On Sun, Nov 10, 2019 at 5:35 PM Mark Miller wrote: > >> And don't worry, there are a lot of people in my wake that don't want to >> fight with me, I'm not fun to fight with, I don't want fight with you >> either. I'm disappointed in myself and in what I've accomplished in a >> decade - pretty much 0 of that is on anyone here but me. I did not intend >> to take it out on anyone here. >> >> - Mark >> >> On Sun, Nov 10, 2019 at 5:16 PM Mark Miller >> wrote: >> >>> New people to Solr and maybe some old ones :) >>> >>> This is an old project. There is a lot of stuff in the history. This >>> whole thing is more about me than anyone else. This software is >>> salvageable, I've seen it. I've seen the stuff in the software to know you >>> can do it - a lot of what you need is there, just not thoroughly done, or >>> its a little off, or whatever. You know, its people trying and having good >>> ideas, but a lot of them not taking root. >>> >>> So don't be scared, this community is good, for some reason there is >>> weird Solr road block, but I'm pretty confident you will get through it >>> now. And you won't have all my code, you don't need all my code, and the >>> code I have, I'm sure you will end up with. I'm entrusting it to good hands. >>> >>> - mark >>> >>> On Sat, Nov 9, 2019 at 7:30 PM Mark Miller >>> wrote: >>> Dear Lucene/Solr Community, I have been searching for an answer for Solr and SolrCloud for a long time. I feel like I landed in a tornado and I don’t know where the time went. I forget even why I’m here. Because I didn’t come here to work for silicon valley companies, or make a lot of money, or impress people I don’t know. I came here for Lucene. I love Lucene. I love developing. I love Lucene tests. I don’t do much Lucene anymore. I was needed more in Solr, and someone started acting like a dictator. I still love Lucene. I’ve tried to love to Solr. But I don’t. And so I’ve been searching for an answer, when not being depressed about it, and as often happens, it was right in front of me. So yeah, a couple times when I got sick of you guys - which is no one and everyone - I went off on my own and started chasing one of my own itches, which leads to things, which leads to things, which leads things. I love that I have no idea at the start. Anyway, after time and some learning I kind of got to the point where I knew enough about the stupid technologies and the whole system - it’s like a lot of code, a lot of debt, blah blah. But I’m banging my head against this - intuition guy - like, just bang bang bang, starts to make sense and I don’t even do any work. So starts to makes sense. I start to address this. And that. I make some progress. I find some things. I say screw working on making this work anymore, it’s impossible, I’m sick of it, I’m finally gonna do the thing I love. Make it fast. So I start making it fast here and there, sometimes. Most efforts are in like 3-4-5 different huge sprints or something - but always efforts around that. You know the lost work story. Lot of lost work. I usually don’t duplicate all the work when I make another attempt. I have enough memories that that is not the important part. The importance is that I learned that none of you you know anything about this system or the components that make it up. I didn’t either. I knew more than a lot of you, but not early enough. And you guys have worked on the very edges on some great necessary stuff and tools - and I take heavy goddamn advantage of those things. Thank you. And I add things. And I track things. And I turn on enforcers. And pluck away. And I strip out all our darn randomization or craziness test hierarchy (or start to try and control it), and I start adding logging that's useful, and debug logging, and I use a good profiler, and I start limiting resources and minimizing shit, until I have a system that I can start to understand and work through. And I spend almost just as much on making myself efficient, cause it’s big. But. All basic stuff. Maybe I’m smart somewhere, maybe I’m not. I’m lazy. I don’t think. I’m a math minor and most can probably attest I will not do a 1
Re: Tracking down inconsistent failure in jenkins
Hi Erick, * On 2019/11/09 15:15:03, Erick Erickson wrote: > How are you running the tests? Just “ant test”? If so the output is all > written to stdout so I usually just redirect it somewhere , e.g. “ant test > > results 2>&1”…. Yea, I run it with ant test. So the output is the log from the cmd, ok. Is there an other possibility to run the tests? > > That file should have the failures _and_ a “reproduce with” line for each > failing test. One thing I didn’t mention is that there’s also a significant > bit of randomization in the test harness. Different locales are chosen at > random, different directory implementations, different timezones, etc… We had > one issue that was a JVM issue that only showed up in the Turkish locale for > instance that we’d never have found without the randomization. The “reproduce > with” line has all that information echoed and will run the test again with > all the same bits of randomization. Ok, this sounds interesting > > It’s relatively rare for the test to fail reliably even if you use the > “reproduce with” line because it’s, well, reproducible. When it is, you’ll > see a JIRA raised something like “reproducible test failure” and/or someone > will jump on it and fix it. So just reproducible issues go into jira? In my experience, it makes sense in some case, to write an issue für a ireproducible bug. So you can collect all data on one place. Sometimes this helps to track the bugs down. > > Timing issues: Well, just that. Say a test creates a collection and _assumes_ > (no, this isn’t a good practice) that it’ll finish in 5 seconds and it takes > 6, then drives on. Oops. Other more subtle issues are just threading issues > where some sequence of context switching happens to hit an unanticipated > problem. etc. > > It’s not that we _never_ get reproducible tests, it’s that when we do someone > fixes them. There are a _lot_ of tests in the full suite, so if > timing-related tests fail 0.1% of the time… > > You can confirm this yourself pretty easily, just save the output and run the > “reproduce with” line. > Ok, I will go now into the source, and see, what some test does and trying to get a test without errors. Last time I have had 1 error. If it continues like this, I will have 0 next time ;-) Regards, Raphael > Best, > Erick > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Solr/SolrCloud
And I don't know you were on Twitter :) Bravo, because I should be able to guess. Like that actually is going haunt me a little and it shouldn't. It should be easy. And like I have a guess and then doesn't seem to quite fit...I mean I didn't read everything towards the end, but good job. It's like 3 of you where doing that. - Mark On Sun, Nov 10, 2019 at 5:35 PM Mark Miller wrote: > And don't worry, there are a lot of people in my wake that don't want to > fight with me, I'm not fun to fight with, I don't want fight with you > either. I'm disappointed in myself and in what I've accomplished in a > decade - pretty much 0 of that is on anyone here but me. I did not intend > to take it out on anyone here. > > - Mark > > On Sun, Nov 10, 2019 at 5:16 PM Mark Miller wrote: > >> New people to Solr and maybe some old ones :) >> >> This is an old project. There is a lot of stuff in the history. This >> whole thing is more about me than anyone else. This software is >> salvageable, I've seen it. I've seen the stuff in the software to know you >> can do it - a lot of what you need is there, just not thoroughly done, or >> its a little off, or whatever. You know, its people trying and having good >> ideas, but a lot of them not taking root. >> >> So don't be scared, this community is good, for some reason there is >> weird Solr road block, but I'm pretty confident you will get through it >> now. And you won't have all my code, you don't need all my code, and the >> code I have, I'm sure you will end up with. I'm entrusting it to good hands. >> >> - mark >> >> On Sat, Nov 9, 2019 at 7:30 PM Mark Miller wrote: >> >>> Dear Lucene/Solr Community, >>> >>> I have been searching for an answer for Solr and SolrCloud for a long >>> time. I feel like I landed in a tornado and I don’t know where the time >>> went. I forget even why I’m here. Because I didn’t come here to work for >>> silicon valley companies, or make a lot of money, or impress people I don’t >>> know. I came here for Lucene. I love Lucene. I love developing. I love >>> Lucene tests. I don’t do much Lucene anymore. I was needed more in Solr, >>> and someone started acting like a dictator. >>> >>> I still love Lucene. I’ve tried to love to Solr. But I don’t. And so >>> I’ve been searching for an answer, when not being depressed about it, and >>> as often happens, it was right in front of me. >>> >>> So yeah, a couple times when I got sick of you guys - which is no one >>> and everyone - I went off on my own and started chasing one of my own >>> itches, which leads to things, which leads to things, which leads things. I >>> love that I have no idea at the start. >>> >>> Anyway, after time and some learning I kind of got to the point where I >>> knew enough about the stupid technologies and the whole system - it’s like >>> a lot of code, a lot of debt, blah blah. But I’m banging my head against >>> this - intuition guy - like, just bang bang bang, starts to make sense and >>> I don’t even do any work. So starts to makes sense. I start to address >>> this. And that. I make some progress. I find some things. I say screw >>> working on making this work anymore, it’s impossible, I’m sick of it, I’m >>> finally gonna do the thing I love. Make it fast. >>> >>> So I start making it fast here and there, sometimes. Most efforts are in >>> like 3-4-5 different huge sprints or something - but always efforts around >>> that. You know the lost work story. Lot of lost work. >>> >>> I usually don’t duplicate all the work when I make another attempt. I >>> have enough memories that that is not the important part. The importance is >>> that I learned that none of you you know anything about this system or the >>> components that make it up. I didn’t either. I knew more than a lot of you, >>> but not early enough. And you guys have worked on the very edges on some >>> great necessary stuff and tools - and I take heavy goddamn advantage of >>> those things. Thank you. And I add things. And I track things. And I turn >>> on enforcers. And pluck away. And I strip out all our darn randomization or >>> craziness test hierarchy (or start to try and control it), and I start >>> adding logging that's useful, and debug logging, and I use a good profiler, >>> and I start limiting resources and minimizing shit, until I have a system >>> that I can start to understand and work through. And I spend almost just as >>> much on making myself efficient, cause it’s big. >>> >>> But. All basic stuff. Maybe I’m smart somewhere, maybe I’m not. I’m >>> lazy. I don’t think. I’m a math minor and most can probably attest I will >>> not do a 1 dollar tip in my head. So I’m just learning about the system, >>> the components, plucking away, cleaning up, finding bugs, adding stuff that >>> will allow me to understand. Starting with basic tests, and like shooting >>> for high goals. I want to be able to start 500 solrcores in 10-15 seconds >>> in a single corecontainer. Thats what I want. So sometimes I
Re: Solr/SolrCloud
And don't worry, there are a lot of people in my wake that don't want to fight with me, I'm not fun to fight with, I don't want fight with you either. I'm disappointed in myself and in what I've accomplished in a decade - pretty much 0 of that is on anyone here but me. I did not intend to take it out on anyone here. - Mark On Sun, Nov 10, 2019 at 5:16 PM Mark Miller wrote: > New people to Solr and maybe some old ones :) > > This is an old project. There is a lot of stuff in the history. This whole > thing is more about me than anyone else. This software is salvageable, I've > seen it. I've seen the stuff in the software to know you can do it - a lot > of what you need is there, just not thoroughly done, or its a little off, > or whatever. You know, its people trying and having good ideas, but a lot > of them not taking root. > > So don't be scared, this community is good, for some reason there is weird > Solr road block, but I'm pretty confident you will get through it now. And > you won't have all my code, you don't need all my code, and the code I > have, I'm sure you will end up with. I'm entrusting it to good hands. > > - mark > > On Sat, Nov 9, 2019 at 7:30 PM Mark Miller wrote: > >> Dear Lucene/Solr Community, >> >> I have been searching for an answer for Solr and SolrCloud for a long >> time. I feel like I landed in a tornado and I don’t know where the time >> went. I forget even why I’m here. Because I didn’t come here to work for >> silicon valley companies, or make a lot of money, or impress people I don’t >> know. I came here for Lucene. I love Lucene. I love developing. I love >> Lucene tests. I don’t do much Lucene anymore. I was needed more in Solr, >> and someone started acting like a dictator. >> >> I still love Lucene. I’ve tried to love to Solr. But I don’t. And so I’ve >> been searching for an answer, when not being depressed about it, and as >> often happens, it was right in front of me. >> >> So yeah, a couple times when I got sick of you guys - which is no one and >> everyone - I went off on my own and started chasing one of my own itches, >> which leads to things, which leads to things, which leads things. I love >> that I have no idea at the start. >> >> Anyway, after time and some learning I kind of got to the point where I >> knew enough about the stupid technologies and the whole system - it’s like >> a lot of code, a lot of debt, blah blah. But I’m banging my head against >> this - intuition guy - like, just bang bang bang, starts to make sense and >> I don’t even do any work. So starts to makes sense. I start to address >> this. And that. I make some progress. I find some things. I say screw >> working on making this work anymore, it’s impossible, I’m sick of it, I’m >> finally gonna do the thing I love. Make it fast. >> >> So I start making it fast here and there, sometimes. Most efforts are in >> like 3-4-5 different huge sprints or something - but always efforts around >> that. You know the lost work story. Lot of lost work. >> >> I usually don’t duplicate all the work when I make another attempt. I >> have enough memories that that is not the important part. The importance is >> that I learned that none of you you know anything about this system or the >> components that make it up. I didn’t either. I knew more than a lot of you, >> but not early enough. And you guys have worked on the very edges on some >> great necessary stuff and tools - and I take heavy goddamn advantage of >> those things. Thank you. And I add things. And I track things. And I turn >> on enforcers. And pluck away. And I strip out all our darn randomization or >> craziness test hierarchy (or start to try and control it), and I start >> adding logging that's useful, and debug logging, and I use a good profiler, >> and I start limiting resources and minimizing shit, until I have a system >> that I can start to understand and work through. And I spend almost just as >> much on making myself efficient, cause it’s big. >> >> But. All basic stuff. Maybe I’m smart somewhere, maybe I’m not. I’m lazy. >> I don’t think. I’m a math minor and most can probably attest I will not do >> a 1 dollar tip in my head. So I’m just learning about the system, the >> components, plucking away, cleaning up, finding bugs, adding stuff that >> will allow me to understand. Starting with basic tests, and like shooting >> for high goals. I want to be able to start 500 solrcores in 10-15 seconds >> in a single corecontainer. Thats what I want. So sometimes I work towards. >> Brings out a lot of great stuff. But the solution is neither fancy or some >> huge credit to me. We dont know anything, we have no good enforcement >> really, and we make it too crazy and wild when it's already crazy and wild >> and the it’s all way more than any human can realistically do anything >> with. Now I wrote a lot of this foundation. It’s not easy for people to >> take me seriously when I say its cause we are shit software developers. >> “Haha,
Re: Solr/SolrCloud
New people to Solr and maybe some old ones :) This is an old project. There is a lot of stuff in the history. This whole thing is more about me than anyone else. This software is salvageable, I've seen it. I've seen the stuff in the software to know you can do it - a lot of what you need is there, just not thoroughly done, or its a little off, or whatever. You know, its people trying and having good ideas, but a lot of them not taking root. So don't be scared, this community is good, for some reason there is weird Solr road block, but I'm pretty confident you will get through it now. And you won't have all my code, you don't need all my code, and the code I have, I'm sure you will end up with. I'm entrusting it to good hands. - mark On Sat, Nov 9, 2019 at 7:30 PM Mark Miller wrote: > Dear Lucene/Solr Community, > > I have been searching for an answer for Solr and SolrCloud for a long > time. I feel like I landed in a tornado and I don’t know where the time > went. I forget even why I’m here. Because I didn’t come here to work for > silicon valley companies, or make a lot of money, or impress people I don’t > know. I came here for Lucene. I love Lucene. I love developing. I love > Lucene tests. I don’t do much Lucene anymore. I was needed more in Solr, > and someone started acting like a dictator. > > I still love Lucene. I’ve tried to love to Solr. But I don’t. And so I’ve > been searching for an answer, when not being depressed about it, and as > often happens, it was right in front of me. > > So yeah, a couple times when I got sick of you guys - which is no one and > everyone - I went off on my own and started chasing one of my own itches, > which leads to things, which leads to things, which leads things. I love > that I have no idea at the start. > > Anyway, after time and some learning I kind of got to the point where I > knew enough about the stupid technologies and the whole system - it’s like > a lot of code, a lot of debt, blah blah. But I’m banging my head against > this - intuition guy - like, just bang bang bang, starts to make sense and > I don’t even do any work. So starts to makes sense. I start to address > this. And that. I make some progress. I find some things. I say screw > working on making this work anymore, it’s impossible, I’m sick of it, I’m > finally gonna do the thing I love. Make it fast. > > So I start making it fast here and there, sometimes. Most efforts are in > like 3-4-5 different huge sprints or something - but always efforts around > that. You know the lost work story. Lot of lost work. > > I usually don’t duplicate all the work when I make another attempt. I have > enough memories that that is not the important part. The importance is that > I learned that none of you you know anything about this system or the > components that make it up. I didn’t either. I knew more than a lot of you, > but not early enough. And you guys have worked on the very edges on some > great necessary stuff and tools - and I take heavy goddamn advantage of > those things. Thank you. And I add things. And I track things. And I turn > on enforcers. And pluck away. And I strip out all our darn randomization or > craziness test hierarchy (or start to try and control it), and I start > adding logging that's useful, and debug logging, and I use a good profiler, > and I start limiting resources and minimizing shit, until I have a system > that I can start to understand and work through. And I spend almost just as > much on making myself efficient, cause it’s big. > > But. All basic stuff. Maybe I’m smart somewhere, maybe I’m not. I’m lazy. > I don’t think. I’m a math minor and most can probably attest I will not do > a 1 dollar tip in my head. So I’m just learning about the system, the > components, plucking away, cleaning up, finding bugs, adding stuff that > will allow me to understand. Starting with basic tests, and like shooting > for high goals. I want to be able to start 500 solrcores in 10-15 seconds > in a single corecontainer. Thats what I want. So sometimes I work towards. > Brings out a lot of great stuff. But the solution is neither fancy or some > huge credit to me. We dont know anything, we have no good enforcement > really, and we make it too crazy and wild when it's already crazy and wild > and the it’s all way more than any human can realistically do anything > with. Now I wrote a lot of this foundation. It’s not easy for people to > take me seriously when I say its cause we are shit software developers. > “Haha, you say cocreator, your software, please tell me how I am the one > that sucks”. Even I had no confidence this could work so well compared to > what was happening. I had to basically get there. Get there again cause > then I didn't care, and then get close again. Like, I don’t trust myself or > brain. So I didn’t need everything - god my knowledge and code is so spread > around - but it’s not important. The design not important. I’d like you to > have whatever design
Re: Change solr/lucene Readme file format
Hi, When building the documentation (ant documentation), all readme files included in the documentation are parsed as markdown (see flexmark task in ant) and converted to html. This works well, although not everything is markdown. If you have a plain readme file it would still parse as valid markdown and HTML output looks fine, so Erik's problem with markdown isn't one. Uwe Am November 10, 2019 4:00:21 PM UTC schrieb Marcus Eagan : >Most README files in contemporary open source projects are Markdown >because >of the formatting features. I personally favor convention over ease of >use >in this case. > >Marcus Eagan > >On Sun, Nov 10, 2019, 8:58 AM Erick Erickson >wrote: > >> Personally I’d make them text files. The last thing I want to do is >make >> reading/updating these have a barrier to entry. We should save >formatting >> for the ref guide and/or Wiki. >> >> Best, >> Erick >> >> > On Nov 10, 2019, at 1:01 AM, Man with No Name > >> wrote: >> > >> > Hey folks, >> > I have been looking into the solr/lucene source code, and the first >> thing caught my eye was the different Readme files. All the files had >> different file and text format. What do you guys think about making >all the >> readmes to markdown file rather than text files, and a standard >template? >> > >> > >> > -- >> > Regards: >> > Pinkesh Sharma >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >> -- Uwe Schindler Achterdiek 19, 28357 Bremen https://www.thetaphi.de
Re: Change solr/lucene Readme file format
Most README files in contemporary open source projects are Markdown because of the formatting features. I personally favor convention over ease of use in this case. Marcus Eagan On Sun, Nov 10, 2019, 8:58 AM Erick Erickson wrote: > Personally I’d make them text files. The last thing I want to do is make > reading/updating these have a barrier to entry. We should save formatting > for the ref guide and/or Wiki. > > Best, > Erick > > > On Nov 10, 2019, at 1:01 AM, Man with No Name > wrote: > > > > Hey folks, > > I have been looking into the solr/lucene source code, and the first > thing caught my eye was the different Readme files. All the files had > different file and text format. What do you guys think about making all the > readmes to markdown file rather than text files, and a standard template? > > > > > > -- > > Regards: > > Pinkesh Sharma > > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: Change solr/lucene Readme file format
Personally I’d make them text files. The last thing I want to do is make reading/updating these have a barrier to entry. We should save formatting for the ref guide and/or Wiki. Best, Erick > On Nov 10, 2019, at 1:01 AM, Man with No Name > wrote: > > Hey folks, > I have been looking into the solr/lucene source code, and the first thing > caught my eye was the different Readme files. All the files had different > file and text format. What do you guys think about making all the readmes to > markdown file rather than text files, and a standard template? > > > -- > Regards: > Pinkesh Sharma - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
