Invitation to WebApps Mailing List

[Doug Schepers]

Hi, WebAPI and WAF fans!

The kings are dead! Long live the king!

As planned a few months ago, we have successfully merged the Web
Application Formats and WebAPI WGs into a single powerful new group, the
Web Application Working Group (WebApps WG to its friends). We made
front page news at W3C:
http://www.w3.org/News/2008#item107

If you are a member of the public interested in participating in
discussions, please join the public-webapps mailing list:
http://lists.w3.org/Archives/Public/public-webapps/

If you wish to join the WG, you can find more info on the home page
(look for the "join" link):
http://www.w3.org/2008/webapps/

Regards-
-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF

[Doug Schepers]

Hi, WebApps Fans-

As a follow-on to my previous invitation, I just wanted to give a tip
about what I see as the easiest way to do this transition.

Step 1: Join public-webapps (
http://lists.w3.org/Archives/Public/public-webapps/ ); you need to do
this explicitly even if you're a members of the WebApps WG;

Step 2: When replying to an email thread on either public-webapi or
public-appformats, add public-webapps to the recipients list;

Step 3: When replying to an email thread on public-webapps, remove
public-webapi or public-appformats from the recipients list, if they are
on there.

This way, we can have a fairly smooth transfer, though for some older
issues, you may have to refer to some emails on one of the older lists.

Thanks!
-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF

[Maciej Stachowiak]

Hi Doug,

Would it be possible to just automatically subscribe members of both
old lists to the new list, to smooth the transition?

Post by Doug Schepers
Hi, WebApps Fans-
As a follow-on to my previous invitation, I just wanted to give a
tip about what I see as the easiest way to do this transition.
Step 1: Join public-webapps ( http://lists.w3.org/Archives/Public/public-webapps/
); you need to do this explicitly even if you're a members of the
WebApps WG;
Step 2: When replying to an email thread on either public-webapi or
public-appformats, add public-webapps to the recipients list;
Step 3: When replying to an email thread on public-webapps, remove
public-webapi or public-appformats from the recipients list, if they
are on there.
This way, we can have a fairly smooth transfer, though for some
older issues, you may have to refer to some emails on one of the
older lists.
Thanks!
-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF

[Doug Schepers]

Hi, Maciej-

Would it be possible to just automatically subscribe members of both old
lists to the new list, to smooth the transition?

Yes, it is possible.

I had thought of doing that, and got as far as concatenating a list of
all subscribers to all lists and diffing that with the current
subscribers to public-webapps... there's about 266 people subscribed to
public-webapi and public-appformats that aren't yet on public-webapps.
It would be easy enough for me to add them manually, with a notification
email sent to all new subscribers.

However...
1) some people may object to being autosubscribed
2) I don't know if there are IPP implications

I will check with our legal/comm people on the IPP issue tomorrow.

As for being subscribed to a list without being asked... I don't know.
On the one hand, these people are presumably already interested in the
topics because they subscribed to at least one of the lists (and there
was a lot of overlap), and they can easily unsubscribe... but on the
other, well, people are weird. What does everyone else think?

Like I said, I'm happy to do it if it's seen as a reasonable thing to
do. It would take me less time than it did to write this email, for
sure. :)

Regards-
-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF

[Ian Hickson]

Post by Doug Schepers
As for being subscribed to a list without being asked... I don't know.

Just position it as a list renaming. :-) Then they're aren't being
subscribed to a new list, so much as having an existing subscription
updated for their convenience.