[lsb-discuss] Unofficial LSB conference call minutes (2012-04-18, 11 to noon)
R P Herrold
herrold at owlriver.com
Wed Apr 18 16:24:08 UTC 2012
LSB teleconference
Wednesday, 18 Apr 2012 @11:00 to noon, US ET
Where:
(605) 715-4920 Access Code: 512468
Gobby:
gobby -j lsb-temp.pmman.net:6522 with passwd: LSB
IRC channels are:
#lsb-meeting at freenode.net during meetings
#lsb at freenode.net most other times
prior meetbot minutes:
no substantive content
http://stewbenedict.org/lsb/irc/meetbot/lsb-meeting/2012/lsb-meeting.2012-04
-11-15.01.html
THIS meeting's meetbot minutes:
permissions issues intruded and the bot was not started
Attendees:
in the form : name (organization) [irc_nick]
===========================================
Jeff Licquia (LF) licquia
Mats Wichmann (Intel) mwichmann
Russ Herrold (Owl River) orc_emac
Rick Troth (Velocity Software) rickt
Stew Benedict (LF) stewb
Glen Petrie (Epson)
Robert Schweikert (SuSE) robjo
potentials:
Denis Silakov (ROSA Labs) denis_silakov
Alan Clark (SuSE) AlanClark
Darren Davis (SuSE)
Jiri Dluhos (SUSE) jdluhos
Kay Tate (SuSE) ktate
Alexey Khoroshilov (ISP RAS) Alexey
Apologies:
==========
Posted Agenda:
=================
- LSB 5.0 planning: status of last week's tasks.
- How do you "get started with the LSB"?
- Charter: what's the status? What do we have? What do we
need?
(this is a bit heavy for one call. We will go in the above
order; anything we do not reach can be carried forward)
Other matter discussed on the mailing list:
- XSS update
https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3487
- GSOC
- Python 3
New business:
=============
Meeting opens at 11:00 with:
- Update on LSB 5.0 timeboxing: sane (Glen), dbus (Robert),
and the other uplifts (Jeff, ISPRAS)
Python3 drill in of one - four 40 hr person-weeks
Robert: dbus interfaces seem stable, but there are additions
over time; Jeff asks: do authors needing to access dbus tend
to prefer toolkit bindings and interfaces, over native dbus
calls? Robert: let's start at the lower level, and add higher
level toolkit interfaces, once an ISV requests it
Glen: sane interfaces are essentially stable; two 40 hr
person-weeks should cover the work; up to four if a scanner
emulator needs to be written and stabilized to test against
(Glen notes that he has a commitments that will stall his
advancement of this for a week)
Next step: Glen and Robert still have things to do w/ SANE and
D-Bus. Jeff will choose a small library and do everything
needed to import it into LSB 5.0, possibly ncursesw. Stew:
will also try to do the same. Russ: maybe w/ a different
library, like SANE, to avoid duplication of effort.
- Getting started with the LSB
Russ speaks to both the desire of the present developer /
conference call participants for 'hands to co-develop'; Also
out there is recreating a pool of people USING the LSB as
candidates for conversion into co-developers as well. The
mailing list simply no longer has new people coming to us and
asking how to get started
Jeff: no question the k.o melt-down hurt; publicity efforts
had to go to a back burner
Use cases are a good way to sell; Russ: are copies of prior
systematic marketing documents around from perhaps 3 or 4
years ago that could be useful; Jeff; not so much as LF was
more focused on advancing the LDN. LF has gotten less
'possessive' on branding issues (Meego, Yacto, Tizen spun out
to stand alone domains, and are simply enumerated with
out-links at the current LF web presence)
Robert recapping: getting a web presence going seems like an
early task. It not being clear that we on the call have
specific talents there. Linuxbase.org seems to be the place
for this. One starts as a 'casual contributor'. Mats: it
should be a welcoming environment and one should be able to
get started fairly easily Robert: and it should provide
satisfaction (positive feedback) quickly. Robert mentions an
example of writing a Tet test case, and getting it vetted and
integrated
So: a 'sample solved process doing such
or: even just fixing a typo; so: getting a local copy of the
VCS, creating a patch, filing the bug to get it reviewed and
committed
Glen notes: there is a wiki page: 'adding a new page to the
LSB specification' -- but stuff is missing, and it is somewhat
bureaucratic loady, up front; it was not clear where to send
it. A meta-description of the overall process (and the
deliverables) would have been helpful, rather than getting
drowned in details
Jeff mentions glibc devel's interest in integrating LSB tests
as expressed at the Collab Summit
Russ: I see grumbling about the feature-paucity of Bazaar by
some here in IRC. Is the DVCS we are using (bzr) off-putting to
the kewl kids who seem to have gone to 'git'? Mats' effort on
the review site setup was trialling work in this space - at
least a way to get patches accessible for commenting a little
more easily
- Bug triage
Mats: reminder: bug triage tomorrow (details below)
Call ends at local 12:05
Weekly Bug triage:
==================
irc-only #lsb-meeting at freenode.net
Thurs at 10:00 Eastern
Bugzilla stats as of 18 Apr 2012: 501 open (494 assigned, 4
new, 1 needinfo, 1 pleasetest). 496 open last week.
New last 90 days: 152, last 30: 28; closed last 90: 102, last
30: 34
Changed this week: 14, last week: 4
Bugs that are assigned but have no milestone: 275
Rollup bugs: 23
No-milestone bugs will be the focus of the next few meetings.
Not all bug categories fit the milestone model.
There was no triage meeting the last two weeks.
Reviewboard:
============
http://reviews.lsbtest.net/dashboard/
Next meeting:
=============
25 Apr 2012 11:00 to noon, US ET
gobby unofficial minutes are open for edit for at least 15 min
after each call, and then issued into the mailing list
=======================================
This document: LSB minutes 20120418.txt
More information about the lsb-discuss
mailing list