<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>956</bug_id>
          
          <creation_ts>2011-04-06 08:37:56 +0000</creation_ts>
          <short_desc>Need updated doc publishing process in Makefiles and Yocto Project website</short_desc>
          <delta_ts>2011-05-13 10:50:24 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>9</classification_id>
          <classification>Documentation</classification>
          <product>Quick Start</product>
          <component>quick-start</component>
          <version>1.0</version>
          <rep_platform>Other</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>Patch pending integration (5-May-2011)</status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>1.0 PointRelease</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Scott Rifenbark">srifenbark</reporter>
          <assigned_to name="Saul Wold">sgw</assigned_to>
          <cc>david.c.stewart</cc>
    
    <cc>elizabeth.flanagan</cc>
    
    <cc>jefro</cc>
    
    <cc>julie.n.fleischer</cc>
    
    <cc>poky.doc.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>13141</commentid>
    <comment_count>0</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-04-06 08:37:56 +0000</bug_when>
    <thetext>Currently our Makefile structure attempts to publish to 
&apos;o-hand.com:/srv/www.pokylinux.org/doc/&apos;.  This doesn&apos;t work and we should 
be pushing to http://yoctoproject.org/docs into the appropriate manual 
directory.  We need to set up the Makefiles with the right URL and have the right permissions going on so that whenever a manual is &quot;made&quot; the HTML version and PDF versions automatically get published to our Yocto Project website doc structure.  This process will make sure the manuals in the website always have the latest information.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13381</commentid>
    <comment_count>1</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-04-22 05:35:54 +0000</bug_when>
    <thetext>Need engineering or IT support to be able to get this going.  Unless I am missing something here the solution seems pretty simple.  Just need some permissions to publish stuff into the drupal site hosting the yocto website.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13386</commentid>
    <comment_count>2</comment_count>
    <who name="Jeff Osier-Mixon">jefro</who>
    <bug_when>2011-04-22 09:10:36 +0000</bug_when>
    <thetext>Hi Scott - Mike may be able to set this up.  I&apos;m assuming the needed permissions are just for you, not for everyone, right?

I had a question, though, about whether it is a good idea to autopublish on every make.  Is there a process to vet the docs before publishing?  In past projects I have set up &quot;make install&quot; to publish the docs, but running &quot;make&quot; just builds locally. Maybe I am misunderstanding the process.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13387</commentid>
    <comment_count>3</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-04-22 09:13:31 +0000</bug_when>
    <thetext>I don&apos;t know who the permissions are required for... This is the part I am unfamiliar with.  I would assume that would work though.  

Regarding publishing on every make I don&apos;t see a problem with that as that would make sure the docs on the website are always most recent.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13388</commentid>
    <comment_count>4</comment_count>
    <who name="Jeff Osier-Mixon">jefro</who>
    <bug_when>2011-04-22 09:29:35 +0000</bug_when>
    <thetext>I&apos;m still not sure I understand. Every time someone downloads poky and builds it, they publish documentation to the main website? That opens up security concerns in addition to quality concerns.

I would strongly recommend changing the Makefile to require a second step to publish documentation to the main site, and some vetting process. I love transparency and community inclusion, but there has to be some gatekeeping process. Imagine if everyone who downloaded and built the Linux kernel also posted it to kernel.org every time they typed &quot;make&quot;.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13390</commentid>
    <comment_count>5</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-04-22 09:45:03 +0000</bug_when>
    <thetext>Good point... I did not think of the world working on the docs.  I was lost in my little closed process of my own.  Maybe I should talk to you and we can think this thing out a bit....</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13391</commentid>
    <comment_count>6</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-04-22 10:17:03 +0000</bug_when>
    <thetext>To fix this bug we will remove the publish option from all the documentation make files.  these were publishing to o-hand and were broke anyway.  then we will create a local script that can be executed to push the most recent HTML documentation files to the Yocto Project website.  The local script can be run at our convenience when we are satisfied with the quality of community patches and internal work regarding the docs.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13429</commentid>
    <comment_count>7</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-04-26 09:46:41 +0000</bug_when>
    <thetext>After further discussion with RP it appears that we do not need a separate local script to publish or push the HTML files to the Yocto Project website.  Evidently the ssh key can be used to restrict access to the website.  So, the fix for this bug will be making sure the ssh key and permissions are set up correctly and then changing the publish statements in each document&apos;s make file.  They currently attempt to publish to o-hand.  I am waiting on RP&apos;s assistance to complete this bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13599</commentid>
    <comment_count>8</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-05-05 09:27:00 +0000</bug_when>
    <thetext>Saul and Beth to work with ScottR to get the permissions on the server and the ssh key stuff straightened out and working.  ScottR to make changes to the Makefiles for the manuals.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13613</commentid>
    <comment_count>9</comment_count>
    <who name="Beth Flanagan">elizabeth.flanagan</who>
    <bug_when>2011-05-06 08:48:54 +0000</bug_when>
    <thetext>A few things we need to discuss here, Scott.

1. Switching the URL/giving you access can happen today. I&apos;ll ping you on IRC
2. That said, the doc publishing has some process issues:
   - We have no history wrt doc publishing. So, for example, we can&apos;t go back to, say, laverne docs. Going forward, this needs to be fixed.

We should have something like:

www.yoctoproject.org/documentation/1.0/&lt;docname&gt;
www.yoctoproject.org/documentation/current/&lt;docname&gt; (symlink to most recent documentation)

This will allow us to have docs that support prior releases.

   - We&apos;re really talking about two release processes here. You need the ability to update documentation that exists, should a bug be found (like a bug in bernard documentation, for example). You also need the ability to release new documentation (like 1.1). This is fairly easy to accomplish and should be brought into the release process. Let&apos;s talk about this. I&apos;ve put a feature on the 1.1 list to bring this into the release process.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13623</commentid>
    <comment_count>10</comment_count>
    <who name="Beth Flanagan">elizabeth.flanagan</who>
    <bug_when>2011-05-06 16:07:32 +0000</bug_when>
    <thetext>I&apos;ve got the server side of this fixed for the time being. However this should be an rsync, not an scp.

A good portion of the publishing functionality should be brought into the release process. I&apos;m going to open another bug on this to track that portion.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13626</commentid>
    <comment_count>11</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-05-06 16:18:52 +0000</bug_when>
    <thetext>I have the Makefile issues worked out and two of the five manuals are working with the changes pushed to yocto-docs.  I will close on this when the other three manuals are good.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13645</commentid>
    <comment_count>12</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2011-05-09 11:37:05 +0000</bug_when>
    <thetext>All changes have been committed and pushed to the yocto-docs repo to satisfy this bug.  The publish process for all five YP manuals now works so that when I run it the HTML and PDF versions of the manuals (along with related style sheets and PNG files) are pushed to the Yocto Project website into the appropriate documentation folder structure.  Once the yocto-docs repo is merged with the poky repo by Saul or RP the bug can be closed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13782</commentid>
    <comment_count>13</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2011-05-13 10:15:11 +0000</bug_when>
    <thetext>http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=92690ef3cca0575fc84819129306b913c7e995df

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f55fec8703a18b56e7ba7f75b90c9f5b276016f3

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f7b1705ef38212dd59a568b4afaca56c2402d825</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13793</commentid>
    <comment_count>14</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2011-05-13 10:50:24 +0000</bug_when>
    <thetext>
Bernard:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=36c91352155617cc6ee3a975b3ced5fb026d1e3b

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=437950723f7bd0d18e4fdf46d4c678a086ccd361
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=5f92b6262f5d902b4212258f0291fe065e534474


http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=65d61e2d113d70acf0c351aadbdd65b6b0e59bb4</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>