On Thursday, September 1, 2016, Brion Vibber <bvib...@wikimedia.org> wrote:
> On Thu, Sep 1, 2016 at 10:32 AM, Brian Wolff <bawo...@gmail.com> wrote:
>
>> Last year there was an attempt to sort of do this (mostly by extending
the
>> word "developer" to mean new things). Largely those types of people didnt
>> attend (although there were a few exceptions), however I remember being
>> left wondering if they did attend, what would they do? It seems to me
most
>> sessions were about architecture design decisions that actually didnt
>> affect anyone not working on the code (ie we were going to make the user
>> visible feature either way, the question was do we use method x or
method y
>> in the backend). With that in mind. Otoh, its entirely possible that some
>> of the sessions i didnt attend were more applicable to these groups.
>>
>> With that in mind are you proposing the focus of event also change? Or do
>> you think that these groups would be interested in it as is?
>>
>
> Yes, I think we *should* provide a focus for the event, and that the focus
> should be on users, use cases, and what we as developers need to do to
> achieve those things.
>
> In my opinion we haven't had a strong focus to the event in the past, and
> it's limited what we accomplish there to largely making a set of technical
> presentations and having a few discussions that either don't produce a
> decision or don't have much affect on what actually happens after the
> summit.
>
> (I'd be very interested also in some feedback on things that *have* worked
> well at MWDS in the past, as I'd love to encourage anything that has been
> productive! But I think we've not been successful in an architectural
focus
> so far.)
>
> -- brion
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to