Qt Project Web Actions

From Qt Wiki
Jump to navigation Jump to search

Suggested action running Qt Project Web and Open Governacing

This document describes actions which we must, should or could do to make Open Goverancing work. It also includes absolutely neccessary actions on day to day operation, and status on how we are solving those actions.

The actions looked at on the IRC progress meeting 18.02.2013, 20:00-21:30:

Choice of Wiki server: Expression Engine and Wikimedia evaluation

What is the problems and benefits with Expression Engine today

Problems:

  • EE does not handle co-working and merging of wikipages

' The Qt 5 documentation cleanup project had to be move to the KDE Wiki, because concurrent edits were lost without warning

  • EE may not separate between different users access, e.g superuser, moderator with control panel access and ordinary users. Workaround is using a group functionality, which is not extendable to the admin console …
  • EE has horrible markup syntax
  • EE has a broken URL parser

' Punctuation after a plain URL becomes part of the URL (e.g. Broken: http://www.google.com, http://www.qt.io) ' Yet, the plus sign gets left out of hyperlinked text (e.g. I can't correctly link to the Wikipedia C++ page++ )

  • EE diffs only highlight the changed line numbers, not the words themselves

Benefits:

  • EE looks good

What is the problems and benefits with Wikimedia?

Problems:

  • WM con? Possible to get commercial support?
  • WM con: perhaps too complicated and feature rich

Benefits:

  • WM I'm fairly sure wikimedia could be "embedded" to current layout too
  • WM pro: standard wiki syntax
  • WM pro: We can put the code into the repo.
  • WM pro: a couple of orders of magnitude over EE in terms of worldwide usage => more support
  • WM provides a watch list, which lets users be notified when a page of interest gets updated
  • WM provides good visual separation between major sections (horizontal line)
  • WM diffs show how each word in a line has changed

Further evaluation required:

  • WM Can we get Single SignOn (SSO) with the bugtracker with EE or wikimedia?
  • WM pro/con There isn't a single entity developing mediawiki and selling support. but there are lots of other companies that do support

What has to be done if we are replacing Expression Engine with Wikimedia?

  • Change to Wikimedia need not only copying EE wiki content over, but also adding new features

What has to be done if we're keeping Expression Engine?

  • The Expression Engine is kept for now, but we are evaluating the options rationally.

Overall improvements

  • single sign on, same accounts across all systems, maybe even without having to reauthenticate everywhere all the time.
  • What I would like to see is some idea how to integrate all the different web-things (gerrit, jira, wiki, devnet forums) we have into one site.
  • Consistent layout for a start, a link to the bugtracker on devnet, one account for everything
  • The site is called Qt-project.org, but it actually is only support.qt.io at this time… all the real work happens elsewhere.
  • the accounts CAN be shared, eventually with some minor work (such as: writing a mediawiki/EE/… plugin that uses JIRA/gerrit account database)

Handling banning of spammers etc.

  • Requirement: Banning users (moderator email list (private) has to be created): All banning requests should be done via qt-project at digia dot com in order to track the reasons
  • Requirement: Request for banning are done to the moderators IRC channel, but also through the the report post… feature.
  • Feature: Suggestions is to track moderators action, then we need a moderators mailing list. Even if we decide on IRC, we can just send a quick mail there saying "I've banned XXX because of spam". quick, effective, I can't see any cons. (as a bonus — moderation requests (aka the "report" button) should be sent to the same ML by the qt-p.o software)
  • Feature: The banning also imply that moderaters are able to use the admin console in the Qt Project Web for memer management.
  • Action: Knut are contacting Gurudutt for a short walk thorugh for the access to Qt Project Web. Which access groups are there, and what's possible in todays setup. E.g moderators should be able to ban spammers and others who breaks code of counduct or license agreement for using Qt Project Web.
  • Privileges

Legal issues

  • Doc and Wiki reuse