Document-Driven Development: Plone Ansible Playbook

--===============8694820245079642137==
Content-Type: multipart/alternative; boundary=20cf303a337d27c37f05035a4966

--20cf303a337d27c37f05035a4966
Content-Type: text/plain; charset=UTF-8

Hi All,

I've opened a new repo https://github.com/plone/ansible-playbook that
currently contains nothing but a first draft of documentation for a
forthcoming Plone Ansible Playbook.

Please, please, please contribute by discussing and/or editing and writing.
I'm trying to use this document to work through the most fundamental
questions about how this facility should look *before* we write much code.

The doc is just a big README at the moment. Don't worry yet about breaking
it up or getting it into good Sphinx format. Instead, think about it and
contribute. We'll refactor later.

Instead, think about questions like:

What tools should be in the stack?

How do we want to encourage customization?

How will be handle versioning and branching going forward?

I'd love for us to get this into shape by the conference so that we can
talk about it, sell it, and incite sprinters with the doc(s) serving as our
story.

Let fly!

Steve

--20cf303a337d27c37f05035a4966
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi All,<div><br></div><div>I&#39;ve opened a new repo=C2=
=A0<a href=3D"https://github.com/plone/ansible-playbook">https://github.com=
/plone/ansible-playbook</a> that currently contains nothing but a first dra=
ft of documentation for a forthcoming Plone Ansible Playbook.</div><div><br=
></div><div>Please, please, please contribute by discussing and/or editing =
and writing. I&#39;m trying to use this document to work through the most f=
undamental questions about how this facility should look *before* we write =
much code.</div><div><br></div><div>The doc is just a big README at the mom=
ent. Don&#39;t worry yet about breaking it up or getting it into good Sphin=
x format. Instead, think about it and contribute. We&#39;ll refactor later.=
</div><div><br></div><div>Instead, think about questions like:</div><div><b=
r></div><div>What tools should be in the stack?</div><div><br></div><div>Ho=
w do we want to encourage customization?</div><div><br></div><div>How will =
be handle versioning and branching going forward?</div><div><br></div><div>=
I&#39;d love for us to get this into shape by the conference so that we can=
 talk about it, sell it, and incite sprinters with the doc(s) serving as ou=
r story.</div><div><br></div><div>Let fly!</div><div><br></div><div>Steve</=
div></div>

--20cf303a337d27c37f05035a4966--


--===============8694820245079642137==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
--===============8694820245079642137==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plone-installers mailing list
Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-installers

--===============8694820245079642137==--