Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)

—sam

On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

Hi Thomas, thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is: https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... Cheers, Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT thomaspt@hotmail.fr wrote:

...

Hello everyone,

The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support.

Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support).

Cheers,

Thomas

...

Début du message réexpédié :

*De: *Johan Jönsson jjonsson@wikimedia.org *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* *Date: *7 novembre 2016 à 20:26:21 UTC+1 *À: *Wikitech Ambassadors wikitech-ambassadors@lists.wikimedia.org *Répondre à: *Coordination of technology deployments across languages/projects wikitech-ambassadors@lists.wikimedia.org

Hi everyone,

Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers, been the focus of Wikimedia hackathons and so on. In short, I think it matters.

Now we're doing the process again.

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

If you'd feel like spreading this in your communities, it would be much appreciated.

*) This is when you can suggest things. This phase will last from 7 November to 20 November. *) Editors who are not comfortable writing in English can write proposals in their language. *) Voting will take place 28 November to 12 December.

Thanks,

//Johan Jönsson

---

Wikitech-ambassadors mailing list Wikitech-ambassadors@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

-- Etiamsi omnes, ego non _________________________________________________ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Thanks Alex :) It's a minor project so far, but I reckon the work you've been doing on making a better, bigger, more proofreading-focused interface is really good. Do stick a proposal up!

So far, we've got:

* Add a 'clean' method for side-titles, and side notes to parser * A spelling- and typo-checking system for proofreading * Visual Editor menu refresh * upload text wizard * Language links in Wikisource for edition items in Wikidata * Display subpage name in category * Make Special:IndexPage transcludeable * Fix Extension:Cite to get rid of foibles

If anyone's got half-formed ideas, I'd encourage you to post something, or just post to this mailing list, and we can all have a chat about it. :)

—sam

On Wed, 9 Nov 2016, at 04:50 PM, Alex Brollo wrote:

I too could add *some* proposals.... but the first one could be a deep revision of nsPage edit interface to got the goal "fixed tools, almost full screen scrolling text & image". In the meantime, I'm go on testing FullScreenEditing.js by Sam, that presently is an excellent, running  step approximating such a goal.

Alex

2016-11-09 1:03 GMT+01:00 Sam Wilson sam@samwilson.id.au:

...

__ Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)

—sam

On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

...

Hi Thomas, thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is: https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... Cheers, Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT thomaspt@hotmail.fr wrote:

...

Hello everyone,

The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support.

Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support).

Cheers,

Thomas

...

Début du message réexpédié :

*De: *Johan Jönsson jjonsson@wikimedia.org *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* *Date: *7 novembre 2016 à 20:26:21 UTC+1 *À: *Wikitech Ambassadors wikitech-ambassadors@lists.wikimedia.org *Répondre à: *Coordination of technology deployments across languages/projects wikitech-ambassadors@lists.wikimedia.org

Hi everyone,

Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers,

been the focus of Wikimedia hackathons and so on. In short, I think it matters.

...

...

...

...

Now we're doing the process again.

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

If you'd feel like spreading this in your communities, it would be much appreciated.

*) This is when you can suggest things. This phase will last from 7 November to 20 November.  *) Editors who are not comfortable writing in English can write proposals in their language. *) Voting will take place 28 November to 12 December.

Thanks,

//Johan Jönsson

---

Wikitech-ambassadors mailing list Wikitech-ambassadors@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

-- Etiamsi omnes, ego non _________________________________________________ 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

Hmm, at the conference I think someone was interested in a feature to make comments on texts, like you can make on some word processors for example. That may be interesting, but how you render the result might be a huge user interface problem. One should be able to choose whom comments should be visible…

Otherwise, I would still be happy to have more flexibable way to "rate" a page. That is, a page might be text proof readed, but laking some css, or a picture should be extracted etc. Having a way to see that for all pages in the book: namespace would be fine.

ĝis baldaŭ

Le 10/11/2016 à 06:09, Sam Wilson a écrit :

Thanks Alex :) It's a minor project so far, but I reckon the work you've been doing on making a better, bigger, more proofreading-focused interface is really good. Do stick a proposal up!

So far, we've got:

• Add a 'clean' method for side-titles, and side notes to parser
• A spelling- and typo-checking system for proofreading
• Visual Editor menu refresh
• upload text wizard
• Language links in Wikisource for edition items in Wikidata
• Display subpage name in category
• Make Special:IndexPage transcludeable
• Fix Extension:Cite to get rid of foibles

If anyone's got half-formed ideas, I'd encourage you to post something, or just post to this mailing list, and we can all have a chat about it. :)

—sam

On Wed, 9 Nov 2016, at 04:50 PM, Alex Brollo wrote:

...

I too could add *some* proposals.... but the first one could be a deep revision of nsPage edit interface to got the goal "fixed tools, almost full screen scrolling text & image". In the meantime, I'm go on testing FullScreenEditing.js by Sam, that presently is an excellent, running step approximating such a goal.

Alex

2016-11-09 1:03 GMT+01:00 Sam Wilson sam@samwilson.id.au:

...

__ Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)

—sam

On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

...

Hi Thomas, thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is: https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... Cheers, Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT thomaspt@hotmail.fr wrote:

...

Hello everyone,

The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support.

Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support).

Cheers,

Thomas

...

Début du message réexpédié :

*De: *Johan Jönsson jjonsson@wikimedia.org *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* *Date: *7 novembre 2016 à 20:26:21 UTC+1 *À: *Wikitech Ambassadors wikitech-ambassadors@lists.wikimedia.org *Répondre à: *Coordination of technology deployments across languages/projects wikitech-ambassadors@lists.wikimedia.org

Hi everyone,

Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers,

been the focus of Wikimedia hackathons and so on. In short, I think it matters.

...

...

...

...

...

Now we're doing the process again.

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

If you'd feel like spreading this in your communities, it would be much appreciated.

*) This is when you can suggest things. This phase will last from 7 November to 20 November. *) Editors who are not comfortable writing in English can write proposals in their language. *) Voting will take place 28 November to 12 December.

Thanks,

//Johan Jönsson

---

Wikitech-ambassadors mailing list Wikitech-ambassadors@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

-- Etiamsi omnes, ego non _________________________________________________ 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

I'd like to state a "binary page quality" splitting the workflow into its basic steps (proofreading of text; formatting; adding links; validating....), t.i. into a set of true/false states, clearly showing the list of lacking steps. I.e. sometimes I fastly add complex formatting to rough text, and this results into a exotic "level" proofreading=false, formatting=true. It's a level 1, but it is deeply different from a level 1 coming from proofreading=true, formatting=false.

Obviously the whole "binary level" could be simply stored as a number, with useful information into it.

Alex

2016-11-11 8:32 GMT+01:00 Sam Wilson sam@samwilson.id.au:

That sounds really interesting! Do you mean as a way for people unfamiliar with Wikisource to easily contribute notes and corrections? On the face of things, it could perhaps work by storing the notes in a the Page_talk namspace and doing some clever thing to display them on the Page (and perhaps in main) namespaces.

It seems like it'd be cool to be able to get "typo reports" or something, from people who mightn't have any idea of Wikisource other than that's where they got an epub.

To rate a page, we currently have the various levels of proofreading quality. Is this not sufficient? And does the current Index page overview of all of a book's statuses work for you? I sometimes wonder if we need another rating, above 'validated', that indicates that a whole book has been read through and (hopefully) any remaining typos have been found.

—sam

On Fri, 11 Nov 2016, at 12:27 AM, mathieu stumpf guntz wrote:

Hmm, at the conference I think someone was interested in a feature to make comments on texts, like you can make on some word processors for example. That may be interesting, but how you render the result might be a huge user interface problem. One should be able to choose whom comments should be visible…

Otherwise, I would still be happy to have more flexibable way to "rate" a page. That is, a page might be text proof readed, but laking some css, or a picture should be extracted etc. Having a way to see that for all pages in the book: namespace would be fine.

ĝis baldaŭ

Le 10/11/2016 à 06:09, Sam Wilson a écrit :

Thanks Alex :) It's a minor project so far, but I reckon the work you've been doing on making a better, bigger, more proofreading-focused interface is really good. Do stick a proposal up!

So far, we've got:

• Add a 'clean' method for side-titles, and side notes to parser
• A spelling- and typo-checking system for proofreading
• Visual Editor menu refresh
• upload text wizard
• Language links in Wikisource for edition items in Wikidata
• Display subpage name in category
• Make Special:IndexPage transcludeable
• Fix Extension:Cite to get rid of foibles

If anyone's got half-formed ideas, I'd encourage you to post something, or just post to this mailing list, and we can all have a chat about it. :)

—sam

On Wed, 9 Nov 2016, at 04:50 PM, Alex Brollo wrote:

I too could add *some* proposals.... but the first one could be a deep revision of nsPage edit interface to got the goal "fixed tools, almost full screen scrolling text & image". In the meantime, I'm go on testing FullScreenEditing.js by Sam, that presently is an excellent, running step approximating such a goal.

Alex

2016-11-09 1:03 GMT+01:00 Sam Wilson sam@samwilson.id.au sam@samwilson.id.au:

__ Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)

—sam

On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

Hi Thomas, thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is:https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... Cheers, Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT thomaspt@hotmail.fr thomaspt@hotmail.fr wrote:

Hello everyone,

The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support.

Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support).

Cheers,

Thomas

Début du message réexpédié :

*De: *Johan Jönsson jjonsson@wikimedia.org jjonsson@wikimedia.org *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* *Date: *7 novembre 2016 à 20:26:21 UTC+1 *À: *Wikitech Ambassadors wikitech-ambassadors@lists.wikimedia.org wikitech-ambassadors@lists.wikimedia.org *Répondre à: *Coordination of technology deployments across languages/projects wikitech-ambassadors@lists.wikimedia.org wikitech-ambassadors@lists.wikimedia.org

Hi everyone,

Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers,

been the focus of Wikimedia hackathons and so on. In short, I think it matters.

Now we're doing the process again. https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

If you'd feel like spreading this in your communities, it would be much appreciated.

*) This is when you can suggest things. This phase will last from 7 November to 20 November. *) Editors who are not comfortable writing in English can write proposals in their language. *) Voting will take place 28 November to 12 December.

Thanks,

//Johan Jönsson

---

Wikitech-ambassadors mailing listWikitech-ambassadors@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

---

Wikisource-l mailing listWikisource-l@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikisource-l

-- Etiamsi omnes, ego non _________________________________________________ Wikisource-l mailing listWikisource-l@lists.wikimedia.orghttps://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 listWikisource-l@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikisource-l

---

Wikisource-l mailing listWikisource-l@lists.wikimedia.orghttps://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

.... coupled with a KISSing approach it could run perhaps.... :-)

Alex

2016-11-11 9:37 GMT+01:00 Sam Wilson sam@samwilson.id.au:

Yes, makes sense! Or a series of attributes like:

proofread once? proofread twice? formatted? all images added? hyperlinked? transcluded? read in context with other pages? etc.

Only some of which need be linear.

And only when all are done is the thing considered bonzer. :-)

—sam

On Fri, 11 Nov 2016, at 04:17 PM, Alex Brollo wrote:

I'd like to state a "binary page quality" splitting the workflow into its basic steps (proofreading of text; formatting; adding links; validating....), t.i. into a set of true/false states, clearly showing the list of lacking steps. I.e. sometimes I fastly add complex formatting to rough text, and this results into a exotic "level" proofreading=false, formatting=true. It's a level 1, but it is deeply different from a level 1 coming from proofreading=true, formatting=false. Obviously the whole "binary level" could be simply stored as a number, with useful information into it. Alex

2016-11-11 8:32 GMT+01:00 Sam Wilson sam@samwilson.id.au:

That sounds really interesting! Do you mean as a way for people unfamiliar with Wikisource to easily contribute notes and corrections? On the face of things, it could perhaps work by storing the notes in a the Page_talk namspace and doing some clever thing to display them on the Page (and perhaps in main) namespaces.

It seems like it'd be cool to be able to get "typo reports" or something, from people who mightn't have any idea of Wikisource other than that's where they got an epub.

To rate a page, we currently have the various levels of proofreading quality. Is this not sufficient? And does the current Index page overview of all of a book's statuses work for you? I sometimes wonder if we need another rating, above 'validated', that indicates that a whole book has been read through and (hopefully) any remaining typos have been found.

—sam

On Fri, 11 Nov 2016, at 12:27 AM, mathieu stumpf guntz wrote:

Hmm, at the conference I think someone was interested in a feature to make comments on texts, like you can make on some word processors for example. That may be interesting, but how you render the result might be a huge user interface problem. One should be able to choose whom comments should be visible…

Otherwise, I would still be happy to have more flexibable way to "rate" a page. That is, a page might be text proof readed, but laking some css, or a picture should be extracted etc. Having a way to see that for all pages in the book: namespace would be fine.

ĝis baldaŭ

Le 10/11/2016 à 06:09, Sam Wilson a écrit :

Thanks Alex :) It's a minor project so far, but I reckon the work you've been doing on making a better, bigger, more proofreading-focused interface is really good. Do stick a proposal up!

So far, we've got:

• Add a 'clean' method for side-titles, and side notes to parser
• A spelling- and typo-checking system for proofreading
• Visual Editor menu refresh
• upload text wizard
• Language links in Wikisource for edition items in Wikidata
• Display subpage name in category
• Make Special:IndexPage transcludeable
• Fix Extension:Cite to get rid of foibles

If anyone's got half-formed ideas, I'd encourage you to post something, or just post to this mailing list, and we can all have a chat about it. :)

—sam

On Wed, 9 Nov 2016, at 04:50 PM, Alex Brollo wrote:

I too could add *some* proposals.... but the first one could be a deep revision of nsPage edit interface to got the goal "fixed tools, almost full screen scrolling text & image". In the meantime, I'm go on testing FullScreenEditing.js by Sam, that presently is an excellent, running step approximating such a goal.

Alex

2016-11-09 1:03 GMT+01:00 Sam Wilson sam@samwilson.id.au sam@samwilson.id.au:

__ Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)

—sam

On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

Hi Thomas, thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is:https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... Cheers, Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT thomaspt@hotmail.fr thomaspt@hotmail.fr wrote:

Hello everyone,

The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support.

Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support).

Cheers,

Thomas

Début du message réexpédié :

*De: *Johan Jönsson jjonsson@wikimedia.org jjonsson@wikimedia.org *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* *Date: *7 novembre 2016 à 20:26:21 UTC+1 *À: *Wikitech Ambassadors wikitech-ambassadors@lists.wikimedia.org wikitech-ambassadors@lists.wikimedia.org *Répondre à: *Coordination of technology deployments across languages/projects wikitech-ambassadors@lists.wikimedia.org wikitech-ambassadors@lists.wikimedia.org

Hi everyone,

Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers,

been the focus of Wikimedia hackathons and so on. In short, I think it matters.

Now we're doing the process again. https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

If you'd feel like spreading this in your communities, it would be much appreciated.

*) This is when you can suggest things. This phase will last from 7 November to 20 November. *) Editors who are not comfortable writing in English can write proposals in their language. *) Voting will take place 28 November to 12 December.

Thanks,

//Johan Jönsson

---

Wikitech-ambassadors mailing listWikitech-ambassadors@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors

---

Wikisource-l mailing listWikisource-l@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikisource-l

-- Etiamsi omnes, ego non _________________________________________________ Wikisource-l mailing listWikisource-l@lists.wikimedia.orghttps://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 listWikisource-l@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikisource-l

---

Wikisource-l mailing listWikisource-l@lists.wikimedia.orghttps://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

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Yes, this is PGDP's approach. They have two rounds of proofreading-only, before any formatting of any sort is applied. The beginner proofreaders start without formatting.

When it comes to comparative text analysis, Wikisource makes things pretty hard, that's for sure. I mean, has anyone tried finding all the extra commas in a Jane Austen first edition vs a modern edition? (It's considerably different.) But not something we can do all that easily.

On Fri, 11 Nov 2016, at 05:00 PM, Andrea Zanni wrote:

I remember when we tried to make a partnership with a scholar who works with ancient texts. He needed some Italian translation of Greek texts in Wikisource, but he was much more interested in validated/proofread text *without* formatting, than the contrary. 75% for us is formatted, always. But, arguably, for people it's easier to correct typos and proofread than format with strange templates and codes. We always assume that people know how Wikisource works, how wikicode works, etc.

A brand new quality workflow could be beneficial.

Aubrey

On Fri, Nov 11, 2016 at 9:54 AM, Alex Brollo alex.brollo@gmail.com wrote:

...

.... coupled with a KISSing approach it could run perhaps.... :-) Alex

2016-11-11 9:37 GMT+01:00 Sam Wilson sam@samwilson.id.au:

...

__ Yes, makes sense! Or a series of attributes like:

proofread once? proofread twice? formatted? all images added? hyperlinked? transcluded? read in context with other pages? etc.

Only some of which need be linear.

And only when all are done is the thing considered bonzer. :-)

—sam

On Fri, 11 Nov 2016, at 04:17 PM, Alex Brollo wrote:

...

I'd like to state a "binary page quality" splitting the workflow into its basic steps (proofreading of text; formatting; adding links; validating....), t.i. into a set of true/false states, clearly showing the list of lacking steps. I.e. sometimes I fastly add complex formatting to rough text, and this results into a exotic "level" proofreading=false, formatting=true. It's a level 1, but it is deeply different from a level 1 coming from proofreading=true, formatting=false. Obviously the whole "binary level" could be simply stored as a number, with useful information into it. Alex

2016-11-11 8:32 GMT+01:00 Sam Wilson sam@samwilson.id.au:

...

__ That sounds really interesting! Do you mean as a way for people unfamiliar with Wikisource to easily contribute notes and corrections? On the face of things, it could perhaps work by storing the notes in a the Page_talk namspace and doing some clever thing to display them on the Page (and perhaps in main) namespaces.

It seems like it'd be cool to be able to get "typo reports" or something, from people who mightn't have any idea of Wikisource other than that's where they got an epub.

To rate a page, we currently have the various levels of proofreading quality. Is this not sufficient? And does the current Index page overview of all of a book's statuses work for you? I sometimes wonder if we need another rating, above 'validated', that indicates that a whole book has been read through and (hopefully) any remaining typos have been found.

—sam

On Fri, 11 Nov 2016, at 12:27 AM, mathieu stumpf guntz wrote:

...

Hmm, at the conference I think someone was interested in a feature to make comments on texts, like you can make on some word processors for example. That may be interesting, but how you render the result might be a huge user interface problem. One should be able to choose whom comments should be visible… Otherwise, I would still be happy to have more flexibable way to "rate" a page. That is, a page might be text proof readed, but laking some css, or a picture should be extracted etc. Having a way to see that for all pages in the book: namespace would be fine. ĝis baldaŭ

Le 10/11/2016 à 06:09, Sam Wilson a écrit : > Thanks Alex :) It's a minor project so far, but I reckon the > work you've been doing on making a better, bigger, more proofreading- > focused interface is really good. Do stick a proposal up! So > far, we've got: * Add a 'clean' method for side-titles, and > side notes to parser * A spelling- and typo-checking system for > proofreading * Visual Editor menu refresh * upload text wizard * > Language links in Wikisource for edition items in Wikidata * > Display subpage name in category * Make Special:IndexPage > transcludeable * Fix Extension:Cite to get rid of foibles If > anyone's got half-formed ideas, I'd encourage you to post > something, or just post to this mailing list, and we can all > have a chat about it. :) —sam On Wed, 9 Nov 2016, at 04:50 > PM, Alex Brollo wrote: > >> I too could add *some* proposals.... but the first one could be >> a deep revision of nsPage edit interface to got the goal "fixed >> tools, almost full screen scrolling text & image". In the >> meantime, I'm go on testing FullScreenEditing.js by Sam, that >> presently is an excellent, running step approximating such a >> goal. Alex 2016-11-09 1:03 GMT+01:00 Sam Wilson >> sam@samwilson.id.au: >> >>> __ Huzza for Wikisource; we've currently got more proposals >>> than any of the other categories (not that it's a competition, >>> but still...). @Micru: this whole topic of how to represent >>> bibliographic data in WD and properly link it in Wikisource is >>> great! I'm looking forward to helping. :-) —sam On Tue, 8 >>> Nov 2016, at 10:08 PM, David Cuenca Tudela wrote: >>> >>>> Hi Thomas, thanks for bringing that up! I wrote a proposal to >>>> finish the work retrieving the language links from several >>>> editions and represent them in wikisource as language links. >>>> To write or vote exiting Wikisource proposals, the link is: >>>> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... >>>> Cheers, Micru On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT >>>> thomaspt@hotmail.fr wrote: >>>> >>>>> Hello everyone, The Wikimedia Foundation Community Tech >>>>> team has launched a new "Community Wishlist Survey". Last >>>>> year survey allowed us to get WMF staff time to work on >>>>> using Google OCR in Wikisource that allowed some Indian >>>>> languages Wikisources to raise and on VisualEditor support. >>>>> Please, take time to submit new wishes and comment them. It >>>>> could be simple things (e.g. a new gadget for a specific >>>>> workflow) or very complicated ones (e.g. native TEI >>>>> support). Cheers, Thomas

...

...

...

...

...

>>>>> >>>>>> Début du message réexpédié : *De: *Johan Jönsson >>>>>> jjonsson@wikimedia.org *Objet: **[Wikitech-ambassadors] >>>>>> Your help needed: Community Wishlist Survey 2016* *Date: *7 >>>>>> novembre 2016 à 20:26:21 UTC+1 *À: *Wikitech Ambassadors >>>>>> wikitech-ambassadors@lists.wikimedia.org *Répondre à: >>>>>> *Coordination of technology deployments across >>>>>> languages/projects <wikitech- >>>>>> ambassadors@lists.wikimedia.org> Hi everyone, Last year, >>>>>> the Community Tech team did a survey for a community >>>>>> wishlist to decide what we shoudl be working on throughout >>>>>> the year. Since it's useful to have a list of tasks from >>>>>> the Wikimedia communities, it's also been used by other >>>>>> developers, >>>>>> > been the focus of Wikimedia hackathons and so on. In short, I > think it matters. > >>>>>> Now we're doing the process again.

...

...

...

...

...

>>>>>> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey >>>>>> If you'd feel like spreading this in your communities, it >>>>>> would be much appreciated. *) This is when you can suggest >>>>>> things. This phase will last from 7 November to 20 >>>>>> November. *) Editors who are not comfortable writing in >>>>>> English can write proposals in their language. *) Voting >>>>>> will take place 28 November to 12 December. Thanks, >>>>>> //Johan Jönsson -- >>>>>> _______________________________________________ Wikitech- >>>>>> ambassadors mailing list Wikitech- >>>>>> ambassadors@lists.wikimedia.org >>>>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors >>>>>> >>>>> _______________________________________________ Wikisource-l >>>>> mailing list Wikisource-l@lists.wikimedia.org >>>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

...

...

...

...

...

>>>>> >>>> -- Etiamsi omnes, ego non >>>> _________________________________________________ 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 >

---

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

---

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

Le 11/11/2016 à 09:17, Alex Brollo a écrit :

I'd like to state a "binary page quality" splitting the workflow into its basic steps (proofreading of text; formatting; adding links; validating....), t.i. into a set of true/false states, clearly showing the list of lacking steps. I.e. sometimes I fastly add complex formatting to rough text, and this results into a exotic "level" proofreading=false, formatting=true. It's a level 1, but it is deeply different from a level 1 coming from proofreading=true, formatting=false.

That's closer to the idea I had in mind. :)

Obviously the whole "binary level" could be simply stored as a number, with useful information into it.

Alex

2016-11-11 8:32 GMT+01:00 Sam Wilson <sam@samwilson.id.au mailto:sam@samwilson.id.au>:

That sounds really interesting! Do you mean as a way for people
unfamiliar with Wikisource to easily contribute notes and
corrections? On the face of things, it could perhaps work by
storing the notes in a the Page_talk namspace and doing some
clever thing to display them on the Page (and perhaps in main)
namespaces.

It seems like it'd be cool to be able to get "typo reports" or
something, from people who mightn't have any idea of Wikisource
other than that's where they got an epub.

To rate a page, we currently have the various levels of
proofreading quality. Is this not sufficient? And does the current
Index page overview of all of a book's statuses work for you? I
sometimes wonder if we need another rating, above 'validated',
that indicates that a whole book has been read through and
(hopefully) any remaining typos have been found.

—sam

On Fri, 11 Nov 2016, at 12:27 AM, mathieu stumpf guntz wrote:

...

Hmm, at the conference I think someone was interested in a
feature to make comments on texts, like you can make on some word
processors for example. That may be interesting, but how you
render the result might be a huge user interface problem. One
should be able to choose whom comments should be visible…

Otherwise, I would still be happy to have more flexibable way to
"rate" a page. That is, a page might be text proof readed, but
laking some css, or a picture should be extracted etc. Having a
way to see that for all pages in the book: namespace would be fine.

ĝis baldaŭ


Le 10/11/2016 à 06:09, Sam Wilson a écrit :

...

Thanks Alex :) It's a minor project so far, but I reckon the work you've
been doing on making a better, bigger, more proofreading-focused
interface is really good. Do stick a proposal up!

So far, we've got:

* Add a 'clean' method for side-titles, and side notes to parser
* A spelling- and typo-checking system for proofreading
* Visual Editor menu refresh
* upload text wizard
* Language links in Wikisource for edition items in Wikidata
* Display subpage name in category
* Make Special:IndexPage transcludeable
* Fix Extension:Cite to get rid of foibles

If anyone's got half-formed ideas, I'd encourage you to post something,
or just post to this mailing list, and we can all have a chat about it.
:)

—sam


On Wed, 9 Nov 2016, at 04:50 PM, Alex Brollo wrote:

...

I too could add *some* proposals.... but the first one could be a deep revision of nsPage edit interface to got the goal "fixed tools, almost full screen scrolling text & image". In the meantime, I'm go on testing FullScreenEditing.js by Sam, that presently is an excellent, running  step approximating such a goal.

Alex

2016-11-09 1:03 GMT+01:00 Sam Wilson<sam@samwilson.id.au> <mailto:sam@samwilson.id.au>:

...

__
Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)


—sam



On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

...

Hi Thomas,
thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource
<https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource>
Cheers,
Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT<thomaspt@hotmail.fr> <mailto:thomaspt@hotmail.fr>  wrote:

> Hello everyone, > > The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". > Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support. > > Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support). > > Cheers, > > Thomas > > > >> Début du message réexpédié : >> >> *De: *Johan Jönssonjjonsson@wikimedia.org mailto:jjonsson@wikimedia.org >> *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* >> *Date: *7 novembre 2016 à 20:26:21 UTC+1 >> *À: *Wikitech Ambassadorswikitech-ambassadors@lists.wikimedia.org >> mailto:wikitech-ambassadors@lists.wikimedia.org >> *Répondre à: *Coordination of technology deployments across languages/projectswikitech-ambassadors@lists.wikimedia.org >> mailto:wikitech-ambassadors@lists.wikimedia.org >> >> Hi everyone, >> >> Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers, >>

  been the focus of Wikimedia hackathons and so on. In short, I think it
  matters.

...

...

...

>> Now we're doing the process again. >> >> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey >> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey >> >> If you'd feel like spreading this in your communities, it would be much appreciated. >> >> *) This is when you can suggest things. This phase will last from 7 November to 20 November. >> *) Editors who are not comfortable writing in English can write proposals in their language. >> *) Voting will take place 28 November to 12 December. >> >> Thanks, >> >> //Johan Jönsson >> -- >> >> >> >> >> _______________________________________________ >> Wikitech-ambassadors mailing list >> Wikitech-ambassadors@lists.wikimedia.org >> mailto:Wikitech-ambassadors@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors >> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors >> > _______________________________________________ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > mailto:Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > https://lists.wikimedia.org/mailman/listinfo/wikisource-l >

>

Etiamsi omnes, ego non
_________________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
<https://lists.wikimedia.org/mailman/listinfo/wikisource-l>

_______________________________________________
  Wikisource-l mailing list
  Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
  https://lists.wikimedia.org/mailman/listinfo/wikisource-l
<https://lists.wikimedia.org/mailman/listinfo/wikisource-l>

_________________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
<https://lists.wikimedia.org/mailman/listinfo/wikisource-l>

_______________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
<https://lists.wikimedia.org/mailman/listinfo/wikisource-l>

_________________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
<https://lists.wikimedia.org/mailman/listinfo/wikisource-l>

_______________________________________________ Wikisource-l
mailing list Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
<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

Le 11/11/2016 à 08:32, Sam Wilson a écrit :

That sounds really interesting! Do you mean as a way for people unfamiliar with Wikisource to easily contribute notes and corrections? On the face of things, it could perhaps work by storing the notes in a the Page_talk namspace and doing some clever thing to display them on the Page (and perhaps in main) namespaces.

Sounds a good initial implementation path. Users may also would like to make more "personal" text comments, in which case storing them in User namespace might be more appropriate.

It seems like it'd be cool to be able to get "typo reports" or something, from people who mightn't have any idea of Wikisource other than that's where they got an epub.

To rate a page, we currently have the various levels of proofreading quality. Is this not sufficient?

Well, at least I would appreciate something more modular. Thinking about it, I may just use some categories, and maybe some js or lua to generate what I wish.

And does the current Index page overview of all of a book's statuses work for you?

That's the same. The thing is, I do like to make restitution as accurate to the original page as I can. That's a work which might be done in several parallel step. For example page layout, proofreading, and image extractions might be in different state of completeness. And for example I do like to have a really accurate page reproduction, so even caesura is the same in Page namespace, but still render without unnecessary dashes in main namespace (example https://fr.wikisource.org/wiki/Page:Holbach_-_Le_Christianisme_d%C3%A9voil%C3%A9,_1756.djvu/46). But not all contributors have this will. :)

I sometimes wonder if we need another rating, above 'validated', that indicates that a whole book has been read through and (hopefully) any remaining typos have been found.

My feedback doesn't really suggest a "rating above", but having separated rates/tags.

—sam

On Fri, 11 Nov 2016, at 12:27 AM, mathieu stumpf guntz wrote:

...

Hmm, at the conference I think someone was interested in a feature to make comments on texts, like you can make on some word processors for example. That may be interesting, but how you render the result might be a huge user interface problem. One should be able to choose whom comments should be visible…

Otherwise, I would still be happy to have more flexibable way to "rate" a page. That is, a page might be text proof readed, but laking some css, or a picture should be extracted etc. Having a way to see that for all pages in the book: namespace would be fine.

ĝis baldaŭ

Le 10/11/2016 à 06:09, Sam Wilson a écrit :

...

Thanks Alex :) It's a minor project so far, but I reckon the work you've been doing on making a better, bigger, more proofreading-focused interface is really good. Do stick a proposal up!

So far, we've got:

• Add a 'clean' method for side-titles, and side notes to parser
• A spelling- and typo-checking system for proofreading
• Visual Editor menu refresh
• upload text wizard
• Language links in Wikisource for edition items in Wikidata
• Display subpage name in category
• Make Special:IndexPage transcludeable
• Fix Extension:Cite to get rid of foibles

If anyone's got half-formed ideas, I'd encourage you to post something, or just post to this mailing list, and we can all have a chat about it. :)

—sam

On Wed, 9 Nov 2016, at 04:50 PM, Alex Brollo wrote:

...

I too could add *some* proposals.... but the first one could be a deep revision of nsPage edit interface to got the goal "fixed tools, almost full screen scrolling text & image". In the meantime, I'm go on testing FullScreenEditing.js by Sam, that presently is an excellent, running step approximating such a goal.

Alex

2016-11-09 1:03 GMT+01:00 Sam Wilsonsam@samwilson.id.au mailto:sam@samwilson.id.au:

...

__ Huzza for Wikisource; we've currently got more proposals than any of the other categories (not that it's a competition, but still...).

@Micru: this whole topic of how to represent bibliographic data in WD and properly link it in Wikisource is great! I'm looking forward to helping. :-)

—sam

On Tue, 8 Nov 2016, at 10:08 PM, David Cuenca Tudela wrote:

...

Hi Thomas, thanks for bringing that up! I wrote a proposal to finish the work retrieving the language links from several editions and represent them in wikisource as language links.

To write or vote exiting Wikisource proposals, the link is: https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wi... Cheers, Micru

On Tue, Nov 8, 2016 at 10:06 AM, Thomas PTthomaspt@hotmail.fr mailto:thomaspt@hotmail.fr wrote:

> Hello everyone, > > The Wikimedia Foundation Community Tech team has launched a new "Community Wishlist Survey". > Last year survey allowed us to get WMF staff time to work on using Google OCR in Wikisource that allowed some Indian languages Wikisources to raise and on VisualEditor support. > > Please, take time to submit new wishes and comment them. It could be simple things (e.g. a new gadget for a specific workflow) or very complicated ones (e.g. native TEI support). > > Cheers, > > Thomas > > > >> Début du message réexpédié : >> >> *De: *Johan Jönssonjjonsson@wikimedia.org mailto:jjonsson@wikimedia.org >> *Objet: **[Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016* >> *Date: *7 novembre 2016 à 20:26:21 UTC+1 >> *À: *Wikitech Ambassadorswikitech-ambassadors@lists.wikimedia.org >> mailto:wikitech-ambassadors@lists.wikimedia.org >> *Répondre à: *Coordination of technology deployments across languages/projectswikitech-ambassadors@lists.wikimedia.org >> mailto:wikitech-ambassadors@lists.wikimedia.org >> >> Hi everyone, >> >> Last year, the Community Tech team did a survey for a community wishlist to decide what we shoudl be working on throughout the year. Since it's useful to have a list of tasks from the Wikimedia communities, it's also been used by other developers, >>

been the focus of Wikimedia hackathons and so on. In short, I think it matters.

...

...

...

>> Now we're doing the process again. >> >> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey >> >> If you'd feel like spreading this in your communities, it would be much appreciated. >> >> *) This is when you can suggest things. This phase will last from 7 November to 20 November. >> *) Editors who are not comfortable writing in English can write proposals in their language. >> *) Voting will take place 28 November to 12 December. >> >> Thanks, >> >> //Johan Jönsson >> -- >> >> >> >> >> _______________________________________________ >> Wikitech-ambassadors mailing list >> Wikitech-ambassadors@lists.wikimedia.org >> mailto:Wikitech-ambassadors@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors >> > _______________________________________________ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > mailto:Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l >

>

Etiamsi omnes, ego non _________________________________________________ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org mailto:Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org mailto:Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org mailto:Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org mailto:Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

---

Wikisource-l mailing list Wikisource-l@lists.wikimedia.org mailto: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