FSG Open Printing Steering Committee

Action Items

(an evergreen document)

Last Updated : 2004.04.28

By: Glen Petrie

Num	Team	Action Item	How to Do	Who will Do	By When	Comment/Result
1000	UJ	All of the subgroups need 3 different linking methods (static, dynamic, and client/server over named pipes) for access to the library. Perhaps the SANE project can provide some help. 1. Goal is to create common methodology for all three linking methods.	- Research SANE concepts - Write proposed mythology for linking methods - Review by all subgroups. - Final written guideline.	Form a high priority short term work-group. Olaf (Lead)? Glen ? Mark ? Others? Norm (By email)	Complete by June 18 date has been postponed until next steering committee meeting. Release guideline often to get feedback for subgroups while developing guideline.	See AI 1003
1001	UJ	Need a finalized reference model for both team to work from i.e. 1. separate Renderer & Transform 2. What is definition of spooler 3. Should spooler be separated from Print Manager?	- Review the proposed reference model by the Arch team - Create a short description of each modules and general interface	Architecture Team	Completed by May 28th Work on reference model on architecture meetings until this item is satisfied.	
1002	UJ	All of the subgroups need to study all of the proposals by other subgroups and read the monthly status reports from the subgroups.	All subgroup will submit proposed specifications to a “review mail list” for comments for a period of 4 weeks.	All contributors		
1003	UJ	Every group needs to use a common coding convention that addresses - name spaces for - function names - environment variable names - key=value strings - installation path - registry information - versioning information - stand alone executable (parameters) - test suites	- Collect existing subgroup coding conventions. - Consolidate and resolve ambiguities. - Review by all subgroups. - Create a final written guideline.	Create subgroup or Architecture Team Same subgroup as for Action Item 1000	Complete by August 30 up to registry information. Date in jeopardy. Some of the items are longer duration than others. Release guideline often to get feedback for subgroups while developing guidelines.	Look at the following: Olaf's Vector code JTAPI Headers Omni code PAPI Status Monitoring
1004	UJ	We need to identify and sign up a graphics art expert that can help us in writing a use case for magazine/offset printing or printing press.	Write email to all mailing lists to request expertise.			Architecture group has drafted a use model.
1005	UJ	We need to identify and sign up a pay for print expert that can help us in writing a use case for pay for print scenarios (college or library).	Write email to all mailing lists to request expertise.			Architecture group has drafted a use model.
1006	UJ	The spooler subgroup (aka PAPI) asked what functionality was needed for a 1.0 release. All of the subgroups need to provide input.	All subgroups must review the current PAPI specification. All subgroups must provide written feedback on agreement for changes to PAPI specification. PAPI group will evaluate, resolve, and update the specification.	All subgroups for step 1 & 2. Architecture team and PAPI team for step 3.	07/30/04	
1007	UJ	Licensing issues were discussed with the result of preferring an MIT license for code and a FDL (Free Documentation License) for documents. There is an incompatibility with the job ticket's use of the CPL (Common Public License) and the FSF (Free Software Foundation). IBM released the code as CPL. The CPL is incompatible with the GPL.	Contact the FSF on what the real problem is and obtain a resolution.	Mark Hamzy	06/04/04	Done. CPL is an allowable license. However, the preference is MIT.
1008	UJ	We need to engage more companies. Ex: HP, Lexmark, Novell, Xerox, Canon, KDE, CUPS, Ghostscript	Identify companies. Identify primary contact. Draft a note. Follow the note up with email/phone conversations.	Mark Hamzy Scott McNeal Till Kamppeter?	ongoing	
1009	UJ	We need a list of places/forums to publicize the specification so that the user community will be aware of our work. Other Linux groups CE Linux (Consumer Electronics) Montavista, Sony, Panasonic, IBM, HP, Phillips Emblix (Embedded Linux) Embedded Linux Consortium IEC/ISO JT C1/SC22	Identify companies. Identify primary contact. Draft a note. Follow the note up with email/phone conversations.	Mark Hamzy Scott McNeal Till Kamppeter?	ongoing	
1010	UJ	The Open Printing group needs a formalized process for releasing documents and reference implementations. For documents the process will be: - The subgroup will submit the spec to the steering committee. - The steering committee will submit the spec to the architecture subgroup. - The architecture subgroup will review it for up to a month. - The spec is released to the general public which has one month to submit feedback. - The feedback is collected by the subgroup and addressed. - The process is repeated with the architecture subgroup looking at the revised spec. - When everyone agrees, the steering committee will present the spec to the Free Standards Group's board of directors who will have the final approval. - The final spec will be housed on the FSG's web site. There needs to be a coding standards guideline for official reference implementation code. Once that exists, then the release process will be the same as the specifications.	- Collect existing software release processes. - Consolidate and resolve ambiguities. - Review by all subgroups. - Create a final written process.		Before Status Monitoring, PAPI, and Job Ticket releases and no later than September 30.	This is a release standard. It should be linked with AI 1000 & AI 1003
1011	UJ	We need a process for promoting the solutions of Open Printing. Which vendors and user groups need to be contacted? We need a coherent story for our solutions.	Identify companies. Identify primary contact. Draft a note. Follow the note up with email/phone conversations.	Mark Hamzy Shida-san	ongoing	
1012	UJ	The steering committee decided on a priority order for new work with the current subgroups. 1) architecture 2) PSM (Print Stream Manager) -- new subgroup 3) PDAPI (vector/raster) 4) SM (Status Monitor -- aka Bi-Di) 5) PAPI (Print manager, application interface) 6) Capabilities -- new subgroup ) JTAPI ) Spooler ) Renderer This ordering will allow printing from the print manager all the way down to the printer. Subgroups 1-5 will submit schedules (planning and headcount) for specifications and code.		US Steering Com Japan Steering Com		
1013	UJ	The vector driver subgroup will merge with the printer driver subgroup and create one common API.	Review existing driver API. Integrate our proposed raster APIs into the vector APIs. Vector group reviews.	US Driver Group Japan Vector Group	October	Should conform to 1003
1014	UJ	The bidi subgroup was told that the work that they did should be called status monitoring (SM).	Revive existing bidi specification to status monitoring. Remove any existing Print Stream Manager functions.	SM subgroup	07/30/04	Steering committee review name of “print stream manager”
1015	UJ	The SM subgroup will also add call-back routines for the notification of printer events like toner low to its API.	Investigate and produce a notification model.	Architecture team SM subgroup	10/01/04	Notification is a system API not an artifact of a subgroup. Japanese group made proposal to government but it was denied. Japanese group will resubmit after additional study. Next proposal is in September.
1016	UJ	A new bidi subgroup called print stream manager (PSM) will be formed by Epson to account for the lack of a common bidirectional communications API.	Create a subgroup.	Steering Committee	06/01/04	Ira: Print Stream is ambiguous. Change to Print Channel Manager. It is working now. In the July steering committee meeting, it will be
1017	UJ	The PSM group will create a model/architecture.	Investigate and produce a Print Stream Model model.	Architecture team PSM subgroup	08/27/04	
1018	UJ	The PSM group will create a 1.0 specification.		PSM subgroup	01/31/05	
1019	UJ	The vector subgroup released some code that was paid for by the Japanese government. This code needs to wait until the standard is merged with the printer driver subgroup and both groups agree on the merged API.	Government should not release the code until 1013 is done.	Japanese members of steering committee.	07/01/04	AI 1013. Hold meeting with Japanese community (40-60) to know what we are doing and ask them to join us.

Num	Team	Action Item	How to Do	Who will Do	By When	Comment/Result
2000	U	The American/European subgroups will give use cases that provide local requirements and ensure that all of the dependencies are documented.	Architecture subgroup meeting	Architecture Team	TBD	
2001	U	The job ticket group will submit a white paper to the Japanese team. This white paper will ask the Japanese government for funding to create a reference implementation of the job ticket specification. The Japanese team will translate this white paper for presentation.	Write a white paper	Job-Ticket Group	Translate 07/01/04 Discuss how to present 08/01/04	The US team submitted a white paper on the pwg ftp site. Japanese team will discuss on how to present it to the government.
2002	U	The JTAPI group will complete the specification for version 1.0.	Write specification	Job-Ticket Group	January 2005	
2003	U	We need a documentation template created to give all of Open Printing's specifications a common look.		Glen Petrie	April 2004 06/25/04 07/25/04	
2004	U	We need a road map for the Open Printing group that has release schedules and goals. Each subgroup will submit their schedules and goals to Mark	Mark will make a schedule template (details, # milestones, draft, alpha, beta). Each subgroup leader will submit a schedule.	Mark Hamzy	May 2004 07/01/04	

Num	Team	Action Item	How to Do	Who will Do	By When	Comment/Result
3000	J	We need more use cases from the Japanese side. Some examples would be mobile, PDA, transactional (forms), Kiosk, PODi/PPML (Print on Demand Initiative/Personalized Print Markup Language), and desktop print segment.			Desired by June 30th.	AI 3000-3005 will be discussed in the meeting with the Japanese community.
3001	J	The Japanese group needs to identify architectural issues with their subgroups and communicate them via email to the architecture subgroup (which, currently, only has participation from Americas/European members).			Desired by June 30th.	
3002	J	The Japanese group will then translate JTAPI white paper for presentation to the agency in charge of government funding.			June 2004	
3003	J	The Japanese group will translate the JTAPI specification and reformat into the appropriate format for submission to the Japanese government.			February 2005	
3004	J	HP has a patent on 1284.4 US05,453,982 Patent to be reviewed for conflict		Toratani-san		
3005	J	The Japanese government has/will purchase a set of fonts to use with Linux. They need to decide which licensing to use before releasing them.				AI 1007

Num

Glen W. Petrie

2004-04-29T14:30:00