[doc8] future development and maintenance
It seems that the doc8 project is lacking some love, regardless the fact that is used by >90 projects from opendev.org. https://review.opendev.org/#/q/project:x/doc8 Last merge and release was more than 2 years ago and no reviews were performed either. I think it would be in our interest to assure that doc8 maintenance continues and that we can keep it usable. I would like to propose extenting the list of cores from the current 4 ones that I already listed in CC with 3 more, so we can effectively make a change that gets merged and later released (anyone willing to help?) If current cores agree, I would be happy to help with maintenance. I estimate that the effort needed would likely be less than 1h/month in longer term. If there is a desire to move it to github/travis, I would not mind either. Thanks Sorin Sbarnea Red Hat TripleO CI
On Thu, 2019-07-11 at 12:01 +0100, Sorin Sbarnea wrote:
It seems that the doc8 project is lacking some love, regardless the fact that is used by >90 projects from opendev.org.
https://review.opendev.org/#/q/project:x/doc8
Last merge and release was more than 2 years ago and no reviews were performed either.
I think it would be in our interest to assure that doc8 maintenance continues and that we can keep it usable.
I would like to propose extenting the list of cores from the current 4 ones that I already listed in CC with 3 more, so we can effectively make a change that gets merged and later released (anyone willing to help?)
If current cores agree, I would be happy to help with maintenance. I estimate that the effort needed would likely be less than 1h/month in longer term. If there is a desire to move it to github/travis, I would not mind either.
I'd be tentatively interested in helping out here, though it's not as if I don't already have a lot on my plate :) I wonder if this might have better success outside of OpenStack, perhaps in the sphinx-doc or sphinx-contrib GitHub repo? Stephen
Thanks Sorin Sbarnea Red Hat TripleO CI
As 2/4 emails returned as invalid accounts, my hopes to hear back are getting lower and lower (tried few other channels too). I also believe that doc8 may be better suited outside OpenStack and especially under GitHub due to extra visibility to other developers. So temporary I created a fork at https://github.com/pycontribs/doc8 when I enabled travis and merged few fixes. If we do not hear back I propose to use ^ for future development and maintenance. If Sphinx organization wants to adopt it, even better, it can be transferred without loosing any tickets/PRs/... To be able to make a new release on https://pypi.org/project/doc8/ from Travis, I would need to have the "pycontribs" user added as maintainer, or I could always attempt to publish it as "doc9" but I would prefer to avoid a schism. /sorin
On 11 Jul 2019, at 17:10, Stephen Finucane <sfinucan@redhat.com> wrote:
On Thu, 2019-07-11 at 12:01 +0100, Sorin Sbarnea wrote:
It seems that the doc8 project is lacking some love, regardless the fact that is used by >90 projects from opendev.org.
https://review.opendev.org/#/q/project:x/doc8
Last merge and release was more than 2 years ago and no reviews were performed either.
I think it would be in our interest to assure that doc8 maintenance continues and that we can keep it usable.
I would like to propose extenting the list of cores from the current 4 ones that I already listed in CC with 3 more, so we can effectively make a change that gets merged and later released (anyone willing to help?)
If current cores agree, I would be happy to help with maintenance. I estimate that the effort needed would likely be less than 1h/month in longer term. If there is a desire to move it to github/travis, I would not mind either.
I'd be tentatively interested in helping out here, though it's not as if I don't already have a lot on my plate :)
I wonder if this might have better success outside of OpenStack, perhaps in the sphinx-doc or sphinx-contrib GitHub repo?
Stephen
Thanks Sorin Sbarnea Red Hat TripleO CI
On Thu, 2019-07-11 at 17:10 +0100, Stephen Finucane wrote:
On Thu, 2019-07-11 at 12:01 +0100, Sorin Sbarnea wrote:
It seems that the doc8 project is lacking some love, regardless the fact that is used by >90 projects from opendev.org.
https://review.opendev.org/#/q/project:x/doc8
Last merge and release was more than 2 years ago and no reviews were performed either.
I think it would be in our interest to assure that doc8 maintenance continues and that we can keep it usable.
I would like to propose extenting the list of cores from the current 4 ones that I already listed in CC with 3 more, so we can effectively make a change that gets merged and later released (anyone willing to help?)
If current cores agree, I would be happy to help with maintenance. I estimate that the effort needed would likely be less than 1h/month in longer term. If there is a desire to move it to github/travis, I would not mind either.
I'd be tentatively interested in helping out here, though it's not as if I don't already have a lot on my plate :)
I wonder if this might have better success outside of OpenStack, perhaps in the sphinx-doc or sphinx-contrib GitHub repo?
Following up on this, the PyCQA organisation on GitHub have kindly accepted our request to move doc8 there [1]. I'd like to start with the paperwork of moving this across shortly and work with infra to get PyPI and the likes configured. However, if anyone has any objections to this plan please making them known now. Cheers, Stephen [1] https://mail.python.org/pipermail/code-quality/2019-July/001112.html
participants (2)
-
Sorin Sbarnea
-
Stephen Finucane