View in #random on Slack
@Code_Potent: OT: Has there been any decisions on which platform to use for the plugin directory?
or framework…
@invisnet: define: platform
@Code_Potent: What will power the directory?
@invisnet: ah - an interesting mix of things i’m writing a paper about as i define it
@Code_Potent: I mean… CP, Laravel, something RoR … or …
@invisnet: e) none of the above
@Code_Potent: Exactly. There’s lots of specs, but, it’s not clear how to actually do something to forward the project.
@invisnet: i’m working on it
my first aim is to create a provisional rest api spec
@Wade_Striebel: Are you working with @William_Patton still on that?
@invisnet: anyone could do that i know, but each part i write about will have some actual thought behind it
“still”?
@Wade_Striebel: Wasn’t he waiting on an API to start building out the frontend?
@invisnet: i discussed in some detail some security aspects with him, not aware of anything else
@Wade_Striebel: It is possible I misunderstood, I have been swamped with everything so everything is just starting to mix together in my mind 
@invisnet: but either way, the idea of defining the rest api first is exactly along those lines - so others can start working on the pretty frontend stuff
@Code_Potent: Exactly… we need to know the data structure.
@Wade_Striebel: I recall I offered help in regards to building out a Laravel backend, I can still help there
@invisnet: too heavy and insecure for what i have in mind for the core, but thanks for the offer
i’ll certainly want input on the api wrt ease of use etc
@Code_Potent: For sure
@Wade_Striebel: I find Laravel pretty lightweight, especially when just building out an API - it does have it’s use cases though
But ya, I am happy to help where I can, I am sure I can find time
@invisnet: laravel assumes you’ve got a database to talk to - we won’t
@Code_Potent: Still got a few hours of work to do here… I’m off. @me if you need me.
@invisnet: @Code_Potent have a good one!
@Wade_Striebel: Makes sense, we use Laravel pretty heavily but we are always building on top of some type of database
“we” being my company
@invisnet: we’ll have a database for searching - daft to do anything else - but it won’t be the primary source of data
@Wade_Striebel: We have used it as a middleware between apis we utilize, but still in that case we are at the very least tracking and logging the calls we make
@invisnet: i don’t have a position on what the back-end presentation layer should be
the core directory will be a restful api - that’s all anything will ever see of it
just as long as we don’t use react or vue or anything else js-based i’m not bothered about that part
@Wade_Striebel: What are you thinking of using to create the restful api?
@invisnet: flat files and symlinks
in exactly the same way the update api works now
@Wade_Striebel: Okay, so what are next steps you need from us? “us” being people interested in helping getting it started
@invisnet: just a little more patience
once i’ve got an outline of the api you can go have fun with that
but until then, go ahead and start thinking about how to present the data on the frontend
how do we display a plugin’s security record?
how do we display the release history?
support links?
etc
oh - and dependencies - very important to show those
@Wade_Striebel: Okay sounds good, I’m going to move this chat to the forums