Re: I18N comments on Manifest for Web applications
On 3/24/15 3:07 PM, Arthur Barstow wrote: On 3/24/15 10:21 AM, Richard Ishida wrote: is it possible to send mail to www-internatio...@w3.org each time someone adds somethign to the github issue? (this is the list where we track and discuss issues). if so, i see no real difference between using github or bugzilla – our process is designed to cope with both bugzilla and email based comments (though it would normally be better to start with the right one rather than switch part way, so changing the SOD would indeed help). we should also ensure, however, that the titles of the issues and any associated notification mails always contain the i18n-issue-xxx string that will allow us and tracker to locate information for a given thread. FYI, I just added [i18n-issue-NNN] to the title of the five Github issues Ken created ([GH]) for the issues Addison submitted (and created the I18N-WG label for them). I don't know if the GH repo can be configured such that all activity for just these issues can be automagically Cc'ed to www-international but I know Dom has done so related work so I will follow up with him separately. FYI, Dom configured GH as requested: [[ I've updated github-notify-ml to support that feature [1], configured it for this particular repo and tested it [2]. Dom 1. https://github.com/dontcallmedom/github-notify-ml/compare/6ce58740823bf5ae3b239fa7ae411e0fc5a11ab3...20b523ab2cf12b8489e13f1241df2471ea650858 2. https://lists.w3.org/Archives/Public/www-international/2015JanMar/0186.html ]] Thanks Dom! -ArtB
Re: I18N comments on Manifest for Web applications
is it possible to send mail to www-internatio...@w3.org each time someone adds somethign to the github issue? (this is the list where we track and discuss issues). if so, i see no real difference between using github or bugzilla – our process is designed to cope with both bugzilla and email based comments (though it would normally be better to start with the right one rather than switch part way, so changing the SOD would indeed help). we should also ensure, however, that the titles of the issues and any associated notification mails always contain the i18n-issue-xxx string that will allow us and tracker to locate information for a given thread. ri On 20/03/2015 16:40, Christiansen, Kenneth R wrote: Marcos, Anssi, what do you think? I would prefer the comments on GitHub as it seems to be a great place for interacting with the web community, judging from our success so far. Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Friday, March 20, 2015 4:43 PM To: Christiansen, Kenneth R; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi Kenneth, Thanks for the reply. I know you're using GitHub. However, whenever I'm filing/forwarding comments on a document on behalf of the Working Group, I always look at the SOTD in the document in question to see what instructions the receiving WG has. In this case, you have a fairly generic SOTD, which says in part: -- This document was published by the Web Applications (WebApps) Working Group as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-webapps@w3.org (subscribe, archives). All comments are welcome. -- If you prefer to have comments filed to GitHub, perhaps modify your instructions? Thanks! Addison Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. -Original Message- From: Christiansen, Kenneth R [mailto:kenneth.r.christian...@intel.com] Sent: Friday, March 20, 2015 1:15 AM To: Phillips, Addison; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi there, The spec authors use GitHub for issue tracking. I duplicated your issues there: https://github.com/w3c/manifest/issues Thanks for looking into internationalization issues with the current spec. Cheers, Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Thursday, March 19, 2015 6:20 PM To: public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: I18N comments on Manifest for Web applications Hello Webapps, As previously mentioned, I am about to send you comments from the Internationalization Working Group on your document (whose current iteration lives at [1]). Because we use Tracker for our comments, I will be sending each comment under separate cover. The I18N WG is always happy to discuss our comments or ways to address same. Please let me know if you prefer to receive comments in a different format (such as Bugzilla) or if you need additional information. If you want to see a summary of our comments, you can find them tracked at [2] Regards (for I18N) Addison [1] http://www.w3.org/TR/appmanifest/ [2] http://www.w3.org/International/track/products/74 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
Re: I18N comments on Manifest for Web applications
As far as I know, you can watch individual issues with GitHub, so you could create a GitHub account with that email address and then watch relevant issues. Also it would mean that an email would be sent if someone mentioned the user (ie @www-international) in any issue Kenneth On Tue, Mar 24, 2015 at 3:25 PM Richard Ishida ish...@w3.org wrote: is it possible to send mail to www-internatio...@w3.org each time someone adds somethign to the github issue? (this is the list where we track and discuss issues). if so, i see no real difference between using github or bugzilla – our process is designed to cope with both bugzilla and email based comments (though it would normally be better to start with the right one rather than switch part way, so changing the SOD would indeed help). we should also ensure, however, that the titles of the issues and any associated notification mails always contain the i18n-issue-xxx string that will allow us and tracker to locate information for a given thread. ri On 20/03/2015 16:40, Christiansen, Kenneth R wrote: Marcos, Anssi, what do you think? I would prefer the comments on GitHub as it seems to be a great place for interacting with the web community, judging from our success so far. Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Friday, March 20, 2015 4:43 PM To: Christiansen, Kenneth R; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi Kenneth, Thanks for the reply. I know you're using GitHub. However, whenever I'm filing/forwarding comments on a document on behalf of the Working Group, I always look at the SOTD in the document in question to see what instructions the receiving WG has. In this case, you have a fairly generic SOTD, which says in part: -- This document was published by the Web Applications (WebApps) Working Group as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-webapps@w3.org (subscribe, archives). All comments are welcome. -- If you prefer to have comments filed to GitHub, perhaps modify your instructions? Thanks! Addison Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. -Original Message- From: Christiansen, Kenneth R [mailto:kenneth.r.christian...@intel.com] Sent: Friday, March 20, 2015 1:15 AM To: Phillips, Addison; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi there, The spec authors use GitHub for issue tracking. I duplicated your issues there: https://github.com/w3c/manifest/issues Thanks for looking into internationalization issues with the current spec. Cheers, Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Thursday, March 19, 2015 6:20 PM To: public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: I18N comments on Manifest for Web applications Hello Webapps, As previously mentioned, I am about to send you comments from the Internationalization Working Group on your document (whose current iteration lives at [1]). Because we use Tracker for our comments, I will be sending each comment under separate cover. The I18N WG is always happy to discuss our comments or ways to address same. Please let me know if you prefer to receive comments in a different format (such as Bugzilla) or if you need additional information. If you want to see a summary of our comments, you can find them tracked at [2] Regards (for I18N) Addison [1] http://www.w3.org/TR/appmanifest/ [2] http://www.w3.org/International/track/products/74 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
Re: I18N comments on Manifest for Web applications
On 3/24/15 10:21 AM, Richard Ishida wrote: is it possible to send mail to www-internatio...@w3.org each time someone adds somethign to the github issue? (this is the list where we track and discuss issues). if so, i see no real difference between using github or bugzilla – our process is designed to cope with both bugzilla and email based comments (though it would normally be better to start with the right one rather than switch part way, so changing the SOD would indeed help). we should also ensure, however, that the titles of the issues and any associated notification mails always contain the i18n-issue-xxx string that will allow us and tracker to locate information for a given thread. FYI, I just added [i18n-issue-NNN] to the title of the five Github issues Ken created ([GH]) for the issues Addison submitted (and created the I18N-WG label for them). I don't know if the GH repo can be configured such that all activity for just these issues can be automagically Cc'ed to www-international but I know Dom has done so related work so I will follow up with him separately. The boiler plate asking for feedback via GH and the Status section asking for feedback via p-webapps is certainly suboptimal. AFAIK, PubRules mandates the comment list. If we can't get that restriction lifted, I recommend the relevant text in the SotD clearly state using GH for comments/bugs/issues is *strongly preferred* and the list should only be used as a `last resort`. (FYI, all of WebApps' GH activity is mirrored to [p-w-gh], thus all I18n activity can be found in the archive, f.ex. via [i18n].) -Thanks, ArtB [GH] https://github.com/w3c/manifest/labels/I18N-WG [p-w-gh] https://lists.w3.org/Archives/Public/public-webapps-github/ [i18n] https://www.w3.org/Search/Mail/Public/search?keywords=hdr-1-name=subjecthdr-1-query=i18nindex-grp=Public_FULLindex-type=ttype-index=public-webapps-github
RE: I18N comments on Manifest for Web applications
Hi there, The spec authors use GitHub for issue tracking. I duplicated your issues there: https://github.com/w3c/manifest/issues Thanks for looking into internationalization issues with the current spec. Cheers, Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Thursday, March 19, 2015 6:20 PM To: public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: I18N comments on Manifest for Web applications Hello Webapps, As previously mentioned, I am about to send you comments from the Internationalization Working Group on your document (whose current iteration lives at [1]). Because we use Tracker for our comments, I will be sending each comment under separate cover. The I18N WG is always happy to discuss our comments or ways to address same. Please let me know if you prefer to receive comments in a different format (such as Bugzilla) or if you need additional information. If you want to see a summary of our comments, you can find them tracked at [2] Regards (for I18N) Addison [1] http://www.w3.org/TR/appmanifest/ [2] http://www.w3.org/International/track/products/74 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
RE: I18N comments on Manifest for Web applications
Hi Kenneth, Thanks for the reply. I know you're using GitHub. However, whenever I'm filing/forwarding comments on a document on behalf of the Working Group, I always look at the SOTD in the document in question to see what instructions the receiving WG has. In this case, you have a fairly generic SOTD, which says in part: -- This document was published by the Web Applications (WebApps) Working Group as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-webapps@w3.org (subscribe, archives). All comments are welcome. -- If you prefer to have comments filed to GitHub, perhaps modify your instructions? Thanks! Addison Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. -Original Message- From: Christiansen, Kenneth R [mailto:kenneth.r.christian...@intel.com] Sent: Friday, March 20, 2015 1:15 AM To: Phillips, Addison; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi there, The spec authors use GitHub for issue tracking. I duplicated your issues there: https://github.com/w3c/manifest/issues Thanks for looking into internationalization issues with the current spec. Cheers, Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Thursday, March 19, 2015 6:20 PM To: public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: I18N comments on Manifest for Web applications Hello Webapps, As previously mentioned, I am about to send you comments from the Internationalization Working Group on your document (whose current iteration lives at [1]). Because we use Tracker for our comments, I will be sending each comment under separate cover. The I18N WG is always happy to discuss our comments or ways to address same. Please let me know if you prefer to receive comments in a different format (such as Bugzilla) or if you need additional information. If you want to see a summary of our comments, you can find them tracked at [2] Regards (for I18N) Addison [1] http://www.w3.org/TR/appmanifest/ [2] http://www.w3.org/International/track/products/74 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
RE: I18N comments on Manifest for Web applications
Marcos, Anssi, what do you think? I would prefer the comments on GitHub as it seems to be a great place for interacting with the web community, judging from our success so far. Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Friday, March 20, 2015 4:43 PM To: Christiansen, Kenneth R; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi Kenneth, Thanks for the reply. I know you're using GitHub. However, whenever I'm filing/forwarding comments on a document on behalf of the Working Group, I always look at the SOTD in the document in question to see what instructions the receiving WG has. In this case, you have a fairly generic SOTD, which says in part: -- This document was published by the Web Applications (WebApps) Working Group as a Working Draft. This document is intended to become a W3C Recommendation. If you wish to make comments regarding this document, please send them to public-webapps@w3.org (subscribe, archives). All comments are welcome. -- If you prefer to have comments filed to GitHub, perhaps modify your instructions? Thanks! Addison Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. -Original Message- From: Christiansen, Kenneth R [mailto:kenneth.r.christian...@intel.com] Sent: Friday, March 20, 2015 1:15 AM To: Phillips, Addison; public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: RE: I18N comments on Manifest for Web applications Hi there, The spec authors use GitHub for issue tracking. I duplicated your issues there: https://github.com/w3c/manifest/issues Thanks for looking into internationalization issues with the current spec. Cheers, Kenneth -Original Message- From: Phillips, Addison [mailto:addi...@lab126.com] Sent: Thursday, March 19, 2015 6:20 PM To: public-webapps@w3.org Cc: public-i18n-c...@w3.org Subject: I18N comments on Manifest for Web applications Hello Webapps, As previously mentioned, I am about to send you comments from the Internationalization Working Group on your document (whose current iteration lives at [1]). Because we use Tracker for our comments, I will be sending each comment under separate cover. The I18N WG is always happy to discuss our comments or ways to address same. Please let me know if you prefer to receive comments in a different format (such as Bugzilla) or if you need additional information. If you want to see a summary of our comments, you can find them tracked at [2] Regards (for I18N) Addison [1] http://www.w3.org/TR/appmanifest/ [2] http://www.w3.org/International/track/products/74 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
I18N comments on Manifest for Web applications
Hello Webapps, As previously mentioned, I am about to send you comments from the Internationalization Working Group on your document (whose current iteration lives at [1]). Because we use Tracker for our comments, I will be sending each comment under separate cover. The I18N WG is always happy to discuss our comments or ways to address same. Please let me know if you prefer to receive comments in a different format (such as Bugzilla) or if you need additional information. If you want to see a summary of our comments, you can find them tracked at [2] Regards (for I18N) Addison [1] http://www.w3.org/TR/appmanifest/ [2] http://www.w3.org/International/track/products/74 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
