Chassis Team Meeting – Mar 10 2015

Issues:

  • Labels added to indicate phases for issue according to Chassis Roadmap
  • File Structure
    • Initial commit landed, closed the issue so work can begin on CSS goals for Phase One.
  • Create Semantic Color Variable Names
    • sfrisk and others added some suggestions for variable names for required colors for Phase One to be used for the themeroller/customization. Prefer a smaller/simpler list of variables starting out.
  • Next Steps
    • Styling for typography, form elements, form validation (will need color variables), html4 elements, tables, and finally Grid.
  • Create a Grid System
    • Looking for a flexible grid, similar to suzy
    • This is a lower priority for Phase One, styling for other elements should be done first.

Chassis Team Meeting – Mar 03 2015

Version 1.0 Goals

  • Release Summer 2015
  • Features
    • Typography
    • HTML4 Elements
    • HTML5 Elements(?)
    • Form Validation
    • Form input state styling
    • grid
    • color pallet

Issues:

Pull Requests:

Goals for the Week:

  • Land PRs so we can start coding!
  • Add labels to help organize issues by release
  • sfrisk to create issue on color variables

Chassis Team Meeting – Feb 24 2015

Issues:

  • Is there some sort of roadmap? #39
    • Question came up about is the roadmap for this project to better understand the goals
    • sfrisk to create a wiki page explaining the roadmap for Chassis.
  • Create a SCSS Style Guide #41
    • Seemed to be some interest in working on this
    • Make this a PR to allow for collaboration (vs wiki)
    • When style guide is finished, submit it to contribute
  • Logo
    • Vote for the color you like best
  • Mailing List
    • sfrisk created a mailing list and shared link
    • join with your IRC and github username if you want to be a member

Pull Requests:

Goals for this week:

  • add yourself to the mailing list
  • sfrisk or arschmitz to update SASS file structure PR
  • sfrisk to add roadmap to wiki

Chassis Team Meeting – Feb 10 2015

Issues:

  • Javascript Summit
    • sfrisk and arschmitz speaking about Chassis today at JavaScript Summit
  • Performance Testing
    • arschmitz has a pull request for this
  • Create Mailing List
    • sfrisk creating a mailing list, need addresses of contributors
  • New Logo Designs
    • isaacdurazo created new versions of the logo. Please check them out and leave your opinion
  • Google Summer of Code
    • Chassis has been submitted as a potential member along with the jQuery Foundation to be part of Google Summer of Code

Pull Requests:

Goals for this week:

  • sfrisk to add addresses to mailing list
  • michaelarestad to update PR

Chassis Team Meeting – Feb 03 2015

Chassis Team Meeting – Jan 27 2015

Chassis Team Meeting – Jan 20 2015

Chassis Team Meeting – Jan 13 2015

Chassis Team Meeting – Jan 06 2015

  • Determine which SVG icon set to use #1
    • Initial discussion to cover which icons to support from the get go, based on current discussion in the issue
    • Decided to start out by created a SVG icon builder for just 3 placeholder icons to test the ability to select certain icons for builds, add in custom icons, replace icons, etc. michaelarestad to make a PR
  • Style Guide #11
    • Discussions in issue were leaning towards generated documentation.
    • Decided we needed to specify what we're talking about when mentioning "Style Guide," since the issue was getting slightly off topic compared to original description. (For example, Code Style Guide vs Pattern Library vs Design Style Guide). Issue is leaning towards auto-generated (or not) docs instead of "pattern library," which is really more what the topic was about. sfrisk renamed issue to "Pattern Library" to help focus issue. Discussion involving the generation of documentation moved to a separate issue/ Concerns raised regarding inline (auto-generated) documentation and how it could clutter code. Also discussed need for code style guides for scss and html.
  • File structure #29
    • MichaelArestad and cbracco opting for atomic structure in issue
    • Majority leaning towards atomic structure, with 100% complete modularity and independence. Discussion turned to possibly bundeling component styles with components rather than in the sass folder (possibly going the include/require an external spreadsheat route). Example here. However, general opinion seemed to be that putting components styling outside of the sass folder might be harder for new people to follow. Pros for that method would be making it easier to use just a button (for example), without pulling down everything in the repo. However, with a good builder, this shouldn't be a problem (similar to what has been done in jQuery mobile)

Chassis Team Meeting – Dec 23 2014

  • Naming convention #4
    • Going with BEM, considering using double dashes. We shall open up a new issue for design patterns
  • Performance Testing #2
    • Need to come up with a list of frameworks, what test pages will contain, and will they be individual components or like a kitchen sink (if later, will need to find a common set of components between various frameworks). Add note regarding that to #2
  • Create Logo #27
    • isaacdurazo will have time to work on logo after the 5th
  • Next Week's Meeting
    • Due to the holidays, many people won't be around next week. Canceling meeting for next week. Chassis meeting to continue on January 6th.