00:05:34 <ralsina_> This is quite a bit more than I expected: 00:05:35 <ralsina_> 249 downloads in the last day 00:05:35 <ralsina_> 821 downloads in the last week 00:05:35 <ralsina_> 2794 downloads in the last month 00:06:04 <ralsina_> And that is with our website sending people to download at github 00:35:38 <Aeyoun> ralsina_: where is those downloads happening? 00:35:51 <ralsina_> PyPI 00:35:56 <Aeyoun> of course 01:48:46 -GitHub[nikola]:#nikola- [nikola] ralsina created check-404 (+1 new commit): http://git.io/vJ9hE 01:48:46 -GitHub[nikola]:#nikola- nikola/check-404 9d3e79a Roberto Alsina: Use https for nikola's URL 01:49:35 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to check-404: http://git.io/vJ9hK 01:49:35 -GitHub[nikola]:#nikola- nikola/check-404 2103aa4 Roberto Alsina: Simplistic remote URL checker 01:57:20 -travis-ci:#nikola- getnikola/nikola#4910 (check-404 - 9d3e79a : Roberto Alsina): The build failed. 01:57:21 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/commit/9d3e79af7081 01:57:21 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61400642 02:04:58 -travis-ci:#nikola- getnikola/nikola#4911 (check-404 - 2103aa4 : Roberto Alsina): The build has errored. 02:04:59 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/9d3e79af7081...2103aa4c48aa 02:04:59 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61400676 02:10:18 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 2 new commits to check-404: http://git.io/vJHJL 02:10:18 -GitHub[nikola]:#nikola- nikola/check-404 f115f8a Roberto Alsina: require requests 02:10:18 -GitHub[nikola]:#nikola- nikola/check-404 0ecdc00 Roberto Alsina: updated changelog 02:11:53 -GitHub[nikola]:#nikola- [nikola] ralsina opened pull request #1693: Check 404 (Issue #1684) (master...check-404) http://git.io/vJHJr 02:18:03 -travis-ci:#nikola- getnikola/nikola#4912 (check-404 - 0ecdc00 : Roberto Alsina): The build failed. 02:18:04 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/2103aa4c48aa...0ecdc00ad8ac 02:18:04 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61402083 02:34:54 <randomuser> hey ralsina_, can you help me understand rest metadata better? 02:35:02 <ralsina_> randomuser: sure 02:35:15 <ralsina_> randomuser: ask away, I'll be around some 15 more minutes :-) 02:35:25 <randomuser> I want to use some arbitrary things, but am not clear on the difference between ".. thing:" and ":thing:" 02:35:38 <randomuser> nice, I'm glad I didn't wait longer to speak up :) 02:36:56 <ralsina_> basically, Nikola only looks at ..thing: at the beginning of the post 02:37:03 <ralsina_> and totally ignores :thing: 02:37:11 <ralsina_> I sorta want to support it tho 02:37:13 * randomuser nods 02:37:18 <randomuser> what does docutils do, though? 02:37:40 <ralsina_> *some* docutils-based tools use :foo: at the beginning of the post (after document title) to get metadata 02:37:50 <ralsina_> for example, the LaTeX writer will use the author data 02:38:17 <ralsina_> I don't have much detail about what docutils does with those fields, and don't recall it being documented 02:38:34 <randomuser> it sounds like the convention is to use ".. directive:" rather than ":field:" 02:38:48 <ralsina_> In Nikola yes it is. 02:39:09 <ralsina_> Keep in mind that Nikola supports arbitrary metadata, and you may not want it to be visible 02:39:23 <ralsina_> Docutils extracts data from a field list (the :foo: bar things) 02:39:26 <ralsina_> but it SHOWS it 02:39:32 <randomuser> I'm thinking abstractly; the category situation means nikola doesn't scale to what I need 02:39:45 <ralsina_> I don't know what you need :-) 02:39:53 <ralsina_> You can probably just abuse tags 02:40:00 <randomuser> but, you're the rest expert I know, and this is where I know to find you, hope that's ok :P 02:40:13 <ralsina_> using something like foo/bar/baz as tags 02:40:41 <ralsina_> randomuser: if you can describe quickly what you NEED with categories, I may suggest a workaround and/or decide to implement it 02:40:48 <randomuser> sure 02:41:33 <randomuser> if you look at http://docs.fedoraproject.org/ the pages are categorized one way: by applicable release 02:41:45 <randomuser> it doesn't scale up well 02:42:24 <randomuser> so I want to enable people to submit short articles, tutorials, etc; that means a more browseable content hierarchy 02:42:52 <randomuser> it's a significant departure from a blog site, though... 02:43:06 <ralsina_> so far so good 02:43:16 <randomuser> :) 02:43:23 <ralsina_> Still don't see what is not supported 02:43:34 <ralsina_> You can create absolutely arbitrary hierarchies 02:43:54 <randomuser> ok, maybe I just need to figure out how 02:44:38 <ralsina_> Maybe post a real description in the mailing list? Just a blue-sky thing: "I want a site that organizes things this way, and I want to present them this way and this way" 02:44:54 <ralsina_> Propose your wildest dream, then we'll cu it down to what's doable 02:45:03 <randomuser> well, I've discussed it with ChrisWarrick and he pointed me at the category plugin 02:45:16 <randomuser> nested category pages, basically 02:45:48 <ralsina_> That's supported, but you probably want tags, not categories 02:45:56 <ralsina_> since categories are one-per-item 02:46:08 <ralsina_> Use path-like tags, and present them as paths 02:46:29 <ralsina_> so tag a document Fedora/22 and you can show that as a tree 02:46:45 <ralsina_> And then tag it document/tutorial and you can show it in THAT tree as well 02:47:05 <randomuser> well, it would be more like "User Docs/Networking/NetworkManager/Routes" 02:47:11 <ralsina_> It *will* need some template tweaking but you already assumed that, right? 02:47:18 <ralsina_> Sure, whatever you want 02:47:27 <ralsina_> just create as many "paths" as places where you want to show it 02:47:34 <ralsina_> Then you show it :-) 02:47:36 <randomuser> or "Contributor Docs/Infrastructure/Deployment" 02:47:46 <ralsina_> In fact, you don't even need to use tags, just use your own metadata field 02:47:53 <randomuser> yeah, I assumed it would need template work :) 02:48:15 <ralsina_> You create your own field, then write a plugin that creates a JSON with the whole site organized by all your hierarchies 02:48:20 <ralsina_> that's your "menu" 02:48:25 * randomuser nods 02:48:25 <ralsina_> the rest is trivial 02:48:42 <ralsina_> The plugin to do that is probably 15 lines of code, BTW 02:49:08 <randomuser> well, I'll come back when I get stuck on line six :P 02:51:16 <ralsina_> np 02:51:28 <randomuser> I'll wrap up converting this one repo of docs over to rest, then try my hand at writing the plugin 02:51:53 <ralsina_> randomuser: basically, the plugin has to check self.site.timeline 02:51:58 <ralsina_> (that's all the posts and pages) 02:52:09 <ralsina_> for each get your metadata (post.meta('whatever') 02:52:17 <ralsina_> split in the separator, and you have your path 02:52:23 <randomuser> niice 02:52:31 <ralsina_> then put it in the right place in a nice data structure 02:52:47 <ralsina_> then json.dump(nicedatastructure) 02:52:51 <ralsina_> to some file 02:53:03 <ralsina_> then you write JS to read that and show a tree and that's much harder ;-) 02:53:21 <ralsina_> but surely there's a jquery tree thing somewhere 02:53:40 <ralsina_> ah, the link to the post (so you can actually, you know, link to it) is post.permalink 02:53:43 <randomuser> yeah, I can think of a few places to borrow from 02:54:06 <ralsina_> And then you put your lovely plugin in https://plugins.getnikola.com ;-) 02:54:51 <randomuser> and hey, you get a high traffic site using nikola to brag about ;) 03:14:15 <ralsina_> win/win ;-) 03:46:44 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to static-navbars: http://git.io/vJHCK 03:46:44 -GitHub[nikola]:#nikola- nikola/static-navbars 24e5def Roberto Alsina: Update CHANGES.txt 03:47:08 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to master: http://git.io/vJHC1 03:47:08 -GitHub[nikola]:#nikola- nikola/master a60b513 Roberto Alsina: Merge pull request #1691 from getnikola/static-navbars... 03:54:07 -travis-ci:#nikola- getnikola/nikola#4914 (static-navbars - 24e5def : Roberto Alsina): The build is still failing. 03:54:08 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/f7ffdc0bc330...24e5def7533d 03:54:08 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61408753 04:03:03 -travis-ci:#nikola- getnikola/nikola#4916 (master - a60b513 : Roberto Alsina): The build was broken. 04:03:04 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/a403a2161991...a60b5139d312 04:03:04 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61408774 08:39:43 -travis-ci:#nikola- Invariant build by Chris Warrick: The build passed. See http://travis-ci.org/getnikola/invariant-builds/builds/61431445. 08:45:04 -GitHub[nikola]:#nikola- [nikola] Kwpolska deleted static-navbars at 24e5def: http://git.io/vJQqU 10:26:10 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to check-404: http://git.io/vJQ6F 10:26:10 -GitHub[nikola]:#nikola- nikola/check-404 f46d50f Roberto Alsina: grammar fix 10:27:23 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to check-404: http://git.io/vJQiO 10:27:23 -GitHub[nikola]:#nikola- nikola/check-404 65a3d01 Roberto Alsina: merged master 10:27:40 -GitHub[nikola]:#nikola- [nikola] ralsina closed pull request #1693: Check 404 (Issue #1684) (master...check-404) http://git.io/vJHJr 10:32:37 -travis-ci:#nikola- getnikola/nikola#4918 (check-404 - 65a3d01 : Roberto Alsina): The build has errored. 10:32:38 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/f46d50fe5779...65a3d010cac5 10:32:38 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61444695 10:33:08 -travis-ci:#nikola- getnikola/nikola#4917 (check-404 - f46d50f : Roberto Alsina): The build has errored. 10:33:09 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/0ecdc00ad8ac...f46d50fe5779 10:33:09 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61444543 10:41:31 -travis-ci:#nikola- getnikola/nikola#4920 (master - fd69359 : Roberto Alsina): The build was broken. 10:41:32 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/a60b5139d312...fd693597f2e8 10:41:32 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61444746 11:04:48 -GitHub[nikola]:#nikola- [nikola] Kwpolska pushed 1 new commit to master: http://git.io/vJQQ5 11:04:48 -GitHub[nikola]:#nikola- nikola/master 47cc127 Chris Warrick: fix req_missing usage/flake8 11:12:54 -travis-ci:#nikola- getnikola/nikola#4921 (master - 47cc127 : Chris Warrick): The build is still failing. 11:12:55 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/fd693597f2e8...47cc127fd0fa 11:12:55 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61448720 11:27:57 -travis-ci:#nikola- Invariant build by Chris Warrick: The build has errored. See http://travis-ci.org/getnikola/invariant-builds/builds/61431445. 11:30:46 -travis-ci:#nikola- Invariant build by Chris Warrick: The build has errored. See http://travis-ci.org/getnikola/invariant-builds/builds/61431445. 11:34:16 -travis-ci:#nikola- Invariant build by Chris Warrick: The build has errored. See http://travis-ci.org/getnikola/invariant-builds/builds/61431445. 11:34:23 <ChrisWarrick> github is having issues, awesome 12:00:50 -travis-ci:#nikola- Invariant build by Chris Warrick: The build passed. See http://travis-ci.org/getnikola/invariant-builds/builds/61431445. 12:50:24 <Aeyoun> ChrisWarrick: http://bildr.no/view/cXE3bHNJ :( 12:50:57 <ChrisWarrick> Aeyoun: tieri 12:51:09 <ChrisWarrick> Aeyoun: cloudflare thinks you (or your ISP) is misbehaving 12:51:55 <Aeyoun> CloudFlare seems to have a lot of opinions about a lot of things. 12:52:08 * Aeyoun hate captchas 12:52:47 <Aeyoun> ChrisWarrick: do they give you data on how many users fill it in and how many abandon the site? Those numbers are probably not good. 12:53:51 <ChrisWarrick> Aeyoun: I have data on how many people received it, but I can’t see conversion 12:55:38 <ralsina_> It's very rare that cloudflare actually does that 12:55:51 <Aeyoun> Giving away control over your site like this seems scary to me. Would never do it. 12:55:58 <Aeyoun> ralsina_: how do you know? 12:56:11 <Aeyoun> 1 in 100 is still a lot of people. 12:56:18 <ralsina_> Because I used to check how many of those were shown compared to number of visitors 12:56:24 <ralsina_> it was more like 1 in 1000 12:56:36 <ralsina_> it could be that it's more today because we are getting more hits 12:56:50 <Aeyoun> As we used to say at Opera, 1.2% of everyone is still a freaking huge number. :-P 12:57:18 <Aeyoun> Didn't have a problem accessing the site yesterday. 12:57:21 <ralsina_> it can be mitigated by toning down our security setting 12:57:37 <ralsina_> Since we are supposed to be secure anyway 13:01:12 <Aeyoun> There isn’t really any sensitive data or anything worth attacking the site over either, is there? 13:01:37 <Aeyoun> Oh, https://users.getnikola.com/ has no CSS. 13:01:59 <Aeyoun> mixed-content, trying to load it over HTTP 13:02:27 <Aeyoun> That is the only subsite with a form to submit data, right? So higher settings there; and low on the main site (where access is the more important factor). 13:03:06 * ChrisWarrick does not give the nikola-users site enough love 13:03:48 <ChrisWarrick> also, same goes with themes., and plugins. is dead 13:05:27 -GitHub[sites]:#nikola- [nikola-users] Kwpolska pushed 1 new commit to master: http://git.io/vJ7Ew 13:05:27 -GitHub[sites]:#nikola- nikola-users/master bde3443 Chris Warrick: https... 13:09:05 -GitHub[themes]:#nikola- [nikola-themes] Kwpolska pushed 1 new commit to master: http://git.io/vJ7z0 13:09:05 -GitHub[themes]:#nikola- nikola-themes/master bd95645 Chris Warrick: https... 13:09:53 -GitHub[sites]:#nikola- [nikola-users] Kwpolska pushed 1 new commit to master: http://git.io/vJ7zH 13:09:53 -GitHub[sites]:#nikola- nikola-users/master f3358fa Chris Warrick: even more https... 13:10:47 <ChrisWarrick> plugins were dead because cloudflare does not protect wildcards 13:12:13 -GitHub[plugins]:#nikola- [plugins] Kwpolska pushed 1 new commit to master: http://git.io/vJ7gy 13:12:13 -GitHub[plugins]:#nikola- plugins/master accf184 Chris Warrick: https... 13:13:05 <ChrisWarrick> all fixed now 13:18:05 <travis-ci> [PLUGINS] getnikola/plugins#604 (master - accf184 : Chris Warrick): The build passed. 13:18:05 <travis-ci> [PLUGINS] Change view: https://github.com/getnikola/plugins/compare/d4bc696d9720...accf1844aae1 13:18:05 <travis-ci> [PLUGINS] Build details: http://travis-ci.org/getnikola/plugins/builds/61461570 16:21:31 <gour> how much is theming tutorial outdated? 16:23:16 <ChrisWarrick> gour: I personally recommend looking at existing themes and copying things from them 16:24:17 <ChrisWarrick> gour: and the theming tutorial is from Nikola v6 days and will result in a failure 16:25:25 <gour> ChrisWarrick: ok, thanks 16:27:22 <gour> what about theming-reference? is it up-to-date as stated? 16:30:07 <ChrisWarrick> gour: it does not mention everything, but looks good enough 16:30:37 <gour> good 16:40:17 <ralsina_> ChrisWarrick: opinion in a 7.4.1 tomorrow? 16:40:58 <ChrisWarrick> ralsina_: a bit too fast, don’t you think? 16:41:35 <ChrisWarrick> ralsina_: I’d say Sunday; I still have to work on this old-style meta plugin and I didn’t have time today. I would like an advert in v7.4.1 if old-style meta is detected 16:41:46 <ralsina_> ChrisWarrick: considering that 7.4.0 will fail to build our oldest customers' sites... 16:42:08 <ralsina_> mostly concerned about annoying faithful users :-) 18:40:11 <Aeyoun> ralsina_: so you’re saying there should be conf.py-upgrade tests? 18:40:24 <ralsina_> ? 18:42:21 <Aeyoun> ralsina_: if you don’t want to annoy users with older conf.py files, there should be some tests with older sites. 18:42:36 <ralsina_> Aeyoun: this is not about config files, it's about actual post data 18:42:44 <ralsina_> Aeyoun: we broke valid metadata files 18:42:55 <Aeyoun> ralsina_: ah, well. tests for that too then 18:43:23 <ralsina_> Sure, tests would be nice 18:43:28 <ralsina_> we can just add one of these to the demo site