-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> On 5 Jan 2009, at 12:00, vArDo wrote: >> Is Pylons planning to apply for participation in GSoC 2 Good question but ... > On 6 Jan 2009, at 20:19, Christopher Barker wrote: >> Docs, tutorials, demos, etc. are not eligible for GSoC anyway. Personally, I have some difficulty seeing where Pylons might afford the opportunity of a GSoc project. There /might/ be a broader contribution which could be based on Pylons ... On 6 Jan 2009, at 19:44, Mike Orr wrote: > - Some sites need specifically wiki features, a la MoinMoin. I've > heard MoinMoin is difficult to set up in a WSGI environment and > integrate into a larger site, so perhaps there's something there to > work on. Some time ago I had a play with calling MoinMoin from a Pylons controller (with a limited degree of success). MoinMoin provides a WSGI-callable entry point, as does Trac. ISTM that there's a loose area pertaining to the propagation of (what would otherwise be) application-specific user preferences to other apps that are sharing a WSGI-based single sign-on environment, e.g. synching user display name and email prefs across apps. It's clearly not pertinent to the WSGI spec but it does seem rather pertinent to apps that inhabit the WGSI layers. I suspect that this issue will have to be tackled by someone at some point in the not-too-distant, as suggested by Mike's list of partially- emerging apps. It might be nice to see the ground staked out by some well-designed middleware. OTOH, perhaps it's more of an issue of consensus rather than coding and hence unsuitable for a GSoC proj. > Non-relational databases. > Authentication/authorization I ought to fess up that I've been kicking around some stuff in this very area. Shabti [1] is a fork of Tesla [2] that presents a variety of what I'm pretentiously calling "elementary design patterns". Specifically, they are a number of paster templates and associated files that create and populate Pylons instances, each of which is augmented in some fashion by an add-on library or facility. The broad idea is to provide a convenient means for folks to explore (extremely limited) ready-rolled extensions, a sort of jumping-off point for exploratory development. I'm holding off until Pylons 0.9.7 is released before I de-cloak. The original Tesla project offered a default template that integrated elixir (back when elixir was under consideration as a core Pylons component), as well as a couple of templates that provided a basic auth'n'auth solution. I forked Tesla on bitbucket [3] a few months ago and have been pratting about with it since then. I've added a template for a repose.who auth, a couchdb auth'n'auth pattern, an auth'n'auth pattern that uses an RDF graph as a back-end and a first stab at a very basic microCMS using tw/twforms. The code's pretty crude [*] but it should get people up and running without them having to tediously follow a trail of cut and paste instructions of sometimes doubtful currency/validity. Mike's raised a couple of options w.r.t. non-relational databases that should probably be included although I quail at the amount of work that it's likely to involve. > Ben could use some help finishing the Pylons documentation for 0.9.7, > although that's too short a timeframe for the Summer of Code. Can you point to anything specific, Ben? [1] http://bel-epa.com/notes/Pylons/Shabti/ [2] http://code.google.com/p/tesla-pylons-elixir/ [3] http://www.bitbucket.org/gjhiggins/shabti/overview/ [*] My coding style has been described variously as "colloquial", "Neanderthal" and "brutal". In my defence, my very first coding experience was back in '69 with Burroughs JCL and I carry the scars to this day, so whaddya expect? Cheers, Graham -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklj47wACgkQOsmLt1NhivzKqwCgkjVZm1qmpk8U0S6q5qezftkY /IMAoJmf3TOdjlVtylgSpVi1X4wIIRORiQCVAgUBSWPjvFnrWVZ7aXD1AQKY5gQA ppDNGPu5szVXNJnTg0gFLw909Gdw5wHfOksYFjGdBNcZEZgtMxyqDLQMbZyFROiN wRsT8rrHSJqBTNUEuHfM5IBFPVaOVziiVPnKEptTBKpIAR2RSFWLftKMYwXfw/6f t/hvu+8HQ1gdf3Sk2NbgI9jc3iGhvD9Gfjmrz3/T+Co= =xhq+ -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
