Developer Meeting

Agenda:
   1. Defining services that cross team boundaries
   2. Who is responsible for defining and implementing services?
   2. How/where should services be documented
   3. SVN commit rights
   4. Jira etiquette
        * Are people assigned Jirta tasks or do they just choose one
        * Building outside of Jira/Confluence/SVN
   5. When can you get started with the nukleus implementation (former poc)
   6. Communication expectations
   7. Recurring page reviews
   8. Jira and Bamboo on list
   9. Team for Heidi
   10. Storage services
   11. OSGi on the capture side

Notes:

let's table for now:
What is storage?  What is distribution?
What is an inner service vs. outer service?

If the implementation is using REST, can specify "intents" (restrictions, qualifications).  If it doesn't meet certain criteria, you can determine whether the service is for you.  Custom intents are possible.

No default communication protocol for OSGI.

Capture considering OSGI.  
-> media packages created using local OSGI container.
-> ingest into inbox using DOSGI
Not sure yet if DOSGI is appropriate or if there should be an "out of band" agreement.  
Is DOSGI a barrier for institutions that want to integrate their own capture solutions?

Determine who is responsible for boundary services.
Ingest -> capture/process folks
Distribution -> processing/engage folks

Tobias suggests a light weight process.  emphasis on quick, lazy consensus. 72 hour time limit.  at the end

boundary services:
-> wiki and code for documentation

inner services:
-> code for documentation
-> Add a blocking jira task to every team, stating to update online documentation

what is the process for requesting code commits?
-> submit patches to your team's tech lead.
-> trunk per team, per iteration?  crucible?  appspot?

Process:
-1 person with commit rights everywhere.  
-he/she can create branches.  people work within branch.  no code is outside of svn.  process to gain commit rights (already identified)
-svn diff with trunk.  
-submit in jira ticket and email out to list for review.
-team lead approves code

jamie is master of dev quickstart pages.

need "quickstart" page or update existing one.


what does the nucleus implementation mean?  the fact that it is not there, how does it impact the other groups?

funded needs to go away.  

come up with must read list for people to review


tagging for subjects and

create matterhorn-automated jira/confluence/bamboo

other list conversation with other community

don't move matterhon related discussions off list

filters

capscribe
user facing applications
mpeg7 and added into indexing
conversion tool?

Captioning team