On Tue, 2017-07-11 at 21:33 -0700, Florian Fainelli wrote: > > On 06/24/2017 09:23 PM, Daniel Axtens wrote: > > Hi all, > > > > So, Andrew, Russell and I had a chat about what we'd like to work > > towards for future versions of Patchwork: > > > > * Things before v2 comes out: > > ** 1 series per patch > > > > We think this is a solid idea. > > > > ** Release a tested version: > > > > We'd really like to see Patchwork v2.0 either be based on an unchanged > > release candidate, or a release candidiate with only very obvious and > > simple bug fixes. We really want to avoid the situation where people > > upgrade and hit major bugs as that makes people want to avoid > > migrating. > > > > ** Fuzzing the parser > > > > The hope here is to find any as-yet-undiscovered failure modes in the > > parser. I am hoping to do this in the next couple of days. > > > > * For v2.0.1 > > ** Django 1.11 support > > > > We need to keep up with Django, so this would be important. > > > > * For version 2.n: > > ** Version support > > > > We currently have the ability to record the version of patches/series - > > we'd like to be able to integrate this in the UI. > > > > ** Check permissions > > > > A more sophisticated model for granting permissions for checks may be > > helpful. > > > > ** Events/ETags/Push API > > > > We've been talking about good ways to provide this. We should do it. > > > > ** Port pwclient to REST > > > > What it says on the box. > > > > * Version 3.0+ > > > > ** Drop Python 2 (and anything < Django 2) > > ** Extend the REST API so that we can separate the front and back end > > ** Drop XMLRPC > > > > Thoughts? > > This does not appear on the list, but it would be great if there was a > way to delegate the user authentication against say LDAP or any backend > really (Github would be cool too). > > The instance that I have set up for some my colleagues would > definitively benefit from having them use the same username and > passwords while we would still manage their roles through Django's > administrative portals. > > What do you think?
Sounds like something worth exploring to me. IIUC, this _should_ be possible with minimal effort using something like django-social-auth [1] or django-auth- ldap [2]. Feel free to add this to the issue tracker [3] and we'll mark is as a 2.x RFE. Stephen [1] https://python-social-auth.readthedocs.io/en/latest/configuration/django.ht ml [2] https://pythonhosted.org/django-auth-ldap/ [3] https://github.com/getpatchwork/patchwork/issues _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork