Hi,

I'd like to officially contact all our teams to learn about potential
issues that might affect your work. I would love to learn how you
organise / share your workload. If you do some regular meetings - be it
on IRC, video conference or whatever I'm interested in joining one of
your next meetings. I included individuel Uploaders of python3-defaults package into this contact. I'm aware that you are not necessarily
identify yourself as DPT members but I think this package is related
and I would love to see you as well in the DebConf BoF (see below) and
if you could also answer my questions below.

Like previous DPLs, I'm open to any inquiries or requests for
assistance. I personally prefer public discussion whenever possible, as
they can benefit a wider audience. You can find a list of contact
options at the bottom of my page on people.d.o[1].

I prefer being offline when I'm away from my keyboard, so I don't carry
a phone. In urgent situations, I can provide the number of my dumb
phone, though it may not always be within reach. Feel free to ping me
via email if I don't respond promptly to ensure I address your concerns.

Please let me know whether I can do something for you. I'm fine joining
your IRC channel if needed but please invite me in case I should be
informed about some urgent discussion there since I normally do not lurk
on this channel.

I'd also like to inform you that I've registered a BoF for DebConf24 in
Busan with the following description:

This BoF is an attempt to gather as much as possible teams inside
Debian to exchange experiences, discuss workflows inside teams, share
their ways to attract newcomers etc.

Each participant team should prepare a short description of their work
and what team roles (“openings”) they have for new contributors. Even
for delegated teams (membership is less fluid), it would be good to
present the team, explain what it takes to be a team member, and what
steps people usually go to end up being invited to participate. Some
other teams can easily absorb contributions from salsa MRs, and at some
point people get commit access. Anyway, the point is that we work on the
idea that the pathway to become a team member becomes more clear from an
outsider point-of-view.

I'm sure not everybody will be able to travel this distance but it would
be great if you would at least consider joining that BoF remotely. I'll
care for a somehow TimeZone aware scheduling - if needed we'll organise
two BoFs to match all time zones. I'm also aware that we have pretty
different teams and it might make sense to do some infrastructure
related BoF with your team and other teams that are caring for Debian infrastructure.

I have some specific questions to the Debian Python team. I'm really interested into individual answers from single contributors either here
on this list or in private.

- Do you feel good when doing your work in Debian Python team?
- Do you consider the workload of your team equally shared amongst its
members?
- Do you have some strategy to gather new contributors for your team?
- Can you give some individual estimation how many hours per week you
are working on your tasks in youre team? Does this fit the amount of
time you can really afford for this task?
- I guess you will have your regular DPT meeting at DebConf (which I
intend to join). What do you think about the general team meeting
I registered.
- In the beginning of this year there was a change in the policy of DPT.
I'd like to hear your opinion about:
* The process how it went (possibly with suggestions to do better)
* The final result after a couple of months
(I'm specifically interested also in the opinion of people who were
not happy about the change.)
- Since a long time we try to migrate from Python3.11 to Python3.12.
* What are your thoughts about the transition process?
* Can you identify some blockers?
* Do you have some suggestions for enhancements of this process?
- Can I do anything for you?


Kind regards and thanks a lot for your work
Andreas.


[1] https://people.debian.org/~tille/

--
https://fam-tille.de

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmZh2FsACgkQV4oElNHG RtF7IBAAlpKbZLkYbdYv/XJN/y1jxwwTYJwN9Eml2Ew+pqivD4OUJ+SI8vLcYMuB c24tgEymUXXSt3JW/OckOwDo+TGoGImyNMZUB35xIIOQZx5POg4zrfYldbE5V/ly PBYVdDOGkOhELsVaOQfokximRtMBamTi920usRU9wpjGHmz8ErENUuacBgkA7lHX +k5YQZScP/hG7QYAFywdsQ9aozgpL3ukqaEWaSW3cAPwkCrASvmVwAbfZuNmUnMf AbBID2b4XXxmnP9/PULUafoYGVPjQZyRlt8a73cGKtK4ywsIh5RbKLpwLAQNRtte MZEwLDYNuQ2uRO7LNzTGRoUtsq1AO1INbzigbC7LlUgJeA8J+TQAp7dNKUNFuWTH 1QjQHoZHZKiyVbXGoq213p4To1w9vrsqUG5sFavd6hw4xxQUOVfTMDIFt9U27ju7 lZgC2MDne15R0QI1HNGDYCRqjkiO61/E08OnQG/t/GrMYGK9bZwRO7Uzw631Wzx5 vp0k16cGUWJ87Hyba4CyeXXjZkKyt8FdcZFJvIfV/3/wHYft2WR3ZmftV+9eaMQ9 +k0+3b5rhnCOpFv0O0FQ7oWuKVzc+NuYpTqe9buJzEQZ6PyBz1MCU56OG6hMEZXo xMS0F6r1qJ4kU+psg+/ErtirGx86IFTLtVHI0D5ZNMjAO/AASU4=
=JQR9
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Jun 06, 2024 at 05:40:15PM +0200, Andreas Tille wrote:

I'd like to officially contact all our teams to learn about potential
issues that might affect your work. I would love to learn how you
organise / share your workload.

I don't think we do, I think it's all ad-hoc. There are some bug lists
in the IRC channel topic.

If you do some regular meetings - be it on IRC, video conference or
whatever

We do not.

I have some specific questions to the Debian Python team. I'm really interested into individual answers from single contributors either here
on this list or in private.

- Do you feel good when doing your work in Debian Python team?

Yes.

- Do you consider the workload of your team equally shared amongst its
members?

No idea if this question makes sense. I think most people just work on
their own packages.

- Do you have some strategy to gather new contributors for your team?

No.

- Can you give some individual estimation how many hours per week you
are working on your tasks in youre team? Does this fit the amount of
time you can really afford for this task?

<1

- In the beginning of this year there was a change in the policy of DPT.
I'd like to hear your opinion about:
* The process how it went (possibly with suggestions to do better)
* The final result after a couple of months
(I'm specifically interested also in the opinion of people who were
not happy about the change.)

It showed yet again that with any change, and equally lack of change, in
Debian there is a possibility that some people will resign.

- Since a long time we try to migrate from Python3.11 to Python3.12.
* What are your thoughts about the transition process?

It's not transparent.

* Can you identify some blockers?

I have no idea.
I know many RC bugs are open but I don't know if any of them are blockers
and not things to be removed from testing.

* Do you have some suggestions for enhancements of this process?

If DPT is expected to be involved besides looking at the RC bug list at
the IRC channel topic, I would like to know how.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmZh5uotFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh T9UQAJtKJHpL7FqCshJ8WXiBNfNz289BRR/S+GWadzDSDQRap3wquGrX5AvA3o+5 ng8/7yrh+PXrA6e1rgkObkWD/szIuX/U5KHnuJlHVfESNN2Zk80sj2pUgbVs/J7W JEpi19/6i1lrIz3PRYAm9wbAx7G9gHU82vSWlUPQ2MwsrHjt0q1mZ+po8FsVzIwh FIM97kLAYJpgMaF+oJUxobkwJBCy3zAc39Hrct9yEKtxPHhQKnBps79clF3DsBC0 r0DuYU8WuFdo9ZG843FgR/Sf3UjKjm0lo5AxcylCNQlGdhTKXqhwpnuQ2QRk18xK FzDUSrWr5ZMWEJ1xBVaviIin7fr6wLaG10USx4igMSoK6bo49lZK2wcAGCcVmFE6 hofFNdPw2/SM9Q3Mk8N2binS1xb/vkHp92Q/gGEPvhhin0JVab4sOQQdYEVA7Obh 6otqA4BOeEuCGoYi7kFPsdyaFh073GAUrC5MtXpW6DJ3gc1eIm/NLLGB7Smn5hG5 fKknEnnUlqHYiGcYhqoYG0rXUWZ+iNJpYs4vmaCCb45sD7cDVmGJXFh3XS6jjdEX cDq4nMKAi5lLUlGhdEMwm5docD4c27qfJzwWoj1NplnQwAPs9eI+Smz0ZzHs/YtZ PsOPoZgyalQtNvCmFxhpo8cxbFRqOS9j3zYz0hYHYNNEPbTR
=7nRT
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thursday, June 6, 2024 11:40:15 AM EDT Andreas Tille wrote:

- In the beginning of this year there was a change in the policy of DPT.
I'd like to hear your opinion about:
* The process how it went (possibly with suggestions to do better)
* The final result after a couple of months
(I'm specifically interested also in the opinion of people who were
not happy about the change.)

Personally, I found the entire exercise quite disappointing. I sensed little to no interest from members of the team in trying to understand other perspectives on the proposed policy change. It seemed to me to be an exercise in individuals trying to get what they thought best for themselves with little interest in the consequences of winning the argument.

Myself, I would have preferred not to change, but I don't find the change itself a major issue either way. I am mostly disheartened by the lack of interest in trying to find consensus in the team (note that this lack of interest was not exclusively from one side of the discussion or the other, I think it was both).

As far as I can tell, they most concrete result is some people left the team. Some packages got picked up by other people, some packages were removed from the team, some packages were orphaned, and some packages were removed from Debian as a result. Any benefit is theoretical as far as I can tell.

I have reduced my participation in the team. I have been working my way through packages to see if I was working on them because I want to or because
I thought I ought to as a part of being a good team member. I have removed myself from uploaders, transferred packages to other uploaders, and orphaned several packages in the latter case.

If someone thinks this change helped anything, I'd be curious to see the data on that supports it. Maybe I just missed it.

Scott K
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAmZih84ACgkQeNfe+5rV mvES5A//Zw83/avhdve7/SFHoehxmwGrS0+P+aQcv56/hW/Nk+M7GJDG1vaMp7Uz zXg4G1FT7znJymz0rtWu2k+r19IXLuKOTzSn5bRbfZv39SB8QbpM75rxFg62yX5r +3c9rsIbQC1VOjVNJzvDAkH38556eOlNTD4mEhbfvtH1xUngxEeylHky5HVqkP+X +yZI8fusIdGGFdxEq87k5oF6LCrIqGLFZsnZCk/RpabWp3ckQk8feSFTPP8GriwI DNuBdvr61sfFnN8/qm8U1gRVb8eXvj3A29izqEijN7JlrKmZiIwSVAgwuOneZPoV e0YsMa0YQJ7+wvwej0GiLNrQSiL6zKai3mAcyijDBN86VdrDr83bY09cABrptAs7 MS4fb/0FWWSyBnsAT9ckGdhOdeI/a/jju8oJN/C4fSdwAOyjcRFaKVNrUs7ZN8vf QYuww6d7IL/vqfAEIYcv4uqGU06efZyfBa4MDg56iW0tNbB5UYi+7Gtr+1y1B0VB 4WT3XAy0SXiVhlEctKtmkEPXFE3KxRhHF6SznhPCWAEDR8MBWt1kEHFsYjVtXqa9 RExYy69jlUW8uzjqcjGZvdN8vHlBX9t9mKe/G3jhyNbYMw1WIcJMbjobdAiwmrhl btHkTYg0Hq7HXNFt+Ic1vr/yyy7wZ9pBuOqcgUtzzugl16eL1LU=
=J3ma
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi all!

On Fri, Jun 07, 2024 at 12:08:46AM -0400, Scott Kitterman wrote:

On Thursday, June 6, 2024 11:40:15 AM EDT Andreas Tille wrote:

- In the beginning of this year there was a change in the policy of DPT.
I'd like to hear your opinion about:
* The process how it went (possibly with suggestions to do better)
* The final result after a couple of months
(I'm specifically interested also in the opinion of people who were
not happy about the change.)

Personally, I found the entire exercise quite disappointing. I sensed little
to no interest from members of the team in trying to understand other perspectives on the proposed policy change. It seemed to me to be an exercise
in individuals trying to get what they thought best for themselves with little
interest in the consequences of winning the argument.

Myself, I would have preferred not to change, but I don't find the change itself a major issue either way. I am mostly disheartened by the lack of interest in trying to find consensus in the team (note that this lack of interest was not exclusively from one side of the discussion or the other, I think it was both).

As far as I can tell, they most concrete result is some people left the team.
Some packages got picked up by other people, some packages were removed from the team, some packages were orphaned, and some packages were removed from Debian as a result. Any benefit is theoretical as far as I can tell.

I was one of the people that accept the policy changes. At the beginning
IMO there were some movements en the packages, there were volunteers
picking orphaned packages, people left the team as you mentioned, but
the team is working as was working before the policy change. I'm not
sure if the policy change had the effect that we expected.

I have reduced my participation in the team. I have been working my way through packages to see if I was working on them because I want to or because
I thought I ought to as a part of being a good team member. I have removed myself from uploaders, transferred packages to other uploaders, and orphaned several packages in the latter case.

If someone thinks this change helped anything, I'd be curious to see the data
on that supports it. Maybe I just missed it.

Scott K

--
cheers,
Emmanuel Arias

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ eamanu@debian.org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
⠈⠳⣄

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmZopMkACgkQ+p3sXeEc Y/FsxBAAi612ks9M1JhUBvYbJlHqLKyEr9XwVN2FjrYZ6OXwwmNT3ImS2lGpnbcK /qgwYN3xwaRfRdcHQtBNNfTh4ZbB3M93XVB2gO+Dp1eas3bf9sQw9DKP0fgIazqf sVtLQlmOyimsBRTaU3jtj8eVufbNgLV0u8dUAYDSIFdE7Vx3d4ActU3S++YYexUZ v5PK6JzpZPD915velxethCl9ui9KbV8MxLkI/RBTqlyZzrFsgzkVapjHAPiQrmLh Au0XHHD2Q8pV7XuxoF4l95rIn+EKSnnN6qnwO0xg23yALztCpCCDjtESFH+DtDV/ CeMXXnKYnSEFWJj8wC0t7+bwd6Cn0UoRDwYs3QAh/HTP7EdmBCTP4Jo5G8pV3oRr 84yMj0iqucLtG9fhLyY3QNsK1GTGRR2s2UhHjVPXf7qvfJugBO72+poHmDsto1HP xxBTYyrc8+z1tiK8glrEecs4KsKIOUna7xZgyP4Gu0OlndRWEpndYbYvxaXbN5XS B9tsxGy8h6Qn4VQg4DqhGve7gJhGlcEXtWpAgeQM5zf4rrinTDVAmRV3tuP/nbo1 bIMcIzEP9+mGF6jzzIBMp9s6qgqDt7Ryf0SXHOFk911R2EWASSf24mK3vk0w5Ynw p6KHSw8lz+Qv0BfMeKdr9rT4F8q+tujtaXo13DOnUzmPZL2

T24gMjAyNC0wNi0wNiAxMSBoIDQwIGEubS4sIEFuZHJlYXMgVGlsbGUgd3JvdGU6DQo+ICAg IC0gRG8geW91IGZlZWwgZ29vZCB3aGVuIGRvaW5nIHlvdXIgd29yayBpbiBEZWJpYW4gUHl0 aG9uIHRlYW0/DQoNClllcy4NCg0KPiAgICAtIERvIHlvdSBjb25zaWRlciB0aGUgd29ya2xv YWQgb2YgeW91ciB0ZWFtIGVxdWFsbHkgc2hhcmVkIGFtb25nc3QgaXRzDQo+ICAgICAgbWVt YmVycz8NCg0KTm8sIGFuZCB0aGF0J3MgcGVyZmVjdGx5IE9LPyBTb21lIHBlb3BsZSBoYXZl IG1vcmUgdGltZSB0byBnaXZlIHRoYW4gb3RoZXJzLg0KDQo+ICAgIC0gRG8geW91IGhhdmUg c29tZSBzdHJhdGVneSB0byBnYXRoZXIgbmV3IGNvbnRyaWJ1dG9ycyBmb3IgeW91ciB0ZWFt Pw0KDQpOb3QgcmVhbGx5LCBidXQgSSBmZWVsIHRoYXQncyBnZW5lcmFsbHkgdHJ1ZSBmb3Ig RGViaWFuIGF0IGxhcmdlIDopIEkgDQp0aGluayBqb2luaW5nIGFuIGFjdGl2ZSB0ZWFtIGlz IGFuIGVhc2llciB3YXkgdG8gc3RhcnQgcGFja2FnaW5nIHRob3VnaC4NCg0KPiAgICAtIEkg Z3Vlc3MgeW91IHdpbGwgaGF2ZSB5b3VyIHJlZ3VsYXIgRFBUIG1lZXRpbmcgYXQgRGViQ29u ZiAod2hpY2ggSQ0KPiAgICAgIGludGVuZCB0byBqb2luKS4gIFdoYXQgZG8geW91IHRoaW5r IGFib3V0IHRoZSBnZW5lcmFsIHRlYW0gbWVldGluZw0KPiAgICAgIEkgcmVnaXN0ZXJlZC4N Cg0KSSB0aGluayBpdCdzIGEgZ3JlYXQgaWRlYSBhbmQgSSdsbCBiZSBtb3JlIHRoYW4gaGFw cHkgdG8gam9pbi4gSSd2ZSANCmhlYXJkIGdyZWF0IHRoaW5ncyBhYm91dCB3aGF0IG90aGVy IHRlYW1zIGhhdmUgYmVlbiBkb2luZyBpbiB0ZXJtcyBvZiANCndvcmtmbG93IGFuZCBwcmFj dGljZXMgYW5kIEknZCBsaWtlIHRvIGxlYXJuIG1vcmUuDQoNCkkgZmVlbCBpdCB3b3VsZCBi ZSByZWFsbHkgcG9zaXRpdmUgaWYgd2UgY291bGQgdHJ5IHRvIHdvcmsgdG93YXJkcyBhIA0K bW9yZSBzdGFuZGFyZGlzZWQgc2V0IG9mICJ0ZWFtIHByYWN0aWNlcyIgaW4gRGViaWFuLCB0 byBtYWtlIHRoZSBnZW5lcmFsIA0KcGFja2FnaW5nIGV4cGVyaWVuY2UgbGVzcyBjaGFvdGlj Lg0KDQo+ICAgIC0gSW4gdGhlIGJlZ2lubmluZyBvZiB0aGlzIHllYXIgdGhlcmUgd2FzIGEg Y2hhbmdlIGluIHRoZSBwb2xpY3kgb2YgRFBULg0KPiAgICAgIEknZCBsaWtlIHRvIGhlYXIg eW91ciBvcGluaW9uIGFib3V0Og0KPiAgICAgICAqIFRoZSBwcm9jZXNzIGhvdyBpdCB3ZW50 IChwb3NzaWJseSB3aXRoIHN1Z2dlc3Rpb25zIHRvIGRvIGJldHRlcikNCj4gICAgICAgKiBU aGUgZmluYWwgcmVzdWx0IGFmdGVyIGEgY291cGxlIG9mIG1vbnRocw0KDQpJJ20gc2FkIHRo YXQgc29tZSBwZW9wbGUgbGVmdCwgYnV0IHRoZW4gYWdhaW4sIEkgZG9uJ3QgdGhpbmsgYSBz b2x1dGlvbiANCnRoYXQgc3VpdGVkIGV2ZXJ5b25lIHdhcyBwb3NzaWJsZS4NCg0KSSBmZWVs IHRoZSBzdGF0dXMgcXVvIGNyZWF0ZWQgYSBsb3Qgb2YgdGVuc2lvbnMgKGVzcGVjaWFsbHkg Zm9yIHNvbWUgDQpuZXdjb21lcnMgd2hvIG1hZGUgaG9uZXN0IG1pc3Rha2VzKSBhbmQgYXMg c3VjaCwgSSBkb24ndCB0aGluayB3ZSANCmNvdWxkJ3ZlIHJlYWNoZWQgYSBjb25zZW5zdXMg YW5kIGJlbGlldmUgYSB2b3RlIHdhcyBuZWNlc3NhcnkuDQoNCj4gICAgLSBTaW5jZSBhIGxv bmcgdGltZSB3ZSB0cnkgdG8gbWlncmF0ZSBmcm9tIFB5dGhvbjMuMTEgdG8gUHl0aG9uMy4x Mi4NCj4gICAgICAgKiBXaGF0IGFyZSB5b3VyIHRob3VnaHRzIGFib3V0IHRoZSB0cmFuc2l0 aW9uIHByb2Nlc3M/DQo+ICAgICAgICogQ2FuIHlvdSBpZGVudGlmeSBzb21lIGJsb2NrZXJz Pw0KPiAgICAgICAqIERvIHlvdSBoYXZlIHNvbWUgc3VnZ2VzdGlvbnMgZm9yIGVuaGFuY2Vt ZW50cyBvZiB0aGlzIHByb2Nlc3M/DQoNCkkndmUgc2FpZCBpdCBtYW55IHRpbWVzIGJ1dCBJ IHJlYWxseSBkaXNsaWtlIHRyYW5zaXRpb25zIHRoYXQgYXJlIG5lYXIgDQp0aGUgcmVsZWFz ZSBmcmVlemUuIEl0IGZvcmNlcyB1cyBpbnRvIGEgY3J1bmNoIGFuZCBJIGRvbid0IHRoaW5r IHRoYXQncyANCmhlYWx0aHkuDQoNCi0tIA0KICAg4qKA4qO04qC+4qC74qK24qOm4qCADQog ICDio77ioIHioqDioJLioIDio7/ioYEgIExvdWlzLVBoaWxpcHBlIFbDqXJvbm5lYXUNCiAg IOKiv+KhhOKgmOKgt+KgmuKgiyAgIHBvbGxvQGRlYmlhbi5vcmcgLyB2ZXJvbm5lYXUub3Jn DQogICDioIjioLPio4QNCg0K

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Jun 14, 2024 at 06:41:58PM +0200, Alexandre Detiste wrote:

Hi,

Le mer. 12 juin 2024 � 16:22, Thomas Goirand <thomas@goirand.fr> a �crit :

On 6/6/24 17:40, Andreas Tille wrote:

- Do you consider the workload of your team equally shared amongst its
members?

The team probably lacks organization, and there's no clear enough
strategy for end goals.

I know we're moving toward getting rid of:
- six
- mock
- nose

and unittest2,
and zombie-imp,
and 2to3,
and cython3-legacy
and m2r
and mistune0
and ...

Even only listing all of these on wiki with
what they could be replaced with would be good starter.

Hi, could you please share the list of those? I have in mind six, mock,
nose unittest2, 2to3 and cython3-legacy. If the team are OK I can update
the wiki with this information.

Cheers,

We could rely on the standard transition tracker to see what remains:
https://release.debian.org/transitions/
or having those get from FTP-Masters an "oldlibs" overide.

I've my own tracker but it's mostly a toy I build to see what could be
done with UDD
and playing around with matplotlib.

An optimal moment to check whether these old dependencies
can be removed seems to be when a new upstream is available.

(m = mock, n=nose, s=six)
$ cat snap
androguard m (depends on Java stuff..) backblaze-b2 m n s (huge)
elasticsearch-curator m n (depends on new spun out library too ITP)
fabric n (I tried)
heudiconv m (attempted uploaded to experimental)
mu-editor m (discussion on mailing
list about packaging style went nowhere)
pagure m s

Now I think I could sort this by upstream release date & make an RSS
out of it ;-)

but is anyone doing any type of coordination for the work to be done ?

I guess people being members of several Teams could give precious help.
I don't see myself pledging to join Teams just to remove
a handful lines from d/control files, and then be gone forever.

It's been a waaaaay too long.

Agree

Greetings

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmZztQcACgkQ+p3sXeEc Y/GpPA/+LmJ+N1oKCB/ekguKi89CtvlX4sWTPAj+EWmVYZZQOUOJhGcTd1gaKTBP GZizWe1EHPGJXrLby/y4bMcQzIik1zzyk7YKPOKeqJLhMmcFoE0wMhXjRmV+c0Xy rGJ/9ssDRFZJ7yFQP9a68hnaSmnqP9NHuyW95WWljvaPog+3//PXiJJIDbaFGMpd Pt7WZ0FP7m4+LZ7S8zGztxX8+KVuGJlE4v0VAG9mFSAJKepO8ShuCLYfeqMWgPRY 5IswvVkTC2leNCSN15mEDewwiaxaXWDg+gplq3acOdzUzuyoK4RGXH3ZEWAw5J3Q /n31uJHJvfKas7UVWN7GwUlosJM5GW8AhGtkNEkshMhSmxuCAGwwghFE7VGQWwe/ 7dKNmHJaVmEwvlnigldQ1v+vorF3bEeawcFYc3Z1NcBVahljgtAvIcleCN3NwCuK iH9eIfN0nx/PlkkZXBkKvddyltMQEDvzwAybrckPP+vuZqSap4LqG4hT6e6FLEw6 bE01I/PLDUTwje+CgGG5qsM/wNy+e/uXToL03nLWBG60jVuv8n38c0QDD3lCfaXQ 0JA9SyzNprAaQk92RznOLgnppS3QrIzcrrcvwHclQDqEN8iE+Rqpl2SSrAGfISq1 47VMhcoyk7OT/PDrYBDyFrwf+sh90y4OeVxNm4vOUyiYyce3M7k=
=5BAk
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)