PurpleBooth

Features

• Automatically bump SemVer
• Update a personal homebrew tap
• Keep that pesky version in the Cargo.toml up to date
• (From dependabot) Get new versions out as soon as possible

Assumptions

• You don't want a changelog

GavinJoyce

These are some notes for the Ember Dublin March 2019 meet up. This hist can be found at http://bit.ly/octane-dublin.

Node 8+ is recommended for the workshop, as is the latest version of ember-cli.

Useful links:

• Ember Octane
• My Octane preview video (slightly out of date, MU mainly)
• Chris Garret’s series:
• Native Classes

machty

/* jshint node: true */

const EmberApp = require('ember-cli/lib/broccoli/ember-app');
const generateWhitelabelIndexes = require('./generate-whitelabel-indexes');

module.exports = function(defaults) {
  const app = new EmberApp(defaults, {
    // ...all sorts of config
  });

samselikoff

The Ember Community

Mission

Make Ember the best way to build web applications

Objectives

[ not our problem ]

searls

The 5-minute backpack demo

Here's what I carry in a Tom Bihn Synapse 19 bag when I travel for 1-to-n days. In general, I optimize for low-weight items, with a secondary focus on reducing maintenance. You can peruse a gallery of pictures, too.

Clothing

MelSumner

1. if you are not yet familiar with the CSS structure, please do one of two things: 
--put the CSS you think you need into the wip.scss file and tag @MelSumner in your commit (I'll put it in the correct place)
--get to know the awesome organized awesomeness of the CSS. It might feel tight at first, like a new pair of shoes, but they will be awesome shoes after a while. 

2. Writing CSS Rules because I love you but I've chosen process. 
# keep specificity low. If you're getting really specific, I'm so sorry to have to be the one to tell you this, but you're wrong. 
# don't use IDs
# lowercase class names, please. 
# put classes in alphabetical order if you can. 
# put the properties in alpha-order. It's *usually* as easy as highlighting the properties and hitting F9. 

GavinJoyce

(This is a WIP collection of resources for first time contributors to Ember.js)

Issues for First Time Contributors

Ember

• Contributing Guide
• Good for new contributors label
• Help wanted label
• Module unification quest

wycats

The Ember Creed

1. Optimize for programmer happiness
2. Convention over configuration
3. The menu is omakase
4. No one paradigm
5. Exalt beautiful code
6. Provide sharp knives
7. Value integrated systems
8. Stability without Stagnation

trabus

Overview

Pods are a type of file organization structure in ember-cli. They allow you to gather related modules and assets together in your file structure. Currently pod structured modules can live side by side with your basic modules because the resolver that ships with ember-cli will look up your path in pod structure, and then fall back to basic structure if no paths are resolved.

Soon there will be a point where some blueprints will only generate in pod structure, and others will only generate in basic structure. This will allow us to collect a list of types that support each lookup structure and only need to lookup modules once. This will also cause less ambiguity around what a project structure looks like.

TLDR

My opinion on pods is that they should not live in the same namespace as type based modules. We should re-appropriate 'components',' models', and 'routes' (or 'resources') as pod prefixes to house the concerns of global ui, data, and route specific ui, respectively. Everything else stays th

stevekinney

Major points:

• Let's us the the route:application outside of code samples instead of App.ApplicationRoute
• We should think about using some special CSS or other markup instead of comments at the top of every file.
• We considered combining the guides on views and components
• Pull requests should be opened on emberjs/guides, not emberjs/website