2.0 release schedule (help needed) and wiki updates.

Hi all:

Just a few notes as we start cycling into the 2.0 release cycle. I
hope to release mid July.

To fix issues with mysql's use of locale (leading to indexer issues)
we have had some code changes. These changes allow the roundup admin
to control the locale used to connect to mysql. At the moment it seems
like mysql databases would have to be dumped and restored as part of
the update cycle even if you are staying with python 2. (Note that a
roundup dump/restore is required if you are going to use roundup 2.0
under python 3.)

However none of the core developers use mysql, so we need support from
the community. If you run mysql we really can use your help to develop
and test upgrading instructions. Please email me if you can provide
assistance. You don't need to install roundup-2.0. The testing can be
done from a current development environment using the demo server.

I have been going through the pages in the wiki and adding them to
Categories.  Currently we have categories for pages with examples:

   * using javascript
   * adding new detectors
   * using the REST interface (new in roundup 2.0)
   * web page UI enhancements

For those of you who have been waiting for a REST interface, I added
an article to the wiki showcasing how to use it. You can visit:

  https://wiki.roundup-tracker.org/CategoryInterfaceRest

to see it as well as other examples when people contribute them.

Providing a nice modern javascript based interface while still
supporting browsers (e.g. w3m, lynx, emacs w3 mode) that don't have
javascript or users who have javascript disabled in their browsers is
tricky.

Using text based browsers is often useful for attaching a file or
recording information from files located on a remote server. This
eliminates the need to transfer the file to a local system, or trying
to use a graphical browser over VNC or X11.

The native text based input that is used for multilink editing works
well without javascript. However it is not a great user experience.
Ideally roundup should require javascript only if the browser supports
it.

https://wiki.roundup-tracker.org/IsJavascriptAvailable describe simple
template extensions and modifications to the page.html template. These
modifications allow the client to tell roundup if javascript is
available. Then the templates can be modified to ship a lean
non-javascript interface when the heavier javascript interface can't
be used.

Some people prefer allowing the user to login with their email address
rather than having to remember their username.
https://wiki.roundup-tracker.org/LoginWithEmail is a replacement
wrapper for the login action that allows a user to log in with their
roundup user name or with their primary email address.

If you haven't visited the wiki recently please take a look and see if
you learn something new.

Have a great week all and stay safe.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.