In regards to follow-up on the meeting about code review - That's
partially my bad that there hasn't been any yet. During the meeting I
said that I would pursue exploring the various options discussed, nag
people, start further discussions and try to ensure the ball kept
rolling. However, I
On Thu, Jan 28, 2016 at 2:57 PM, Pine W wrote:
> Is there, or will there be, a page somewhere that describes the outcomes of
> the Developer Summit?
>
I would love for the working group chairs to make the outcomes available
from the main WikiDev16 page:
On Tue, Feb 2, 2016 at 9:40 AM, Rob Lanphier wrote:
> On Thu, Jan 28, 2016 at 2:57 PM, Pine W wrote:
>
>> Is there, or will there be, a page somewhere that describes the outcomes of
>> the Developer Summit?
>>
>
> I would love for the working group
Hi Rob,
Code review seems to be a choke point and the subject of numerous concerns,
so I'd like to see SMART goals for improvements to code review, and one or
more individuals (probably WMF individuals) taking leadership for meeting
those goals. Perhaps the conversation at the Summit will inform
On Thu, 2016-01-28 at 14:57 -0800, Pine W wrote:
> Is there, or will there be, a page somewhere that describes the
> outcomes of the Developer Summit?
I'm not aware of a page but summaries for specific tracks or sessions
can be found in the corresponding Phabricator tasks:
Hi Quim,
Is there, or will there be, a page somewhere that describes the outcomes of
the Developer Summit?
Thanks!
Pine
On Thu, Jan 28, 2016 at 6:19 AM, Quim Gil wrote:
> The Winter break took longer than expected. Busy times!
>
> You can help develop the next summary.
>
>
On Fri, Dec 4, 2015 at 11:36 AM, Oliver Keyes wrote:
> That way people can get the information from the nicely-formatted
> source without simultaneously being lured by a not-as-nicely formatted
> source.
Why is that better than making both sources nicely formatted? All it
On Fri, Dec 4, 2015 at 1:03 PM, Gergo Tisza wrote:
>
> On Fri, Dec 4, 2015 at 11:36 AM, Oliver Keyes wrote:
>
> > That way people can get the information from the nicely-formatted
> > source without simultaneously being lured by a not-as-nicely
The wiki view is vastly better than the email body. My perception is that
this summary is not "What developer relations has been doing", but rather
"if you're a developer here's stuff that might interest you". With that
filter, it made much more sense.
Kevin Smith
Agile Coach, Wikimedia
Well, when the message doesn't adapt to the medium, it's of limited
utility to argue the problem is the medium. You can argue as long as
you want, just don't expect it to change ;)
It seems like an easy resolution to this would be to just point people
at the wiki. So instead of sending
On 2015-12-03 01:33, Gergo Tisza wrote:
(I wouldn't mind if the
email would be HTML as well but there are usually people who dislike that.)
This list strips HTML formatting.
--
Bartosz Dziewoński
___
Wikitech-l mailing list
I am positive that people will be subscribing to a newsletter with the name
'Developer Relations Weekly Summary' soon, which will send the Echo notifs,
and people do directly look at the wiki page :)
https://www.mediawiki.org/wiki/Extension:Newsletter
Thanks,
Tony Thomas
My feedback last time was "could you put some of the content in the
email so we don't have to open 15 links to find out what's going on?
Some of this is pretty contextless". This looks pretty much the same.
On 3 December 2015 at 07:50, Quim Gil wrote:
> Thank you for your
Point! On that front it is much improved; thank you :)
On 3 December 2015 at 11:20, Quim Gil wrote:
> On Thu, Dec 3, 2015 at 3:23 PM, Oliver Keyes wrote:
>> My feedback last time was "could you put some of the content in the
>> email so we don't have to
On Thu, Dec 3, 2015 at 3:23 PM, Oliver Keyes wrote:
> My feedback last time was "could you put some of the content in the
> email so we don't have to open 15 links to find out what's going on?
> Some of this is pretty contextless". This looks pretty much the same.
Actually
On Thu, Dec 3, 2015 at 2:50 AM, Bartosz Dziewoński
wrote:
> This list strips HTML formatting.
Looks like we identified the root problem then.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On 27 November 2015 at 11:32, Oliver Keyes wrote:
> This is a very long list of individual links. Could you quickly
> summarise in text what the team has been working on and what they will
> be next?
I agree with this. The weekly update email, as currently structured, is
On Wed, Dec 2, 2015 at 4:25 PM, Dan Garry wrote:
> I agree with this. The weekly update email, as currently structured, is
> pretty much unreadable for me. A short summary would work better for me.
>
You can click the first link and read the wiki version, where all the
This is a very long list of individual links. Could you quickly
summarise in text what the team has been working on and what they will
be next?
On 27 November 2015 at 11:36, Quim Gil wrote:
> Original version:
>
That "Wikimedia UI" thing looks good! Except it seems to require
third-party javascript (myfontastic?), which is not allowed on Tools Labs,
IIRC.
And it wants to run Flash. Why???
On Thu, Nov 5, 2015 at 12:33 PM Quim Gil wrote:
> Original web version:
>
>
Hi Quim,
I'm glad to see the tasks about 3D files in there. Open license 3D files
were a need mentioned at WCONUSA for GLAMs.
There has been a lot of discussion recently about the Education Exension's
problems. Any chance of getting Developer Relations resources in making
that code at least
> There has been a lot of discussion recently about the Education Exension's
> problems. Any chance of getting Developer Relations resources in making
> that code at least secure and maintainable enough to keep it deployed on
> its current wikis in the short term and in order to buy some time for
Hi,
On Thu, 2015-10-22 at 08:23 -0700, Pine W wrote:
> There has been a lot of discussion recently about the Education Exension's
> problems. Any chance of getting Developer Relations resources in making
> that code at least secure and maintainable enough to keep it deployed on
> its current
Thanks Quim, I like the summary. Code review is a particular interest of
mine and I'm glad to see some stats mentioned here.
Pine
On Oct 8, 2015 3:03 AM, "Quim Gil" wrote:
> We are discussing the possibility of maintaining a weekly summary of news
> related to the areas
24 matches
Mail list logo