Posted by srlawr on June 6, 2012 at 9:16am
Start:
2012-06-06 18:00 - 22:00 Europe/London It's very last minute, but, as has been stated, there may have enough momentum for people to have safely assumed that the first Wednesday of the month means Drupal-dot-beer in Bristol? :D
As I've already cleared it with the missus, I am going to pop along to the Elephant after work and loiter in the usual corner (I don't think fears of over-spilling will be a problem this week).
I'd love to chat to someone about Services 3 (and web services in general) and would be willing to buy a pint or two in exchange for knowledge..
Comments
cool, ill be there
maybe just for a bit though. I'm all over services in d7 (and particularly in non-Drupal services at the moment) and I'll give Dave in PracticeWEB a shout, he's built a whole product on top of services in Drupal.
Wavvering
I haven't cleared it with the missus yet, but may be there... Unfortunately not in a position to claim the free drinks off of Simon, but happy to lurk if I make it.
My personal cloudy summary
Hayfever, anti-histamine and Cider blurred a few elements, but some of my edited highlights... for comment.
Context module: for block placement, seemed to be some for and against, my view would be yes if all blocks are placed that way, but in an environment where many disparate people which varying levels of knowledge about the project are going to be sticking their fingers in I would probably find a way to enforce it beyond convention. I like context module for all the other things it does as well, and you can do more in your own modules based on contexts, so generally gets a thumbs up from me, also have had reasonably happy times updating contexts in code.
Features module: I would like to pursue views on this further, I did get the impression there are mixed experiences with this, in theory should be a no-brainer (doubleplus good) however once updating from a feature fails you once (site murder,death,kill) it is easy to loose confidence. It is possible that bad experiences with early days of Drupal 7 (and it's contrib modules) flakiness are to blame for this and once thinking that fieldcollections were a good idea (anyone want to defend fieldcollections).
Services 3 : I haven't used but interested, I think the point I was slightly blurredly trying to put across was that using the node resource seems like it would end up in a horrible to use service. Interacting with nodes requiring all the nested structures that Drupal uses. I believe Sift guys were saying they created their own resources specifically to get over this. I can see other situations where you may want to write some sort of simplified data transfer object also.....
Project management: The advantages of proper technical project management, over glorified account management in keeping projects properly scoped, profitable and on target, nuff said .....?
Only a small slice, I had to go early, was quite an interesting chat.
phew
well. That was heavy for a school night..
A very good night overall though, some Drupal discussion (.. and some.. not so Drupal discussion)
I'll try to throw a bit up of what I learnt later.. but first. Bacon roll.