devblog/day 285 tuning git-annex unused refsgit-annexhttp://git-annex.branchable.com/devblog/day_285__tuning_git-annex_unused_refs/git-annexikiwiki2015-05-16T21:46:20Zmailing lists and support siteshttp://git-annex.branchable.com/devblog/day_285__tuning_git-annex_unused_refs/comment_1_a3f0dd4fc8457af7c72040fbe8fd5fee/anarcat2015-05-14T20:26:59Z2015-05-14T20:26:59Z
<p>after years subscribing to zillions of them, i have acquired an allergy to mailing lists. it seems that i get this every once in a while: i'm subscribed to a bunch of them and i stop reading and just hit "d" on my mail client. <img src="http://git-annex.branchable.com/smileys/smile.png" alt=":)" /></p>
<p>i think there are very interesting alternatives, online web forums (yes yes, i know, bear with me) where knowledge is established and shared instead of just having a threaded conversation. i'm thinking of http://ask.debian.net/ or the stackexchange sites. as i <a href="http://git-annex.branchable.com/devblog/day_268_stressed_out/#comment-e0814585df0047e6d4e11515aebe1dec">analysed before</a>, the forum is the biggest part of this website (and consequently the git-annex source code!), bug tracker coming in second, and the two together forming the majority of disk usage of the git repository. there are alternative discussion tools like discourse.org that may also be interesting for people wanting to run such a service.</p>
<p>anyways, the ideas of those is to converge on a set of FAQs and knowledge items more than just have random discussion, and force people to reuse existing topics.</p>
<p>if i had more time, i'd probably setup something like this but really, i can only encourage those initiatives at this point. <img src="http://git-annex.branchable.com/smileys/smile.png" alt=":)" /></p>
comment 2http://git-annex.branchable.com/devblog/day_285__tuning_git-annex_unused_refs/comment_2_dae167e473c60dace129c66beb0af384/joeyh.name2015-05-16T18:35:22Z2015-05-16T18:35:22Z
Unfortunately stack exchange is nearly unusable for me on dialup. In order for me to contribute to any git-annex communication channels, it needs to be something that can be taken offline, like git or email.
comment 3http://git-annex.branchable.com/devblog/day_285__tuning_git-annex_unused_refs/comment_3_52179fc326e681d8fbf85ee8963f352c/anarcat [id.koumbit.net]2015-05-16T21:46:20Z2015-05-16T21:46:20Z
<p>interesting! i didn't think of those requirements, which do seem quite stringent, but i am certainly sensitive to them, considering i will be spending my own significant amount of time with intermittent access soon.</p>
<p>i have opened a todo item to move the discussion somewhere more relevant, see <a href="http://git-annex.branchable.com/todo/enable_a_discussion_forum_or_support_system/">enable a discussion forum or support system</a>.</p>