[pytest-dev] Using meta project for organization wide issues

[Bruno Oliveira]

Hi everyone,

The Discussions feature is now enabled.

Let's see how best we can use this feature to declutter the issue tracker
if possible, and create a good knowledge base of problems/solutions.

Cheers,

On Wed, Sep 9, 2020 at 8:32 AM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Thanks Sorin for bringing this up.
>
> I've posted a request to enable the Discussions feature for
> pytest-dev/pytest:
> https://github.community/t/can-one-apply-for-github-discussions-beta/121120/162?u=nicoddemus
>
> Cheers,
> Bruno.
>
> On Tue, Sep 8, 2020 at 11:08 AM Sorin Sbarnea <ssbarnea at redhat.com> wrote:
>
>> My intent was to separate organization threads from the development ones,
>> not to deprecate the mailing list.
>>
>> I do not think that an issue tracker is good for **discussions** as in
>> open-ended subjects, or even for support. In fact using the issue tracker
>> for user support is really bad as it make maintenance much harder.
>>
>> Still, there is something new from github called discussions which is a
>> very basic forum directly integrated into github.
>>
>> You can see it as
>> https://github.com/ansible-community/molecule/discussions -- not very
>> active but functional.
>>
>> Discussions are in private beta, and we need to ask github to enable
>> them.
>>
>> If anyone wants to enable it for "pytest", I could try to pull some
>> strings. If desired, an org/repo admin should ask for it at
>> https://github.community/t/can-one-apply-for-github-discussions-beta/121120
>>
>>
>> > On 8 Sep 2020, at 14:54, Arseniy Antonov <arseny.antonov at gmail.com>
>> wrote:
>> >
>> > Hi Sorin,
>> > So basically you want to move all projects related discussions from
>> maillists to the github issues - did I get you correct?  If the answer is
>> yes then from my perspective it's a really nice idea.
>> > Also a lot of communities have #slack accounts - have you ever thought
>> about the slack/(any other messenger) group for pytest community?
>> >
>> > вт, 8 сент. 2020 г. в 16:07, Sorin Sbarnea <ssbarnea at redhat.com>:
>> > About two weeks ago I created the https://github.com/pytest-dev/meta
>> project with the hope of being used for tracking organization wide issues
>> (and avoid having to pollute our main pytest project).
>> >
>> > I seen use of "meta" on many github organizations for the same purpose,
>> "stuff" that is unrelated to the code of a specific repository. I hope it
>> will become popular. I do also see other benefits as used of a mailing list
>> sets a higher barrier for people that are not yet fully dedicated (we do
>> all know experienced the "Ahh not another ML!" sensation).
>> >
>> > Early today I also added the first ticket, the proposal for adoption of
>> the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1
>> and comment there.
>> >
>> > Cheers,
>> > Sorin
>> >
>> > _______________________________________________
>> > pytest-dev mailing list
>> > pytest-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>> >
>> >
>> > --
>> > --------------------------
>> > Regards.
>> > Arseny Antonov
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200910/7fbf4a09/attachment.html>