#foswiki 2016-12-09,Fri

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
GithubBot[OpenIDLoginContrib] jesuisse pushed 1 new commit to master: https://git.io/v1aMx
OpenIDLoginContrib/master fae3d52 Pascal Schuppli: Item14248: Corrected configuration keys
[00:48]
***GithubBot has left [00:48]
FoswikiBothttps://foswiki.org/Tasks/Item14248 [ Item14248: Create OpenID Login Manager to authenticate with MS, Google etc ] [00:48]
GithubBot[distro] vrurg pushed 2 new commits to Item14237: https://git.io/v1aDf
distro/Item14237 66cb062 Vadim Belman: Item14237: Improved config key options validation....
distro/Item14237 5b3f9ca Vadim Belman: Item14237: More tests for keys parsing and validation.
[00:48]
***GithubBot has left [00:48]
FoswikiBothttps://foswiki.org/Tasks/Item14237 [ Item14237: Implement Development.OOConfigSpecsFormat proposal ] [00:48]
............................. (idle for 2h24mn)
vrurggac410: Hi, I guess it's time to change the meeting date in the topic. [03:12]
gac410whoops ... good point
;)
[03:12]
***gac410 changes topic to: Logs: http://irclogs.foswiki.org/bin/irclogger_log/foswiki - Slack: https://foswiki-slackin.herokuapp.com/ - Bugs: https://foswiki.org/Tasks - Next up: Release meeting Monday 12 Dec, 1300Z [03:14]
gac410Thanks [03:14]
vrurgnp [03:14]
gac410thx [03:16]
vrurgIt turns out that my config specs proposal has a disadvantage comparing to the old format – there is no way to fast fetch default values without complete spec parsing.
Would be necessary to cache them separately somewhere.
[03:22]
gac410:( [03:22]
vrurgThat's not a big deal but adds more work to an already big project. [03:23]
gac410No job is too small to make a project out of it. ;) [03:24]
vrurgAha, if the goal is to build up a project not make a result. ;)
BTW, have a little question. It is planned to have support for various spec formats: perl, yaml, whatever else a plugin would be written for. Currently the best way to distinguish among them is to support shebang – i.e. #!legacy for current format, #!yaml, etc. But what if we use filenames for the purpose? Spec.legacy, Spec.std, Spec.yaml?
[03:24]
gac410Hm I suppose 6 / half dozen. [03:33]
vrurgPardon? [03:34]
gac410sorry - idiom. I guess it doesn't matter one way or the other.
Just concerned about complexity.
[03:35]
vrurgThe only question I can think of right now if this would have any impact over BuildContrib. [03:36]
gac410I'm not sure BuildContrib even uses the spec. It just copies it as another file in the manifest.
Config.spec is purely a configure thing.
[03:37]
vrurgOk, then it's not that big of a deal. Unless CDot would have any additional thoughts on this. [03:38]
gac410He's really the most knowledgable configure person. [03:38]
vrurgI know. And will need his expertise and support soon. I plan to have new specs be terminilogically compatible with the old ones to be able to directly comile the legacy format into perl structure. And to minimize changes to the ConfigurePlugin. The changes better be technical, not logical. [03:40]
.................. (idle for 1h25mn)
***gac410 has left [05:05]
..................................................................... (idle for 5h42mn)
ChanServ sets mode: +o MichaelDaum [10:47]
.............................................................................. (idle for 6h29mn)
ChanServ sets mode: +o gac410 [17:16]
......................................... (idle for 3h22mn)
GithubBot[OpenIDLoginContrib] jesuisse pushed 1 new commit to master: https://git.io/v1wwn
OpenIDLoginContrib/master fa59d14 Pascal Schuppli: Item14248: Simplified openid templates. Also corrected a protocol error (requesting scopes that aren't supported)
[20:38]
***GithubBot has left [20:38]
FoswikiBothttps://foswiki.org/Tasks/Item14248 [ Item14248: Create OpenID Login Manager to authenticate with MS, Google etc ] [20:38]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)