[Wikimedia-l] WMBE Wikimedia Belgium 2023 reports

2024-02-01 Thread Geert Van Pamel
cial/2023> WMBE Financial report 2023 Geert Van Pamel ___ 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 Pub

[Wikimedia-l] Re: Who is the editor with the longest editing streak? Find out!

2023-07-31 Thread Geert Van Pamel
Could be interesting to add a column "active streak" yes/no Geert Van Pamel -Oorspronkelijk bericht- Van: Kunal Mehta Verzonden: maandag 31 juli 2023 10:09 Aan: wikimedia-l@lists.wikimedia.org Onderwerp: [Wikimedia-l] Re: Who is the editor with the longest editing streak? Fin

[Wikimedia-l] New Board of Directors for Wikimedia Belgium

2022-07-04 Thread Geert Van Pamel
On 18 June, Wikimedia Belgium held its <https://be.wikimedia.org/wiki/2022-06-18_General_Assembly> annual general assembly. The annual accounts were approved and a new board was elected. We bid farewell to AnneJea as board member and thank her for her many years of commitment. Geert Van

[Wikimedia-l] Re: Building Partnerships and Identifying and Addressing Harassment Online self-guided courses now available on WikiLearn platform

2022-05-14 Thread Geert Van Pamel
Mike, The new course platform is really "intended to serve the entire Wikimedia movement!" - opposite to what you believe; you have access via your Wikimedia account. The platform is a real MOOC platform, unlike other MediaWiki powered sites. Geert

[MediaWiki-l] Re: Request

2022-04-14 Thread Geert Van Pamel
Can the following help? https://lists.wikimedia.org/hyperkitty/ ___ MediaWiki-l mailing list -- mediawiki-l@lists.wikimedia.org To unsubscribe send an email to mediawiki-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/mediawiki-l.

[Wikimedia-l] Re: Small gratitude to our fellow wikimedians

2021-11-09 Thread Geert Van Pamel
volunteers that are no longer amongst us via https://en.wikipedia.org/wiki/Special:ListUsers. Geert Van Pamel ___ Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and

[Wikimedia-l] Annual report from Wikimedia Belgium

2021-06-23 Thread Geert Van Pamel
y/2020 * <https://meta.wikimedia.org/wiki/Grants:Simple/Applications/Wikimedia_Belgium/2020/Endreport/Spending> https://meta.wikimedia.org/wiki/Grants:Simple/Applications/Wikimedia_Belgium/2020/Endreport/Spending Geert Van Pamel ___ Wikimed

[MediaWiki-l] Newsletter Wikimedia Belgium September 2020

2020-10-15 Thread Geert Van Pamel
See https://be.wikimedia.org/wiki/Newsletter/2020-09 ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Re: [Wikimedia-l] Comment Open on U.S. Open Access Policy

2020-04-20 Thread Geert Van Pamel
Perfect statement: only one correction: you need to negate the following phrase... And, if they are *un*able to read and cite it... If every country would vote an equivalent law for Free Knowledge, the world would become a better place to live... -- Geert Van Pamel

[Wikimedia-l] Announcement from the Board of Wikimedia Belgium (WMBE)

2019-07-30 Thread Geert Van Pamel
WMBE was founded for: activities to get more free knowledge.   -- The Board of Wikimedia Belgium (WMBE) -- Geert Van Pamel, Chair of Wikimedia Belgium [1] https://lists.wikimedia.org/pipermail/wikimedia-l/2019-June/092878.html [2] https://meta.wikimedia.org/wiki

Re: [Wikimedia-l] New board for Wikimedia Belgium + evaluation behaviour WMF

2019-06-21 Thread Geert Van Pamel
ing into account certain handicaps like hard-hearing, or autism. That being said, please stop discussing this specific conflict publicly, because a lot of important details are missing, are single-sided interpretations, or even completely wrong. -- Geert Van Pamel, chair of W

[Wikimedia-l] New board for Wikimedia Belgium + evaluation behaviour WMF

2019-06-20 Thread Geert Van Pamel
ing into account certain handicaps like hard-hearing, or autism. That being said, please stop discussing this specific conflict publicly, because a lot of important details are missing, are single-sided interpretations, or even completely wrong. -- Geert Van Pamel, chair of W

[MediaWiki-l] New board for Wikimedia Belgium + evaluation behaviour WMF

2019-06-20 Thread Geert Van Pamel
ing into account certain handicaps like hard-hearing, or autism. That being said, please stop discussing this specific conflict publicly, because a lot of important details are missing, are single-sided interpretations, or even completely wrong. -- Geert Van Pamel, chair of W

Re: [MediaWiki-l] Error converting MediaWiki database from 1.4.5 to 1.5.8

2017-06-28 Thread Geert Van Pamel
to 1.5.8 On 26/06/17 01:54, Geert Van Pamel wrote: > I try to convert a MediaWiki database from 1.4.5 to 1.5.8 (yes I know > I am a bit late. but up to now the database has perfectly served me ever > since 2005). We now want to migrate to a new Linux server, so we want to > up

[MediaWiki-l] Error converting MediaWiki database from 1.4.5 to 1.5.8

2017-06-25 Thread Geert Van Pamel
sql_query( $sql, $this->mConn ); } else { $ret = mysql_unbuffered_query( $sql, $this->mConn ); } return $ret; Geert Van Pamel ___ MediaWiki-l mailing list To uns

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-04-13 Thread Geert Van Pamel
No errors on SIP debug output. File Attachments RFC-3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-28 Thread Geert Van Pamel
> On March 22, 2014, 4:39 p.m., Olle E Johansson wrote: > > I don't see what happens with the phone-context argument. Shouldn't we pass > > that on as a channel variable? > > Geert Van Pamel wrote: > We return this into the hostport. > > Geert Van

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-24 Thread Geert Van Pamel
> On March 22, 2014, 4:39 p.m., Olle E Johansson wrote: > > I don't see what happens with the phone-context argument. Shouldn't we pass > > that on as a channel variable? > > Geert Van Pamel wrote: > We return this into the hostport. > > Geert Van

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-23 Thread Geert Van Pamel
> On March 22, 2014, 4:39 p.m., Olle E Johansson wrote: > > I don't see what happens with the phone-context argument. Shouldn't we pass > > that on as a channel variable? > > Geert Van Pamel wrote: > We return this into the hostport. > > Geert Van

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-22 Thread Geert Van Pamel
ly, visit: https://reviewboard.asterisk.org/r/3349/#review11227 ----------- On March 22, 2014, 2:08 p.m., Geert Van Pamel wrote: > > --- > This is an automatically generated e-mail.

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-22 Thread Geert Van Pamel
> On March 22, 2014, 4:39 p.m., Olle E Johansson wrote: > > I don't see what happens with the phone-context argument. Shouldn't we pass > > that on as a channel variable? > > Geert Van Pamel wrote: > We return this into the hostport. According to RFC 396

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-22 Thread Geert Van Pamel
> On March 21, 2014, 7:01 p.m., Corey Farrell wrote: > > /trunk/channels/sip/reqresp_parser.c, line 130 > > <https://reviewboard.asterisk.org/r/3349/diff/7-8/?file=56285#file56285line130> > > > > This needs to blank both variables: > > userinfo

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-22 Thread Geert Van Pamel
-- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3349/#review11323 --- On March 22, 2014, 2:08 p.m., Geert Van Pamel wrote: > > -

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-22 Thread Geert Van Pamel
l number nor a phone-context. - Geert --- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3349/#review11314 --- On March 22, 2014,

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-22 Thread Geert Van Pamel
- RFC-3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Bandwidth and Colocation P

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-21 Thread Geert Van Pamel
997185193} > > Return userinfo when RFC 3966 does not include neither global number, nor context. In this case hostport will not be available. Avoid NULL string reference segmentation fault by adding explicit test && (userinfo != NULL) before strstr test. - Geert

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-21 Thread Geert Van Pamel
3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Bandwidth and Colocation Provided by http://w

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-20 Thread Geert Van Pamel
ext= or isub= parameters remain unparsed; but should be further parsed from userinfo when the RFC 3966 will be fully implemented (with ISDN or PSTN local extensions). - Geert --- This is an automatically generated e-mail. To rep

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-20 Thread Geert Van Pamel
l URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Bandwidth and Colocation Provided by http:/

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-19 Thread Geert Van Pamel
2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update opt

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-17 Thread Geert Van Pamel
This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3349/#review11237 ----------- On March 17, 2014, 8:01 p.m., Geert Van Pamel wrote: > > ---

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-17 Thread Geert Van Pamel
- Geert --- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3349/#review11241 --- On March 17, 2014, 8:01 p.m., Geert Va

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-17 Thread Geert Van Pamel
erisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev m

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-15 Thread Geert Van Pamel
ttachments RFC-3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Ban

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-15 Thread Geert Van Pamel
ttachments RFC-3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ -- Bandwidth and

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-15 Thread Geert Van Pamel
SIP debug output. File Attachments RFC-3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert

Re: [asterisk-dev] [Code Review] 3349: Implement RFC-3966 TEL URI incoming INVITE

2014-03-13 Thread Geert Van Pamel
ut. File Attachments RFC-3966 tel URI patch https://reviewboard.asterisk.org/media/uploaded/files/2014/03/13/cad7a996-88c1-47fe-a2a9-cc6987af3b75__rfc-3966-tel-uri-patch-diff.txt Thanks, Geert Van Pamel -- _ --

Re: [asterisk-dev] [Code Review] 3250: chan_sip: Add incoming tel: uri support (rfc3966)

2014-02-26 Thread Geert Van Pamel
(Updated Feb. 23, 2014, 12:17 p.m.) > > > Review request for Asterisk Developers. > > > Bugs: ASTERISK-17179 > https://issues.asterisk.org/jira/browse/ASTERISK-17179 > > > Repository: Asterisk > > > Description > --- > > This patch is

[Bug 159251] Re: Atheros Wifi on laptop compaq nc6000 does not work

2008-08-20 Thread Geert Van Pamel
With Ubuntu Hardy Heron 8.04 the Atheros Wifi card is finally recognized. I did manage to make a connection with WEP. WPA still does not work. With other Linux distributions the Atheros card does not work at all. I only got a CISCO PMCIA card working. And only with WEP, never with WPA. Thanks for

[Bug 159251] Atheros Wifi on laptop compaq nc6000 does not work

2007-11-01 Thread Geert Van Pamel
Public bug reported: I cannot get a WEP or WPA Wifi connection with the builtin Athoros Wifi modem in compap nc6000 laptop. With a Cisco PMCIA card, I do not have this problem. tail /var/log/messages Nov 1 10:05:29 debian kernel: [490644.012000] wifi1: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps No

[Bug 159251] Re: Atheros Wifi on laptop compaq nc6000 does not work

2007-11-01 Thread Geert Van Pamel
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/10238484/Dependencies.txt -- Atheros Wifi on laptop compaq nc6000 does not work https://bugs.launchpad.net/bugs/159251 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for