Mimir:Spring 2019 James Canavan Log

From Openitware
Jump to: navigation, search


Week Ending February 5, 2019

Task

Review 5th Draft Introduction

Revise "What Is A Programming Language?" of Introduction

Review Wiki-text-markdown-language

Propose template for text using Wiki-text

Results

Complete - Review 5th Draft Introduction

Complete - Revise "What Is A Programming Language?" of Introduction

Complete - Review Wiki-text-markdown-language

85% complete - Propose template for text using Wiki-text | I am still working on this template. I expect to have it completed Friday, Feb 8th

Plan

Finish Wiki-text template

Review Chapter 2, maybe 3 also.

Concerns

+The group does not have a clear objective at this time.

    - My understanding of what is expected and what our object should be
         - Create Wiki-template that is a standardized page structure which all future chapters conform to.
              - This structure should include rules that define the treatment of:
                    - Headers
                    - Bullet notes 
                    - Photos
                    - Citations
                    - Code Excerpts 
         - Edit current content. Do not create new content unless it makes sense to do so.
         - Create something to the effect of an "Enhancement Request" page where people can leave feedback, or suggest content change/add/delete
              - Example: In the 5th draft, I feel that chapters should be re-organized. I think that chapters 9, 10, 11 and 12 should be right after chapter 2.

Week Ending February 12, 2019

Task


Results


Plan


Concerns


Week Ending February 19, 2019

Task
  • Create Governance with regards to document management
  • Finalize styling format
  • Review editors work, if any.
Results
  • We defined (2) objectives; which are 1) condense what is written to be "a faster read" 2) create a "One voice" tone
  • We created a workflow - albeit a weak one. This will improve.
  • We created a "Structure/Cadence" for weekly meetings. There is room for improvement here.


Plan
  • I will create a governance document that details the rules by which documents should be created/edited/changed for all future groups to follow. This will include rules to make amendments to the rules which should go through some sort of approval process within the group. Each section and or chapter will have an "owner" whose responsible for editing that content and submitting to the Reviewer for review. The goal of having multiple editors and (1) reviewer is to capture that "one voice" feel, or in other words, a document manager who maintains all the documents and stylizes it to a specific standard.
Concerns
  • There currently are no guidelines or rules in so far as what is expected from each group member, what each member is responsible for, or how workflow should happen. I hope to at least start a workflow that facilitates good operation with regards to document creation & management.

Week Ending February 26, 2019

Task


Results


Plan


Concerns


Week Ending March 5, 2019

Task
  1. Get current state of textbook
  2. Formatting: look at Draft 6 to highlight state of chapters (2 weeks)
  3. Compare formatting of chapter 1 with other chapters


Results
  1. All Chapters start with a quote that can be applied to what the chapter is about. I like this.
    1. Few Chapters are missing a quote, however there is a header for a quote to be inserted, this is uniformed and good.
  2. All Chapters are uniformed with regards to using headers such as: "==Subject Title==" headings. This is good and looks good. Helps the reader navigate and is easy on the eyes.
  3. Chapter 1 is disconnected in the sense that it covers both an Introduction and a deep history lesson of programming languages.
  4. Chapter 1 does a good job at balancing the use of images, code blocks and tables. The positioning of non-text items is left aligned and makes sense.
Plan
  1. Remove "history" from chapter, make it it's own section
  2. Align chapter 1 formatting to match chapter 2


Concerns
  1. Chapter 2, albeit the most well formatted, is entirely too long.
  2. Chapter 1, is disconnected.

Week Ending March 19, 2019

Task


Results


Plan


Concerns


Week Ending March 26, 2019

Task
  1. Capture meta-knowledge of formatting decisions used in chapter 1
  2. Discuss changing/merging formatting from other chapters to chapter 1
Results
  1. The use of Bold & Italic words are not uniformed across chapters. Keywords should be in bold as they are in chapter 1
  2. Chapter 2 is like reading War and Peace. Great content... too much content. A lot of chapter 2 gives an intro to subsequent chapters. Why not put that content with the chapters it belongs to?
Plan
  1. Begin revising chapters for formatting.
  2. Begin "removing" & "word-smithing" awkward sentence structures
Concerns
  1. none at this time

Week Ending April 2, 2019

Task


Results


Plan


Concerns


Week Ending April 9, 2019

Task
  1. Re-work Chapter 1
Results
  1. Removed "History" section of chapter 1 and gave a History section in stead
  2. Began restructuring awkward & ambiguous words/sentences
  3. Unplanned: Created a "template" for sub sequential chapters.
Plan
  1. Next week, continue to work on restructuring
Concerns
  1. Book needs a good preface.

Week Ending April 16, 2019

Task


Results


Plan


Concerns


Week Ending April 23, 2019

Task
  1. Continue re-working awkward sentences
Results
  1. Chapter 1 completed in so far as re-working sentences
Plan
  1. Next week, start on preface
Concerns
  1. none at this time.

Week Ending April 30, 2019

Task


Results


Plan


Concerns


Week Ending May 7, 2019

Task
  1. Complete preface
Results
  1. Have not started.
Plan
  1. Work harder,stop stressing.
Concerns
  1. Time constraints.