Skip to content

Instantly share code, notes, and snippets.

**Bring your own framework**
We want a site that allows contributors to speak from within their framework. Overall,
this broadens the appeal of the site, and it preserves the richness of expression when
answers are given in the natural context of the one giving the answer, even if this
means expressing one's framework or opinions as unqualified facts.
Our aim is to be 'expert' in the context of the internet. This will not be the best
home for those who do not think deeply about the texts or those who cannot communicate
clearly and effectively. But it is not our aim to be home only to academics or full-time
**Avoid truth assertions**
We want a site that welcomes people of all perspectives, as our site description says.
This broadens the appeal of the site (though of course we don't want a free-for-all).
This site focuses on the *text* and the
process of interpreting it, using the tools of (at least) grammar, linguistics, history,
archaeology, science, and comparison with other texts. None of that is inherently
religious, and that non-dependence on a religious foundation is what
*distinguishes* BH from other sites in the SE network.
There have been a lot of discussions on meta about different aspects of site direction, but none directly focused on the fundamental question: What kind of site do we want to have? What should our culture be? In particular, what style of answers are we looking for?
This question is fundamentally about **where do we want to be in the end**, and not about *how we get there*.
**We all agree that contributions must 'show their work'. Exactly where and how we draw the line is an implementation detail and outside the scope of this question.**
We've provided answers that capture the main positions we know about. Please feel free to add your own if you have another outcome in mind.
Please up-vote answers you find acceptable, down-vote ones you don't, and abstain if you don't feel strongly either way. Please also up-vote the question no matter which of these you do, so we can gauge participation.
@jackdouglas
jackdouglas / next-steps-a
Last active December 27, 2015 09:59 — forked from cellio/next-steps-a
Jack and Monica jointly propose the following path forward:
The results of this question have been somewhat inconclusive so far. The most-voted
answers have the following vote breakdowns (as of this writing):
- Avoid truth assertions (use qualified language): +12 / -7 (5)
- Bring your own framework: +10 / -6 (4)
- Good answers respect their questions: +8 / -4 (4)
- Specify your framework: +6 / -5 (1)
@jackdouglas
jackdouglas / next-steps-a
Last active December 27, 2015 16:39 — forked from cellio/next-steps-a
BH already has a "show your work" guideline and this still applies. In essence we<sup><sup>1</sup></sup>
propose to firm up this guideline and begin to enforce it more vigorously. The other answers here
illustrated a division in the community and we hope to be able to move forward together by focussing on
what we agree on.
Writing descriptively -- "such-and-such source says X",
as opposed to "X is true" -- dovetails nicely with "show your work". If you do this you're most of the
way to showing your work. We are not in general requiring this approach, but it's a helpful approach
and answers that use it are likely to fare well. Specifying a framework explicitly in an answer can
help readers understand the internal logic, particularly for frameworks that