> "ecosystem" is nice in that it doesn't limit it to macros/scripts/whatever
> and is pretty future-proof.
>
> The only thing I'm mulling about is the order: another possibility could be
> "rpm-ecosystem-python" so assuming there will be multiple such projects for
> different languages they line up nicely next to each other in eg file lists.
> But then it has other downsides, and I certainly dont want this to get stuck
> on bikeshedding over the name
I prefer this one for several reasons. One of them is that if we decide to
have an `rpm-ecosystem` repository and/or project, this name would fit much
better.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1607#issuecomment-808272046
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
