Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

2015-07-06 Thread Xiaoqian Wu

 On 6 Jul, 2015, at 5:18 pm, Hayato Ito hay...@google.com wrote:
 
 I've finished the migration. All 141 bugs have been migrated [1]. I'll triage 
 the migrated bugs manually later.
 
 I'm sorry that public-webapps@ has received the mass flood of bugspam mail 
 again this time. That's unintentional.
 The lesson for for the future: We need to change also the setting of *every* 
 bugs to stop the auto-emails, not only from the default CC list.
 
 From now on, please use the GitHub issues [2] to file a bug for Web 
 Components. I've already updated [3] the editors' drafts of Custom Elements 
 and HTML Imports so that they have a link to GitHub Issues.
 xiaoqian@ will kindly disable the bugzilla component, Component Models, so 
 that people won't add a bug there.

Thanks Hayato.

Fyi, this bugzilla component has been disabled and renamed as HISTORICAL - 
Component Model”.

—
xiaoqian

 
 - [1]: https://github.com/w3c/webcomponents/issues/119 
 https://github.com/w3c/webcomponents/issues/119
 - [2]: https://github.com/w3c/webcomponents/issues 
 https://github.com/w3c/webcomponents/issues
 - [3]: 
 https://github.com/w3c/webcomponents/commit/54434ada278440999649915b00772b6e96e57d4d
  
 https://github.com/w3c/webcomponents/commit/54434ada278440999649915b00772b6e96e57d4d
 
 
 On Wed, Jul 1, 2015 at 4:24 PM Xiaoqian Wu xiaoq...@w3.org 
 mailto:xiaoq...@w3.org wrote:
 
 On 1 Jul, 2015, at 1:30 pm, Hayato Ito hay...@google.com 
 mailto:hay...@google.com wrote:
 
 Thank you. I appreciate that. Then, let me migrate all open bugs of 
 'Component Model'. I think that include also HTML Imports bugs in addition 
 to Custom Elements bugs.
 When I finish, I'll announce that.
 
 SGTM. Please go ahead.
 
 —
 xiaoqian



Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

2015-07-06 Thread Hayato Ito
I've finished the migration. All 141 bugs have been migrated [1]. I'll
triage the migrated bugs manually later.

I'm sorry that public-webapps@ has received the mass flood of bugspam mail
again this time. That's unintentional.
The lesson for for the future: We need to change also the setting of
*every* bugs to stop the auto-emails, not only from the default CC list.

From now on, please use the GitHub issues [2] to file a bug for Web
Components. I've already updated [3] the editors' drafts of Custom Elements
and HTML Imports so that they have a link to GitHub Issues.
xiaoqian@ will kindly disable the bugzilla component, Component Models,
so that people won't add a bug there.

- [1]: https://github.com/w3c/webcomponents/issues/119
- [2]: https://github.com/w3c/webcomponents/issues
- [3]:
https://github.com/w3c/webcomponents/commit/54434ada278440999649915b00772b6e96e57d4d


On Wed, Jul 1, 2015 at 4:24 PM Xiaoqian Wu xiaoq...@w3.org wrote:


 On 1 Jul, 2015, at 1:30 pm, Hayato Ito hay...@google.com wrote:

 Thank you. I appreciate that. Then, let me migrate all open bugs of
 'Component Model'. I think that include also HTML Imports bugs in addition
 to Custom Elements bugs.
 When I finish, I'll announce that.


 SGTM. Please go ahead.

 —
 xiaoqian



Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

2015-07-01 Thread Xiaoqian Wu

 On 1 Jul, 2015, at 1:30 pm, Hayato Ito hay...@google.com wrote:
 
 Thank you. I appreciate that. Then, let me migrate all open bugs of 
 'Component Model'. I think that include also HTML Imports bugs in addition to 
 Custom Elements bugs.
 When I finish, I'll announce that.

SGTM. Please go ahead.

—
xiaoqian

Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

2015-06-30 Thread Hayato Ito
Thank you. I appreciate that. Then, let me migrate all open bugs of
'Component Model'. I think that include also HTML Imports bugs in addition
to Custom Elements bugs.
When I finish, I'll announce that.

On Tue, Jun 30, 2015 at 11:21 PM Xiaoqian Wu xiaoq...@w3.org wrote:

 Hi Hayato,

 public-webapps has been removed from the default CC list of ‘Component
 Model’. Please let us know when you finish migrating and we will recover
 this component ASAP.

 Thanks.

 —
 xiaoqian

  On 29 Jun, 2015, at 10:42 pm, Arthur Barstow art.bars...@gmail.com
 wrote:
 
  Yves, Xiaoqian, Mike - would one of you please do as Hayato requests
 below (and then notify him so he can move the Custom Elements bugs to
 Github)?
 
  -Thanks, ArtB
 
  On 6/25/15 2:49 AM, Hayato Ito wrote:
  I am thinking about migrating Custom Element bugs[1] to Web Components
 GitHub Issues [2], as I did it for Shadow DOM a few weeks ago, for the
 consistency.
 
  Could someone turn off the automatic email to public-webapps for Custom
 Elements Bugs in the bugzilla so that we won't receive the mass flood of
 bugspam by marking the all bugs MOVED? I'm assuming the automatic email is
 on for public-webapps@.
 
  If you have any concerns about migrating, let me know that.
 
  [1]
 https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14968hide_resolved=1
  [2] https://github.com/w3c/webcomponents/issues
 
  On Thu, May 28, 2015 at 10:35 AM Hayato Ito hay...@google.com mailto:
 hay...@google.com wrote:
 
 I totally agree. I'm really sorry for spamming. I forgot that
 closing a bug would trigger sending a mail to public-webapps@. My
 bad.
 
 I thought that a closing bug would notify only people who opted-in
 to add themselves to a list of cc in each bug. That might be a
 good opportunity for them to keep tracking of the bug status by
 subscribing a migrated bug on GitHub Issues.
 
 On Thu, May 28, 2015 at 6:49 AM Tab Atkins Jr.
 jackalm...@gmail.com mailto:jackalm...@gmail.com wrote:
 
 Note for the future (to you and editors of other specs in
 WebApps):
 
 Before doing this kind of mass bug editting, please turn off the
 automatic email to public-webapps.  If you can't do that
 yourself,
 Mike Smith can (at least, he's done it in the past).  That
 prevents
 the mass flood of bugspam from clogging up people's inboxes. ^_^
 
 ~TJ
 
 On Tue, May 26, 2015 at 8:30 PM, Hayato Ito hay...@google.com
 mailto:hay...@google.com wrote:
  PSA: I've finished the migration. All open bugs are now
 marked as MOVED
  with a link to the corresponding GitHub issue.
 
  On Mon, May 25, 2015 at 5:58 PM Hayato Ito
 hay...@google.com mailto:hay...@google.com wrote:
 
  Regarding with the Shadow DOM spec, more and more workflows
 are happening
  [1] on GitHub w3c/webcomponents repository recently.
  Therefore, I am thinking about migrating the bugs of the
 Shadow DOM spec,
  from the bugzilla [2], to the GitHub issues [3], as some of
 other specs are
  already doing so.
 
  As an experiment, I've just migrated the existing open bugs
 on the
  bugzilla to the GitHub issues, by a tiny script I've
 written using GitHub
  APIs.
 
  Unless there is an objection to the migration, I am going
 to close the
  existing open Shadow DOM spec bugs on the bugzilla, with a
 link to the
  corresponding bug on the GitHub issues.
 
  Please let me know if you have a concern.
 
  [1] https://github.com/w3c/webcomponents/commits/gh-pages
  [2]
 https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14978
  [3] https://github.com/w3c/webcomponents/issues
 
 
 
 




Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

2015-06-30 Thread Xiaoqian Wu
Hi Hayato, 

public-webapps has been removed from the default CC list of ‘Component Model’. 
Please let us know when you finish migrating and we will recover this component 
ASAP.

Thanks.

—
xiaoqian

 On 29 Jun, 2015, at 10:42 pm, Arthur Barstow art.bars...@gmail.com wrote:
 
 Yves, Xiaoqian, Mike - would one of you please do as Hayato requests below 
 (and then notify him so he can move the Custom Elements bugs to Github)?
 
 -Thanks, ArtB
 
 On 6/25/15 2:49 AM, Hayato Ito wrote:
 I am thinking about migrating Custom Element bugs[1] to Web Components 
 GitHub Issues [2], as I did it for Shadow DOM a few weeks ago, for the 
 consistency.
 
 Could someone turn off the automatic email to public-webapps for Custom 
 Elements Bugs in the bugzilla so that we won't receive the mass flood of 
 bugspam by marking the all bugs MOVED? I'm assuming the automatic email is 
 on for public-webapps@.
 
 If you have any concerns about migrating, let me know that.
 
 [1] 
 https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14968hide_resolved=1
 [2] https://github.com/w3c/webcomponents/issues
 
 On Thu, May 28, 2015 at 10:35 AM Hayato Ito hay...@google.com 
 mailto:hay...@google.com wrote:
 
I totally agree. I'm really sorry for spamming. I forgot that
closing a bug would trigger sending a mail to public-webapps@. My bad.
 
I thought that a closing bug would notify only people who opted-in
to add themselves to a list of cc in each bug. That might be a
good opportunity for them to keep tracking of the bug status by
subscribing a migrated bug on GitHub Issues.
 
On Thu, May 28, 2015 at 6:49 AM Tab Atkins Jr.
jackalm...@gmail.com mailto:jackalm...@gmail.com wrote:
 
Note for the future (to you and editors of other specs in
WebApps):
 
Before doing this kind of mass bug editting, please turn off the
automatic email to public-webapps.  If you can't do that yourself,
Mike Smith can (at least, he's done it in the past).  That
prevents
the mass flood of bugspam from clogging up people's inboxes. ^_^
 
~TJ
 
On Tue, May 26, 2015 at 8:30 PM, Hayato Ito hay...@google.com
mailto:hay...@google.com wrote:
 PSA: I've finished the migration. All open bugs are now
marked as MOVED
 with a link to the corresponding GitHub issue.

 On Mon, May 25, 2015 at 5:58 PM Hayato Ito
hay...@google.com mailto:hay...@google.com wrote:

 Regarding with the Shadow DOM spec, more and more workflows
are happening
 [1] on GitHub w3c/webcomponents repository recently.
 Therefore, I am thinking about migrating the bugs of the
Shadow DOM spec,
 from the bugzilla [2], to the GitHub issues [3], as some of
other specs are
 already doing so.

 As an experiment, I've just migrated the existing open bugs
on the
 bugzilla to the GitHub issues, by a tiny script I've
written using GitHub
 APIs.

 Unless there is an objection to the migration, I am going
to close the
 existing open Shadow DOM spec bugs on the bugzilla, with a
link to the
 corresponding bug on the GitHub issues.

 Please let me know if you have a concern.

 [1] https://github.com/w3c/webcomponents/commits/gh-pages
 [2]
https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14978
 [3] https://github.com/w3c/webcomponents/issues


 
 




[admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

2015-06-29 Thread Arthur Barstow
Yves, Xiaoqian, Mike - would one of you please do as Hayato requests 
below (and then notify him so he can move the Custom Elements bugs to 
Github)?


-Thanks, ArtB

On 6/25/15 2:49 AM, Hayato Ito wrote:
I am thinking about migrating Custom Element bugs[1] to Web Components 
GitHub Issues [2], as I did it for Shadow DOM a few weeks ago, for the 
consistency.


Could someone turn off the automatic email to public-webapps for 
Custom Elements Bugs in the bugzilla so that we won't receive the mass 
flood of bugspam by marking the all bugs MOVED? I'm assuming the 
automatic email is on for public-webapps@.


If you have any concerns about migrating, let me know that.

[1] 
https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14968hide_resolved=1

[2] https://github.com/w3c/webcomponents/issues

On Thu, May 28, 2015 at 10:35 AM Hayato Ito hay...@google.com 
mailto:hay...@google.com wrote:


I totally agree. I'm really sorry for spamming. I forgot that
closing a bug would trigger sending a mail to public-webapps@. My bad.

I thought that a closing bug would notify only people who opted-in
to add themselves to a list of cc in each bug. That might be a
good opportunity for them to keep tracking of the bug status by
subscribing a migrated bug on GitHub Issues.

On Thu, May 28, 2015 at 6:49 AM Tab Atkins Jr.
jackalm...@gmail.com mailto:jackalm...@gmail.com wrote:

Note for the future (to you and editors of other specs in
WebApps):

Before doing this kind of mass bug editting, please turn off the
automatic email to public-webapps.  If you can't do that yourself,
Mike Smith can (at least, he's done it in the past).  That
prevents
the mass flood of bugspam from clogging up people's inboxes. ^_^

~TJ

On Tue, May 26, 2015 at 8:30 PM, Hayato Ito hay...@google.com
mailto:hay...@google.com wrote:
 PSA: I've finished the migration. All open bugs are now
marked as MOVED
 with a link to the corresponding GitHub issue.

 On Mon, May 25, 2015 at 5:58 PM Hayato Ito
hay...@google.com mailto:hay...@google.com wrote:

 Regarding with the Shadow DOM spec, more and more workflows
are happening
 [1] on GitHub w3c/webcomponents repository recently.
 Therefore, I am thinking about migrating the bugs of the
Shadow DOM spec,
 from the bugzilla [2], to the GitHub issues [3], as some of
other specs are
 already doing so.

 As an experiment, I've just migrated the existing open bugs
on the
 bugzilla to the GitHub issues, by a tiny script I've
written using GitHub
 APIs.

 Unless there is an objection to the migration, I am going
to close the
 existing open Shadow DOM spec bugs on the bugzilla, with a
link to the
 corresponding bug on the GitHub issues.

 Please let me know if you have a concern.

 [1] https://github.com/w3c/webcomponents/commits/gh-pages
 [2]
https://www.w3.org/Bugs/Public/showdependencytree.cgi?id=14978
 [3] https://github.com/w3c/webcomponents/issues