Adding a New Package

To propose adding a new package to the Trilinos repository, please complete the following questions and email the responses to the Trilinos Developers mail list, CC'ing the Trilinos Framework mail list. The Trilinos Community will then provide feedback on the request. The Trilinos Product Area Leaders will approve/deny approval of new package requests.

1. What is the proposed package's name?

2. What is the purpose for the package?

3. Why should this functionality not be included in an existing Trilinos package?

4. The TriBITS build system supports easy build-time incorporation of Trilinos-compatible packages. This might be an appropriate alternative to official inclusion into Trilinos. On the other hand, if the candidate package can provide basic capabilities that might be used by existing or future Trilinos packages, inclusion in Trilinos might be best. Why should the proposed new package be added to the Trilinos repository, rather than being a Trilinos-compatible, stand-alone package that is included in the Trilinos build through an external repository?

5. What required and optional internal Trilinos packages dependencies will this code have?

6. What required and optional external TPL dependencies will this code have?

7. Will this be immediately considered Stable code or Experimental Code?

8. Describe the subpackages the new package will contain, if applicable.

9. What is the long term development, support, and maintenance plan for the new package going to be?

10. Who is going to maintain this package? If no-one can pledge long term support for the package, then when the package is released it should be made clear that the Trilinos community will not be providing long term support for the package.

11. What is the licensing plan for the package? Has the copyright and licensing process already been completed? Trilinos has a strong preference for a 3-clause BSD license.