Open	Team	Action Item	How to Do	Who will Do	By When	Comment/Result
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	Ongoing	2004.11.16 groups have stopped submission. 2005-04-05 Groups need to reengage members of other subgroups. All final document review requests should be sent to all active workgroups.
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	On Hold	Look at the following: Olaf's Vector code JTAPI Headers Omni code PAPI Status Monitoring glen is attempt This is not expected to be completed prior to several groups having v1.0 specifications ready (or close to ready) for publication. We need to focus our efforts on getting several of the currently active specifications completed. As a result, it is being closed for now. It may be reopened in the future when resources permit. 2005-04-05 on hold for the time being. This will not be used for current specifications that are virtually complete, but expected for later specifications.
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	On Hold	Should conform to 1003. Glen and Mark will update specificaiton with by the end-of October. Discuss at face-to-face in Texas. 2005-04-05 on hold until Driver subgroup restarts.
1014	UJ	The bidi subgroup was told that the work that they did should be called status monitoring (SM).	Revise existing bidi specification to status monitoring. Remove any existing Print Channel Manager functions.	SM subgroup	2004-08-30	The renaming is done. The revising is still work in progress. 2004.0823 Shida believe it done. BiDi functionality could not be removed for japanese govennment development. Waiting for PCM to finish, then will remove functionality 2004.11.16 do we have hooks-on for function in api or mantoray support of api. – Japanese team will investigate.
1015	UJ	The SM subgroup will 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	2004-10-01	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. 2004.11.16 still open
1017	UJ	The PCM group will create model, architecture, and v1.0 specification	Investigate and produce a Print Channel Manager model.	PCM subgroup	2005-05-31	The architecture subgroup will comment on the proposal. 2004.0823 shida upload report to ftp and send note to sc and arch group 2004.11.16 after f2f discussion, pcm group will reasscess their current architecture and submit to arch team and SC
1020	U	OpenPrinting.org website updates	need updated web page with structure, org, group, member, mail list, working group information . Web pages in English and Japanese is optional. submit to support.freestandards.org with changes	Takaaki Higuchi - Japanese Norm Jacobs - English	2005-04-31	2004.11.16 assigned 2005-04-05 Norm has taken the action to contact the FSG and get updates put in place 2005-04-06 contacted FSG about updates, waiting for tWiki to be installed on site so that we can make it self-service.
1021	U	remove req for all three api type from spec process	edit changes	Glen Petrie	2005-05-31	2004.11.16 assigned
1022	UJ	Evangelization We need to solicit, engage participation, and build awareness with more Companies, OpenSource Projects, and community members. We need to engage more companies. Ex: HP, Lexmark, Novell, Xerox, Canon, KDE, CUPS, Ghostscript	Identify companies and contacts open dialogue via email Participate in OpenSource projects through maillist, IRC, and contribution where printing ties in. Participate in workgroup meetings, discussion, and lists. Create up-to-date web presence (see AI 1020)	All contributors	ongoing	2005-04-05 This action was to combine/replace 1008, 1009, and 1011 Companies should include system vendors, software vendors, and printer vendors. Like HP, Lexmark, Novell, Xerox, Canon, Phillips, etc. OpenSource projects should initially include those with identified printing needs and interaction like GNOME, KDE, CUPS, Mozilla, OpenOffice, Xprint, Ghostscript, etc. Community members should include workgroups, consortia, and individual contributors like the PWG, Embedded Linux Consortium, etc.
1023	U	The PAPI group will complete v1.0 of specification	Add final wording for areas to be covered in post-1.0	PAPI team	2005-05-31	2005-04-05 action opened
1024	U	Find out about final FSG acceptance criterion	Contact FSG	Norm Jacobs	2005-05-13	2005-04-05 action opened email sent to FSG liason, awaiting reply
1025	U	Restart Driver workgroup	Email driver alias Set time to meet, set goals, etc.	Glen Petrie	2005-05-13	2005-04-05 action opened Glen sent email on 2005-04-04
1026	U	Publish Timeline for the next 12 months	Contact workgourps for input Consolidate/publish on web	Norm Jacobs	2005-05-13	2005-04-05 action opened
1027	U	Prepare slides for PWG/FSG meeting in Japan	Create slides, get review from JTAPI and PAPI	Ira McDonald	2005-04-09	2005-04-05 action opened Ira sent slides for review on 2005-04-06, so far there are no objections.
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	ongoing	Should we limit this to 4 use cases? 2004.11.16 open
2002	U	The JTAPI group will complete the specification for version 1.0.	Write specification	Job-Ticket Group	2005-01-31	2004.11.16 on schedule
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	make a schedule template (details, # milestones, draft, alpha, beta). Each subgroup leader will submit a schedule.	Norm Jacobs	2005-06-01	2004.0823 Mark will try to do. 2004.11.16 Mark will try to do. 2005-04-04 Norm will work on this.
2005	U	Create a simplified reference model document	base on current arch team information	Glen Petrie	2005-05-31	2204.11.16 started
3003	J	The Japanese group will translate the JTAPI specification and reformat into the appropriate format for submission to the Japanese government.	Wait for final JTAPI 1.0 spec.		2005-03-31	JTAPI will be done in January 2005. The Japanese team will summarize the specification before the final document is ready. 2005-04-05 waiting for AI 2002
3006	J	Will determine who in japan will develop the thin thread to be started on feb 1st		Toratani Yasumasa	2005-01-15	2004.11.16 assigned

Closed	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. Will be done in Japan. Release guideline often to get feedback for subgroups while developing guideline.	See AI 1003 2004.0823. Glen and Mark will connect with Olaf to get this restarted by August 30th. 2004.11.16 – remove req for all spec to include the 3 methods. Still a comment methodology for all three. 2005-04-05 closed
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.	2004.11.16 continue 2005-04-05 closed
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. 2004.11.16 no action 2005-04-05 closed, not active
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. 2004.11.16 no action 2005-04-05 closed, not active
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.	08/30/04	Document object should go in. Norm will post a note with a strawman. 2004.0823 – Norm send out a note but it may not have got to every one, so Ira will sent it out again. 2004.11.16 norm I done.
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	DONE	Done. CPL is an allowable license. However, the preference is MIT 2004.11.16 resolved. work product can be cpl, mit, bsd. doc is still open - glen
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	2004.11.16 discuss and action defined 2005-04-05 replaced by AI 1022
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	2004.11.16 Mark will address 2005-04-05 replaced by AI 1022
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 This needs a date and an owner or this will be removed from the action items. We need Glen's input. 2004.0823 Glen will try creating a strawman. October. 2004.11.16 closed
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	2004.11.16 see action item 1009 2005-04-05 replaced by AI 1022
1012	UJ	The steering committee decided on a priority order for new work with the current subgroups. 1) architecture 2) PCM (Print channel 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	DONE	2004.11.16 on going
1016	UJ	A new bidi subgroup called print channel manager (PCM) will be formed by Epson to account for the lack of a common bidirectional communications API.	Create a subgroup. Create a draft specification.	Steering Committee	08/30/04	The subgroup has been created. They are working on draft specification. 2004.11.16 done
1018	UJ	The PCM group will create a 1.0 specification.		PCM subgroup	01/31/05	2004.11.16 after f2f discussion, pcm group will reasscess their current architecture and submit to arch team and SC
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. It was released before 1013 was done.	Japanese members of steering committee.	DONE	The code has been released on TurboLinux (10F) and Epson Kowa's site in the old format. 2004.11.16 done
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 See AI3002	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. Nomura-san has translated the document. The Japanese group will schedule a meeting with the government. 2004.0823 Preparing material for presentation but not given. Will give update in Sept or Oct. 2004.11.16 done
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 08/30/04	2004.0823 Glen will try to start a template 2004.11.16 still open
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.		Shida-san	08/31/04	AI 3000-3005 will be discussed in the meeting with the Japanese community. Some use cases were created. Shida-san will put them together. 2004.0823 Shida will try to do 2004.11.16 shida will try to do. 2005-04-05 closed, not active
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).			08/31/04	The PCM summary will help make this happen. 2004.0823 This on-going but we have got any communications 2004.11.16 communication must be extended beyond f2f and include email. 2005-04-05 closed
3002	J	The Japanese group will then translate JTAPI white paper for presentation to the agency in charge of government funding.		Nomura-san	DONE	2004.11.16 not yet, it will submitted in the normal proposal cycle. Dec 10 th the Japanese will determine if the is a Japanese company willing to champion jtapi with Japanese government. If no Japanese company will support then the Japanese SC will submit current white as unsolicited white paper.
3004	J	HP has a patent on 1284.4 US05,453,982 Patent to be reviewed for conflict		Toratani-san	DONE	The bidi group has changed the protocol to avoid this patent. 2004.11.16 done. we can avoid the patent issue by changing the protocol.
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 Agency will make a private license. 2004.08.23 Kowa is study with the agency on this issue. 2004.11.16 closed. It has IPA modified conditional license for use.

FSG Open Printing Steering Committee Action Items

2005-04-06	9	21:36:43

Num

Glen W. Petrie

2005-04-05T22:19:00

jacobs