pauamma: Cartooney crab holding drink (Default)
Res facta quae tamen fingi potuit ([personal profile] pauamma) wrote in [site community profile] dw_dev2017-04-08 09:19 pm
Entry tags:

Question thread #51

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
ironymaiden: (Gir/piggy)

[personal profile] ironymaiden 2017-04-09 03:41 am (UTC)(link)
I see that there's a git pull request called "API framework" and that it's untriaged. my understanding is that the API is the main blocker for mobile app development.

how does the DW pull request process work? (i.e. does untriaged mean that no one is looking at that right now, or does it stay "untriaged" until it has a review complete, or something else?)

(i really really want that mobile app.)
ironymaiden: (Default)

[personal profile] ironymaiden 2017-04-09 04:57 pm (UTC)(link)
Maybe I'm confused. I thought pull requests were code awaiting approval to be merged into the project. So I can see that people have been contributing API code, but it seems to just be sitting there. No comments, no other tags.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)

[staff profile] denise 2017-04-10 10:17 am (UTC)(link)
That particular PR is from the working team that's drafting "API 2.0" and in this case is a checkpoint PR -- even if it were merged, it wouldn't be a full, working API yet. That PR is just like saying "hey, here's the bones of the thing we've got laid down already, are we on the right track?" The next step is that [staff profile] mark will review the bones for content, style, architecture, load, security, etc (and it is on his to-do list) and provide feedback, both of the "how this particular PR needs to be changed" and "hey, keep this in mind for when you add the next set of API calls" variety. Mark's day job has been unexpectedly busy lately, though, so he hasn't had the uninterrupted block of time necessary to do the code review!

(I totally know that the lack of a mobile app is the biggest problem most people have with DW right now! But we're putting as much of our attention to it as we can.)