[lsb-discuss] unofficial LSB conference call minutes for 30 Apr 2014

R P Herrold herrold at owlriver.com
Thu May 1 22:19:15 UTC 2014

LSB teleconference

Wednesday, 30 Apr 2014 @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

in the form : name (organization)  [irc_nick]
Jeff Licquia (LF)  licquia
Robert Schweikert (SuSE)  robjo
Jeff Johnson (Open Mandriva) 
Russ Herrold (Owl River)  orc_emac
Kay Tate (LSB)  ktate
Rick Troth (Velocity Software) rickt

Mats Wichmann (LSB)  mwichmann
   (prior call commitment)

Posted Agenda: 

 - Status of LSB 5: build slaves, GTK+ 3, other bugs.

 - Discussion of pending items on "new LSB".
New business:

Meeting opens at 11:00 with:

Builders are chugging by and large;  Spot fixes here and there 
save in the s390

The C parser issue raises its head yet again.  Jeff L is 
talking about writing a special purpose tool to identifty GTK 
Structs.  Jeff J points out that GCC will emit post-processed 
'clist' <?> content. Jeff J also mentions Tom Christensen's 
perlish: c2ph  Russ sees: "Only perl can parse Perl" is 
attributed to Tom Christiansen, and when we have had this 
discussion before, several tools have been emntioned if we 
need to delve into the bowels of macro expansion and C++ ... 
the LLVM 'clang' compiler has such a feature as well

There have been some 4 series certification bugs coming in; 
Russ notes there is a way to brand and then test for the 
present of branding in libraries, and it is probably the case 
that we need to undertake doing and then checking that ONLY 
such are present in a testing environment.  Russ to file the 
bug with a proposal

Robert: the git is languishing; pull requests 9, 6, and 3 need 
love soon.  Robert will also send the mailing list a proposal 
for a periodic review session -- probably IRC based in 
#lsb-meeting  to make sure that content in the 'git' does not 
starve for attention.  Post call Russ did some 'git' training 
with some others on the call so they could approach 
participation.  Bug triagers and coders of the world, unite.  
You have nothing to lose but old cruft that should be 
refactored out

Call ends at local Noon

Weekly Bug triage:
The bug tracker is at: 
(A former bug tracker was used, but is not longer active at:
for people doing research.  Please do not use it for new 

Bug triage occurs weekly: irc-only #lsb-meeting at 
*** FRIDAY* ** at 10:00 Eastern

Bugzilla (lsbbugs) stats as of  1 May 2014: 
617 open, 614 open last week 
612 assigned, 4 new, 1 reopened, 1 needinfo, 2 pleasetest
New last 90 days: 62, last 30: 18; closed last 90: 38, last 
Changed this week: 5, last week: 11
Bugs that are assigned but have no milestone: 245
Rollup bugs: 25

Bug (bugs) stats:  no data
XXX open FHS
XXX assigned, XX new, XX reopened, XX needinfo, XX pleasetest

last week's bug triage minutes:

Minutes (text):

How to get involved:
 - join and participate in the mailing list
 - 'star', 'watch' and join with merge proposals our Github 
presence (free)
 - register for a bugzilla account (free)
 - watch, review, test and comment on the commits crossing the 
RO mailing list: 
 - join and lurk in the IRC channels
 - dial into the weekly call and participate
 - join in the edit of the weekly minutes in the gobby
   Free gobby clients available at: 
 - join bug triage and resolution
 - file and fix bugs
 - document matter in the wiki
   (requires LF web account to edit, free)
 - set up and run a puppet build master and build slave 
continuous integration tester
 - Read about editting the specification

Next meeting:
 7 May 2014 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_20140430.txt

 .-- -... ---.. ... -.- -.--
Copyright (C) 2014 R P Herrold
      herrold at owlriver.com
   My words are not deathless prose,
      but they are mine.

More information about the lsb-discuss mailing list