https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #2 from Shyamsundar ---
My thoughts:
Let's not do it after 2 weeks, let it happen as the review is posted.
Also, let's add MAINTAINERS as per their areas of responsibility, that way a
patch does not get 20 reviewers, but rather 2
https://bugzilla.redhat.com/show_bug.cgi?id=1584992
--- Comment #2 from Nigel Babu ---
pep8 issues: 3K
pylint issues: 12K
pylint python3 issues: 370
It's not worth running a CI unless we can fix them or tweak the config so we
care about the right things.
--
You are receiving this mail becaus
https://bugzilla.redhat.com/show_bug.cgi?id=1584992
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #1 from Ni
https://bugzilla.redhat.com/show_bug.cgi?id=1585055
Nigel Babu changed:
What|Removed |Added
Status|NEW |CLOSED
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=1584998
--- Comment #1 from Amar Tumballi ---
Notice that this has a problem that we can get into infinite loop of warning
people every 2weeks of inactivity, but never reaching 90days. Hence we need a
mechanism to identify the patches only once, ie, f
https://bugzilla.redhat.com/show_bug.cgi?id=1585055
Bug ID: 1585055
Summary: Moving parsefuse to gluster project on Github
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: b...@gluster.org
Rep