Dev meeting 2016 03 08

Agenda

• Release schedule, c.f. https://github.com/bolt/bolt/issues/2985
• Issues needing escalation
• PR: added config var replacement ability (#3005)
• v3.1
  • Short cycle
  • Freeze on feature work
  • Freeze on rebasing
  • Focus on unit/acceptance tests
• Change log updates for core team members
• For the docs: Which "install methods" should we list as 'first class citizens', and how should we name them?

Log

<gawainlynch> ping Bopp carsonfull gawainlynch ('cause I can) rarila rixbeck rossriley SahAssar sleezd 
<SahAssar> pong
<gawainlynch> … slick0 
* gawainlynch can't TAB
<phillipp> no ping for me today? xD
<rossriley> checking in
<gawainlynch> ping phillipp 
<gawainlynch> ;-)
<rossriley> ping phillipp 
<phillipp> connection timeout
<phillipp> :D
<Bopp> yo, here!!
<rarila> preserveComments: all: 552k, some: 552k, none: 411k
<gawainlynch> OK, slick0 is at the end of a sprint… carsonfull said he'd be here, but might be caught up… so let's rock
<gawainlynch> Easy one first. #3005
-[BoltIssueBall]/#boltcms- #3005 [open] added config var replacement ability https://github.com/bolt/bolt/pull/3005 
<gawainlynch> Yes/no? 
<gawainlynch> It's gong nowhere, been there forever
<rossriley> +1 from me
<Bopp> -1 until documented
<Bopp> i don't know what it does, or how to do it. 
<gawainlynch> -1 for dependencies that are now abandoned by Igor
<gawainlynch> (but I'm open)
<rossriley> there’s no dependencies is there?
<gawainlynch> rossriley: No, not in the PR… just in the direction 
<SahAssar> -1 until documented
<gawainlynch> I'd really like to hear from carsonfull as well on this, so if he doesn't show, I am going to bump this one to another week as I think he's with Ross on this
<phillipp> i dont see the usecase
<rossriley> well we do have service based lookups on controller routing and that wasn’t documented as far as I know
<gawainlynch> Welcome, Rix
<gawainlynch> rossriley: You raise a good point
* rixdroid in car still... 
<rossriley> If we merge it in though, I’ll sort out the docs before release
<gawainlynch> rossriley: Sounds like a deal
<Bopp> works for me. 
<gawainlynch> Release schedule… #2985
-[BoltIssueBall]/#boltcms- #2985 [closed] [RFC] Bolt Release Process https://github.com/bolt/bolt/issues/2985  — assigned to GawainLynch
<Bopp> Can't wait to read the docs on that, and find out what it does. ;-)
<rossriley> Bopp: you’ll be disappointed it’s a tiny feature
<Bopp> rossriley: don't crush my dreams. ;-)
<gawainlynch> Post 3.0… as mentioned earlier it would be good to have a few weeks before lifting freeze to give everyone rest… but personally I would like to aim for 3.1 to be small and test based
<gawainlynch> We've dropped our coverage a lot recently
<Bopp> Yes. +1 
<rossriley> I’ll go back to being the test fascist :-)
<gawainlynch> rossriley: Yeah, I had intended on putting more in too, but moving countries got to me :-)
<gawainlynch> rossriley: Seriously though, if you have the bandwidth… it would be good if you could step up for that and mark PRs as "Under review" and push back on merge
<gawainlynch> Probably a small job overall, but helpful
<rossriley> yes, I have no problem with that
<gawainlynch> I think we're still going to have some refactoring/features land in 3.1… but if we freeze quickly we can limit that, and if we're hard on requiring tests, that can help too
<gawainlynch> OK… next change logs
<Bopp> There'll be a fair share of bugfixes most likely, too
<gawainlynch> Bopp: Want to get everyone on page with our discussion on that
<Bopp> Yes. So, currently, i'm practically the only one who's updating the changelog.md periodically
<Bopp> I don't mind being the one responsible for that, but it'd be great if PR's from core members came accompanied with a one-liner for the changelog.
<Bopp> either as a direct change to the changelog.md, or as a line to copy/paste into that file by me. 
<gawainlynch> +1
<phillipp> +1
<SahAssar> Sure, sounds good
* gawainlynch is the biggest offender
<Bopp> We can't expect this of newcomers, so i'll need to stay alert.. 
<Bopp> but, every bit helps.
<gawainlynch> SahAssar: Anything you'd like to raise from Planet Issue Management
<Bopp> LESS THAN 100!!
<gawainlynch> #karma SahAssar 
<phillipp> partey
<[BoltIssueBall]> BoltKarma for SahAssar is now 123
<SahAssar> Planet Issue shrunk a whole lot during the last week due to great work from all :)
<Bopp> so many issues closed last week!
<SahAssar> #karma all!
<[BoltIssueBall]> Sorry but karma can only be added for channel members, all! isn't here and they lose out!
<gawainlynch> Haha
<phillipp> without campbelling them :)
<gawainlynch> I love our bot
<gawainlynch> phillipp: BoltCon & Themes… progress?
<phillipp> yeah BoltCon ... slow progress. I was too lazy to write some mails to collect more venue options
<phillipp> but i have many recommendations and tips for all the printing stuff we need some day
<Bopp> Nice!
<gawainlynch> Kewl
<gawainlynch> ejanuszewski: Did you have anything you wanted to add yourself, or just wanted to stay quietly listening in?
<Bopp> BTW, we can have shirts made at the place i always have them made
<ejanuszewski> I'm just listening in :)
<phillipp> not sure what you mean with themes, but we really need more quality themes. i thought about a little contest on boltthemes so motivate people to make themes
<phillipp> *to motivate
<Bopp> I think and hope a new base theme with good examples and best practices will help a little bit with that
<gawainlynch> phillipp: I just mean that you seem to have the "thing" with boltthem.es etc… so interested to hear how you're going
<gawainlynch> OK… anything from anyone to raise?
<phillipp> yeah need to work on boltthem.es a bit.
<gawainlynch> </meeting>
<rossriley> is the asset fix nearly done?
<Bopp> <meeting> 
<gawainlynch> Yes mate, I think we're down to tests
<Bopp> We're forgetting the "installation" part of the docs. 
<gawainlynch> It's been hard to get Carson and I into the same workable time
<gawainlynch> Bopp: So sorry
<aerth> hey i made an alpine/nginx bolt docker image it makes it really easy to launch a bunch of bolts on different ports
<Bopp> In short: I'm working on docs, and i'm going to shuffle the ways of installation about a bit.. 
<aerth> docker pull aerth/boltcms:latest
<gawainlynch> rossriley: But yes, the work left is small, just need to get time to finish it
<Bopp> put them on separate pages for starters, so we can gather analytics on them. 
<rarila> Extension developers, look out for the bolt.events API, that one is for you, in case you didn't notice!!
<Bopp> i've discussed with Gawain that we'll change the first listed one (paste a few lines, curl, tar, done) to be slightly different
<gawainlynch> On installs… Bopp and I were talking about this today, and there is a feeling that the archive install should be built off of a Composer install (ping rossriley)
<Bopp> It will stay the first one listed, but app/ and vendor/ will be outside the webroot
<aerth> docker run -it -d -p 8080:80 aerth/boltcms:latest
<rossriley> yes, that could work
<gawainlynch> This give us several advantage, we deliver a large set of people an easy default that is more secure… and if they can learn basic Composer, updating is easy
<Bopp> My _main_ reason to keep that one first, is that I really, really want the method that takes the _least_ amount of time and hassle to be the first thing newcomers find. 
<gawainlynch> …if not… untar a new one
<gawainlynch> ^ what Bopp said
<phillipp> i am for that
<rossriley> yes, so the default installs are we going to recommend a separate web dir now?
<Bopp> ok, i'll work on re-arranging the docs like that. 
<gawainlynch> rossriley: That is my desire, yes
<Bopp> Perhaps next week I want imput on the "naming" of those methods of installation
<gawainlynch> rossriley: We're moving that way (very successfully) at TK too
<Bopp> Ok, now i'm done :-)
<gawainlynch> OK… 30 second call for comments…
<Bopp> aerth: For 3.0 i aim to have a page with "other ways to install bolt."
<Bopp> aerth: You're very welcome to PR suggestions and your way to that page. 
<rossriley> it would be nice if a UI person could get move up/down implemented for repeaters
<rossriley> though not a blocker if noone has time
<Bopp> <drops mic> 
<aerth>  awesome 
<Bopp> rossriley: will re-ordering them in the HTML do? Or does it need changes under water?
<rossriley> reorder in html and then call the reindex js function
<SahAssar> Bopp: moving them in the html would remove the event listeners, no?(master...issue-4970) https://git.io/vaJiO
<Bopp> rossriley: Ok, we'll want that for 3.0! I'll open an issue for that. 
<SahAssar> Ah, got it
<aerth> one of you should make an official docker image from an automated from master ;D
<Bopp> aerth: You want it, you make it
<rossriley> aerth: I do have a set
<rossriley> that I try and keep updated from time to time...
<aerth> rossriley: i used a lot of urstuff for my nginx alpine one
<aerth> but you can make an "automated build" from github/docker connection
<aerth>  and people can "docker pull boltcms/bolt:latest"
<rossriley> cool.. I wanted to move to the new docker library images once they’re done
<aerth> https://github.com/aerth/docker-boltcms
<aerth> free to modify
<aerth> for the official
<gawainlynch> </meeting>