Comments (8)
The weekly mailer "This Week in Rust" contains a "Call for Participation" section with links to issues in various Rust repositories. They go even further by adding a fuzzy difficulty, allowing first-time contributors to tackle problems in line with their comfort zone.
It would be amazing to have something similar, perhaps with even more visibility than a weekly mailer. I think we stand to make great strides by showing people a way into Ember's repositories. I'd love to see something like this regularly added to blog posts. Throwing a call for participation section into release blog posts seems like a great place to start.
from rfcs.
@acorncom this is great! Though the fact that I'm only learning about it through an RFC comment shows an obvious outreach issue. Maybe some members of ember-help-wanted could be involved in a "Call for Participation" section on release blog posts?
from rfcs.
Off-topic (so will keep this short): @kybishop what you're describing above is what we're after here: https://github.com/ember-learn/ember-help-wanted If you'd like to help push on "Call for Participation" stuff, please get in touch on that repo (or in Slack), would love to discuss further
from rfcs.
from rfcs.
Quest issue to go with thanks to @martndemus: ember-cli/ember-cli.github.io#111
from rfcs.
So I set out to explore a bit of WebPack, and found (unsurprisingly) that it doesn't offer us much, but would be nice if they pivot to being a more generic bundler (which they seem willing to do based on discussions with @TheLarkInn), in which case it may offer us an easier bundle optimization story.
webpack maybe could work completely for an ember app but yes it would be a complex configuration and require assistance in understanding a noteworthy amount of ember internals on our end to help set it up correctly.
from rfcs.
Some good points, can I suggest this be refreshed to not be so "stream of consciousness", as that form of communication forces each reader to individually extract useful bits, as it risks leaving each reader in a very different place once they begin participating in this bellow discourse. Which opens the door for miscommunication and other issues such as unclear expectations or just unfocused venting. (slack or over a beer or something might be a better venue for that).
I suspect the above can be summarized (at-least partially to):
There exists a list of high leverage scenarios that require some change (doc, infra, invention) to be accessible to our users. (e.g. simplifiying service worker, etc.etc)
Given this, maybe a list of 3-5 of these scenarios can be curated (no solutions at this phase please, just outcomes/problems). From that, one we ensure are near/term and long term goals can facilitate. (If we collectively come to agreement).
I have a pretty good idea of what these are, but potentially by working with others we can both improve prioritization and also share some of the burden. But the only way to do that, is to correctly identify the individual aspects, flesh them out then approach them systematically.
from rfcs.
We are working on closing the ember-cli/rfcs repo in favor of using a single central RFC's repo for everything. This was laid out in https://emberjs.github.io/rfcs/0300-rfc-process-update.html.
Sorry for the troubles, but would you mind reviewing to see if this is still something we need, and if so migrating this over to emberjs/rfcs?
from rfcs.
Related Issues (20)
- convention for specifying browser support HOT 2
- Problems with standardized targets RFC #95 and javascript HOT 23
- configurable tmp directory [Docker] HOT 5
- Dropping ember data from the default blueprint HOT 1
- Making addon dummy apps less special HOT 10
- addon entry-point other than index.js HOT 5
- Public API to examine app dependencies from an addon HOT 3
- lib/broccoli/ember-modules-app HOT 4
- Generate Babel Helpers HOT 2
- Provide a way to skip import of add-on assets HOT 5
- Breaking "bugfixes" for an eventual 3.0 HOT 1
- Access to `app.options` is inconsistent HOT 3
- Configurable paths for Tree Paths HOT 5
- I'd like to discuss Webpack HOT 4
- Better server watchers HOT 10
- Expose API to customize and/or disable colors used in terminal output. HOT 1
- Import syntax should "just work" for ES6 modules available via npm HOT 17
- Don't set license in app's package.json HOT 1
- Support in-repo commands by default. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rfcs.