Dear all,
------------------------------
Like with all other development, I find a need in more documentation of the
plans and of the currently active things.
For example, VisualEditor has nothing to help me comprehend its code-base than
the source code itself; it had only been a jamesf's line at a meeting which
made me aware of the fact that the cologne blue and modern skins are now only
supported by community.
Now there are some really cool beta features that only work with the vector
skin. To only resource to help me is the source code. There is no UML diagram,
no docs explaining which part of code does what.
------------------------------
Another idea is an answer to WHY you are working on the media viewer. It is a
nice experience but...
...there is a lot of pages which would make use of a do-it-without-page-reload
approach, such as log-in page, edit page, history page.
...there also is a need of all sister projects in wizard tools and widgets.
Currently adding an article to Wiktionary is a royal pain and I could not
figure out how to add an idiom with translation, without pulling hair and
spending time to find another existing Wiktionary entry which is (1) a verb,
(2) an idiom, and (3) has a translation. There also are gadgets for the
so-called "interactive template" use-case [1] where each developer reinvents
wheel a lot and the gadgets share no code but they should.
...everything the WMF works on should have long-term impact after WMF stops
working on the darn thing. The impact should be cross project.
... With this in mind I would personally encourage heavy collaboration of all
teams to build a framework which lets people script the MediaWiki software
including media viewer screen, log-in screens, article creation screens /
wizard, an interactive thingie for working with templates [1] (taking an
{{unblock}} request for example without having to memorize the template syntax).
This may need help from VisualEditor and Parsoid people; from Flow people who
had spread the 'custom workflows' rumour; and YOUR help to understand that
moving an interactive thingie logic from an extension onto a wiki benefits
everyone, even if it makes codereview-worthy bits harder to spot (recall some
people saying that none of UploadWizard's logic can sit on-wiki because of that
[2])
[1] https://www.mediawiki.org/wiki/User:Gryllida/Templates/Interactive
[2]
https://www.mediawiki.org/wiki/Requests_for_comment/UploadWizard:_scale_to_sister_projects
Gryllida.
On Sun, 23 Feb 2014, at 20:25, Gergo Tisza wrote:
> Hi all,
>
> the Multimedia team had some discussions recently about how to make our
> work more transparent and more open to volunteers, and we decided to try
> using an open subscription mailing list for team discussions, instead of
> the current practice of cc-ing each member manually. These discussions are
> about day-to-day details of our work; sometimes feature requirements or
> design, sometimes technical details. The volume is typically one or two new
> threads per day.
>
> We weren't sure how much members of this list would be interested in such
> conversations and didn't want to flood this list with mails that are not
> useful for most members, but we also do not want to split conversation
> channels unnecessarily. Please help us by telling whether you would be
> interested in the topics mentioned above, or would prefer if we created a
> new mailing list for them.
>
> Thanks!
> Gergő
> _______________________________________________
> Multimedia mailing list
> multime...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/multimedia
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
