QEP #14 - Authentication configuration system with master password

[dakcarto]

Direct link to QEP .rst preview.

[NathanW2]

Gave it number 14

[NathanW2]

@dakcarto has there been any more work done on this? Are you using it in production.

[dakcarto]

Please note, this QEP is currently being revamped to address the large number of changes in the #2330 PR, specifically the new authentication editors and method plugins. It should be done today.

[dakcarto]

@NathanW2 This is a final draft (unless you see errors), ready to vote on. A bit of a moot point since I already completed most of the work and it has been heavily tested for months. I guess the vote is more of whether the approach is sound, which I think it is.

Btw, the authentication system now supports authentication method plugins (kind of like data provider).

[nyalldawson]

Good to see this listed - I think these two tasks are important and should be prioritised if possible.

[dakcarto]

Hmm. A little dismayed this has been up since January with almost no action or comments about the design or implementation from the PSC, and again with the major revamp within the past week.

Can I get some opinions here when you get a chance? Is it good enough I can just push the fully functioning PR and forego the whole QEP process?

[NathanW2]

Larry feel free to just focus on the PR and merge if you have good feedback.

I need to revamp the QEP process for faster processing.

On Fri, 25 Sep 2015 7:45 am Larry Shaffer notifications@github.com wrote:

Hmm. A little dismayed this has been up since January with almost no
action or comments about the design or implementation from the PSC, and
again with the major revamp within the past week.

Can I get some opinions here when you get a chance? Is it good enough I
can just push the fully functioning PR and forego the whole QEP process?

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

[NathanW2]

Leave this here though because we can use it for docs later.

On Fri, 25 Sep 2015 8:10 am Nathan Woodrow madmanwoo@gmail.com wrote:

Larry feel free to just focus on the PR and merge if you have good
feedback.

I need to revamp the QEP process for faster processing.

On Fri, 25 Sep 2015 7:45 am Larry Shaffer notifications@github.com
wrote:

Hmm. A little dismayed this has been up since January with almost no
action or comments about the design or implementation from the PSC, and
again with the major revamp within the past week.

Can I get some opinions here when you get a chance? Is it good enough I
can just push the fully functioning PR and forego the whole QEP process?

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

[dakcarto]

Ok. Thanks @NathanW2 for getting back to me.

[NathanW2]

Sorry for delay and stuffing around

On Fri, 25 Sep 2015 11:26 am Larry Shaffer notifications@github.com wrote:

Ok. Thanks @NathanW2 https://github.com/NathanW2 for getting back to me.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

[timlinux]

Hi

On 25 Sep 2015, at 02:44, Larry Shaffer notifications@github.com wrote:

Hmm. A little dismayed this has been up since January with almost no action or comments about the design or implementation from the PSC, and again with the major revamp within the past week.

Can I get some opinions here when you get a chance? Is it good enough I can just push the fully functioning PR and forego the whole QEP process?

In general you should solicit comments from the community of developers and consider the PSC as a source of arbitration if there are disputes over decisions being made - or if you feel your QEP is not getting the attention it needs ask us to help - though I think Nathan is on it now. Nathan would normally bring any QEP needing a vote from the PSC to us at that stage.

Apologies for any confusion!

Regards

Tim

—
Reply to this email directly or view it on GitHub #17 (comment).

—

Tim Sutton

Visit http://kartoza.com http://kartoza.com/ to find out about open source:

• Desktop GIS programming services
• Geospatial web development
• GIS Training
• Consulting Services

Skype: timlinux Irc: timlinux on #qgis at freenode.net
Tim is a member of the QGIS Project Steering Committee

Kartoza is a merger between Linfiniti and Afrispatial

[dakcarto]

Hi Tim,

Thank you for the clarification.

[NathanW2]

QEPs done via issues now.

New ticket at #35

Sorry for the inconvenience.

Email out soon on why.