2017-02-07

[xaviervia]

No description provided.

[xaviervia]

• Nobody seems to be shipping unbuild babel projects to npm, so we should not prio that in Sagui.

[xaviervia]

• Generating content (screencasts & blog posts) around the projects would be interesting.

[xaviervia]

• Sagui can probably de-prio CSS modules

[xaviervia]

• Wouldn’t it be nice to have a snooze button on github issues?
• NPM or some other package manager could implement donations?

[xaviervia]

• An idea, probably not happening: move react-entanglement to a monorepo in batata-frita?

• It’s currently fairly hard to test different adapters

• We need to figure out a way to follow up on React Entanglement

[xaviervia]

Electron in Sagui will be done only after it's tried out in other projects: saguijs/sagui#308 (comment)

[xaviervia]

To follow up each project we probably want to do in a separate day:

• https://github.com/macaco-maluco/day-one needs to merge the big refactor branch

[xaviervia]

Prios:

1. Move mature projects to batata-frita (react-context-props, git-revision-webpack-plugin are low hanging fruit)
2. Sagui Webpack 2: first step though is to verify that the approach for extract text webpack plugin is not a hack
3. Merge Day One refactor
4. React Component for open source landing pages, probably using material ui or something like that. The idea is to be able to generate landing pages so that there is less friction around publishing. Once this is done(/while it's being done), the idea is to use it for React Entanglement.
5. Put aside some time to submit mature projects to curated lists