[TYPO3-doc] Integrating "Disqus" on docs.typo3.org
Bastian Waidelich
bastian at typo3.org
Tue Aug 6 12:17:00 CEST 2013
Michael Stucki wrote:
Hi Stucki,
> [...] let me mention that the server team could provide any of these
> tools even if they are based on Ruby on Rails. That's just the same case
> for Redmine already, so don't consider this as a limiting factor...
That's great news, thanks for the input!
> [...] unfortunately, it appears to me like this topic is slowly fading
> out without any result.
I feared the same but frankly I don't really know what to do about it..
I had another look at the two suggested solutions and I'm not convinced
that either one is sufficient enough for *.typo3.org in the current state:
Juvias' documentation is very limited but based on the README and a demo
installation it seems that it is missing some key features:
* Flagging comments as inappropriate
* Voting
* Code highlighting
* Email notifications
* Extensible authentication
* Nested comments
I'm not 100% for all of these as the demo is so limited and when I tried
to create a non-admin user I think I broke it..
Discourse looks quite promising to me but in their FAQ they state that
it is "early beta software, and likely to remain so for many months".
Maybe you guys don't agree with the minimal feature set I suggested in
the first post, but I couldn't find a different solution that covers it.
So I experimented a bit with the disqus API[1] and now the example shows
how many comments there are for the current page *without transferring
your data to the disqus servers*. In fact it should be possible to
tunnel all interactions (display, create, delete, flag, ... comments)
through a PHP script that talks to the API and no cookie whatsoever
would be sent to a 3rd party.
But that would mean a lot of work (maybe not so much less than if we
really implemented the whole thing ourself).
I happily help..
* ..by asking the association regarding legal implications
* ..implementing a solution (PHP)
* ..moderating comments
But my initial recommendation stays (using a 3rd party tool with
opt-in/out to start with) and if there is no valid counter-proposal I
don't know what to do about this.
[1] http://disqus.com/api/docs/
--
Bastian Waidelich
--
Core Developer Team
TYPO3 .... inspiring people to share!
Get involved: typo3.org
More information about the TYPO3-project-documentation
mailing list