Hello everyone,
can I ask you if you are currently using IA Upload tool
with IA books that *do not* have a Djvu file?
It's few weeks I'm trying to upload this book
https://archive.org/details/ComeRuinareLAutoritaImage
with the tool, and in theory the IA-upload can now make the djvu by
himself,
but in this case it's not working.
But maybe it's just this book.
Did you have any issues?
Andrea
Hi all,
I've recently started working on the Community Tech team
https://meta.wikimedia.org/wiki/Community_Tech at the Wikimedia
Foundation. So I just wanted to say hi and that I'm really excited to be
able to work on Wikimedia code full-time! :-)
Community Tech is all about helping build tools that support
contributors, and basically takes its work-list from the annual
Community Wishlist Survey:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
For the last couple of weeks I've been working on a tool to bring better
OCR to indic-language Wikisources, via Google's Cloud Vision API:
https://wikisource.org/wiki/Wikisource:Google_OCR
I'm not at all exclusively working on Wiksource stuff of course, not by
a long shot. But that's still where my personal interest lies, and so if
anyone's got any ideas about future software development that we need
then I'm keen to help if I can. And this year's Wishlist Survey will be
happening before too long, so get ready to list stuff there!
Lastly, please be gentle with me as I try to figure out how to shift to
life not-as-a-volunteer! (Although I'm still a volunteer too.) I'm
trying very hard to be transparent and professional and not blur the
various roles.... gets confusing though! :-)
Thanks,
Sam.
--
[[User:Samwilson]]
[[User:SWilson (WMF)]]
I guess that both into larger and into smaller wikisource projects there
are plentiful of clever templates, modules and javascript tools, developed
by users for practical goals.
Please take a little bit of time and import them into mul.source and
la.source - the latter being something like a second "multi-language
wikisource". IMHO we need to share our best ideas and tricks, and both
mul,source and la.source could be good showcases for them.
Alex brollo
Hi all,
together with Andrea (User:Aubrey), Bodhisattwa (User:Bodhisattwa) and
Jayanta (User:Jayantanth) we have put together a page about the
"Wikisource Anniversary Proofreading Contest" (WAPC). If I recall
correctly, the first WAPC was organised for the first time 3 years ago
in November in occasion of the 10th anniversary of Wikisource.
You can find more info about WAPCs on Meta:
https://meta.wikimedia.org/wiki/Wikisource_anniversary_proofreading_contest
there you can find some tips on how to run a WAPC in your local Wikisource.
We have also put together a set of tools on GitHub - under the
umbrella of a new "organisation" called `wscontest` - here they are:
https://github.com/wscontest/
you can find the repos for some tools
* the votecounter script, to count the points for each contestant;
* the ranking script, to designate the winner (who has the most
points) and to draw the second and third-place winners;
These tools are also available on Tool Labs under the `wscontest`:
https://tools.wmflabs.org/wscontest/
The documentation, at least for the votecounter script, is quite
extensive and I think that with this tools it would be possible to run
a contest in your local Wikisource, provided that you find someone
with Tool Labs access which can help with running the scripts.
However, it would be very nice if we could write a nice front-end for
everything so that organizing a contest. counting votes, and
establishing the winner, so that it becomes easy and can be done by
any community without technical support. Basically, we would need to
design and code some front-end:
* a page where you create a contest and upload a book list and define
the parameters of the contest: starting and ending date, how points
are awarded, etc.;
* a page where you launch the votecount script and collect the results;
* a page where you launch the ranking script and get the winners
posted on Wikisource;
It would also be very nice if we could add some authentication with
Wikimedia/Wikisource credentials.
I would like to see if we can gather some interest and help for coding
this idea. Alas, I have little time myself to code what is needed, but
Jayanta can also help and we already have a small team. You can also
put your name on meta here:
https://meta.wikimedia.org/wiki/Wikisource_anniversary_proofreading_contest…
Ciao,
C
I am very grateful to Aubrey!! :-)
Although, Aubrey, I think you have the wrong word there! ;-) Surely I
must not "pretend" but to actually and properly seek feedback?! ;-)
Which indeed, we shall all do I think.
So, how best to do that? Wikisource communities are small, but I think
we're actually more united in some ways than in other projects. But I
still think there's a fair bit of dispersion of conversations — I think
most people know about their local Scriptorium (or Bar, Cafe, Warung
kopi, or Тековни настани as the case may be), but there are lots of
contributors who aren't on this mailing list, or don't know about
Phabricator, or don't use IRC.
This issue is pertinent:
T144074 Improve the representation of Wikimedia communities beyond
English Wikipedia in the Community Wishlist Survey 2016[1]
So, anyway, thank you everyone for your welcomes. I just hope I can live
up to it all. :-)
Thanks,
Sam.
On Mon, 19 Sep 2016, at 09:03 PM, Andrea Zanni wrote:
> This is *fantastic* news!
> I'm really happy for Sam and I think this will bring a lot of good
> things for our community.
>
> Of course I don't want to take any credit, but I think it's important
> to remember that:
> * I talked with Ryan Kaldari and Danny Horn (of Community Tech) a lot
> in Berlin. Johann (also CT) was in Wien e we all met him:
> * they told me they were in need of another person in the team, and
> would have liked a Wikisource person too
> * they were very impressed by the response that came from Wikisource
> community during the Community Survey
>
> In the end, all this advocacy and commitment from the community (plus
> the crucial fact that Sam is awesome) paid off: I think we should all
> be proud of this.
>
> Having a person like Sam inside the WMF is special and crucial.
> He will not of course work just for Wikisource, but we have a real
> chance, as a community, to have a fruitful and rich conversation and
> communication between the community and the team, and we must not
> waste that.
>
> Sam ***must pretend*** a thorough feedback from us as a community,
> when he works on Wikisource stuff.
> We can collaborate to put our requests and feedbacks in the right
> places, and make sure that crucial problems are heard by the "top".
> So, it's a lot of work from us :-)
> We really need to to waste this opportunity.
>
> Aubrey
>
> On Mon, Sep 19, 2016 at 4:22 AM, Sam Wilson
> <sam(a)samwilson.id.au> wrote:
>> Yes, I hope so too!! :-)
>>
>> Maybe we should create a column on the Wikisource board on which
>> to put
>> wishlist items? https://phabricator.wikimedia.org/project/view/1117/
>>
>>
>> Oh, and for anyone who missed it, there's a great interview with tpt
>> here:
>> https://blog.wikimedia.de/2016/09/08/i-dont-have-to-find-tasks-tasks-are-co…
>>
>>
>>
>> On Fri, 16 Sep 2016, at 03:22 PM, Thomas Tanon wrote:
>> > Hello Sam,
>> >
>> > Congratulations! That's amazing! I really hope you will be able to
>> > keep
>> > making the Wikisource tech backlog lower [1].
>> >
>> > Congrats again,
>> >
>> > Thomas
>> >
>> > [1] https://phabricator.wikimedia.org/tag/wikisource/
>> >
>> >
>> > > Le 16 sept. 2016 à 05:23, Sam Wilson <sam(a)samwilson.id.au> a
>> > > écrit :
>> > >
>> > > Hi all,
>> > >
>> > > I've recently started working on the Community Tech team
>> > > https://meta.wikimedia.org/wiki/Community_Tech at the Wikimedia
>> > > Foundation. So I just wanted to say hi and that I'm really
>> > > excited to be
>> > > able to work on Wikimedia code full-time! :-)
>> > >
>> > > Community Tech is all about helping build tools that support
>> > > contributors, and basically takes its work-list from the annual
>> > > Community Wishlist Survey:
>> > > https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
>> > >
>> > > For the last couple of weeks I've been working on a tool to
>> > > bring better
>> > > OCR to indic-language Wikisources, via Google's Cloud Vision
>> > > API:
>> > > https://wikisource.org/wiki/Wikisource:Google_OCR
>> > >
>> > > I'm not at all exclusively working on Wiksource stuff of course,
>> > > not by
>> > > a long shot. But that's still where my personal interest lies,
>> > > and so if
>> > > anyone's got any ideas about future software development that we
>> > > need
>> > > then I'm keen to help if I can. And this year's Wishlist Survey
>> > > will be
>> > > happening before too long, so get ready to list stuff there!
>> > >
>> > > Lastly, please be gentle with me as I try to figure out how to
>> > > shift to
>> > > life not-as-a-volunteer! (Although I'm still a volunteer too.)
>> > > I'm
>> > > trying very hard to be transparent and professional and not blur
>> > > the
>> > > various roles.... gets confusing though! :-)
>> > >
>> > > Thanks,
>> > > Sam.
>> > >
>> > > --
>> > > [[User:Samwilson]]
>> > > [[User:SWilson (WMF)]]
>> > >
>> > > _______________________________________________
>> > > Wikisource-l mailing list
>> > > Wikisource-l(a)lists.wikimedia.org
>> > > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> >
>> > _______________________________________________
>> > Wikisource-l mailing list
>> > Wikisource-l(a)lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> > Email had 1 attachment:
>> > + signature.asc
>> > 1k (application/pgp-signature)
>>
>>
>> _______________________________________________
>> Wikisource-l mailing list
>> Wikisource-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> _________________________________________________
> Wikisource-l mailing list
> Wikisource-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Links:
1. https://phabricator.wikimedia.org/T144074
Hello all,
We've just published the September 2016 Indic Wikisource statistics. After
implementing Google OCR script to our all Indic Wikisource , they are
growing rapidly.
Here is the few stats...
As per Number of article
1. Sanskrit Wikisourece ( 14606 pages) - supported by 0.05% scan pages.
2. Telugu Wikisource ( 11707 pages) - supported by 24.3% scan pages.
3. Kannada Wikisource ( 7452 pages) - supported by 1.05% scan pages.
As per Number of page Validation
1. Telugu Wikisource ( 17783 pages)
2. Tamil Wikisource ( 4928 pages)
3. Bengali Wikisource ( 1591 pages)
As per Number of page Proofread
1. Telugu Wikisource ( 19378 pages)
2. Malayalam Wikisource ( 7962 pages)
3. Tamil Wikisource ( 6462 pages)
As per percentage supported by scan pages.
1. Telugu Wikisource ( 24.3%)
2. Bengali Wikisource (20.12%)
3. Malayalam Wikisource (10.93%)
Full Indic Wikisource stats here
https://wikisource.org/wiki/Wikisource:Indic_Wikisource_Stats
Regards,
Jayanta Nath
Indic Wikisource Community