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 <davidda...@redhat.com> 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 <bmbou...@redhat.com> > 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 <ggai...@redhat.com> wrote: >> >>> On Thu, Jun 3, 2021 at 9:40 AM David Davis <davidda...@redhat.com> >>> 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 <davidda...@redhat.com> >>>> 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
