how-to-maintain.txt (2188B)
1 [DRAFT DRAFT DRAFT] 2 3 4 How to maintain the anonbib / how to make the anonbib maintainable. 5 ------------------------------------------------------------------- 6 7 1. Keep an eye on the proceedings of conferences where 8 anonbib-related papers are often published. A long time ago, I 9 listed a bunch in venue-checklist.txt. Are we missing any papers? 10 11 If you read the paper, do you have any comments on why other 12 people should read it? If so, add some notes. 13 14 15 2. When you add papers to anonbib.bib, make sure you include a URL, 16 a section, and optionally the 'selected' tag. Except under 17 extreme circumstances, never mark a paper as selected unless it 18 is online with some URL. 19 20 21 3. If anybody sends you a paper, add it. Take about 30-60 seconds to 22 decide whether it should be 'selected'. Use your judgment. 23 24 If they send you a paper and you can't find it online, ask them 25 for a URL, and remind them about "Online or Invisible". 26 27 (EXTRA CREDIT: figure out why the paper wasn't added 28 earlier. Should we look at other papers published in the same 29 venue? Should we try to find other stuff on the authors' CVs?) 30 31 32 4. If you have done neither 1 nor 3 in the last 3 months, it is 33 bad form to add papers that you co-wrote. 34 35 36 5. EXTRA CREDIT: when you add/read a paper, look at its bibliography 37 and related works section and see if we're missing anything. 38 39 40 6. EXTRA CREDIT: When you write a paper, look to see whether there's 41 anything in your bibliography that isn't in anonbib and should 42 be. 43 44 45 Things we need to do to make anonbib functional. 46 ------------------------------------------------- 47 48 1. We need more people doing the above stuff. Historically, grad 49 students who are trying to catch up on the whole field are pretty 50 productive here, since they are doing this kind of stuff anyway. 51 52 2. We need the website-rebuild process to be more functional and 53 automated. A cronjob or a commit hook would be fine here. 54 55 3. We need to decide whether to move to git{hub,lab}, or whether to 56 give torproject LDAP accounts to everybody who needs commit 57 rights. 58 59 4. Perhaps a code rewrite; my 2003 Python is pretty janky! 60 61 62 63 [DRAFT DRAFT DRAFT] 64