Basil.js Team Call 2017 Summary

Summary basil.js Team Call, Nov 17th 2017

Timeline
- November - March: Development / working on ToDos
- Mar 5th - Mar 9th 2018: basil.js Sprint
- Mar 16th: Feature Freeze
- Mar 20th: Release
- April TBD: Weekend meet-up in Basel
b-less
- Fabian will try to set up a "micro basil" and get b-less to work
- Agreed that we move basil to global namespace
- if possible that includes function draw() -> function setup() and function loop() -> function draw()
- if possible get rid of b.go()
- find a way to stop looping scripts()
- if the b-less turns out to have nasty issues, we stick with b. instead
Features
- We basically release with what we'll have ready in time
- Timo works on getting some important features in
  - rework of how transforms work
  - grabbing of user's env constants and resetting them in the end (units etc.)
- if issues have become really messy/long, a new clean and summarizing issue could be opened instead, so the old one can be closed
Documentation
- Ted and Benedikt will focus on the documentation, updating and adding to the tutorials, editing the website's contents etc.

Website will be moved over to github.io
Fabian will taking care of getting the old site to work on GitHub
- auto generating of reference
Forwarding from the old website to the github site will be set up
Generally the website should get a "facelift", but we'll stick with the current layout
Showcase
- well-visible call for project submissions via email
- sorted it chronologically, most recent project on top
- find a good way to include source code via metadata
Workshops
- new section that showcases past and future workshops
- small sticky header for "coming up next"

review process can be somewhat minimized or skipped entirely in some cases
only if there are questions our doubts about a feature an issue needs to be opened
for small stuff or features that try to catch up with p5 or Processing, PRs can be opened and merged right away

Screen redrawing issues in Ted's and Timo's classes -> Ted will open an issue
Random random issue in Timo's class -> Timo will open an issue
Twitter -> Ted will set up Tweetdeck, so all devs can post news on basil-related stuff