Meeting with James 8th June - hamstar/Braincase GitHub Wiki
Agenda
- Show layered architecture diagram
- Evaluation of software review for existing Wikis
###Actions from previous meeting on 28th May
- Create a layered architecture diagram
- https://docs.google.com/a/telescum.co.nz/document/d/1d8Cjm2cnDrs1Zzx4BVgZ16DmRLkMXAvUMOaqNOQhcsI/edit
- Finish Software Review
- https://docs.google.com/a/telescum.co.nz/document/d/1nHdgJBOYmLEnQ4XRGvANRlhxXHb3rTz0hg1_427naUk/edit
- Finish Vision
- https://github.com/hamstar/Braincase/wiki/Vision
Minutes
-
Software Review
-
Itil, a framework we could look at using
-
Issue: Code Review -> Why Not? ie Not Safety Critical, not enough manpower
-
Reasons for using comparison -> Use References
-
Layer Diagram
-
Add hardware Layer
-
Add OS Layer
-
Deployment dependencies
-
Vision
-
first paragraph, reference to academic paper he gave us -> Mindmapping
-
For reach feature, need references
-
"Exports into an open format" -> Remove PKB references
-
How Braincase allows development, free from servers, organisations
-
Remove passwords reference ->
-
Secuirty should be industry standard, not more than that.
##Issues
- Code Review, Why not
- Compare Windows vs Linux
- Compare Licence, security, community, documentation, developers
Actions for this meeting
- Further add to Vision Document
- Create another Layered Diagram
- Define a methodology for comparing software.