- From: Coralie Mercier <coralie@w3.org>
- Date: Mon, 12 May 2014 22:49:05 +0200
- To: public-webizen@w3.org
Hi all,
The minutes of today's teleconference are at:
http://www.w3.org/2014/05/12-webizen-minutes.html
Summary:
--------
We went over the content of the wiki that changed recently.
Name:
Help still needed to suggest a better name (one that has some sparkle to
it).
Benefits:
* We discussed the pluses and minuses around Webizen Blogging,
particularly on the W3C Blog which drives a lot of traffic. Suggestion
that Webizen AC rep might have write-access to W3C Blog, and At Large
Webizen to a separate Blog.
* Make Webizen ID card optional, propose that t-shirt be either optional,
or that shipping be covered by Webizens.
Voting mechanism:
"Webizen voting for the AC" section restructured.
Jeff called attention that proposal 2 and beyond are welcome in the wiki.
Webizen network structure:
The association with a W3C Office, or chapter, isn't ironed out.
Comm plan:
-1 on a discount for Early adopters; counter proposal: leverage low
Webizen ID number.
Next meeting: (and last before the AC Meeting) 2 June, same time, same
code.
The wiki has been updated by Jeff since the call ended.
Here's the text snapshot of the minutes:
----------------------------------------
Webizen task force meeting
12 May 2014
See also: [2]IRC log
[2] http://www.w3.org/2014/05/12-webizen-irc
Attendees
Present
Jean-Charles Verdié, Coralie Mercier, Veronica Thom,
Jeff Jaffe, Virginie Galindo
Regrets
Andrei Sambra
Chair
Jeff Jaffe
Scribe
Coralie Mercier
Contents
* [3]Topics
1. [4]Name
2. [5]Package of benefits
3. [6]Participation Benefits and Non Benefits
4. [7]Drafting a Webizen network structure
5. [8]Marketing and Communications
6. [9]Recent e-mail discussions
7. [10]Actions
8. [11]Next Meeting
9. [12]AC Meeting discussion
* [13]Summary of Action Items
__________________________________________________________
<koaliie> [14]Prevous Webizen task force meeting (2014-05-05)
[14] http://www.w3.org/2014/05/05-webizen-minutes.html
<scribe> scribe: Coralie
<scribe> scribenick: koalie
Jeff: Any point we should discuss, further to e-mail activity?
Virginie: Let's go over wiki, I suggest
Jeff: OK
... Background hasn't changed
... Concept hasn't changed
Name
Jeff: Name
... there are a number of proposed names
... Ann added a note that name should have some sparkle
... and note also of meaning in cultures
... "Webizen" has maybe a bad connotation in French, Virginie,
any opinion? Frenchies on the call?
JC: "Collaborator", which was initially suggested, would have a
bad connotation in French
... I don't see anything bad with "Webizen"
Coralie: neither do I
<virginie> note : I am ok with webizen
Jeff: "Zen" means something in French
... also "citizen/citoyen"
JC: I can't speak for that person, but I disagree.
... and there is nothing bad I can think of with "citoyen"
Jeff: Let's move away then
Package of benefits
Jeff: Some did not like the idea of a web ID card
Virginie: Could make it a possibility
... they don't have to have it
<veronica> how about just an ecard?
Jeff: We can make it optional, or even virtual
JC: I was concerned about yet another card in my wallet
... Either virtual or optional would be good
Jeff: OK, we can make that change.
... There was a concern about shipping, similarly for the idea
of a t-shirt
... We could also charge for shipping
... How does that sound?
<veronica> ok with me
<virginie> +1 to me
Coralie: I'd suggest to table for now with a note in wiki, till
we have a stronger list of packages and we know which we can
nix which to make optional
Jeff: OK
... Chaals has concerns on a Webizen Blog
... putting them on the W3C blog would require some overhead
virginie: I don't understand, is that a separate blog?
Jeff: The idea would be a link to a webizen blog
... a clearly identified place for webizen to reflect on the
Web, however they want to
... You can have an unmoderated, or a moderated Blog
... It should be the Webizens themselves to moderate it, rather
than the W3C team.
Virginie: For me the value, maybe the vision I have is wrong,
would be to be on the W3C blog
... and it should be moderated by Team
... That would be the value
... Another silo for discussion would not be valuable.
+1 to virginie
JC: I'd tend to disagree on the Blog
... People who will blog will blog on their own blog
... They might not be willing to blog somewhere else
... We could duplicate entries, with authors' agreement
Coralie: +1 to JC, people favour blogging in their own space
... that being said, the W3C blog generates a lot of views
... so people might like the appeal to blog there
Jeff: If we were to open up to Webizen, given the WC blog is a
trusted place, and quality control is required, it would mean a
lot of overhead
Coralie: Yes
Virginie: When I said the Webizens could blog directly in W3C
Blog, I wasn't thinking 10 entries per day.
Jeff: If you call it a benefit that they have a voice in the
W3C Blog, then at least in theory, you're inviting everybody to
blog on the W3C blog
... and you get a quantity and quality issue to manage
... how would you manage it?
... W3C bloggers have write access to a trusted space.
... Another thing we could do is that elected representatives
can write on the W3C Blog
... and the Webizens would have a voice on a separate blog
... What do people think about that?
<virginie> ok
Coralie: That would work for me
<veronica> ok
Jeff: Any other comments on the benefits before we move on?
Participation Benefits and Non Benefits
Jeff: Section on elected AC reps
... chaals came up with a crazy formula on the ML
... for Webizen voting for the AC, some people on AC forum had
a lot to say,
... So I restructured that section a bit
... to say that the techniques that Webizens would use to vote
for their AC reps will be determined by the webizens themselves
... and we would use the wiki to collect the proposals; I wrote
proposal 1.
... I have yet to see a proposal 2
... Calling attention now that proposals are welcome in the
wiki.
Virginie: I have a question, as I wasn't there when you started
to discuss this
... What is the critical mass which would make the webizens
choose a mechanism?
... I understand there is a wish to let them design their own
system
Jeff: I should add to the wiki that we can revisit every year
Virginie: you may ask every 2 years if all webizen are happy
with the voting process, making sure everyone agrees
Jeff: It may never be the case that everyone agrees, but I
agree with everything you said before "until everyone agrees".
Drafting a Webizen network structure
Jeff: I modified a bit that text because I had question;
Virginie as original author, please ensure this is right
Virginie: actually, chaals asked for clarification
... I was thinking about fees
... It was taken from OWASP
... I don't know if it makes sense to give money to the W3C
Offices; I don't know how the existing system works
... The idea is to associate people with an Office, be part of
a mailing list, etc., and pay with that office.
Jeff: I like the idea of having association with an office
... we need to have sufficient scale,
... otherwise it won't make a big difference
... I don't want to overly describe it until we have more
experience with it overall.
+1
<virginie> +1
Virginie: Makes sense.
Jeff: Coralie wrote to the W3C Offices to introduce the
program, seek feedback..
Marketing and Communications
<jeff> [Koalie reviews the Marketing and Communications part of
the wiki]
<jeff>
[15]https://www.w3.org/wiki/Webizen#Marketing_and_Communication
s
[15] https://www.w3.org/wiki/Webizen#Marketing_and_Communications
<Zakim> jeff, you wanted to discuss early adopters
Jeff: I have a different proposal for early adopters
... People I'd expect to rush and join would be like us, active
in W3C
... and the last thing I want to give them is a discount!
... They would probably be willing to pay more
... -1 to discount, I don't like this idea
... but if we have ID numbers, low serial number will be
cherished
+1
<Zakim> jj, you wanted to discuss cost
Jeff: I have a question on estimated cost for visual design and
website
... When I look at the list of things above, on the website,
none of that feels like it shoud cost $15-20K
Coralie: the figure came via Ian who's had to have visual
identity and website produced for other initiatives.
Jeff: OK
... Let's use the wiki to drive our early adoption
... I don't know that there is anything else on the wiki to go
over
... any other input before we move to e-mail discussions?
Recent e-mail discussions
[16]http://lists.w3.org/Archives/Public/public-webizen/2014May/
[16] http://lists.w3.org/Archives/Public/public-webizen/2014May/
Jeff: Ossi from the W3C Offices has sent a long reply on the
W3C Office mailing list
... he has some use-cases
... not sure it really bears on the proposal in the webizen
wiki right now.
Actions
Jeff: Veronica, update on your action?
Veronica: Ann Bassetti wanted to compare W3C member and webizen
proposal
... I have an excel document
... The benefits we were looking at for discount:
... - W3C Validator Suite
... - W3C Training
... - W3C Conference
... I looked at the services; the typical early bird rates
offered range between 15-20%
... I had recommended that a 20% discount to Webizens for
Training and W3Conf might sound reasonable
... When I asked busdev team, they were not so inclined, and
would support 10%
... That being said, we don't have a program for member
discounts
... everyone is able to take advantage of an early bird
discount.
... I mentioned Validator Suite, during MWC this year, busdev
had an offer with 200 free credits (amounts to about 20%)
... I proposed the same for W3C Validator Suite, but again,
busdev would support 10%
... the feeling on the Webizen call at the time was that 10%
wasn't a lot of discount
+1, my +1 at the time still stands
Jeff: +1, 10% is a joke. I understand we don't have even
formalized a member discount program.
<jcverdie> +1 again, indeed 10% is a joke
Jeff: You may need to make a formal proposal to W3M.
veronica: I'll do that.
Jeff: That takes care of action items.
Next Meeting
Jeff: Next meeting? or are we done?
... I'll be traveling in the coming weeks, but should we have
one more meeting before the AC meeting?
... June 2nd same time?
<veronica> ok
<jcverdie> LGTM
works for me
<virginie> ok
Jeff: I'll have this set up, then.
AC Meeting discussion
Virginie: What will be requested from the AC at the AC Meeting?
... choose among the package, or adoption of the full package?
Jeff: I plan to ask the AC 5 questions
... I plan to get their advice
[17]https://www.w3.org/wiki/Webizen#ISSUES:_June_discussion_at_
the_W3C_Advisory_Committee_Meeting
[17]
https://www.w3.org/wiki/Webizen#ISSUES:_June_discussion_at_the_W3C_Advisory_Committee_Meeting
Virginie: for me the package looks great
... but is it a list to choose three from?
... the full list? is W3C ready to support the full list?
Jeff: Internal management meeting late June (the Woods meeting)
... to make final decision on the Webizen program
... the point of the AC discussion is to get people's input
... it's not going to be a vote
... it's about people's thoughts on these ideas.
virginie: OK.
Jeff: We're done for the day.
... and for three weeks.
... Let's continue to discuss on the mailing list
... and update the wiki
... Final call on 2 June.
<jeff> [adjourned]
<veronica> bye
Summary of Action Items
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [18]scribe.perl version
1.138 ([19]CVS log)
$Date: 2014-05-12 20:28:56 $
[18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[19] http://dev.w3.org/cvsweb/2002/scribe/
--
Coralie Mercier - W3C Communications Team - http://www.w3.org
mailto:coralie@w3.org +336 4322 0001 http://www.w3.org/People/CMercier/
Received on Monday, 12 May 2014 20:49:15 UTC