[Intelmq-dev] Write Access to Repositories, Issue Tracker: Develop Community Guidelines
L. Aaron Kaplan
kaplan at cert.at
Thu Jan 5 13:22:38 CET 2017
> On 05 Jan 2017, at 11:51, Dustin Demuth <dustin.demuth at intevation.de> wrote:
>
>
> Hi Dev's
>
> I'm wondering how and if we want to organise write access to the main
> repository.
I definitely prefer the current model *for all of us* to send PRs and the core maintainers (mostly Sebix) has to go over the PRs and do some QA before merging them in.
It's really a matter of cleanliness and quality assurance.
That's what I want to ensure by this process.
Thanks,
a.
--
// CERT Austria
// L. Aaron Kaplan <kaplan at cert.at>
// T: +43 1 505 64 16 78
// http://www.cert.at
// Eine Initiative der nic.at GmbH
// http://www.nic.at/ - Firmenbuchnummer 172568b, LG Salzburg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.cert.at/pipermail/intelmq-dev/attachments/20170105/a3fb87fa/attachment.sig>
More information about the Intelmq-dev
mailing list