Hey all, I'd vote for user facing components.
Cheers Markus .::Yagni likes a DRY KISS::.Cheers On Mon, Dec 18, 2017 at 11:17 AM Myrle Krantz <[email protected]> wrote: > Hey everyone, > > I've requested a Jira project for Fineract CN named FinCN: > > https://issues.apache.org/jira/projects/INFRA/issues/INFRA-15684 > > Once we have this, we need to decide which way to classify the project > into components. There are two common approaches: > * by build artifact (ie repository), or > * by user-visible domain. > > Classifying by build artifact has the advantage that a newby starting > on a ticket will know which repository to make changes to. > Classifying by user-visible domain would make it easier for > non-programmers to create an initial classification with minimal > knowledge of the workings of the project. > > Since more than one component can be set for a ticket, we can combine > these approaches. We can create the following components > corresponding to UI domains: > 1.) offices > 2.) permissions > 3.) employees > 4.) accounting > 5.) member > 6.) loan > 7.) deposit > 8.) teller > > AND the following components corresponding to repositories: > 9.) repo-fims-e2e > 10.) repo-fims-web-app > 11.) repo-portfolio > 12.) repo-deposit-account-management > 13.) repo-accounting > 14.) repo-customer > 15.) repo-demo-server > 16.) repo-teller > 17.) repo-cheques > 18.) repo-payroll > 19.) repo-reporting > 20.) repo-office > 21.) repo-rhythm > 22.) repo-provisioner > 23.) repo-permitted-feign-client > 24.) repo-mariadb > 25.) repo-api > 26.) repo-lang > 27.) repo-identity > 28.) repo-default-setup > 29.) repo-integration-tests > 30.) repo-anubis > 31.) repo-template > 32.) repo-test > 33.) repo-cassandra > 34.) repo-command > 35.) repo-async > 36.) repo-starter > 37.) repo-crypto > 38.) repo-group > 39.) repo-data-jpa > > Does that work for everyone? > > Best Regards, > Myrle >
