While naming packages, developers should adhere to the following rules:
- Packages shouldn't have underscores, hyphens, or mixedCaps
- Packages shouldn't be named with generic naming schemes, such as common, util, base, or helper
- Package naming should be related to the function that the package is performing
- Packages should retain a decent-sized scope; all the elements in a package should have similar goals and objectives
- Utilizing internal packages can help while you're vetting new packages before they are aligned with your public API