hossman@apache - Chris Hostetter

Quick Links

Presentations

Standard Disclaimers

These don't allways apply perfectly in all circumstances, but they work well as starting points.

I tend to keep them generic, so anyone wishing to reuse them is welcome to cut/paste the text (and URL) into their own emails....

# Privately Asked Questions About Open Source Projects

Please don't take this the wrong wrong way, but I have a policy of not 
answering any questions about __PROJECT_NAME__ emailed to me directly.  
I believe that the biggest asset an Open Source project has is it's 
community of users who help each other.  When you ask a question to a 
single community member privately, you not only lose out on potentially 
useful answers from other members of the community, but you also deny 
the rest of the community the benefit of learning from your question 
(and any answers you may receive).

If you post your question to __PROJECT_EMAIL_LIST__ then I'll be happy 
to participate in the discussion.

# XY Problem

Your question appears to be an "XY Problem" ... that is: you are dealing
with "X", you are assuming "Y" will help you, and you are asking about "Y"
without giving more details about the "X" so that we can understand the
full issue.  Perhaps the best solution doesn't involve "Y" at all?
See Also: http://www.perlmonks.org/index.pl?node_id=542341

# Thread Hijacking on Mailing Lists

When starting a new discussion on a mailing list, please do not reply to 
an existing message, instead start a fresh email.  Even if you change the 
subject line of your email, other mail headers still track which thread 
you replied to and your question is "hidden" in that thread and gets less 
attention.   It makes following discussions in the mailing list archives 
particularly difficult.

# Please Use "java-user@lucene" Not "dev@lucene"

Your question is better suited for the java-user@lucene mailing list ...
not the dev@lucene list.  The dev list is for discussing development of
the internals of Solr and the Lucene Java library ... it is *not* the 
appropriate place to ask questions about how to use Solr or the Lucene 
Java library when developing your own applications.  Please resend your 
message to the java-user mailing list, where you are likely to get 
more/better responses since that list also has a larger number of subscribers.

# Please Use "solr-user@lucene" Not "dev@lucene"

Your question is better suited for the solr-user@lucene mailing list ...
not the dev@lucene list.  The dev list is for discussing development of
the internals of Solr and the Lucene Java library ... it is *not* the 
appropriate place to ask questions about how to use Solr or the Lucene 
Java library when developing your own applications.  Please resend your 
message to the solr-user mailing list, where you are likely to get 
more/betterresponses since that list also has a larger number of subscribers.

# Personal Attacks

In accordance with the goals and ideal of the Apache Software Foundation,
It is inappropriate to use an apache.org mailing list for making personal
attacks.  A personal attack is any statement "criticizing the person rather 
than the idea".   While it is acceptable (indeed, encouraged) to criticize
ideas, it is not acceptable to criticize a person suggesting the idea --
doing so diminishes everyone's ability to contribute productively.

This disclaimer is the only reply or acknowledgement I will make to any
communication I receive containing a personal attack -- regardless of 
whatever other comments or ideas in that message may have merit.

http://wiki.apache.org/incubator/CodeOfConduct
http://www.apache.org/dev/project-mailing-lists.html#trolls
http://en.wikipedia.org/wiki/Netiquette

# Consulting Service Requests and/or Job Offers

I'm sorry, I am happily employed by LucidWorks and I'm unable to 
accept other paid work. 

If you are not already aware, there are lists of parties for hire 
who can provide Lucene/Solr support...

http://wiki.apache.org/lucene-java/Support
http://wiki.apache.org/solr/Support

I personally recommend contacting LucidWorks, I know all the guys 
who work in our consulting/support group, and they are great...
http://lucidworks.com/product/training-and-consulting/