It would also re nice to have a "user problem report" web page that had a few fields like Solr release, query, error message or stack trace, query response, expected response, etc. And maybe a few bullet points like "Add debugQuery to get detailed response for troubleshooting", "Be sure to restart Solr after changing schema or config", and "Be sure to reindex data after changing schema", etc. IOW, make it super easy to send a user problem report, increase the likelihood that it will have relevant information, and increase the likelihood that the user can resolve the problem themselves.
-- Jack Krupansky On Mon, Mar 16, 2015 at 8:05 PM, Erick Erickson <[email protected]> wrote: > +1 to that, I never made the connection between usage problems in > JIRAs and the location of the two on the resources page... > > Not quite sure how to make the changes though.. > > Erick > > On Mon, Mar 16, 2015 at 3:49 PM, Shawn Heisey <[email protected]> wrote: > > I have some changes I'd like to make to the Solr website, but I'm not > > entirely sure what kind of review process that should go through. > > Should I open an issue in Jira, or just discuss it here? > > > > Here are the changes I'd like to do: > > > > http://apaste.info/pc5 > > > > I think part of the reason that we are having so many people start a > > request for support by opening an issue in Jira is that the info about > > the issue tracker is listed *before* the mailing lists on the resources > > page. My patch moves that whole section so it's after the mailing list > > info. This may not entirely solve the problem, but I think it will help. > > > > There are also some changes on the solr-user mailing list info and the > > IRC channel info. > > > > Thanks, > > Shawn > > > > > > --------------------------------------------------------------------- > > 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] > >
