From nobody Mon Jan 10 13:00:31 2022 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 32C49194B31E for ; Mon, 10 Jan 2022 13:01:10 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JXYq95l0mz4mCn; Mon, 10 Jan 2022 13:01:09 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-wm1-x336.google.com with SMTP id l12-20020a7bc34c000000b003467c58cbdfso9221903wmj.2; Mon, 10 Jan 2022 05:01:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lZ9VW5UeyfDgXr7kKtJHz4UxyNhMFFJO7YZ+trNyGno=; b=N3nWwEtpcbPK3GD5ha86H6NnCsfeax7VdGrzz9pYCF0KlKzrlAeh1rO584mx0suqmi z/IzkXfVrjHYsBPCyG1Jf3hVLJY4GFMdTixraziEDXyk1j2hhnqoNYhk9qVOlKsQklp7 3QPUlSVoolYgd+m0/HwzCHBL4M6v885Bq8KoOJFe0eA9xzAvhq1UBY9CZBZr7zQ2t+Nl vZyYKeYVzV2KsF/sSiNYKdxwMDHnXMZj3BB7pqPLr3omeWXrEo3D1wr2Kdl2Q/WuW2Td S2vbqADQznsKy8v/8HSHwsP9Empd6MNDPkuwpgkUxultOi4ILPqLIxNAvOIgQ1lnNMGy 8NRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lZ9VW5UeyfDgXr7kKtJHz4UxyNhMFFJO7YZ+trNyGno=; b=wfLESuMUligRRrSjDbytmBQpUqTbtnIBWODnDnyL1LZ8uuTHe16SOZoQekYNI8I01L WZbEQLmmR171rZNj5IEV7QCEpur4WDsYG7vRI3xCXmTGghOcjETVhFxv7nqjs28qrYQt 8HXaQyJZbGAHHpMbu6MRF3MqTozvxB8lAn9+kwKuENIK7/oVRwYJ1xiz4iGCOkdHCT+L XSXoeA+Mb3oc2JX2hlvc8Ad3I+oWeoq8W0p35A4BFuAGq0X4xajYqw6k4rJHfTCeJfeZ LFh2Oyj+hpw/EpGXrRg064e5HEzEKrfgpCy5RfqlKDEzi0oKa1LWlYeUYzA1yP31worW AT0w== X-Gm-Message-State: AOAM531Ilc5F3ozx2o4iVznwDh7mKnUCUSyvkXLyPn89niV+hYu/ispH aFa3sBYNGS8AtC4JclKPpjQpyYu+U82Pi+W9Yl9DXP21KLq7nw== X-Google-Smtp-Source: ABdhPJzGnTbEZ9+nO2n5oQ+jj3QHDG5X2YqaSi8LsF8qZEW/LuOYSv9ETJpAMn0FO6Zy48rXj6edtZ3I0ALRsxGkIuo= X-Received: by 2002:a7b:c0c1:: with SMTP id s1mr21490871wmh.176.1641819668264; Mon, 10 Jan 2022 05:01:08 -0800 (PST) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mehmet Erol Sanliturk Date: Mon, 10 Jan 2022 16:00:31 +0300 Message-ID: Subject: Re: How to contribute To: Kurt Jaeger Cc: "T. G." , FreeBSD Ports List Content-Type: multipart/alternative; boundary="0000000000001cbce205d539ee5a" X-Rspamd-Queue-Id: 4JXYq95l0mz4mCn X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_FROM(0.00)[]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N --0000000000001cbce205d539ee5a Content-Type: text/plain; charset="UTF-8" On Mon, Jan 10, 2022 at 9:40 AM Kurt Jaeger wrote: > Hi! > > > I fixed a lot of bugs in my local related to gnome or other ports. I want > > to know how can i get @FreeBSD email and make some bug-fix commits. > > That's a two-step process: 1) Please submit patches via bugs.freebsd.org > or reviews.freebsd.org. Some committer will have a look, check and commit > if the patches look fine. 2) After a bunch of those patches, some committer > will probably step up as mentor so that you can become a ports committer > yourself. > > > I read https://docs.freebsd.org/en/articles/committers-guide but i did > not > > understand everything. > > If you have questions, try to write them to ports@ and we'll try > to find answers. > > -- > pi@FreeBSD.org +49 171 3101372 Now what ? > > Additional to the above steps , you may do the following actions : In GitHub.com , there is the following repository : https://github.com/freebsd/freebsd-src FreeBSD src tree (read-only mirror) https://github.com/freebsd/freebsd-src/pulls Pull requests You may fork FreeBSD sources into your account . Apply your modifications . Test the your modifications by generating a snapshot , download , and use them to see that your contributions are working as you want AND they are applicable by the other people . Prepare "Pull requests" . Inform the Ports or other mailing list members that you have applicable patches prepared with respect to FreeBSD rules : bug report() , review item(s) , pull request(s) , etc. . The above steps may not be complete , and may be defective , or , excessive , because I am NOT an active GitHub.com user or FreeBSD contributor . Please read and learn GitHub usage rules to become proficient on them and at the same time FreeBSD documentations ( If you have not do these at present , or there are missing parts not learned yet ) to work on these domains fluently . You will see that your efforts will not be wasted , and they will be utilized as much as possible . In the FreeBSD world , the conventions and applications are in this way . Thank you very much , and with my best wishes for all of you , Mehmet Erol Sanliturk --0000000000001cbce205d539ee5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Jan 10, 2022= at 9:40 AM Kurt Jaeger <pi@freebsd.or= g> wrote:
Hi!

> I fixed a lot of bugs in my local related to gnome or other ports. I w= ant
> to know how can i get @FreeBSD email and make some bug-fix commits.
That's a two-step process: 1) Please submit patches via bugs.freebsd.org<= /a>
or reviews.freebsd.org. Some committer will have a look, check and com= mit
if the patches look fine. 2) After a bunch of those patches, some committer=
will probably step up as mentor so that you can become a ports committer yourself.

> I read https://docs.freebsd.org/en/article= s/committers-guide but i did not
> understand everything.

If you have questions, try to write them to ports@ and we'll try
to find answers.

--
pi@FreeBSD.org=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+49 171 3101372=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Now what ?



Additional to= the above steps , you may do the following actions :

<= br>
In GitHub.com , there is the following repository :=

https://github.com/freebsd/freebsd-src
FreeB= SD src tree (read-only mirror)

https://github.com/fre= ebsd/freebsd-src/pulls
Pull requests


<= div>
You may fork FreeBSD sources into your account .
Apply your modifications .
Test the your modifications by= generating a snapshot , download , and use them to see
that= your contributions are working as you want AND they are applicable by the = other
people .
Prepare "Pull reques= ts"=C2=A0 .
Inform the Ports or other mailing list memb= ers that you have applicable patches
prepared with resp= ect to FreeBSD rules : bug report() , review item(s) , pull request(s) ,
etc. .



The above steps may not be complete , and may be de= fective , or , excessive ,
because I am NOT an active GitHu= b.com=C2=A0 user or FreeBSD contributor .

Please read and learn GitHub usage rules to become proficient on the= m and
at the same time FreeBSD documentations
( If you have not do these at present , or there are missing par= ts not learned yet )
to work on these domains fluently = .

You will see that your efforts will = not be wasted , and they will be utilized as much as possible . In the Free= BSD world , the conventions and applications are in this way .


Thank you very much , and wi= th my best wishes for all of you ,


<= /div>
Mehmet Erol Sanliturk



--0000000000001cbce205d539ee5a--