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 lunar):

 All in for a static blog generator backed by a revision control system.

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

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

 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?

 (''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.'')

 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.

 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.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10022#comment:5>
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