I didn't say young projects we're categorically disallowed. I'm disinclined to inviting them for the reasons I listed in my last email. I don't see the benefits for the project or its creator (in this case you). That's why I asked what benefits you were expecting.

Given how very loosely the group of projects is organized and the almost complete lack of cross-project coordination/contribution except from 1 or 2 people, it doesn't make sense to add projects to the organization just because they are in the same vein. It's easy for you to completely abandon your project in the PyCQA and then we become the code quality tooling graveyard.

That's fine, I don't consider us a real authority on anything really. I'm tempted to rename from Authority to Amalgamation as it's more accurate.

Sent from my phone with my typo-happy thumbs. Please excuse my brevity

On Mon, Sep 28, 2020, 12:32 Batuhan Taskaya <isidentical@gmail.com> wrote:
I wasn't aware that 'young' projects aren't allowed, if there are strict time or user requirements, it would be great if you can supply them. 


All I thought was, this is a code quality tool and would be a consistent idea to have it under the umbrella of the PyCQA.

On Mon, Sep 28, 2020, 8:21 PM Ian Stapleton Cordasco <graffatcolmingov@gmail.com> wrote:
So generally speaking I'm not in favor of such young projects being moved into the organization so early in their lifecycle.

There are zero realized benefits for being in the organization for such a low-traffic, low-collaborator count project in my opinion.

New contributors don't magically show up to work on projects they've never used before and I haven't seen people adopt projects simply for being in the org.

What's your motivation for migrating into an organization with the above context?

Sent from my phone with my typo-happy thumbs. Please excuse my brevity

On Mon, Sep 28, 2020, 11:09 Thomas Grainger <tagrain@gmail.com> wrote:
I'm seeing https://teyit.org/

Thomas Grainger

On Mon, 28 Sep 2020 at 17:07, Batuhan Taskaya <isidentical@gmail.com> wrote:
>
> Would you enlighten me more about that (I didn't see any teyit's in
> python tooling ecosystem)? If so, we can go through a name changing
> process
>
> On Mon, Sep 28, 2020 at 6:01 PM Thomas Grainger <tagrain@gmail.com> wrote:
> >
> > I'm generally in favour - but I think teyit is a trademark
> > _______________________________________________
> > code-quality mailing list -- code-quality@python.org
> > To unsubscribe send an email to code-quality-leave@python.org
> > https://mail.python.org/mailman3/lists/code-quality.python.org/
> > Member address: isidentical@gmail.com
_______________________________________________
code-quality mailing list -- code-quality@python.org
To unsubscribe send an email to code-quality-leave@python.org
https://mail.python.org/mailman3/lists/code-quality.python.org/
Member address: graffatcolmingov@gmail.com