Re: [tor-bugs] #10022 [Website]: We need a new blogging system

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#10022: We need a new blogging system
-----------------------------+-----------------
     Reporter:  phobos       |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Website      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by arma):

 Replying to [comment:5 lunar]:
 > All in for a static blog generator backed by a revision control system.

 Sounds good to me (in theory).

 > The blog is also doing the event calendar.  Should that be kept?

 I think an event calendar could be quite useful if we keep it up to date
 and if we make it findable for our community. It could be something very
 simple, like a text file we update via git, and point to from the end of
 the 'upcoming events' section of TWN.

 > What about migration? We need to keep content, but do we also want to
 migrate comments?

 Unfortunately, my vote is yes. It sure sounds like a pain, but many of the
 comment sections of more recent posts (where I've put a lot of effort in)
 are useful resources.

 Maybe that means we don't want to migrate, and instead just take static
 html from the old posts-with-their-comments?

 Another option is to go through and extract everything perfectly into
 stackexchange questions and answers. I'd like that to happen, but I think
 it needs to be done by the community at their own pace.

 > Regarding comments, the main think I can think of here is social: who's
 taking care of them? Moderation, answering the bulkâ Roger is doing a good
 amount of that for the current blog, but we might want to have more formal
 roles or processes?

 I'm basically the sole blog person at this point. And it is a bit weird
 that we have a blog, we have helpdesk, and we have stackexchange. It seems
 like about half of the blog things, and an unknown fraction of the
 helpdesk things, could be resolved by making a good stackexchange entry
 and just pointing to it each time the issue comes up. But there's
 remaining value in both even if we do that.

 As for more formal roles / processes... that's a tough one. I'd love to
 have some more volunteers here. But it's not clear that it would be the
 best use of our (at this moment limited) funding. On the third hand, here
 I am not doing some of the other just-as-critical things that I could be
 doing.

 > (''This is actually the reason why I always disabled comments for TWN
 posts. I don't want to feel sole responsible with the comments there and
 piling unmoderated ones are bad from our users point of view.'')

 Makes perfect sense.

 > I don't think Disqus is an option, otherwise we are going to have the
 same problem we are currently having with Stack Exchange: we can't trust
 their data retention policy.

 Yeah.

 > Discourse looks nice from several aspects. That's a Rails app, not the
 worst to administrate but it needs a maintainer on the sysadmin side. It
 also have an impressive feature list and so it also needs someone to
 decide about how to turn all the little knobs.

 Haven't looked at it, but am open to it.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10022#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs