This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
Columns recommended for review by DAG, PLS, and REM are marked with a to signify "ready for recommended review"; signifies "recommended but not ready yet." The few items marked are tentatively recommended, cf. Notes column.
Another way of looking at the dates, as transmitted by Steve in e-mail:
|Documentation||An head page that provides a technically-logical progression of sub-topics in a "ToC" set of summaries and links, in an order almost identical to the more scholarship-centric/"conceptual" entry point to the documentation About Project Bamboo; much material is deliberately duplicated between these two pages.|
|See note to "Documentation" page above. Note that order of this page pushes Research Environments above Identity and Access Management – a conceptual to deeper-dive order that would not make as much sense to a technical reader more interested in progressing (in either direction, up or down the wedding cake) from capabilities to user interface where diversely-sourced capabilities are integrated (or, less likely, in the reverse direction). This page also de-emphasizes deployment-centric concerns, which are less likely to interest a conceptual or scholarship-oriented reader.|
|HowTo child page is not marked for review.|
|This is an overview page. Note that Book Model page is not marked for review because it is an excerpt of part of a page in the RE section.|
|This document was completed after PLS did his review of the documentation set. On 24 May, PLS was invited (along with several others) to contribute his ideas to the child page of this one, Future Development Directions for the CI Hub.|
(A Bruce Barton document)
PLS: Looks good to me.
|PLS: Looks good to me.|
|PLS: Great - very well documented!|
|Authorization and Policy||PLS: Looks good to me.|
|Authentication - Current Limitations and Future Direction||PLS: Looks good to me.|
sub-pages re: configuration, etc.:
This material is largely complete; exceptions are expected to be complete by end of May, with exception of Social/SAML Gateway doc, which will be some weeks late.
REM should review all documents linked in this row (all children of the page Centrally-Hosted Bamboo Services - Development-Deployment-Invocation).
DAG: Only necessary to review TOP level page Service APIs - Other Services with attention to characterization of U Chicago contributions, as segregated from "Centrally-Hosted Bamboo Services."
PLS: Not sure if you want to look at these at all.
REM: RESTful API documents for your review primarily. Links to Javadoc for SOA-layer API toward or at end of each RESTful service API page
NOTE: These are mostly complete; ready for review in light of exceptions noted below:
remaining work is
BSP Architecture [FA]
PLS: Looks good to me, although if the Enabling Arch section is not complete, perhaps the doc should be edited to remove this?
SJM: made changes per discussion with PLS on 22 May 2013
|REM to note code and API links at bottom of page|
(A Bruce Barton document)
PLS: Some of the commentary on the implementation reads a little odd (as though it was written by an external reviewer, rather than project staff). There is not a clear evaluation of the state of the implementation in use, as with some other docs.
(A Bruce Barton diagram)
PLS: useful, but I do not really understand the title.
SJM: Sorry, the title as given on this page was still a placeholder, this page now reflects the actual title of the document, Tool integrations in Research Environments
PLS: Looks fine. Although intro explains what was done and not done, much of the document seems to be design, rather than documentation. That's fine, but might be more clearly indicated somehow (e.g., in headings)
SJM: made changes to header to clarify, per PLS suggestion, on 22 May 2013
|PLS: I had forgotten how good Martin's essay is. Great stuff.|
|Not a lot to do here.|
|Not a lot to do here. PLS and REM might be interested to see where artifacts are located.|
|Bamboo Documentation FAQ||PLS: This is nice - great idea.|