[lsb-discuss] In the "new" world

R P Herrold herrold at owlriver.com
Tue Apr 1 14:59:06 UTC 2014


On Mon, 31 Mar 2014, Robert Schweikert wrote:

> I know this is reaching a bit as we have not published the meeting minutes
> from the f2f last week. I did post a high level summary to the wiki
> (https://wiki.linuxfoundation.org/en/LSB_Plenary_2014#Meeting_Minutes)

I know there is the IRC transcript, and some additional 
minutes by others what might profitably be merged as well.  No 
doubt we will discuss such at tomorrow's call (alert to Jeff 
as to an agenda item, for both a Collab meeting debrief, and 
as to possibly adding more formal documentation of the event 
outcomes)

> A second example is distribution identification, i.e.
> http://www.freedesktop.org/software/systemd/man/os-release.html , 
> this AFAIK is currently not in the standard but is
> 
> a.) relatively simple to sum up in a problem statement and a solution plus
> test
> 
> and
> 
> b.) should not be very controversial
> 
> On the other hand it is already on freedesktop.org. 

I am unclear as to the last 'it' pronoun ... I think the 
'standard documentation' part is at freedesktop.org, but a 
test interface is not. We have often seen this with 
'incorporated' third party 'standards' documentation, with the 
testing tools over at LSB code space

We have discussed in the IRC channel from time to time, and I 
think I have an open bug to start a formal process of 
'mirroring' into an archive under LSB maintenance, remote 
standards statements.  We have been burned a few times, when 
linkrot has caused some holes in our 'upstream' references

As to adding a new tool at LSB or in some other test suite 
[Linux Test Project, and more] to probe and confirm assertions 
of a standard are met, an additional test seems valuable, save 
that it adds more maintenance load to 'keep it relevant'.  A 
common problem in testing with TDD, and unit tests, or course 

And the expansion into a more modern VCS as the next choice 
'after' the substantially mortibund BZR, is already underway 
by LSB. Thanks to Robert's 'seizing the ears of the tiger', we 
have a new 'presence' at GitHub where minimal effort 'pull 
requests' may be received.  My concerns about their EULA 
Indemnification clause are probably a product of 
hyper-cautious-ness, but ...

-- Russ herrold


More information about the lsb-discuss mailing list