Re: [Pulp-dev] [Pulp-list] Github Discussions

[David Davis]

I've taken down Github Discussions. It looks like Github stores the
Discussions though so I can still re-enable them temporarily if anyone
needs info, etc.

David


On Tue, Aug 24, 2021 at 2:44 PM David Davis  wrote:

> AFAICT, there's no way to make discussions readonly so any discussions not
> migrated over won't be accessible although I think we can still get to them
> by temporarily enabling Discussions.
>
> Looks like mcorr already migrated over your thread. :)
>
> David
>
>
> On Tue, Aug 24, 2021 at 2:01 AM Quirin Pamp  wrote:
>
>> Will it still be possible to read old discussion threads?
>>
>> If no, I would like it if this one could be migrated (for the conclusions
>> reached in the thread):
>>
>> https://github.com/pulp/community/discussions/73
>>
>> Quirin (quba42)
>>
>> 
>> From: pulp-dev-boun...@redhat.com  on
>> behalf of David Davis 
>> Sent: 23 August 2021 15:30
>> To: Melanie Corr
>> Cc: pulp-list; Pulp Development List
>> Subject: Re: [Pulp-dev] [Pulp-list]  Github Discussions
>>
>> If no one objects, I will be retiring Pulp's Github Discussions by
>> September 1st. It seems like the options we are considering going forward
>> are either staying on the mailing lists or moving to Discourse.
>>
>> If you need something migrated over to Discourse from Github Discussions,
>> please let me know.
>>
>> David
>>
>>
>> On Wed, Aug 11, 2021 at 9:55 AM Melanie Corr > mc...@redhat.com>> wrote:
>> Hi all,
>>
>> Based on your feedback, we now have a Pulp Community Discourse:
>> https://discourse.pulpproject.org/
>>
>> This is still a continuation of our evaluation of whether to move away
>> from the mailing list as a primary communication method. We need you to
>> tell us if this is helpful.
>>
>> We will wrap up any discussions that remain open on our GitHub
>> Discussions page and migrate any open discussions.
>>
>> I'm getting everything ready. Please feel free to make suggestions.
>>
>> Please join us over on Discourse!
>>
>> Melanie
>>
>> Ar Aoine 18 Meith 2021 ag 17:01, scríobh Melanie Corr > <mailto:mc...@redhat.com>>:
>> Having been an admin on the Foreman Community Discourse for over a year,
>> I am +1 to a using Discourse for community conversations.
>> Greg Sutcliffe has data to prove the increase in community engagement
>> after the move.
>>
>> Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley > <mailto:dal...@redhat.com>>:
>> And Matrix integration.
>> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522
>>
>>
>> On Thu, Jun 17, 2021 at 1:11 PM David Davis > <mailto:davidda...@redhat.com>> wrote:
>> I was rather surprised but Discourse did approve us for a free plan. The
>> instance has been set up at https://pulp.discourse.group/. Feel free to
>> try it out and experiment with it.
>>
>> However, the main limitation I see is the 50k pageviews per month limit.
>> For reference, community.theforeman.org<http://community.theforeman.org>
>> gets about 160-220k pageviews per month. So I think this would end up being
>> a problem. I also checked with OSCI though and they apparently have
>> experience with setting up Discourse instances for other open source
>> communities. So I think they might be willing to set up a Discourse
>> instance for us. I'm going to follow up and confirm.
>>
>> If we go this route, then we can also add the calendar plugin which would
>> give us a public calendar like foreman has:
>>
>> https://community.theforeman.org/c/events/13/l/calendar
>>
>> I'm imagining we can use this to list events that are open to the public
>> like triage/open floor and perhaps plugin team meetings.
>>
>> The more I use Discourse, the more I feel like it ticks all the boxes
>> from granular notifications (weekly digests, ability to follow/unfollow
>> categories, etc) to a mailing list mode users can enable to SSO integration
>> with services like Github.
>>
>> David
>>
>>
>> On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa > ngomp...@gmail.com>> wrote:
>> On Wed, Jun 16, 2021 at 7:21 PM David Davis > <mailto:davidda...@redhat.com>> wrote:
>> >
>> > One of the main reasons we wanted to move off mailing lists is that
>> signing up is inconvenient for users that may just want to ask a single
>> question. But I agree that Github Discussions is not so great if users wan

Re: [Pulp-dev] [Pulp-list] Github Discussions

[David Davis]

AFAICT, there's no way to make discussions readonly so any discussions not
migrated over won't be accessible although I think we can still get to them
by temporarily enabling Discussions.

Looks like mcorr already migrated over your thread. :)

David


On Tue, Aug 24, 2021 at 2:01 AM Quirin Pamp  wrote:

> Will it still be possible to read old discussion threads?
>
> If no, I would like it if this one could be migrated (for the conclusions
> reached in the thread):
>
> https://github.com/pulp/community/discussions/73
>
> Quirin (quba42)
>
> 
> From: pulp-dev-boun...@redhat.com  on behalf
> of David Davis 
> Sent: 23 August 2021 15:30
> To: Melanie Corr
> Cc: pulp-list; Pulp Development List
> Subject: Re: [Pulp-dev] [Pulp-list]  Github Discussions
>
> If no one objects, I will be retiring Pulp's Github Discussions by
> September 1st. It seems like the options we are considering going forward
> are either staying on the mailing lists or moving to Discourse.
>
> If you need something migrated over to Discourse from Github Discussions,
> please let me know.
>
> David
>
>
> On Wed, Aug 11, 2021 at 9:55 AM Melanie Corr  mc...@redhat.com>> wrote:
> Hi all,
>
> Based on your feedback, we now have a Pulp Community Discourse:
> https://discourse.pulpproject.org/
>
> This is still a continuation of our evaluation of whether to move away
> from the mailing list as a primary communication method. We need you to
> tell us if this is helpful.
>
> We will wrap up any discussions that remain open on our GitHub Discussions
> page and migrate any open discussions.
>
> I'm getting everything ready. Please feel free to make suggestions.
>
> Please join us over on Discourse!
>
> Melanie
>
> Ar Aoine 18 Meith 2021 ag 17:01, scríobh Melanie Corr  <mailto:mc...@redhat.com>>:
> Having been an admin on the Foreman Community Discourse for over a year, I
> am +1 to a using Discourse for community conversations.
> Greg Sutcliffe has data to prove the increase in community engagement
> after the move.
>
> Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley  <mailto:dal...@redhat.com>>:
> And Matrix integration.
> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522
>
>
> On Thu, Jun 17, 2021 at 1:11 PM David Davis  davidda...@redhat.com>> wrote:
> I was rather surprised but Discourse did approve us for a free plan. The
> instance has been set up at https://pulp.discourse.group/. Feel free to
> try it out and experiment with it.
>
> However, the main limitation I see is the 50k pageviews per month limit.
> For reference, community.theforeman.org<http://community.theforeman.org>
> gets about 160-220k pageviews per month. So I think this would end up being
> a problem. I also checked with OSCI though and they apparently have
> experience with setting up Discourse instances for other open source
> communities. So I think they might be willing to set up a Discourse
> instance for us. I'm going to follow up and confirm.
>
> If we go this route, then we can also add the calendar plugin which would
> give us a public calendar like foreman has:
>
> https://community.theforeman.org/c/events/13/l/calendar
>
> I'm imagining we can use this to list events that are open to the public
> like triage/open floor and perhaps plugin team meetings.
>
> The more I use Discourse, the more I feel like it ticks all the boxes from
> granular notifications (weekly digests, ability to follow/unfollow
> categories, etc) to a mailing list mode users can enable to SSO integration
> with services like Github.
>
> David
>
>
> On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa  ngomp...@gmail.com>> wrote:
> On Wed, Jun 16, 2021 at 7:21 PM David Davis  davidda...@redhat.com>> wrote:
> >
> > One of the main reasons we wanted to move off mailing lists is that
> signing up is inconvenient for users that may just want to ask a single
> question. But I agree that Github Discussions is not so great if users want
> to periodically monitor news and discussions for a project like Pulp. I
> wonder perhaps if Discourse[0] would be a better fit (see Foreman's use of
> discourse as an example[1]). It provides a mailing list mode that users can
> enable if they want to interact solely via email. And also, it also offers
> more granular control of notifications and auth with services like Github.
> >
>
> The Fedora mailing list system (HyperKitty) actually manages to strike
> a good balance here. You can sign in with OIDC/Social Login with
> Fedora, Google, etc. and post to a list and only be subscribed to that
> thread. Or you can subscribe to the whole 

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Quirin Pamp]

Will it still be possible to read old discussion threads?

If no, I would like it if this one could be migrated (for the conclusions 
reached in the thread):

https://github.com/pulp/community/discussions/73

Quirin (quba42)


From: pulp-dev-boun...@redhat.com  on behalf of 
David Davis 
Sent: 23 August 2021 15:30
To: Melanie Corr
Cc: pulp-list; Pulp Development List
Subject: Re: [Pulp-dev] [Pulp-list]  Github Discussions

If no one objects, I will be retiring Pulp's Github Discussions by September 
1st. It seems like the options we are considering going forward are either 
staying on the mailing lists or moving to Discourse.

If you need something migrated over to Discourse from Github Discussions, 
please let me know.

David


On Wed, Aug 11, 2021 at 9:55 AM Melanie Corr 
mailto:mc...@redhat.com>> wrote:
Hi all,

Based on your feedback, we now have a Pulp Community Discourse: 
https://discourse.pulpproject.org/

This is still a continuation of our evaluation of whether to move away from the 
mailing list as a primary communication method. We need you to tell us if this 
is helpful.

We will wrap up any discussions that remain open on our GitHub Discussions page 
and migrate any open discussions.

I'm getting everything ready. Please feel free to make suggestions.

Please join us over on Discourse!

Melanie

Ar Aoine 18 Meith 2021 ag 17:01, scríobh Melanie Corr 
mailto:mc...@redhat.com>>:
Having been an admin on the Foreman Community Discourse for over a year, I am 
+1 to a using Discourse for community conversations.
Greg Sutcliffe has data to prove the increase in community engagement after the 
move.

Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley 
mailto:dal...@redhat.com>>:
And Matrix integration.  
https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522


On Thu, Jun 17, 2021 at 1:11 PM David Davis 
mailto:davidda...@redhat.com>> wrote:
I was rather surprised but Discourse did approve us for a free plan. The 
instance has been set up at https://pulp.discourse.group/. Feel free to try it 
out and experiment with it.

However, the main limitation I see is the 50k pageviews per month limit. For 
reference, community.theforeman.org<http://community.theforeman.org> gets about 
160-220k pageviews per month. So I think this would end up being a problem. I 
also checked with OSCI though and they apparently have experience with setting 
up Discourse instances for other open source communities. So I think they might 
be willing to set up a Discourse instance for us. I'm going to follow up and 
confirm.

If we go this route, then we can also add the calendar plugin which would give 
us a public calendar like foreman has:

https://community.theforeman.org/c/events/13/l/calendar

I'm imagining we can use this to list events that are open to the public like 
triage/open floor and perhaps plugin team meetings.

The more I use Discourse, the more I feel like it ticks all the boxes from 
granular notifications (weekly digests, ability to follow/unfollow categories, 
etc) to a mailing list mode users can enable to SSO integration with services 
like Github.

David


On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa 
mailto:ngomp...@gmail.com>> wrote:
On Wed, Jun 16, 2021 at 7:21 PM David Davis 
mailto:davidda...@redhat.com>> wrote:
>
> One of the main reasons we wanted to move off mailing lists is that signing 
> up is inconvenient for users that may just want to ask a single question. But 
> I agree that Github Discussions is not so great if users want to periodically 
> monitor news and discussions for a project like Pulp. I wonder perhaps if 
> Discourse[0] would be a better fit (see Foreman's use of discourse as an 
> example[1]). It provides a mailing list mode that users can enable if they 
> want to interact solely via email. And also, it also offers more granular 
> control of notifications and auth with services like Github.
>

The Fedora mailing list system (HyperKitty) actually manages to strike
a good balance here. You can sign in with OIDC/Social Login with
Fedora, Google, etc. and post to a list and only be subscribed to that
thread. Or you can subscribe to the whole list and do things like we
do now.

> One of the main concerns we've had around using Discourse is hosting it 
> ourselves but it does look like Discourse provides a free plan for open 
> source projects[2]. It has some limitations (not sure if they'd be an issue 
> for us?) but I've submitted an application to see if we qualify. I should 
> hear back in a couple days.
>

I suspect not, but it'd be an interesting surprise if we qualified.



--
真�gはいつも一つ！/ Always, there's only one truth!

___
Pulp-dev mailing list
Pulp-dev@redhat.com<mailto:Pulp-dev@redhat.com>
https://listman.redhat.com/mailman/listinfo/pulp-dev
_

Re: [Pulp-dev] [Pulp-list] Github Discussions

[David Davis]

If no one objects, I will be retiring Pulp's Github Discussions by
September 1st. It seems like the options we are considering going forward
are either staying on the mailing lists or moving to Discourse.

If you need something migrated over to Discourse from Github Discussions,
please let me know.

David


On Wed, Aug 11, 2021 at 9:55 AM Melanie Corr  wrote:

> Hi all,
>
> Based on your feedback, we now have a Pulp Community Discourse:
> https://discourse.pulpproject.org/
>
> This is still a continuation of our evaluation of whether to move away
> from the mailing list as a primary communication method. We need you to
> tell us if this is helpful.
>
> We will wrap up any discussions that remain open on our GitHub Discussions
> page and migrate any open discussions.
>
> I'm getting everything ready. Please feel free to make suggestions.
>
> Please join us over on Discourse!
>
> Melanie
>
> Ar Aoine 18 Meith 2021 ag 17:01, scríobh Melanie Corr :
>
>> Having been an admin on the Foreman Community Discourse for over a year,
>> I am +1 to a using Discourse for community conversations.
>> Greg Sutcliffe has data to prove the increase in community engagement
>> after the move.
>>
>> Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley > >:
>>
>>> And Matrix integration.
>>> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522
>>>
>>>
>>> On Thu, Jun 17, 2021 at 1:11 PM David Davis 
>>> wrote:
>>>
 I was rather surprised but Discourse did approve us for a free plan.
 The instance has been set up at https://pulp.discourse.group/. Feel
 free to try it out and experiment with it.

 However, the main limitation I see is the 50k pageviews per month
 limit. For reference, community.theforeman.org gets about 160-220k
 pageviews per month. So I think this would end up being a problem. I also
 checked with OSCI though and they apparently have experience with setting
 up Discourse instances for other open source communities. So I think they
 might be willing to set up a Discourse instance for us. I'm going to follow
 up and confirm.

 If we go this route, then we can also add the calendar plugin which
 would give us a public calendar like foreman has:

 https://community.theforeman.org/c/events/13/l/calendar

 I'm imagining we can use this to list events that are open to the
 public like triage/open floor and perhaps plugin team meetings.

 The more I use Discourse, the more I feel like it ticks all the boxes
 from granular notifications (weekly digests, ability to follow/unfollow
 categories, etc) to a mailing list mode users can enable to SSO integration
 with services like Github.

 David


 On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa  wrote:

> On Wed, Jun 16, 2021 at 7:21 PM David Davis 
> wrote:
> >
> > One of the main reasons we wanted to move off mailing lists is that
> signing up is inconvenient for users that may just want to ask a single
> question. But I agree that Github Discussions is not so great if users 
> want
> to periodically monitor news and discussions for a project like Pulp. I
> wonder perhaps if Discourse[0] would be a better fit (see Foreman's use of
> discourse as an example[1]). It provides a mailing list mode that users 
> can
> enable if they want to interact solely via email. And also, it also offers
> more granular control of notifications and auth with services like Github.
> >
>
> The Fedora mailing list system (HyperKitty) actually manages to strike
> a good balance here. You can sign in with OIDC/Social Login with
> Fedora, Google, etc. and post to a list and only be subscribed to that
> thread. Or you can subscribe to the whole list and do things like we
> do now.
>
> > One of the main concerns we've had around using Discourse is hosting
> it ourselves but it does look like Discourse provides a free plan for open
> source projects[2]. It has some limitations (not sure if they'd be an 
> issue
> for us?) but I've submitted an application to see if we qualify. I should
> hear back in a couple days.
> >
>
> I suspect not, but it'd be an interesting surprise if we qualified.
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
> ___
 Pulp-dev mailing list
 Pulp-dev@redhat.com
 https://listman.redhat.com/mailman/listinfo/pulp-dev

>>> ___
>>> Pulp-list mailing list
>>> pulp-l...@redhat.com
>>> https://listman.redhat.com/mailman/listinfo/pulp-list
>>
>>
>>
>> --
>>
>> Melanie Corr, RHCE
>>
>> Community Manager
>>
>> Red Hat 
>>
>> Remote, Ireland
>>
>> mc...@redhat.com
>> M: +353857774436 IM: mcorr
>> 
>>
>>
>
> --
>
> Melanie Corr, 

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Melanie Corr]

Hi all,

Based on your feedback, we now have a Pulp Community Discourse:
https://discourse.pulpproject.org/

This is still a continuation of our evaluation of whether to move away from
the mailing list as a primary communication method. We need you to tell us
if this is helpful.

We will wrap up any discussions that remain open on our GitHub Discussions
page and migrate any open discussions.

I'm getting everything ready. Please feel free to make suggestions.

Please join us over on Discourse!

Melanie

Ar Aoine 18 Meith 2021 ag 17:01, scríobh Melanie Corr :

> Having been an admin on the Foreman Community Discourse for over a year, I
> am +1 to a using Discourse for community conversations.
> Greg Sutcliffe has data to prove the increase in community engagement
> after the move.
>
> Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley :
>
>> And Matrix integration.
>> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522
>>
>>
>> On Thu, Jun 17, 2021 at 1:11 PM David Davis 
>> wrote:
>>
>>> I was rather surprised but Discourse did approve us for a free plan. The
>>> instance has been set up at https://pulp.discourse.group/. Feel free to
>>> try it out and experiment with it.
>>>
>>> However, the main limitation I see is the 50k pageviews per month limit.
>>> For reference, community.theforeman.org gets about 160-220k pageviews
>>> per month. So I think this would end up being a problem. I also checked
>>> with OSCI though and they apparently have experience with setting up
>>> Discourse instances for other open source communities. So I think they
>>> might be willing to set up a Discourse instance for us. I'm going to follow
>>> up and confirm.
>>>
>>> If we go this route, then we can also add the calendar plugin which
>>> would give us a public calendar like foreman has:
>>>
>>> https://community.theforeman.org/c/events/13/l/calendar
>>>
>>> I'm imagining we can use this to list events that are open to the public
>>> like triage/open floor and perhaps plugin team meetings.
>>>
>>> The more I use Discourse, the more I feel like it ticks all the boxes
>>> from granular notifications (weekly digests, ability to follow/unfollow
>>> categories, etc) to a mailing list mode users can enable to SSO integration
>>> with services like Github.
>>>
>>> David
>>>
>>>
>>> On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa  wrote:
>>>
 On Wed, Jun 16, 2021 at 7:21 PM David Davis 
 wrote:
 >
 > One of the main reasons we wanted to move off mailing lists is that
 signing up is inconvenient for users that may just want to ask a single
 question. But I agree that Github Discussions is not so great if users want
 to periodically monitor news and discussions for a project like Pulp. I
 wonder perhaps if Discourse[0] would be a better fit (see Foreman's use of
 discourse as an example[1]). It provides a mailing list mode that users can
 enable if they want to interact solely via email. And also, it also offers
 more granular control of notifications and auth with services like Github.
 >

 The Fedora mailing list system (HyperKitty) actually manages to strike
 a good balance here. You can sign in with OIDC/Social Login with
 Fedora, Google, etc. and post to a list and only be subscribed to that
 thread. Or you can subscribe to the whole list and do things like we
 do now.

 > One of the main concerns we've had around using Discourse is hosting
 it ourselves but it does look like Discourse provides a free plan for open
 source projects[2]. It has some limitations (not sure if they'd be an issue
 for us?) but I've submitted an application to see if we qualify. I should
 hear back in a couple days.
 >

 I suspect not, but it'd be an interesting surprise if we qualified.



 --
 真実はいつも一つ！/ Always, there's only one truth!

 ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://listman.redhat.com/mailman/listinfo/pulp-dev
>>>
>> ___
>> Pulp-list mailing list
>> pulp-l...@redhat.com
>> https://listman.redhat.com/mailman/listinfo/pulp-list
>
>
>
> --
>
> Melanie Corr, RHCE
>
> Community Manager
>
> Red Hat 
>
> Remote, Ireland
>
> mc...@redhat.com
> M: +353857774436 IM: mcorr
> 
>
>

-- 

Melanie Corr, RHCE

Community Manager

Red Hat 

Remote, Ireland

mc...@redhat.com
M: +353857774436 IM: mcorr

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Melanie Corr]

Having been an admin on the Foreman Community Discourse for over a year, I
am +1 to a using Discourse for community conversations.
Greg Sutcliffe has data to prove the increase in community engagement after
the move.

Ar Aoine 18 Meith 2021 ag 16:33, scríobh Daniel Alley :

> And Matrix integration.
> https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522
>
>
> On Thu, Jun 17, 2021 at 1:11 PM David Davis  wrote:
>
>> I was rather surprised but Discourse did approve us for a free plan. The
>> instance has been set up at https://pulp.discourse.group/. Feel free to
>> try it out and experiment with it.
>>
>> However, the main limitation I see is the 50k pageviews per month limit.
>> For reference, community.theforeman.org gets about 160-220k pageviews
>> per month. So I think this would end up being a problem. I also checked
>> with OSCI though and they apparently have experience with setting up
>> Discourse instances for other open source communities. So I think they
>> might be willing to set up a Discourse instance for us. I'm going to follow
>> up and confirm.
>>
>> If we go this route, then we can also add the calendar plugin which would
>> give us a public calendar like foreman has:
>>
>> https://community.theforeman.org/c/events/13/l/calendar
>>
>> I'm imagining we can use this to list events that are open to the public
>> like triage/open floor and perhaps plugin team meetings.
>>
>> The more I use Discourse, the more I feel like it ticks all the boxes
>> from granular notifications (weekly digests, ability to follow/unfollow
>> categories, etc) to a mailing list mode users can enable to SSO integration
>> with services like Github.
>>
>> David
>>
>>
>> On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa  wrote:
>>
>>> On Wed, Jun 16, 2021 at 7:21 PM David Davis 
>>> wrote:
>>> >
>>> > One of the main reasons we wanted to move off mailing lists is that
>>> signing up is inconvenient for users that may just want to ask a single
>>> question. But I agree that Github Discussions is not so great if users want
>>> to periodically monitor news and discussions for a project like Pulp. I
>>> wonder perhaps if Discourse[0] would be a better fit (see Foreman's use of
>>> discourse as an example[1]). It provides a mailing list mode that users can
>>> enable if they want to interact solely via email. And also, it also offers
>>> more granular control of notifications and auth with services like Github.
>>> >
>>>
>>> The Fedora mailing list system (HyperKitty) actually manages to strike
>>> a good balance here. You can sign in with OIDC/Social Login with
>>> Fedora, Google, etc. and post to a list and only be subscribed to that
>>> thread. Or you can subscribe to the whole list and do things like we
>>> do now.
>>>
>>> > One of the main concerns we've had around using Discourse is hosting
>>> it ourselves but it does look like Discourse provides a free plan for open
>>> source projects[2]. It has some limitations (not sure if they'd be an issue
>>> for us?) but I've submitted an application to see if we qualify. I should
>>> hear back in a couple days.
>>> >
>>>
>>> I suspect not, but it'd be an interesting surprise if we qualified.
>>>
>>>
>>>
>>> --
>>> 真実はいつも一つ！/ Always, there's only one truth!
>>>
>>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://listman.redhat.com/mailman/listinfo/pulp-dev
>>
> ___
> Pulp-list mailing list
> pulp-l...@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-list



-- 

Melanie Corr, RHCE

Community Manager

Red Hat 

Remote, Ireland

mc...@redhat.com
M: +353857774436 IM: mcorr

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Daniel Alley]

And Matrix integration.
https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522


On Thu, Jun 17, 2021 at 1:11 PM David Davis  wrote:

> I was rather surprised but Discourse did approve us for a free plan. The
> instance has been set up at https://pulp.discourse.group/. Feel free to
> try it out and experiment with it.
>
> However, the main limitation I see is the 50k pageviews per month limit.
> For reference, community.theforeman.org gets about 160-220k pageviews per
> month. So I think this would end up being a problem. I also checked with
> OSCI though and they apparently have experience with setting up Discourse
> instances for other open source communities. So I think they might be
> willing to set up a Discourse instance for us. I'm going to follow up and
> confirm.
>
> If we go this route, then we can also add the calendar plugin which would
> give us a public calendar like foreman has:
>
> https://community.theforeman.org/c/events/13/l/calendar
>
> I'm imagining we can use this to list events that are open to the public
> like triage/open floor and perhaps plugin team meetings.
>
> The more I use Discourse, the more I feel like it ticks all the boxes from
> granular notifications (weekly digests, ability to follow/unfollow
> categories, etc) to a mailing list mode users can enable to SSO integration
> with services like Github.
>
> David
>
>
> On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa  wrote:
>
>> On Wed, Jun 16, 2021 at 7:21 PM David Davis 
>> wrote:
>> >
>> > One of the main reasons we wanted to move off mailing lists is that
>> signing up is inconvenient for users that may just want to ask a single
>> question. But I agree that Github Discussions is not so great if users want
>> to periodically monitor news and discussions for a project like Pulp. I
>> wonder perhaps if Discourse[0] would be a better fit (see Foreman's use of
>> discourse as an example[1]). It provides a mailing list mode that users can
>> enable if they want to interact solely via email. And also, it also offers
>> more granular control of notifications and auth with services like Github.
>> >
>>
>> The Fedora mailing list system (HyperKitty) actually manages to strike
>> a good balance here. You can sign in with OIDC/Social Login with
>> Fedora, Google, etc. and post to a list and only be subscribed to that
>> thread. Or you can subscribe to the whole list and do things like we
>> do now.
>>
>> > One of the main concerns we've had around using Discourse is hosting it
>> ourselves but it does look like Discourse provides a free plan for open
>> source projects[2]. It has some limitations (not sure if they'd be an issue
>> for us?) but I've submitted an application to see if we qualify. I should
>> hear back in a couple days.
>> >
>>
>> I suspect not, but it'd be an interesting surprise if we qualified.
>>
>>
>>
>> --
>> 真実はいつも一つ！/ Always, there's only one truth!
>>
>> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[David Davis]

I was rather surprised but Discourse did approve us for a free plan. The
instance has been set up at https://pulp.discourse.group/. Feel free to try
it out and experiment with it.

However, the main limitation I see is the 50k pageviews per month limit.
For reference, community.theforeman.org gets about 160-220k pageviews per
month. So I think this would end up being a problem. I also checked with
OSCI though and they apparently have experience with setting up Discourse
instances for other open source communities. So I think they might be
willing to set up a Discourse instance for us. I'm going to follow up and
confirm.

If we go this route, then we can also add the calendar plugin which would
give us a public calendar like foreman has:

https://community.theforeman.org/c/events/13/l/calendar

I'm imagining we can use this to list events that are open to the public
like triage/open floor and perhaps plugin team meetings.

The more I use Discourse, the more I feel like it ticks all the boxes from
granular notifications (weekly digests, ability to follow/unfollow
categories, etc) to a mailing list mode users can enable to SSO integration
with services like Github.

David


On Wed, Jun 16, 2021 at 7:59 PM Neal Gompa  wrote:

> On Wed, Jun 16, 2021 at 7:21 PM David Davis  wrote:
> >
> > One of the main reasons we wanted to move off mailing lists is that
> signing up is inconvenient for users that may just want to ask a single
> question. But I agree that Github Discussions is not so great if users want
> to periodically monitor news and discussions for a project like Pulp. I
> wonder perhaps if Discourse[0] would be a better fit (see Foreman's use of
> discourse as an example[1]). It provides a mailing list mode that users can
> enable if they want to interact solely via email. And also, it also offers
> more granular control of notifications and auth with services like Github.
> >
>
> The Fedora mailing list system (HyperKitty) actually manages to strike
> a good balance here. You can sign in with OIDC/Social Login with
> Fedora, Google, etc. and post to a list and only be subscribed to that
> thread. Or you can subscribe to the whole list and do things like we
> do now.
>
> > One of the main concerns we've had around using Discourse is hosting it
> ourselves but it does look like Discourse provides a free plan for open
> source projects[2]. It has some limitations (not sure if they'd be an issue
> for us?) but I've submitted an application to see if we qualify. I should
> hear back in a couple days.
> >
>
> I suspect not, but it'd be an interesting surprise if we qualified.
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Neal Gompa]

On Wed, Jun 16, 2021 at 7:21 PM David Davis  wrote:
>
> One of the main reasons we wanted to move off mailing lists is that signing 
> up is inconvenient for users that may just want to ask a single question. But 
> I agree that Github Discussions is not so great if users want to periodically 
> monitor news and discussions for a project like Pulp. I wonder perhaps if 
> Discourse[0] would be a better fit (see Foreman's use of discourse as an 
> example[1]). It provides a mailing list mode that users can enable if they 
> want to interact solely via email. And also, it also offers more granular 
> control of notifications and auth with services like Github.
>

The Fedora mailing list system (HyperKitty) actually manages to strike
a good balance here. You can sign in with OIDC/Social Login with
Fedora, Google, etc. and post to a list and only be subscribed to that
thread. Or you can subscribe to the whole list and do things like we
do now.

> One of the main concerns we've had around using Discourse is hosting it 
> ourselves but it does look like Discourse provides a free plan for open 
> source projects[2]. It has some limitations (not sure if they'd be an issue 
> for us?) but I've submitted an application to see if we qualify. I should 
> hear back in a couple days.
>

I suspect not, but it'd be an interesting surprise if we qualified.



-- 
真実はいつも一つ！/ Always, there's only one truth!


___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[David Davis]

One of the main reasons we wanted to move off mailing lists is that signing
up is inconvenient for users that may just want to ask a single question.
But I agree that Github Discussions is not so great if users want to
periodically monitor news and discussions for a project like Pulp. I wonder
perhaps if Discourse[0] would be a better fit (see Foreman's use of
discourse as an example[1]). It provides a mailing list mode that users can
enable if they want to interact solely via email. And also, it also offers
more granular control of notifications and auth with services like Github.

One of the main concerns we've had around using Discourse is hosting it
ourselves but it does look like Discourse provides a free plan for open
source projects[2]. It has some limitations (not sure if they'd be an issue
for us?) but I've submitted an application to see if we qualify. I should
hear back in a couple days.

[0] https://www.discourse.org/
[1] https://community.theforeman.org/
[2] https://free.discourse.group/

David


On Wed, Jun 16, 2021 at 5:31 PM James Cassell 
wrote:

> On Wed, Jun 16, 2021, at 3:12 PM, Neal Gompa wrote:
> > On Wed, Jun 16, 2021 at 11:59 AM David Davis 
> wrote:
> > >
> > > Yesterday at open floor, we discussed decommissioning pulp-dev list in
> favor of of using Github Discussions[0] for developer discussions.
> > >
> > > If there are no objections, I plan to decommission the pulp-dev list
> next week.
> > >
> > > [0] https://github.com/pulp/community/discussions
> > >
> >
> > I don't know how I'd be able to keep track of what's going on with
> > GitHub Discussions. With mailing list discussions, it's relatively
> > easy for me to see the topics as they're coming in and participate off
> > the cuff. With GitHub Discussions, it doesn't seem possible for me to
> > do that.
> >
> >
> >
>
> Same here.  I prefer the e-mail list.  I almost never see the github spam
> messages because I get literally thousands...
>
> V/r,
> James Cassell
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[James Cassell]

On Wed, Jun 16, 2021, at 3:12 PM, Neal Gompa wrote:
> On Wed, Jun 16, 2021 at 11:59 AM David Davis  wrote:
> >
> > Yesterday at open floor, we discussed decommissioning pulp-dev list in 
> > favor of of using Github Discussions[0] for developer discussions.
> >
> > If there are no objections, I plan to decommission the pulp-dev list next 
> > week.
> >
> > [0] https://github.com/pulp/community/discussions
> >
> 
> I don't know how I'd be able to keep track of what's going on with
> GitHub Discussions. With mailing list discussions, it's relatively
> easy for me to see the topics as they're coming in and participate off
> the cuff. With GitHub Discussions, it doesn't seem possible for me to
> do that.
> 
> 
> 

Same here.  I prefer the e-mail list.  I almost never see the github spam 
messages because I get literally thousands...

V/r,
James Cassell

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Daniel Alley]

>
> It's pretty hard to do filtering of GitHub mail...


I can't disagree with that.

On Wed, Jun 16, 2021 at 4:35 PM Neal Gompa  wrote:

> Well, let's see if that works. Another concern I have is about
> filtering stuff from discussions in Gmail. It's pretty hard to do
> filtering of GitHub mail...
>
> On Wed, Jun 16, 2021 at 4:29 PM David Davis  wrote:
> >
> > If you watch the repo, you should be able to get notifications when
> there's new activity?
> >
> > David
> >
> >
> > On Wed, Jun 16, 2021 at 3:13 PM Neal Gompa  wrote:
> >>
> >> On Wed, Jun 16, 2021 at 11:59 AM David Davis 
> wrote:
> >> >
> >> > Yesterday at open floor, we discussed decommissioning pulp-dev list
> in favor of of using Github Discussions[0] for developer discussions.
> >> >
> >> > If there are no objections, I plan to decommission the pulp-dev list
> next week.
> >> >
> >> > [0] https://github.com/pulp/community/discussions
> >> >
> >>
> >> I don't know how I'd be able to keep track of what's going on with
> >> GitHub Discussions. With mailing list discussions, it's relatively
> >> easy for me to see the topics as they're coming in and participate off
> >> the cuff. With GitHub Discussions, it doesn't seem possible for me to
> >> do that.
> >>
> >>
> >>
> >> --
> >> 真実はいつも一つ！/ Always, there's only one truth!
> >>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[David Davis]

If you watch the repo, you should be able to get notifications when there's
new activity?

David


On Wed, Jun 16, 2021 at 3:13 PM Neal Gompa  wrote:

> On Wed, Jun 16, 2021 at 11:59 AM David Davis 
> wrote:
> >
> > Yesterday at open floor, we discussed decommissioning pulp-dev list in
> favor of of using Github Discussions[0] for developer discussions.
> >
> > If there are no objections, I plan to decommission the pulp-dev list
> next week.
> >
> > [0] https://github.com/pulp/community/discussions
> >
>
> I don't know how I'd be able to keep track of what's going on with
> GitHub Discussions. With mailing list discussions, it's relatively
> easy for me to see the topics as they're coming in and participate off
> the cuff. With GitHub Discussions, it doesn't seem possible for me to
> do that.
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Neal Gompa]

Well, let's see if that works. Another concern I have is about
filtering stuff from discussions in Gmail. It's pretty hard to do
filtering of GitHub mail...

On Wed, Jun 16, 2021 at 4:29 PM David Davis  wrote:
>
> If you watch the repo, you should be able to get notifications when there's 
> new activity?
>
> David
>
>
> On Wed, Jun 16, 2021 at 3:13 PM Neal Gompa  wrote:
>>
>> On Wed, Jun 16, 2021 at 11:59 AM David Davis  wrote:
>> >
>> > Yesterday at open floor, we discussed decommissioning pulp-dev list in 
>> > favor of of using Github Discussions[0] for developer discussions.
>> >
>> > If there are no objections, I plan to decommission the pulp-dev list next 
>> > week.
>> >
>> > [0] https://github.com/pulp/community/discussions
>> >
>>
>> I don't know how I'd be able to keep track of what's going on with
>> GitHub Discussions. With mailing list discussions, it's relatively
>> easy for me to see the topics as they're coming in and participate off
>> the cuff. With GitHub Discussions, it doesn't seem possible for me to
>> do that.
>>
>>
>>
>> --
>> 真実はいつも一つ！/ Always, there's only one truth!
>>


-- 
真実はいつも一つ！/ Always, there's only one truth!


___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Neal Gompa]

On Wed, Jun 16, 2021 at 11:59 AM David Davis  wrote:
>
> Yesterday at open floor, we discussed decommissioning pulp-dev list in favor 
> of of using Github Discussions[0] for developer discussions.
>
> If there are no objections, I plan to decommission the pulp-dev list next 
> week.
>
> [0] https://github.com/pulp/community/discussions
>

I don't know how I'd be able to keep track of what's going on with
GitHub Discussions. With mailing list discussions, it's relatively
easy for me to see the topics as they're coming in and participate off
the cuff. With GitHub Discussions, it doesn't seem possible for me to
do that.



-- 
真実はいつも一つ！/ Always, there's only one truth!


___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Grant Gainey]

There are a few places in the docs where we reference pulp-dev@ , that
should be changed as part of/before we pull the plug.

contributing/index.rst:  * through the developer mailing list (``
pulp-dev@redhat.com``)
plugins/plugin-writer/concepts/index.rst:maintainers either through the
developer mailing list (``pulp-dev@redhat.com``) or on Freenode in
plugins/index.rst:   Are we missing a plugin? Let us know via the
pulp-dev@redhat.com mailing list.

On Wed, Jun 16, 2021 at 11:55 AM David Davis  wrote:

> Yesterday at open floor, we discussed decommissioning pulp-dev list in
> favor of of using Github Discussions[0] for developer discussions.
>
> If there are no objections, I plan to decommission the pulp-dev list next
> week.
>
> [0] https://github.com/pulp/community/discussions
>
> David
>
>
> On Thu, Jun 3, 2021 at 11:01 AM Brian Bouterse 
> wrote:
>
>> I did this also for the pulpcore meeting:
>> https://github.com/pulp/community/discussions/8
>>
>> My format was a little different, but the same idea.
>>
>> On Thu, Jun 3, 2021 at 10:13 AM Grant Gainey  wrote:
>>
>>> On Thu, Jun 3, 2021 at 9:40 AM David Davis 
>>> wrote:
>>>
 Based on feedback, I've moved discussions to its own repo:
 https://github.com/pulp/community/discussions.

>>>
>>> Brillliant!
>>>
>>> One discovery I made this week - for 'Meetings' threads that exist to
>>> have meeting-minutes posted, the first entry should be a description of
>>> what the meeting you're recording is for, and each set of minutes should be
>>> a comment. This lets the reader sort by "Newest" and get
>>> most-recent-minutes-first.The initial message in a discussion is always at
>>> the top, no matter how you sort - so if it's your first meeting-minutes,
>>> they'll always be first.
>>>
>>> I redid the katello/pulp and community/pulp integration
>>> discussion-threads (in their new location) in light of this, apologies to
>>> anyone who got some notification-spam as a result this morning.
>>>
>>>- https://github.com/pulp/community/discussions/7
>>>- https://github.com/pulp/community/discussions/4
>>>
>>> G
>>>

 David


 On Tue, May 25, 2021 at 1:49 PM David Davis 
 wrote:

> We've heard from the community about the amount of friction involved
> in getting help with Pulp and one of the areas I think we could improve is
> user communications. We currently run two mailing lists: pulp-list and
> pulp-dev.
>
> At today's open floor meeting, we talked about using Github's new
> Discussions feature[0] to host these conversations instead. I've set up a
> Discussion against pulpcore[1] for us to try but here's also an example of
> a project that has a lot of threads[2].
>
> I think the consensus was that we'd just keep pulpcore as our one and
> only Github Discussions instance, which would serve as a replacement for
> pulp-list and pulp-dev. I'd propose that we try this out for a bit and
> eventually decommission our mailing lists.
>
> [0] https://docs.github.com/en/discussions
> [1] https://github.com/pulp/pulpcore/discussions
> [2] https://github.com/vercel/next.js/discussions
>
> David
>
 ___
 Pulp-list mailing list
 pulp-l...@redhat.com
 https://listman.redhat.com/mailman/listinfo/pulp-list
>>>
>>>
>>>
>>> --
>>> Grant Gainey
>>> Principal Software Engineer, Red Hat System Management Engineering
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://listman.redhat.com/mailman/listinfo/pulp-dev
>>>
>>

-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Brian Bouterse]

I did this also for the pulpcore meeting:
https://github.com/pulp/community/discussions/8

My format was a little different, but the same idea.

On Thu, Jun 3, 2021 at 10:13 AM Grant Gainey  wrote:

> On Thu, Jun 3, 2021 at 9:40 AM David Davis  wrote:
>
>> Based on feedback, I've moved discussions to its own repo:
>> https://github.com/pulp/community/discussions.
>>
>
> Brillliant!
>
> One discovery I made this week - for 'Meetings' threads that exist to have
> meeting-minutes posted, the first entry should be a description of what the
> meeting you're recording is for, and each set of minutes should be a
> comment. This lets the reader sort by "Newest" and get
> most-recent-minutes-first.The initial message in a discussion is always at
> the top, no matter how you sort - so if it's your first meeting-minutes,
> they'll always be first.
>
> I redid the katello/pulp and community/pulp integration discussion-threads
> (in their new location) in light of this, apologies to anyone who got some
> notification-spam as a result this morning.
>
>- https://github.com/pulp/community/discussions/7
>- https://github.com/pulp/community/discussions/4
>
> G
>
>>
>> David
>>
>>
>> On Tue, May 25, 2021 at 1:49 PM David Davis 
>> wrote:
>>
>>> We've heard from the community about the amount of friction involved in
>>> getting help with Pulp and one of the areas I think we could improve is
>>> user communications. We currently run two mailing lists: pulp-list and
>>> pulp-dev.
>>>
>>> At today's open floor meeting, we talked about using Github's new
>>> Discussions feature[0] to host these conversations instead. I've set up a
>>> Discussion against pulpcore[1] for us to try but here's also an example of
>>> a project that has a lot of threads[2].
>>>
>>> I think the consensus was that we'd just keep pulpcore as our one and
>>> only Github Discussions instance, which would serve as a replacement for
>>> pulp-list and pulp-dev. I'd propose that we try this out for a bit and
>>> eventually decommission our mailing lists.
>>>
>>> [0] https://docs.github.com/en/discussions
>>> [1] https://github.com/pulp/pulpcore/discussions
>>> [2] https://github.com/vercel/next.js/discussions
>>>
>>> David
>>>
>> ___
>> Pulp-list mailing list
>> pulp-l...@redhat.com
>> https://listman.redhat.com/mailman/listinfo/pulp-list
>
>
>
> --
> Grant Gainey
> Principal Software Engineer, Red Hat System Management Engineering
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] [Pulp-list] Github Discussions

[Grant Gainey]

On Thu, Jun 3, 2021 at 9:40 AM David Davis  wrote:

> Based on feedback, I've moved discussions to its own repo:
> https://github.com/pulp/community/discussions.
>

Brillliant!

One discovery I made this week - for 'Meetings' threads that exist to have
meeting-minutes posted, the first entry should be a description of what the
meeting you're recording is for, and each set of minutes should be a
comment. This lets the reader sort by "Newest" and get
most-recent-minutes-first.The initial message in a discussion is always at
the top, no matter how you sort - so if it's your first meeting-minutes,
they'll always be first.

I redid the katello/pulp and community/pulp integration discussion-threads
(in their new location) in light of this, apologies to anyone who got some
notification-spam as a result this morning.

   - https://github.com/pulp/community/discussions/7
   - https://github.com/pulp/community/discussions/4

G

>
> David
>
>
> On Tue, May 25, 2021 at 1:49 PM David Davis  wrote:
>
>> We've heard from the community about the amount of friction involved in
>> getting help with Pulp and one of the areas I think we could improve is
>> user communications. We currently run two mailing lists: pulp-list and
>> pulp-dev.
>>
>> At today's open floor meeting, we talked about using Github's new
>> Discussions feature[0] to host these conversations instead. I've set up a
>> Discussion against pulpcore[1] for us to try but here's also an example of
>> a project that has a lot of threads[2].
>>
>> I think the consensus was that we'd just keep pulpcore as our one and
>> only Github Discussions instance, which would serve as a replacement for
>> pulp-list and pulp-dev. I'd propose that we try this out for a bit and
>> eventually decommission our mailing lists.
>>
>> [0] https://docs.github.com/en/discussions
>> [1] https://github.com/pulp/pulpcore/discussions
>> [2] https://github.com/vercel/next.js/discussions
>>
>> David
>>
> ___
> Pulp-list mailing list
> pulp-l...@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-list



-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev