Open Stack

I found at least one instance and I think maybe two as we've been convertingthe HA Guide to RST.  We're doing minor edits as we convert and these involvedhideous sentences that a reviewer called out as needing to be rewritten.  I happenedto be checking Wikipaedia for something else and there was exactly the same hideouslybad sentence ;-)
I would like to think that Stackers had the common decency to only plageurize good stuff ;-)
I defer to others to determine the right way to handle this, but I suspect we may have a fairamount of plageurized material in the guides.  Or, who knows?  Maybe someone plageurizedthe OpenStack docs when writing the Wikipedia articles...
meg

 
      From: Lana Brindley <openstack at lanabrindley.com>
 To: openstack-docs at lists.openstack.org 
 Sent: Sunday, July 12, 2015 6:27 PM
 Subject: Re: [OpenStack-docs] Copying from wikipedia ;(
   
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 13/07/15 10:54, Anita Kuno wrote:
> On 07/12/2015 08:34 PM, Jeremy Stanley wrote:
>> On 2015-07-12 14:50:32 +0200 (+0200), Andreas Jaeger wrote:
>> [...]
>>> Jeremy, I'm just wondering whether we should add a line to the infra manual
>>> (
>>> http://docs.openstack.org/infra/manual/developers.html#sign-the-appropriate-individual-contributor-license-agreement)
>>> stating what the CLA is about.
>>
>> That's probably okay, though summarizing legal documents is tricky
>> business (lawyers generally tell you that if the explanation of a
>> legal document is shorter than the document itself, then either it's
>> an insufficient explanation or the legal document being explained is
>> poorly-written).
>>
> 
> I'm actually finding that the time taken to inform people how to use
> common sense is an increasing contributor anti-pattern, not just to
> documentation.
> 
> I'm not offering an opinion about what-is-to-be-done, I'm saying that
> needed to do anything about behaviour which is in direct contravention
> of standard open source behaviour is really draining on our community as
> a whole.

I agree with you Anita, and that's why I'm happy with just calling out
the behaviour, mentioning it directly to the individual, and then
getting on with our lives. This doesn't happen often enough (at least,
that we know of) for us to make any significant changes. I'm happy with
a one line "don't plagiarise!" to cover this base.

L

- -- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVoxQbAAoJELppzVb4+KUynP8IAKhK1O3k3JqqOBU86hLuZmH1
KCg2KO7LNMJ2rZi/8xnSglBjX6kFRHePkP+En7LJ0QDnn5zVHabKO8O7r0nemLsz
SLAtquNQtiR0B9X2KA6rLXeGZvNQ7KN6UANJ64m1+SUprHwbL8fWwxS5A+iy6DYk
T9C/57phPDY8mB3Cri0D3JFE084bG/oyZX8hUo2LUlDuVYgJqbCVa5P1o+tdbQjZ
TV3BzBwoS4H86wgzTWNgbWu0Nv2doO7uby/ruNGwdowWV/ALbkz5gK7hnaIZSMfe
Y9MQByQyEsC9mVdSMa2WRQ0gCs/Z3zhmLlQ50s17OHSkHJkZaHiD1x3f+7/PzQo=
=4cfE
-----END PGP SIGNATURE-----



_______________________________________________
OpenStack-docs mailing list
OpenStack-docs at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150713/ab775c4c/attachment-0001.html>