Re: Make Development More Accessible

2019-08-12 Thread '1337 Shadow Hacker' via Django developers (Contributions to Django itself)
Given the number of Open Pull request, does Django craves more contribution quantity, or quality ? Not the same focus -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and

Re: Make Development More Accessible

2019-08-08 Thread William Vincent
I think the way Rails does it, aka with well-done newcomers guide (https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html) is worth looking at, as Carlton notes. A bit more streamlined than the current Django How To Contribute Guides. Incidentally, Carlton and I will be having a

Re: Make Development More Accessible

2019-08-08 Thread Tim Graham
Although I'm not engaged too much with Django development now, a big drawback of moving to GitHub issues for me would be that I could no longer do a Google search like "something something site:code.djangoproject.com". I could pretty much always find the ticket I was looking for that way.

Re: Make Development More Accessible

2019-08-08 Thread Carlton Gibson
Just on this point: > I agree with Andrew Godwins statement on Django loosing many contributors over the years and being in largely maintenance mode. First, I'm not sure Andrew actually said this. Rather I think he reported is a point raised. However... I hear this kind of thing said. It

Re: Make Development More Accessible

2019-08-07 Thread John Gooding
Hi All, I want to thank you all for your time and input. I'll start doing some research into how cpython and others are managing this. I will draw up a few options and present them so we can better work out the possibilities and details before submitting a process DEP. I don't want to submit

Re: Make Development More Accessible

2019-08-07 Thread Andrew Godwin
We actually discussed this a little at the PyCon AU sprints and the consensus was that GitHub issues would be great *if only they were a bit more featureful*. The problems I feel are specifically an issue: - Ticket states; this is not easily replicated with labels, while components etc. are

Re: Make Development More Accessible

2019-08-07 Thread Carlton Gibson
The more I use Trac, the more I appreciate its power. I'm normally all for Progress™ but I'm not sure GitHub's UI is up to it. (Being able to find the old discussion is super handy: it's not that often that an idea has not come up before at this stage.) *I'd be interested to see what a

Re: Make Development More Accessible

2019-08-07 Thread Josh Smeaton
Mariatta has put together a some PEPs for migrating CPython issues over to GitHub. https://www.python.org/dev/peps/pep-0581/ proposing the migration. https://www.python.org/dev/peps/pep-0588/ migration plan. Django and Cpython are not the same, so there'll be substantial differences. But it's

Re: Make Development More Accessible

2019-08-07 Thread John Gooding
Hi Aymeric, You bring up a lot of good points. There will undoubtedly be challenges and huge amount of work in moving to a new system, or implementing any big sweeping changes, however, I truly honestly believe that it would be worth it in the long run, and the payoff would far outweigh the

Re: Make Development More Accessible

2019-08-07 Thread John Gooding
To put it short, the barrier to entry is far too high and difficult for newcomers and even long time users of Django. I agree with others sentiment that there isn't anything that trac can do which github issues cannot, especially for the overwhelming majority of tickets. As a long time user

Re: Make Development More Accessible

2019-08-07 Thread Aymeric Augustin
Hello John, This was discussed before, when we moved from self-hosted svn to GitHub-hosted git, but I'm not sure there are public archives of all discussions. As far as I remember, the main points to tackle are: 1. Does GitHub allow "anonymous triage" i.e. labelling, closing, and reopening

Make Development More Accessible

2019-08-07 Thread John Gooding
I'd like to propose moving Django issues to github and make a real decision on it here in this thread. If there has been a recent discussion on this I apologize, but searching for issue tracking / github links to about every thread ever posted here. I believe this would lower the barrier to