Received: by 10.100.76.4 with SMTP id y4mr2520254ana.21.1335450079845;
        Thu, 26 Apr 2012 07:21:19 -0700 (PDT)
X-BeenThere: lazarus-br@googlegroups.com
Received: by 10.101.201.10 with SMTP id d10ls221468anq.1.gmail; Thu, 26 Apr
 2012 07:21:19 -0700 (PDT)
Received: by 10.101.112.3 with SMTP id p3mr2632838anm.0.1335450079280;
        Thu, 26 Apr 2012 07:21:19 -0700 (PDT)
Received: by 10.101.112.3 with SMTP id p3mr2632837anm.0.1335450079264;
        Thu, 26 Apr 2012 07:21:19 -0700 (PDT)
Return-Path: <dgasp...@gmail.com>
Received: from mail-gy0-f173.google.com (mail-gy0-f173.google.com [209.85.160.173])
        by gmr-mx.google.com with ESMTPS id j51si3236370yhi.1.2012.04.26.07.21.19
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 26 Apr 2012 07:21:19 -0700 (PDT)
Received-SPF: pass (google.com: domain of dgasp...@gmail.com designates 209.85.160.173 as permitted sender) client-ip=209.85.160.173;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dgasp...@gmail.com designates 209.85.160.173 as permitted sender) smtp.mail=dgasp...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-gy0-f173.google.com with SMTP id r14so1094442ghr.32
        for <lazarus-br@googlegroups.com>; Thu, 26 Apr 2012 07:21:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        bh=cKz3Ri8+PAGtNyqTZcH1xD6Fqv6ppdSJYB+W6HAsXRk=;
        b=VcuGzRPUXvvK72/MRXq5sSnnf/xfIHOcD+IwWguLHjTJGMD+SB50md9oW98ecIHCj2
         bd0IhE5ad2xHroLJTZ2RJROLa12iw3emULPJqW/Y3fb/pNk4hQ1TZmsHDUBgsX1vvgDq
         StDYA8hTkNzYbN44SdByYYpmKElhtnF3fSZ79GfXH6gN8mfhakRGPElqVO222mywx1Qi
         WtXgjVwW5SuWkmqKF9grSIjPChkHzdSY/DqGZsDWYB2qz/yEESQqp7mElb+ycyLhLVf/
         LHXW3sXv2MXZ4PZ5kaNtiZXj5kpYwpGyxetwi/SsQ6LHKWqPkrwCcr416YbWSKm3FhIK
         lr9A==
MIME-Version: 1.0
Received: by 10.236.175.41 with SMTP id y29mr6780046yhl.60.1335450079192; Thu,
 26 Apr 2012 07:21:19 -0700 (PDT)
Received: by 10.147.56.15 with HTTP; Thu, 26 Apr 2012 07:21:19 -0700 (PDT)
In-Reply-To: <32801303.758.1335441507329.JavaMail.geo-discussion-forums@vbqq1>
References: <32801303.758.1335441507329.JavaMail.geo-discussion-forums@vbqq1>
Date: Thu, 26 Apr 2012 11:21:19 -0300
Message-ID: <CAALDFzJe1rzANR+oWN9pvQpw+5Y1BXDLmL4eRVLAtX2nsx=...@mail.gmail.com>
Subject: =?ISO-8859-1?Q?Re=3A_=5Blazarus=2Dbr=5D_Desenvolvimento_em_Equipe_=2D_Como_ev?=
	=?ISO-8859-1?Q?itar_roubo_do_c=F3digo_fonte=3F?=
From: Daniel Gaspary <dgasp...@gmail.com>
To: lazarus-br@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2012/4/26 Renato Ricci <renatori...@singlesoftware.com.br>:
> Ol=E1 amigos..
>
> Estou desenvolvendo um sistema de gest=E3o e minha ideia =E9 futuramente =
ter
> mais pessoas envolvidas diretamente com o desenvolvimento do sistema.
> Gostaria de saber quais as melhores pr=E1ticas que se pode adotar para se
> evitar que o c=F3digo fonte do sistema seja furtado por um programador de=
 m=E1
> f=E9 dentro da equipe.

Evitar mesmo n=E3o sei se =E9 poss=EDvel. Mas uma iniciativa interessante,
que pode inibir, =E9 ao contratar pedir que o funcion=E1rio assine uma
declara=E7=E3o de sigilo que deixe expl=EDcito os pontos que quer proteger,
para n=E3o haver d=FAvida e nem ficar nada subentendido.

Creio que hoje em dia toda empresa m=E9dia que lide com c=F3digo fa=E7a iss=
o.

Talvez seja melhor consultar um advogado, nesses casos "achismos" s=E3o
meio perigosos.

E embora precise existir confian=E7a entre as partes, infelizmente nem
todo mundo pensa assim, ent=E3o creio ser uma medida interessante.