I'd like to tell too my concern too about CX : it has been pushed into
production for several years, with a lot of unnecessary advertisements (I
still get a popup inciting me to use it each time I try to look at a
deleted page, while I have clearly disabled CX in the configuration) and
with many problems in the articles created with it, which requires a lot of
work from wiki gnomes to fix them... Bug reports are just put on the side
(example T192582 <https://phabricator.wikimedia.org/T192582>) with the
reasoning that CX2 is coming, but it's been months/years and nothing seems
to be in sight.
What's the actual roadmap ? A real one, not a wishlist...
If CX2 is not going to be available soon, could you at least reduce the
burden imposed on volunteers to fix the problems it creates by reducing
ads, focusing on fixing problems...
On Thu, Sep 6, 2018 at 10:13 AM Strainu <strainu10(a)gmail.com> wrote:
More than a year has passed since the email below and subjectively,
editors are complaining just as much about not being able to save
changes and other nuisances. Now, I know that wikipedians are not shy
about expressing their discontent, but I also cannot overstate the
impact CX can have for small and medium-sized communities.
Since the pages mentioned in Amir's email have not seen much action, I
would like to ask for another update from the engineering team. Is CX
still developed? Are small bug reports handled yet or are you still
waiting for some big feature?
2017-05-02 11:42 GMT+03:00 Amir E. Aharoni <amir.aharoni(a)mail.huji.ac.il>il>:
2017-04-27 8:55 GMT+03:00 Strainu
Following the recent outage, we've had a new
series of complaints
about the lack of improvements in CX, especially related to
server-side activities like saving/publishing pages.
Now, I know the team is involved in a long-term effort to merge the
editor with the VE, but is there an end in sight for that effort? Can
I tell people who ask "look, 6 more months then we'll have a much
better translation tool"?
Is there a publicly available roadmap for this project and more
generally, for CX?
Thanks again for bringing this up.
Currently the Language team is indeed working on transitioning the
component to VE. At the moment we are completing
the rewrite of the
frontend internals using OOjs UI and so using VE's special handling of
cases. This is more than a refactoring—this will
also improve the
of several features such as saving and loading,
paragraph alignment, and
We hope to complete the transition of the translation editing interface
VE in July–September 2017. This will not only
change the interface
but will also bring in some of the most often
requested CX features, such
as the ability to add new categories, templates, and references using
existing tools rather than just adapt them, and
to edit the translation
using wiki syntax.
The next part to develop would be another round of improvement of
support. The previous iteration was done in the
latter half of 2016, and
allowed adapting a much wider array of templates, including infoboxes.
However, one important kind of template that is not yet supported well
enough is ones inside references (a.k.a. citations or footnotes), and
will be the focus of the next iteration. We also
plan to improve CX’s
template editor itself by allowing machine translation of template
parameter values, and by fixing several outstanding bugs in it.
After finishing these two major projects, in early 2018 we expect to work
on fixing various remaining bugs, after which we plan to start declaring
Content Translation as non-beta in some languages. We are figuring out
which bugs exactly will these be; the current list is at
, but it will
change somewhat before we get there. (Suggestions
about what should go
there are welcome at any time.)
Finally, two further future directions that we are thinking about
1. Translation List: Shared and personal lists of articles awaiting
translation ( https://phabricator.wikimedia.org/T96147
). We already
designs for it, but the implementation will have
to wait until we fix the
more urgent issues above.
2. Better support on mobile devices. This is complicated, but
Some early thoughts about this can be found at
, but there will need to be much more design and
development around this.
You can see a more formal document about this here, although the content
largely the same:
The Language team already had this more or less figured out a couple of
months ago, but the publishing was delayed because of the higher-level
planning process (
Wikitech-l mailing list
Wikitech-l mailing list