Add you name/fas id here so it can be added in to the pagure Go SIG group.
FAS : robbinespu
FAS: logic
FAS: kumarpraveen
All requests processed until this point.
FAS: zsun
FAS: sadin
Done. @sadin @zsun
FAS: copart
FAS: deparker
Done. @deparker @copart
FAS: mosquito
Remind me to add deparker to the Go-SIG group on FAS once he is sponsored to be a packager.
FAS: carlwgeorge
FAS: mskalick
@mskalick Done
FAS: szydell
FAS: acaldwell
done
FAS: decathorpe
(yes, I'm back)
FAS: decathorpe (yes, I'm back)
Done. Also suscribe to https://lists.fedoraproject.org/archives/list/golang%40lists.fedoraproject.org/
FAS: mgoodwin (have subscribed to golang@lists.fedoraproject.org)
FAS: mgoodwin
FAS: comaldave
Please add me.
https://blog.davsk.net
Thank you.
FAS: alexsaezm
You don't appear to be in the packager group.
FAS: blowry
FAS ID: nasirhm
Please add me to Go SIG group. FAS: olem
Please add me to GO SIG group. FAS: masch
You need to be sponsored as a member of the packager group first.
FAS: dfateyev
Done. Also subscribe to https://lists.fedoraproject.org/archives/list/golang%40lists.fedoraproject.org/ (for organising)
You are also subscribed to go-sig@lists.fedoraproject.org (for package activity, heavy load, please tweak your Sieve scripts accordingly).
I will make your Go Review Request first.
FAS: dancoe77
Processed @alexsaezm . @dancoe77 you need to be a packager https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
FAS: yanqiyu
Please add me
FAS: yanqiyu Please add me
Sorry for the delay, I've added you.
Please also subscribe to https://lists.fedoraproject.org/archives/list/golang%40lists.fedoraproject.org/ (for organising)
Please add me :)
FAS: jjasghar
FAS: obudai
FAS: obudai Please add me
sorry for the wait I thought someone else would have taken care of it by now.
I've added you to go-sig@lists.fedoraproject.org , please prepare your sieve scripts to handle the stream of mail.
FAS: fab
I have added you to the SIG.
Please register to the MLs:
https://lists.fedoraproject.org/admin/lists/go-sig.lists.fedoraproject.org/ (bugzilla bugs, high throughput, private) https://lists.fedoraproject.org/admin/lists/golang.lists.fedoraproject.org/ (communication between members, public)
FAS: suanand
FAS: gotmax
Can you please add me? I already joined golang@lists.fedoraproject.org.
Thanks, Maxwell
FAS: copperi Please add me
@eclipseo Still following this issue ?
I'm really busy these days, i see you have been added, don't forget to subscribe to the ML.
@gotmax23 Thanks for accepting PR.
No problem, @eclipseo. Thank you for all of the work you have done :). I know you are stretched pretty thin.
I submitted PRs to update golang-github-google-cmp and golang-google-protobuf which you maintain. In the future, would it be okay for me to build and submit updates for go-sig packages instead of creating a PR? I didn't want to step on anybody's toes, so I didn't.
golang-github-google-cmp
golang-google-protobuf
go-sig
On Mon, 20 Dec 2021, 02:48 Maxwell G, pagure@pagure.io wrote:
gotmax23 added a new comment to an issue you are following: `` No problem, @eclipseo. Thank you for all of the work you have done :). I know you are stretched pretty thin. I submitted PRs to update golang-github-google-cmp and golang-google-protobuf which you maintain. In the future, would it be okay for me to build and submit updates for go-sig packages instead of creating a PR? I didn't want to step on anybody's toes, so I didn't. `` To reply, visit the link below or just reply to this email https://pagure.io/GoSIG/go-sig/issue/1
gotmax23 added a new comment to an issue you are following: `` No problem, @eclipseo. Thank you for all of the work you have done :). I know you are stretched pretty thin.
I submitted PRs to update golang-github-google-cmp and golang-google-protobuf which you maintain. In the future, would it be okay for me to build and submit updates for go-sig packages instead of creating a PR? I didn't want to step on anybody's toes, so I didn't. ``
To reply, visit the link below or just reply to this email https://pagure.io/GoSIG/go-sig/issue/1
Yes but I'd like you to convert all the spec to rpmautospec. You need to do it in a separate commit before your update. 1. Copy the existing changelog to a file called changelog 2. Replace the existing %changeling with:
%changelog %autochangelog
Release: %autorelease
Commit your change as "Convert to rpmautospec"
Then do your update of the spec and commit it with the change log message you want: "Update to X. X. X Close: rhbz#XXXXXXX"
On Mon, 20 Dec 2021, 02:48 Maxwell G, pagure@pagure.io wrote: gotmax23 added a new comment to an issue you are following: `` No problem, @eclipseo. Thank you for all of the work you have done :). I know you are stretched pretty thin. I submitted PRs to update golang-github-google-cmp and golang-google-protobuf which you maintain. In the future, would it be okay for me to build and submit updates for go-sig packages instead of creating a PR? I didn't want to step on anybody's toes, so I didn't. `` To reply, visit the link below or just reply to this email https://pagure.io/GoSIG/go-sig/issue/1 Yes but I'd like you to convert all the spec to rpmautospec. You need to do it in a separate commit before your update. 1. Copy the existing changelog to a file called changelog 2. Replace the existing %changeling with: %changelog %autochangelog Replace the Release: with: Release: %autorelease Commit your change as "Convert to rpmautospec" Then do your update of the spec and commit it with the change log message you want: "Update to X. X. X Close: rhbz#XXXXXXX"
Alright, I will do so for the specfiles that you maintain, but I prefer to use rpmdev-bumpspec and fedpkg clog with a regular changelog for mine.
rpmdev-bumpspec
fedpkg clog
On Mon, 20 Dec 2021, 02:48 Maxwell G, pagure@pagure.io wrote: Yes but I'd like you to convert all the spec to rpmautospec. You need to do it in a separate commit before your update. 1. Copy the existing changelog to a file called changelog 2. Replace the existing %changeling with: %changelog %autochangelog Replace the Release: with: Release: %autorelease Commit your change as "Convert to rpmautospec" Then do your update of the spec and commit it with the change log message you want: "Update to X. X. X Close: rhbz#XXXXXXX"
On Mon, 20 Dec 2021, 02:48 Maxwell G, pagure@pagure.io wrote: Yes but I'd like you to convert all the spec to rpmautospec. You need to do it in a separate commit before your update. 1. Copy the existing changelog to a file called changelog 2. Replace the existing %changeling with:
Don't convert manually! Install the the development version of rpmautospec from https://pagure.io/fedora-infra/rpmautospec and then you get the rpmautospec convert command that was recently merged. Hopefully they will make a release soon that you can just update from rpm.
rpmautospec convert
@eclipseo, can you also please add me to @GoSIG on pagure.io? When I was initially added, I was added to the FAS group but not the Pagure group or the mailing list.
I added you to the Pagure group. I think I added you to the mailing list the other day too.
@eclipseo, can you also please add me to @GoSIG on pagure.io? When I was initially added, I was added to the FAS group but not the Pagure group or the mailing list. I added you to the Pagure group. I think I added you to the mailing list the other day too.
Yes, you did. Thank you for both!
Please add me! (FAS: fale)
Please, add me!
FAS: mikelo2
Please add me: FAS: fuller
Hi, I added you.
Please add me: FAS: eduram
You need to join the packager group first (and sign the CLA):
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/
You are added. Please join the golang (low traffic) and go-sig (very high traffic) ML, and join us on our Matrix channel.
Best regards
FAS: matthickford (not yet in packager group)
FAS: rishi
I've added you.
Please add me. FAS: matthickford (now in the packager group)
Login to comment on this ticket.