Yes, exactly. Trying to combine the DRMAA2 tree with the pbspro tree could cause unnecessary complexity and work. The root for the new DRMAA2 project would be https://github.com/PBSPro/DRMAA2 and @subhasisb will have to create it for you. Then you can populate it with whatever files you need. You should build the DRMAA2 library on a system with PBS Pro installed, but without the PBS Pro source code present. That's what most end users will be doing.
If we go forward with this approach, you may structure your code as you see fit. You won't find me complaining about the unittest directory. You would also be free to install the library in either /usr/lib or /opt/pbs/lib. Ultimately, the prefix will be set when you call configure so you can change it later if you need to.
You list some bits of source code in your design document. Does all of this code come from the specifications?
Aside from the code in the specifications, will you be incorporating any code that was written by someone other than yourself into the project? If so, we need to make sure it is legal for us to do so. We must also include the following copyright notice in the package. For PBS Pro, this was done in the LICENSE file in the section entitled "Third Party Software Information".
Copyright © Open Grid Forum (2012-2016). Some Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that
comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice
and this paragraph are included as references to the derived portions on all such copies and derivative works.
The published OGF document from which such works are derived, however, may not be modified in any way,
such as by removing the copyright notice or references to the OGF or other organizations, except as needed
for the purpose of developing new or updated OGF documents in conformance with the procedures defined
in the OGF Document Process, or as required to translate it into languages other than English. OGF, with
the approval of its board, may remove this restriction for inclusion of OGF document content for the purpose
of producing standards in cooperation with other international standards bodies.
The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors