• Service fabric is something we've talked about and decided that it was out-of-scope for Amdatu 1.0; but it remains a concept of Amdatu. The documentation on it is still work in progress, as stated on the initial page (http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Fabric);
  • As part of the cleanup I've reshuffled most of the pages to a more logical place and removed much of the (temporary) discussion pages, see http://www.amdatu.org/confluence/display/Amdatu/Amdatu-641%3A+proposed+new+wiki+structure;
  • I do not have sufficient rights to remove the pages from the attic, I agree that these pages should go away;
  • There's no single definition of the platform, it is a bunch of services that in any form make up a platform. For example, the usage of services in BlueConic are different than those in Leren-op-Maat. Hence, it would be a bit weird to describe the platform as a whole...
  • Regarding the components with a "fuzzy" status:
    • Kitchensink is yet another form of the platform, used by us as a sort of playground for the new services we're developed;
    • Amdatu Parent & checkstyle are technical asset needed to have an uniform build structure for the various services we've developed. It would be a bit awkward to have official releases for something them;
    • AMS (aka Provisioning) has always been an official subproject.

HtH

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to