• Pick Teams
• Slack Channels 
• Start GitHub
• Brain Writes
• Wire Frames
• README
• Scrum Board     
• Running Project
• Individual Home Pages
• Journal TPT

• Scrum Boards and Issue for each individual (.5 to seed). 
• GitHub plan and commits by each individual (.5 to seed) 
• Distraction policy in effect immediately (-1 point from seed)

• M - Stand Up Meetings (Scrum Team and BOF as needed). BOF Deployment Tech Talk 3
• Tu - TPT 3. 
• W - CCC
• Th - PBL 1.0 Live Reviews, AP MCQ Practice Test Due
• F - Elephant Gift and/or Potluck? 

• see Canvas
  
  

• PBL - Look for a real need, Teacher/Student need, Educational Study or Simulation, Campus Club, Campus Interest, Business Interest, Charitable Organization, etc
  • Starting Objective is to begin a code base.  Longer term vision is to  build skills for a final project in Trimester 3.   IMO, it is much more interesting to work on something that has 3rd party interest and that you can ultimately acquire a sponsor.  This Trimester is to get us ready.  
  • Designs are required and must meet Teacher Approval.  Be sure to pick something that you don't burn out on after a couple of weeks.
  • As a Concept/Idea in Education Need...  Highlight all 5 Big Ideas from CB.   Make a student site that one Ups college board.   The Web Site covers key topics, but the one Up site includes code and projects.  Essentially, remake that site to be Student Friendly, More Code, and less Video.

• Two to Three TOs/OOs in class to Facilitate TPT, TT events.  Coordinating across Team TOs/OOs
• Serve as Project Owners in Agile Development, process.   Essentially acting as Sponsor of projects.
• Help in setting up and approve projects and ideas.  
• Assist in planning common or shared code across all Scrum Teams, ie User Database and APIs
• Coordination for Unit #1-#5 MCQ reviews.  Trying to make things interesting with individual challenges, engagements, hacks, kahoots, etc.  (very little lecture)

• Scrum Master.  Ensure roles are assigned.  Build Scrum Board.  
• GitHub Admin.  Setup Project in Git.  Integrate any starter code from Trimester 1.  Build policies for Fork and Pull requests.
• Primary Designer.  Primary Designer and Layout manager.  Organize Jinja2 Enabled Templates, ensure usage of Bootstrap (minimize CSS customization per page).  Establish plan for overrides on each of the User Pages.
• Deployment Manager (RPi or AWS).  Deploy Web site.  Establish policy and frequency for updates.  Ensure site is not broken and always alive for reviews.
• Technical Officer from Scrum Team.  Works with Teacher, Classroom TOs, and BOF TO's to form TPT lessons and Tech Talk Topics for Trimester.  Also, facilitates learning of Technical Concepts within Scrum Team.

• Bootstrap starter template, 
• Society layout.html
• head, style, script, body
• Society templates
• Society statics

• The focus is to organizing your files in Python.  
• A benefit is on grouping py, statics, templates into a local structure and establish clear directory of ownership
• Helps to avoid merge conflicts
• Logical means of accessing Functions and Statics with url_for, avoids path confusions

• Establishing consistent style across HTML, review starter templates
• Bootstrap has it all:  Containers, Grids , Cards,  Navbars etc

• Objective is to preserve session properties
• Requires Light and Dark design considerations for each page, review "Starters" runtime menu
• Introduction to Sassy CSS (SCCS), used to support Dark Mode color actions, custom.sccs
• HTML usage of Bootstrap Colors joke.html
• Local storage and Java Script

• Install node.js
• From Terminal in IntelliJ
  • npm install -g sass
  • npm install --global less
  • npm install bootstrap
• In .gitignore add lines

  • node_modules
    /node_modules/.package-lock.json
    /static/scss/custom.css.map
    /package.json
    /package-lock.json

• In IntelliJ Plugins add "File Watcher"
• In IntelliJ Settings Tools-File-Watcher. configure SCSS
  • See Visual with Page

• M - Planning meeting between now and tree. Stand Up meetings for Scrum Team.  Form TPT from Student OO's for Tri 2.
• Tu - Student Led TPT Schedule
• W - CCC,  Design manager BOF.  Tech Talk 1.1, Organizing Templates and Files
• Th - CCC, Technical Officer BOF. Tech Talk 1.2 - Accessing data Asynchronously
• Th & F - Conduct Scrum Master / Teacher Project Reviews
• F - CCC, OOs.  Review ticket Crossover score and TPT and score, focus on fellow BOF.  

• see Canvas

Innovation Sprint 1,2
Week 2

• M - Stand Up meetings (Scrum Team 10 minutes and BOF 10 minutes)
• Tu - See TPT schedule.  After TPT Designer BOF to instruct on layout guidelines within Scrum Team.
• W - CCC, Scrum Master to share Create Task plans and weekly tagging to post Winter Break on Scrum Board with Teacher.  
• Th - Tech Talk 2: Teacher and TO BOF SQLite Database Intro.  Scrum Team (Scrum Master, GitHub Admin, Deployment Manager) perform release day policy training.
• F - CCC, About Pages 1.0 Due via Deployed Server due, details on Canvas (Live reviews by Teacher, OOs, TOs)

• see Canvas

1. Model has a function is where we retreive data.  Model Definition has a Class where we define and store data in a Table (Python/SQLite).  This includes Filtering and returning dictionary data from the Database.  Details on Model definition will be a future Tech Talk. 
2. View is where we a form to search the data (HTML/JavaScript).  The Javascript includes a fetch for sending data from User to Backend.  BootStrap infused HTML, JavaScript Fetch, and dynamically building result Container.
3. Control is where we set up routes and direct traffic between Model and View.   Receiving request header, formatting response JSON, and handling success/errors are responsibilities of control.

• Pressing Search button and leaving search box is empty will return all the data.
• Entering a string and pressing Search button will look for partial match in database, filter is looking for result in either  name and email.  
• Result area is under Search Box.  This area is cleared between each search.

• A "Table" is a Data Structure within a Database.  
• A "Table" definition in Python/SQLAlchemy is manifested with a "Class" in Python.
  • A Class is the combination of many data structures (ie list + dictionary),  
  • A Class has many Functions (see def indents inside Python Class
  • A Class inherits code and functionality of packages (see class Users(db.Model)). 

1. Model Defining the Table Class
2. Model Testing and Initial Setup
3. Model Defining function to support CRUD operations 
4. Control Methods for Create, Read, Update, Delete or Alternative CRUD API definitions 
5. View Here is a runtime showing off some CRUD. All the MVC code is show at the bottom of this page.

• README. You will have a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.  Also, README will continue having  Individual quick links and Time Boxed changes per Canvas assignment.  Your project could have other *.md files to cover specific topics, however, for these kind of items you may consider WIKI.
• WIKIS.  Wikis provide a place in your repository to lay out the design and high level roadmap of your project.     WIKIS should be capture longer "stories".  Most of the presentations we had in Trimester 1 could be authored in WIKIS. Think about how wikipedia is organized.
• Issues.  Use GitHub Issues to track assignment within team, feedback from other teams, or bugs.  There is integration between Issues and Pull requests, when you want to manage you code base more effectively.
• Project Board.  Beta Project Board.   There needs to be a view into your Issues that easily identifies status.  Kanban is the Scrum Board style we used.  There are other presentations, your README should present the presentation you use and is comfortable with your team.

• P3: Avinh, Sophie, Anthony
• P4M: Raiden, Katie, Aadya
• P4N: Arushi, Riya, Yolanda
• P5: Allison, Christina, Soren

• Page must Extend from Layout and have special customization (color pallet, background, etc)
• Picture with Mask that toggles to Picture of Choice (ie pic without mask)
• Pull or show data (Web API) with information of interest
• Establish link(s) to journal and other key indicators of your work and progress (remember pop quiz)

• Padlet and Canvas will contain weekly assignments
• Instruction will be provided on Canvas for how CB items will be graded
• TPT will continue, but we will have more involvement and rotation.  Activities should be interactive, very little lecture.

• CB Performance Task (practice)
• Proctored AP MCQ Test

• PBL Project for N@tM
• Talk about client recruitment

• Pages and Jekyll Challenges
• TT4 Challenges

Python Database Modeling Sprint 4
Week 5

• Start Indi Reviews
  • Home Page
  • PBL Issues

JavaScript Simulations Sprint 7, 8
Week 8

• Finish Indi Reviews
  • Home Page
  • PBL Issues

• Obtain Equipment.  (RPi or AWS)
• Git setup.  Setting up an environment on deployment host to synchronize changes.
• Flask, Python.  This involves setting up a Virtual Environment and Pip packages to run  the Web Application on the deployment host.  This process involves requirement.txt and resolving any dependencies for Web Application.
• Service File.  This requires Gunicorn testing and running the Web Server in WSGI standard.  Also, this involves building a Service file to run and keep-alive the Web Application.
• Nginx setup.  Build a Reverse Proxy configuration setup directing HTTP(S) requests to Web Application. This setup can support multiple Web Applications.  For instance, you could split your application between Front End and Web APIs.
• DNS routing and port forwarding.  This involves a friendly domain name to route to the server hosting the Web Application proxy.   Port forwarding is required when server has private IP and is behind a router.
• Certbot (certbot --nginx).  This is certificate setup to enable your Web Application to be secure.

• Pull from GitHub
• Check or Update Dependencies
• Restart Service File

• “Talk is cheap. Show me the code.”
• “Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.”
• Microsoft isn't evil; they just make really crappy operating systems.

• "git clone" makes a local repository (decentralized) from the cloud server (GitHub).   
• A .git directory contains a local database (see illustration) that keeps track of local changes, "git commit" makes a child of the original parent on the local directory.  Git commits over time are a series of SHA's.
• A .gitignore file tells .git to ignore certain files in directory tree (ie .idea)
• The "git push" command moves files from local system back to cloud server (GitHub)
• Often a merge is required as a decentralized system has many simultaneous contributors.
• Git branches and/or forks can be used to push code to  isolated locations to on the server/cloud.  This simply delays the inevitable merge, but has benefit of keeping main branch of project stable.
• Pull requests is common process used to merge code from isolated branches to main branch.

• Pull Requests and Branches.  
• An alternative to branches is Forks.
• IntelliJ Branch Creation
• IntelliJ Apply Branches
• IntelliJ and Pull Request Video

• How have you started you GitHub project?  Did you create a .gitignore to avoid committing files that don't belong in version control?  Did you make sure NO .idea files are in your GitHub repository.
• How do you manage commits to avoid problems?  
• Have you considered branching techniques with pull requests?  
• What actions will you  take this Trimester to get better at managing merge or commit problems?