IV: Compensating Measures
In the event that a resource is not able to avoid or adhere to all areas of these guidelines, they may choose other compensating measures. For example, a community project already with a questionable domain name may be able to compensate by being clearer on the relationship between the site and the project, and the project does not expect that all community projects will meet all criteria at all times.
V: Inclusion in Core Infrastructure
If, by mutual agreement, a community project is moved into our core infrastructure, the LedgerSMB core team will require some level of administrative access to content and some relevant domain names. This can be achieved by transfering the domain to one under
ledgersmb.org, etc. (i.e. moving, say, a demo site from
ledgersmb.example.com to
demo.ledgersmb.org). However, the original maintainers will still be encouraged to run the project and will be given proper access to relevant infrastructure to achieve this end. While the core team needs the ability to straighen out problems should they arise, our time is better spent elsewhere.
Furthermore, donors of such projects should retain the right to acknowledgement of their contributions as this is beneficial to both the project and the donor.