docs November 2013

docs@lists.fedoraproject.org

18 participants
24 discussions

#5214: Setup koji tags and repo for Docs
by Fedora Release Engineering 21 Jan '14

21 Jan '14

#5214: Setup koji tags and repo for Docs -----------------------------+------------------------ Reporter: crantila | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: docs | Blocked By: Blocking: | -----------------------------+------------------------ Posted here as per [https://fedorahosted.org/fedora- infrastructure/ticket/3320] '''phenomenon''' To support simpler and more robust updates to docs.fp.o, need to setup koji to handle a new tag and repo for Docs. '''implementation recommendation''' <Sparks> What would be required to stand up a separate instance of koji for Docs? <dgilmore> Sparks: why would you want a seperate instance? <dgilmore> Sparks: i dont see any valid reason to do so <Sparks> dgilmore: For the Docs website. Publican has the ability publish documentation from packages (separate repo from the Fedora repo) for the website. We want to replace the git repo that operates it now. <dgilmore> Sparks: and why does that need a seperate koji? <Sparks> The git repo has gotten HUGE and is becoming an issue. <dgilmore> Sparks: so, why does that mean a seperate koji instance <dgilmore> Sparks: we could use a seperate tag and targets in koji <dgilmore> i dont see why it would need its own koji <Sparks> dgilmore: It's either that or try to get everyone setup as packagers. <dgilmore> Sparks: get everyone setup as packagers <Sparks> dgilmore: Except that they really won't be packagers. <dgilmore> Sparks: though you dont need to be a a packager to get a koji cert <dgilmore> you just need fas <dgilmore> Sparks: what would be the workflow? <Sparks> dgilmore: Okay, and with that we can send packages through koji and tag them separately? <Sparks> dgilmore: Basically we just tell Publican to build the package and submit it to koji. The Publican software does all the work. <dgilmore> Sparks: I still really dont know what your trying to do. pretend im an idiot(not really that hard) and explain what it is and how it should work <Sparks> dgilmore: I'm not far off... <Sparks> dgilmore: So Publican will make an SRPM package, submit it to koji destined for a repo. Our Publican backend will install those packages and publish the data to the website. <Sparks> ...as I understand it <dgilmore> Sparks: so we would need to set up seperate tags and tagets for it, defining a koji policy allowing srpms to be built. likely we would add a new group to koji and add people allowed to build docs to it and limit access to the tags/targets to people in that group <dgilmore> Sparks: so its all doable <Sparks> dgilmore: Well that's a lot easier. :) <Sparks> dgilmore: We already have a group in FAS for people that should have access (docs- publishers). Should I open a ticket? <dgilmore> Sparks: koji doesnt know anything about fas <dgilmore> Sparks: please file a ticket. We wont be able to make changes until after f17 is done <Sparks> dgilmore: That's fine. We're not completely ready for the transition so after F17 would be good. <Sparks> dgilmore: Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5214> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 15

Docs FAD 2014
by Eric Christensen 31 Dec '13

31 Dec '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 It's been a while[0] since we've all gathered around a table and broke bread (or pizza). I wonder if it's time to have another FAD and get people focused on knocking out some of the documentation problems we've seem to had over the past few releases with regards to new features (and old ones going away). We will also have a new publishing system by then (hopefully) so it might be good to make sure everyone is on the same page. With that, I introduce the idea of the Docs FAD 2014[1]. Since our group has become quite diverse (geographically, among other traits) I'm thinking that having two FADs linked by video teleconferencing would work the best. The Brno office already has said that they'd be interested in doing this and I'm hoping I can get the Raleigh office onboard as well. If you are interested in participating please add your name to the list[2] and include your means of travel (of if you're local say so). I'm going to try to get a budget for this to help people travel and stay. It would also be good to include weekends that you are available to do this in January. Thanks! [0] https://fedoraproject.org/wiki/FAD_SELF_2009 [1] https://fedoraproject.org/wiki/Docs_FAD_2014 [2] https://fedoraproject.org/wiki/Docs_FAD_2014#Participants - -- Eric - -------------------------------------------------- Eric "Sparks" Christensen Fedora Project sparks(a)fedoraproject.org - sparks(a)redhat.com 097C 82C3 52DF C64A 50C2 E3A3 8076 ABDE 024B B3D1 - -------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQGcBAEBCgAGBQJSik9hAAoJEB/kgVGp2CYvoFgL/21eqDddqGzaHs1j03petxMG OByisqAw6Lo8TxlnEy73WeOteFn78ehYd1FvWKTiJ6yibfIWzG4YYGl8Un8xIsm1 2e2RCwnzbRXnamFlfc3jOYTV3YayAmJ9sEIpYrrifKgWO9HECROpNX9ncvl9+Y74 GdH8dVklQARym3D6wwIUYbQh174gCtNdage1GAz+1vvHmyRRp2fcqlZP4PuTebcz yC+4WVxaODQOwi5extykTOZukInktETqh49fL53ahKJ8hd+kECJqVcKrdzNE85xG /r/KPjeT/FhK97kgQb5sewK6HhJ0Bj6QV2+pY3nVosHqhWEqXf0DGlbupyN8CvBv i5ORvJ9EOrA3cvO2QabEgtYkbftUC94izpu3f5NJ6trnGOQEsrC/MtDs9BhOmNn0 veW58MHGSrWCr6B3XaFrpAZZV7XVZv9lvv8v0md10J4mBggOXAwEEEJABdS2YMLi 6GwPbdxJrTlKOoBZ0n3ZSsqFDxhTAdN/SAaGAGBNTg== =n8Nh -----END PGP SIGNATURE-----

5 9

Lowering the participation barrier for Fedora Docs
by Pete Travis 30 Dec '13

30 Dec '13

I took some time over the weekend to update my workstation to F20. It involved performing a lot of now routine tasks; installing the package set I use, pulling in the git repo I keep for $HOME, updating /etc/fstab to include network shares, adding a couple polkit rules for libvirt, blah blah. I'm sure we all have such a list. These are among many routine, everyday tasks for Fedora users. The kind of task that an experienced user could sit down and perform, and write up a how-to for the action on the fly while they do it. The kind of task that an inexperienced user would ask about on a forum, or on irc, or research with relatively specific search terms. I think of this as 'incidental' or 'case-specific' documentation, rather than generalized documentation as provided in the guides. Our existing documentation base is *great*, and anyone who reads through it all will surely come out with the ability to fill in the gaps and handle case-specific problems. We're teaching techniques and tools, not execution. However, between the broad nature of the guides and the SEO reality of a publican site, I think we are failing to reach many users that are actively looking for tutorial-format content. Publican based guides have one major shortcoming. The barrier to entry for potential contributors is high. I had a chance at Flock to have some candid conversation over beer with a few folks outside of the loyal Docs team, and there was a general consensus that while they might be willing to write some *incidental* documentation - again, my term - contributing to a guide was an ordeal they didn't have time for. We've seen this repeatedly with new contributors as well, people who start out with enthusiasm that fades when there isn't work that they can easily drop into. Contributing to a guide is *not* a casual endeavor; it requires us to not only learn docbook and the subject matter, but to be entirely self-motivated while working on a project owned by someone else. Fitting into the workflow is just as intimidating as learning the tools, if not more. I would like to try something different. We should have a product that leverages the experience and quality of our seasoned contributors and enables new contributors to get started. We should have something that helps inexperienced, impatient users. We should enable the Fedora community at large to participate in our efforts, and I think that means coming to them as much as them coming to us. If we have something easier to contribute to, more contributors will likely follow, and then contributors and content for guides as well. I've set up a quick demonstration[1] of some software that I think will address these concerns, a python application called "Nikola"[2]. I have a package review in progress for it, and have already packaged some dependencies. Briefly, it takes plain text files with ReStructuredText or Markdown and transforms them into fully themed static websites. It hooks in to transifex nicely as well. Take a look, you'll find a post detailing how the implementation might work, and a post for the kind of content I envision putting there. [1] http://appliance.randomuser.org/solutions/ [2] http://www.getnikola.com/ -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

14 36

Flashback: Fedora Docs CVS
by Pete Travis 30 Nov '13

30 Nov '13

I spent some time this afternoon playing around with the Fedora Docs CVS archive. The ambassador team is rewarding commemorative t-shirts to long-time contributors, and between the CVS logs and git logs with help from ohloh[1] I'll sort out who has been the most active over the last 10 years. The script found: 143 branches 11720 total commits 108 unique committers Top committers: 5011 pfrields 962 kwade 610 elliss 560 jtr 373 zepires 361 tombo 331 mdious 299 transif 231 bbbush 223 raven 172 fab 146 tfox 139 hyuuga 123 diegobz 118 kmilos 116 glezos 106 mwiriadi 100 warrink It represents a *massive* amount of work, and a strong foundation for our documentation today. Thanks to the Fedora Docs team of then, now, and tommorrow! [1] https://www.ohloh.net/p/8544 -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

2 2

Final release notes for Fedora 20
by Adam Williamson 29 Nov '13

29 Nov '13

Hi, folks. We have a final release requirement for the release notes: "The final branded release notes must be present on release-blocking images and the appropriately versioned generic release notes must be available in the release repository." https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Release_not… That means we need the final fedora-release-notes package to be built and submitted as an update ASAP: we're in the middle of building Final TCs ATM, and Go/No-Go is next Thursday. Next Tuesday is really the deadline to have all the stuff we need for Final built. I've filed a bug and nominated it as a release blocker to track this: https://bugzilla.redhat.com/show_bug.cgi?id=1035531 . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

3 4

F20 documentation
by Gianluca Sforna 26 Nov '13

26 Nov '13

Hi, I am looking for a list of F20 documentation I can feed the IT translation team with. I am not really sure what's ready and what will be, any pointer appreciated. Regards G. -- Gianluca Sforna http://morefedora.blogspot.com http://identi.ca/giallu - http://twitter.com/giallu

2 2

Docs Project Meeting Summary 25 Nov 2013
by Pete Travis 25 Nov '13

25 Nov '13

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:00:02 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-11-25/fedora_docs.2013… . Meeting summary --------------- * Roll Call (randomuser, 14:00:03) * release notes (randomuser, 14:05:24) * Guide Status (randomuser, 14:11:00) * Pete wants to get some content pumped into the new MultiBoot guide and get it published (randomuser, 14:11:38) * Check bugzilla for docs work, and open bugs too (randomuser, 14:16:49) * LINK: https://git.fedorahosted.org/git/docs/ARM-getting-started-guide.git (zoglesby, 14:19:53) * zoglesby needs help with the ARM-GSG (randomuser, 14:22:06) * BZ tickets (randomuser, 14:26:57) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=998327 (randomuser, 14:27:10) * the script that redirects to a given locale is broken for romanian (randomuser, 14:27:33) * LINK: http://tinyurl.com/lbrq84 (randomuser, 14:32:09) * thanks ciupicri for the patch! (randomuser, 14:38:03) * open floor discussion (randomuser, 14:41:27) Meeting ended at 14:55:19 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * randomuser (67) * jjmcd (17) * zoglesby (11) * ciupicri (8) * pbokoc (6) * pkovar (6) * sgordon (4) * zodbot (3) * yruseva (1) * pwhalen (1) -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Fedora Docs Meeting Reminder 1400UTC 25 Nov 2013
by Pete Travis 25 Nov '13

25 Nov '13

Please attend the Fedora Documentation Project's weekly meeting at 1400UTC in #fedora-meeting on freenode. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize(a)fedoraproject.org

1 0

Let's Keep Talking (Lowering the Participation Barrier)
by Christopher Antila 24 Nov '13

24 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi everybody: Since the conversation has died down a bit, I went ahead and started collecting everybody's comments on the wiki.[0] My idea for that wiki page is *just* to collect what people have already said. We should keep the discussion on the mailing list or IRC. If you'd like to help me categorize or re-phrase the points, please go ahead. If you wish to remove points, please put them in a "not important" category, to help us be clear about options we considered but did not choose. If you wish to add points that weren't in the previous email thread, please write to the mailing list first. So far, I've realized a couple of themes have emerged, with no consensus. I'm pretty impressed with the level of productive ideas being suggested, which means we should have some good energy for building better solutions! Christopher [0] https://fedoraproject.org/wiki/User:Crantila/What_up_Docs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCgAGBQJSkZqsAAoJEAWCcTQ3FNFMEFgP/j0S2t7PDq4vtWt8wpm4+Wwd vpHSouVmdZoLADisf1QyjWdjjNkd47oTstDxD7X5d2twTfGRFH7Mjn2qGIpLuNAW Nw+Yv84v/oT1Lr1w3EekqYcTYbXlpzPV7kz6gEbTgmkw4Ro8jdQ3gogNb4FiJQeO 7qc0qyGdiDtJueiUyGdKoKUSfalF3ZdIy/zSbs4uojvnBP4NSJdbzsUqGXfYrBxc y1tQrvdA8syt3Ya9igpc0hebPP3Gk+Daps9Tmw2BHVGN+mjVuVJMNDPHXoCY6JUY 0loILBOizNUwFAE+sf9r9VY94SPtWBwO0gH7W4ajelxdAkbliO4XjZVpKXLaY9wp sKnxIhsgz5j6vJld408V7yld0xn7PraP3BH7zdi5c4Q8Cv1/HecpUbCxnoiGvgo0 URdC/+swc0nooGVru57m2fSNpsqnE6PUDoCJPpUcTNlQ8npCFzFTyCpALA95XxX7 FWM8xV3lAqycE0zEA1moCQcsnvczuyM+OnWOJwKH7CgRZ2AlP98He+RwF7VMZhuc pQ3QplWr3XpRku/UT61hyFRTyZxpviMxNIp4m8HUV5ED+JZiJ3C9fU89IGgE20OD ixwjYDvzVXrtyE8XvyzqcaC9nEVc+4fkpiZb443DNiuHFa0v7NtLCgqfb6VlISEA KcO33ZwDAKv9/ENFcFDB =xsbO -----END PGP SIGNATURE-----

1 0

Re: Lowering the participation barrier for Fedora Docs
by Edith Rivero 19 Nov '13

19 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone: On Mon, Nov 18, 2013 at 5:21 PM, Chris Murphy <lists(a)colorremedies.com> wrote: > - - I'm used to being ruthless when editing other people's work, and unoffended when I get back work a majority of which has been marked up for edits. I don't know if that's a possible barrier (real or imagined). I support Chris Murphy's opinnion. Because as a new contributor i find important receive answers/feedback even if they ask for rewrite a huge amount of work done with the objective of good results in documentation. Something i really found encouraging was when i received an e-mail from Jaromir Hradilek (thank you!) to be a contributor. That made me feel confident and responsible to understand tools. Then I have worked in bugs (yet, simple ones) and send docummentation to solve them. But it would be very rewarding if i received feedback form owners about what i did, even this feedback requires lots of corrections. I am working to add some content through git, i am not sure if that will help, i hope so. Regards, Edith Rivero -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQEcBAEBAgAGBQJSi9IMAAoJEGdLNCCu0KPvP8MH/jZqJkzboA192BpNqkg1V1PT zTu6S62mPj9WyuNEqbmEJ8SrTU+BGjw2eTDY/UQ+wHzJCndxUoDy0R323EikSvy4 +FvE8kdp1+u/apSSXwv4ILf5VX4goy5XpnIKl3Y7fMcxc0W+2JTMPVqDeU56p8NC i+6c/9Cee3xdG8+pH6Bk+0lI53Scs5fNixDcDF1f/nihvgOdazOAD+G7sr7LicsM W8CALFhJuQJ7s0XVnWEVgEsCFD6CVebEkLjcbIvfYXZw7M69QgoPM6P3oWKgn2tp q5LjLyjIQAJj65il+p7Na6UzVRMzYRsTc5vc/zfJkYhwjUPxzuAffP/aAdGLlwU= =5Ba7 -----END PGP SIGNATURE-----

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs November 2013