Dear all,
It is back again the time to select representants for our Wikimedia
Foundation Board of Trustees.
This year, the process is different from previous year. If you want to
go look in details, I invite you to read ALL the details on :
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022
However, if you want to get the essence of it... here is what you should
know...
1) Two people will be selected to join the board, following a two
step-process
Step 1: From 1 to 15th of July, all affiliates will vote on the initial
list of candidates. Only one (1) vote per affiliate. From all votes
pooled together, a short list of 6 candidates will be sorted
Step 2 : From 15-29th of August, the community will vote on that short
list.
In between the two... the community can ask questions to the candidates
2) Currently, 13 people are candidates. You may find details here :
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Candida…
They have provided initial statements.
3) Our affiliate will vote beginning of July. Sam and I will prepare a
process so that you may cast your votes. From your propositions, we will
sort ONE name.
4) I will invite all current candidates to promote themselves, should
they be interested to, on this mailing list
Cheers
Florence
We are to rank all candidates. Shani has also done great work these last
few years and has supported offline efforts during this time. She is
currently on the board so has excellent experience of what is involved.
On Thu, May 19, 2022 at 05:03 <offline-l-request(a)lists.wikimedia.org> wrote:
> Send Offline-l mailing list submissions to
> offline-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe, please visit
>
> https://lists.wikimedia.org/postorius/lists/offline-l.lists.wikimedia.org/
>
> You can reach the person managing the list at
> offline-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Offline-l digest..."
>
> Today's Topics:
>
> 1. WMF board elections are back (Florence Devouard)
> 2. Re: WMF board elections are back (Stephane Coillet-Matillon)
> 3. Re: WMF board elections are back (Federico Leva (Nemo))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 18 May 2022 20:22:40 +0200
> From: Florence Devouard <fdevouard(a)gmail.com>
> Subject: [Offline-l] WMF board elections are back
> To: Using Wikimedia projects and MediaWiki offline
> <offline-l(a)lists.wikimedia.org>
> Message-ID: <ba08f8da-8409-c867-916b-b0cb69eb21f5(a)gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Dear all,
>
>
> It is back again the time to select representants for our Wikimedia
> Foundation Board of Trustees.
>
> This year, the process is different from previous year. If you want to
> go look in details, I invite you to read ALL the details on :
> https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022
>
> However, if you want to get the essence of it... here is what you should
> know...
>
> 1) Two people will be selected to join the board, following a two
> step-process
>
> Step 1: From 1 to 15th of July, all affiliates will vote on the initial
> list of candidates. Only one (1) vote per affiliate. From all votes
> pooled together, a short list of 6 candidates will be sorted
> Step 2 : From 15-29th of August, the community will vote on that short
> list.
>
> In between the two... the community can ask questions to the candidates
>
>
> 2) Currently, 13 people are candidates. You may find details here :
>
> https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Candida…
> They have provided initial statements.
>
> 3) Our affiliate will vote beginning of July. Sam and I will prepare a
> process so that you may cast your votes. From your propositions, we will
> sort ONE name.
>
>
> 4) I will invite all current candidates to promote themselves, should
> they be interested to, on this mailing list
>
>
>
> Cheers
>
>
> Florence
>
> ------------------------------
>
> Message: 2
> Date: Thu, 19 May 2022 09:23:50 +0200
> From: Stephane Coillet-Matillon <stephane(a)kiwix.org>
> Subject: [Offline-l] Re: WMF board elections are back
> To: Using Wikimedia projects and MediaWiki offline
> <offline-l(a)lists.wikimedia.org>
> Message-ID: <72AE417B-7084-4BD2-A19B-5F1F02F458D9(a)kiwix.org>
> Content-Type: multipart/alternative;
> boundary="Apple-Mail=_D36D33C5-676F-4C08-85C3-BF27AD27DCD0"
>
> Hi everyone,
>
> Thanks for this Florence. I’ve gone through the list of candidates and
> there are very fine people (better that than the opposite!).
>
> We at Kiwix, however, would like to single out Kunal Mehta <
> https://meta.wikimedia.org/wiki/User:Legoktm> (legoktm), who has been a
> long-time supporter of Kiwix within the Foundation (I might stand corrected
> but he also single-handedly ensured Debian ports for it and volunteered top
> code). Needless to say (but I am still saying it), Kunal has been getting
> our Kiwix-branded chocolates ever since we started sending them out.
>
> I encourage you to read his bio/user page <
> https://meta.wikimedia.org/wiki/User:Legoktm> - Kunal is not just a
> coder, but has a vision for free knowledge. I am told he left the WMF last
> December, so my take here is that we would have a trustee here that 1.
> Understands the tech 2. Understands the WMF and 3. Understands us (the
> offline crowd). That’s a lot boxes to tick.
>
> My little informative email has turned into a longer-than-expected soapbox
> campaigning, but so be it. If you home chapter is undecided about whom to
> support, I encourage you to forward it to them as well.
>
> Cheers,
> Stephane
>
> > Le 18 mai 2022 à 20:22, Florence Devouard <fdevouard(a)gmail.com> a écrit
> :
> >
> > Dear all,
> >
> >
> > It is back again the time to select representants for our Wikimedia
> Foundation Board of Trustees.
> >
> > This year, the process is different from previous year. If you want to
> go look in details, I invite you to read ALL the details on :
> https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022
> >
> > However, if you want to get the essence of it... here is what you should
> know...
> >
> > 1) Two people will be selected to join the board, following a two
> step-process
> >
> > Step 1: From 1 to 15th of July, all affiliates will vote on the initial
> list of candidates. Only one (1) vote per affiliate. From all votes pooled
> together, a short list of 6 candidates will be sorted
> > Step 2 : From 15-29th of August, the community will vote on that short
> list.
> >
> > In between the two... the community can ask questions to the candidates
> >
> >
> > 2) Currently, 13 people are candidates. You may find details here :
> https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Candida…
> > They have provided initial statements.
> >
> > 3) Our affiliate will vote beginning of July. Sam and I will prepare a
> process so that you may cast your votes. From your propositions, we will
> sort ONE name.
> >
> >
> > 4) I will invite all current candidates to promote themselves, should
> they be interested to, on this mailing list
> >
> >
> >
> > Cheers
> >
> >
> > Florence
> > _______________________________________________
> > Offline-l mailing list -- offline-l(a)lists.wikimedia.org
> > To unsubscribe send an email to offline-l-leave(a)lists.wikimedia.org
>
>
Hello
This last few months we have published important new versions of Kiwix
Desktop (rich ZIM reader for Windows & GNU/Linux), Kiwix Tools (with
HTTP daemon Kiwix Serve) and the underlying Libkiwix (for all Kiwix ports).
This has been a really long time since we talked here about our Kiwix
flagship softwares. Actually, these releases are the result of almost 18
months of work. We are not proud to take so long to make new releases
but the resources are tight and major changes have been done which
needed a high level of coordination and a long standing effort.
We finally have released:
* Kiwix Desktop 2.1 & 2.2 (93 tickets closed)
* Kiwix Tools 3.2 (21 tickets closed)
* Libkiwix 10 (123 tickets closed)
In a Nutshell here are the main improvements:
* Support of new libzim7 API and ZIM format
* Numerous improvements and bug fixes around fulltext search and suggestions
* Major improvements in the library mgmt
* Many UI design improvements in Kiwix Desktop
* Few fixes around GNU/Linux appimage version of Kiwix Desktop
* Revamp the welcome page in Kiwix Serve and allow filtering
* Strong development of the OPDS API in Kiwix Serve
* Lots of smaller bug fixes and new features
* ... You can go to https://code.kiwix.org to get the complete
changelogs and for more details.
Go to https://kiwix.org to download latest versions of Kiwix!
In the next 18 months, more releases of these pieces will be done. 2020
and 2021 have been busy with core improvements and this is now over (at
least for a bit ;). We are quite happy with our low-level libraries. We
will - from now - focus more on the UX around books in Kiwix, in
particular around the local/online library (something we would already
have done in 2021 but we have been too short on time).
I want to emphasize that this part of our work would not be possible
without the strong commitment of the WMF. The WMF, with his financing,
secures a baseline maintenance of the core software pieces in openZIM
and Kiwix. For the rest, we rely on the time & talent of C++ volunteer
developers.
Happy WE!
Kelson
--
Kiwix - Wikipedia Offline & more
* Web: https://kiwix.org/
* Twitter: https://twitter.com/KiwixOffline
* Wiki: https://wiki.kiwix.org/
Hi
I remark that it seems it makes a year a half that we don't have post
posted here news about Kiwix JS. It is a pity, because this is one of
our most active code repository!
On the top of this, we just have released version 3.3.1 of all Web
Browser extensions (Firefox, Chrome & Edge) and Kiwix JS for Windows.
You can find the latest version of Kiwix JS Browser extensions:
* Chrome:
https://chrome.google.com/webstore/detail/kiwix/donaljnlmapmngakoipdmehbfci…
* Firefox: https://addons.mozilla.org/en-US/firefox/addon/kiwix-offline/
* Edge:
https://microsoftedge.microsoft.com/addons/detail/kiwix/jlepddlenlljlnnhjin…
Here are the recent changelogs:
Kiwix-JS v3.3.0
* FIX: Improve packaging for the Ubuntu Touch app
* FEATURE: Provided a workaround to enable Service Worker mode in
Firefox extensions (via a PWA)
* NEW: App now defaults to Service Worker mode if accessed directly as a
PWA (does not apply to browser extensions)
* NEW: Support for non-http URLs in img and link tags (e.g. data:
javascript:) in JQuery mode
* NEW: Added helpful tooltips to icons and settings in the app
* FIX: Scrolling to anchor targets in JQuery mode
* FIX: Caching of ZIM assets now includes any required query string in
SW mode
* FIX: Any favicon declared by the ZIM is now extracted and attached in
JQuery mode
* BUGFIX: Incorrect processing of titles with question marks or hashes
prevented display of some articles
Kiwix-JS v3.2.0
* NEW: Support latest format of ZIM archives (with no namespace)
* NEW: Optimization of title search by eliminating redundancies
* NEW: Support new format of title listings (v1) in no-namespace ZIM
archives
* NEW: Use fast binary WASM decoders with fallback to ASM if necessary
* UPDATE: Clearer and more extensive documentation for end users in About
* BUGFIX: Issue with calculation for selection of random articles
Kiwix-JS v3.1.0
* NEW: Low-level block cache significantly improves binary search speed,
and can speed up resource loading in most browsers
* NEW: Archives with WebP-encoded images are now decoded in legacy
browsers via a polyfill
* UPDATE: Images are now extracted sequentially in jQuery mode from the
top of the DOM
* BUGFIX: Running binary searches are now cancelled completely if user
enters new search term or navigates away
The full Changelog can be found here:
https://github.com/kiwix/kiwix-js/blob/master/CHANGELOG.md
We have already started to release ZIM files "without namesapces" and
this version 3.2.0+ is mandatory if you want to enjoy them with Kiwix JS.
All our Windows apps based on Kiwix JS have been updated in Microsoft
App Store too. You can enjoy our apps on all Windows
based devices (mobiles, tablets, PC, Xbox, ...):
* Wikivoyage:
https://www.microsoft.com/fr-ch/p/wikivoyage-by-kiwix/9n5sb90q4jbj
* Wikimed: https://www.microsoft.com/fr-ch/p/wikimed/9phjsnp1cz8j
* Kiwix: https://www.microsoft.com/fr-ch/p/kiwix-js/9p8slz4j979j
Please report any problem. Work continues on our forge at
https://github.com/kiwix/kiwix-js and
https://github.com/kiwix/kiwix-js-windows.
Regards
Emmanuel
--
Kiwix - Wikipedia Offline & more
* Web: http://www.kiwix.org
* Twitter: https://twitter.com/KiwixOffline
* more: http://www.kiwix.org/wiki/Communication
Dear WOW, there is an ongoing discussion on Meta about how affiliates
should participate in board elections.
---------- Forwarded message ---------
Please follow this link to make proposals and discuss these questions
<https://meta.m.wikimedia.org/wiki/Wikimedia_Foundation_Board_of_Trustees/Ca…>
:
1. How can we ensure diverse representation among elected candidates?
The Board of Trustees noted the importance of selecting candidates who
represent the full diversity of the Wikimedia movement.
2. What are the expectations for the candidates during the elections?
Board candidates have traditionally completed applications and answered
community questions. How else might we get insight into candidates?
3. How should affiliates participate in the elections?
Two seats of the Board of Trustees due to be filled this year were last
filled in 2019 through the Affiliate-selected Board seats process. A change
in the Bylaws removed the distinction between community and affiliate seats
<https://foundation.wikimedia.org/w/index.php?title=Bylaws&type=revision&dif…>.
How should affiliates be involved in the selection of new seats?
The Board is seeking feedback about this last question especially from the
affiliate community. Everyone is invited to share proposals and join the
conversation.
Hi,
We have released the first minor release of libzim7 branch: libzim 7.1.0.
Nothing really big, here is the changelog:
* Fix dirent test on 32 bits architectures (@mgautierfr #632)
* Fix compilation on Alpine - with musl (@amirouche #649)
* Don't crash if ZIM without illustration nor X/W namespace
(@mgautierfr #641)
* Switch default suggestion operator to AND (@maneeshpm #644)
* Add a new method Archive::getMetadataItem (@mgautierfr #639)
* Better indexion criterias (@mgautierfr #642)
* Avoid duplicated archives in the searcher (@veloman-yunkan #648)
* Fix random entry (@veloman-yunkan #650)
* Various improvements.
- CI @mgautierfr #640, @kelson42 #638, @legoktm #654
- Doc @rgaudin #646
A new Python-libzim using it will be released soon and we are still
working on the libzim7 Node.js binding.
A small minor release 7.2.0 is already in the pipe and should be
released next week.
More info at: https://github.com/openzim/libzim
For the Kiwix team
Kelson
--
Kiwix - Wikipedia Offline & more
* Web: https://kiwix.org/
* Twitter: https://twitter.com/KiwixOffline
* Wiki: https://wiki.kiwix.org/
Hi,
After announcing the libzim7 release a month ago, we are proud to
release the version 3.0.0 of the Zim-tools. The Zim-tools is the
swiss-knife for manipulating ZIM files.
Actually this release has been made available already a few weeks ago
and here again this is major release. It makes almost a year we have
been working on this new release which mainly brings support of libzim7
and major improvements to the zimcheck tool.
Here is the complete changelog:
* zimwriterfs: Do not allow zimwriterfs to overwrite a existing zim
file (@asashnov #193)
* zimcheck: Make zimcheck print json output with option `--json`
(@veloman-yunkan #206)
* zimcheck: Make zimcheck multithreaded (@veloman-yunkan #194)
* zimcheck: Add an option to check for redirection loops (@shashwat1002
#218)
* zimrecreate: Add an option `-j` to not create fulltext index
(@data-man #234)
* zimrecreate: Add option `-J` (--threads) to set the number of threads
to use (@data-man #235)
* remove zstd compression options. We are now always creating zim file
with zstd (@kelson42 #261, 264)
* zimwriterfs: Do not use the extension of file as mimetype (@mgautier
#265)
* zimcheck: Improve performance of detection of the kind of url
(@veloman-yunkan #179)
* Support new protocols xmpp, news and urn (@kelson42 #205)
* zimdump: zimdump now print the favicon and mainentry path instead of
the index (@kelson42 #220)
* zimdump: Add a option to create html redirect insteal of symlink
* zimdump: Fix issue where zimdump crash depending of the stored path
of redirection (@maneesh #211)
* zimdump: Fix argument --ns not working (@maneesh #216)
* Add zimcheck unit tests (@veloman-yunkan #215)
* zimdump: Fix http redirect (@veloman-yunkan #225)
* Adapt zim tools to new libzim api (@mgautier @veloman-yunkan @maneesh)
* Compile zimsearch binary only if libzim is compiled with xapian
(@mgautier, #201)
* Docker : Better open zimtools image (@rgaudin #209)
This new release is an important milestone in our global QA effort
around ZIM files. Latest Zimcheck has been already integrated in our
Zimfarm and its new machine readable output can now be checked in our
(currently being build) CMS.
From a more general point of view, improving the Zim-tools is essential
to allow hackers to easily deal with the ZIM files and maybe even
produce their own. More infos at https://github.com/openzim/zim-tools.
Happy coding!
Kelson
--
Kiwix - Wikipedia Offline & more
* Web: https://kiwix.org/
* Twitter: https://twitter.com/KiwixOffline
* Wiki: https://wiki.kiwix.org/