Re: [Printing-architecture] War / Notes from last meeting...

[Till Kamppeter <till.kamppeter@gmx.net>]

Here is the TMDA tool against spam about which I talked last week:

http://tmda.net/index.html

For me it makes the impression that with this there is no problem when 
the e-mail address gets public.

Every mail from an unknown person gets into a queue and the sender gets 
an automatic answer asking him to confirm his e-mail. If he confirms, 
his original mail gets into your mailbox and the sender gets onto the 
list of known users, so that his next mails get through directly. If the 
sender does not confirm, you never get his e-mail. Spam is sent by 
robots, so noone sees when to one of the spams an answer comes back, so 
even if the sender´s address of the spam is valid, it will not be 
confirmed and you are protected. You can also edit the list of known 
users manually, for example adding persons you know.

You can once protect your account with TMDA, but perhaps it would even 
be a good thing to somehow apply it to the FSG lists. Then everyone has 
to confirm once and never again, but spam does not get in.

Another way to protect lists is to make them subscriber-only (this is do 
on linuxprinting.org.

    Till


HEMSTREET,CHARLES (HP-Vancouver,ex1) wrote:
> Folks:
> 
> Is anyone out there changing their PWG/FSG travel plans due to the onset of
> war with Iraq?
> 
> I am reluctant to post to this forum now that I have found that it is
> publishing my email address.  I suspect that my sharp increase in spam over
> the last few months is due to my posting on this forum.  Shawn and I are
> working with the administrators to stop this.  
> 
> Agenda for next meeting:
> 
> 1) Travel plans FSP/PWG
> 2) alternative posting mechanism
> 3) finish last weeks discussions
> 
> 
> Thanks,
> Charles
>  
> 
> 
> Linux Open Printing Meeting
> 03/13/03, 8-9am PST (actual 8:00 - 9:00am PST)
> 
> Attendees:
> Charles Hemstreet
> Glen Petrie
> Ira McDonald
> Claudia
> Mark Hamzy
> Till Kamppeter
> Norm Jacobs
> Bob Taylor
> 
> 
> Agenda for meeting (03/13/03):
> 
> * Spam and email distribution lists - the lists should be subscriber only
> * Mark Hamzy - driver subgroup - we need to start working on the subgroup.
> What is the goal of the driver subgroup?  PAPI and JobTicket define a set of
> properties to support a job.  None of the current printer drivers use this
> information.
> 
> Proposal - the pwg standard media names.  It is already in the document.
> Use standard job properties for the driver.  Use all the job properties at
> once, rather than calling each property individually.  Omni has a special
> problem that it has XML device support for the driver.  We need to decide to
> do or not do job properties.  Need common job properties at the driver.
> Objective - use appropriate standard for relevant attribute rather than
> rewriting a new standard.
> 
> One set of forenames - don't support three different names.  Choose one of
> the native name forms of IPP or JDF.  
> 
> Mark will get some phone numbers to get us all together to talk about this
> subgroup.  The meeting will be happening on next Wednesday, March 19th, 11am
> PST - 1pm PST.  Charles get David Suffield to join us.
> 
> The objective of the driver subgroup is to have agreement on the common
> technological goals and put them together for the PWG meeting.  We will
> decide the foundations of where we want to go.  Mark will create slides and
> publish.  The directory is published in Claudia's JobTicket notes.  Post as
> PDF and whatever other source you might need.  An additional goal is a
> tentative time schedule (common keys, etc.)
> 
> * Agenda input for upcoming Washington DC meeting - we need to post the
> agenda to Amy Patel (ask that she distribute it right away)
> * Till suggesting to give a short presentation for foomatic
> * Dave Hall/Alan B. would like to present PSI at our meeting.
> * Claudia talked to Harry Lewis about aligning PWG and FSG.  There is an
> evening plenary on Wednesday PWG/FSG.  This is on the schedule.
> * other?
> 
> 
> 
> Proposed FSG Meeting agenda (Tuesday, April 1, 2003)
> Following is a proposed agenda for the FSG meeting:
> ---------------------------------------------------------
> 8:00-9:00 AM - Plenary
>       (60 minutes = 15 minutes for coffee + 45 minutes for meeting)
>    Presenters: Shawn Pratt/Charles Hemstreet
>    Agenda
>       a. Coffee
>       b. Business meeting
> 
> 9:00-9:30 AM - Architecture Overview
>       (30 minutes = 20 minutes for presentation + 10 minutes for questions)
>    Presenters: Charles Hemstreet/Mark Hamzy
>       a. High level architecture diagram
>       b. Identify major pieces of the architecture and which are:
>          1. Work in progress (percentage complete)
>          2. Not much activity, need more work
>       c. Questions
> 
> 9:30-9:45 AM - Break (15 minutes)
> 
> 9:45-10:45 AM - JTAPI
>       (60 minutes = 40 minutes for presentation + 20 minutes for questions)
>    Presenter: Claudia Alimpich
>    For the agenda guidelines, see the *note below
> 
> 10:45-11:45 AM - PAPI
>       (60 minutes = 40 minutes for presentation + 20 minutes for questions)
>    Presenter: Michael Sweet?
>    For the agenda guidelines, see the *note below
> 
> 11:45 AM -1:00 PM - Lunch (75 minutes)
> 
> 1:00-1:30 PM - Capabilities (30 minutes)
>    Presenter: ???
>    For the agenda guidelines, see the *note below
> 
> 1:30-2:00 PM - Notification (30 minutes)
>    Presenter: Tom Hastings
>    For the agenda guidelines, see the *note below
> 
> 2:00-3:00 PM - Printer Driver Renderer (60 minutes)
>    Presenter: Glen Petrie/Mark Hamzy
>    For the agenda guidelines, see the *note below
> 
> 3:00-3:15 PM - Break (15 minutes)
> 
> 3:15-5:15 PM - Architecture details (120 minutes)
>    Presenter: Charles Hemstreet/Mark Hamzy
>    a. Low level architecture diagram
>    b. Resolve problems/issues identified during earlier sessions
>    c. Resolve open problems/issues
> 
> 5:15-7:00 PM - Dinner (105 minutes)
> 
> 7:00-9:00 PM - Overflow (120 minutes)
>    Any items that were identified during the previous sessions need to be
> covered. The agenda will be determined as the day progresses.
> 
> 
> *note - The following format should be followed for the slide presentation:
>    a. Introduction/Purpose
>    b. Status
>       - Milestones (previous and future)
>    c. Details
>       - Whatever slides are needed to describe the details
>    d. Issues
>    e. Information about this working group
>       1. Active participants
>       2. Meeting day, time, call in information
>       3. Websites
>          - Mailing list and archives
>          - Other documents pertaining to this working group
>    f. Q&A and discussion
> 
> 
> 
> 
> 
> Action items
> #	What	Owner	Status
> Action items from 03/06/03
> 1 	Check to see if there is a good polycon conference phone to FSG
> meeting	Shawn	
> 2 	Check to see if there is a good polycon conference phone to FSG
> meeting	Ira	
> Action items from 02/27/03
> 1 	It would be nice if we could get a translation or running summary
> (one sentence) of the discussions that happen on the printing-japan
> discussion list	Charles	
> Action items from 01/30/03
> 1 	Charles to talk Shawn about getting us a date for face to face
> meeting at PWG	Charles/Shawn	Done
> 2	Ira to check dates at PWG and report back	Ira	
> Action items from 01/16/03
> 1 	None		
> Action items from 01/09/03
> 1 	Work with Shawn to report back to pwg	Charles	Complete
> 2	Can the executive board provide grants for travel to summits
> Shawn	
> 3	Email people to notify that we will not have a face-to-face meeting
> at LinuxWorld	Shawn	
> 4	Release to printing announce, prerelease message for LinuxWorld
> regarding to PAPI	Shawn	
> Action items from 11/21/02
> 1 	Send out an announcement that the meeting will not be held next
> week.	Charles	Done
> 2	Claudia will write down the sequences that she described on the
> teleconference - narrative in plain text (terse)	Claudia	
> Action items from 11/14/02
> 1 	Work with Mark Hamzy to find HP people to work on PDC	Charles	
> 2	Post agenda items query on architecture list	Charles	Done
> Action items from 11/07/02
> 	none		
> Action items from 10/31/02
> 1 	Contact Robert Kravitz to find out if he can make it an hour later
> Till	Done
> 2	Talk to Shawn about moving his meeting to another day	Charles	Done
> 3	Mailing lists are not behaving probably, contact Shawn	Till	Done
> 4	Need bidirectional arrows for bubbles A, B, C, and D		
> Action items from 10/24/02
> 1 	Change the list so that subscribers can post, moderate the
> unsubscribed	Charles	Done
> 2	Move Charles to be the moderator of the discussion list, and
> printing meetingnotes	Charles	In Progress
> 3	Change archival from 90 days to 1 year of printing-meetingnotes list
> Charles	In Progress
> 4	Follow up with Michael Sweet to see if new time is doable.	Ira
> Done
> 5	Follow up with Michael Sweet to find out what morning time would
> work for him	Ira	Done
> 6	Send out demo information for Webex so users can be comfortable with
> it before the next meeting	Charles	
> 7	Find out if there is a netmeeting client for Linux	Charles	In
> Progress
> Action items from 10/17/02
> 1 	Take discussion list forum and move to meeting minutes forum
> 	Shawn	Done
> 2	Move architecture discussions to new time slot, moving from the
> Thursday morning time slot.	Charles	In progress.
> (Related to AI#3)
> 3	Michael, Tom and Robert Krawitz to suggest a time for the
> architecture teleconference. 	Michael, Tom, Robert - (Ira and Till will
> follow up)	In Progress
> 4	Put the overview template out in the architecture directory
> (fsg/pwg)	Claudia	
> 5	Update the web site with Claudia's template	Shawn	In Progress
> Action items from 10/10/02
> 1	Find out if we can use WebEx	Shawn Pratt/Charles Hemstreet
> started
> 2	example documentation for Job Ticket API (from overview diagram)
> Claudia	Claudia will provide by 10/14
> 3	Post to web and to discussion group for review. (Discussion groups -
> done, web - not yet, ran into some server issues)	Shawn / Alan	
> 4	Make note to other distribution lists to review this spec with
> objective to get agreement. (Done - am planning to do a reminder).
> Shawn	
> 5	Broadcast message to application developers to review spec.  Work to
> get applications to adopt the capabilities methodology.  	Shawn to
> general app groups, participants to their own company app groups (ongoing)
> Ongoing
> 6	Provide a starting point with the Device object definition	Ira
> 
> 7	Start reviewing and comment on areas of discrepancies and areas for
> mapping.	All	In progress
> 8	Completion of the architecture diagram and wording.  	All	In
> progress
> 9	Requirements document (Shawn to establish an outline, need input to
> fill in the info	All	
> 10	Get feedback to Mark Hamzy on how to get Japan more involved in
> OpenPrinting before 10/16/02	All	In progress
> 11	Issue next version of PAPI spec, version 0.6, candidate for
> functionally frozen 1.0.  Add summary info from above as well as a
> print-by-reference function.  Targeted for 9/20/02.  	Alan	Done
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@freestandards.org
> http://freestandards.org/mailman/listinfo/printing-architecture
> 
>