1) Who can take over the help site, or if we should just close it.
We've been dragging our collective feet on this since forever. NPM has blazed a trail with figuring out privacy policies and a code of conduct:Please read both of these pages. The policies here sound exactly like how we have been operating RubyGems.org, we just haven't written them down, agreed to them, and started to enforce them.I'm starting to see one of many reasons why NPM, Inc. exists: It's to provide the human face behind the service. Our support queue on http://help.rubygems.org is currently 30 issues deep. These issues are mostly requests to delete gems, and at least one that has threatened legal action against an all-volunteer run service.
I got in touch with an acquaintance of mine who is a lawyer with a particular focus on startups and issues such as these. He said he'd be up for helping out on a pro bono basis if you're interested. Let me know and I can put you in touch. He's given me personally some valuable advice on my own projects, as well as being an important resource to the company I work with.
======================================================= I welcome VSRE emails. Learn more at http://vsre.info/ =======================================================