Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think those kinds of questions couldn't really be asked until (if)
we find a suitable chunk of code that's capable of handling it.

L

On 13/07/15 22:41, Matt Kassawara wrote:
> Also, how do we handle false-positives? Non-voting job?
> 
> On Sun, Jul 12, 2015 at 10:10 PM, Lana Brindley
> <openstack at lanabrindley.com> wrote:
> 
> So, I just had a chat to Josh Hesketh (Infra core), who seems to
> think that if some kind of open source code for checking against an
> English corpus already existed (which it may do, most universities
> do something like this for assignment submissions), then creating
> the Jenkins job would be OK. The tricky part, of course, is
> creating and maintaining the index to be searched against.
> 
> Food for thought :)
> 
> L
> 
> On 13/07/15 13:47, Olga Gusarenko wrote:
>>>> Hi to all!
>>>> 
>>>> Besides autocheck for the text uniqueness, I believe we
>>>> should cover the matter for the contributors. What if I add
>>>> licensing and copywriting as a seperate section of the
>>>> Contributor guide spec? 13 июля 2015 г. 6:15 пользователь
>>>> "Lana Brindley" < openstack at lanabrindley.com> написал:
>>>> 
>>>> Hrm, I wonder how easy it would be to automate a check for
>>>> this? I might go poke an Infra person.
>>>> 
>>>> L
>>>> 
>>>> On 13/07/15 13:13, Meg McRoberts wrote:
>>>>>>> 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 ;(
>>>>>>> 
>>>>>>> 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
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________ 
>>>>>>> OpenStack-docs mailing list 
>>>>>>> OpenStack-docs at lists.openstack.org 
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>>
>>>>>
>>>>>>> 
_______________________________________________
>>>>> OpenStack-docs mailing list 
>>>>> OpenStack-docs at lists.openstack.org 
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>>
>>>>
>
>>>>> 
>> 
>> _______________________________________________ OpenStack-docs
>> mailing list OpenStack-docs at lists.openstack.org 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>> 
- -- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVpCYWAAoJELppzVb4+KUyZEgIAMvDafbJxoiapMtCypnJPKN5
BMvP496RFHcqfmS4gkqCiTvPydyePjkHhogcbINtzT943cHqb9Mi31clwv4MLHw7
5HY23q8z7mCJR1PxL/OIVCMSmrqCLIR9U8s+XYjgRy1+MNw9LWARAhGZorqVWipu
6eYCDFrmUzMRVewXTPBxMN8umrf0Xn4k+Ig5vWuvZQgm/3In3/Zt+C7jL+VlrY11
FLkhm5yuZzkLDOrmhMhVgbu32Ri9U5V7YMoSSFThOXlb/ixv/uLEJZkEfeYG9M4U
6ua8XnaqGsCmx2sHkhuTIvkaoyzxC7i4u1qUyzpLLCfR+Wrr9FRx7/66N5xhctg=
=L76f
-----END PGP SIGNATURE-----