Dev meeting 2016 02 09

Agenda

• New extension model
  • How to communicate with extension devs
• Release management/managers (stable & dev)

Log

<gawainlynch> ping Bopp carsonfull rarila rarilaDroid2 rossriley SahAssar slick0 
<rarila> pong!
<gawainlynch> …and a cast of thousands
<Bopp> Here!
<rossriley> hello
<SahAssar> pong!
<gawainlynch> OK… while we wait on Lucky Phil… 
<gawainlynch> SahAssar: Issues… how is that going and do you need cover/backup?
<Bopp> #4202 can do with a little updating, it seems. 
-[BoltIssueBall]/#boltcms- #4202 [open] [Tracker] Bolt 3.0 Release Blocking Issues https://github.com/bolt/bolt/issues/4202 
<gawainlynch> ¿qué?
<SahAssar> gawainlynch: Yeah, I've been pretty swamped. The lesser ones I can handle, but I'm going to need some backup on the more in depth ones
<gawainlynch> SahAssar: Do you have a strat for nagging rossriley? ;-)
<rossriley> ha
<SahAssar> haha, I'm going to make a label for 'need backup'
<Bopp> gawainlynch: what I meant (and not as critique on SahAssar), is that it seems there are a bunch of newer issues with [blocking release] and at the same time, I'm guessing a bunch of the ones listed have been resolved in the meantime. 
<gawainlynch> Seriously "under review" might work there and raising in here
<Bopp> +1
<gawainlynch> Bopp: We can all edit that issue though… unless I am missing the obvious
<gawainlynch> (which is likely)
<gawainlynch> rossriley: That PR on your extension… offensive or just haven't had time?
<Bopp> gawainlynch: No, you're correct. We all can, but we've all been neglecting to do so. :-)
<SahAssar> Well, ideally the person that tags it with blocking adds it to the tracker
<gawainlynch> SahAssar: I do try… apologies if I fail
<rossriley> gawainlynch: no I’ll get it merged… i need to update the tutorial to reflect too though
<gawainlynch> SahAssar: But good point wrt process
<Bopp> I'm raising it as a "Please don't forget to update #4202 if you add or fix a blocking issue" 
-[BoltIssueBall]/#boltcms- #4202 [open] [Tracker] Bolt 3.0 Release Blocking Issues https://github.com/bolt/bolt/issues/4202 
<gawainlynch> rossriley: Already done :-)
<SahAssar> gawainlynch: Well, I miss it often too, not meant as a jab at anyone :)
<gawainlynch> rossriley: I did the docs, then thought it was rude to not PR the extension :-)
<rossriley> ah ok: https://github.com/bolt/docs/blob/v3-extensions/source_docs/extensions/customfields.md
<rossriley> https://github.com/bolt/docs/blob/v3-extensions/source_docs/extensions/fieldtypes.md
<gawainlynch> SahAssar: No jabs taken… we're working process out as we go
<rossriley> those are the updated tutorials, hopefully I should have covered everything from a docs point of view with that
<gawainlynch> SahAssar: What I used to do was just go through the label list from time to time and compare to the tracker
<gawainlynch> rossriley: Awesome
<gawainlynch> rossriley: Do you have plans for more on the storage stuff?
<SahAssar> yep, I'll have a runthrough after the meet
<gawainlynch> +`
<gawainlynch> +1
<Bopp> Great.
<gawainlynch> rarila: I presume you're in a holding pattern waiting for freeze to lift?
<rossriley> gawainlynch: nothing specific on storage… although we might need a more general ‘How-to’ page if anyone has any requests
<rarila> gawainlynch: no, I'm in a not-having-sparetime pattern :-(
<Bopp> rossriley: Let's wait and see what people request most, and run with that. 
<gawainlynch> rossriley: Yeah, I think it is more the internals that is under-loved
<gawainlynch> I was able to run with it for Members pretty easily… but I have had a lot of exposure
<[BoltGitHubBot]> [bolt] SahAssar closed issue #4815: [RFC] The choice between rich-text (html) vs markdown should be up to the author on an individual basis, not a monolithic attribute of the field https://git.io/vg43K
<gawainlynch> i.e. it might not hurt to give a how-to that goes over a custom repo/entity 
<gawainlynch> #karma SahAssar 
<[BoltIssueBall]> BoltKarma for SahAssar is now 116
<rossriley> gawainlynch: yes, ok that sounds like a good idea
<gawainlynch> rossriley: I can to the table class part if needed… but I think the work in Members has an OK (?) pointer on that part we can draw from (again ?)
<gawainlynch> Overall… we're bringing in some pretty modern concepts to Bolt in this release
<Bopp> :-)
<gawainlynch> Some people might initially struggle with that
<gawainlynch> We can't teach them how, and I don't think we should… but pointers never hurt :-)
<gawainlynch> Anywya
<gawainlynch> :koala: can't type
<gawainlynch> Bopp: docs site refactor?
<Bopp> Going steadily. 
<Bopp> Working on getting the templates neat and tidy with Foundation 6. 
<gawainlynch> Bopp: Is it at the stage we can safely PR for stuff?
<Bopp> we can use the one codebase for showing multiple versions, more than two levels, stuff like that. 
<gawainlynch> Sound good
<Bopp> Yes, by all means.. I'm keeping my ongoing PR's small, so it'll be easy enough for me to merge and/or rebase incoming changes. 
<gawainlynch> Yeah, always a good strat
<gawainlynch> 300 commit PRs… pfft who'd do that!
<gawainlynch> OK… Anyone need to raise anything else?
<Bopp> The first one was larger, but consecutive ones will be more manageable. :-)
<Bopp> Not for now, I'll keep working on docs this week, mostly
<gawainlynch> Yeah… I was having a dig at carsonfull… or was it me :-P
<Bopp> oh, one small things
<Bopp> Based on feedback i've gotten, I'd like to integrate the cheatsheet into the docs site. ;-)
<Bopp> That's it for me.
<gawainlynch> IMHO… docs.bolt.cm should be the only site someone has to visit
<Bopp> Yes, i agree. Working towards that goal.
<gawainlynch> WFM
<gawainlynch> Given SahAssar is busy drinking vodka, rarila drinking beer and rossriley too… I'd say you and I agree