From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.8 required=3.0 tests=BAYES_00,DEAR_SOMETHING, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DE13C4338F for ; Tue, 17 Aug 2021 00:53:23 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A679F60295 for ; Tue, 17 Aug 2021 00:53:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A679F60295 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=aj.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4GpXZn2Bzvz2yLs for ; Tue, 17 Aug 2021 10:53:21 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=aj.id.au header.i=@aj.id.au header.a=rsa-sha256 header.s=fm3 header.b=NlDF0Ps2; dkim=pass (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=Vm4Z9PD2; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=aj.id.au (client-ip=66.111.4.25; helo=out1-smtp.messagingengine.com; envelope-from=andrew@aj.id.au; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=aj.id.au header.i=@aj.id.au header.a=rsa-sha256 header.s=fm3 header.b=NlDF0Ps2; dkim=pass (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=Vm4Z9PD2; dkim-atps=neutral Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4GpXYy1cBjz308t for ; Tue, 17 Aug 2021 10:52:37 +1000 (AEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 3ACF65C01E0; Mon, 16 Aug 2021 20:52:33 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute2.internal (MEProxy); Mon, 16 Aug 2021 20:52:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=aRUIVL8bDQg60r27tg3YTaXhc0JWk+Q UG2N46SHCKRE=; b=NlDF0Ps29cteRKOTiG9Pg5iaC74XVNa9q/tJLo7XVpsu6z8 PVpQ4lw7haYVMZPhkLqbEEcOzPDbwtg26wSl8NVquj66OfsMYhPtm7yYDd3Wzff1 0f+wCy5R1n18cbG+mtNZwfuVS3Z3bWkLKT8qKaOMTmz4uhBBlAgPBz5O8MJWfrtF EYix8xpAu3ZrOnY/c4p7/kssu2q9y6TUowMc2+JdmkxGAWZOdHs6ZPrimVHp3j/l VPXallVN/5GBChx7nf9g4rcFeOUShFvSqqiAS/4oRDpF882eCJYtFs+arZHoyr7r +j++BeMUOQf/+ULSRTjCrgmwUf9CP2Xe/ASa67Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=aRUIVL 8bDQg60r27tg3YTaXhc0JWk+QUG2N46SHCKRE=; b=Vm4Z9PD25WnxZFf7+Pi2W1 hEsm3Q6RIFZTzNbdDX6+ssM4TbmZcm18BYRrZ4dkF0Wdy52L4SxLPylH0n8GwFhf V0GwoabBE3d4aMNoc6rSTZPvpZeh/ozfDcEmZgpYXb24DI2VUlJWc+pOh7byYwse 7VFv9FvG84ChJbQPF4+cR4DjynrR05UNZFiHhg0IqFvvnyVmLZpNJzuiU00/apuR snPv/n/vVFCTCm9xPBdy78ywxE0KignpBikLlc3pKU4rt2SoQsdZTgqvQm/9J73o 3zSzB9hyur+zGhQ1jGx9WGziC4cZe6/bJOPLZtYwQwxVKfl1IU84K1tboEz643nQ == X-ME-Sender:

X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrledvgdeflecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculddvfedmnecujfgurhepofgfgg fkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdetnhgurhgvficulfgvfhhf vghrhidfuceorghnughrvgifsegrjhdrihgurdgruheqnecuggftrfgrthhtvghrnhepte duudeugfffffduffetgedtkeetieellefhueeuhfdtjeelkeejfeffffffueeknecuffho mhgrihhnpehgihhthhhusgdrtghomhdptghonhhtrhhisghuthhinhhgrdhmugdpohhpvg hnsghmtghprhhojhgvtghtrdighiiinecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomheprghnughrvgifsegrjhdrihgurdgruh X-ME-Proxy:

Received: by mailuser.nyi.internal (Postfix, from userid 501) id 079B1AC0E77; Mon, 16 Aug 2021 20:52:33 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-1118-g75eff666e5-fm-20210816.002-g75eff666 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Tue, 17 Aug 2021 10:22:12 +0930 From: "Andrew Jeffery" To: "Figo Chen" , openbmc@lists.ozlabs.org Subject: Re: Apply the account for OpenBMC contribute Content-Type: text/plain X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" Hello Figo Chen, On Mon, 16 Aug 2021, at 16:16, Figo Chen wrote: > Dear Sir, > > May I have an account to join the OpenBMC git to contribute ? We need to unpack a few things to answer this question, because how to answer it is less clear than you might suspect: 1. No one needs to create an account for you if you're looking to push patches for review, you can do this yourself by following the process documented here: https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-server-to-openbmc Essentially, you need a Github account, and once you have one, you use it to sign into our Gerrit instance[1]. [1] https://gerrit.openbmc_project.xyz/ 2. If you're looking to become a maintainer and have the ability to submit patches, you need to show the existing maintainers that you're capable. This is usually done by participating in discussions on the mailing list or Discord, reviewing other people's patches and proposing your own. To the point: Generally a very small set of people can actually merge patches. 3. Currently, contributions to OpenBMC require signing a Contributor License Agreement (CLA). The process is described here: https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#starting-out Essentially, If you're doing this out of your own interest and not on behalf of an employer, then you need to sign the Individual CLA (ICLA). If you will be contributing on behalf of your employer, then you should convince them to sign the Corporate CLA (CCLA). Prefer the CCLA if you can. Hope that helps, Andrew