[Treebase-devel] TreeBASE hosting at Naturalis

[Rutger V. <rut...@gm...>]

Hi all,

here a quick status update on TreeBASE hosting at Naturalis, with some
pressing questions from our ICT dept at the bottom:

The "project bureau" of the Naturalis ICT department has considered hosting
TreeBASE and would be keen to do this, though they are aware that they are
not the only candidates for this so they are now developing a plan for what
hosting would mean and whether they can offer something that we can all
commit to with confidence.

The basic idea is that they would replicate as much as possible the
practices and configuration that were developed at NESCent, but folding it
a bit more into the ICT departments workflow and way of doing this. This
might include things such as:
- move code to github
- decide whether to adopt Jenkins (or something else)
- expand automated provisioning of dev/stage/prod servers using puppet

They want to make very, very specific agreements about who's responsible
for what. As far as they've been able to tell, this includes the following
topics, with they responsibility between parentheses:
- the content, i.e. editing and reviewing submissions (presumably, they
have nothing to do with that)
- the code, i.e. bug fixes and feature additions (again, they don't plan to
do anything with that)
- testing, i.e. do bug fixes and enhancements work as intended on the
staging server (presumably this is shared, e.g. they deploy, others test &
verify)
- system/db administration, i.e. checking performance and tuning it (to the
extent that this doesn't involve code modifications they would do this)

*And they would like further clarification on a number of issues - so the
following are important and require your feedback:*
*- do they need to worry about copyright issues w.r.t. the abstracts in the
database?*
*- what exactly does the annual growth rate (60%/pa) refer to?*
*- what's in place in terms of automation (e.g. continuous integration) and
how would they best be able to copy this?*

Thanks,

Rutger