(gobby.debian.org /debconf13/bof/Lintian)

In this BoF session, we would like to know more about what you want from Lintian if it turned into a reusable static package analysis framework. (more automated rejections :) )

Some open questions I hope we can debate in this session:
  * Would you be interested in maintaining your own (Lintian-based) checks that are domain-/team-specific?
    - Maybe a set of checks for pkg-$lang to check the team conventions are followed.
    - Or just a $language specific check that apply to packages of that $language.

  * What about having your checks run on all packages in the archive regularly?
    - Is that "must have", "nice to have" or just "meh, don't care"?

  * Are there some design limitations in Lintian that would make it unsuitable for your purpose?
    - Is it enough to be able to process a source and the binaries built from it?
      (Would it be useful to be able to process two versions of the same package/source together?)

Tutorials+Examples:
  binary:
    /usr/share/doc/lintian/examples/checks
  source:
  doc/examples/checks
  perldoc doc/tutorial/Lintian/Tutorial.pod
  (or: debian/rules api-doc
     + $browser doc/api.html/index.html)

Yelling at people is fun. (redirect people complaining about autorejects to ftpmaster@) :)


Sprint?
 - Have a well defined TODO/task list