from:"wilson"

As the error mentions please "Check the 'Rules' of this config repository"
- by default your config repo won't have rules/permissions to define
pipelines in any pipeline groups, environments etc. It is "secure by
default". You'll want to add a permission to do so.

e.g a blanket permission to allow a config repo to affect any environment
or pipeline group looked like: You can click the "learn more" link from the
config repo edit to read more about these rules.

[image: image.png]
-Chad

On Fri, Oct 27, 2023 at 1:27 PM vv-fork  wrote:

> Greetings colleagues,
>
> I am trying to get into Yaml plugin (*gocd-yaml-config-plugin.jar* v.
> *0.14.3-321*) with goCD v.23.3.0.
>
> The plugin is able to receive the yaml file but always throws the same
> error.
>
> I am stuck with something pretty simple, like this:
> format_version: 10
>
> pipelines:
>   mypipe:
> group: mygroup
> materials:
>   mygit:
> git: http://example.com/mygit.git
> stages:
>   - build:
>   jobs:
> build:
>   tasks:
>- exec:
>command: make
>
> environments:
>
> The message is:
> INVALID MERGED CONFIGURATION Number of errors: 1+ I. Rule Validation
> Errors: 1. Not allowed to refer to pipeline group 'mygroup'. Check the
> 'Rules' of this config repository. II. Config Validation Errors: - For
> Config Repo: https://github.com/...p at revision 03a639fd6444>>>74d5
>
> What am I doing wrong?
>
> Vlad.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/01c04e91-0322-45fa-9021-58dd90424b80n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH9LXz3xBiN822wKt4GaF8m9232nnjsJvdwMjTf_2VsAiA%40mail.gmail.com.

Re: [go-cd] GoCD and private GitHub repo

Based on the error message it looks like the clone URL you are using is
still an HTTPS one - to use SSH auth, you need to change it to an ssh URL,
e.g g...@github.com:gocd/gocd.git - it's an entirely different git
transport, not just an auth mechanism so the URL needs to change
accordingly :-)

If you're new to using SSH to talk to a git repo manager, you might want to
try doing it separately on the command line with a git clone before getting
it to work with GoCD as adding in the GoCD server and agent adds some extra
complexity.

-Chad

On Fri, Oct 27, 2023 at 1:13 PM vv-fork  wrote:

> Thank you guys Sriram and Chad for answering those! Now it's getting
> clearer to me
>
> *I was able to connect using token. It's fine.*
>
> Though I* wasn't able* to connect using SSH Certificate.
> The key has been generated and installed:
> [image: unnamed.png]
>
> it seems i set proper permissions:
> [image: unnamed.png]
>
> but i still get that error message when i test connection from go-server:
> --- STANDARD ERR --- STDERR: fatal: could not read Username for '
> https://github.com': No such device or address ---
>
>
> So what am i doing wrong? May that be I have messed with permissions for *go
> user*?
>
>
> Vlad.
>
> On Thursday, October 26, 2023 at 8:41:33 PM UTC+13 Chad Wilson wrote:
>
>> To add on to Sriram's comments, the use of the
>> github-oauth-authorization-plugin doesn't have any relationship with access
>> to repository content on GitHub - it simply allows people to log onto GoCD
>> using their Github identity, and optionally to have access to GoCD pipeline
>> groups mapped to GitHub roles.
>>
>> This is because materials/repositories need to be accessed in an identity
>> known to the GoCD server/agents, not necessarily the individual user who
>> happens to be logged in to GoCD. So even if you use that authorization
>> plugin, you still need to decide how to provide GoCD itself access to
>> repositories on Github.
>>
>> You can use an SSH key linked to a GitHub user
>> <https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account>
>> if you wish to use SSH access - no restrictions for private repos unless
>> your GitHub org blocks use of SSH keys. If you instead wish to use HTTPS
>> access to repositories you have to fill in a username/"password" for each
>> material you configure. That "password" would be a personal access token
>> <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens>
>> with at least read-only access to the 1 or more repositories you want to
>> use.
>>
>> If you want to share one personal access token across many materials
>> (perhaps a single token has read-only access to many repositories), the
>> easiest way is to use a GoCD Secrets Management plugin and refer to them in
>> the username/"password" fields of each material using the special secrets
>> interpolation syntax:
>> https://docs.gocd.org/current/configuration/secrets_management.html This
>> will work with either manually defined pipelines/materials, or those
>> defined externally in source control.
>>
>> -Chad
>>
>> On Thu, Oct 26, 2023 at 3:01 PM Sriram Narayanan 
>> wrote:
>>
>>> Please see:
>>>
>>> https://docs.github.com/en/authentication/connecting-to-github-with-ssh
>>>
>>> The gocd server runs as a particular user account. That user account
>>> needs access to the ssh private keys used to authenticate with GitHub.
>>>
>>> The go agent too needs the same access.
>>>
>>> Assuming you are on Linux and installer gocd via rpm, then you would set
>>> this key in the home directory (
>>> /var/lib/go-server/.ssh/myprivatekey.id_rsa)
>>>
>>> Permissions for .ssh would be 600, and for the key would be 400, with
>>> the gocd process user owning the directory and The identity file.
>>>
>>> — Sriram
>>>
>>>
>>> On Thu, 26 Oct 2023 at 12:00 PM, vv-fork  wrote:
>>>
>>>> Hello colleagues!
>>>>
>>>> What is the best way to connect on-prem goCD with GitHub private repo
>>>> in cloud? I was smoking docs and manuals for quite a while, but what people
>>>> say it’s to install ssh keys to both GitHub and goCD, which won’t work,
>>>> since I am using github.com, so i suppose i can’t install ssh key
>>>> there.
>>>>
>>>> I’ve installed github-oauth-authorization-plugin and set it as
>>>> des

[Translators-l] Ready for translation: Tech News #44 (2023)

2023-10-26 Thread Nick Wilson (Quiddity)

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/44

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F44=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [Servercert-wg] Draft Ballot SC-067: Applicant, Subscriber and Subscriber Agreements - Feedback requested

2023-10-26 Thread Ben Wilson via Servercert-wg

Just inside lines 276-279, I suggest we replace "Applicant" with
"Applicant/Subscriber" so it would read:

**Applicant/Subscriber Representative**: A natural person or human sponsor
who is either the Applicant/Subscriber, employed by the
Applicant/Subscriber, or an authorized agent who has express authority to
represent the Applicant/Subscriber:

  i. who signs and submits, or approves a certificate request on behalf of
the Applicant/Subscriber, and/or

  ii. who accepts a Subscriber Agreement on behalf of the
Applicant/Subscriber.

Thanks,

Ben

On Wed, Oct 25, 2023 at 7:47 PM Dustin Hollenback via Servercert-wg <
servercert-wg@cabforum.org> wrote:

> Hello all,
>
>
>
> This is a request for feedback for this draft ballot.
>
>
>
> Thank you,
>
>
>
>
>
> Dustin
>
>
>
>
>
>
> ---
>
>
>
> *Purpose of Ballot SC-067*
>
> This ballot proposes updates to the Baseline Requirements for the Issuance
> and Management of Publicly-Trusted Certificates related to Subscriber
> Agreements and Terms of Use. It combines the requirements for both into
> only the Subscriber Agreement and clarifies the requirement language. It
> removes the requirement and reference to "Terms of Use". It also modifies
> details related to Subscriber, Applicant, and representatives for them.
>
>
>
> Notes:
>
> •  This removes any ambiguity to ensure that there is no
> requirement that the Subscriber Agreement be legally enforceable when the
> CA and Subscriber are affiliated.
>
> •  This updates definitions for “Applicant”, “Subscriber” and
> “Subscriber Agreement” and removes the definition for “Terms of Use” as
> these separate concepts are creating unnecessary work for CAs and
> Subscribers without adding any value when separated.
>
> •  This adds a new definition for “Applicant/Subscriber” to
> account for scenarios where a person or entity may be either. And renames
> “Applicant Representative” to “Applicant/Subscriber Representative” and
> updated definition to account for reseller scenarios.
>
> •  As observed with other ballots in the past, minor
> administrative updates must be made to the proposed ballot text before
> publication such that the appropriate Version # and Change History are
> accurately represented (e.g., to indicate these changes will be represented
> in Version 2.0.2).
>
> •  This ballot does not modify the “Guidelines for the
> Issuance and Management of Extended Validation Certificates”. More work
> will be made to that document after changes are finalized in this one.
>
>
>
> The following motion has been proposed by Dustin Hollenback of Microsoft,
> and endorsed by Tadahiko Ito of SECOM and Ben Wilson of Mozilla.
>
>
>
> *— Motion Begins —*
>
>
>
> This ballot modifies the “Baseline Requirements for the Issuance and
> Management of Publicly-Trusted Certificates” (“Baseline Requirements”),
> based on Version 2.0.1.
>
>
>
> MODIFY the Baseline Requirements as specified in the following Redline:
>
>
>
> Here is a link to the GitHub redline:
>
>
> https://github.com/cabforum/servercert/compare/90a98dc7c1131eaab01af411968aa7330d315b9b...9eebd9949810f698edd5087235acaf16e04ead21
>
>
>
> *— Motion Ends —*
>
>
>
> This ballot proposes a Final Maintenance Guideline. The procedure for
> approval of this ballot is as follows:
>
>
>
> *Discussion (7+ days)*
>
> • Start time: -XX-XX 22:00:00 UTC
>
> • End time: -XX-XX 22:00:00 UTC
>
>
>
> *Vote for approval (7 days)*
>
> • Start time: -XX-XX 22:00:00 UTC
>
> • End time: -XX-XX 22:00:00 UTC
>
>
>
>
>
> --
>
>
>
>
>
>
>
>
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [go-cd] Kubernetes Elastic Agents - Pods can no longer be created

Unfortunately the error message is a bit mysterious and useless. Which
agent image you are using? Anything special in the elastic agent pod spec
that might no longer work as expected on Kubernetes 1.24? (e.g use of
docker dind images)

Does the pod get created (and fail) if you look at the events on the
kubernetes side, or does it never get that far?

-Chad

On Thu, Oct 26, 2023 at 11:37 PM Chad Wilson  wrote:

> Just curious - were the errors/stack traces on failure essentially
> identical before and after you upgraded your gocd and elastic agent plugin
> versions?
>
> On Thu, Oct 26, 2023 at 11:33 PM Kim Pham  wrote:
>
>> Hi Ashwanth,
>>
>> I checked the clusterrole of the service account it's using and it
>> basically has full access atm.
>>
>> PolicyRule:
>>   Resources   Non-Resource URLs  Resource Names  Verbs
>>   -   -  --  -
>>   events  [] []  [*]
>>   namespaces  [] []  [*]
>>   nodes   [] []  [*]
>>   pods/log[] []  [*]
>>   pods[] []  [*]
>>
>> On Thu, Oct 26, 2023 at 10:21 AM 'Ashwanth Kumar' via go-cd <
>> go-cd@googlegroups.com> wrote:
>>
>>> A wild guess, anything changed on the service account side or a custom
>>> role being added as part of the upgrade that is probably not allowing the
>>> gocd plugin to create the pod?
>>>
>>> Thanks,
>>>
>>>
>>> On Thu, 26 Oct 2023 at 20:27, Kim Pham  wrote:
>>>
>>>> Hi All,
>>>>
>>>> We recently began to encounter issues where pods were unable to be
>>>> created.  Nothing has changed in terms of GoCD server, agent, and
>>>> Kubernetes elastic agent plugin versions.  However, we did notice that the
>>>> cluster went through an automatic upgrade and updated gke version to
>>>> 1.24.14.  GoCD is able to see the node pools through the 'Status Report'
>>>> button.
>>>>
>>>> When attempting to create an agent on those node pools, I do see a 500
>>>> in the plugin logs and gocd-server logs.  Attached are logs.
>>>>
>>>> I've tried updating GoCD and the plugins to latest release versions.
>>>> Our static agents that are running on older gke versions aren't having any
>>>> issues.
>>>>
>>>> Has anyone encountered this?
>>>>
>>>> Thanks in advance.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "go-cd" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to go-cd+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/go-cd/a6b8e99d-f415-4c18-b67d-e86c3df16733n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/go-cd/a6b8e99d-f415-4c18-b67d-e86c3df16733n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>>
>>> Ashwanth Kumar / ashwanthkumar.in
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/CAD9m7Cw2cK5yt_r9e5r1sxD%2B%2B%2Bjkd3%3DFTQe51vKqb081MunU%3DQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/go-cd/CAD9m7Cw2cK5yt_r9e5r1sxD%2B%2B%2Bjkd3%3DFTQe51vKqb081MunU%3DQ%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/CA%2BnJfx4-Zks6-FOr1bYSOroxG2o4e2e4ir0OFUm3TsggWsrYpA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/go-cd/CA%2BnJfx4-Zks6-FOr1bYSOroxG2o4e2e4ir0OFUm3TsggWsrYpA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH-tw%3D0MFCgWRQoT8ZwFYcyJsGT8T5pPxrBzzu46Nn960w%40mail.gmail.com.

Re: [go-cd] Kubernetes Elastic Agents - Pods can no longer be created

Just curious - were the errors/stack traces on failure essentially
identical before and after you upgraded your gocd and elastic agent plugin
versions?

On Thu, Oct 26, 2023 at 11:33 PM Kim Pham  wrote:

> Hi Ashwanth,
>
> I checked the clusterrole of the service account it's using and it
> basically has full access atm.
>
> PolicyRule:
>   Resources   Non-Resource URLs  Resource Names  Verbs
>   -   -  --  -
>   events  [] []  [*]
>   namespaces  [] []  [*]
>   nodes   [] []  [*]
>   pods/log[] []  [*]
>   pods[] []  [*]
>
> On Thu, Oct 26, 2023 at 10:21 AM 'Ashwanth Kumar' via go-cd <
> go-cd@googlegroups.com> wrote:
>
>> A wild guess, anything changed on the service account side or a custom
>> role being added as part of the upgrade that is probably not allowing the
>> gocd plugin to create the pod?
>>
>> Thanks,
>>
>>
>> On Thu, 26 Oct 2023 at 20:27, Kim Pham  wrote:
>>
>>> Hi All,
>>>
>>> We recently began to encounter issues where pods were unable to be
>>> created.  Nothing has changed in terms of GoCD server, agent, and
>>> Kubernetes elastic agent plugin versions.  However, we did notice that the
>>> cluster went through an automatic upgrade and updated gke version to
>>> 1.24.14.  GoCD is able to see the node pools through the 'Status Report'
>>> button.
>>>
>>> When attempting to create an agent on those node pools, I do see a 500
>>> in the plugin logs and gocd-server logs.  Attached are logs.
>>>
>>> I've tried updating GoCD and the plugins to latest release versions.
>>> Our static agents that are running on older gke versions aren't having any
>>> issues.
>>>
>>> Has anyone encountered this?
>>>
>>> Thanks in advance.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/a6b8e99d-f415-4c18-b67d-e86c3df16733n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> Ashwanth Kumar / ashwanthkumar.in
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/CAD9m7Cw2cK5yt_r9e5r1sxD%2B%2B%2Bjkd3%3DFTQe51vKqb081MunU%3DQ%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CA%2BnJfx4-Zks6-FOr1bYSOroxG2o4e2e4ir0OFUm3TsggWsrYpA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH9L%3DmBaJbvnXDfJ0d3J2_GuhC%2B38y4sMUiaMPDgAEd__Q%40mail.gmail.com.

Re: [go-cd] GoCD and private GitHub repo

To add on to Sriram's comments, the use of the
github-oauth-authorization-plugin doesn't have any relationship with access
to repository content on GitHub - it simply allows people to log onto GoCD
using their Github identity, and optionally to have access to GoCD pipeline
groups mapped to GitHub roles.

This is because materials/repositories need to be accessed in an identity
known to the GoCD server/agents, not necessarily the individual user who
happens to be logged in to GoCD. So even if you use that authorization
plugin, you still need to decide how to provide GoCD itself access to
repositories on Github.

You can use an SSH key linked to a GitHub user

if you wish to use SSH access - no restrictions for private repos unless
your GitHub org blocks use of SSH keys. If you instead wish to use HTTPS
access to repositories you have to fill in a username/"password" for each
material you configure. That "password" would be a personal access token

with at least read-only access to the 1 or more repositories you want to
use.

If you want to share one personal access token across many materials
(perhaps a single token has read-only access to many repositories), the
easiest way is to use a GoCD Secrets Management plugin and refer to them in
the username/"password" fields of each material using the special secrets
interpolation syntax:
https://docs.gocd.org/current/configuration/secrets_management.html This
will work with either manually defined pipelines/materials, or those
defined externally in source control.

-Chad

On Thu, Oct 26, 2023 at 3:01 PM Sriram Narayanan 
wrote:

> Please see:
>
> https://docs.github.com/en/authentication/connecting-to-github-with-ssh
>
> The gocd server runs as a particular user account. That user account needs
> access to the ssh private keys used to authenticate with GitHub.
>
> The go agent too needs the same access.
>
> Assuming you are on Linux and installer gocd via rpm, then you would set
> this key in the home directory (
> /var/lib/go-server/.ssh/myprivatekey.id_rsa)
>
> Permissions for .ssh would be 600, and for the key would be 400, with the
> gocd process user owning the directory and The identity file.
>
> — Sriram
>
>
> On Thu, 26 Oct 2023 at 12:00 PM, vv-fork  wrote:
>
>> Hello colleagues!
>>
>> What is the best way to connect on-prem goCD with GitHub private repo in
>> cloud? I was smoking docs and manuals for quite a while, but what people
>> say it’s to install ssh keys to both GitHub and goCD, which won’t work,
>> since I am using github.com, so i suppose i can’t install ssh key there.
>>
>> I’ve installed github-oauth-authorization-plugin and set it as described
>> (connection ok in authorisation configuration step), and restarted the
>> server, however it’s still throwing that standard error “fatal: could not
>> read Username for ‘https://github.com’ meaning that the access is still
>> closed.
>>
>> What else can be done as you think?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/ed3022b6-e1ec-4c3b-8ca3-3c5e6b7d72f4n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CANiY96azM2%3DaFO351d4PpExOatRCO%2BoaQju3Juvm2yAbQR2d5A%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH-R9v39GDB_Rs98pXnh0x7xyMZKwanye7Mcq%3D7hSdA1tQ%40mail.gmail.com.

[African Wikimedians] [Wiki Loves Africa] Heures de bureau le 28 octobre 2023

2023-10-26 Thread Wilson Oluoha

Chers Wikimédiens,

Nous annonçons des heures de bureau pour Wiki Loves Africa ce samedi (28
octobre), nous fournirons de l'aide pour les demandes de subvention Rapide
pour  2024. Vous trouverez les détails ci-dessous:

Office hour mix English/French[edit
<https://meta.wikimedia.org/w/index.php?title=Wiki_Loves_Africa_2024/Participating_communities=edit=5>
]

   - Saturday 28 October 2023 (08:00 UTC)
  - Click to join zoom meeting <https://us02web.zoom.us/j/83642040330>


Pour plus d'informations, veuillez consulter la page des communautés
participantes ici
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities>
.

Cordialment,

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] Office hours 28th October 2023

2023-10-26 Thread Wilson Oluoha

Dear Wikimedians,

Announcing office hours for Wiki Loves Africa this *Saturday (28th Oct.*),
we will be providing help with 2024 Rapid grant applications. You can find
the details below:

Office hour mix English/French[edit
<https://meta.wikimedia.org/w/index.php?title=Wiki_Loves_Africa_2024/Participating_communities=edit=5>
]

   - Saturday 28 October 2023 (08:00 UTC)
  - Click to join zoom meeting <https://us02web.zoom.us/j/83642040330>


For more information, please visit the participating communities page here
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities>
.

Best,

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: [ANN] Maven Surefire 3.2.1 released

2023-10-25 Thread Garret Wilson

Could you clarify whether this means that the plugin will not work 
correctly, and whether we should wait for a patch version that uses the 
correct dependencies instead of upgrading our POMs to use this announced 
version 3.2.1?


Thanks,

Garret

On 10/24/2023 7:42 AM, Thomas Broyer wrote:

This is using plexus-xml 4.0.0 (from Parent 40). Shouldn't that be
downgraded to 3.0.0?
(
https://github.com/apache/maven-parent/commit/096de2d1f79a1b692a112db16675ecc2ac013597
says 4.0.0 is not compatible with Maven 3; maybe a Parent 41 should have
been released after that commit?)

Fwiw, I have a plugin that depends on surefire-common (maybe it shouldn't
but that's another story) and this brings maven-xml-impl et al. that are
flagged as not being in the correct scope (brought in as "compile", should
be "provided"). My tests pass with that version, but I've explicitly
downgraded to 3.0.0 (upgraded plexus-utils to 4.0.0 and added dependency on
plexus-xml 3.0.0) and tests still pass, so I think I'm going to go with
that.

On Mon, Oct 23, 2023 at 10:00 PM Michael Osipov  wrote:


The Apache Maven team is pleased to announce the release of the Maven
Surefire version 3.2.1.

https://maven.apache.org/surefire/


Release Notes - Maven Surefire - Version 3.2.1

** Bug
  * [SUREFIRE-2190] - optional dependencies and JPMS modules confuse
surefire
  * [SUREFIRE-2196] -
maven-surefire-report-plugin:failsafe-report-only failed: Unmatched
braces in the pattern
  * [SUREFIRE-2202] - NullPointerException if super class meets
specific condition

** New Feature
  * [SUREFIRE-1124] - Let ${surefire.forkNumber} deliver unique
environmentVariables when used in parallel mvn builds

** Improvement
  * [SUREFIRE-2177] - Use junit-bom instead of single JUnit 5 versions
  * [SUREFIRE-2178] - classpathDependencyExcludes should support
classifiers
  * [SUREFIRE-2179] - additionalClasspathElements should support
Maven coordinates
  * [SUREFIRE-2182] - Log starter implementation on DEBUG level

** Dependency upgrade
  * [SUREFIRE-2188] - Upgrade to Parent 40


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[Translators-l] Re: Ready for translation: Tech News #43 (2023)

2023-10-23 Thread Nick Wilson (Quiddity)

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 19 languages) to 1,095 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 43

2023-10-23 Thread Nick Wilson (Quiddity)

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/43. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - There is a new Language and internationalization newsletter
   
,
   written quarterly. It contains updates on new feature development,
   improvements in various language-related technical projects, and related
   support work.
   - Source map support has been enabled on all wikis. When you open the
   debugger in your browser's developer tools, you should be able to see the
   unminified JavaScript source code. [1]
   

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 24 October. It
   will be on non-Wikipedia wikis and some Wikipedias from 25 October. It will
   be on all wikis from 26 October (calendar
   ).

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute
 •
Translate
 •
Get help  • Give feedback
 • Subscribe or unsubscribe
.*
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

[African Wikimedians] [WLA][RAPPEL] Notification de la date limite de pour demander une rapide subvention pour le concours 2024

2023-10-23 Thread Wilson Oluoha

  Chers Wikimédiens,

Cet e-mail a pour vous informer que la date limite de dépôt des demandes de
subvention rapide pour l'organisation de Wiki Loves Africa 2024 est fixée
au *1er novembre 2023*.

Nous vous encourageons à compléter vos demandes (pour ceux qui ont besoin
d'une subvention rapide) et à les soumettre au plus tard à la date limite
mentionnée ci-dessus. Nous vous serions également reconnaissants d'indiquer
les détails de votre communauté sur la page des participants ici
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities#Participating_communities_in_2024>
.

Le thème du concours 2024 est *Africa Create* et débutera en mars 2024.

N'hésitez pas à envoyer un courriel à *wil...@wikiinafrica.org
* si vous avez des questions ou si vous avez
besoin d'informations et/ou d'assistance.

Cordialment



-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [WLA][REMINDER] Notification of Deadline for Rapid Grants Applications

2023-10-23 Thread Wilson Oluoha

Dear Wikimedians,

This email is to notify you that the deadline for applying for a rapid
grant for the purpose of organizing Wiki Loves Africa 2024 is *1st November
2023*.

You are encouraged to complete your applications (for those who need a
rapid grant) and submit on or before the above mentioned deadline. We would
also be grateful if you list out details of your community on the participants
page here

.

The Theme for the 2024 contest is *Africa Create* and will commence in
March 2024.

Kindly email *wil...@wikiinafrica.org * if you
have any questions or need any information and/or assistance.

Best regards
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[Elecraft] Kitchen Radio

2023-10-22 Thread Wilson Lamb via Elecraft

Would someone please tell me how to find the message about the improvised 
radios made from kitchen finds?
Thanks,
Wilson
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

[Translators-l] Re: Ready for translation: Tech News #43 (2023)

2023-10-20 Thread Nick Wilson (Quiddity)

On Thu, Oct 19, 2023 at 4:07 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/43
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F43=page
>

The text of the newsletter is now final.

*One item has been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[grpc-io] gRPC-Java v1.59.0 Released

2023-10-20 Thread 'Terry Wilson' via grpc.io

You can now grab the v1.59.0 
 release.

PLANNED ABI BREAKAGE!

This breaks the ABI of the @ExperimentalApi classes listed below.
This does not impact source code (API); it only impacts code compiled with 
a different version of gRPC than it runs with (ABI).

Users that recompiled their code using grpc-java v1.36.0 
 (released on Feb 
23, 2021) and later, ARE NOT AFFECTED.
Users that compiled their source using grpc-java earlier than v1.36.0 may 
need to recompile when upgrading to grpc-java v1.59.0.

See details in #10406 .

*Affected classes*

Class io.grpc.internal.AbstractManagedChannelImplBuilder is deleted, and no 
longer in the class hierarchy of the channel builders:

io.grpc.netty.NettyChannelBuilder
io.grpc.okhttp.OkhttpChannelBuilder
io.grpc.cronet.CronetChannelBuilder
Class io.grpc.internal.AbstractServerImplBuilder is deleted, and no longer 
in the class hierarchy of the server builders:

io.grpc.netty.NettyServerBuilder
io.grpc.inprocess.InProcessServerBuilder

API Changes
core: AbstractManagedChannelImplBuilder and AbstractServerImplBuilder are 
removed (#10530 ). This is 
ABI-breaking, see the warning above. (#10406 
)
core: Removed .class file hack previously introduced in v1.36.0 
 to ease removal of 
internal ABIs. (#10406 )
api: Add ForwardingChannelBuilder2, an ABI-safe version of 
ForwardingChannelBuilder, which will be deprecated in the following 
release. (#10585 , #10406 
)
api: Add LoadBalancer.FixedResultPicker convenience class for load balancer 
implementations. It is a replacement for ErrorPicker and EMPTY_PICKER added 
in 1.58.0
testing: Stabilize TestMethodDescriptors (#10530 
)

Behavior Changes
core: de-expermentalize pick first config parsing (#10531 
)
netty: Respect -Dio.netty.allocator.type=unpooled when getting Netty 
Allocator instead of ignoring it (#10543 
)
netty: Use UNAVAILABLE for connections closed while writing. Previously 
this would result in UNKNOWN
binder: Enable indirect addressing using s. (#10550 
)

Improvements
core: only use reflection to resolve InternalCensusStatsAccessor once 
instead of once per channel
core: enhance error message in the case of DEADLINE_EXCEEDED to indicate 
name resolution delay.
netty: When creating a connection, use java.util.logging formatting instead 
of String.format to avoid work when not logged
netty: Touch ByteBuf when message framing has been decoded. If the buffer 
is leaked, this helps narrow down the source of reference counting bug
java_grpc_library.bzl: Disable Automatic Exec Groups inside grpc libraries (
#10514 ). This improves 
compatibility with future Bazel versions while retaining Bazel 5.x 
compatibility

Bug Fixes
netty: Avoid NettyAdaptiveCumulator incorrectly releasing its input ByteBuf 
twice when reading messages under certain error conditions (#10537 
)
xds: Add fix for xdstp replacement for percent-encoded authorities (#10571 
)

Documentation
API documentation (Javadoc) for Server and Channel builders now correctly 
displays inherited methods and the class hierarchy. (#10406 
)
examples: add an example for OAuth (#10560 
)

Dependencies
Upgrade Netty to 4.1.97.Final

Acknowledgements
John Cormie (@jdcormie)
Stephane Landelle (@slandelle)
@kotlaja

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/64bd646c-5167-4201-9118-b18a8d5bd50dn%40googlegroups.com.

[Translators-l] Ready for translation: Tech News #43 (2023)

2023-10-19 Thread Nick Wilson (Quiddity)

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/43

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F43=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [tesseract-ocr] Should box include surrounding space?

2023-10-19 Thread 'Danny Wilson' via tesseract-ocr

Sorry, I had the coordinate system flipped on my last post.

Here is a correct image produced by text2image and includes both FULLWIDTH 
COMMA and COMMA.


For both types of comma, the boxes produced by text2image include only the 
boundaries of the glyph itself and does not consider the vertical position.

I've trained using this type of ground truth but when running the OCR the latin 
COMMA is always output instead of the correct FULLWIDTH COMMA. That's wrong.

If the box only surrounds the glyph exactly, then I fear that no amount of 
training will enable the model to differentiate between the two types of comma.

Is there a way to tune the training process?

Or... if instead I render boxes for some special characters to extend from the 
text baseline, which would then differentiate between the mid-line and baseline 
commas (but still not differentiate the fonts that have both fullwidth and 
normal comma on the baseline...)

Anyone have some experience with that?

Thanks
Danny

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/775668F0-506F-4FC3-B962-2FE0898252E3%40mac.com.

Re: [tesseract-ocr] Should box include surrounding space?

2023-10-18 Thread 'Danny Wilson' via tesseract-ocr

Because of some issues with licensed fonts not working with text2image, we 
wrote our own image and box file generator in Swift on the Mac.

We use that to generate a data set for 100,000 text lines and feed that into 
the regular training on Linux.

Using a non-licensed font, I checked what box text2image generated for the 
FULLWIDTH COMMA (should've done that earlier!)



So it looks like text2image uses the top base line for the box, which extends 
only as far down as the lowest extent of the glyph.  Such a box would 
differentiate between FULLWIDTH COMMA and COMMA if the font vertically centers 
FULLWIDTH COMMA.  

If the font renders FULLWIDTH COMMA on the text baseline, then the model would 
get confused between FULLWIDTH COMMA and COMMA since both are down on the 
baseline.

How does tesseract handle the whitespace to the left/right of a character?  Is 
there some kind parameter to set or would training with data containing both 
(baseline) FULLWIDTH COMMA and COMMA work?

Danny



> On 18 Oct 2023, at 20:43, Des Bw  wrote:
> 
> You need a large  data. That is all. 
> If you can collect a lot of text lines that contain all those types of 
> commas: and produce the training material using text2image (synthetic data) 
> for each font, I am pretty sure Tesseract will learn all of them with no 
> problem. 
> 
> On Wednesday, October 18, 2023 at 12:35:01 PM UTC+3 Danny wrote:
>> There are a few "commas" used in CJK which makes it complicated for me.
>> 
>> FULLWIDTH COMMA U+FF0C (link ) 
>> which might have the glyph in the center of the box or in the lower left 
>> corner depending on the font:
>> 
>>  
>> 
>> HALFWIDTH IDEOGRAPHIC COMMA U+FF64 (link 
>> ) which (as far as I can tell) 
>> will always be in the bottom corner regardless of font. (used to enumerate 
>> sequences)
>> 
>> 
>> COMMA U+002C, (link ) which isn't 
>> part of formal CJK languages but in practice is used all the time
>> 
>> 
>> So I'd like to train to recognize the three types of commas so the OCR 
>> output is matches the input images.  "FULLWIDTH COMMA" is a problem because 
>> the glyph position in the box is different depending on the font.  Hence my 
>> question "where and how big is the box?"
>> 
>> 
>> 
>> In the image above, lines 1, 2, and 3 are all FULLWIDTH COMMA but line 1 is 
>> a different font.  Line 4 is COMMA (U+002C) while line 5 is HALFWIDTH 
>> IDEOGRAPHIC COMMA U+FF64.
>> 
>> What's the best way to train given those types of input and the expected 
>> output?
>> 
>> Danny
>> On Wednesday, October 18, 2023 at 1:22:25 PM UTC+8 desal...@gmail.com <> 
>> wrote:
>>> If the space is included in the training across the board, the model might 
>>> not recognize  the comma when it appears without space  (as in numbers: 
>>> 23,334). 
>>> 
>>> On Wednesday, October 18, 2023 at 5:29:13 AM UTC+3 Danny wrote:
 For purposes of training, I'm wondering if the box for a character should 
 include the surrounding space. 
 
 In particular for the CJK "FULLWIDTH COMMA", should the box be the red or 
 green rectangle? 
 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "tesseract-ocr" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/tesseract-ocr/FJyyTpX1d7k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> tesseract-ocr+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tesseract-ocr/df5cc0ce-7af3-4b57-a911-06fa18217e52n%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/7DA5E773-AD3C-4F93-B804-E44C58989F89%40mac.com.

Re: [cabfpub] Forum Ballot to Amend Server Certificate WG Charter

2023-10-18 Thread Ben Wilson via Public

Thanks for your input, Dimitris.
I've amended section 4.d. as proposed -
https://github.com/cabforum/forum/commit/c6850e24eb49d5cfcb00eae4d11e82544504bffb
Thanks again,
Ben

On Wed, Oct 18, 2023 at 3:03 AM Dimitris Zacharopoulos (HARICA) <
dzach...@harica.gr> wrote:

>
> Hello Ben,
>
> At F2F58
> <https://cabforum.org/2023/03/02/minutes-of-the-f2f-58-meeting-in-ottawa-canada-28-february-1-march-2023/>we
> had a discussion about the lessons learned from ballot SC60
> <https://cabforum.org/wp-content/uploads/11-CABF_Lessons-learned-from-SC60.pdf>.
> During that meeting, a proposal was made that seems to fix the ambiguity of
> the current Bylaws.
>
> In line 93 of the proposed ballot, it says:
>
> ***(d)** There is a mandatory six-month probationary period during which
> any representative of an Applicant must attend at least 30% of all SCWG
> teleconferences (not counting subcommittee meetings) and at least one SCWG
> face-to-face meeting (either physically or virtually). After successful
> completion of the mandatory probationary period and meeting all
> requirements of section 3(a) or 3(b), an Applicant may become a Voting
> Member, if the SCWG determines by consensus among the Members during a
> Meeting or Teleconference, or upon the request of any Member, by a Ballot
> among the Members, that the Applicant meets the requirements of section
> 3(a) or 3(b). Acceptance by consensus shall be determined, or a Ballot of
> the Members shall be held, as soon as the Applicant indicates that it has
> presented all information required and has responded to all follow-up
> questions from the SCWG and the Applicant has complied with the
> requirements of Section 5.5 of the CA/Browser Forum Bylaws.*
>
>
> Instead of:
>
> *"or upon the request of any Member, by a Ballot among the Members, by a
> Ballot among the Members, that the Applicant meets the requirements of
> section 3(a) or 3(b)" *
>
> please update to:
>
> *"or upon the request of any Member that challenges the Applicant's
> adherence to all of the requirements of section 3(a) or 3(b), by a Ballot
> among the Members."*
>
> I read the rest of the proposed changes and they look good. If you are ok
> with the change above, HARICA would be happy to endorse the ballot.
>
>
> Best regards,
> Dimitris.
>
> On 13/10/2023 1:23 π.μ., Ben Wilson via Public wrote:
>
> All,
>
> I am planning to introduce a Forum ballot to amend the Server Certificate
> Working Group Charter.
>
> At a high level, here are some of the proposed changes:
>
>- Section numbering added
>- "Root Certificate Issuer" voting category removed
>- Membership requirements for Certificate Consumers added
>- 6-month probationary period prior to voting membership added
>- Voting percentages and quorum clarified
>
> Because there are numerous proposed changes, here are a diff and a blob
> for your review.
>
> <http://goog_919727606>
>
> https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...85e569a43a5a2c9e5e16ce8bf1e569a98cfbd720
>
> <https://mail.google.com/mail/u/0/goog_919727603>
>
> https://github.com/cabforum/forum/blob/BenWilson-SCWG-charter-1.3/SCWG-charter.md
>
> I look forward to your comments and suggestions.
>
> Thanks,
>
> Ben
>
>
> ___
> Public mailing 
> listPublic@cabforum.orghttps://lists.cabforum.org/mailman/listinfo/public
>
>
>
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

[Wikimedia-l] Re: Recognition of Wikimedians of Japan User Group

2023-10-18 Thread Wilson Oluoha

Congratulations to the new  Wikimedians of Japan User Group.

Best Wishes


On Wed, Oct 18, 2023 at 4:42 PM Affiliations Committee 
wrote:

> Hi everyone!
>
> I'm very happy to announce that the Affiliations Committee has recognized
> [1] Wikimedians of Japan User Group [2] as a Wikimedia User Group. The
> group aims to establish a national organization to promote Wikimedia
> projects and support Wikimedians in Japan.
>
> Please join me in congratulating the members of this new user group!
>
> Regards,
> Jeffrey Keefer
> Chair, Affiliations Committee
>
> [1]
> https://meta.wikimedia.org/wiki/Affiliations_Committee/Resolutions/Recognition_of_Wikimedians_of_Japan_User_Group
> [2] https://meta.wikimedia.org/wiki/Wikimedians_of_Japan_User_Group
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/BBRYSHTBT7HDUKVCF3VGZKMNZGTAKMM7/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org



-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/RPNRDZNFTZEGRTWW6RVRWZL42P7HVFZC/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[tesseract-ocr] Should box include surrounding space?

2023-10-17 Thread 'Danny Wilson' via tesseract-ocr

For purposes of training, I'm wondering if the box for a character should 
include the surrounding space.

In particular for the CJK "FULLWIDTH COMMA", should the box be the red or green 
rectangle?

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/D482C8A0-6DD7-4D1B-8A3E-C9B66CA9179C%40mac.com.


The red box is easier to render because of the info available in the font 
metrics, but after training, OCR has many problems with the full width comma 
not being translated properly.  It often translates to either nothing (no 
recognition) or translates to a latin comma.

Thanks
Danny

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/D482C8A0-6DD7-4D1B-8A3E-C9B66CA9179C%40mac.com.

Re: [blink-dev] Re: PSA: Web MIDI Permissions Prompt Change

2023-10-17 Thread Michael Wilson

Hi Alex,

We've been having trouble finishing up the engineering work, hence the
delay.  I'm trying to make some workflow adjustments now.

Best,
Michael

On Tue, Oct 17, 2023 at 2:30 PM Alex Russell 
wrote:

> What's the rationale for this change? Is it documented anywhere? I don't
> see an Explainer linked.
>
> On Tue, Oct 17, 2023, 2:11 PM 'Ajay Rahatekar' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> This feature is now planned to ship in M121.
>>
>> On Tuesday, July 18, 2023 at 12:59:23 PM UTC-7 Ajay Rahatekar wrote:
>>
>>> This feature is planned to ship in M118.
>>>
>>> On Thursday, April 13, 2023 at 10:56:40 AM UTC-7 Ajay Rahatekar wrote:
>>>
 A correction. The permission prompt will not be released on Webview at
 this time. This is planned for to be revisited later.

 On Wednesday, April 5, 2023 at 4:54:20 PM UTC-7 Ajay Rahatekar wrote:

> Contact emails
>
> mjwi...@chromium.org, sinaf...@chromium.org, hong...@chromium.org
>
> Specification
>
> https://www.w3.org/TR/webmidi/#requestmidiaccess
>
> Summary
>
> This change will require users to grant permission before they can use
> the Web MIDI API. Currently, users must explicitly grant permission to use
> SysEx messages with the Web MIDI API. With this change, users will need to
> grant a single permission to use the Web MIDI API and SysEx support. Both
> permissions will be requested in a bundled permission prompt.
>
> Blink component
>
> Blink>WebMIDI
> 
>
> Search tags
>
> MIDI , SysEx
>
> Risks
>
> Firefox already has a permissions prompt on Web MIDI API. We are
> working with known partners and plan on socializing this Chromium change.
>
> Will this feature be supported on all six Blink platforms (Windows,
> Mac, Linux, Chrome OS, Android, and Android WebView)?
>
> Yes
>
> Is this feature fully tested by web-platform-tests
> 
> ?
>
> No
>
> Requires code in //chrome?
>
> False
>
> Tracking bug
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1420307
>
> Estimated milestones
>
> We hope to ship this in Q2 2023.
>
>
> Anticipated spec changes
>
> Open questions about a feature may be a source of future web compat or
> interop issues. Please list open issues (e.g. links to known github issues
> in the project for the feature specification) whose resolution may
> introduce web compat/interop risk (e.g., changing to naming or structure 
> of
> the API in a non-backward-compatible way).
>
> None
>
>
> Link to entry on the Chrome Platform Status
>
> https://chromestatus.com/feature/5087054662205440
>
> This intent message was generated by Chrome Platform Status
> .
>
>
> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cac6d789-cb16-4a4d-b0e2-448acfca2f6an%40chromium.org
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BuAeqTPZ2ydsS1kWdeCKV6DyquMbfUAbmrMu%3D%2B43KQqYmSEBg%40mail.gmail.com.

Re: [blink-dev] Re: PSA: Web MIDI Permissions Prompt Change

2023-10-17 Thread Michael Wilson

In case you were asking about the permissions prompt change instead of the
schedule change:

This is not an API change and that's why we are sending out a PSA instead
of an intent. The nature of the permission prompt change is described in
the Chromestatus entry.

Please let me know if you have more questions.

Best,
Michael


On Tue, Oct 17, 2023 at 3:11 PM Michael Wilson 
wrote:

> Hi Alex,
>
> We've been having trouble finishing up the engineering work, hence the
> delay.  I'm trying to make some workflow adjustments now.
>
> Best,
> Michael
>
> On Tue, Oct 17, 2023 at 2:30 PM Alex Russell 
> wrote:
>
>> What's the rationale for this change? Is it documented anywhere? I don't
>> see an Explainer linked.
>>
>> On Tue, Oct 17, 2023, 2:11 PM 'Ajay Rahatekar' via blink-dev <
>> blink-dev@chromium.org> wrote:
>>
>>> This feature is now planned to ship in M121.
>>>
>>> On Tuesday, July 18, 2023 at 12:59:23 PM UTC-7 Ajay Rahatekar wrote:
>>>
>>>> This feature is planned to ship in M118.
>>>>
>>>> On Thursday, April 13, 2023 at 10:56:40 AM UTC-7 Ajay Rahatekar wrote:
>>>>
>>>>> A correction. The permission prompt will not be released on Webview at
>>>>> this time. This is planned for to be revisited later.
>>>>>
>>>>> On Wednesday, April 5, 2023 at 4:54:20 PM UTC-7 Ajay Rahatekar wrote:
>>>>>
>>>>>> Contact emails
>>>>>>
>>>>>> mjwi...@chromium.org, sinaf...@chromium.org, hong...@chromium.org
>>>>>>
>>>>>> Specification
>>>>>>
>>>>>> https://www.w3.org/TR/webmidi/#requestmidiaccess
>>>>>>
>>>>>> Summary
>>>>>>
>>>>>> This change will require users to grant permission before they can
>>>>>> use the Web MIDI API. Currently, users must explicitly grant permission 
>>>>>> to
>>>>>> use SysEx messages with the Web MIDI API. With this change, users will 
>>>>>> need
>>>>>> to grant a single permission to use the Web MIDI API and SysEx support.
>>>>>> Both permissions will be requested in a bundled permission prompt.
>>>>>>
>>>>>> Blink component
>>>>>>
>>>>>> Blink>WebMIDI
>>>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebMIDI>
>>>>>>
>>>>>> Search tags
>>>>>>
>>>>>> MIDI <https://chromestatus.com/features#tags:MIDI>, SysEx
>>>>>>
>>>>>> Risks
>>>>>>
>>>>>> Firefox already has a permissions prompt on Web MIDI API. We are
>>>>>> working with known partners and plan on socializing this Chromium change.
>>>>>>
>>>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>>>> Mac, Linux, Chrome OS, Android, and Android WebView)?
>>>>>>
>>>>>> Yes
>>>>>>
>>>>>> Is this feature fully tested by web-platform-tests
>>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>>>>>> ?
>>>>>>
>>>>>> No
>>>>>>
>>>>>> Requires code in //chrome?
>>>>>>
>>>>>> False
>>>>>>
>>>>>> Tracking bug
>>>>>>
>>>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1420307
>>>>>>
>>>>>> Estimated milestones
>>>>>>
>>>>>> We hope to ship this in Q2 2023.
>>>>>>
>>>>>>
>>>>>> Anticipated spec changes
>>>>>>
>>>>>> Open questions about a feature may be a source of future web compat
>>>>>> or interop issues. Please list open issues (e.g. links to known github
>>>>>> issues in the project for the feature specification) whose resolution may
>>>>>> introduce web compat/interop risk (e.g., changing to naming or structure 
>>>>>> of
>>>>>> the API in a non-backward-compatible way).
>>>>>>
>>>>>> None
>>>>>>
>>>>>>
>>>>>> Link to entry on the Chrome Platform Status
>>>>>>
>>>>>> https://chromestatus.com/feature/5087054662205440
>>>>>>
>>>>>> This intent message was generated by Chrome Platform Status
>>>>>> <https://chromestatus.com/>.
>>>>>>
>>>>>>
>>>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to blink-dev+unsubscr...@chromium.org.
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cac6d789-cb16-4a4d-b0e2-448acfca2f6an%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cac6d789-cb16-4a4d-b0e2-448acfca2f6an%40chromium.org?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BuAeqR2L%3DUoH0r1JdMxR3En6V8F8javgsV7%3DT8Lm7LKQ5EJ%3Dw%40mail.gmail.com.

Updated Incident Reporting Requirements

2023-10-17 Thread Ben Wilson

All,

The framework for reporting compliance incidents has been updated on the
CCADB website. See https://www.ccadb.org/cas/incident-report.  Note that
the expected contents in Sections 1 through 7 of an incident report have
changed.

Effective immediately, incident reports should use the markdown template
 and
adhere to the guidance found on the CCADB website. (Additional,
Mozilla-specific guidance is also still provided on our CA wiki -
https://wiki.mozilla.org/CA/Responding_To_An_Incident.)

Thanks,

Ben

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabnQwqck4tO_cO8xCuBBL6OpQbqMWHkhm_zZG8UvHodPQ%40mail.gmail.com.

Re: [cabfpub] Forum Ballot to Amend Server Certificate WG Charter

2023-10-17 Thread Ben Wilson via Public

All,

I am looking for at least one more endorser for this ballot.

Thanks,

Ben

On Thu, Oct 12, 2023 at 4:23 PM Ben Wilson  wrote:

> All,
>
> I am planning to introduce a Forum ballot to amend the Server Certificate
> Working Group Charter.
>
> At a high level, here are some of the proposed changes:
>
>- Section numbering added
>- "Root Certificate Issuer" voting category removed
>- Membership requirements for Certificate Consumers added
>- 6-month probationary period prior to voting membership added
>- Voting percentages and quorum clarified
>
> Because there are numerous proposed changes, here are a diff and a blob
> for your review.
>
> <http://goog_919727606>
>
> https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...85e569a43a5a2c9e5e16ce8bf1e569a98cfbd720
>
> <https://mail.google.com/mail/u/0/goog_919727603>
>
> https://github.com/cabforum/forum/blob/BenWilson-SCWG-charter-1.3/SCWG-charter.md
>
> I look forward to your comments and suggestions.
>
> Thanks,
>
> Ben
>
>
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

Re: Audit Reminder Email Summary - Intermediate Certificates

2023-10-17 Thread Kathleen Wilson

 Forwarded Message 
Subject: Summary of October 2023 Outdated Audit Statements for Intermediate 
Certs
Date: Tue, 17 Oct 2023 12:00:17 + (GMT)

CA Owner: Government of The Netherlands, PKIoverheid (Logius)
   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Services 
CA - 2023
SHA-256 Fingerprint: 
6E25C0044C7EBB30D01A4CC3D5733D734D06CD296A6823E63527F4182D528351
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Burger CA - 2023
SHA-256 Fingerprint: 
66388EE649CBE920FD949FA9B77E2AA45B5DEC4120B8FFAB371B0C9C5E38C1C1
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Persoon CA 
- 2023
SHA-256 Fingerprint: 
C8C77ECF368D73214D50D88384464339E6F8E59F34B47E39E7965F4E5787CF1D
Standard Audit Period End Date (mm/dd/): 05/31/2022

Mozilla Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1843265#c9


-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/9e3ba8c8-4def-46bb-8738-fddc80693851n%40mozilla.org.

Re: Audit Reminder Email Summary - Root Certificates

2023-10-17 Thread Kathleen Wilson

 Forwarded Message 
Subject: Summary of October 2023 Audit Reminder Emails
Date: Tue, 17 Oct 2023 12:00:33 + (GMT)

Mozilla: Overdue Audit Statements
CA Owner: SSL.com
Root Certificates:
   SSL.com TLS ECC Root CA 2022**
   SSL.com EV Root Certification Authority RSA R2**
   SSL.com EV Root Certification Authority ECC**
   SSL.com Root Certification Authority ECC**
   SSL.com Root Certification Authority RSA**
   SSL.com TLS RSA Root CA 2022**
   SSL.com Client RSA Root CA 2022**
   SSL.com Client ECC Root CA 2022**

** Audit Case in the Common CA Database is under review for this root 
certificate.

Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=f8559916-8dae-43bb-a3f3-2c8b27315707
Standard Audit Period End Date: 2022-06-30
Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=4abb6f0c-a72d-40ca-90a1-1c40b140f75a
Standard Audit Period End Date: 2022-06-30
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=46752846-7d64-424d-bdf4-9aba8564e584
BR Audit Period End Date: 2022-06-30
EV Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=adbc8c7c-930a-4dee-bcbf-b927ae2c5b3a
EV Audit Period End Date: 2022-06-30
EV Audit: 
EV Audit Period End Date: 
CA Comments: null



Mozilla: Audit Reminder
CA Owner: China Financial Certification Authority (CFCA)
Root Certificates:
   CFCA EV ROOT
Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=34ed32d4-5088-485b-af4e-52a6354528b1
Standard Audit Period End Date: 2022-07-31
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=b7433894-7c3e-4c77-9e30-30896e187d4d
BR Audit Period End Date: 2022-07-31
EV Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=3f1ae8a1-e5ac-4dea-ad68-9d1e1c522d65
EV Audit Period End Date: 2022-07-31
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Internet Security Research Group
Root Certificates:
   ISRG Root X2
   ISRG Root X1
Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=cd221a0a-aa3c-49a9-bd8a-ad336588075a
Standard Audit Period End Date: 2022-08-31
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=7f5e9f87-ecfd-4120-ae6f-e136e8637a4b
BR Audit Period End Date: 2022-08-31
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Certigna
Root Certificates:
   Certigna Root CA
   Certigna
Standard Audit: 
https://www.lsti-certification.fr/wp-content/uploads/2022/12/23_1582_ATPB_V3S.pdf
Standard Audit Period End Date: 2022-09-09
BR Audit: 
https://www.lsti-certification.fr/wp-content/uploads/2022/12/23_1582_ATPB_V3S.pdf
BR Audit Period End Date: 2022-09-09
CA Comments: null



Mozilla: Overdue Audit Statements
CA Owner: GoDaddy
Root Certificates:
   Go Daddy Class 2 CA**
   Go Daddy Root Certificate Authority - G2**
   Starfield Class 2 CA**
   Starfield Root Certificate Authority - G2**

** Audit Case in the Common CA Database is under review for this root 
certificate.

Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=fa4da3e3-2d4d-44f2-9c2d-42bd626512c8
Standard Audit Period End Date: 2022-06-30
BR Audit: https://bug1742657.bmoattachments.org/attachment.cgi?id=9296656
BR Audit Period End Date: 2022-06-30
EV Audit: https://bug1742657.bmoattachments.org/attachment.cgi?id=9296653
EV Audit Period End Date: 2022-06-30
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Microsec Ltd.
Root Certificates:
   e-Szigno Root CA 2017
   Microsec e-Szigno Root CA 2009
Standard Audit: 
https://www.hunguard.hu/wp-content/uploads/2022/11/Attestation_letter_005_ECC_v11_ds.pdf
Standard Audit Period End Date: 2022-09-09
Standard Audit: 
https://www.hunguard.hu/wp-content/uploads/2022/11/Attestation_letter_006_RSA_v11_ds.pdf
Standard Audit Period End Date: 2022-09-09
BR Audit: 
https://www.hunguard.hu/wp-content/uploads/2022/11/Attestation_letter_005_ECC_v11_ds.pdf
BR Audit Period End Date: 2022-09-09
BR Audit: 
https://www.hunguard.hu/wp-content/uploads/2022/11/Attestation_letter_006_RSA_v11_ds.pdf
BR Audit Period End Date: 2022-09-09
CA Comments: null



-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/eda1ce87-fac3-401c-8081-7aa622611ea0n%40mozilla.org.

[African Wikimedians] [WIKI LOVES AFRICA][IMPORTANT] Notification of Deadline for Rapid Grants Applications

2023-10-17 Thread Wilson Oluoha

Dear Wikimedians,

This email is to notify you that the deadline for applying for a rapid
grant for the purpose of organizing Wiki Loves Africa 2024 is *1st November
2023*.

You are encouraged to complete your applications (for those who need a
rapid grant) and submit on or before the above mentioned deadline. We would
also be grateful if you list out details of your community on the participants
page here
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities#Participating_communities_in_2024>
.

The Theme for the 2024 contest is *Africa Create* and will commence in
March 2024.

Kindly email *wil...@wikiinafrica.org * if you
have any questions or need any information and/or assistance.

Best regards


-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [WIKI LOVES AFRICA][IMPORTANT] Notification de la date limite de pour demander une rapide subvention pour le concours 2024

2023-10-17 Thread Wilson Oluoha

Chers Wikimédiens,

Cet e-mail a pour vous informer que la date limite de dépôt des demandes de
subvention rapide pour l'organisation de Wiki Loves Africa 2024 est fixée
au *1er novembre 2023*.

Nous vous encourageons à compléter vos demandes (pour ceux qui ont besoin
d'une subvention rapide) et à les soumettre au plus tard à la date limite
mentionnée ci-dessus. Nous vous serions également reconnaissants d'indiquer
les détails de votre communauté sur la page des participants ici
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities#Participating_communities_in_2024>.


Le thème du concours 2024 est *Africa Create* et débutera en mars 2024.

N'hésitez pas à envoyer un courriel à *wil...@wikiinafrica.org
* si vous avez des questions ou si vous avez
besoin d'informations et/ou d'assistance.

Cordialment

-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: [tesseract-ocr] OCR Output contains "xlz"

2023-10-16 Thread 'Danny Wilson' via tesseract-ocr

Hi Tom,

I was hoping not to introduce heuristics before scanning the images but sounds 
like the page segmentation in tesseract is not smart enough.
So from what you say, if the input image is:

a) "square-ish" : PSM 10 Single Character
b) approx. single-multiple of character height in given font: PSM 6 Single Line
c) approx. Nx character height: PSM 6 Uniform Block

For your reference, closed captions used in US, Canada, and Korea are text 
based. DVB Subtitles, used in the rest of the world, are bit map pictures.

Danny

> On 17 Oct 2023, at 04:29, Tom Morris  wrote:
> 
> It's not terribly surprising that "page" segmentation gets confused by a 
> single character, although I'm a little surprised that it came up with 
> overlapping bounding boxes. 
> 
> Since the TV image capture is presumably fixed resolution and it sounds like 
> you've only got a single font to deal with, it seems like you can tell based 
> on the image bounds whether you've got a single line (PSM 7) or more than one 
> line (PSM 6).
> 
> It's been a long time since I looked at it, but closed captioning is usually 
> encoded in the signal digitally in a side band channel, which would be a much 
> simpler way to extract it.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/6727242B-34CA-4234-BF1E-746510705817%40mac.com.

[Translators-l] Re: Ready for translation: Tech News #42 (2023)

2023-10-16 Thread Nick Wilson (Quiddity)

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 19 languages) to 1,094 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 42

2023-10-16 Thread Nick Wilson (Quiddity)

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/42. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - The Unified login
   
   system's edge login should now be fixed for some browsers (Chrome, Edge,
   Opera). This means that if you visit a new sister project wiki, you should
   be logged in automatically without the need to click "Log in" or reload the
   page. Feedback on whether it's working for you is welcome. [1]
   
   - Edit notices
   

   are now available within the MobileFrontend/Minerva skin. This feature was
   inspired by the gadget on English Wikipedia
   . See
   more details in T316178 .

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 17 October. It
   will be on non-Wikipedia wikis and some Wikipedias from 18 October. It will
   be on all wikis from 19 October (calendar
   ).

*Future changes*

   - In 3 weeks, in the Vector 2022 skin, code related to addPortletLink
   and #p-namespaces that was deprecated one year ago will be removed. If
   you notice tools that should appear next to the "Discussion" tab are then
   missing, please tell the gadget's maintainers to see instructions in the
   Phabricator task .

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute
 •
Translate
 •
Get help  • Give feedback
 • Subscribe or unsubscribe
.*
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

[Kernel-packages] [Bug 2032761] Re: Bluetooth headset microphone not working after upgrade to Kernel 6.2

2023-10-16 Thread Matt Wilson

I can confirm the same behavior (unable to select on the same headphones
(Sony WH-1000XM5). When I look at the device in the "pacmd list-cards"
output I see:

profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: yes)
handsfree_head_unit: Handsfree Head Unit (HFP) (priority 30, 
available: no)

I've been able to get it working more reliably when I have the blueman
package installed. Usually "systemctl restart bluetooth" does the trick.
"pacmd list-cards" says:

profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: yes)
handsfree_head_unit: Handsfree Head Unit (HFP) (priority 30, 
available: unknown)
off: Off (priority 0, available: yes)

And I'm able to run:

pacmd set-card-profile bluez_card.[my-mac-address-redacted]
handsfree_head_unit

and it works as it used to.

I don't know if blueman is doing something under the covers to make the
handsfree profile work more reliabily?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2032761

Title:
  Bluetooth headset microphone not working after upgrade to Kernel 6.2

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  Since my Ubuntu (22.04) was upgraded to Kernel 6.2.0-26 , my
  headphones (Sony WH-1000XM5) can no longer connect with the headset
  (handsfree_head_unit) profile (a2dp_sink, i.e. audio only, works
  fine). Booting back into kernel 5 (5.19.0-50-generic) "fixes" the
  issue.

  Trying to change profile:

  ➜  ~ pacmd set-card-profile bluez_card.AC_80_0A_1A_D6_56 off
  ➜  ~ pacmd set-card-profile bluez_card.AC_80_0A_1A_D6_56 handsfree_head_unit
  Failed to set card profile to 'handsfree_head_unit'.
  sysctl logs (not very helpful):

  Aug 15 17:33:40 pulseaudio[4088]: Refused to switch profile to
  handsfree_head_unit: Not connected

  ---

  Confirmed online that this also affects, at least, another headset
  (Sony WH-1000XM4) and still present on Kernel 6.4.11-060411 -
  https://askubuntu.com/questions/1482493/upgrade-to-kernel-6-2-broke-
  bluetooth-headset-microphone

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Wed Aug 23 08:54:32 2023
  InstallationDate: Installed on 2023-03-20 (155 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2032761/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14


On 10/16/2023 4:59 PM, Tamás Cservenák wrote:

You'd use Plexus?  In 2023?


I don't know what I'd use. I'm asking. I haven't written a Maven plugin 
yet. I'm just reading the latest documentation, and the [Plugin 
Developers Centre](https://maven.apache.org/plugin-developers/) seems to 
say at https://maven.apache.org/maven-jsr330.html that I either have to 
use Plexus or JSR-330, and you just told me I can't use JSR-330, so that 
leaves Plexus.


If I'm not understanding the documentation correctly, please point out 
what I'm missing.



…
In other words: whatever is "managed by sisu, should be max Java 14"
bytecode in current release Maven versions. Naturally, this does NOT apply
to ANY code, just those being JSR330 (and Mojo) annotated.


Maybe you are saying I can write a Maven plugin without using Plexus or 
JSR-330? So dependency injection in Maven Plugins is optional? The page 
at https://maven.apache.org/maven-jsr330.html makes it seem like 
dependency injection in a Maven Plugin is a common thing.


(Maybe your announcement makes perfect sense to those who have written 
Maven plugins before. In the meantime I'm reading the online 
documentation and trying to understand how this will affect me once I 
write a plugin.)


Garret


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14


On 10/16/2023 4:36 PM, Tamás Cservenák wrote:

…

no, this applies to "sisu managed components" ONLY. So not ALL the code
needs to be downgraded, only those annotated with JSR330 annotations.


After reading and trying to understand 
https://maven.apache.org/maven-jsr330.html , does this mean I'll have to 
use the old-style [Plexus 
annotations](https://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/), 
and then just convert to JSR-330 once Maven updates Sisu?


In other words, if I use Plexus annotations I'll be fine with Java 17, 
and have no limitations or problems from not using JSR-330 annotations?


Garret


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Tamás, thank you very much for the clarification. The previous 
announcement sounded like it applied to every Maven plugin.


Garret

On 10/16/2023 4:36 PM, Tamás Cservenák wrote:

Hej Garret,

no, this applies to "sisu managed components" ONLY. So not ALL the code
needs to be downgraded, only those annotated with JSR330 annotations.
And yes, Maven 3.9.6 could upgrade Sisu to the latest version, basically
lifting this limitation.

HTH
T

On Mon, Oct 16, 2023 at 9:19 PM Garret Wilson 
wrote:


Wait, really? I have an annotation processor being developed now with
Java 17, and parts of it soon will need to move to a Maven plugin. This
means that I'll have to downgrade all the code to Java 14?? In 2023?

Are there any workarounds? The issue #94 you mentioned has already been
closed as addressed. Are you saying that Sisu 0.9.0.M2 fixes the
problem? Can't Maven 3.x simply upgrade to that and release v3.9.6?

Garret

On 10/16/2023 3:45 PM, Tamás Cservenák wrote:

Howdy,

This mail is just a general response (initiated by those asking me in
private): it seems that the Maven team "forgot" to emphasize an important
question on the Maven site, while it is becoming more and more pressing,
especially as Java 17 is out long time ago, and Java 21 is here as well.

In short: if you develop Java Mojo (a Maven plugin), that you plan to use
with current "stable" Maven versions (3.9.x and maybe 3.8,x), your
maven-plugin packaged artifact MUST NOT use Java bytecode that is newer
than Java 14!

What happens is that Eclipse Sisu is unable to inspect the component
class/bytecode 14+ in question (despite is listed on index, in
META-INF/sisu/javax.inject.Named file), and it will silently ignore the
component, "pretend" like it's absent (and error reported will be like
Guice does not find the component to be injected). This can be seen, if

you

make Sisu DEBUG (-Dsisu.debug on maven cli).

Cause of limitation is the version of Eclipse Sisu used in Maven (the
JSR330 container implementation Maven uses internally), see
https://github.com/eclipse/sisu.inject/issues/94. Eclipse Sisu versions
0.3.5 (used in Maven 3.8.x and 3.9.x) uses ASM that is able to scan
bytecode only up to Java 14. Latest release 0.9.0.M2 (used in Maven4) is
covering this up to Java21, while this issue above should fully cover,

and

will probably be updated in Maven4 once released.

So, for plugin devs targeting Maven3, best is to not exceed Java 14

(safest

Java11) bytecode version for components (Mojos and JSR330 components).

HTH
Tamas


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

Wait, really? I have an annotation processor being developed now with 
Java 17, and parts of it soon will need to move to a Maven plugin. This 
means that I'll have to downgrade all the code to Java 14?? In 2023?


Are there any workarounds? The issue #94 you mentioned has already been 
closed as addressed. Are you saying that Sisu 0.9.0.M2 fixes the 
problem? Can't Maven 3.x simply upgrade to that and release v3.9.6?


Garret

On 10/16/2023 3:45 PM, Tamás Cservenák wrote:

Howdy,

This mail is just a general response (initiated by those asking me in
private): it seems that the Maven team "forgot" to emphasize an important
question on the Maven site, while it is becoming more and more pressing,
especially as Java 17 is out long time ago, and Java 21 is here as well.

In short: if you develop Java Mojo (a Maven plugin), that you plan to use
with current "stable" Maven versions (3.9.x and maybe 3.8,x), your
maven-plugin packaged artifact MUST NOT use Java bytecode that is newer
than Java 14!

What happens is that Eclipse Sisu is unable to inspect the component
class/bytecode 14+ in question (despite is listed on index, in
META-INF/sisu/javax.inject.Named file), and it will silently ignore the
component, "pretend" like it's absent (and error reported will be like
Guice does not find the component to be injected). This can be seen, if you
make Sisu DEBUG (-Dsisu.debug on maven cli).

Cause of limitation is the version of Eclipse Sisu used in Maven (the
JSR330 container implementation Maven uses internally), see
https://github.com/eclipse/sisu.inject/issues/94. Eclipse Sisu versions
0.3.5 (used in Maven 3.8.x and 3.9.x) uses ASM that is able to scan
bytecode only up to Java 14. Latest release 0.9.0.M2 (used in Maven4) is
covering this up to Java21, while this issue above should fully cover, and
will probably be updated in Maven4 once released.

So, for plugin devs targeting Maven3, best is to not exceed Java 14 (safest
Java11) bytecode version for components (Mojos and JSR330 components).

HTH
Tamas



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: CCADB Update: Audit Team Qualifications

2023-10-16 Thread Ben Wilson

All,

The update to the CCADB, which adds an Audit Team Qualifications document
upload field to the AUDITS tab of  “Add/Update Root Request” cases, is now
complete. (This is mainly for audits that do not include this information
directly in audit statements.)  Under the AUDITS tab of  “Add/Update Root
Request” cases, there are now sections for "Audit Firm" and "Audit Team".

Instructions for this new upload functionality in the CCADB are available
here
<https://docs.google.com/document/d/12U4az-hjYDC_aWsVn8-Y5vVmJ10inVziAxrQoxP-hfI/edit#bookmark=id.q9frfps8jur5>.

As noted in a separate email
<https://groups.google.com/a/ccadb.org/g/public/c/hvhra7upKMU/m/zItEhBVLBgAJ>,
on October 25, 2023, we expect to add a new section 5.2 to the CCADB Policy
(Audit Firm and Audit Team Qualifications), which recounts the expected
contents of a statement of Audit Team Qualifications. Until then, please
refer to each separate root store policy for its audit team qualification
requirements.

Thank you

- Ben, on behalf of the CCADB Steering Committee

On Sun, Oct 15, 2023 at 11:26 AM Ben Wilson  wrote:

> All,
>
> Tomorrow, Monday, October 16, 2023, we will be updating the AUDITS tab of
> “Add/Update Root Request” Cases in the CCADB to provide upload
> functionality for Audit Team Qualifications documents (mainly for WebTrust
> audits, as ETSI audit teams already include this information directly in
> audit statements).
>
> CA Owners should not be impacted during this update and can perform
> routine CCADB functions as expected.
>
> We will send a separate email when the update is complete.
>
> Thank you,
>
> Ben, on behalf of the CCADB Steering Committee
>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtaZVzsqBB4FT0-kO0myt-KQd7U%3Dzchdpxbjt3TQjwaFzuA%40mail.gmail.com.

Re: [tesseract-ocr] OCR Output contains "xlz"

2023-10-16 Thread 'Danny Wilson' via tesseract-ocr

The command line did not get included in my last mail.  Sending again now.


$ tesseract sub0089w.png debugOut -l ARYuanB5-MD --dpi 72 --psm 6   -c 
classify_debug_level=1

Processing word with lang ARYuanB5-MD at:Bounding box=(3,45)->(33,56)
Trying word using lang ARYuanB5-MD, oem 1
Best choice: accepted=0, adaptable=0, done=1 : Lang result : Ll : R=10.3645, 
C=-11.8365, F=1, Perm=2, xht=[0,3.40282e+38], ambig=0
str L   l
1 new words better than 0 old words: r: 10.3645 v 0 c: -11.8365 v 0 valid dict: 
0 v 0

Processing word with lang ARYuanB5-MD at:Bounding box=(3,3)->(56,58)
Trying word using lang ARYuanB5-MD, oem 1
Best choice: accepted=1, adaptable=0, done=1 : Lang result : 對 : R=3.09071, 
C=-1.8713, F=1, Perm=2, xht=[0,3.40282e+38], ambig=0
str 對
state:  1
1 new words better than 0 old words: r: 3.09071 v 0 c: -1.8713 v 0 valid dict: 
0 v 0

$ cat debugOut.txt
Ll
對


-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/79D5D3A6-C41C-4A4F-9DCD-3B9FD2AB215B%40mac.com.

Re: [tesseract-ocr] OCR Output contains "xlz"

2023-10-16 Thread 'Danny Wilson' via tesseract-ocr

After running tesseract with various debug switches activated, I've found that 
it thinks there are two characters in the image and trying OCR on each of them.

Changing the page segmentation mode changes the output:
PSM 6 (single uniform block of text) : outputs garbage plus correct character
PSM 7 (single text line) : works correctly. 
PSM 8 (single word) : works correctly

The debug output is below.

This raises a new issue: the input data (TV subtitles) are a mixture of 1 or 2 
line text blocks. And a 1-line text block might be a single character in this 
case.

So the ideal page segmentation mode should be 6, no? But looking at the debug 
output, it thinks there are two characters in the input image...

That doesn't sound like a training issue but rather some problem with how it 
identifies glyphs in the input image...


-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/28D1A233-AD19-4541-95E3-F31422000F67%40mac.com.


> $ tesseract sub0089w.png debugOut -l ARYuanB5-MD --dpi 72 --psm 6   -c 
> classify_debug_level=1
> 
> Processing word with lang ARYuanB5-MD at:Bounding box=(3,45)->(33,56)
> Trying word using lang ARYuanB5-MD, oem 1
> Best choice: accepted=0, adaptable=0, done=1 : Lang result : Ll : R=10.3645, 
> C=-11.8365, F=1, Perm=2, xht=[0,3.40282e+38], ambig=0
> str   L   l
> 1 new words better than 0 old words: r: 10.3645 v 0 c: -11.8365 v 0 valid 
> dict: 0 v 0
> 
> Processing word with lang ARYuanB5-MD at:Bounding box=(3,3)->(56,58)
> Trying word using lang ARYuanB5-MD, oem 1
> Best choice: accepted=1, adaptable=0, done=1 : Lang result : 對 : R=3.09071, 
> C=-1.8713, F=1, Perm=2, xht=[0,3.40282e+38], ambig=0
> str   對
> state:1
> 1 new words better than 0 old words: r: 3.09071 v 0 c: -1.8713 v 0 valid 
> dict: 0 v 0
> 
> $ cat debugOut.txt
> Ll
> 對


> On 16 Oct 2023, at 09:08, 'Danny Wilson' via tesseract-ocr 
>  wrote:
> 
> I guess I am the author... ARYuanB5-MD is the font.
> 
> For further background, the stock tessdata_best/chi_tra.traineddata did not 
> do a good job at all on the text I'm trying to recognize.  
> 
> So I retrained:
> - copying the existing Chinese wordlist and added additional characters and 
> sentences (total 47,000 lines)
> - rendered ground truth images (with the special font) and box files
> - used lang data from "chi_tra" (config, unicharset, Han.xx, Latin.xx, 
> radical-stroke etc)
> - ran lstmtraining with 30,000 iterations

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/28D1A233-AD19-4541-95E3-F31422000F67%40mac.com.

Re: [tesseract-ocr] OCR Output contains "xlz"

2023-10-15 Thread 'Danny Wilson' via tesseract-ocr

I guess I am the author... ARYuanB5-MD is the font.

For further background, the stock tessdata_best/chi_tra.traineddata did not do 
a good job at all on the text I'm trying to recognize.  

So I retrained:
- copying the existing Chinese wordlist and added additional characters and 
sentences (total 47,000 lines)
- rendered ground truth images (with the special font) and box files
- used lang data from "chi_tra" (config, unicharset, Han.xx, Latin.xx, 
radical-stroke etc)
- ran lstmtraining with 30,000 iterations

lstmtraining completed with BCER of 0.846:

> At iteration 2689/3/30013, mean rms=0.244%, delta=0.426%, BCER 
> train=1.425%, BWER train=3.900%, skip ratio=0.000%, New worst BCER = 1.425 
> wrote checkpoint.
> Finished! Selected model with minimal training error rate (BCER) = 0.846


Then copy the output ARYuanB5-MD.traineddata to tessdata directory.

With that traineddata, OCR is very good on the input text... except for the "對" 
character, which outputs the extra "xlz".

Neither the ground-truth nor the wordlist has "xlz" anywhere in it.  

Any suggestions on how to track this down?  

Thanks




> On 15 Oct 2023, at 22:20, Zdenko Podobny  wrote:
> 
> Seam like you should put this question to the author of language data 
> "ARYuanB5-MD"...
> 
> Zdenko
> 
> 
> ne 15. 10. 2023 o 15:44 'Danny Wilson' via tesseract-ocr 
> mailto:tesseract-ocr@googlegroups.com>> 
> napísal(a):
>> Running tesseract on a single Chinese character "對" outputs the character, 
>> but also the text "xlz".  
>> 
>> Command line: 
>> tesseract sub0089w.png debugOut -l ARYuanB5-MD --dpi 72 --psm 6 -c 
>> preserve_interword_spaces=1
>> 
>> The output is two lines:
>> xlz
>> 對
>> 
>> It used to output "sMz"  but after retraining several times with the 
>> specific font in use, it now outputs "xlz".
>> 
>> Why?
>> 
>> I've attached the image file in question...
>> 
>> 
>> 
>> (Searching the source code, the file universalambigs.h has a line " xlZ le 
>> 1" which is similar, but not exact to the errant text I'm finding)
>> 
>> Thank you.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "tesseract-ocr" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tesseract-ocr+unsubscr...@googlegroups.com 
>> <mailto:tesseract-ocr+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tesseract-ocr/76ed2f78-e10f-4b9f-8d61-30f4b0f333dbn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tesseract-ocr/76ed2f78-e10f-4b9f-8d61-30f4b0f333dbn%40googlegroups.com?utm_medium=email_source=footer>.
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "tesseract-ocr" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/tesseract-ocr/V7Rqwv2tnOk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> tesseract-ocr+unsubscr...@googlegroups.com 
> <mailto:tesseract-ocr+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tesseract-ocr/CAJbzG8y1_y%3Diw8uCEw5Z3km%3DApZ5%2BFFudjqMKV_HO9QJ41FNyw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/tesseract-ocr/CAJbzG8y1_y%3Diw8uCEw5Z3km%3DApZ5%2BFFudjqMKV_HO9QJ41FNyw%40mail.gmail.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/59227072-0E73-47BD-B841-52F3B5646412%40mac.com.

CCADB Update: Audit Team Qualifications

2023-10-15 Thread Ben Wilson

All,

Tomorrow, Monday, October 16, 2023, we will be updating the AUDITS tab of
“Add/Update Root Request” Cases in the CCADB to provide upload
functionality for Audit Team Qualifications documents (mainly for WebTrust
audits, as ETSI audit teams already include this information directly in
audit statements).

CA Owners should not be impacted during this update and can perform routine
CCADB functions as expected.

We will send a separate email when the update is complete.

Thank you,

Ben, on behalf of the CCADB Steering Committee

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtaZmM7S%3DCiR2%3DN1p2AwX6topYKi08OTDn87gx0gy819ufA%40mail.gmail.com.

Re: [ccp4bb] Assistant Professor in Structural Biology, University of Nebraska-Lincoln

2023-10-15 Thread Mark Wilson

Hi Gerlind,
To clarify, the position is tenure-leading, where tenure dossiers are typically 
submitted in the 5th year of employment.  If tenure is granted, then the 
position is a continuous appointment.  The 9-month language in the ad refers to 
the academic year-typically faculty can either choose to take their salary over 
either 9 or 12 months.   Faculty can also raise additional funds for salary 
over the summer via grants.  This is common (nearly universal) in the US 
system. Importantly, this is _not_ simply a 9-month contract position, which 
would not make sense for an Assistant Professor.

Best regards,
Mark

Mark A. Wilson (he/him)
Professor
Department of Biochemistry/Redox Biology Center
University of Nebraska
N118 Beadle Center
1901 Vine St.
Lincoln, NE 68588

From: Gerlind Sulzenbacher 
Date: Sunday, October 15, 2023 at 10:15 AM
To: Mark Wilson , CCP4BB@JISCMAIL.AC.UK 

Subject: Re: [ccp4bb] Assistant Professor in Structural Biology, University of 
Nebraska-Lincoln
Non-NU Email

Dear Mark,

thank you for posting this job offer, probably very interesting for people 
currently unemployed.

Personally, I feel that working conditions and job offers in the scientific 
field have deteriorated considerably in recent years.
I've always been shocked by one-year job offers involving international 
movements.
Now we seem to be down at job offers for 9 months.

>From a human point of view, I find this extremely worrying.
Sorry to pollute the mailing list with my personal opinions.

All the best.
Gerlind


On 15/10/2023 16:46, Mark Wilson wrote:
Dear Colleagues,

The Department of Biochemistry at the University of Nebraska-Lincoln (UNL) 
invites applications for a tenure-track nine-month (academic year) faculty 
position at the rank of Assistant Professor. Areas of particular interest 
include but are not limited to time-resolved approaches to understanding 
macromolecular function, multiscale imaging, and integrated computational and 
experimental approaches to structural biology. Researchers at UNL have 
collaborations with national user facilities pioneering time-resolved X-ray 
diffraction techniques and have established a state-of-the-art cryo-EM facility 
housing a Thermo Scientific Glacios 200 keV Cryo TEM equipped with a Falcon 4i 
direct electron detector camera, a Selectris zero-loss energy filter, and 
capability for micro-electron diffraction of crystalline samples. The new 
cryo-EM facility is part of a strategic growth plan at UNL and complements 
existing strengths in X-ray crystallography, biophysics, and computation at UNL.

Review of applications will begin November 15, 2023 and continue until the 
position is filled or the search is closed. To view details of the position and 
the application, go to https://employment.unl.edu, requisition F_230175 or 
visit https://employment.unl.edu/postings/88408. Click “Apply for this Job” and 
complete the information form. As an EO/AA employer, the University of Nebraska 
considers qualified applicants for employment without regard to race, color, 
ethnicity, national origin, sex, pregnancy, sexual orientation, gender 
identity, religion, disability, age, genetic information, veteran status, 
marital status, and/or political affiliation. See 
https://www.unl.edu/equity/notice-nondiscrimination.


Best regards,
Mark

Mark A. Wilson (he/him)
Professor
Department of Biochemistry/Redox Biology Center
University of Nebraska
N118 Beadle Center
1901 Vine St.
Lincoln, NE 68588



To unsubscribe from the CCP4BB list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=CCP4BB=1<https://urldefense.com/v3/__https:/www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=CCP4BB=1__;!!PvXuogZ4sRB2p-tU!Bav1hl7rOBTJ55aiWQJffSIG_gw4KPgMy-qLUQCUbhZ-k4fKBhpQxyMoBersHEFXrgHD558g184sfDS-O5RkYNknP_tYVxXeDQ$>



--

Gerlind Sulzenbacher

Architecture et Fonction des Macromolécules Biologiques

UMR7257 CNRS, Aix-Marseille Université

Case 932

163 Avenue de Luminy

13288 Marseille cedex 9

France

Tel +33 413 94 95 27

E-mail: 
gerlind.sulzenbac...@univ-amu.fr<mailto:gerlind.sulzenbac...@univ-amu.fr>



To unsubscribe from the CCP4BB list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=CCP4BB=1

This message was issued to members of www.jiscmail.ac.uk/CCP4BB, a mailing list 
hosted by www.jiscmail.ac.uk, terms & conditions are available at 
https://www.jiscmail.ac.uk/policyandsecurity/

[ccp4bb] Assistant Professor in Structural Biology, University of Nebraska-Lincoln

2023-10-15 Thread Mark Wilson

Dear Colleagues,

The Department of Biochemistry at the University of Nebraska-Lincoln (UNL) 
invites applications for a tenure-track nine-month (academic year) faculty 
position at the rank of Assistant Professor. Areas of particular interest 
include but are not limited to time-resolved approaches to understanding 
macromolecular function, multiscale imaging, and integrated computational and 
experimental approaches to structural biology. Researchers at UNL have 
collaborations with national user facilities pioneering time-resolved X-ray 
diffraction techniques and have established a state-of-the-art cryo-EM facility 
housing a Thermo Scientific Glacios 200 keV Cryo TEM equipped with a Falcon 4i 
direct electron detector camera, a Selectris zero-loss energy filter, and 
capability for micro-electron diffraction of crystalline samples. The new 
cryo-EM facility is part of a strategic growth plan at UNL and complements 
existing strengths in X-ray crystallography, biophysics, and computation at UNL.

Review of applications will begin November 15, 2023 and continue until the 
position is filled or the search is closed. To view details of the position and 
the application, go to https://employment.unl.edu, requisition F_230175 or 
visit https://employment.unl.edu/postings/88408. Click “Apply for this Job” and 
complete the information form. As an EO/AA employer, the University of Nebraska 
considers qualified applicants for employment without regard to race, color, 
ethnicity, national origin, sex, pregnancy, sexual orientation, gender 
identity, religion, disability, age, genetic information, veteran status, 
marital status, and/or political affiliation. See 
https://www.unl.edu/equity/notice-nondiscrimination.


Best regards,
Mark

Mark A. Wilson (he/him)
Professor
Department of Biochemistry/Redox Biology Center
University of Nebraska
N118 Beadle Center
1901 Vine St.
Lincoln, NE 68588



To unsubscribe from the CCP4BB list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=CCP4BB=1

This message was issued to members of www.jiscmail.ac.uk/CCP4BB, a mailing list 
hosted by www.jiscmail.ac.uk, terms & conditions are available at 
https://www.jiscmail.ac.uk/policyandsecurity/

Automatic installation of Debian 11 on ARM64

2023-10-15 Thread Frank Wilson

Hi,

Has anyone successfully used the "automatic installation" option for the
Debian 11 installer? I was expecting this option to give me screen where I
can enter the URL to my preseed file (which it does on x86), but all I get
on arm64 is a black screen and a blinking cursor. There are no apparent
error messages.

Any tips on how to debug further would be appreciated.

Thanks,

Frank

[tesseract-ocr] OCR Output contains "xlz"

2023-10-15 Thread 'Danny Wilson' via tesseract-ocr

Running tesseract on a single Chinese character "對" outputs the character, 
but also the text "xlz".  

Command line: 
tesseract sub0089w.png debugOut -l ARYuanB5-MD --dpi 72 --psm 6 -c 
preserve_interword_spaces=1

The output is two lines:
xlz
對

It used to output "sMz"  but after retraining several times with the 
specific font in use, it now outputs "xlz".

Why?

I've attached the image file in question...

[image: sub0089w.png]

(Searching the source code, the file universalambigs.h has a line " xlZ le 
1" which is similar, but not exact to the errant text I'm finding)

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tesseract-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tesseract-ocr/76ed2f78-e10f-4b9f-8d61-30f4b0f333dbn%40googlegroups.com.

Re: escaping single quote for Exec Maven Plugin `exc.args`

2023-10-15 Thread Garret Wilson

On 10/15/2023 9:24 AM, Garret Wilson wrote:

On 10/15/2023 1:31 AM, Alexander Kriegisch wrote:

…
Let us settle on only using double quotes to enclose arguments
containing spaces. Then, we do not need to escape single quotes and
can use them literally. But we do need to escape nested double quotes.

…
Just for a moment, forget about Bash/PowerShell/CMD escaping rules.
What are escaping the rules of the Maven Exec Plugin? What does it
consider a delimiter for indicating multiple arguments?

I guess at this point it's easier just to dig into the source code. The
relevant plugin source code seems to be here (after a cursory glance):

https://github.com/mojohaus/exec-maven-plugin/blob/ddefecff84ebbf6427a6bb9eb6c2fdb332bfac7c/src/main/java/org/codehaus/mojo/exec/ExecMojo.java#L600

It appears to be using `CommandLineUtils.translateCommandline( argsProp
)` to parse the string input into an array. A little more searching
seems to indicate that that utility is here:

https://github.com/codehaus-plexus/plexus-utils/blob/d4f0d2de40c5d6cb5d80c8a199fa4f32a4e59879/src/main/java/org/codehaus/plexus/util/cli/CommandLineUtils.java#L348C85-L348C85

That code uses `StringTokenizer` constructed using `new
StringTokenizer(toProcess, "\"\' ", true)`. So yes, Alexander, it does
indeed appear to be using both single quotes and and double quotes as
delimiters.

So next is the question of escaping. The
[documentation](https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/util/StringTokenizer.html)
for `StringTokenizer` says nothing about escaping. I glanced (extremely
quickly) over the source code for `StringTokenizer`, and I don't see it
translating any escape sequences.

Thus if escaping is happening, it would have to be in
`CommandLineUtils.translateCommandline( argsProp )`. And it would be
possible, as it uses the `StringTokenizer` option to return delimiters.
But glancing (again very quickly) over the `CommandLineUtils` code, I
don't see any escaping handling at all.

Thus my conclusion is that the Maven Exec Plugin handles either single
quotes or double quotes as the delimiter, but /does not handle escaping
in either case/. You pick one or the other, and cross your fingers that
the given argument does not contain that delimiter, because there's no
way to escape it ahead of time.

All the discussion of escaping at the Bash/PowerShell/CMD level, while
useful in its own context, has absolutely zero bearing on the issue I
was raising, which was: how to escape a quote at the Maven Exec Plugin
level. The answer seems to be: you can't.

(I glanced over the source code extremely fast, so I could have missed
something. If so please point it out to me!)

Garret

Re: escaping single quote for Exec Maven Plugin `exc.args`

2023-10-15 Thread Garret Wilson

On 10/15/2023 1:31 AM, Alexander Kriegisch wrote:

…
Let us settle on only using double quotes to enclose arguments containing
spaces. Then, we do not need to escape single quotes and can use them
literally. But we do need to escape nested double quotes.

Let's make sure we don't confuse whether we're talking about escaping
occurring at the Bash level, or at the Maven Exec Plugin level. I [made
the
mistake](https://stackoverflow.com/questions/77294556/bash-single-quote-elements-of-array-and-concatenate-using-space?noredirect=1#comment136265886_77294609)
of confusing the two at first.

Just for a moment, forget about Bash/PowerShell/CMD escaping rules. What
are escaping the rules of the Maven Exec Plugin? What does it consider a
delimiter for indicating multiple arguments? Are you saying that Maven
Exec Plugin will accept either single or double quote for delimiter? I'm
not saying it doesn't (I haven't seen the code), but I wouldn't want to
assume it does, either.

For example, let's assume I use whatever escaping rules are appropriate
for my shell, and I do it 100% correctly, so that the Maven Exec Plugin
sees `test "foo\" bar" 'more stuff'`. (I'm using the backtick here to
delimit the string.) The backslash is not part of the Bash-level
escaping—it's literally what the Maven Exec Plugin sees (i.e. I probably
escaped it using `\\\"` or something at the Bash level). How does Maven
Exec Plugin interpret that string? As one argument? As two? As three?

And where is the Maven Exec Plugin documentation for this? The delimiter
rules of the Maven Exec Plugin would be completely independent of the
shell escaping rules. (This is the same as if I passed a single quote
using `` from XML; once it got to the Maven Exec Plugin in a Maven
property, it would be irrelevant how it was escaped in XML.)

In UNIX-like shells like Bash, a double quote is escaped by a backslash:

-Dexec.args="one \"it's OK\" three"

OK, so following the discussion above, the Maven Exec Plugin will see
the string `one "it's OK" three` (again using a backtick here in this
email as a somewhat arbitrary delimiter for the entire string). Bash is
now out of the picture. How does the Maven Exec Plugin interpret the
string `one "it's OK" three`, and where is that documented?

Garret

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

escaping single quote for Exec Maven Plugin `exc.args`

2023-10-14 Thread Garret Wilson

Here's a fun one for your weekend. As you know from (almost) the 
beginning of time we could invoke a Java application using Maven using 
the Maven Exec Plugin, as in the following (although Maven's `--quiet` 
may be a recent addition):


```bash
mvn exec:java -Dexec.mainClass="com.example.MyApplication" 
-Dexec.args="test" --quiet

```

This passes a single command-line argument to my Java `main()` method 
args array: "test". If I want to pass a string with a space, I put it in 
single quotes, like this:


```bash
mvn exec:java -Dexec.mainClass="com.example.MyApplication" 
-Dexec.args="'foo bar'" --quiet

```

That passes a single string "foo bar" to my application `main()` method 
args array.


Now … what if I want to pass a single string "foo'bar" (note just one 
single quote in the string) as a single string to my `main()` method 
args array? is there some way to escape the single quote? The 
[documention](https://www.mojohaus.org/exec-maven-plugin/java-mojo.html#commandlineArgs) 
doesn't give any clues.


I guess I could look at the Exec Maven Plugin source code (if it's 
available), but that would take half a day and I've already spent half 
of today going down other rabbit holes. So I thought I'd ask here to see 
if anyone knew; otherwise I'll investigate another day when I'm 
refreshed (or just put a temporary note in my Bash script about this 
corner case, but that's not really my style).


Garret


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[Translators-l] Re: Ready for translation: Tech News #42 (2023)

2023-10-13 Thread Nick Wilson (Quiddity)

On Thu, Oct 12, 2023 at 3:28 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/42
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F42=page
>

The text of the newsletter is now final.

Nothing has changed since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Intent to Approve Commscope's CA Inclusion Request

2023-10-13 Thread Ben Wilson

All,
We recently concluded a 6-week public discussion on the CCADB list of the
request for inclusion of root CA certificates by Commscope.  See
https://groups.google.com/a/ccadb.org/g/public/c/HVwBXDw6GnU/m/q2WRYe_TBQAJ.
In accordance with Step 7 of the Mozilla inclusion process,
https://wiki.mozilla.org/CA/Application_Process, this is notice that we
intend to approve Commscope's request. This begins a 7-day "last call" for
objections.
Thanks,
Ben

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtaZcbq3ZzZXetT_0WUfQCCcDRyz%3DxJBhEUDKS7Lkj05Gmw%40mail.gmail.com.

[African Wikimedians] [Wiki Loves Africa] Heures de bureau aujourd'hui soir

2023-10-13 Thread Wilson Oluoha

Chers Wikimédiens,

Nous avons des heures de bureau pour Wiki Loves Africa aujourd'hui (*vendredi
13*), nous fournirons de l'aide pour les demandes de subventions rapides
pour 2024. Vous trouverez les détails ci-dessous:

Office hours en français

   - Vendredi 13, Octobre 2023 (17:00 UTC)
  - Cliquez pour rejoindre la réunion sur Zoom
  <https://us02web.zoom.us/j/89701654679>


Pour plus d'informations, veuillez consulter la page des communautés
participantes ici
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities>
.

A bientôt,

Wilson
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[Translators-l] Ready for translation: Tech News #42 (2023)

2023-10-12 Thread Nick Wilson (Quiddity)

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/42

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F42=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html

-- 
Nick "Quiddity" Wilson (he/him)
Community Relations Specialist
Wikimedia Foundation
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[cabfpub] Forum Ballot to Amend Server Certificate WG Charter

2023-10-12 Thread Ben Wilson via Public

All,

I am planning to introduce a Forum ballot to amend the Server Certificate
Working Group Charter.

At a high level, here are some of the proposed changes:

   - Section numbering added
   - "Root Certificate Issuer" voting category removed
   - Membership requirements for Certificate Consumers added
   - 6-month probationary period prior to voting membership added
   - Voting percentages and quorum clarified

Because there are numerous proposed changes, here are a diff and a blob for
your review.


https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...85e569a43a5a2c9e5e16ce8bf1e569a98cfbd720


https://github.com/cabforum/forum/blob/BenWilson-SCWG-charter-1.3/SCWG-charter.md

I look forward to your comments and suggestions.

Thanks,

Ben
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

[African Wikimedians] [Wiki Loves Africa] Annonce du thème 2024 et des Heures de bureau demain soir

2023-10-12 Thread Wilson Oluoha

Chers Wikimédiens,

Nous vous informons que le vote pour la sélection du thème 2024
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024/Theme_voting>
est maintenant terminé et qu'après avoir pris connaissance de vos votes et
de tous vos commentaires, nous vous annonçons le nouveau thème du concours
2024:


*Le thème de Wiki Loves Africa 2024 est Africa Create.*

Vous vous êtes tous exprimés et nous vous avons écoutés. Une discussion
informelle sur ce thème aura lieu demain (vendredi 13) aux heures de
bureau, où nous fournirons une assistance pour les demandes de subventions
rapides pour 2024. Vous trouverez les détails ci-dessous:

Office hours en français

   - Vendredi 13, Octobre 2023 (17:00 UTC)
  - Cliquez pour rejoindre la réunion sur Zoom
  <https://us02web.zoom.us/j/89701654679>



Pour plus d'informations, veuillez consulter la page des communautés
participantes ici
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities>
.

Cordialement,


-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] Announcing 2024 Theme and Office Hours

2023-10-12 Thread Wilson Oluoha

Dear Wikimedians,

This is to inform you that the vote to select the 2024 theme
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024/Theme_voting>
has now closed and having viewed your votes and read all your comments, we
hereby announce the new theme for the 2024 contest:

*The theme for Wiki Loves Africa 2024 is Africa Create.*

You all spoke and we listened. There will be an informal discussion around
the theme at the office Hours tomorrow (Fri. 13) where we will be providing
assistance for rapid grants applications for 2024. Please find details
below:

Office Hours in English

   - Fri. 13, October 2023 (16:00 UTC)
  - Click to join zoom meeting <https://us02web.zoom.us/j/89701654679>

Office hours en français

   - Vendredi 13, Octobre 2023 (17:00 UTC)
  - Cliquez pour rejoindre la réunion sur Zoom
  <https://us02web.zoom.us/j/89701654679>


For more information, please consult the participating communities page here
<https://meta.wikimedia.org/wiki/Wiki_Loves_Africa_2024/Participating_communities>
.

Best regards

-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: [cabf_validation] EVG 9.8.2. cabfOrganizationIdentifier

2023-10-11 Thread Clint Wilson via Validation

Hi Tim,

I had thought the point of including cabfOrganizationIdentifier was to enable 
deprecation of subject:organizationIdentifier, rather than the inverse. It 
seems it would be minimally appropriate to understand the discussions and/or 
actions ETSI has taken post SC17 to address the topic of adoption of the 
CABFOrganizationIdentifier (for example, an explanation of why its adoption was 
rejected or additional background on why it’s unsuited for ETSI’s use-case(s)) 
prior to considering moving forward with such a ballot. 
FWIW, I attempted to find something along those lines, but was unable to (most 
likely due to insufficient Google-fu, but perhaps such discussions are not 
public or perhaps they have not occurred).

Thanks!
-Clint

> On Oct 11, 2023, at 12:57 PM, Tim Hollebeek via Validation 
>  wrote:
> 
>  
> Ballot SC17 added the cabfOrganizationIdentifer, which duplicates the 
> information encoded in the subject:organizationIdentifier field, just in a 
> different format/encoding.  The subject:orgID field is standardized by ETSI 
> and used in the processing of eIDAS certificates; on the other hand, to the 
> best of my knowledge, no software has ever been written that processes or 
> uses the cabfOrganzationIdentifier field.
>  
> Is there a good reason to keep requiring the field?  It was added as a 
> political compromise to get ballot SC17 passed, but that’s not a good reason 
> to keep around a clunky alternative encoding for information already present 
> in the certificate, in an obscure bespoke ASN.1 format that no tools support 
> or use.
>  
> I’m tempted to write a quick ballot to make it optional, so CAs can start 
> leaving it out.
>  
> -Tim
> ___
> Validation mailing list
> Validation@cabforum.org 
> https://lists.cabforum.org/mailman/listinfo/validation

smime.p7s
Description: S/MIME cryptographic signature
___
Validation mailing list
Validation@cabforum.org
https://lists.cabforum.org/mailman/listinfo/validation

[Wikimedia-l] [Wikimedia Announcements] [Wiki Loves Africa] - Announcing Results and Statistics for 2023

Dear Wikimedians,


I hope this email finds you well.

I am excited to share with you the amazing results and statistics of the
2023 Wiki Loves Africa contest. Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023> aims to
celebrate the richness, diversity and beauty of Africa by encouraging
participants and contributors to upload their media to Wikimedia Commons
for subsequent use on Wikipedia.


The 2023 iteration of the project, which ran from 1st March to 30th April
with the theme *Climate & Weather*, received an overwhelming response, with
a total
<https://ptools.toolforge.org/uploadersincat.php?category=Images+from+Wiki+Loves+Africa+2023>
of *13,385* submissions from* 785* uploaders representing *53 African
countries
<https://commons.wikimedia.org/wiki/Category:Images_from_Wiki_Loves_Africa_2023>*.
It's been truly inspiring to witness the continental response to the
concept of climate and weather as it concerns Africa through this
initiative.


Today, we are excited to announce the *winning media entries
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/Winners>*,
which were selected by our esteemed panel of judges. Also, this year, we
introduced a Video jury (first ever in the Wikimedia space) to help us
select the winning uploads for the various video categories.



*The International prizes:*

*Photography:*
*1st prize:* US$2000 -  Auyo village flood by Sani Maikatanga
<https://commons.wikimedia.org/wiki/File:Auyo_village_flood_06.jpg>
 (Nigeria)
*2nd prize:* US$1500 - Stormy day in somalia by Mohamed Nasr
<https://commons.wikimedia.org/wiki/File:Stormy_day_in_somalia.jpg>
 (Somalia)
*3rd prize:* US$1000 -  Kids and the river by Mohammed Osman
<https://commons.wikimedia.org/wiki/File:Kids_and_the_river.jpg> (Sudan)




*Media (Video, Audio, Graphics, Photo Essays):*
*Best audio :* US$ 750 - Change Immersion by Abdullahi Tanimu Abubakar
<https://commons.wikimedia.org/wiki/File:Change-immersion.ogg> (Nigeria)
*Best video prize :* US$ 1,000 - GOOD YESTERDAYS WIKI LOVES AFRICA 2023 by
Green Wilfred Somoni
<https://commons.wikimedia.org/wiki/File:GOOD_YESTERDAYS_WIKI_LOVES_AFRICA_2023_By_Green_Wilfred_Somoni.webm>
 (Nigeria)
*Africa Environment Video Prize* (Best video representation of the impact
of climate change) : US$ 2,000 - Last Stand by Alamin Mohammed
<https://commons.wikimedia.org/wiki/File:Last_Stand.webm>
*Africa Environment Special Collection Prize:* Collection of 13 videos  by
Wiki Loves Africa Fan Club Cote d'Ivoire
<https://commons.wikimedia.org/wiki/Category:Wiki_Loves_Africa_2023_C%C3%B4te_d%27Ivoire_Fan_Club>



*Useful links:*


Click to see best photos from the contest
<https://commons.wikimedia.org/wiki/Category:Best_images_from_Wiki_Loves_Africa_2023>
.


Click to view Quality photos from the contest
<https://commons.wikimedia.org/wiki/Category:Quality_images_from_Wiki_Loves_Africa_2023>
.


Click to see the Top 20 photo considerations from the contest.
<https://youtu.be/njrJyQwLeBI?feature=shared>


Click to view the National winners from several local contests.
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/National_winners>



On a final note, we would like to acknowledge the support of all our
partners, jury, organizers and volunteers whose tireless efforts,
assistance and contributions made this year's contest a success. We are
immensely grateful for your dedication and passion to supporting Wiki Loves
Africa. We look forward to your continued participation in future endeavors.


If you have any questions or would like further information, please do not
hesitate to reach out via wil...@wikiinafrica.org. Thank you once again for
your interest and support.



Warm regards,


*Wilson*

On behalf of the International team Wiki Loves Africa
___
Please note: all replies sent to this mailing list will be immediately directed 
to Wikimedia-l, the public mailing list of the Wikimedia community. For more 
information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
___
WikimediaAnnounce-l mailing list -- wikimediaannounc...@lists.wikimedia.org
To unsubscribe send an email to wikimediaannounce-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/5YH2W7FTN2PRLD3DP7P23JNOK4YUQ67B/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia Announcements] [Wiki Loves Africa] - Announcing Results and Statistics for 2023

Dear Wikimedians,


I hope this email finds you well.

I am excited to share with you the amazing results and statistics of the
2023 Wiki Loves Africa contest. Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023> aims to
celebrate the richness, diversity and beauty of Africa by encouraging
participants and contributors to upload their media to Wikimedia Commons
for subsequent use on Wikipedia.


The 2023 iteration of the project, which ran from 1st March to 30th April
with the theme *Climate & Weather*, received an overwhelming response, with
a total
<https://ptools.toolforge.org/uploadersincat.php?category=Images+from+Wiki+Loves+Africa+2023>
of *13,385* submissions from* 785* uploaders representing *53 African
countries
<https://commons.wikimedia.org/wiki/Category:Images_from_Wiki_Loves_Africa_2023>*.
It's been truly inspiring to witness the continental response to the
concept of climate and weather as it concerns Africa through this
initiative.


Today, we are excited to announce the *winning media entries
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/Winners>*,
which were selected by our esteemed panel of judges. Also, this year, we
introduced a Video jury (first ever in the Wikimedia space) to help us
select the winning uploads for the various video categories.



*The International prizes:*

*Photography:*
*1st prize:* US$2000 -  Auyo village flood by Sani Maikatanga
<https://commons.wikimedia.org/wiki/File:Auyo_village_flood_06.jpg>
 (Nigeria)
*2nd prize:* US$1500 - Stormy day in somalia by Mohamed Nasr
<https://commons.wikimedia.org/wiki/File:Stormy_day_in_somalia.jpg>
 (Somalia)
*3rd prize:* US$1000 -  Kids and the river by Mohammed Osman
<https://commons.wikimedia.org/wiki/File:Kids_and_the_river.jpg> (Sudan)




*Media (Video, Audio, Graphics, Photo Essays):*
*Best audio :* US$ 750 - Change Immersion by Abdullahi Tanimu Abubakar
<https://commons.wikimedia.org/wiki/File:Change-immersion.ogg> (Nigeria)
*Best video prize :* US$ 1,000 - GOOD YESTERDAYS WIKI LOVES AFRICA 2023 by
Green Wilfred Somoni
<https://commons.wikimedia.org/wiki/File:GOOD_YESTERDAYS_WIKI_LOVES_AFRICA_2023_By_Green_Wilfred_Somoni.webm>
 (Nigeria)
*Africa Environment Video Prize* (Best video representation of the impact
of climate change) : US$ 2,000 - Last Stand by Alamin Mohammed
<https://commons.wikimedia.org/wiki/File:Last_Stand.webm>
*Africa Environment Special Collection Prize:* Collection of 13 videos  by
Wiki Loves Africa Fan Club Cote d'Ivoire
<https://commons.wikimedia.org/wiki/Category:Wiki_Loves_Africa_2023_C%C3%B4te_d%27Ivoire_Fan_Club>



*Useful links:*


Click to see best photos from the contest
<https://commons.wikimedia.org/wiki/Category:Best_images_from_Wiki_Loves_Africa_2023>
.


Click to view Quality photos from the contest
<https://commons.wikimedia.org/wiki/Category:Quality_images_from_Wiki_Loves_Africa_2023>
.


Click to see the Top 20 photo considerations from the contest.
<https://youtu.be/njrJyQwLeBI?feature=shared>


Click to view the National winners from several local contests.
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/National_winners>



On a final note, we would like to acknowledge the support of all our
partners, jury, organizers and volunteers whose tireless efforts,
assistance and contributions made this year's contest a success. We are
immensely grateful for your dedication and passion to supporting Wiki Loves
Africa. We look forward to your continued participation in future endeavors.


If you have any questions or would like further information, please do not
hesitate to reach out via wil...@wikiinafrica.org. Thank you once again for
your interest and support.



Warm regards,


*Wilson*

On behalf of the International team Wiki Loves Africa
___
Please note: all replies sent to this mailing list will be immediately directed 
to Wikimedia-l, the public mailing list of the Wikimedia community. For more 
information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
___
WikimediaAnnounce-l mailing list -- wikimediaannounce-l@lists.wikimedia.org
To unsubscribe send an email to wikimediaannounce-l-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] - Annonce des résultats et des statistiques pour 2023

Chers Wikimédiens,

J'espère que ce mail vous trouvera en bonne santé.

Je suis ravi de partager avec vous les résultats et les statistiques du
concours Wiki Loves Africa 2023. Wiki Loves Africa vise à célébrer la
richesse, la diversité et la beauté de l'Afrique en encourageant les
participants et les contributeurs à télécharger leurs médias sur Wikimedia
Commons pour une utilisation ultérieure sur Wikipédia.


La version 2023 du projet, qui s'est déroulée du 1er mars au 30 avril sur
le thème du climat et de la météo, a reçu une réponse massive, avec un
total de 13 385 soumissions de la part de 785 téléchargeurs représentant 53
pays africains. Il a été très stimulant d'assister à la réponse du
continent au concept de climat et de météo en ce qui concerne l'Afrique à
travers cette initiative.


Aujourd'hui, nous sommes heureux d'annoncer les contributions médiatiques
gagnantes, qui ont été sélectionnées par notre estimé panel de juges. Cette
année, nous avons également introduit un jury vidéo (une première dans
l'espace Wikimedia) pour nous aider à sélectionner les téléchargements
gagnants dans les différentes catégories vidéo.



*Les prix internationaux :*

*Photography:*
*1er** prize:* US$2000 -  Auyo village flood by Sani Maikatanga
<https://commons.wikimedia.org/wiki/File:Auyo_village_flood_06.jpg>
(Nigeria)
*2nd prize:* US$1500 - Stormy day in somalia by Mohamed Nasr
<https://commons.wikimedia.org/wiki/File:Stormy_day_in_somalia.jpg>
(Somalia)
*3rd prize:* US$1000 -  Kids and the river by Mohammed Osman
<https://commons.wikimedia.org/wiki/File:Kids_and_the_river.jpg> (Sudan)




*Media (Video, Audio, Graphics, Photo Essays):*
*Best audio :* US$ 750 - Change Immersion by Abdullahi Tanimu Abubakar
<https://commons.wikimedia.org/wiki/File:Change-immersion.ogg> (Nigeria)
*Best video prize :* US$ 1,000 - GOOD YESTERDAYS WIKI LOVES AFRICA 2023 by
Green Wilfred Somoni
<https://commons.wikimedia.org/wiki/File:GOOD_YESTERDAYS_WIKI_LOVES_AFRICA_2023_By_Green_Wilfred_Somoni.webm>
(Nigeria)
*Africa Environment Video Prize* (Best video representation of the impact
of climate change) : US$ 2,000 - Last Stand by Alamin Mohammed
<https://commons.wikimedia.org/wiki/File:Last_Stand.webm>
*Africa Environment Special Collection Prize:* Collection of 13 videos  by
Wiki Loves Africa Fan Club Cote d'Ivoire
<https://commons.wikimedia.org/wiki/Category:Wiki_Loves_Africa_2023_C%C3%B4te_d%27Ivoire_Fan_Club>



*Liens utiles:*


Cliquez pour voir les meilleures photos du concours.
<https://commons.wikimedia.org/wiki/Category:Best_images_from_Wiki_Loves_Africa_2023>
.


Cliquez pour voir les photos de qualité du concours
<https://commons.wikimedia.org/wiki/Category:Quality_images_from_Wiki_Loves_Africa_2023>
.


Cliquez pour voir les 20 meilleures photos du concours.
<https://youtu.be/njrJyQwLeBI?feature=shared>


Cliquez pour voir les gagnants nationaux de plusieurs concours locaux.
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/National_winners>



Enfin, nous tenons à remercier tous nos partenaires, le jury, les
organisateurs et les bénévoles pour leurs efforts inlassables, leur aide et
leurs contributions qui ont fait du concours de cette année un succès. Nous
vous sommes immensément reconnaissants de votre dévouement et de votre
passion pour Wiki Loves Africa. Nous espérons que vous continuerez à
participer à nos futurs projets.


Si vous avez des questions ou si vous souhaitez obtenir de plus amples
informations, n'hésitez pas à nous contacter à l'adresse
wil...@wikiinafrica.org. Nous vous remercions une nouvelle fois de votre
intérêt et de votre soutien.



Cordialement,


*Wilson*

Pour le Wiki Loves Africa
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] - Announcing Results and Statistics for 2023

Dear Wikimedians,


I hope this email finds you well.

I am excited to share with you the amazing results and statistics of the
2023 Wiki Loves Africa contest. Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023> aims to
celebrate the richness, diversity and beauty of Africa by encouraging
participants and contributors to upload their media to Wikimedia Commons
for subsequent use on Wikipedia.


The 2023 iteration of the project, which ran from 1st March to 30th April
with the theme *Climate & Weather*, received an overwhelming response, with
a total
<https://ptools.toolforge.org/uploadersincat.php?category=Images+from+Wiki+Loves+Africa+2023>
of *13,385* submissions from* 785* uploaders representing *53 African
countries
<https://commons.wikimedia.org/wiki/Category:Images_from_Wiki_Loves_Africa_2023>*.
It's been truly inspiring to witness the continental response to the
concept of climate and weather as it concerns Africa through this
initiative.


Today, we are excited to announce the *winning media entries
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/Winners>*,
which were selected by our esteemed panel of judges. Also, this year, we
introduced a Video jury (first ever in the Wikimedia space) to help us
select the winning uploads for the various video categories.



*The International prizes:*

*Photography:*
*1st prize:* US$2000 -  Auyo village flood by Sani Maikatanga
<https://commons.wikimedia.org/wiki/File:Auyo_village_flood_06.jpg>
(Nigeria)
*2nd prize:* US$1500 - Stormy day in somalia by Mohamed Nasr
<https://commons.wikimedia.org/wiki/File:Stormy_day_in_somalia.jpg>
(Somalia)
*3rd prize:* US$1000 -  Kids and the river by Mohammed Osman
<https://commons.wikimedia.org/wiki/File:Kids_and_the_river.jpg> (Sudan)




*Media (Video, Audio, Graphics, Photo Essays):*
*Best audio :* US$ 750 - Change Immersion by Abdullahi Tanimu Abubakar
<https://commons.wikimedia.org/wiki/File:Change-immersion.ogg> (Nigeria)
*Best video prize :* US$ 1,000 - GOOD YESTERDAYS WIKI LOVES AFRICA 2023 by
Green Wilfred Somoni
<https://commons.wikimedia.org/wiki/File:GOOD_YESTERDAYS_WIKI_LOVES_AFRICA_2023_By_Green_Wilfred_Somoni.webm>
(Nigeria)
*Africa Environment Video Prize* (Best video representation of the impact
of climate change) : US$ 2,000 - Last Stand by Alamin Mohammed
<https://commons.wikimedia.org/wiki/File:Last_Stand.webm>
*Africa Environment Special Collection Prize:* Collection of 13 videos  by
Wiki Loves Africa Fan Club Cote d'Ivoire
<https://commons.wikimedia.org/wiki/Category:Wiki_Loves_Africa_2023_C%C3%B4te_d%27Ivoire_Fan_Club>



*Useful links:*


Click to see best photos from the contest
<https://commons.wikimedia.org/wiki/Category:Best_images_from_Wiki_Loves_Africa_2023>
.


Click to view Quality photos from the contest
<https://commons.wikimedia.org/wiki/Category:Quality_images_from_Wiki_Loves_Africa_2023>
.


Click to see the Top 20 photo considerations from the contest.
<https://youtu.be/njrJyQwLeBI?feature=shared>


Click to view the National winners from several local contests.
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/National_winners>



On a final note, we would like to acknowledge the support of all our
partners, jury, organizers and volunteers whose tireless efforts,
assistance and contributions made this year's contest a success. We are
immensely grateful for your dedication and passion to supporting Wiki Loves
Africa. We look forward to your continued participation in future endeavors.


If you have any questions or would like further information, please do not
hesitate to reach out via wil...@wikiinafrica.org. Thank you once again for
your interest and support.



Warm regards,


*Wilson*

On behalf of the International team Wiki Loves Africa
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[Commons-l] [Wiki Loves Africa] - Announcing Results and Statistics for 2023

Dear Wikimedians,


I hope this email finds you well.

I am excited to share with you the amazing results and statistics of the
2023 Wiki Loves Africa contest. Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023> aims to
celebrate the richness, diversity and beauty of Africa by encouraging
participants and contributors to upload their media to Wikimedia Commons
for subsequent use on Wikipedia.


The 2023 iteration of the project, which ran from 1st March to 30th April
with the theme *Climate & Weather*, received an overwhelming response, with
a total
<https://ptools.toolforge.org/uploadersincat.php?category=Images+from+Wiki+Loves+Africa+2023>
of *13,385* submissions from* 785* uploaders representing *53 African
countries
<https://commons.wikimedia.org/wiki/Category:Images_from_Wiki_Loves_Africa_2023>*.
It's been truly inspiring to witness the continental response to the
concept of climate and weather as it concerns Africa through this
initiative.


Today, we are excited to announce the *winning media entries
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/Winners>*,
which were selected by our esteemed panel of judges. Also, this year, we
introduced a Video jury (first ever in the Wikimedia space) to help us
select the winning uploads for the various video categories.



*The International prizes:*

*Photography:*
*1st prize:* US$2000 -  Auyo village flood by Sani Maikatanga
<https://commons.wikimedia.org/wiki/File:Auyo_village_flood_06.jpg>
(Nigeria)
*2nd prize:* US$1500 - Stormy day in somalia by Mohamed Nasr
<https://commons.wikimedia.org/wiki/File:Stormy_day_in_somalia.jpg>
(Somalia)
*3rd prize:* US$1000 -  Kids and the river by Mohammed Osman
<https://commons.wikimedia.org/wiki/File:Kids_and_the_river.jpg> (Sudan)




*Media (Video, Audio, Graphics, Photo Essays):*
*Best audio :* US$ 750 - Change Immersion by Abdullahi Tanimu Abubakar
<https://commons.wikimedia.org/wiki/File:Change-immersion.ogg> (Nigeria)
*Best video prize :* US$ 1,000 - GOOD YESTERDAYS WIKI LOVES AFRICA 2023 by
Green Wilfred Somoni
<https://commons.wikimedia.org/wiki/File:GOOD_YESTERDAYS_WIKI_LOVES_AFRICA_2023_By_Green_Wilfred_Somoni.webm>
(Nigeria)
*Africa Environment Video Prize* (Best video representation of the impact
of climate change) : US$ 2,000 - Last Stand by Alamin Mohammed
<https://commons.wikimedia.org/wiki/File:Last_Stand.webm>
*Africa Environment Special Collection Prize:* Collection of 13 videos  by
Wiki Loves Africa Fan Club Cote d'Ivoire
<https://commons.wikimedia.org/wiki/Category:Wiki_Loves_Africa_2023_C%C3%B4te_d%27Ivoire_Fan_Club>



*Useful links:*


Click to see best photos from the contest
<https://commons.wikimedia.org/wiki/Category:Best_images_from_Wiki_Loves_Africa_2023>
.


Click to view Quality photos from the contest
<https://commons.wikimedia.org/wiki/Category:Quality_images_from_Wiki_Loves_Africa_2023>
.


Click to see the Top 20 photo considerations from the contest.
<https://youtu.be/njrJyQwLeBI?feature=shared>


Click to view the National winners from several local contests.
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2023/National_winners>



On a final note, we would like to acknowledge the support of all our
partners, jury, organizers and volunteers whose tireless efforts,
assistance and contributions made this year's contest a success. We are
immensely grateful for your dedication and passion to supporting Wiki Loves
Africa. We look forward to your continued participation in future endeavors.


If you have any questions or would like further information, please do not
hesitate to reach out via wil...@wikiinafrica.org. Thank you once again for
your interest and support.



Warm regards,


*Wilson*

On behalf of the International team Wiki Loves Africa
___
Commons-l mailing list -- commons-l@lists.wikimedia.org
To unsubscribe send an email to commons-l-le...@lists.wikimedia.org

[Wikimedia-l] [Wiki Loves Africa] - Announcing Results and Statistics for 2023