lsb-futures TODO list ===================== Intro This file is a less formal way to keep track of lsb-futures tasks than using the candidate tracker, the BTS, or the postnuke stuff. Things get moved into one of those when appropriate. Last updated: Tue, 8 Mar 2005 15:29:37 -0800 by taggart DONE: things that are accomplished but need to be disussed at a futures meeting, get recorded in the minutes, and then removed. ======================================================================= EXISTING ITEMS: In progress, once completed move to DONE ======================================================================= Bugs assigned to futures http://bugs.linuxbase.org/buglist.cgi?assigned_to=lsb-futures@freestandards.org need to do a review of SUS for what it documents and we don't include need to generate an interface list somehow nick will file a bug with a list of what's missing these are either bugs, futures candidates, or policy decisions libffi http://freestandards.org/pipermail/lsb-futures/2004-February/001253.html haven't seen demand, ask gk4 if he knows more add but blocked on stability, demand Security standards http://freestandards.org/pipermail/lsb-futures/2004-January/001250.html When security subgroup is started, maybe contact this person? gnutls, openssl, kerberos, extra PAM modules, LDAP components, etc. http://freestandards.org/pipermail/lsb-futures/2003-February/000718.html OSDL was working on a udev thing http://freestandards.org/pipermail/lsb-futures/2004-April/001277.html the OSDL thing hasn't made progress mats will think about if we need to say anything multiarch http://www.linuxbase.org/~taggart/multiarch.html asyncIO - need to review tracker info mats will review bzip2 - need to review tracker info, not much actually uses it http://sources.redhat.com/bzip2/ main use would be rpm payload need owner $HOME configuration files - taggart create a doc page http://freestandards.org/pipermail/lsb-futures/2004-August/001324.html owen's list of libs - add list to tracker http://freedesktop.org/pipermail/xdg/2004-August/004322.html refer to the wiki maybe think about adding GConf? review LSB criteria - In particular "Best Practice". taggart will send out a message asking people to review What is the LSB's role with working with the projects to help them conform to their upstream standards? (example: POSIX, java) How do we document when we make exceptions to referenced standards? Do we need a policy here? How do we document this? license criteria discussion in http://freestandards.org/pipermail/lsb-futures/2003-November/001041.html http://freestandards.org/pipermail/lsb-futures/2003-November/001043.html stuff todo in http://freestandards.org/pipermail/lsb-futures/2004-September/001335.html taggart will import for review Stuart talked about things that people ask for that are out of scope for the LSB but could still use a standard because people will use them anyway, mostly admin like stuff utmp APIs, mount APIs, setent/getent APIs utmp API is already in could we create a standards module for this? Stuart has another idea for standardizing some stable well used ioctls things like maybe sound, joystick, v4l, etc. these often pop up when trying LSB certify apps Gordon will start looking at this, after he does Xextensions. Can be done in parallel Still need Thread Local Storage upstream status for non-ppc archs maybe ask Thorsten need a way to test it, gdb has some test cases for it that could be modified talk about supporting multiple lsb runtimes http://freestandards.org/pipermail/lsb-futures/2003-December/001094.html we think this is fully documented in the packaging chapter does this dependency on versioned provides hurt deb based runtimes? in particular this is broken at the lsb commands level (linux study group found it) finish the "building on the LSB" document? http://freestandards.org/pipermail/lsb-futures/2003-October/000991.html still interesting and maybe useful? rules are useful example: ulibc vs glibc take out of the mail archive and make a webpage (taggart?) this could be a chapter in the book too would be nice to have in the 3.0 lifetime aka "how to build a module" clean up the module documentation we think this still needs to be done mats has interesting graphs at http://www.linuxbase.org/~mats/ where is the code that generates this stuff? we should give this to developers to run on their own apps we should spend some time looking at the graphs now in cvs, need to create a webpage for them needs to be able to work on libs too, sorta working get the old doug survey data and write pages about it doug will send the anonymized data to taggart taggart will clean up for review some people wanted to see the data, taggart taggart will remind doug about this old ISV survey, should it be cleaned up? http://www.linuxbase.org/~gk4/isvsurvey.php disable with a pointer to somewhere else OSDL did an analysis of common packages among 8 distros Cliff sent a pointer to the list taggart should add a pointer on the identification page ELF group still on hold due to SCO did this get solved? killproc init script function http://freestandards.org/pipermail/lsb-discuss/2003-May/001585.html ping Mark Hatle ask him what he did Tobias would be good to look at this, but he's busy SuSE might have thoughts, since they're using the LSB init stuff taggart will send mail to them never replied to this http://freestandards.org/pipermail/lsb-discuss/2003-May/001576.html good idea, we've talked about it before out of scope for LSB, another standard would be good, need someone to drive Init script $named boot facility, did this get fixed? http://freestandards.org/pipermail/lsb-discuss/2003-May/001582.html ping Mark Hatle about it (along with the above) ABI best practice document still needed freedesktop did one, stuart will send a pointer to futures remind stuart taggart will add it once he sends memory locking http://freestandards.org/pipermail/lsb-futures/2003-April/000815.html is this still desirable? taggart ask lsb-discuss the "open source POSIX tests" project has some tests for this patent issue never got addressed http://freestandards.org/pipermail/lsb-futures/2003-February/000718.html still on the FSG BoD todo list taggart will start on a template document for contacting upstream authors wrt standardization group criteria according to "what's needed to create a module" vs "what's needed to be in the LSB certification". module creation and orphan guidelines taggart will write something up unless someone beats him to it gordon and rajesh generated some data on application library usage put script and data on identification page mknod has been removed, maybe add to kernel page taggart will add add SE Linux to list of Security group stuff maybe they have tests? taggart will create a TODO list for the non-existant security group we'll let the security group add it when demanded there may be lsb-core implications add workgroup "owner" and initial requestor (where known) to all candidates that don't have them taggart will do this maybe figure out a way to remind owner when things get out of date Jim promised to send something about OpenPrinting, Accessibility, and OpenI18N to the list. Stuart needs to review/correct Xextensions tracker info fix Xextentions tracker to point to wiki Stuart needs to review/correct MAS tracker info taggart will talk to paul anderson and see if he can help with Xextensions nick needs to review/correct NPTL tracker info this is done? talk about TCP wrappers security but dependent on adding some kind of inetd both could be covered by the generic install method stuff we've been talking about make atk, glib separate candidates taggart will do add libogg/libvorbis/libvorbisfile libreadline, blocked on license libsane, blocked on demand add libXpm Rajesh needs to add inkscape, dia, python, perl to symbol analysis process Consider adding rendezvous as a managability candidate taggart needs to find out if HP's managability apps are available for rajesh to analyze marvin needs to find out if IBM's managability apps are available for rajesh to analyze look at libmng (wrapper layer around image libs) taggart add as a candidate look at boost as a candidate (c++ add ons) look at using boost as a test for our libstdc++ NEW: new items, need to be discussed at a futures meeting before they can move to EXISTING ======================================================================= need to review pre-January 2003 mailing list and look for todo items