LSARC/2008/061 - Indiana check list

[Brian Cameron]

John:

 >      Indicate Sun's involvement in the community
 >      [ ] Maintainer
 >      [ ] Contributor
 >      [ ] Monitoring

Rather than ask whether we are a contributor or a maintainer, we should
ask how the project is involved.  Build fixes, code enhancements,
integration with Sun-specific services, G11N support, documentation
support, QA, a11y.  All of the above?

 >      Will changes be feed back to the community?
 >      [ ] Yes
 >      [ ] No - briefly explain

I think it would be good to "briefly explain" when the answer is Yes.
We should tease out what sort of involvement exists, and what is
planned.  Only Solaris-specific build/bug fixes?  G11N support?
What, exactly.

 >      Will we or are we forking from the community?
 >      [ ] Yes - ARC review required prior to forking
 >      [ ] No

There often is debate about whether applying patches is a "fork".
At what point do we define a fork?  How many patches?  Or do patches
not have anything to do with forking?

 >    2.2.3 Licensing
 >      Indicate the license for the component(s)
 >      [ ] GPL
 >      [ ] Other

This question seems less than useful.  What about LGPL, MIT, etc.?
A fill-in-the-blank would be better.  Perhaps should also ask if the
license has any exceptions (like media programs sometimes have to
allow IP plugins).

 >         3.1.2 Share and Sharable
 >      Are any components shared with other Free Open Souce Software
 > (FOSS)?
 >      [ ] Yes
 >      [ ] No

I am not clear what this means.  Could you explain, perhaps provide
an example?

I see no questions about the following sorts of things which would
be useful, I'd think:

- degree of I18N support
- existence of manpages and whether they describe the interfaces
   reasonably well.
- existence of installed API documentation for libraries or other
   interface documentation (such as gtk-docs)
- existence of any encryption
- whether the interface duplicates the functionality of another module
   we already ship (is it yet another database, for example).  If yes,
   please explain
- degree of a11y support (perhaps several questions for each use case
   GOK, orca, theming, keynav, etc.)
- Does the program follow usability style guide (such as GNOME HIG if it
   is a GNOME Program, or CLIP).
- Does the project install a GPL library to /usr/lib?
- Does the project install C++ interfaces