<div dir="ltr">+1 to Josh's comment about contract editors for flexibility in expertise and project size, rather than commit to FTE at this point.<div><br></div><div>There appears to be broad community acceptance of the concept, so next steps would be.....</div><div><br></div><div>1.  Project leaders in need of support today, or by early 1st Qtr 2016, <u>should draft up a 1 page summary of 'need',</u> defining any specific editing skills, the length of time the person might be needed, and the list of anticipated outputs......Create document A, Edit & update document B, etc.</div><div><br></div><div>2.  I'm open to 'how' we connect job need with freelance editors.</div><div>---  OWASP culture supports Project leaders reaching out directly to contractors to select the 'best fit' for their project.</div><div>---  Elance is a reasonable solution too.</div><div>---  We can also allocate a portion of Claudia's time as Project Coordinator to help coordinate finding contractors to fit project needs.</div><div><br></div><div>3.  The Foundation will need to have the contractors sign off on some basic contractor agreement for payment and deliverables, so once a contractor is identified, let us know so we can help finish 'the paperwork'.</div><div><br></div><div>4.  Funding - As always, Project level budgets get used first, then if the need is more than a project has budgeted, Project leader can make the request for the additional funding.  As Josh mentioned, funds are available.</div><div><br></div><div>My suggestions to move this issue toward some actionable next steps.</div><div>Paul</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Best Regards, Paul Ritchie</div><div>OWASP Executive Director</div><div><a href="mailto:paul.ritchie@owasp.org" target="_blank">paul.ritchie@owasp.org</a></div><div><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Nov 9, 2015 at 1:46 PM, Josh Sokol <span dir="ltr"><<a href="mailto:josh.sokol@owasp.org" target="_blank">josh.sokol@owasp.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Going back to Simon's original request, I think that he had the right idea.  Projects that have funds should absolutely feel free to hire a contract technical editor to help with these things.  For projects that don't have funds, in January you'll have $500, and can certainly use that for this purpose.  There are also still pools of money that could be used for it.  As for hiring a FTE to do this, I'm not sure that's warranted.  As the charity is moving over $1m/yr in revenue, we need to be conscious of how much money is spent on overhead vs on the mission.  FTE's are typically viewed as overhead to support, while a contractor would be directly supporting an initiative.  A small difference, but a difference nonetheless where reporting is concerned.  I would like to see us follow Paul's guidance here in establishing the need and quality before considering hiring somebody as a FTE.<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888">~josh<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 9, 2015 at 1:50 PM, Bill Sempf <span dir="ltr"><<a href="mailto:bill@pointweb.net" target="_blank">bill@pointweb.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey, everyone, I have a large number of freelance technical writer/editor resources from my writing with Wiley.  I can reach out and get a list of people we can bring in who are known entities.<span><font color="#888888"><div><br></div><div>S</div><div><br></div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 9, 2015 at 2:26 PM, johanna curiel curiel <span dir="ltr"><<a href="mailto:johanna.curiel@owasp.org" target="_blank">johanna.curiel@owasp.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dinis Idea is great. I think hiring contracting through Elance is a good way to experiment without much risk<div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 9, 2015 at 1:20 PM, Jim Manico <span dir="ltr"><<a href="mailto:jim.manico@owasp.org" target="_blank">jim.manico@owasp.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Sounds reasonable so we can pull from different sets of
    expertise....<div><div><br>
    <br>
    <div>On 11/9/15 7:09 AM, Dinis Cruz wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">I agree that this is a very important resource, and
        maybe instead of hiring a FTE, why don't we make a budget
        available for this, and then allow the leaders to allocate it
        using 'blocks of time contracts' 
        <div><br>
        </div>
        <div>The actual contract could/should be managed by OWASP's FTE
          (or something like elance) and in practice OWASP would be
          contracting 5/10/20 days of technical editing from N
          contractors (located anywhere in the world)</div>
        <div><br>
        </div>
        <div>This will most likely be better than one FTE dedicated as
          technical author (since we would be able to hire based on
          technical knowledge and focus)</div>
        <div><br>
        </div>
        <div>Dinis</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On 9 November 2015 at 16:56, Jim Manico
          <span dir="ltr"><<a href="mailto:jim.manico@owasp.org" target="_blank">jim.manico@owasp.org</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> Johanna,<br>
              <br>
              I've been thinking about this hire quite a bit. I agree
              with you, Simon and several other project leaders who have
              echoed this request. It seems like a solid hire request
              (in some form or fashion) that would serve the foundation
              in several regards. I get the feeling we could keep a
              technical writer busy full time year round. <br>
              <br>
              I'd also like to see some technical resources enhance the
              wiki, especially around editorial controls, but I think we
              could make that happen with a contractor.<br>
              <br>
              At the end of the day, this is Paul's call, but these
              suggestions certainly help. :)<br>
              <br>
              Aloha,<br>
              Jim
              <div>
                <div><br>
                  <br>
                  <br>
                  <div>On 11/8/15 5:29 AM, johanna curiel curiel wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">Hi All
                      <div><br>
                      </div>
                      <div>I think we need a Technical Editor to help us
                        clean up the text and a Wiki admin content
                        manager, someone responsible for organising the
                        content</div>
                      <div>The Wiki Content Manager can work on how to
                        structure the Wiki and apply a process similar
                        to the Mozilla wiki for reviewing and publishing
                        content</div>
                      <div>I think we need to be realistic that a Wiki
                        Content manager will not be able to 'know' how
                        to structure Security content if himself is not
                        familiar with the content</div>
                      <div><br>
                      </div>
                      <div>I think a Technical Editor will help shape
                        the actual content and we should apply he rule
                        'divide and conquer'</div>
                      <div><br>
                      </div>
                      <div>Begin helping first some projects like ZAP,
                        then it can move on to other tasks but these
                        ones should be organised in a project ,
                        prioritising the content that needs to be
                        reviewed and organised first.</div>
                      <div><br>
                      </div>
                      <div>Regards</div>
                      <div><br>
                      </div>
                      <div>Johanna</div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">On Fri, Nov 6, 2015 at
                        12:42 PM, Jim Manico <span dir="ltr"><<a href="mailto:jim.manico@owasp.org" target="_blank"></a><a href="mailto:jim.manico@owasp.org" target="_blank">jim.manico@owasp.org</a>></span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree with you
                          1000%, Tim.<br>
                          <br>
                          I am trying to encourage OWASP to hire someone
                          full time to own the wiki from a technical and
                          editorial point of view. We do not even have
                          the wiki community editorial features turned
                          on, which is one of the main benefits of a
                          real wiki...<br>
                          <br>
                          I'm trying, Tim.<br>
                          <br>
                          Aloha,<br>
                          Jim<br>
                          <br>
                          <br>
                          On 11/6/15 6:40 AM, Tim wrote:<br>
                          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I think this
                            is an excellent idea.  Certainly some
                            projects need the<br>
                            documentation help, but I'd be particularly
                            interested in seeing this<br>
                            applied to the wiki.  Lots of areas can be
                            improved.  Far too many<br>
                            technical topics in the wiki are out of date
                            or disorganized to the<br>
                            point where I (as a pentester) don't feel
                            good about pointing my<br>
                            clients to them.  But as Paul mentions, a
                            conservative step-by-step<br>
                            approach is prudent.<br>
                            <br>
                            tim
                            <div>
                              <div><br>
                                <br>
                                <br>
                                On Fri, Nov 06, 2015 at 08:30:37AM
                                -0800, Paul Ritchie wrote:<br>
                              </div>
                            </div>
                            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                              <div>
                                <div> Hello Simon Jim, All:<br>
                                  <br>
                                  Re:  technical author working on a
                                  load of ZAP documentation.<br>
                                  <br>
                                  +1 on my side.  I would like to see
                                  this proceed with some 'first-hand'<br>
                                  recommendations from the Community on
                                  'contract authors' who have been<br>
                                  efficient & successful on past
                                  projects.<br>
                                  I'd also like to see the search look
                                  on a Global Scale to help reduce
                                  costs.<br>
                                  <br>
                                  At this moment, I would not be
                                  supportive of a FT person until we see<br>
                                  enough work for FT, and the
                                  quality/consistency of the contractors
                                  output.<br>
                                  <br>
                                  Paul<br>
                                  <br>
                                  Best Regards, Paul Ritchie<br>
                                  OWASP Executive Director<br>
                                  <a href="mailto:paul.ritchie@owasp.org" target="_blank">paul.ritchie@owasp.org</a><br>
                                  <br>
                                  <br>
                                  On Fri, Nov 6, 2015 at 7:57 AM, Jim
                                  Manico <<a href="mailto:jim.manico@owasp.org" target="_blank">jim.manico@owasp.org</a>>

                                  wrote:<br>
                                  <br>
                                </div>
                              </div>
                              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                                <div>
                                  <div> Simon,<br>
                                    <br>
                                    Your request is duly noted, Simon.<br>
                                    <br>
                                    What a great time to bring this up
                                    as we are going to be discussing
                                    2016<br>
                                    budgeting soon.<br>
                                    <br>
                                    Give me a few weeks but I'll keep
                                    you updated on the progress of this<br>
                                    request.<br>
                                    <br>
                                    I get the feeling that between the
                                    wiki and a few projects alone, we
                                    could<br>
                                    keep more than one technical writer
                                    busy full time....<br>
                                    <br>
                                    Aloha,<br>
                                    <br>
                                    --<br>
                                    Jim Manico<br>
                                    Global Board Member<br>
                                  </div>
                                </div>
                                OWASP Foundationhttps://<a href="http://www.owasp.org" rel="noreferrer" target="_blank"></a><a href="http://www.owasp.org" target="_blank">www.owasp.org</a><span><br>
                                  <br>
                                  <br>
                                  <br>
                                  <br>
                                  On 11/6/15 12:14 AM, psiinon wrote:<br>
                                  <br>
                                  We could _really_ do with a technical
                                  author working on a load of ZAP<br>
                                  documentation.<br>
                                  Does anyone have any recommendations
                                  for someone we could employ (we have<br>
                                  some funds)?<br>
                                  <br>
                                  Are any other projects interested in
                                  doing something similar?<br>
                                  Could OWASP employ a technical author
                                  (full time/part time/contract) and<br>
                                  them make them available to projects
                                  (possibly for a discounted fee)?<br>
                                  I suspect we could keep one pretty
                                  busy between us...<br>
                                  <br>
                                  Cheers,<br>
                                  <br>
                                  Simon<br>
                                  <br>
                                  --<br>
                                </span> OWASP ZAP <<a href="https://www.owasp.org/index.php/ZAP" rel="noreferrer" target="_blank"></a><a href="https://www.owasp.org/index.php/ZAP" target="_blank">https://www.owasp.org/index.php/ZAP</a>>

                                Project leader<br>
                                <br>
                                <br>
_______________________________________________<br>
                                OWASP-Leaders mailing <a href="mailto:listOWASP-Leaders@lists.owasp.orghttps://" target="_blank"></a><a href="mailto:listOWASP-Leaders@lists.owasp.orghttps://" target="_blank">listOWASP-Leaders@lists.owasp.orghttps://</a><a href="http://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">lists.owasp.org/mailman/listinfo/owasp-leaders</a><span><br>
                                  <br>
                                  <br>
                                  <br>
_______________________________________________<br>
                                  OWASP-Leaders mailing list<br>
                                  <a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
                                  <a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
                                  <br>
                                  <br>
                                </span></blockquote>
                              <span>
                                _______________________________________________<br>
                                OWASP-Leaders mailing list<br>
                                <a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
                                <a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
                              </span></blockquote>
                          </blockquote>
                          <br>
                          <span> -- <br>
                            Jim Manico<br>
                            Global Board Member<br>
                            OWASP Foundation<br>
                            <a href="https://www.owasp.org" rel="noreferrer" target="_blank">https://www.owasp.org</a><br>
                            <br>
                          </span>
                          <div>
                            <div>
                              _______________________________________________<br>
                              OWASP-Leaders mailing list<br>
                              <a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
                              <a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
                            </div>
                          </div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                  <pre cols="72">-- 
Jim Manico
Global Board Member
OWASP Foundation
<a href="https://www.owasp.org" target="_blank">https://www.owasp.org</a></pre>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            OWASP-Leaders mailing list<br>
            <a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
            <a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre cols="72">-- 
Jim Manico
Global Board Member
OWASP Foundation
<a href="https://www.owasp.org" target="_blank">https://www.owasp.org</a></pre>
  </div></div></div>

</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OWASP-Leaders mailing list<br>
<a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
<a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OWASP-Leaders mailing list<br>
<a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
<a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OWASP-Leaders mailing list<br>
<a href="mailto:OWASP-Leaders@lists.owasp.org">OWASP-Leaders@lists.owasp.org</a><br>
<a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" rel="noreferrer" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><br>
<br></blockquote></div><br></div>