CC does not offer such an option as the GPL does.

It may be preferable to get that under 4.0 or later, so you don't need to contact every contributor again if in some years there is intention to switch to a newer version released by Creative Commons.

For the pogo-pin test clip to flash, it is available in China.

1. I'd like to suggest to include a mail alias "paypal@gnupg.org".

Metazoa (Ingo Bläser) quote busy. Promised to send an offer with a brief concept "in March". I will ping him.

I use BBG-SWD (my own tool to flash MCU) for transparency of the process. It's up to you to choice a tool for initial flashing.
Just in case, here are resources to be reproducible.

Some of my terminology: I call "case", "shell", and "board".

The metal case, I bought from here (it's expensive CNY3.00, for individuals): https://item.taobao.com/item.htm?id=550180089286

For prototype, I used:

• ZL-272 (without slits): https://detail.1688.com/offer/566273410945.html
• ZL-271, the metal shell: https://detail.1688.com/offer/566197153418.html

• Repository for PCB design: https://git.gniibe.org/cgit/gnuk/fst-01.git/
  • tag: release/3.01 is the latest for the design itself, but last commit 8ee4e0d53a73993e42d1c2ccc12b08757338f4b1 added data sheet for connector.
    • • The particular data sheet is for a variant of connector with slits.
    • in the output directory, I put additional information as well as the gerber output: https://git.gniibe.org/cgit/gnuk/fst-01.git/tree/output?id=8ee4e0d53a73993e42d1c2ccc12b08757338f4b1
    • In output/README.txt, there are information for procurement for the GD32F103 chip and ZL-272 connector.
    • But those are the ones I specified, and the actual vendors/distributors are different
    • For ZL-272 with slits, it seems that it's DongGuan Yuliang Electronics Co., Limited (http://www.dgyuliang.net) which provides the connector
• The test plan I specified is: https://www.gniibe.org/memo/development/fst-01/fst-01sz-testplan.html

I don't see it as a priority right now. We should keep it in mind for T3811 .

I do not think that we should prioritize this right now. I had a talk with Michael and he said that we basically have the trademark because we are currently using it. To really register it and enforce it we would have to hire patent lawyers and that will easily go into 6 figure sums. Which I don't think we need right now. Let's keep it as "GnuPG is in use as a Product of g10cde".

Ping.

During a meeting with Werner today agreed:

• All content under gnupg.org should be handled by Verein
• Metazoa should write an offer regarding gnupg.org

(- Markus Meier is working for gnupg._com_!)
Contact to Metazoa already running. Will update Ingo Bläser.

In another project in the early 2000ies we had a lawyer from one of those Königsallee lawfirsm as partner. IIRC the estimated cost for a word trademark in the EU, US, and JP was in the range of 10k for just a couple of years.

Just trying to find out who spoke about _which_ website _exactly_. Obviously, it wasn't just about GnuPG e.V.

Just talked to Michael Stehmann again. He added some useful thoughts. Unfortunately, he didn't agree to summarise them in 2-3 paragraphs. So I'll try...

Please provide a summary of the talk.

My opinion:

Talked to Michael Stehmann. First questions to be decided before estimating the efforts:

At end of 2018 we had a talk with designer Markus Maier in the Düsseldorf Office.
The issue was handled as well.

The pages of the Verein shall use a different layout than the general gnupg.org pages.

We didn't found the time to organize it. There will be a OpenPGP summit this fall organized by Patrick, though

I wonder if there's potential for engaging users remotely? Also, in addition to a workshop, maybe a user interface study of how users learn and interact with the tool? I feel like doing that with people who are relatively light/new users of gpg (like me, currently struggling as I wade thru a mix of docs, some of it outdated) could be beneficial. See also: https://arxiv.org/abs/1510.08555

Hello Andre.

We should publish a status report about the campaign. I'd suggest to do this a few days before the 2.2 release.

E194 started a bit too late but here we go: