info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Notes from the Toronto Open Session on Web Compat
63 views
Skip to first unread message
Mike Taylor
Oct 8, 2013, 12:08:03 PM10/8/13
to compat...@lists.mozilla.org
See https://etherpad.mozilla.org/webcompat-opensession, starting at line
75. A huge thanks to Chris Mills from the MDN docs team for taking notes.
There were some really good ideas that came out of this session's
discussion and I'm curious to hear how the sessions in the other
locations went.
Given the competition with other sexy topics like DRM and 20 other cool
things I would have attended personally, our session was small (about 9
or 10 people) but productive. A million thanks to all those who endured
to the end of the 3rd day of the summit and participated.
And naturally I've probably left some things out, so please respond to
clarify, correct, or remind me of important things I missed.
In no particular order:
* Make some swag to recognize and thank community members that are
pitching in. Stickers + shirts would be cool. Leonard from Venezuela
said t-shirts are the most desired thing. (Maybe we could send a sticker
to people who help us get in contact with a site and a shirt if they've
helped on 3 bugs or something?)
* We need to have better intra-org communication. Lisa from the FxOS
apps approval team talked about having contacts at many large partner
sites. She said she's very willing to share.
* Lisa also mentioned that they have a volunteer sign up list for people
wanting to review FxOS apps, with more interest than they can
accommodate. This might be a good opportunity to funnel willing people
into our efforts.
* Make a slide that the Dev Engagement/Evangelism team can show during
their presentations. They'd be willing to show it, but we would need to
provide something they can drop in.
* http://www.whatcanidoformozilla.org/ -> come up with paths that will
lead to Tech Evangelism bugs. Speak Greek? How about contacting
http://www.zougla.gr/ [Bug XXXXXXXX], etc.
* Anthony Ricaud had the idea of creating an add-on that would allow
users to share their browser history so we could better understand what
sites users are visiting (as opposed to assuming Alexa is the best).
Some concerns about privacy, but a webapp that allowed users to edit the
history entries that are submitted seems like a good compromise.
* Regarding community engagement, be very careful that we're not just
showing up asking people to do work for us, e.g., we need help to fix
content in your country vs. please do this work for our team. Leonard
said that contacting them in their own language is better than just
English (especially for the Mozilla Hispano community, there are lots
who could help who don't speak English). Robert Nyman reminded us to be
careful again, let's not just take them for granted and always ask, ask,
ask, ask. So how do we establish a relationship where we're able and
willing to contribute to their needs as well?
--
Mike Taylor
Web Compat, Mozilla
75. A huge thanks to Chris Mills from the MDN docs team for taking notes.
There were some really good ideas that came out of this session's
discussion and I'm curious to hear how the sessions in the other
locations went.
Given the competition with other sexy topics like DRM and 20 other cool
things I would have attended personally, our session was small (about 9
or 10 people) but productive. A million thanks to all those who endured
to the end of the 3rd day of the summit and participated.
And naturally I've probably left some things out, so please respond to
clarify, correct, or remind me of important things I missed.
In no particular order:
* Make some swag to recognize and thank community members that are
pitching in. Stickers + shirts would be cool. Leonard from Venezuela
said t-shirts are the most desired thing. (Maybe we could send a sticker
to people who help us get in contact with a site and a shirt if they've
helped on 3 bugs or something?)
* We need to have better intra-org communication. Lisa from the FxOS
apps approval team talked about having contacts at many large partner
sites. She said she's very willing to share.
* Lisa also mentioned that they have a volunteer sign up list for people
wanting to review FxOS apps, with more interest than they can
accommodate. This might be a good opportunity to funnel willing people
into our efforts.
* Make a slide that the Dev Engagement/Evangelism team can show during
their presentations. They'd be willing to show it, but we would need to
provide something they can drop in.
* http://www.whatcanidoformozilla.org/ -> come up with paths that will
lead to Tech Evangelism bugs. Speak Greek? How about contacting
http://www.zougla.gr/ [Bug XXXXXXXX], etc.
* Anthony Ricaud had the idea of creating an add-on that would allow
users to share their browser history so we could better understand what
sites users are visiting (as opposed to assuming Alexa is the best).
Some concerns about privacy, but a webapp that allowed users to edit the
history entries that are submitted seems like a good compromise.
* Regarding community engagement, be very careful that we're not just
showing up asking people to do work for us, e.g., we need help to fix
content in your country vs. please do this work for our team. Leonard
said that contacting them in their own language is better than just
English (especially for the Mozilla Hispano community, there are lots
who could help who don't speak English). Robert Nyman reminded us to be
careful again, let's not just take them for granted and always ask, ask,
ask, ask. So how do we establish a relationship where we're able and
willing to contribute to their needs as well?
--
Mike Taylor
Web Compat, Mozilla
Bradford Lassey
Oct 8, 2013, 12:39:02 PM10/8/13
to compat...@lists.mozilla.org
In Brussels we had about 20 people by the end (there was confusion
around the room and people trickled in). I unfortunately took my notes
in an emacs scratch buffer and have now lost them. Perhaps Hallvord has
better memory than I do.
From memory, we had participants from Brazil, the UK, the US, Isreal
and Germany... but I know there were more.
We had people from the US,
gets pushed. Holding web compat to the same standard I think would
translate into sending a T-shirt after making contact and getting the
issue resolved for 1 site. T-shirts are (relatively) cheap and
incredibly motivating. I think we should work up a design to
specifically recognise webcompat work.
they'll show up in Bugs Ahoy! (http://www.joshmatthews.net/bugsahoy/).
telemetry or FHR about what sites people are visiting.
allowing community groups to own the relationships in their locales.
-Brad
around the room and people trickled in). I unfortunately took my notes
in an emacs scratch buffer and have now lost them. Perhaps Hallvord has
better memory than I do.
From memory, we had participants from Brazil, the UK, the US, Isreal
and Germany... but I know there were more.
We had people from the US,
On 10/8/13 12:08 PM, Mike Taylor wrote:
> See https://etherpad.mozilla.org/webcompat-opensession, starting at
> line 75. A huge thanks to Chris Mills from the MDN docs team for
> taking notes.
>
> There were some really good ideas that came out of this session's
> discussion and I'm curious to hear how the sessions in the other
> locations went.
>
> Given the competition with other sexy topics like DRM and 20 other
> cool things I would have attended personally, our session was small
> (about 9 or 10 people) but productive. A million thanks to all those
> who endured to the end of the 3rd day of the summit and participated.
>
> And naturally I've probably left some things out, so please respond to
> clarify, correct, or remind me of important things I missed.
>
> In no particular order:
>
> * Make some swag to recognize and thank community members that are
> pitching in. Stickers + shirts would be cool. Leonard from Venezuela
> said t-shirts are the most desired thing. (Maybe we could send a
> sticker to people who help us get in contact with a site and a shirt
> if they've helped on 3 bugs or something?)
We've adopted a policy for engineering of sending a T-shirt when a patch
> See https://etherpad.mozilla.org/webcompat-opensession, starting at
> line 75. A huge thanks to Chris Mills from the MDN docs team for
> taking notes.
>
> There were some really good ideas that came out of this session's
> discussion and I'm curious to hear how the sessions in the other
> locations went.
>
> Given the competition with other sexy topics like DRM and 20 other
> cool things I would have attended personally, our session was small
> (about 9 or 10 people) but productive. A million thanks to all those
> who endured to the end of the 3rd day of the summit and participated.
>
> And naturally I've probably left some things out, so please respond to
> clarify, correct, or remind me of important things I missed.
>
> In no particular order:
>
> * Make some swag to recognize and thank community members that are
> pitching in. Stickers + shirts would be cool. Leonard from Venezuela
> said t-shirts are the most desired thing. (Maybe we could send a
> sticker to people who help us get in contact with a site and a shirt
> if they've helped on 3 bugs or something?)
gets pushed. Holding web compat to the same standard I think would
translate into sending a T-shirt after making contact and getting the
issue resolved for 1 site. T-shirts are (relatively) cheap and
incredibly motivating. I think we should work up a design to
specifically recognise webcompat work.
>
> * We need to have better intra-org communication. Lisa from the FxOS
> apps approval team talked about having contacts at many large partner
> sites. She said she's very willing to share.
>
> * Lisa also mentioned that they have a volunteer sign up list for
> people wanting to review FxOS apps, with more interest than they can
> accommodate. This might be a good opportunity to funnel willing people
> into our efforts.
>
> * Make a slide that the Dev Engagement/Evangelism team can show during
> their presentations. They'd be willing to show it, but we would need
> to provide something they can drop in.
I can do this. Who is the best person to talk to? Stormy?
> * We need to have better intra-org communication. Lisa from the FxOS
> apps approval team talked about having contacts at many large partner
> sites. She said she's very willing to share.
>
> * Lisa also mentioned that they have a volunteer sign up list for
> people wanting to review FxOS apps, with more interest than they can
> accommodate. This might be a good opportunity to funnel willing people
> into our efforts.
>
> * Make a slide that the Dev Engagement/Evangelism team can show during
> their presentations. They'd be willing to show it, but we would need
> to provide something they can drop in.
>
> * http://www.whatcanidoformozilla.org/ -> come up with paths that will
> lead to Tech Evangelism bugs. Speak Greek? How about contacting
> http://www.zougla.gr/ [Bug XXXXXXXX], etc.
perfect. Also, if we add [mentor=XXXX] to all of the contact ready bugs
> * http://www.whatcanidoformozilla.org/ -> come up with paths that will
> lead to Tech Evangelism bugs. Speak Greek? How about contacting
> http://www.zougla.gr/ [Bug XXXXXXXX], etc.
they'll show up in Bugs Ahoy! (http://www.joshmatthews.net/bugsahoy/).
>
> * Anthony Ricaud had the idea of creating an add-on that would allow
> users to share their browser history so we could better understand
> what sites users are visiting (as opposed to assuming Alexa is the
> best). Some concerns about privacy, but a webapp that allowed users to
> edit the history entries that are submitted seems like a good compromise.
a similar point came up in our session about collecting some data though
> * Anthony Ricaud had the idea of creating an add-on that would allow
> users to share their browser history so we could better understand
> what sites users are visiting (as opposed to assuming Alexa is the
> best). Some concerns about privacy, but a webapp that allowed users to
> edit the history entries that are submitted seems like a good compromise.
telemetry or FHR about what sites people are visiting.
>
> * Regarding community engagement, be very careful that we're not just
> showing up asking people to do work for us, e.g., we need help to fix
> content in your country vs. please do this work for our team. Leonard
> said that contacting them in their own language is better than just
> English (especially for the Mozilla Hispano community, there are lots
> who could help who don't speak English). Robert Nyman reminded us to
> be careful again, let's not just take them for granted and always ask,
> ask, ask, ask. So how do we establish a relationship where we're able
> and willing to contribute to their needs as well?
>
>
Yes, this. I really want to emphasize community *driven* web compat and
> * Regarding community engagement, be very careful that we're not just
> showing up asking people to do work for us, e.g., we need help to fix
> content in your country vs. please do this work for our team. Leonard
> said that contacting them in their own language is better than just
> English (especially for the Mozilla Hispano community, there are lots
> who could help who don't speak English). Robert Nyman reminded us to
> be careful again, let's not just take them for granted and always ask,
> ask, ask, ask. So how do we establish a relationship where we're able
> and willing to contribute to their needs as well?
>
>
allowing community groups to own the relationships in their locales.
-Brad
Karl Dubost
Oct 8, 2013, 2:31:34 PM10/8/13
to compat...@lists.mozilla.org
About the specific topic of community engagement,
Mike Taylor [2013-10-08T12:08]:
1. here there is work to do
2. people can get involved
3. this is the way to maximize the volunteer effort.
I also want to broaden that in a way which doesn't make it specifically exclusive to Mozilla. We want to have the things being fixed for Firefox OS, Android (and Desktop) but it is necessary to be pushed in a way that will make it better for the Web as large. Often I test in Opera and some other browsers I have around and if not working I report it.
There could have been a good opportunity of work with the Opera Open Web team… oh wait ;). We have contacts with Blackberry (webkit browser) team which has also issues.
An example
https://bugzilla.mozilla.org/show_bug.cgi?id=826517#c1
> Leonard said that contacting them in their own language is better than just English (especially for the Mozilla Hispano community, there are lots who could help who don't speak English).
So here there's a need for people who are bridges.
In our own team, I believe we have at least (English removed being our working language)
* Hallvord: Norwegian
* Mike: Portuguese (Brazil)
* Karl: French, Japanese (a little bit), (I may brush up my german if needed, but tough)
I don't know for Aaron, Lawrence, Jason, Vishy, etc.
> Robert Nyman reminded us to be careful again, let's not just take them for granted and always ask, ask, ask, ask. So how do we establish a relationship where we're able and willing to contribute to their needs as well?
Yes yes yes. Agreed 1000 times. Volunteers contribute because they want to help not because they have too. I contributed to translations of W3C specs in the past. And it's something you do not at a regular pace and depending on your own schedule.
It's also a good way to learn new things, and that might be a way to promote Web compatibility volunteer effort. What will you learn doing that?
--
Karl Dubost, Mozilla
http://www.la-grange.net/karl/moz
Mike Taylor [2013-10-08T12:08]:
> * Regarding community engagement, be very careful that we're not just showing up asking people to do work for us, e.g., we need help to fix content in your country vs. please do this work for our team.
Yes. Definitely. Somehow it is more about knowing that
1. here there is work to do
2. people can get involved
3. this is the way to maximize the volunteer effort.
I also want to broaden that in a way which doesn't make it specifically exclusive to Mozilla. We want to have the things being fixed for Firefox OS, Android (and Desktop) but it is necessary to be pushed in a way that will make it better for the Web as large. Often I test in Opera and some other browsers I have around and if not working I report it.
There could have been a good opportunity of work with the Opera Open Web team… oh wait ;). We have contacts with Blackberry (webkit browser) team which has also issues.
An example
https://bugzilla.mozilla.org/show_bug.cgi?id=826517#c1
> Leonard said that contacting them in their own language is better than just English (especially for the Mozilla Hispano community, there are lots who could help who don't speak English).
In our own team, I believe we have at least (English removed being our working language)
* Hallvord: Norwegian
* Mike: Portuguese (Brazil)
* Karl: French, Japanese (a little bit), (I may brush up my german if needed, but tough)
I don't know for Aaron, Lawrence, Jason, Vishy, etc.
> Robert Nyman reminded us to be careful again, let's not just take them for granted and always ask, ask, ask, ask. So how do we establish a relationship where we're able and willing to contribute to their needs as well?
It's also a good way to learn new things, and that might be a way to promote Web compatibility volunteer effort. What will you learn doing that?
--
Karl Dubost, Mozilla
http://www.la-grange.net/karl/moz
Karl Dubost
Oct 8, 2013, 2:42:53 PM10/8/13
to compat...@lists.mozilla.org
About ways of thanking the people who are working, giving time to get things improved.
Mike Taylor [2013-10-08T12:08]:
* Coming up with a cool t-shirt, sticker design
* Having the mention of Mozilla in small (The sleeve, a corner of the design, etc.) Something that people can wear in different circumstances. The "I open the Web" is one the best tee I ever had.
http://files.myopera.com/dstorey/files/2opera1.jpg
* Something that is cross-community, cross-platform, etc.
The issue with t-shirts also is that it is nice when it is the first one, after a while your cabinet looks like a geek/nerd fashion empire. :) People who are volunteering are many with different tastes and styles. USB keys, notebook, or sometimes just your name on a page is enough. :)
Ah and on the topic of tshirts. WOMEN CUT too :)
Basically there is not only one way of thanking. :)
Mike Taylor [2013-10-08T12:08]:
> * Make some swag to recognize and thank community members that are pitching in. Stickers + shirts would be cool. Leonard from Venezuela said t-shirts are the most desired thing. (Maybe we could send a sticker to people who help us get in contact with a site and a shirt if they've helped on 3 bugs or something?)
I will give a counter argument :) just to balance things. I'm in a geek category which doesn't like very much t-shirt or any kind of swag with big logo and branding on it. ;) So there might be ways to make this more diverse.
* Coming up with a cool t-shirt, sticker design
* Having the mention of Mozilla in small (The sleeve, a corner of the design, etc.) Something that people can wear in different circumstances. The "I open the Web" is one the best tee I ever had.
http://files.myopera.com/dstorey/files/2opera1.jpg
* Something that is cross-community, cross-platform, etc.
The issue with t-shirts also is that it is nice when it is the first one, after a while your cabinet looks like a geek/nerd fashion empire. :) People who are volunteering are many with different tastes and styles. USB keys, notebook, or sometimes just your name on a page is enough. :)
Ah and on the topic of tshirts. WOMEN CUT too :)
Basically there is not only one way of thanking. :)
Mike Taylor
Oct 8, 2013, 3:22:57 PM10/8/13
to compat...@lists.mozilla.org
On 08/10/2013 13:42, Karl Dubost wrote:
> About ways of thanking the people who are working, giving time to get things improved.
>
> Mike Taylor [2013-10-08T12:08]:
>> * Make some swag to recognize and thank community members that are pitching in. Stickers + shirts would be cool. Leonard from Venezuela said t-shirts are the most desired thing. (Maybe we could send a sticker to people who help us get in contact with a site and a shirt if they've helped on 3 bugs or something?)
>
> I will give a counter argument :) just to balance things. I'm in a geek category which doesn't like very much t-shirt or any kind of swag with big logo and branding on it. ;) So there might be ways to make this more diverse.
>
> * Coming up with a cool t-shirt, sticker design
> * Having the mention of Mozilla in small (The sleeve, a corner of the design, etc.) Something that people can wear in different circumstances. The "I open the Web" is one the best tee I ever had.
> http://files.myopera.com/dstorey/files/2opera1.jpg
> * Something that is cross-community, cross-platform, etc.
Absolutely agree.
> About ways of thanking the people who are working, giving time to get things improved.
>
> Mike Taylor [2013-10-08T12:08]:
>> * Make some swag to recognize and thank community members that are pitching in. Stickers + shirts would be cool. Leonard from Venezuela said t-shirts are the most desired thing. (Maybe we could send a sticker to people who help us get in contact with a site and a shirt if they've helped on 3 bugs or something?)
>
> I will give a counter argument :) just to balance things. I'm in a geek category which doesn't like very much t-shirt or any kind of swag with big logo and branding on it. ;) So there might be ways to make this more diverse.
>
> * Coming up with a cool t-shirt, sticker design
> * Having the mention of Mozilla in small (The sleeve, a corner of the design, etc.) Something that people can wear in different circumstances. The "I open the Web" is one the best tee I ever had.
> http://files.myopera.com/dstorey/files/2opera1.jpg
> * Something that is cross-community, cross-platform, etc.
> The issue with t-shirts also is that it is nice when it is the first one, after a while your cabinet looks like a geek/nerd fashion empire. :) People who are volunteering are many with different tastes and styles. USB keys, notebook, or sometimes just your name on a page is enough. :)
But I agree (I gave away 2 of my 3 summit shirts to a non-employee
contributor in Toronto). People are different and it's not hard to give
a few simple options. Would you like a shirt? A sticker? Can we mention
you in a blog post to thank you?
> Ah and on the topic of tshirts. WOMEN CUT too :)
> Basically there is not only one way of thanking. :)
was fun, but I spent that ages ago. A hall of fame site [1] is a nice
way to thank people in conjunction with other rewards too.
[1]
https://sites.google.com/a/chromium.org/dev/Home/chromium-security/hall-of-fame
Lawrence Mandel
Oct 9, 2013, 12:14:02 PM10/9/13
to Mike Taylor, compat...@lists.mozilla.org
----- Original Message -----
> See https://etherpad.mozilla.org/webcompat-opensession, starting at line
> 75. A huge thanks to Chris Mills from the MDN docs team for taking notes.
Thanks to Chris and to Mike for running what amounted to a very engaging session with good ideas (as Mike lists below).
> See https://etherpad.mozilla.org/webcompat-opensession, starting at line
> 75. A huge thanks to Chris Mills from the MDN docs team for taking notes.
> There were some really good ideas that came out of this session's
> discussion and I'm curious to hear how the sessions in the other
> locations went.
>
> Given the competition with other sexy topics like DRM and 20 other cool
> things I would have attended personally, our session was small (about 9
> or 10 people) but productive. A million thanks to all those who endured
> to the end of the 3rd day of the summit and participated.
>
> And naturally I've probably left some things out, so please respond to
> clarify, correct, or remind me of important things I missed.
>
> In no particular order:
>
> * Make some swag to recognize and thank community members that are
> pitching in. Stickers + shirts would be cool. Leonard from Venezuela
> said t-shirts are the most desired thing. (Maybe we could send a sticker
> to people who help us get in contact with a site and a shirt if they've
> helped on 3 bugs or something?)
Let's discuss the criteria and get a bug on file about the design. We can follow up with some of the Toronto folks who have created t-shirts in the past. (There are several.)
> pitching in. Stickers + shirts would be cool. Leonard from Venezuela
> said t-shirts are the most desired thing. (Maybe we could send a sticker
> to people who help us get in contact with a site and a shirt if they've
> helped on 3 bugs or something?)
> * We need to have better intra-org communication. Lisa from the FxOS
> apps approval team talked about having contacts at many large partner
> sites. She said she's very willing to share.
> * Lisa also mentioned that they have a volunteer sign up list for people
> wanting to review FxOS apps, with more interest than they can
> accommodate. This might be a good opportunity to funnel willing people
> into our efforts.
> * Make a slide that the Dev Engagement/Evangelism team can show during
> their presentations. They'd be willing to show it, but we would need to
> provide something they can drop in.
>
> * http://www.whatcanidoformozilla.org/ -> come up with paths that will
> lead to Tech Evangelism bugs. Speak Greek? How about contacting
> http://www.zougla.gr/ [Bug XXXXXXXX], etc.
I think this is the Github repo for the site:
> lead to Tech Evangelism bugs. Speak Greek? How about contacting
> http://www.zougla.gr/ [Bug XXXXXXXX], etc.
https://github.com/jdm/asknot
Josh Matthews is located in Toronto and, from our previous conversations, is happy to add additional teams/projects/skills to this site. We should definitely pursue this opportunity.
Lawrence
> * Anthony Ricaud had the idea of creating an add-on that would allow
> users to share their browser history so we could better understand what
> sites users are visiting (as opposed to assuming Alexa is the best).
> Some concerns about privacy, but a webapp that allowed users to edit the
> history entries that are submitted seems like a good compromise.
>
> * Regarding community engagement, be very careful that we're not just
> showing up asking people to do work for us, e.g., we need help to fix
> content in your country vs. please do this work for our team. Leonard
> showing up asking people to do work for us, e.g., we need help to fix
> said that contacting them in their own language is better than just
> English (especially for the Mozilla Hispano community, there are lots
> who could help who don't speak English). Robert Nyman reminded us to be
> English (especially for the Mozilla Hispano community, there are lots
> careful again, let's not just take them for granted and always ask, ask,
> ask, ask. So how do we establish a relationship where we're able and
> willing to contribute to their needs as well?
>
>
> ask, ask. So how do we establish a relationship where we're able and
> willing to contribute to their needs as well?
>
>
> --
> Mike Taylor
> Web Compat, Mozilla
> _______________________________________________
> Mike Taylor
> Web Compat, Mozilla
> compatibility mailing list
> compat...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/compatibility
>
Lawrence Mandel
Oct 9, 2013, 12:18:05 PM10/9/13
to Karl Dubost, compat...@lists.mozilla.org
----- Original Message -----
> About the specific topic of community engagement,
>
> Mike Taylor [2013-10-08T12:08]:
> About the specific topic of community engagement,
>
> Mike Taylor [2013-10-08T12:08]:
> > * Regarding community engagement, be very careful that we're not just
> > showing up asking people to do work for us, e.g., we need help to fix
> > content in your country vs. please do this work for our team.
Another way to think about this is that we want some volunteer Karls. People who will work as Web openers contacting sites, walking them through the issues, and making the case for supporting the open Web.
> > showing up asking people to do work for us, e.g., we need help to fix
> > content in your country vs. please do this work for our team.
> Yes. Definitely. Somehow it is more about knowing that
>
> 1. here there is work to do
> 2. people can get involved
> 3. this is the way to maximize the volunteer effort.
>
> I also want to broaden that in a way which doesn't make it specifically
> exclusive to Mozilla. We want to have the things being fixed for Firefox OS,
> Android (and Desktop) but it is necessary to be pushed in a way that will
> make it better for the Web as large. Often I test in Opera and some other
> browsers I have around and if not working I report it.
> There could have been a good opportunity of work with the Opera Open Web
> team… oh wait ;). We have contacts with Blackberry (webkit browser) team
> which has also issues.
> An example
> https://bugzilla.mozilla.org/show_bug.cgi?id=826517#c1
>
>
> > Leonard said that contacting them in their own language is better than just
> > English (especially for the Mozilla Hispano community, there are lots who
> > could help who don't speak English).
>
> > English (especially for the Mozilla Hispano community, there are lots who
> > could help who don't speak English).
>
> So here there's a need for people who are bridges.
> In our own team, I believe we have at least (English removed being our
> working language)
>
> * Hallvord: Norwegian
> * Mike: Portuguese (Brazil)
> * Karl: French, Japanese (a little bit), (I may brush up my german if needed,
> but tough)
>
> I don't know for Aaron, Lawrence, Jason, Vishy, etc.
My Hebrew is decent by rusty. My French is OK for travel but breaks down in e-mail.
> In our own team, I believe we have at least (English removed being our
> working language)
>
> * Hallvord: Norwegian
> * Mike: Portuguese (Brazil)
> * Karl: French, Japanese (a little bit), (I may brush up my german if needed,
> but tough)
>
> I don't know for Aaron, Lawrence, Jason, Vishy, etc.
Lawrence
>
>
> > Robert Nyman reminded us to be careful again, let's not just take them for
> > granted and always ask, ask, ask, ask. So how do we establish a
> > relationship where we're able and willing to contribute to their needs as
> > well?
>
>
> Yes yes yes. Agreed 1000 times. Volunteers contribute because they want to
> help not because they have too. I contributed to translations of W3C specs
> in the past. And it's something you do not at a regular pace and depending
> on your own schedule.
>
> It's also a good way to learn new things, and that might be a way to promote
> Web compatibility volunteer effort. What will you learn doing that?
>
>
> help not because they have too. I contributed to translations of W3C specs
> in the past. And it's something you do not at a regular pace and depending
> on your own schedule.
>
> It's also a good way to learn new things, and that might be a way to promote
> Web compatibility volunteer effort. What will you learn doing that?
>
>
Mike Taylor
Oct 16, 2013, 12:51:54 PM10/16/13
to compat...@lists.mozilla.org
On 09/10/2013 11:14, Lawrence Mandel wrote:
> Let's discuss the criteria and get a bug on file about the design. We can follow up with some of the Toronto folks who have created t-shirts in the past. (There are several.)
I've opened https://bugzilla.mozilla.org/show_bug.cgi?id=927478 for a
> Let's discuss the criteria and get a bug on file about the design. We can follow up with some of the Toronto folks who have created t-shirts in the past. (There are several.)
sticker & tshirt design.
0 new messages