[Wikisource-l] Re: Google not indexing Wikisource for last few years now.
Hi all, for what I've read, it suffices to generate a sitemap file with MediaWiki and how to submit it to Google. There is a script for that: generateSitemap.php. Once done, the sitemap has to be updated regularly in order to include the new pages. If it is more complicated, I hope that in Singapore, directly speaking to people, can solve the matter. Cheers, A. *Ruthven* on Wikipedia On Tue, 1 Aug 2023 at 12:03, Sohom Datta wrote: > For everyone : >> > Plus, the problem is not *better* indexing (that would be great of >> course), the problem here is that a lot (if not most) Wikisource pages are >> *not* indexed! >> If you type "when men went up in balloons" or "The banners rustle in the >> breeze" in Google (taken from the previous examples), Wikisource doesn't >> appear at all (and for other examples, when it does, it's incomplete and >> with a long delay of - at least - several months, the first example was >> done last week, the second was created in February!). >> That's why some of us suspect something is wrong somewhere (maybe because >> of the proofread extension ? and that Google doesn't "see" our pages. > > I've tested a bunch of non-indexed pages (some of which are from 2011) > across multiple Wikisources, it shows up as "URL is available to Google'' > (indicating that Googlebot can see the page). I am pretty sure that there > is no issue wrt to this specific thing on ProofreadPage/Wikisource > extension's side (there could be one on Google's end?) > > More gadget you use, more unreadable is the pages to the machines. > > > > Try to have a blind person reading the Wikisource pages with their own >> tools. Will it be difficult for them? Found the problem. > > > > You want to create pages which are more user friendly? But you do it for >> people having eyes. Machines doesn't have eyes. > > I agree with this on principle, but Wikisource pages are by default > readable without any javascript. And testing with Google bot (on the search > console) shows that it is able to read the associated content. > > I think this is a good opportunity to discuss with Google's Search Team >> here in Singapore in 2 weeks time. > > This would definitely be great :) > > Regards, > Sohom Datta > --- > Open-source contributor @Wikimedia > > > On Tue, Aug 1, 2023 at 3:18 PM Nicolas VIGNERON < > vigneron.nico...@gmail.com> wrote: > >> Thanks Ilario, >> That's very good general advice but would you have more concrete and >> specific ones? >> For instance, what would you change on >> https://en.wikisource.org/wiki/Baltimore_American/Volume_192/Issue_34,925/Travel_by_Balloon >> or >> https://en.wikisource.org/wiki/The_Poetical_Works_of_William_Motherwell/The_Crusader%27s_Farewell >> ? >> >> For everyone : >> Plus, the problem is not *better* indexing (that would be great of >> course), the problem here is that a lot (if not most) Wikisource pages are >> *not* indexed! >> If you type "when men went up in balloons" or "The banners rustle in the >> breeze" in Google (taken from the previous examples), Wikisource doesn't >> appear at all (and for other examples, when it does, it's incomplete and >> with a long delay of - at least - several months, the first example was >> done last week, the second was created in February!). >> That's why some of us suspect something is wrong somewhere (maybe because >> of the proofread extension ? and that Google doesn't "see" our pages. >> >> Cheers, >> Nicolas >> >> Le mar. 1 août 2023 à 11:24, Ilario valdelli a >> écrit : >> >>> To better index, you must follow as much as possible structured page. >>> >>> More gadget you use, more unreadable is the pages to the machines. >>> >>> Try to have a blind person reading the Wikisource pages with their own >>> tools. Will it be difficult for them? Found the problem. >>> >>> You want to create pages which are more user friendly? But you do it for >>> people having eyes. Machines doesn't have eyes. >>> >>> KInd regards >>> >>> On 01/08/2023 08:47, Bodhisattwa wrote: >>> > Hello all, >>> > >>> > Apologies for cross-posting. >>> > >>> > For those who have not noticed till now, Google is not indexing any >>> > Wikisource language editions for the last couple of years which >>> > practically means that any Wikisource contents in any languages, which >>> > are being created in these years, are not searchable on Google and >>
[Wikisource-l] asking grants to improve WS: WMI is funding some of our projects
Hi guys, during the Wikisource triage meetings we discussed the opportunity of using Foundation and Chapter grants in order to improve the project (focusing on the ProofreadPage extension), instead of waiting for the Annual Wishlist or hoping for some computer scientist user with a lot of good will. Other User Groups regularly ask for grants with success, even if the activities do not directly improve the projects. We were lucky because WMI (Wikimedia Italy) funded two grants we requested. We asked for grants for developers on very punctual tasks. Sohom is adapting theEdit-in-sequence gadget, used in some projects, to have it natively in the ProofreadPage extension. Jay is upgrading the BookReader (currently, this tool is limited to the Indic Wikisource community) so that other global Wikisource communities can also use it. Sam is supervising in his work hours the two projects. Here's the link to the WMI announcement: https://www.wikimedia.it/news/sostenere-le-idee-dei-volontari-per-liberare-conoscenza/ Let's hope that we can pursue this course of action in the future, in order to have efficient and up-to-date projects. Check with your local chapter if there are grants available for developers, and join us in the Triage meetings! Cheers, Alex *Ruthven* on Wikipedia ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: International copyright and wikisource
Hi all, yes, the consensus was not to delete no-URAA files only on the basis of US law. But there is an ongoing discussion about reverting this decision apparently: https://commons.wikimedia.org/wiki/Commons_talk:WikiProject_Public_Domain/URAA_review#Starting_the_review I recommend to participate, in order to fix a consensus. A. *Ruthven* on Wikipedia On Fri, 3 Jun 2022 at 01:32, J Hayes wrote: > According to Joyce foundation “all works published during his lifetime are > in the public domain” [in the EU, UK and Ireland. ] > > https://joycefoundation.utulsa.edu/joyce-copyright/joyce-works-copyright-public-domain/ > > apparently this is a URAA item > https://commons.wikimedia.org/wiki/Commons:URAA-restored_copyrights > > i do not see that it has ever been deleted on commons. > > however "*YES. URAA cannot be used as the sole reason for deletion."* > > https://commons.wikimedia.org/wiki/Commons:Massive_restoration_of_deleted_images_by_the_URAA > > here it is a internet archive > https://archive.org/details/in.ernet.dli.2015.463592/page/n3/mode/2up > > so a bold individual, might well defy precautionary principle and upload > expect a deletion nomination in response. > > jim hayes > > On Thu, Jun 2, 2022 at 10:03 AM Nicolas VIGNERON < > vigneron.nico...@gmail.com> wrote: > >> Hi, >> >> Some explanations/clarifications here : >> - applicable law is a millennia old unsolved nightmare, but to make it >> short, both US and local laws are applicable on Wikimedia Commons. >> - when you say "Finnegans Wake by James Joyce", what are you talking >> about exactly? There are a lot of editions, with a lot of >> corresponding copyright (and I would say that some - if not most - of >> them are already public domain in both the local country and US). Who >> is the translator? What is the publication date in the US? Was there a >> copyright notice? >> - "internet barrier" is indeed not possible (hence my first point) >> - "a German subsidiary legal entity" (or any/all other countries) has >> already been discussed many times, in the end it's just not feasible >> (see previous point) nor realistic (US law is probably still >> applicable anyway). >> >> PS: in any case, it will clearly be public domain in the US in 2035, >> which is quite soon (we have files marked to undelete as far as 2160 >> on Commons/Wikisource ;) ) and there is a lot more other work to >> transcribe on Wikisource meanwhile. >> >> Cheers, >> Nicolas >> >> >> >> Le mer. 1 juin 2022 à 21:56, J Hayes a écrit : >> > >> > Yes, there was a wikilivres project in Canada (pma +50) but it fizzled >> out. >> > There have also been attempts to have a local EDP or “fair use” of the >> lesser term, but that would be up to the local wikisource community. >> (English has resisted this) >> > Other institutions have transcription efforts not constrained by >> commons copyright rules. For example, transcribed si.org >> > Sorry about that >> > Jim hayes >> > >> > On Wed, Jun 1, 2022 at 10:05 AM Julius Hamilton < >> juliushamilton...@gmail.com> wrote: >> >> >> >> Hey, >> >> >> >> From what I understand WikiSource’s servers are located in the US and >> must therefore follow US Copyright. >> >> >> >> I would like a much deeper understanding of how copyright is upheld >> online since it’s so easy to access “foreign” websites, of course. >> >> >> >> I would like to upload a book - Finnegans Wake by James Joyce - to >> WikiSource. It’s out of copyright in Europe but on the US, because they >> have different copyright lengths. >> >> >> >> If we assume US copyright law applying to servers physically located >> in the US, that much makes sense. But is there a law that people in the US >> cannot access those same materials on foreign servers where they are not >> copyrighted? If that’s actually a law, how do they enforce that? They would >> need to stick up some kind of internet barrier, internet censorship. Is >> that legal? How could they achieve it? Wouldn’t they basically have to get >> internet service providers to block a certain domain or something? So… the >> government would say, “We heard foreign site X is serving copyrighted >> material to American citizens; block that site for all Americans”? And then >> the foreign site would respond (to get unblocked) by checking the location >> of whoever’s requesting their webpage and probably specifically limit >> content dep
[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment
Hi all, and thanks for the info. I get from your messages that there are two major points to be solved: 1. A clear lack of communication (mass messages are often unread or quickly read, because there is some abuse of the tool, and what is important gets lost in the flood of messages). Probably it's not the role of developers to communicate, but someone has to do it. 2. A clear lack of management. There is a global lack of trust in Mediawiki developers for the reason above, but also because certain changes introduced more issues than they solved. I agree with Sam: there is a need for product managers, who can also communicate about important changes, but also check the development and be sure that new changes can be safely deployed. I mean: it's the basics of software development! I don't think it's a matter of time if we focus on one feature at a time, test it, test it again, do beta test, and then merge it. We're not a software house: we do have time. I understand that volunteers might not be happy in being constrained by a strict workflow, but I also understand that work has to be done well or not done at all. Btw, I understand that there is beta.wikisource somewhere. Maybe an invitation to the different projects to test the new features there before the merge, would be a good occasion to involve more people in quality control. (sorry if this has been done, and I've missed it) Cheers, A. *Ruthven* on Wikipedia On Mon, 22 Nov 2021 at 04:45, Sam Wilson wrote: > I think most Wikisource developers are likely to be on this list. Of > course, it's best to make sure there are Phabricator tickets for every > separate bug or feature request. > On 21/11/21 1:36 am, Ankry 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 -- wikisource-l@lists.wikimedia.org > To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org > > > ___ > Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org > To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org > > ___ > Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org > To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org > ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment
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 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 -- wikisource-l@lists.wikimedia.org > To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org > > ___ > Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org > To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org > ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] MediaWiki, Wikisource extensions, and new implementations deployment
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 -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Round table at Wikimania 2021
Hi all, I've submitted a live round table at Wikimania. Check it out: https://pretalx.com/individuals-collectives-session-submission-2021/talk/review/BYH9T7SHBWCLUMNXKWQYF3GALKV9WHLQ It will be the occasion to discuss with Sam Wilson about the OCR improvements, and its testing. Possibly Natalia Rodriguez, Product Manager at Community Tech, will illustrate us the improvements they have in mind. I hope that we will use this occasion to make progress on the technical side! Cheers, Alex *Ruthven* on Wikipedia ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
Re: [Wikisource-l] Wikisource at the Wikimedia Summit 2020
Hi all, Unfortunately I'm not available tomorrow at 1pm. Good luck, I'll check on the etherpad. Cheers, *Ruthven* on Wikipedia On Fri, 13 Dec 2019 at 12:06, Mardetanha wrote: > Good, i will do my best to join you. > > On Fri, Dec 13, 2019 at 1:51 PM Nicolas VIGNERON < > vigneron.nico...@gmail.com> wrote: > >> Hi all, >> >> So according to the framadate (https://framadate.org/DWcnhfcsWQRjFKhP) >> we have equality for Saturday and Sunday but Mohsen didn't vote and said he >> preferred Saturday (IIRC). >> If there is no objection, then the meeting is tomorrow Saturday at 13:00 >> (1 pm) UTC (time conversion: >> https://www.timeanddate.com/worldclock/converter.html?iso=20191214T13=195=176=263 >> ). >> >> The meeting will be at this URL: https://meet.jit.si/WCUG (just click >> the link, no account needed ; you may get a "Browser warning" but most of >> the time it's relevant, the Jitsi devs are tweaking things right now >> apparently). >> We will take notes on this pad: https://etherpad.wikimedia.org/p/WCUG >> (I already included the four questions about Movement Strategy, is that >> the "essay" you are talking about Jim? ping @Bodhisattwa and @Mohsen as you >> two are in Strategy working groups your input would be valuable, feel free >> to comment in the pad before the meeting ;) ). >> >> See you tomorrow! >> >> Cheers, ~nicolas >> >> >> Le mar. 10 déc. 2019 à 20:23, J Hayes a écrit : >> >>> Yes, I concur. >>> I am concerned that the conference will be used to rubber stamp >>> strategic plan. >>> There is some unrest among other affiliates, that they are not feeling >>> the resource support from WMF. And that WMF does not collaborate well with >>> others. >>> (Which goes unmentioned in strategic plan) >>> also you may need to don your "corporate speak" hat in the essay >>> responses to get invited. >>> >>> Cdmt, slowking >>> >>> On Tue, Dec 10, 2019, 1:08 PM Bodhisattwa Mandal < >>> bodhisattwa.rg...@gmail.com> wrote: >>> >>>> Hi Nicolas, >>>> >>>> In this summit, we need an experienced Wikisourcer who can strongly >>>> advocate for the project, so that the project and it's communities does not >>>> get left behind or forgotten during the implementation phase of strategy. >>>> This year, we need to send someone who can opine in the implementation >>>> discussion in such a way, that it is at least ensured on paper, that >>>> Wikisource will get the support it deserves. It is also needed to >>>> strategize for Wikisource for future w.r.t. knowledge equity. >>>> >>>> Personally I think, you are one of the best persons, we have, to >>>> represent the entire community and if you decide to go, you have my very >>>> strong support. >>>> >>>> Regards, >>>> Bodhisattwa >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Tue, 10 Dec 2019, 19:37 balaji, wrote: >>>> >>>>> Hi, >>>>> Thanks Vigneron for starting this up for timely discussion. We need to >>>>> discuss how and what to present about our group in the conference. We need >>>>> to take into account about experience, opportunity for people, full >>>>> availability for the conference.(Not like the same person representing >>>>> wikisource also doing other activities in conference), etc while selecting >>>>> the people. >>>>> >>>>> p.s. This year I wont be able to travel during that time. So i am not >>>>> a candidate. >>>>> >>>>> Regards, >>>>> Balaji. >>>>> >>>>> On Tue, Dec 10, 2019 at 6:12 PM Nicolas VIGNERON < >>>>> vigneron.nico...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> According to the reports : >>>>>> - 2014 : Micru and Aubrey >>>>>> - 2015 : Micru and Aubrey >>>>>> - 2016 and 2017 : Aubrey >>>>>> - 2018 : Balajijagadesh and VIGNERON >>>>>> - 2019 : Gurlal Maan >>>>>> >>>>>> @Mardetanha and the others: is Friday or Saturday better for you? >>>>>> I started a poll to find the best day: >>>>>> https://framadate.org/DWcnhfcsWQRjFKhP (feel free to comment)
Re: [Wikisource-l] Deployment of the Wikisource extension
Thanks Thomas, a good news and a great job! I already started applying it to it.source; e.g. https://it.wikisource.org/wiki/Orlando_furioso Cheers! *Ruthven* on Wikipedia On Thu, 12 Dec 2019 at 22:29, Thomas Pellissier Tanon < tho...@pellissier-tanon.fr> wrote: > Hi all, > > The "Wikisource" MediaWiki extension has just been enabled on all > Wikisources. For now, this extension contains only the piece of code > allowing to fill the "In other projects" navigation section based on > the Wikidata "edition of" (P629) property. In the future this > extension aims to store code customizing MediaWiki shared by all > Wikisources. > > This is the first step to solve the "Inter-language link support via > Wikidata" wish that arrived 4th in the Community Wishlist survey. [2]. > > A working example is available on the English Wikisource [3]. You > could see that on this page there is a "Wikipedia" link in the "In > other projects" sidebar. This link does not come from the wikitext > code of the page, and not from the Wikidata item connected to the page > (Q15854278) either but from the Wikidata item Q936276 that is the > "work" entity of "The Wind in the Willows". The property "edition of" > (P629) connects the "edition" Wikidata item (connected to the > Wikisource page) to the "work" item. It is this property that the > Wikisource extension is using to find a link to Wikipedia to display > in the "In other projects" sidebar if the Wikidata item connected to > the page (here the "edition" item) does not provide a link to > Wikipedia. > > This, of course, works not only for Wikipedia but for all the sister > projects displayed in the sidebar (Commons, Wikiquote...). > > Cheers, > > Thomas > > [1] https://phabricator.wikimedia.org/T180303 > [2] > https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource/Inter-language_link_support_via_Wikidata > [3] https://en.wikisource.org/wiki/The_Wind_in_the_Willows_(1913) > > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Wikisource at the Wikimedia Summit 2020
Hi all, I am available this week (evening hours CET) and on Sunday. Even if I personally have some recommendations feedback on the creation process of new Wikisource projects, it would be cool if we can agree on some priorities to push on for the Wikimedia Strategy. Cheers, Alex *Ruthven* on Wikipedia On Tue, 10 Dec 2019 at 11:32, Thomas Pellissier Tanon < tho...@pellissier-tanon.fr> wrote: > Thank you Nicolas for taking care of this. > > It would be great to have someone at the Wikimedia Summit advocating > for Wikisource. > > I'm interested to attend the meeting this week if it could help to > choose representative. I'm available most of the week in CET timezone. > > I am already attending a lot of Wikimedia events and I'm not the best > speaker, so I'm not candidate to attend the Wikimedia Summit either. > > Cheers, > > Thomas > > > Le mar. 10 déc. 2019 à 10:46, Mardetanha a > écrit : > > > > This is a very good idea, do we know how many people are interested? if > you are interested please put your name here that we can discuss, (I am > personally not a candidate this year) > > > > Mardetanha > > > > > > On Tue, Dec 10, 2019 at 11:53 AM Nicolas VIGNERON < > vigneron.nico...@gmail.com> wrote: > >> > >> Hi all, > >> > >> This year again, we need to select the representative of the Wikisource > Community User Group to the Wikimedia Summit 2020. This year summit is even > more focused on strategy and the deadline is December 16. > >> > >> There was some issues with last year process (as pointed by Gurlal > report) and time is short, so I think the best would be an online meeting > sometimes this week (when ?). > >> Who is interested and available ? (both for the meeting but also to go > to Berlin). > >> > >> Cheers, > >> Nicolas > >> ___ > >> Wikisource-l mailing list > >> Wikisource-l@lists.wikimedia.org > >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l > > > > ___ > > Wikisource-l mailing list > > Wikisource-l@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
