V Thu, Feb 16, 2023 at 07:29:07PM +0000, Kenneth Goldman napsal(a):
I think I followed all those steps - identifying the package, announcing that I want to be the packager, making an account, etc.
What's next?
Submit an updated tss2 package for a package review. As far as I can see, there is no review opened for tss2 now https://bugzilla.redhat.com/buglist.cgi?component=Package%20Review&product=Fedora&short_desc=tss2&short_desc_type=allwordssubstr. How to do it is described at https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/#_contributor. Especially pay attention to:
If you are not member of the packager group, you need a sponsor. Add FE-NEEDSPONSOR to the bugs being blocked by your review request.
Does someone approve me?
Based on the FE-NEEDSPONSOR blocker someone from sponsors should notice your review request and start to communicate with you in the review request in Bugzilla. (If that does not happen, approach you a sponsor of your choice as recommended at https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#how_to_find_a_sponsor)
Once the sponsor finds your package looks good and you understand how to maintain a package, he/she will sponsor you, i.e. adds you into a packagers group. Then you will be able to continue from this item on the Package_Review_Process document:
When your package passes the review you should use fedpkg to request a Git repository for it.
Move a git repo somewhere?
For the purpose of the package review, you need to publish the spec file and the SRPM file somewhere on the Internet. (Once you become a packager, you can also use https://fedorapeople.org/ server for that purpose.)
Once the package review passes, the offical git repository (called dist-git in Fedora) for the tss2 package will be reopened with completing this item:
Request a Git repository for the package
Then you will commit the new spec file into the reopen dist-git repository.
-- Petr
On Fri, Feb 17, 2023 at 9:04 AM Petr Pisar ppisar@redhat.com wrote:
V Thu, Feb 16, 2023 at 07:29:07PM +0000, Kenneth Goldman napsal(a):
I think I followed all those steps - identifying the package, announcing that I want to be the packager, making an account, etc.
What's next?
Submit an updated tss2 package for a package review. As far as I can see, there is no review opened for tss2 now
It was only retired on Jan 9th so should not need a re-review.
I think the process needs to be: 1) get a package sponsor. If you don't have one I can possibly do it as I co-maintain the intel tpm2 packages 2) request ownership and unblocking of the package 3) build new versions as follow the process.
https://bugzilla.redhat.com/buglist.cgi?component=Package%20Review&product=Fedora&short_desc=tss2&short_desc_type=allwordssubstr. How to do it is described at https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/#_contributor. Especially pay attention to:
If you are not member of the packager group, you need a sponsor. Add FE-NEEDSPONSOR to the bugs being blocked by your review request.
Does someone approve me?
Based on the FE-NEEDSPONSOR blocker someone from sponsors should notice your review request and start to communicate with you in the review request in Bugzilla. (If that does not happen, approach you a sponsor of your choice as recommended at https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#how_to_find_a_sponsor)
Once the sponsor finds your package looks good and you understand how to maintain a package, he/she will sponsor you, i.e. adds you into a packagers group. Then you will be able to continue from this item on the Package_Review_Process document:
When your package passes the review you should use fedpkg to request a Git repository for it.
Move a git repo somewhere?
For the purpose of the package review, you need to publish the spec file and the SRPM file somewhere on the Internet. (Once you become a packager, you can also use https://fedorapeople.org/ server for that purpose.)
Once the package review passes, the offical git repository (called dist-git in Fedora) for the tss2 package will be reopened with completing this item:
Request a Git repository for the package
Then you will commit the new spec file into the reopen dist-git repository.
-- Petr _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-----Original Message----- From: Peter Robinson pbrobinson@gmail.com Sent: Friday, February 17, 2023 4:20 AM To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: [EXTERNAL] Re: TSS maintainer volunteer
On Fri, Feb 17, 2023 at 9:04 AM Petr Pisar ppisar@redhat.com wrote:
V Thu, Feb 16, 2023 at 07:29:07PM +0000, Kenneth Goldman napsal(a):
I think I followed all those steps - identifying the package, announcing that I want to be the packager, making an account, etc.
What's next?
Submit an updated tss2 package for a package review. As far as I can see, there is no review opened for tss2 now
It was only retired on Jan 9th so should not need a re-review.
I think the process needs to be:
- get a package sponsor. If you don't have one I can possibly do it as I
co- maintain the intel tpm2 packages
Can you get me a sponsor / sponsor it? That seems to be the next step.
- request ownership and unblocking of the package
How do I do that? I did the Pagure, releng tickets
#559 tss2, tss2-devel package maintainer #11294 Unretire tss2, tss2-devel
- build new versions as follow the process.
I'm working through the tutorial. If you have an alternate HOWTO, let me know.
3A__bugzilla.redhat.com_buglist.cgi-3Fcomponent-3DPackage-2520Review- 26product-3DFedora-26short-5Fdesc-3Dtss2-26short-5Fdesc-5Ftype- 3Dallwordssubstr&d=DwIGaQ&c=jf_iaSHvJObTbx- siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1- mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9- uwvnxzuXat8ZLOJ_EwPWbbZ&s=ChnuonR2xzfsR- 55TVKYnZojmhjceqrcSRl9S_URRow&e= >.
How to do it is described at <https://urldefense.proofpoint.com/v2/url?u=https-
3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Package- 5FReview-5FProcess_-23-5Fcontributor&d=DwIGaQ&c=jf_iaSHvJObTbx- siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1- mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9- uwvnxzuXat8ZLOJ_EwPWbbZ&s=69hUQdHPBi7Qv8EFcTVNjiZd880oTiPox9hM0rB oKtg&e= >.
Especially pay attention to:
If you are not member of the packager group, you need a sponsor. Add FE-NEEDSPONSOR to the bugs being blocked by your review request.
Does someone approve me?
Based on the FE-NEEDSPONSOR blocker someone from sponsors should notice your review request and start to communicate with you in the review request in Bugzilla. (If that does not happen, approach you a sponsor of your choice as recommended at <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproje ct.org_en-2DUS_package-2Dmaintainers_How-5Fto-5FGet-5FSponsored-
5Finto
-5Fthe-5FPackager-5FGroup_-23how-5Fto-5Ffind-5Fa-
5Fsponsor&d=DwIGaQ&c=
jf_iaSHvJObTbx-siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
mlmiA&m
=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
uwvnxzuXat8ZLOJ_EwPWbbZ&s=wQ
0j4l0zTDLd6Wcb3Easz-QF-q_MukicKUX5PjsECMU&e= >)
Once the sponsor finds your package looks good and you understand how to maintain a package, he/she will sponsor you, i.e. adds you into a packagers group. Then you will be able to continue from this item on the Package_Review_Process document:
When your package passes the review you should use fedpkg to request a
Git
repository for it.
Move a git repo somewhere?
For the purpose of the package review, you need to publish the spec file and the SRPM file somewhere on the Internet. (Once you become a packager, you can also use <https://urldefense.proofpoint.com/v2/url?u=https-3A__fedorapeople.org _&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-
O1GZkt
Ffre1-mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
uwvnxzuXat8ZLOJ
_EwPWbbZ&s=W-SMTTNywFjnciP-Cj5_16Zh9LkcQDkEAEitLklonsA&e= > server
for
that purpose.)
Once the package review passes, the offical git repository (called dist-git in Fedora) for the tss2 package will be reopened with completing this item:
Request a Git repository for the package
Then you will commit the new spec file into the reopen dist-git repository.
-- Petr _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraprojec t.org_en-2DUS_project_code-2Dof-
2Dconduct_&d=DwIGaQ&c=jf_iaSHvJObTbx-s
iA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
mlmiA&m=LENjKgA1o8jJJQU
eUgkw1NFO085ft2GxJNSWS6C9-
uwvnxzuXat8ZLOJ_EwPWbbZ&s=oV9NmN_quxXMyDtHMw
-SotPI3e712uROhkbauKod2ZY&e= List Guidelines: https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org _wiki_Mailing-5Flist-5Fguidelines&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r= DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO
085ft2GxJNSWS6C9-uwvnxzuXat8ZLOJ_EwPWbbZ&s=VrVh1-
gosV0wONSHHCIMHxw3oup
c2yn2E75bZW5TYKo&e= List Archives: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproje ct.org_archives_list_devel-40lists.fedoraproject.org&d=DwIGaQ&c=jf_iaS HvJObTbx-siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
mlmiA&m=LENjK
gA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
uwvnxzuXat8ZLOJ_EwPWbbZ&s=ITQ9OU6F
6c-UL1IGFGxGBecuF8dTdUxud8NWucxWOGo&e= Do not reply to spam, report it: https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora- 2Dinfrastructure_new-5Fissue&d=DwIGaQ&c=jf_iaSHvJObTbx-
siA1ZOg&r=DZCVG
43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft
2GxJNSWS6C9-uwvnxzuXat8ZLOJ_EwPWbbZ&s=6gKbDLBdJP-
8HUi343qYZa61H_ZOsF7P
D2TtE_jQUew&e=
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://urldefense.proofpoint.com/v2/url?u=https- 3A__docs.fedoraproject.org_en-2DUS_project_code-2Dof- 2Dconduct_&d=DwIGaQ&c=jf_iaSHvJObTbx- siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1- mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9- uwvnxzuXat8ZLOJ_EwPWbbZ&s=oV9NmN_quxXMyDtHMw- SotPI3e712uROhkbauKod2ZY&e= List Guidelines: https://urldefense.proofpoint.com/v2/url?u=https- 3A__fedoraproject.org_wiki_Mailing-5Flist- 5Fguidelines&d=DwIGaQ&c=jf_iaSHvJObTbx- siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1- mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9- uwvnxzuXat8ZLOJ_EwPWbbZ&s=VrVh1- gosV0wONSHHCIMHxw3oupc2yn2E75bZW5TYKo&e= List Archives: https://urldefense.proofpoint.com/v2/url?u=https- 3A__lists.fedoraproject.org_archives_list_devel- 40lists.fedoraproject.org&d=DwIGaQ&c=jf_iaSHvJObTbx- siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1- mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9- uwvnxzuXat8ZLOJ_EwPWbbZ&s=ITQ9OU6F6c- UL1IGFGxGBecuF8dTdUxud8NWucxWOGo&e= Do not reply to spam, report it: https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora- 2Dinfrastructure_new-5Fissue&d=DwIGaQ&c=jf_iaSHvJObTbx- siA1ZOg&r=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1- mlmiA&m=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9- uwvnxzuXat8ZLOJ_EwPWbbZ&s=6gKbDLBdJP- 8HUi343qYZa61H_ZOsF7PD2TtE_jQUew&e=
I'm not 100% clear on the process. I have a .spec file that passes fedpkg mockbuild.
I submitted the request to https://bugzilla.redhat.com/show_bug.cgi?id=2238052.
Is that all? What else should I do?