Some points of clarification

Everybody in the tech team (I call this way for the current whole stakeholders for the time being, but we need to define the tech team)

• Who’s who in the team? (Developers and some business experts?)
• (Re)organisation of the team
• How to communicate with others? (emails, Skype, Adobe, Gtalk, Gdoc, Trac etc)
• Shared calendar? (especially to report long holidays)
• Do we organise regular virtual meetings? (How?)
• How to organise( report/assign/curate/solve) a ticket? (to establish a workflow for bug fixing, new features, feedback, analysis etc).
• How to organise Trac Wiki?

Among developers:

• What servers will be used for what? (At least, (developer’s local instance), test and production servers. How to use Minerva and Hephaistos servers (ACDH) in comparison with Dutch servers?)
• What development tools will be used and how?
• Who are the admins of the servers and software?
• What are trunk and branch strategies? (for milestones/releases)
• What are the coding conventions?
• Who will make basic technical documentations (of the current architecture, workflow, configurations, practices etc)? (cf Official documentation for data ingestion/curation is planned. Re-organisation of CLARIN web documentation is planned.)

In relation to business team

• Who’s in the business team?
• How does the business (and/or curation) team work with developers? (also regular virtual meetings less frequent than developer’s?)
• How to write the business requirements (use cases, functional specifications) and technical requirements and specifications?
• How to work on testing?
• How to make decision on development (priorities, sign-off, release dates etc)?
• How to cooperate with user evaluation and marketing activities (eg CLARIN Plus)?
• How to work with other taskforces (CCR, legal etc)?
• How to work with other CLARIN service developments (Content Search, Weblicht etc)?