Marked the task Ack or nak ASN.1 comm. as completed

Marked the task Ack or nak ASN.1 comm. as incomplete

News vs. article publication protocol

Here's a proposal to handle ARTICLES and NEWSLETTERS.

• Definition: ARTICLE

  A thematic communication that has no time constraint. It is written in a way that it can receive updates later on, even weeks or months later, as the theme evolves. E.g., white papers, the ASN.1 vulnerability, Snowden and bunnie's Introspection Engine.

• Definition: NEWSLETTER

  A compilation of pointers to timely information: published articles, noteworthy project developments, Press article or industry news...

• ARTICLES are published on the website at random intervals (according to their availability), and announced on Twitter

• NEWSLETTERS are published on the website at regular intervals (between 3 and 6 weeks according to the volume of news items), relayed to readership by email, and announced on Twitter.

• ARTICLES generate a news item in the next NEWSLETTER

• NEWSLETTER production:

  • have a "news $DATE" issue, like for meetings, but 3 weeks ahead, that we add contents to. When "enough contents" are reached, before the 3 weeks, publish, and restart a new issue for T + 3 weeks. If the time limit is reached without enough news, ponder whether to add some content and publish right away, or postpone to T + 3 weeks, with the pending news items. A NEWSLETTER SHOULD NOT be postponed twice in a row, so as to keep the interval between emails < 2 months at all times.

Marked the task News vs. article publication protocol as completed

Snowden narrative update

There's a pre-draft at http://sprunge.us/QPKR (don't waste your time there)

Review updated draft on Monday

Marked the task Snowden narrative update as completed

Ack or nak ASN.1 comm

@joerg_rw ACKed, pending integration of www#9 (comment 7574)

Publication tomorrow morning.

Marked the task Ack or nak ASN.1 comm. as completed

Marked the task hellekin advanced travel: tomorrow afternoon! as completed

Marked the task joerg on travel from tomorrow Friday til Sunday evening as completed

Status changed to closed

hellekin advanced travel: tomorrow afternoon!

Instead of tomorrow night

joerg on travel from tomorrow Friday til Sunday evening

so next meeting postponed to Monday

mentioned in issue #10

#9 (comment 7578) looks good

ACK

given you actually adhere to those rules :-)

the post itself might even make a nice uBlog or "article"

wondering how we break out such issues as a separate issue, instead of keeping it in a "meeting xxxx-yy-zz" melange of unasorted stuff. Maybe as a general rule: always create a new topic as soon as some comment to a meeting topic point gets added? What I said: gitlab maybe provides means to manage stuff, but it doesn't enforce it. Plus we ( I at least) need education on how to correctly use this tool

mentioned in issue www#11