Podcasts about DocBook

Wyniki ankiety JetBrains, "The State of Developer Ecosystem 2023", jakie są, każdy widzi. Mało kto używa dity, wszyscy kodują. Ale skąd takie właśnie wyniki i jaką grupę one odzwierciedlają? Czy Tech Writerzy używają narzędzi enterprise? Czy testują dokumentację? Czy wyłania się nam persona Tech Writera, który koduje? Patrzymy na wyniki ankiety krytycznym okiem, badamy czy mogą one sugerować trendy przyszłości i staramy się ocenić kontekst. Jako bonus bierzemy na warsztat Writerside - narzędzie JetBrains do tworzenia dokumentacji. Omawiamy jego funkcjonalności i fundamentalną zasadę działania. Czy jest to remake MadCap Flare'a? Posłuchaj naszej rozmowy, a dowiesz się co o nim sądzimy. Dźwięki wykorzystane w audycji pochodzą z kolekcji "107 Free Retro Game Sounds" dostępnej na stronie https://dominik-braun.net, udostępnianej na podstawie licencji Creative Commons license CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Informacje dodatkowe: "The State of Developer Ecosystem 2023", JetBrains: https://www.jetbrains.com/lp/devecosystem-2023/ Writerside: https://www.jetbrains.com/writerside/ "Docs as code", Write the Docs: ⁠https://www.writethedocs.org/guide/docs-as-code/ Chris Chinchilla: https://chrischinchilla.com/ MadCap Flare: https://www.madcapsoftware.com/products/flare/ Adobe RoboHelp: https://www.adobe.com/pl/products/robohelp.html ClickHelp: https://clickhelp.com/ Adobe FrameMaker: https://www.adobe.com/pl/products/framemaker.html Help+Manual: https://helpandmanual.com/ WordPress: https://pl.wordpress.org/ Drupal: https://www.drupal.org/ "Markdown", Wikipedia: https://en.wikipedia.org/wiki/Markdown Schematron: https://www.schematron.com/ Swagger UI: https://swagger.io/tools/swagger-ui/ Redoc: https://github.com/Redocly/redoc "Zintegrowane środowisko programistyczne (IDE)", Wikipedia: https://pl.wikipedia.org/wiki/Zintegrowane_%C5%9Brodowisko_programistyczne IntelliJ IDEA: https://www.jetbrains.com/idea/ Wtyczka Writerside: https://plugins.jetbrains.com/plugin/20158-writerside "XML schema", Wikipedia: https://en.wikipedia.org/wiki/XML_schema "Darwin Information Typing Architecture (DITA)", Wikipedia: https://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture "DocBook", Wikipedia: https://en.wikipedia.org/wiki/DocBook Lightweight DITA: http://docs.oasis-open.org/dita/LwDITA/v1.0/cnprd01/LwDITA-v1.0-cnprd01.html "What is vendor lock-in?", TechTarget: https://www.techtarget.com/searchdatacenter/definition/vendor-lock-in

Why You Should Use BSD Licensing for Your Next Open Source Project or Product, Update on FreeBSD Foundation Investment in Linuxulator, OPNsense 21.1.5 released, FreeBSD meetings on the Desktop, Running FreeBSD jails with containerd 1.5, Markdown, DocBook, and the quest for semantic documentation on NetBSD.org, and more. NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) Headlines Why You Should Use BSD Licensing for Your Next Open Source Project or Product (https://klarasystems.com/articles/why-you-should-use-bsd-licensing-for-your-next-open-source-project-or-product/) The term “open source” has its origins in the context of software development, designating a specific approach to developing computer programs. Nowadays, however, it stands for a broad set of values – open source means open exchange, transparency, collaborative participation and development for the benefit of the entire community. Update on FreeBSD Foundation Investment in Linuxulator (https://freebsdfoundation.org/blog/update-on-freebsd-foundation-investment-in-linuxulator/) Dr. Emmett Brown’s similar-sounding Flux Capacitor from the movie Back to the Future bridged the dimension of time, uniting past, present, and future for the McFlys. Similarly, the FreeBSDⓇ Linuxulator project also bridges dimensions – in our case, these are LinuxⓇ and FreeBSD. News Roundup OPNsense 21.1.5 released (https://opnsense.org/opnsense-21-1-5-released/) This is mainly a security and reliablility update. There are several FreeBSD security advisories and updates for third party tools such as curl. + OPNsense to rebase on FreeBSD 13 (https://forum.opnsense.org/index.php?topic=22761.msg108313#msg108313) FreeBSD meetings on the Desktop (https://euroquis.nl//freebsd/2021/04/20/fbsd-bbb.html) FreeBSD on the desktop is a whole stack - X11, Qt, KDE Frameworks, KDE Plasma and KDE Gear, and Wayland, and Poppler and GTK - o my! Running FreeBSD jails with containerd 1.5 (https://samuel.karp.dev/blog/2021/05/running-freebsd-jails-with-containerd-1-5/) containerd 1.5.0 was released today and now works on a new operating system: FreeBSD! This new release includes a series of patches (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) which allow containerd to build, enable the native and zfs snapshotters, and use a compatible runtime like runj. Markdown, DocBook, and the quest for semantic documentation on NetBSD.org (https://washbear.neocities.org/markdown.html) Recently, I’ve been doing a lot of maintenance of the NetBSD website. It contains a boatload of documentation, much of which was originally written in the 2000s. It has some special requirements: it has to work in text-based web browsers like lynx, or maybe even without any working browser installed at all, or just ftp(1) for downloading plain text over HTTP. Naturally, the most important parts are static, suitable for serving from the standard NetBSD http server, which runs from inetd by default. Beastie Bits Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Alrekur - An Interesting FreeBSD Find (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/403/feedback/Alrekur%20-%20An%20Interesting%20FreeBSD%20Find) They presented at the FreeBSD Vendor summit last year too: https://www.youtube.com/watch?v=8LUdZseNrpE Sven - feedback (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/403/feedback/Sven%20-%20feedback) Robert - firewalling (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/403/feedback/Robert%20-%20firewalling) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

Mit LaTeX kann man Dokumente erzeugen. Aber wie? Und für wen eignet es sich?

Mit LaTeX kann man Dokumente erzeugen. Aber wie? Und für wen eignet es sich?

PHP Internals News: Episode 78: Moving the PHP Documentation to GIT London, UK Thursday, March 11th 2021, 09:06 GMT In this episode of "PHP Internals News" I chat with Andreas Heigl (Twitter, GitHub, Mastodon, Website) to follow up with his project to move the PHP Documentation project from SVN to GIT, which has now completed. The RSS feed for this podcast is https://derickrethans.nl/feed-phpinternalsnews.xml, you can download this episode's MP3 file, and it's available on Spotify and iTunes. There is a dedicated website: https://phpinternals.news Transcript Derick Rethans 0:15 Hi, I'm Derick. Welcome to PHP internals news, the podcast dedicated to explaining the latest developments in the PHP language. This is Episode 78. In this episode, I'm talking with Andreas Heigl about moving the PHP documentation to GIT. Andreas, would you please introduce yourself? Andreas Heigl 0:35 Hi yeah I'm Andreas, I'm working in Germany at a company doing PHP software development. I'm doing a lot of stuff in between, as well. And one of the things that I got annoyed, was always having to go through hilarious ways of contributing to the PHP documentation, every time I found an issue with that. So at one point in time, I thought why not move that to Git and, well, here we are. Derick Rethans 1:07 Here we are five years later, right? Because we already spoke about moving the documentation to GIT back in 2019 and Episode 28. But now it has finally happened, so I thought it'd be nice to catch up and see what actually has changed and how we ended up getting here. Where would you want to start. What was the hardest thing to sort out in the end? Andreas Heigl 1:27 Well the hardest thing in the end to sort out was people, as probably always in software development. The technical oddities and the technical bits and pieces were rather fast to solve. What really was taking a long time was, well for one thing, actually, consistently working on that. And on the other hand, chasing down people to actually get stuff done. Because one of the major things here was not the technical side but getting the bits and pieces of information together to get access to the different servers, to the infrastructure of the PHP ecosystem, and chasing down the people that want to help you is one thing, and then chasing down the people that actually can help you is a completely different one. That was for me the most challenging bit, getting actually, to know who can do what and getting, yeah in the end, getting access to the actual machines, the whole ecosystem is running on that was really heavy. Derick Rethans 2:34 The System Administration of PHP.net systems is very fragmented. There's some people having access to some machines and some other people having access to other machines and yea it sometimes takes some time to track down where are all these bits actually run. Andreas Heigl 2:51 One thing is getting tracking down, where the bits run, the other one is, there is an excellent documentation in the wiki, the PHP wiki, which in some parts is kind of outdated. The other thing is, if you don't actually address the different people themselves personally, it is like screaming into the void so you can can send an email to 15 different people that have access to a box, like someone needs to do this and this and this. And everyone kind of seems to think, yeah, someone else can do that. I just don't have the time at this point in time Things get delayed, so you're waiting for an answer for a week; you do some other stuff, so two weeks go into the lab four weeks go into the land, and suddenly two months have passed. You didn't receive an answer and oh wait a minute, there was this project with moving the documentation to GIT so perhaps I should have a look at that again. Derick Rethans 3:44 So what has changed for people that want to contribute to the PHP documentation. Can you explain a little bit the difference between before and after? Andreas Heigl 3:52 Before the documentation was moved everything was an SVN and there was generally there were two kinds of people. There were regular contributors that had an SVN account. They had the documentation on their machine. They could actually modify the documentation and just do an SVN commit, and everything was working smoothly, so that documentation was then actually built. We ran into some issues with that as well but that's a different story. Now, it is as everything is has moved to GIT, the sources are now on git.php.net. Before I come to that, what was it for people that did not have an SVN account. There was an awesome piece of technology on a web server called edit.php.net, which was a graphical user interface to the PHP documentation and to the translation so everyone could more or less log in there, with an anonymous account for example, modify the documentation, and create yeah well a kind of a pull request Create a patch that was then reviewed and could then be merged by people with SVN access. That awesome piece of technology was an awesome piece of technology when it was created some 12 years ago or something like that. It has not changed much in between. So it was still kind of working, not always, it was offline for some time. And the people that had access to the SVN were not really that responsive at all times so it could take some while for your patch to actually be merged in. So how is it now, now all the sources are on git.php.net, and there is a mirror for all translations, on https://github.com/php/, for example, doc-en for the English documentation. You have the repository, and you can create a pull request there. So you just move there, edit the file you want to move, create a pull request. And then the pull request will be merged into the main sources, again, by people with merge access. As this is a pull request that usually happens, a bit faster than before. We are still not at that point where we can create a GitHub action for that so that perhaps that can be completely automated after some technical things are resolved, like yes that does build, and we don't have any issues, technical issues with that. We could just build that automatically and merge that automatically into to the GIT sources. Those are possibilities that we now have, and from that point of view, now the contribution is much easier as we are using the technology that every one of us knows already. Derick Rethans 6:34 The original translation to work with sub modules in SVN, now how is with the GIT approach? Andreas Heigl 6:40 It actually didn't work with sub modules in SVN, it worked with, actually, one folder for the documentation, and then sub folders for the different translations. So there was a base folder PHP Doc, and within that base folder PHP Doc, there was a folder EN for the English base, kind of, and then DE for the German translation or PT_BR for the Brazilian Portuguese translation, or IT for the Italian translation. Or some other rather outdated translations that we actually didn't move over, so we only moved everything that was touched within the last two years, which brought some interesting bugs. Of course we actually moved something that was touched within the last two years, but that is not considered an active translation, and that caused some havoc. Derick Rethans 7:30 Which translation was that? Andreas Heigl 7:31 That was the Italian translation. So actually, there is no official Italian translation of the PHP documentation. But there is an Italian translation that is actually worked on, and hopefully at one point in time, we can actually promote that to a valid active translation, so that Italian people can actually see some Italian documentation for them. In GIT on the other hand, we have different repos, different repositories for the different languages. It is now, not possible to just check out phpdoc, and have every translation. Now you actually have to say, I want to check out the English documentation, and I want to check out the Italian documentation, and I want to check out the Japanese documentation, because I want to work on each of them. That has some disadvantages, especially for people that are working on multiple documentations or multiple translations. On the other hand, that also has advantages because you don't need to actually download all the translations that you're not at all interested in. Derick Rethans 8:35 But that shouldn't be something new because I'm pretty sure that I've never checked out all the translations, even with SVN. Andreas Heigl 8:41 SVN you could decide to only check out certain translations but if you check out the PHP doc base folder you would get all the documentation. Yes, there were some sub modules that actually did exactly that, like, if you check out the sub module for Italian for example you would get the English base and the Italian translation. That was all. Derick Rethans 9:04 I remember we employed some SVN magic to do that kind of things, but I forgot the most about that because it's so long ago, Andreas Heigl 9:11 Not really to worry about. Derick Rethans 9:14 No. Andreas Heigl 9:14 We're thinking about doing this similar thing for GIT now for the by using GIT sub modules, but we have not yet implemented that, because there were other pressing issues like getting the ref check documentation up and running, where you can actually see which files are outdated which files need to be translated and stuff like that. So that was more more pressing some other people have done, also work on that need to check what the current status is, to be honest, because I didn't check that. That was going on very strongly in January, after we moved between Christmas and New Year's Eve. After we equalized some glitches that happened during the whole process, because of Yeah, sometimes also processes that were nowhere really documented, and I got just got plain wrong. So then I had to invest some time and fix all that, but luckily that was during my holiday time so I had a lot of time for that so that was not an issue. Derick Rethans 10:15 So working on the documentation during your holiday's huh? Andreas Heigl 10:18 Yes, definitely. Derick Rethans 10:20 That makes it different from travelling to visit family, because that is of course not something we could do to here. Andreas Heigl 10:25 Exactly, though. Luckily, having a family at home was quite okay it was a nice change to actually be able to get away sometime, from seeing the same people over and over again. Derick Rethans 10:38 Now the documentation has moved from SVN to GIT, and everybody can now finally forget all their SVN commands. But the documentation itself is still written in Docbook. XML as far as I understand. Are there any discussions going on about changing that to something, perhaps a bit more modern? Andreas Heigl 10:58 Yes, there were a lot of discussions going on during the whole phase. I deliberately try to calm that down to not to too many things at once. The thing that I wanted to get going was moving the documentation from SVN to GIT. Just change the underlying source code repository, and not change anything else in the process, because that was already hard enough. Now that we have moved, it is easily possible to actually modify or move the documentation to some other toolage, whether that is markdown or ASCII doc or whatever. I don't care to be honest because that's someone else's job to do. In my opinion, Docbook is actually a pretty good format for that. Yes it is rather verbose for sure, but it allows you to create a lot of different documentations, because the HTML is not the only documentation that is created, there is also the possibility to create a PDF documentation or a CHM for Windows documentation, and stuff like that. I'm not 100% sure how that would work with a rather, with something like like markdown or ASCII doc or something like that. Derick Rethans 12:12 There's different strengths in different formats. Markdown for example doesn't really allow you to link in between documents, so that's probably not very handy but there's like Pandoc, which is stuff that the Python project uses. It's all pretty much designed around restructured text and linking in between them and stuff like that, so I guess that could be a way forward. It is certainly a lot easier to use than Docbook XML, but of course Docbook XML was created for this kind of rich marker without laying things out kind of situations right. Andreas Heigl 12:44 Yeah. The nice thing is actually that in with Docbook. What perhaps that is possible with other tools as well but in Docbook for example, you have one single file where all the links are located in, and every translation just links to this one file, so if a link changes for whatever reason, you can just modify that in one place and don't have to go through all the documentation. And, of course, leave half of the links unchanged, and broken, whatever. So there is a lot of stuff actually that is pretty cool. But as I said that's now up for discussion. If there is someone that actually wants to tackle that and move the documentation format to something else that is a different story. Go ahead, propose that to the internals mailing list, or to the documentation team, we'll see how it goes from there. The documentation itself, the source code itself, is hosted on a platform that we all understand, at least by now a bit better than SVN. Derick Rethans 13:42 Even though it started out on CVS, just like PHP that's. Andreas Heigl 13:46 Yes. Derick Rethans 13:47 A long long time ago. Andreas Heigl 13:49 I found the remaining stuff from the transfer from S from CVS to SVN, yes, Derick Rethans 13:55 I am sure there's still some commits lurking somewhere for that. Andreas Heigl 13:59 Oh yes, especially in the in the ref check, there is a lot of commented out code with yeah CV, in CVS we did it this way now we have to modify that for SVN. Yes, I'm pretty sure now we have some commits in there that modify the SVN stuff for making it usable with GIT. Derick Rethans 14:16 Andreas, do you have anything else to add? Andreas Heigl 14:19 In all it was an awesome experience for me. I got to know a lot of people, a lot of awesome people. That was really really insightful, and I'm really happy that I had the chance to do that, and the trust of the community was really amazing. If anyone wants to get into that stuff, kind of stuff, pick yourself something that the community needs, and go for it, and don't let yourself be derailed by unresponsive mailing lists, or just things not happening. It's not because people think you are stupid, or the task is stupid, it's just because everything is done by volunteers that just pays its price. Derick Rethans 15:00 It certainly does. Thank you, Andreas for taking the time today to talk to me about moving to PHP documentation to GIT. Andreas Heigl 15:07 Thank you very much. It was a pleasure to be here. Derick Rethans 15:13 Thank you for listening to this instalment of PHP internals news, a podcast dedicated to demystifying the development of the PHP language. I maintain a Patreon account for supporters of this podcast, as well as the Xdebug debugging tool. You can sign up for Patreon at https://drck.me/patreon. If you have comments or suggestions, feel free to email them to derick@phpinternals.news. Thank you for listening, and I'll see you next time. Show Notes Episode #28: Moving PHP Documentation to GIT Credits Music: Chipper Doodle v2 — Kevin MacLeod (incompetech.com) — Creative Commons: By Attribution 3.0

**libx86** and **linuxdoc-tools**, including Asciidoc and Docbook. shasum -a256=156ae740fe92fd7506cb6ceb4f71b51e1a6932e8f4c77edb8fa2771c7747a968

Hannah Kirk Hannah Kirk has great ideas about how technical writing and content strategy can support each other. She's not a typical tech writer. She loves and appreciates technical documentation and enjoys practicing it. But she has always been more interested in strategy. And she has always spent a lot of time thinking about how content is organized. Hannah and I talked about: #BlackLivesMatter her background in enterprise technical writing her transition to identifying as a content strategist the history of technical writing the benefits of component-ized content, especially compared to old-fashioned documents and publications the shift in the role of tech writers form being publication formatters to folks more focused on writing topic-based authoring and DITA and Flare and Oxygen and similar tools how she's not a "typical" technical writer the four times she has been the sole technical writer/content strategist in an organization a confusing juncture in her career when she went to Silicon Valley and found that they weren't at the cutting edge of technical documentation :) tools for technical writers - from Microsoft Word, to Framemaker, XMetal, Oxygen, Markdown, DITA, DocBook, and more the benefits of Markdown in tech-savvy organizations like startups the importance for technical writers of having a few more technical skills than other content strategists how she engages engineers and other sometimes-hard-to-engage folks in conversation her message to the content strategy profession: Don't overlook technical writers as an ally in your work, and likewise her desire to learn from content strategists Hannah's Bio Hannah Kirk (a.k.a. “The Pink-haired Content Strategist”) is a content strategist in Silicon Valley, working primarily with B2B software products. Hannah started technical documentation departments and worked as a lone writer at four startups. She implemented processes, authoring tools, CMS's, and publishing flows in FrameMaker, DITA, Docbook, and Markdown and integrated small documentation departments into larger companies as a result of three acquisitions. She's now at Inkling bringing customer content into the Inkling platform and advising customers on best practices of migrating, organizing, and optimizing content. Hannah also started the Medium publication, Content Strategy Adventures. Follow Hannah on social media HannahKirk215 on LinkedIn PinkHairedCS on Twitter PinkHairedCS on Medium Video Here's the video version of our conversation: https://youtu.be/2fg9DEufj1Q Podcast Intro Transcript Depending on how you look at it, the profession of technical writing may be the oldest branch of the field we now call content strategy. Technical documentation pre-dates the web by at least a couple of decades. And many of the practices now being adopted by content strategists have their origins in technical communications. Hannah Kirk has been writing technical documentation for more than 15 years. She has some great insights into how content strategy and technical communications can support each other. Interview Transcript Larry: Hi, everyone. Welcome to Episode Number 70 of the Content Strategy Insights podcast. I'm really happy today to have with us, Hannah Kirk. We'll talk a little bit more about Hannah's background in just a couple of minutes, but I want to start this episode by just acknowledging that we are in a really fraught time right now. We're recording this episode on June 3, 2020. We're just a week or so out from the horrific murder of George Floyd and the ensuing protests and other activities around that. I just want to say, we're not going to talk about that on this podcast, but I just want to acknowledge upfront that black lives matter. One of the things that Hannah and I were talking about before we went on the air is that how, I think, for people, the content strategy field is a field that's uniquely positioned or uniqu...

Hannah Kirk Hannah Kirk has great ideas about how technical writing and content strategy can support each other. She's not a typical tech writer. She loves and appreciates technical documentation and enjoys practicing it. But she has always been more interested in strategy. And she has always spent a lot of time thinking about how content is organized. Hannah and I talked about: #BlackLivesMatter her background in enterprise technical writing her transition to identifying as a content strategist the history of technical writing the benefits of component-ized content, especially compared to old-fashioned documents and publications the shift in the role of tech writers form being publication formatters to folks more focused on writing topic-based authoring and DITA and Flare and Oxygen and similar tools how she's not a "typical" technical writer the four times she has been the sole technical writer/content strategist in an organization a confusing juncture in her career when she went to Silicon Valley and found that they weren't at the cutting edge of technical documentation :) tools for technical writers - from Microsoft Word, to Framemaker, XMetal, Oxygen, Markdown, DITA, DocBook, and more the benefits of Markdown in tech-savvy organizations like startups the importance for technical writers of having a few more technical skills than other content strategists how she engages engineers and other sometimes-hard-to-engage folks in conversation her message to the content strategy profession: Don't overlook technical writers as an ally in your work, and likewise her desire to learn from content strategists Hannah's Bio Hannah Kirk (a.k.a. “The Pink-haired Content Strategist”) is a content strategist in Silicon Valley, working primarily with B2B software products. Hannah started technical documentation departments and worked as a lone writer at four startups. She implemented processes, authoring tools, CMS's, and publishing flows in FrameMaker, DITA, Docbook, and Markdown and integrated small documentation departments into larger companies as a result of three acquisitions. She’s now at Inkling bringing customer content into the Inkling platform and advising customers on best practices of migrating, organizing, and optimizing content. Hannah also started the Medium publication, Content Strategy Adventures. Follow Hannah on social media HannahKirk215 on LinkedIn PinkHairedCS on Twitter PinkHairedCS on Medium Video Here’s the video version of our conversation: https://youtu.be/2fg9DEufj1Q Podcast Intro Transcript Depending on how you look at it, the profession of technical writing may be the oldest branch of the field we now call content strategy. Technical documentation pre-dates the web by at least a couple of decades. And many of the practices now being adopted by content strategists have their origins in technical communications. Hannah Kirk has been writing technical documentation for more than 15 years. She has some great insights into how content strategy and technical communications can support each other. Interview Transcript Larry: Hi, everyone. Welcome to Episode Number 70 of the Content Strategy Insights podcast. I'm really happy today to have with us, Hannah Kirk. We'll talk a little bit more about Hannah's background in just a couple of minutes, but I want to start this episode by just acknowledging that we are in a really fraught time right now. We're recording this episode on June 3, 2020. We're just a week or so out from the horrific murder of George Floyd and the ensuing protests and other activities around that. I just want to say, we're not going to talk about that on this podcast, but I just want to acknowledge upfront that black lives matter. One of the things that Hannah and I were talking about before we went on the air is that how, I think, for people, the content strategy field is a field that's uniquely positioned or uniqu...

In this episode, we chat with technical writer Bob Binstock about mirroring databases in InterSystems products — specifically in InterSystems IRIS. Bob is a technical writer at InterSystems with lots of knowledge about topics like these, and he walks us through the concept of mirroring for high availability. You'll hear about primaries and backups, journal files, failovers, and more. To try out the First Look exercise on data resiliency and mirroring, visit https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=AFL_dataresil. For more information about Data Points, visit https://datapoints.intersystems.com.

Do 208. dílu dorazil Radim Šnajdr a Vilém Vatrt z Quadientu a téma bylo školení, dokumentace no prostě všechno co jsme si jako mladí elévové zažili. Jaké bylo naše překvapení, že nástroje, se kterými jsme pracovali ještě my, jsou stále používané. Ať žije DocBook! V podcastu ukázal Vilda své lingvistické dovednosti, můžete se těšit na zdravici ve španělštině a portugalštině.

Dans cet épisode, Maxime et Guillaume discutent des langages de markup - en particulier Asciidoctor - pour l’écriture de documentation. Quels sont leurs bénéfices, quels outils et flux de travail adopter ? On y aborde ces questions. Enregistré le 31 mars 2016 Téléchargement de l’épisode LesCastCodeurs-Episode–144.mp3 Interview Ta vie, ton oeuvre Maxime Gréau @mgreau eXo Platform Guillaume Scheibel @g_scheibel Expedia Markup et documentation Qu’est-ce qu’un langage de markup ? Pourquoi est-ce mieux, quels sont les avantages ? HTML XML AsciiDoc / Asciidoctor LaTeX Docbook Qu’est-ce qu’AsciiDoc ? Quelles sont ses caractéristiques uniques Qu’est-ce qu’Asciidoctor ? AsciiDoc Asciidoctor Comparaison avec Markdown Comparaison avec Docbook Markdown WYSIWYG Une idée par ligne Une idée par ligne - le retour d’expérience En pratique Qu’est-ce que j’installe ? Un blog en Français décrivant tous les outils pour débuter Google Chrome plugin: Asciidoctor.js Live Preview Firefox plugin: Asciidoctor.ja Live Preview Asciidoctor Gist Conteneur Docker pour Asciidoctor Maven Plugin Gradle Plugin Ant Task Comment j’apprends ? Documentation Asciidoctor L’antisèche La bible Comparaison AsciiDoc vs Markdown par l’équipe Asciidoctor Comment est-ce que j’édite ? Les éditeurs disponibles La boucle de retour écriture / visualisation (locale ou en ligne) Atom Bracket IntelliJ Eclipse Vim folding Convertir sa documentation existante DocbookRx (docbook vers AsciiDoc) docbook2asciidoc (Docbook vers AsciiDoc) via XSLT Kramdown pour AsciiDoc Markdown to AsciiDoc Pandoc Google Docs vers AsciiDoc Comment gérer les modifications concurrentes et les commentaires (à la Microsoft Word et LibreOffice) Écrire de la documentation Quels sont les avantages Comment convaincre les non développeurs d’utiliser Asciidoctor ? La composition et la réutilisation de morceaux de documentation Les autres cas d’utilisation Écrire un livre Ecrire un livre en AsciiDoc avec InfoQ Enterprise Web Development: From Desktop to Mobile écrit en AsciiDoc avec O’Reilly - source du livre en AsciiDoc Pro Git v2 (FR) - source du livre en AsciiDoc Un blog HubPress.io Jeckyll AsciiDoc plugin et son quickstart Le code du site web hibernate.org Le code du blog de l’équipe Hibernate Les présentations reveal.js avec Asciidoctor dzslides avec Asciidoctor deckjs avec Asciidoctor Bespoke avec Asciidoctor Exemple de présentation de Maxime en dzslides + Asciidoctor - source Quelques points précis Les additions (formules mathématiques, schémas, etc) Les diagrammes Comment contribuer Communauté française importante Compte Github Ruby -> core Java -> asciidoctorJ wrapper via JRuby Javascript -> asciidoctor.js CoffeeScript -> plugin Atom Nous contacter Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/ Flattr-ez nous (dons) sur https://lescastcodeurs.com/ En savoir plus sur le sponsoring? sponsors@lescastcodeurs.com

02:18 - Ben Browning Introduction Twitter GitHub Blog Red Hat JRuby 02:46 - TorqueBox @torquebox 04:05 - Use Cases and Benchmarks TechEmpower's latest round of benchmark results, filtered to just the Ruby servers running Rack/Rails/Sinatra/etc apps and their JSON serialization test 06:32 - The Genesis of TorqueBox Bob McWhirter 07:49 - JBoss WildFly 09:15 - The Name “TorqueBox” 10:12 - Adoption 12:05 - Documentation DocBook YARD 13:18 - When should/could you use TorqueBox? 17:25 - Monolith vs Microservice WildFly Swarm 21:36 - JAR Files and WAR Files 25:31 - Server Setup & Deployment Process 27:16 - Packaging Static Assets in JAR and WAR Files 28:27 - Contribution and Community Involvement 32:55 - Startup Cost 35:53 - Getting Started with TorqueBox 37:33 - Immutant 40:17 - The Rack Spec and TorqueBox tubesock SockJS 42:11 - Useful Features 44:26 - Building Useful Features 45:53 - Growth Picks [Khan Academy] Pixar in a Box: Introduction to Animation Curves (Saron) Tony Stark in Salt and Pepper (Saron) ElixirConf (Jessica) Nick Shrock: GraphQL Introduction (Jessica) Troll - Shane Koyczan (Coraline) funtools (Coraline) Ruby Remote Conf Talks (Chuck) Angular Remote Conf (Chuck) Bob McWhirter: qcon-keynote (Ben) Coders For Sanders (Ben) Extras JavaScript Jabber Episode #152: GraphQL and Relay with Nick Schrock and Joe Savona

02:18 - Ben Browning Introduction Twitter GitHub Blog Red Hat JRuby 02:46 - TorqueBox @torquebox 04:05 - Use Cases and Benchmarks TechEmpower's latest round of benchmark results, filtered to just the Ruby servers running Rack/Rails/Sinatra/etc apps and their JSON serialization test 06:32 - The Genesis of TorqueBox Bob McWhirter 07:49 - JBoss WildFly 09:15 - The Name “TorqueBox” 10:12 - Adoption 12:05 - Documentation DocBook YARD 13:18 - When should/could you use TorqueBox? 17:25 - Monolith vs Microservice WildFly Swarm 21:36 - JAR Files and WAR Files 25:31 - Server Setup & Deployment Process 27:16 - Packaging Static Assets in JAR and WAR Files 28:27 - Contribution and Community Involvement 32:55 - Startup Cost 35:53 - Getting Started with TorqueBox 37:33 - Immutant 40:17 - The Rack Spec and TorqueBox tubesock SockJS 42:11 - Useful Features 44:26 - Building Useful Features 45:53 - Growth Picks [Khan Academy] Pixar in a Box: Introduction to Animation Curves (Saron) Tony Stark in Salt and Pepper (Saron) ElixirConf (Jessica) Nick Shrock: GraphQL Introduction (Jessica) Troll - Shane Koyczan (Coraline) funtools (Coraline) Ruby Remote Conf Talks (Chuck) Angular Remote Conf (Chuck) Bob McWhirter: qcon-keynote (Ben) Coders For Sanders (Ben) Extras JavaScript Jabber Episode #152: GraphQL and Relay with Nick Schrock and Joe Savona

02:18 - Ben Browning Introduction Twitter GitHub Blog Red Hat JRuby 02:46 - TorqueBox @torquebox 04:05 - Use Cases and Benchmarks TechEmpower's latest round of benchmark results, filtered to just the Ruby servers running Rack/Rails/Sinatra/etc apps and their JSON serialization test 06:32 - The Genesis of TorqueBox Bob McWhirter 07:49 - JBoss WildFly 09:15 - The Name “TorqueBox” 10:12 - Adoption 12:05 - Documentation DocBook YARD 13:18 - When should/could you use TorqueBox? 17:25 - Monolith vs Microservice WildFly Swarm 21:36 - JAR Files and WAR Files 25:31 - Server Setup & Deployment Process 27:16 - Packaging Static Assets in JAR and WAR Files 28:27 - Contribution and Community Involvement 32:55 - Startup Cost 35:53 - Getting Started with TorqueBox 37:33 - Immutant 40:17 - The Rack Spec and TorqueBox tubesock SockJS 42:11 - Useful Features 44:26 - Building Useful Features 45:53 - Growth Picks [Khan Academy] Pixar in a Box: Introduction to Animation Curves (Saron) Tony Stark in Salt and Pepper (Saron) ElixirConf (Jessica) Nick Shrock: GraphQL Introduction (Jessica) Troll - Shane Koyczan (Coraline) funtools (Coraline) Ruby Remote Conf Talks (Chuck) Angular Remote Conf (Chuck) Bob McWhirter: qcon-keynote (Ben) Coders For Sanders (Ben) Extras JavaScript Jabber Episode #152: GraphQL and Relay with Nick Schrock and Joe Savona

缘起： ThoughtWorks 是传说中的十大最难面试公司之首，前段时间 ThoughtWorks 的 HR 任蕙在 RubyChina 发了一篇帖子，标题是：“找工作的人那么多，为什么我还招不到人？来吐槽面试好么?” 并收到了很多网友的问题，我联系了任蕙，争取到一次采访两位来自 ThoughtWorks 的面试官的机会，于是我带着这些问题走进了 ThoughtWorks 北京办公室，开始了本次访谈。 在准备这期访谈之前，我有一个疑虑，很担心本期的采访嘉宾，ThoughtWorks 的面试官韩凯和王健会以公司发言人的态度和方式应对本次访谈，但是当我见到两位面试官后，我的疑虑被彻底打消了。两位面试官一开始就以当年黑暗的亲身经历，给我们展现了两个活生生的草根逆袭的励志故事，然后一步一步解构一家全球顶尖IT公司的面试流程每个环节，特点，并给出非常实际可操作性极强的建议，访谈中两位面试官诙谐幽默，让整个过程笑场不断，内容让人深受启发却又感觉轻松欢快…… 本期的话题 十大入职面试最难的科技公司，ThoughtWorks 排名第一，你敢来挑战么？ 两位 ThoughtWorks 的面试官用自己当年的面试经历现身说法。 ThoughtWorks 的面试号称业界最难，他们面试方式给候选人带来怎样的压力，候选人在面试中可能容易犯的错误，以及面试官建议。 ThoughtWorks 是一家什么样的公司，入职 ThoughtWorks 可以给你怎样的成长和未来？ ThoughtWorks ThoughtWorks的HR任蕙 找工作的人辣么多，为什么我还招不到人。来吐槽面试好么 疯狂英语 熊节 梦想风暴 APM 最难面试的IT公司，你敢来挑战么？ 结对编程 RubyChina 敏捷软件开发 精益软件开发 Docbook Scala Clojure HHKB Aeron Chairs ThoughtWorks Go 马丁·福勒 ThoughtWorks University 把时间当作朋友 ibuick OS X Mountain Lion高手进阶 CI 雪球专刊 Special Guests: 王健 and 韩凯.

本期由Terry Tai主持，邀请到了国内著名的 Common Lisp 程序员，实用 Common Lisp 编程 一书的译者田春(冰河)，和我们一起聊聊 Lisp 的方方面面, 揭开 Lisp 的神秘面纱。 实用Common Lisp编程 KnewOne Solaris Studio On Lisp ANSI Common Lisp Common Lisp the Language, 2nd Edition SICP S-表达式 Simple Network Management Protocol SourceForge cl-net-snmp Racket Scheme Common Lisp HyperSpec LispWorks SLIME Hunchentoot Quicklisp Clojure Paul Graham Arc Hacker News LALR parser Rich Hickey ABCL yacc FileMaker Pro FrameMaker InDesign DocBook LaTeX The Little Schemer Paul Graham Special Guests: 李路 and 田春(冰河).

We kick off the first episode with the latest BSD news, show you how to avoid intrusion detection systems and talk to Peter Hessler about BGP spam blacklists! Headlines Radeon KMS commited (https://lists.freebsd.org/pipermail/svn-src-head/2013-August/050931.html) Committed by Jean-Sebastien Pedron Brings kernel mode setting to -CURRENT, will be in 10.0-RELEASE (ETA 12/2013) 10-STABLE is expected to be branched in October, to begin the process of stabilizing development Initial testing shows it works well May be merged to 9.X, but due to changes to the VM subsystem this will require a lot of work, and is currently not a priority for the Radeon KMS developer Still suffers from the syscons / KMS switcher issues, same as Intel video More info: https://wiki.freebsd.org/AMD_GPU *** VeriSign Embraces FreeBSD (http://www.eweek.com/enterprise-apps/verisign-embraces-open-source-freebsd-for-diversity/) "BSD is quite literally at the very core foundation of what makes the Internet work" Using BSD and Linux together provides reliability and diversity Verisign gives back to the community, runs vBSDCon "You get comfortable with something because it works well for your particular purposes and can find a good community that you can interact with. That all rang true for us with FreeBSD." *** fetch/libfetch get a makeover (http://freshbsd.org/commit/freebsd/r253680) Adds support for SSL certificate verification Requires root ca bundle (security/rootcanss) Still missing TLS SNI support (Server Name Indication, allows name based virtual hosts over SSL) *** FreeBSD Foundation Semi-Annual Newsletter (http://www.freebsdfoundation.org/press/2013Jul-newsletter) The FreeBSD Foundation took the 20th anniversary of FreeBSD as an opportunity to look at where the project is, and where it might want to go The foundation sets out some basic goals that the project should strive towards: Unify User Experience “ensure that knowledge gained mastering one task translates to the next” “if we do pay attention to consistency, not only will FreeBSD be easier to use, it will be easier to learn” Design for Human and Programmatic Use 200 machines used to be considered a large deployment, with high density servers, blades, virtualization and the cloud, that is not so anymore “the tools we provide for status reporting, configuration, and control of FreeBSD just do not scale or fail to provide the desired user experience” “The FreeBSD of tomorrow needs to give programmability and human interaction equal weighting as requirements” Embrace New Ways to Document FreeBSD More ‘Getting Started' sections in documentation Link to external How-Tos and other documentation “upgrade the cross-referencing and search tools built into FreeBSD, so FreeBSD, not an Internet search engine, is the best place to learn about FreeBSD” Spring Fundraising Campaign, April 17 - May 31, raised a total of $219,806 from 12 organizations and 365 individual donors. In the same period last year we raised a total of $23,422 from 2 organizations and 53 individuals Funds donated to the FreeBSD Foundation have been used on these projects recently: Capsicum security-component framework Transparent superpages support of the FreeBSD/ARM architecture Expanded and faster IPv6 Native in-kernel iSCSI stack Five New TCP Congestion Control Algorithms Direct mapped I/O to avoid extra memory copies Unified Extensible Firmware Interface (UEFI) boot environment Porting FreeBSD to the Genesi Efika MX SmartBook laptop (ARM-based) NAND Flash filesystem and storage stack Funds were also used to sponsor a number of BSD focused conferences: BSDCan, EuroBSDCon, AsiaBSDCon, BSDDay, NYCBSDCon, vBSDCon, plus Vendor summits and Developer summits It is important that the foundation receive donations from individuals, to maintain their tax exempt status in the USA. Even a donation of $5 helps make it clear that the FreeBSD Foundation is backed by a large community, not only a few vendors Donate Today (http://www.freebsdfoundation.org/donate) *** The place to B...SD Ohio Linuxfest, Sept. 13-15, 2013 (http://ohiolinux.org/schedule) Very BSD friendly Kirk McKusick giving the keynote BSD Certification on the 15th, all other stuff on the 14th Multiple BSD talks *** LinuxCon, Sept. 16-18, 2013 (http://events.linuxfoundation.org/events/linuxcon-north-america) Dru Lavigne and Kris Moore will be manning a FreeBSD booth Number of talks of interest to BSD users, including ZFS coop (http://linuxconcloudopenna2013.sched.org/event/b50b23f3ed3bd728fa0052b54021a2cc?iframe=yes&w=900&sidebar=yes&bg=no) EuroBSDCon, Sept. 26-29, 2013 (http://2013.eurobsdcon.org/eurobsdcon-2013/talks/) Tutorials on the 26 & 27th (plus private FreeBSD DevSummit) 43 talks spread over 3 tracks on the 28 & 29th Keynote by Theo de Raadt Hosted in the picturesque St. Julians Area, Malta (Hilton Conference Centre) *** Interview - Peter Hessler - phessler@openbsd.org (mailto:phessler@openbsd.org) / @phessler (https://twitter.com/phessler) Using BGP to distribute spam blacklists and whitelists Tutorial Using stunnel to hide your traffic from Deep Packet Inspection (http://www.bsdnow.tv/tutorials/stunnel) News Roundup NetBSD 6.1.1 released (https://blog.netbsd.org/tnf/entry/netbsd_6_1_1_released) First security/bug fix update of the NetBSD 6.1 release branch Fixes 4 security vulnerabilities Adds 4 new sysctls to avoid IPv6 DoS attacks Misc. other updates *** Sudo Mastery (http://blather.michaelwlucas.com/archives/1792) MWL is a well-known author of many BSD books Also does SSH, networking, DNSSEC, etc. Next book is about sudo, which comes from OpenBSD (did you know that?) Available for preorder now at a discounted price *** Documentation Infrastructure Enhancements (http://freebsdfoundation.blogspot.com/2013/08/new-funded-project-documentation.html) Gábor Kövesdán has completed a funded project to improve the infrastructure behind the documentation project Will upgrade documentation from DocBook 4.2 to DocBook 4.5 and at the same time migrate to proper XML tools. DSSSL is an old and dead standard, which will not evolve any more. DocBook 5.0 tree added *** FreeBSD FIBs get new features (https://svnweb.freebsd.org/base?view=revision&revision=254943) FIBs (as discussed earlier in the interview) are Forward Information Bases (technical term for a routing table) The FreeBSD kernel can be compiled to allow you to maintain multiple FIBs, creating separate routing tables for different processes or jails In r254943 ps(1) is extended to support a new column ‘fib', to display which routing table a process is using *** FreeNAS 9.1.0 and 9.1.1 released (http://www.ixsystems.com/resources/ix/news/ixsystems-announces-revolutionary-freenas-910-release.html) Many improvements in nearly all areas, big upgrade Based on FreeBSD 9-STABLE, lots of new ZFS features Cherry picked some features from 10-CURRENT New volume manager and easy to use plugin management system 9.1.1 released shortly thereafter to fix a few UI and plugin bugs *** BSD licensed "patch" becomes default (http://freshbsd.org/commit/freebsd/r253689) bsdpatch has become mature, does what GNU patch can do, but has a much better license Approved by portmgr@ for use in ports Added WITHGNUPATCH build option for people who still need it ***