Scripting guidelines

[David Caro]

El vie 21 feb 2014 14:17:12 CET, Dave Neary escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I'll reply to Allon's email separately, but...
>
> On 02/21/2014 11:01 AM, David Caro wrote:
>> From the company you work for, and a pretty old and active
>> participation on open source projects, Dave (cc'd) seems to
>> disagree with your view of open source management:
>>
>> https://opensource.com/business/11/2/leadership-open-source-communities
>
>
> Leadership
>>
> in open source communities
> Posted 8 Feb 2011 by David Nalley
>
> (so, not me) :-)

Sorry for the confusion, you know, if the first and the last letters 
are the same, you can read whatever you think it should say...

http://www.ecenglish.com/learnenglish/lessons/can-you-read


>
>> """ So how are open source communities led? Largely by the people
>> doing the work. Most groups have a loosely defined common goal
>> (build software widgets, or develop a awesome, open source,
>> computer-based fourth grade math curriculum), and decisions are
>> made by the people doing the work. There's no manager in place
>> dictating edicts about how things must be done or what objectives
>> to seek after. Many people object to this method, call it anarchy,
>> and claim that it impedes progress. It's true that if the same set
>> of people was coerced into a single direction, they might make more
>> progress, but there likely wouldn't be the same level of
>> innovation. """
>
> I do agree with this.
>
> However: people will look to a leader to figure out what should be
> done, in what priority, and who has the authority to give access to
> things required to get stuff done. In the absence of an existing
> hierarchy, you quickly end up in gridlock. The loosely defined common
> goal is important.
>
> Let's take patches as an example. Anyone can write code to implement a
> feature, fix a bug, whatever - but someone needs to merge the patches,
> bundle up a release, exercise some level of discretion, and give some
> guidance as to whether contributed patches will be accepted or not by
> setting a direction.
>
> I don't think that a strict hierarchy is needed. But seeding the group
> with the people doing the work is important. And that's what we've
> done, I think - clearly, David, Eyal, Ewoud, Rydekull, Kiril, quaid
> and myself have the knowledge and do the work (with different levels
> of skills and knowledge for different pieces of the infrastructure),
> and get to say who gets access to resources and whether contributions
> come up to our standards or not.

So let's keep the original subject, scripting style guide.

Until now, the only modification that I've read (and we agreed) is:

 - Dan: Use the '-e' switch whenever possible (make the script fail 
when a compound command fails).
   false || true -> this does not fail because the last executed 
command in the composite returns 0
   fase -> this fails because the last executed command in the 
composite returns != 0

I've opened an etherpad with the suggestions:
   http://etherpad.ovirt.org/p/bash-style-guide

>
> Cheers,
> Dave.
>
>
>>> As for infra, it is not part of anything we distribute so it is
>>> not that important, however, standards compliance is something
>>> that should be considered.
>>>
>>>>
>>>>
>>>> [1] http://www.ovirt.org/Bash_style_guide
>>>>
>>>> Cheers!
>>>>
>>>> -- David Caro
>>>>
>>>> Red Hat S.L. Continuous Integration Engineer - EMEA ENG
>>>> Virtualization R&D
>>>>
>>>> Email: dcaro at redhat.com Web: www.redhat.com RHT Global #:
>>>> 82-62605
>>>>
>>>>
>>>> _______________________________________________ Infra mailing
>>>> list Infra at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/infra
>>>>
>>
>>
>
> - --
> Dave Neary - Community Action and Impact
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTB1HYAAoJECd1qeknDCgg9mQH/Rue01YltsL676/DcJJLhosv
> YotA4xY7MDtwf8zmpF0xZP30Jj6HH7a9WFE7VxU72iMcavaQ/6SGoMp0erTreWxM
> ovAHiaFgnkn8/EtnA8yoUr3yGU+hATyUCIsSOeOr3mOmXC8+ehgR/Esibk+DKPQ0
> qUOgW61QArR0RVNN3KVgakhsZ2hSm+YrIJCi6FZfL6Li8aWzZVYkkfWgI/I52zd8
> C3XTJ0y93UgZKAroPDUiKi+tP3zAxldqYbPgq1B7hfxnPxxeFSibmj/fi+U1wkLU
> FrIle3qOhFqCl9s/X0TtG/FBvwuhjWkIUaaD9DWfSFp/aoPt6LcdLo2/Mvp6xZ8=
> =2HB5
> -----END PGP SIGNATURE-----



--
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20140221/f06af546/attachment.sig>