We've formed the Deepin DE SIG for a while, and we want to formally announce the SIG to call for more packagers to help. So before I send another email to devel list, I want to request for resources that we need for the SIG.
I think we need
deepinde-sig@lists.fp.o
deepinde@lists.fp.o
I know this is a loooooooot of work for infra, or maybe some of them should go to different ticket systems. So if you need separate ticket for each item, please let me know.
Thanks a lot.
There is no deadline of course, but the earlier the better ;-)
If you need backup contact, @cheeselee should be the right person.
@pingou can you do this one? Or if not I can try tomorrow...
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Metadata Update from @pingou: - Issue assigned to pingou
I've created the two new mailing list: - https://lists.fedoraproject.org/admin/lists/deepinde.lists.fedoraproject.org/ - https://lists.fedoraproject.org/admin/lists/deepinde-sig.lists.fedoraproject.org/
I've created the deepinde-sig group in FAS: https://admin.fedoraproject.org/accounts/group/view/deepinde-sig
I've created the deepinde-sig group on src.fp.o: https://src.fedoraproject.org/group/deepinde-sig
The rest of your list is correct, you need to create a BZ account for deepinde-sig@lists.fp.o, set the list to be private (as private tickets opened in bugzilla will be sent there). To associate the group with the bugzilla, you need to edit the group's preferences in FAS and set the mailing-list address to be deepinde-sig@lists.fp.o, that's how the sync is then done to bugzilla. Then you can simply add the group to the packages of interest on src.fp.o
For COPR I don't really know how groups are synced/handled so I don't know what to do there.
Metadata Update from @pingou: - Assignee reset
Thanks for the quick response. I just set the deepinde-sig@l.fp.o to private and created the bugzilla account as well as set the mailing list to the FAS group. I am travelling at the moment and internet access is limited, so I will check more details after back (probably in early Feb).
Closing this, please reopen if you face any issues
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.