 Hi there everybody, welcome back to the fedora documentation fad 2016 this is the day to report out We are using a local video rather than blue jeans for a number of reasons but What happened today was we started out with a demo of a number of projects that could potentially help us out of solutions This included doxodruple, which was presented by Silas Anerist, which we had presented by mr. Travis and Pintail, which was presented by mr. McCann's We looked at each of the demos we talked about their strengths and weaknesses and then we put them up on the board behind us and We took all of those Post-it notes with the priorities and walked through the top ones from each category In a spreadsheet and we said whether or not it was a plus a check or a minus and rank them all based on the requirements of our users so at the list that we had for that was a Pintail based tool chain wordpress Drupal media wiki Golem and kuma, which is what Mozilla development network uses and After going through extensively through the list and doing pluses and minuses We actually settled on a Pintail with Pagura repos as sort of the proposed solution and a more succinct or direct description of that would be Using Pagura repos which are settled on an ASCII doc format that we are then running through an orchestration layer that does continuous integration continuous deployment and Translation that we can then pump through Pintail and then a publishing layer so that we can get ASCII docs that will be useful to make fedora and upstream for rel and having the repositories each sort of sectioned off individually We already have some of our doc repos on Pagura and we're going to explore solutions more in-depth tomorrow if you would like to look at the voting and justification for the Sort of requirements of vetting that we did today Inside of the etherpad doc, which is etherpad.osuosl.org slash fedora Docs fad 2016 all one word you should find that under the subheading of day two Otherwise, we will be making this video available online Thank you all for following along and We also took IRC notes from different people during the day Thank you to everybody who participated and we're going to pick up tomorrow By experimenting with solutions and seeing where we end up and making sure that we have specific tasks that we can identify Owners for and have some dates so that we can do actionable things starting tomorrow and continuing on and doing check-ins on a regular basis include Google Summer for Code internship tasks and a variety of other Interesting ways of tackling this large problem, but lots of consensus today I think we made we did our due diligence and now it's a matter of just working through some solutions So thanks everybody for who participated and we'll see you tomorrow And I'll do it around the room once because we got a bunch of people here. That's probably worth it Mr. Gilson It's always be Travis Mr. Lurch Silas Sean Jim and Back to the board and our friends online who are not online right now. Alright. Thanks everybody and we'll see you tomorrow Happy hacking