Hi Ankry, on Italian Wikisource and on Neapolitan Wikisource there are "Technical" village pumps. I suppose that would be the correct place to post it if there is such a page in other languages. It would be interesting to see what happens if a whole community writes on Phabricator in order to delay a major deployment... It happened in the past that we used global CSS to nullify (display=None) a newly deployed feature that wasn't mature enough. Here it would require more work I suppose, but I am sure that it can be done.
What I am trying to say is that it's ridiculous to be passive when a different community (the so called developers) modify a project without any contact with the users. Alex *Ruthven* on Wikipedia On Sat, 20 Nov 2021 at 18:36, Ankry <[email protected]> wrote: > Well, I was notified by techncally skilled users that the ned OpenSeadragon > library is much heavier and more memory consuming than curreently used > tools. So I can only hope that its load into memory can be disabled if one > needs so. > > (may be critical while working on multiple pages at once) > > However, I doubt if any technical comments from communities expressed here > will reach developers. And which wiki pages would be more appropriate for > such comments. > > Ankry > W dniu 20.11.2021 o 14:33, Ruthven pisze: > > Hi all, > as usual, I get surprised every time there are major changes on the > MediaWiki software that are deployed without providing advance warning to > the community. > Every time it's the same story: something stops working on the project. A > gadget, a toolbar or some personalised JS. > > This time it was T288141 (see https://phabricator.wikimedia.org/T288141), > that was deployed in all the Wikisources (then rolled back because > WikiMedia computer scientists are the best) completely disrupting redesigning > the image side of the Page namespace. This affected the toolbars (see > https://phabricator.wikimedia.org/T296033) and several gadgets around all > the Wikisources. > > I am not saying that MediaWiki software shouldn't be improved: it's normal > that we're trying to get all we can from this outdated software. I am just > asking that major changes that affect all the Wikisources should be > announced in every single Village Pump waaay before deploying them on the > projects. > > Is it possible, as a Usergroup, to do a little pressure to be considered > as a community and not as guinea pigs on which to deploy new, > partially-tested features? > > Alex > *Ruthven* on Wikipedia > > _______________________________________________ > Wikisource-l mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > _______________________________________________ > Wikisource-l mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Wikisource-l mailing list -- [email protected] To unsubscribe send an email to [email protected]
