Plone Conf 2014 - Day 1: Lightning Talks: Part 1
CC Attribution - NonCommercial 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
McMahon, Steve
Tax, Paul
Roeland, Paul
Soukka, Asko
Kleinfeldt, Sally
Terada, Manabu
- Steve McMahon (Plone installation, the future) What is the Installer team doing for Plone 5. You can still use your custom buildout, no problem, so your future may still vary. Unified Installer will still work. Platform binary installers may not work; possibly Windows; nearly certainly not OS X, as it gets harder and harder to do open source development there. The hot newness is Cloud or VM kits. We are working on making that happen for Plone too. Our principal tool is going to be Ansible. Build a full-stack server. Vagrant instance to test it before you deploy it. We are not scaring people away from other approaches. Targets: from 5 to 5000 dollars per month, with configuration. Working on boxes for Digital Ocean, AWS, etc. Plone 5: no longer ZopeSkel or templar, but mr.bob as tool for bootstrapping a new project. You are free to use the tool you like. - Paul Tax (Anniversary sprint) I am the new guy at Four Digits, Arnhem, The Netherlands. We are organizing a sprint on 22 till 26 June 2015. Hotels near, good wifi, standing desks if you want, agile planning, standups, food and drinks. Party on Friday, because it is our ten year anniversary. No problem if you only want to join for the party. Homebrewn beer. - Paul Roeland (Paragon) Paragon is the search for the very best in Plone add-ons. The hunt is on, especially for add-ons making the lives of integrators easier. No undead add-ons please, no unmaintained. Just good, useful add-ons. You can nominate until November 14. Are they maintained? Are they safe to put on a production site? - Asko Soukka (venusianconfiguration) Venusian configuration: no more zcml. Put that configuration in a Python file. It can scan modules, a bit like grok, but explicitly. It will not be released, because I don't want all the hate mail. :-) But maybe incorporate it in Zope configuration. - Sally, Cris, Jens, Alexander, Andreas (bibliographies) Bibliographies are really important to a certain segment of users, academics specifically. There is funding to make some things better. This is a call for help. I scheduled an open space for this topic on Friday, please come and give your input. Create a plan of action. - Manabu Terada (Recent topics about Plone in Japan) PyCon Japan September 2014, 500 people, one English track. I conducted a session about Plone, about 100 people attended. Number of Python developers is increasing in Japan. We wish to spread Plone usage in Japan. Next year: Plone Symposium Tokyo! May/July 2015. Get interesting sessions, so speakers from overseas are very much invited. Airport, big city: English is no problem, outside may be difficult. Tokyo is very cheap. Safe? Yes, we even hold the Olympics in 2020. See you in Tokyo next year.
 Hello. How's everybody been doing the first day? Good? Yay! This is great. We've been having some great talks and it's been great seeing everybody here and everything seems to be running really smoothly. If anybody does have any comments or questions or feedback or needs anything, then as usual just try and find somebody with a red badge. It's easy to find us or come find us at the reception desk. Anyway, to finish off today we have lightning talks today. We can do that and then head on out into the wilds of Bristol for dinner. We don't have anywhere particular set for dinner because it's quite difficult to get everybody in one place. So I guess find groups and go out and explore. There's plenty of places around for dinner and drinks. Anyway, on to the lightning talks. We've got five minutes each. Yes, let's get going. We have a timer? Oh, good question. A timer. Great. So Chris is a timer. He will yell, ding, wave, sing, something. If you're on that list, start moving to the front. Have your laptop ready? And we can try and get things going nice and quickly. So starting off, we have Steve McMahon. Hi, folks. I'm embarrassed to have the number one spot, but I'll use it. I'm going to talk about what the installer team is doing with Plone Installers 4.5. Now, every time we have a discussion about installers, some people get anxious that somehow we are going to force a given installation method upon them. No, I mean, if you want to use your custom buildouts, your custom buildouts will continue to work. This is just what we're trying to make easy. These are the paths we're trying to grease so that it'll be easy to do installs. So your future may vary from what I'm going to describe. Okay, what are we aiming for for Plone 5? First of all, the Unified Installer will still work. We will have one. In fact, it will be much improved and it will check for dependencies thanks to some of the work Sven's been doing. Platform Binary Installers may not work and you should not count on them for the future. We're going to try and keep the Windows Binary Installer work because people need them. But OSX, it gets harder to make it work every time so we may be more emphasizing using virtual environments inside OSX as Apple makes it harder and harder to do open source development. So we're thinking about vagrant and virtual box style replacements for those. Okay, we know, everybody knows that the hot newness in terms of installation is cloud and virtual machines. I mean, that's been coming for years. Now it's starting to get incredibly easy and cheap. And so we are working on installation methods that will make it very easy to get a Plone instance quickly installed and running on your choice of cloud machine. And let's see if I can get that slide to change. Our principle tool for doing that is going to be Ansible. We know that there are people that use puppet and chef and salt and everything else in the world. But after talking a lot of agreement, the largest group of people are willing to work on Ansible as a provisioning tool that we can include as part of the Plone kit that will allow you to quickly create a full stack server. And by a full stack server, I mean one that if you need ZO and multiple clients, it will have it. It will have a load balancer. It will have a cacher and it will have a rewrite engine like engine X or Apache at the front of it. And you'll be able to install it practically with a single command. And in the same directory that you're maintaining your Ansible install, you'll have a vagrant instance where you can test all those things on a test server before you deploy them. Again, you may do things differently. That's great. We are not going to take the ability away from people to use puppet or AWS kits, anything of the sort. This is just what we're going to make really easy to do. And we've already been doing some work on it. We're going to try and target everything from a $5 a month server to a $5,000 a month server just by allowing you to change some configuration options. So yes, I mean, we'll make it easy to do digital ocean for a $5 server for some lightweight blown sites. We'll also try and deliver some pre-made virtual boxes for the very popular kits that are out there. And SPEN has been working on some techniques where we can take one Ansible kit and then turn it into droplets for digital ocean, AWS kits, that sort of thing that can be deployed quickly. Okay, Zope scale, we're also working on skeleton generators. That's part of them making things easy. In the past, we've been using Zope scale. You may have tried Templar. Those are going to be going away. They're just not maintained very well. Chris Hewing who was working on Templar is rejoicing. We're going to be replacing those with Mr. Bob. You are welcome to use what you please. Okay, we are not taking anything away from everybody. This is just what we'll ship with the installers as hopefully community supported tools. Okay, the future is coming. Your experience may vary, but the future is closer than it appears. A lot of these things are going to be working at the end of the sprint. Please come and help us sprint on it. Thank you all very much. Thank you, Steve. So now we've got Paul up. Who's doing? Paul? Yes. Great. So Paul talking about anniversary sprint. Then after that, we've got Paula Polo-Yester and Asco. Are they around if they want to start coming up? Paul Polo-Yester right there. And Asco somewhere over there. Great. Okay, you guys are up. Hello. I'm Paul. I'm the new guy at Four Digits in Arnhem. They thought it was a nice idea to get me out of my comfort zone. As a jungle guy, put me in front of 150 Plonistas. The reason I'm here is that we are organizing a sprint in June from the 22nd to the 26th in Arnhem, the second most beautiful city in Holland, but really close to the most beautiful city in Holland. So this is Arnhem. You can reach it. Yeah, Amsterdam, Klaver, Eindhoven, public transportation is very good in Arnhem, so no problem getting there. Hotels and hostels, no problem in Arnhem as well. We have room for over 50 sprinters. I don't see any chairs. We have standing desks. We see a five channel connection available, so very fast internet. Topics will be announced shortly, not shortly, probably a month or so in advance. Agile planning and stand-ups, food and especially drinks will be taken care of, as some of the guys, if you know Four Digits, that will be taken care of. The whole sprint sort of is an excuse for the big party we are organizing on Friday, which is the 10-year anniversary of Four Digits. So if you only want to join for the party on Friday, no problem. Live music. I believe everybody is joining some sort of band, so... Omru beer. So yeah, please join us from the 22nd to the 26th. Don't leave on Friday, leave on Saturday, so you can join the party. APPLAUSE OK, next up we have Paul Rowland talking about Paragon. Do stuff. OK, I'm here to talk about a little site project that has had much delays, but will be reaching its conclusion soon. And that is Plone Paragon. What Plone Paragon is, for those of you who don't know, is a search for the best in add-ons. We are looking for add-ons that make the life of integrators especially and directly integrators easier. There are about 3,000 add-ons at the moment registered on PIPI, which is not a usable statistic for any normal human. And there are the quality of those, whereas also some of them are completely unmaintained, some of them are guaranteed to blow up your site, and some of them are sort of like the undead, they will keep reappearing no matter what you try to do to get rid of them. That is not the best experience. We want new integrators and also older integrators to have. So we want to point out what are good, useful add-ons. And to have those, well, we have a nomination process. Anybody can nominate. The nominations were already finished, but we ran a little late. So the nominations will be extended until November the 14th. That's two weeks after the conference. You can still nominate add-ons. Those add-ons should best of all, for full certain criteria, and there are some basic ones like are they still maintained. We are specifically looking for a list of add-ons that are safe to put on production sites. There will be a separate page in the documentation for developer add-ons. So don't nominate, plon.reload, because you don't want that on your production site. The nomination, it's quite easy to nominate. You go to paragonplon.org and you click the big green friendly button at the top, at the bottom. And you have to say which add-on, your name, what it does, if you have screenshots, send them. If you can fill in categories, that will be lovely. There are a lot of fields here. People have complained, but there are only a few that are required. If you nominate an add-on, please save us the trouble of finding out the PIEPIE URL and the GitHub URL. So you need to fill in those. If you know some of the user experience, things like does it have documentation, is it possible to translate it, all the better, fill it in. If you have no clue about that, still nominate, the jury will find it out. And the following of the jury, we finally have a most esteemed jury. The jury is Steve McMayen, Sally Kleinfeldt, Kim Niem, and Philip Bauer. And I will be cheerly digging them on as well. I think all of you know those four persons. We have together an impressive length of experience in Plone. And the results will then be announced in December. And why is this important? Well, it's important for the add-ons that get nominated. It's also because we will feature those on the new Plone.org, which will appear relatively soon and which will not have a product section anymore. And we will have links to PIEPIE, but we will feature this list of sort of not recommended add-ons, but sort of recommended add-ons. There will be add-ons that solve actual problems and will not blow up your site. We are aiming to increase the quality of add-ons and to have as pleasant an experience for integrators as possible. And that's the goal. So start nominating, help us in getting your favorite product or add-on nominated. And this is a process that will most likely be repeated over the coming time because new add-ons do appear. So, and if an add-on is not chosen, it doesn't mean it's really bad. Don't worry about it. We do have to give new people the best entrance into getting our site up to speed as possible. Thank you. APPLAUSE Great. Thanks Paul. Now we have Asko Suken and followed by Sally Chris, Andreas and Alex. Wow, that's going to be a veritable smorgasbord of lightning talks going on there. And then Manabu Tirada after that if you guys can get ready. Okay, great. Something completely different. My name is Asko. I come from Iwasgola, Finland. And I present something that many of you don't want, but I want to use it. So we remember Crock configuration that was replacement for HTML configuration in Python. But probably it's broken. It doesn't work. You cannot replace HTML with it and it doesn't cover all the directives. But I did want to use Python configuration to work better with IDE. So when I replace something, some class with name, class with some other name, then I can use refactoring of IDE to replace also all the configuration. So about a year ago, almost, I figured out the way to map Python syntax into, directly into job configuration directives. So no more HTML, also only Python files. The main file is by default, config.by. And it can, well, can contain any mapping to any job configuration directive. It would look quite similar to what you have in HTML. Yeah, it can also, yeah, like, like, it creates a page, features. And most of those directives also work as decorators. This is for utility. For multi-adaptors. And you can even use it for creating more directives. And yeah, those directives are used by scanning. So this is Venom Venusian package as backend. But because I didn't like how by default, Crop can scan it all subdirectors also. Also, that was a little bit difficult with job configuration. So it also only travels for one, scans for one package per time. And when you have subpackages, you have to include those with the include directive last you do with ctml. And for complex directives that are like, like, inside HTML tags in ctml, I use Python context managers. So you can have content managers to use, make those complex directives. And the best part of this is that I will not be releasing this in public because I don't want all the hate mail for introducing yet another way to conjugate the line. But if you are interested in this, then we should find a way to, well, think about if the syntax is correct to tweak it somehow. And is there a way how we could make this into a job configuration? So job configuration, as all the job packages, is so O-engineered that it very little depends on ctml. Most of the stuff is independent from ctml. And so this is like only one more syntax to use job configuration. So I think the correct base for this would be in job configuration. That's under a job foundation. And I don't have agreement for the contribution to job foundation code. So I have no idea how to make it into corporate. If you are interested, maybe we can figure out something. Thank you. Right. Thank you, Asko. Oh, yeah, you got a multitask now, Chris. Time out. So if this goes on for half an hour, we know who to blame. I'll let somebody else shout out if it gets down. We should have just turned the camera around. We should have just, you know, everybody's down there. So this is actually my first lightning talk, so I have to have safety in numbers here. Whoa! So, yes, this talk is about bibliographies, like the most boring possible topic that anybody can think of. It is also a set of tools that's pretty ugly in clone. If any of you have worked in academic sites, you'll know that the CMS Bibliography AT package is not the most modern or straightforward package. However, bibliographies are really important to a certain segment of users, academics specifically, and higher education research. And that is a pretty important clone constituency, really. It's one of the things that we do a lot of work on at Jess Carter. It's just important. And in addition to that, there's actually some funding out there in some of the institutions we work with that Alex works with to make some things better. This is a call to, for help. I scheduled an open space on this topic on Friday. If anyone has, like, any experience in this, any thoughts on this, we'd really love to have your input. We're going to talk about just, I mean, we're not going to rewrite, rewrite, seem a bibliography in one open space. We're going to talk about a plan, a plan of action kind of technically, how are we going to approach this? What kind of funding do we ultimately need? Who is there available to help? So this is just a call for please. If you can't make the open space, I know there's lots of conflicts. Then just let me know what your thoughts are, because we'd really like to make this tool suite better. There's some pretty awesome bibliography tools now out there, kind of more end user focus that we can integrate that I think would make this a really strong point of clone again. So, woo-hoo, bibliographies. Yeah. APPLAUSE OK, next up we have Manabu, Tirada. And then following that, we've got Maurizio and then Vincenzo. He's Japanese. OK. Hi, I'm Manabu Tirada from Tokyo, Japan. So I will talk about recent topic about pro in Japan. I'm both German of PyConJP. So we had on September this year in Tokyo, over 500 people joined us, and we had one English track. So this photo was taken before session of closing. So I had a talk session of the plon in the conference. So plon basics and history, about plon 5, and plon community, about 100 people attended. However, Japanese plon market is very small. So number of plon developers increase in Japan, Django and Pyramid are well known in Japan. So some university and institute using plon in Japan. So we wish to spread plon users in Japan. So we will host plon symposium in Tokyo next year. APPLAUSE Thank you. So we hope to increase the province of plon in Japan and let more people know about plon. So main target, so web engineer and plon users and other CMS users. So this event description, May 2 July next year. So one day to tracks talking and one day sprint in Tokyo. So we want to have interesting session for engineers and exposed to tech media and promote in engineer communities. So I want to come speakers from overseas. So everybody please, so I will have a planning session in the open space. So please join. So one more thing. Tokyo, do you know Tokyo? Okay. Is English okay in Tokyo? So at the airport and hotel and major cities, English is no problem. So however small cities and local market, English may be difficult. And Tokyo is not expensive. Very cheap. Very cheap. Very cheap. Okay. So and safety. So because before Olympic was in London, you know, so next Olympic the Rio. So next Olympic in Tokyo. So see you next year in Tokyo. Thank you very much.
 Hello.  How's everybody been doing the first day?  Good?  Yay!  This is great. We've been having some great talks and it's been great seeing everybody here and everything seems to be running really smoothly.  If anybody does have any comments or questions or feedback or needs anything, then as usual just try and find somebody with a red badge.  It's easy to find us or come find us at the reception desk.  Anyway, to finish off today we have lightning talks today. We can do that and then head on out into the wilds of Bristol for dinner.  We don't have anywhere particular set for dinner because it's quite difficult to get everybody in one place.  So I guess find groups and go out and explore. There's plenty of places around for dinner and drinks.  Anyway, on to the lightning talks. We've got five minutes each.  Yes, let's get going.  We have a timer?  Oh, good question. A timer.  Great. So Chris is a timer. He will yell, ding, wave, sing, something.  If you're on that list, start moving to the front. Have your laptop ready?  And we can try and get things going nice and quickly. So starting off, we have Steve McMahon.  Hi, folks. I'm embarrassed to have the number one spot, but I'll use it.  I'm going to talk about what the installer team is doing with Plone Installers 4.5.  Now, every time we have a discussion about installers, some people get anxious that somehow we are going to force a given installation method upon them.  No, I mean, if you want to use your custom buildouts, your custom buildouts will continue to work.  This is just what we're trying to make easy. These are the paths we're trying to grease so that it'll be easy to do installs.  So your future may vary from what I'm going to describe.  Okay, what are we aiming for for Plone 5?  First of all, the Unified Installer will still work. We will have one.  In fact, it will be much improved and it will check for dependencies thanks to some of the work Sven's been doing.  Platform Binary Installers may not work and you should not count on them for the future.  We're going to try and keep the Windows Binary Installer work because people need them.  But OSX, it gets harder to make it work every time so we may be more emphasizing using virtual environments inside OSX as Apple makes it harder and harder to do open source development.  So we're thinking about vagrant and virtual box style replacements for those.  Okay, we know, everybody knows that the hot newness in terms of installation is cloud and virtual machines.  I mean, that's been coming for years. Now it's starting to get incredibly easy and cheap.  And so we are working on installation methods that will make it very easy to get a Plone instance quickly installed and running on your choice of cloud machine.  And let's see if I can get that slide to change.  Our principle tool for doing that is going to be Ansible.  We know that there are people that use puppet and chef and salt and everything else in the world.  But after talking a lot of agreement, the largest group of people are willing to work on Ansible as a provisioning tool that we can include as part of the Plone kit that will allow you to quickly create a full stack server.  And by a full stack server, I mean one that if you need ZO and multiple clients, it will have it.  It will have a load balancer. It will have a cacher and it will have a rewrite engine like engine X or Apache at the front of it.  And you'll be able to install it practically with a single command.  And in the same directory that you're maintaining your Ansible install, you'll have a vagrant instance where you can test all those things on a test server before you deploy them.  Again, you may do things differently.  That's great. We are not going to take the ability away from people to use puppet or AWS kits, anything of the sort.  This is just what we're going to make really easy to do. And we've already been doing some work on it.  We're going to try and target everything from a $5 a month server to a $5,000 a month server just by allowing you to change some configuration options.  So yes, I mean, we'll make it easy to do digital ocean for a $5 server for some lightweight blown sites.  We'll also try and deliver some pre-made virtual boxes for the very popular kits that are out there.  And SPEN has been working on some techniques where we can take one Ansible kit and then turn it into droplets for digital ocean, AWS kits, that sort of thing that can be deployed quickly.  Okay, Zope scale, we're also working on skeleton generators. That's part of them making things easy.  In the past, we've been using Zope scale. You may have tried Templar. Those are going to be going away.  They're just not maintained very well. Chris Hewing who was working on Templar is rejoicing.  We're going to be replacing those with Mr. Bob. You are welcome to use what you please.  Okay, we are not taking anything away from everybody. This is just what we'll ship with the installers as hopefully community supported tools.  Okay, the future is coming. Your experience may vary, but the future is closer than it appears.  A lot of these things are going to be working at the end of the sprint. Please come and help us sprint on it. Thank you all very much.  Thank you, Steve. So now we've got Paul up. Who's doing? Paul? Yes.  Great. So Paul talking about anniversary sprint.  Then after that, we've got Paula Polo-Yester and Asco. Are they around if they want to start coming up?  Paul Polo-Yester right there. And Asco somewhere over there. Great. Okay, you guys are up.  Hello. I'm Paul. I'm the new guy at Four Digits in Arnhem. They thought it was a nice idea to get me out of my comfort zone.  As a jungle guy, put me in front of 150 Plonistas. The reason I'm here is that we are organizing a sprint in June from the 22nd to the 26th in Arnhem,  the second most beautiful city in Holland, but really close to the most beautiful city in Holland.  So this is Arnhem. You can reach it. Yeah, Amsterdam, Klaver, Eindhoven, public transportation is very good in Arnhem,  so no problem getting there. Hotels and hostels, no problem in Arnhem as well.  We have room for over 50 sprinters.  I don't see any chairs.  We have standing desks. We see a five channel connection available, so very fast internet.  Topics will be announced shortly, not shortly, probably a month or so in advance. Agile planning and stand-ups,  food and especially drinks will be taken care of, as some of the guys, if you know Four Digits, that will be taken care of.  The whole sprint sort of is an excuse for the big party we are organizing on Friday, which is the 10-year anniversary of Four Digits.  So if you only want to join for the party on Friday, no problem.  Live music. I believe everybody is joining some sort of band, so...  Omru beer.  So yeah, please join us from the 22nd to the 26th. Don't leave on Friday, leave on Saturday, so you can join the party.  APPLAUSE  OK, next up we have Paul Rowland talking about Paragon.  Do stuff. OK, I'm here to talk about a little site project that has had much delays, but will be reaching its conclusion soon.  And that is Plone Paragon. What Plone Paragon is, for those of you who don't know, is a search for the best in add-ons.  We are looking for add-ons that make the life of integrators especially and directly integrators easier.  There are about 3,000 add-ons at the moment registered on PIPI, which is not a usable statistic for any normal human.  And there are the quality of those, whereas also some of them are completely unmaintained, some of them are guaranteed to blow up your site,  and some of them are sort of like the undead, they will keep reappearing no matter what you try to do to get rid of them.  That is not the best experience. We want new integrators and also older integrators to have.  So we want to point out what are good, useful add-ons.  And to have those, well, we have a nomination process. Anybody can nominate. The nominations were already finished, but we ran a little late.  So the nominations will be extended until November the 14th. That's two weeks after the conference.  You can still nominate add-ons. Those add-ons should best of all, for full certain criteria,  and there are some basic ones like are they still maintained.  We are specifically looking for a list of add-ons that are safe to put on production sites.  There will be a separate page in the documentation for developer add-ons.  So don't nominate, plon.reload, because you don't want that on your production site.  The nomination, it's quite easy to nominate. You go to paragonplon.org and you click the big green friendly button at the top, at the bottom.  And you have to say which add-on, your name, what it does, if you have screenshots, send them.  If you can fill in categories, that will be lovely. There are a lot of fields here.  People have complained, but there are only a few that are required. If you nominate an add-on, please save us the trouble of finding out the PIEPIE URL and the GitHub URL.  So you need to fill in those. If you know some of the user experience, things like does it have documentation, is it possible to translate it, all the better, fill it in.  If you have no clue about that, still nominate, the jury will find it out.  And the following of the jury, we finally have a most esteemed jury. The jury is Steve McMayen, Sally Kleinfeldt, Kim Niem, and Philip Bauer.  And I will be cheerly digging them on as well. I think all of you know those four persons.  We have together an impressive length of experience in Plone. And the results will then be announced in December.  And why is this important? Well, it's important for the add-ons that get nominated.  It's also because we will feature those on the new Plone.org, which will appear relatively soon and which will not have a product section anymore.  And we will have links to PIEPIE, but we will feature this list of sort of not recommended add-ons, but sort of recommended add-ons.  There will be add-ons that solve actual problems and will not blow up your site.  We are aiming to increase the quality of add-ons and to have as pleasant an experience for integrators as possible.  And that's the goal. So start nominating, help us in getting your favorite product or add-on nominated.  And this is a process that will most likely be repeated over the coming time because new add-ons do appear.  So, and if an add-on is not chosen, it doesn't mean it's really bad. Don't worry about it.  We do have to give new people the best entrance into getting our site up to speed as possible. Thank you.  APPLAUSE  Great. Thanks Paul. Now we have Asko Suken and followed by Sally Chris, Andreas and Alex.  Wow, that's going to be a veritable smorgasbord of lightning talks going on there.  And then Manabu Tirada after that if you guys can get ready.  Okay, great. Something completely different. My name is Asko. I come from Iwasgola, Finland.  And I present something that many of you don't want, but I want to use it.  So we remember Crock configuration that was replacement for HTML configuration in Python.  But probably it's broken. It doesn't work. You cannot replace HTML with it and it doesn't cover all the directives.  But I did want to use Python configuration to work better with IDE.  So when I replace something, some class with name, class with some other name,  then I can use refactoring of IDE to replace also all the configuration.  So about a year ago, almost, I figured out the way to map Python syntax into,  directly into job configuration directives.  So no more HTML, also only Python files. The main file is by default, config.by.  And it can, well, can contain any mapping to any job configuration directive.  It would look quite similar to what you have in HTML.  Yeah, it can also, yeah, like, like, it creates a page, features.  And most of those directives also work as decorators.  This is for utility. For multi-adaptors.  And you can even use it for creating more directives.  And yeah, those directives are used by scanning.  So this is Venom Venusian package as backend.  But because I didn't like how by default, Crop can scan it all subdirectors also.  Also, that was a little bit difficult with job configuration.  So it also only travels for one, scans for one package per time.  And when you have subpackages, you have to include those with the include directive last you do with ctml.  And for complex directives that are like, like, inside HTML tags in ctml,  I use Python context managers.  So you can have content managers to use, make those complex directives.  And the best part of this is that I will not be releasing this in public  because I don't want all the hate mail for introducing yet another way to conjugate the line.  But if you are interested in this, then we should find a way to,  well, think about if the syntax is correct to tweak it somehow.  And is there a way how we could make this into a job configuration?  So job configuration, as all the job packages, is so O-engineered that it very little depends on ctml.  Most of the stuff is independent from ctml. And so this is like only one more syntax to use job configuration.  So I think the correct base for this would be in job configuration.  That's under a job foundation.  And I don't have agreement for the contribution to job foundation code.  So I have no idea how to make it into corporate.  If you are interested, maybe we can figure out something.  Thank you.  Right. Thank you, Asko.  Oh, yeah, you got a multitask now, Chris.  Time out.  So if this goes on for half an hour, we know who to blame.  I'll let somebody else shout out if it gets down.  We should have just turned the camera around.  We should have just, you know, everybody's down there.  So this is actually my first lightning talk, so I have to have safety in numbers here.  Whoa!  So, yes, this talk is about bibliographies, like the most boring possible topic that anybody can think of.  It is also a set of tools that's pretty ugly in clone.  If any of you have worked in academic sites, you'll know that the CMS Bibliography AT package is not the most modern or straightforward package.  However, bibliographies are really important to a certain segment of users, academics specifically, and higher education research.  And that is a pretty important clone constituency, really.  It's one of the things that we do a lot of work on at Jess Carter.  It's just important.  And in addition to that, there's actually some funding out there in some of the institutions we work with that Alex works with to make some things better.  This is a call to, for help.  I scheduled an open space on this topic on Friday.  If anyone has, like, any experience in this, any thoughts on this, we'd really love to have your input.  We're going to talk about just, I mean, we're not going to rewrite, rewrite, seem a bibliography in one open space.  We're going to talk about a plan, a plan of action kind of technically, how are we going to approach this?  What kind of funding do we ultimately need?  Who is there available to help?  So this is just a call for please.  If you can't make the open space, I know there's lots of conflicts.  Then just let me know what your thoughts are, because we'd really like to make this tool suite better.  There's some pretty awesome bibliography tools now out there, kind of more end user focus that we can integrate that I think would make this a really strong point of clone again.  So, woo-hoo, bibliographies.  Yeah.  APPLAUSE  OK, next up we have Manabu, Tirada.  And then following that, we've got Maurizio and then Vincenzo.  He's Japanese.  OK.  Hi, I'm Manabu Tirada from Tokyo, Japan.  So I will talk about recent topic about pro in Japan.  I'm both German of PyConJP.  So we had on September this year in Tokyo, over 500 people joined us, and we had one English track.  So this photo was taken before session of closing.  So I had a talk session of the plon in the conference.  So plon basics and history, about plon 5, and plon community, about 100 people attended.  However, Japanese plon market is very small.  So number of plon developers increase in Japan, Django and Pyramid are well known in Japan.  So some university and institute using plon in Japan.  So we wish to spread plon users in Japan.  So we will host plon symposium in Tokyo next year.  APPLAUSE  Thank you.  So we hope to increase the province of plon in Japan and let more people know about plon.  So main target, so web engineer and plon users and other CMS users.  So this event description, May 2 July next year.  So one day to tracks talking and one day sprint in Tokyo.  So we want to have interesting session for engineers and exposed to tech media and promote in engineer communities.  So I want to come speakers from overseas.  So everybody please, so I will have a planning session in the open space.  So please join.  So one more thing.  Tokyo, do you know Tokyo?  Okay.  Is English okay in Tokyo?  So at the airport and hotel and major cities, English is no problem.  So however small cities and local market, English may be difficult.  And Tokyo is not expensive.  Very cheap.  Very cheap.  Very cheap.  Okay.  So and safety.  So because before Olympic was in London, you know, so next Olympic the Rio.  So next Olympic in Tokyo.  So see you next year in Tokyo.  Thank you very much.
Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_0_1403.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_1404_1907.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_1908_2063.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_2064_2759.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_2760_2939.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_2940_3467.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_3468_4127.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_4128_4187.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_4188_10823.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_10824_10943.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_10944_11075.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_11076_13151.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_13152_15515.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_15516_15563.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_15564_15995.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_15996_23015.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_23016_23063.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_23064_23459.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_23460_28643.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_28644_28943.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_28944_29147.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_29148_32807.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_32808_33023.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_33024_33251.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_33252_35519.png Plone_Conference_2014_-_Lightning_talks_1_HD_WEB_35520_38858.png