minutes (brief) from r-w telconf 11am friday 17sept04 (edt)
Leon Shiman <[email protected]>
| Newsgroups | gmane.comp.freedesktop.release-wranglers |
|---|---|
| Message-ID | <[email protected]> |
Brief Minutes of: X.Org Release-Wranglers' telconf: EDT 11:00(am) Friday 17 September 2004: attendees: kem, sk, jg, alanc, ee, ds, ls. - security release 6.8.1 final version nearly complete, including cosmetic changes. to be released today. kem helping ease daniel's heavy work load. - ee making release scripts. - discussion of future security releases, syncing to embargo date, propose security advisory announcement with security patch attached or linked,timed to end of embargo, with actual release and announcement following, allowing time for thorough preparation. - discussed joining vendor-sec. two reps required for overlap. two approaches: vendor-sec members join xorg and/or xorg members join vendor-sec. ee now working with v-sec through suse's v-sec rep/maintainer. process should be driven by xorg. xorg should have input to emabargo date. matthieu herbe was in v-sec, daniel not in v-sec but volunteered to help. volume of traffic in v-sec is a barrier to participating. Matt Zimmerman's name was proposed. Managing this is a an important x.org task. Markus Meissner's name was mentioned as having helped ee draft 6.8.1 security announcement. - doctools discussion. Soren (sp?) Sandman(n) script. old bsd doctools script(s) should be put in CVS. David Dawes (old) notes should be rewritten before being included in cvs [ who will do this?]. the sgml-smtp perl script is important. it was proposed that a more modern docbook format is preferable. it was noted that both gnome and kde use doc book. proposed that both be contacted. laurie watts at kde was mentioned. proposed forming a joint doc group on fd.o. pointed out that this is important to x.org. docs needing attention were: xf86 sgml, man pages, framemaker pages. - brief note that security page was required, but hat contacts were first necessary. x.org security button will be checked. any security page ont he wiki should require strong authentication for editing. [ no complaints tolerated -- leon ]