[Cryptech Core] git repository usage patterns and access control

Joachim Strömbergson joachim at secworks.se
Tue Oct 7 05:19:05 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Aloha!

Linus Nordberg wrote:
> Rob Austein  wrote Mon, 06 Oct 2014 16:23:59 -0400:
> 
> | 2) Same as (1), but adopt a github-like work pattern where 
> developers |    who want to hack each other's code fork the 
> repository.  gitolite
> 
> This is what I would suggest. I'd also like to explain how I like 
> software projects with multiple developers and git. If this model 
> suits the work flow for Cryptech too, I don't know.
> 
> For a given "project" (i.e. repository), each developer has their
> own repository. Perhaps under /user/$NAME/. Only $NAME can push to
> repos under /user/$NAME/.
> 
> For a given "project", there is also "the main" repository, or 
> perhaps better "the official" repository. One or more (hopefully at 
> least two) maintainers have push access to it. They merge changes 
> from topic branches in other repositories into this official 
> repository. This is where we point people. This is what we make 
> releases from.

Yes. This is what we want. IMHO.

(And yes, me asking for write access to Pauls repo was actually wrong.)

- -- Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
 Joachim Strömbergson          Secworks AB          joachim at secworks.se
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJUM3fJAAoJEF3cfFQkIuyNiRMP/j1b38Fh0EJevnIRcfeabiXI
tahUcvStNt9qy+1KQF98N5K2qNN+Cc7emQ3/V4V7llYvmiTiYr0wWLI1BAaqV7ig
CcBIyiF7NrYXySU16v4yOPMW05PS/jzPJo06xbBcqGXaxnSag3hhX8BO9uqaUBwF
h1Ef+bmjxvHNmQwvUevPUpMgthF8Tw/okepoikk4ym4YpJMsgYhAqtHweU+OWp8O
cta2hbO/WkyWXJ+aV8I/Rry3+tLxiVymvfv7hansb94zXb7wyFZzMlUgaDeqpyYZ
blbLak2SkUMU9HqrxasY1N8b+Fo2SgMAeBl9zeIB62mZZRPLKNJyHOsci+REZVn6
ht1moo5LCWLD9QkVAZ75ADyoGKgWOFAHEws8EDzCaAu44TRSn6QiBoHCTNaHr6V4
9C+yV6BbZ/bRzEMsIzHy8ZQ+/v/5rp1tBLH3Z3Mday/32BmdEnkusuifB3JBwLLF
AaE29TpBQKszzmUsqIHRGuwauF1tm/guy95tGFOWaRmGH5m2115xwKD/NDQfNvKm
jNrdgZa8rQft5AfLfQx/AVY4GhzPSWJFQUsPLtyN62fXEbTSJnPux1LOAWltOhgu
skeKd4qXmxFSNK79vD/ZSvbv4myslgufK37AKpcMn0bTrhc4s/7e064WkrBcacpG
jM0px/JW4eZQ3e4Bq9Ni
=oq1X
-----END PGP SIGNATURE-----



More information about the Core mailing list