[KI-LC] [BoT] Group "Join" Form
Joni Brennan
joni at ieee-isto.org
Tue Jun 30 08:32:41 PDT 2009
In the context of the User Driven nature of Kantara Initiative I see value
in officer operational participation where ever possible - even if that
participation is limited to monitoring. I see Staff as the Primary layer
here and I see the officer moderator as the Secondary layer and the role as
being more informative than operational. It may be a subtle change to the
policy but I think it aligns with our overall operational visions.
In this case the value of assigning an officer as list moderator is that
they are kept informed on behalf of the group. One Example: moderators get
notices of new and leaving subscriptions.
We could even broaden the scope to add more value and designate an officer
as a list Administrator - which would give that officer the ability to admin
the list in the case that staff was unavailable.
My goal here is to include an officer to provide value and buy-in. I'm
happy to hear additional thoughts for or against this direction.
thx
- Joni
On Tue, Jun 30, 2009 at 11:18 AM, J. Trent Adams <adams at isoc.org> wrote:
> Joni -
>
> What tasks do you believe a "Moderator" should be performing?
>
> - Trent
>
>
> Joni Brennan wrote:
> > Hello,
> >
> > I would like to add a provision to section 5 stating that, in addition
> > to the staff layer of management, ONE officer from each WG/DG will be
> > designated as a list moderator. This could be the Chair, Vice-Chair
> > or Secretary from each group.
> >
> > Or we could decided that one of those players will always = a list
> > moderator. Perhaps Trent can weigh in on which WG/DG officer would be
> > the best person to fill this role.
> >
> > Thanks,
> >
> > Joni
> >
> > On Tue, Jun 30, 2009 at 9:34 AM, J. Trent Adams <adams at isoc.org
> > <mailto:adams at isoc.org>> wrote:
> >
> > Roger M. -
> >
> > This appears to be a great clarification and streamlining of the
> > process
> > we were trying to define. I definitely appreciate the time and
> effort
> > you put into carefully preserving the spirit of the prior work, while
> > also improving it.
> >
> > My nits are so minor I feel embarrassed even bringing them up:
> >
> > 1. The term "Intellectual Property Rights" is
> > introduced earlier than the acronym was
> > parenthetically defined. Perhaps moving up the
> > acronym to the first instance?
> >
> > 2. The term "Follower" is now only referenced in
> > the second bullet of Section (6). Perhaps it makes
> > sense to eliminate the term from the Definitions
> > Section (2) and insert the meaning in (6)?
> >
> > 3. If we're leveraging defined terms (e.g. Member,
> > Participant, etc.) from other Controlling
> > Documents, do we need to formally reference
> > them in some way? Perhaps by including them
> > in the Definitions Section (2), linking a reference
> > to the Bylaws and/or Operating Procedures as
> > appropriate?
> >
> > 4. In the same vein, if we're referencing externally-
> > defined terms, do we need to include the term
> > "Participant of a Group" in this document? This
> > seems close enough to "Participant" as defined
> > in 1.13 of the Bylaws that perhaps we can remove
> > the qualifying "of a Group" so they're equivalent?
> > Or is there a subtle difference I'm missing?
> >
> > Let me know what you suggest.
> >
> > Thanks again,
> > Trent
> >
> >
> > Roger Martin wrote:
> > > I have spent some time reviewing the "Groups Email Discussion List
> > > Policy" draft and have rewritten it in what I believe to be an
> > easier
> > > to understand and more comprehensive format.
> > >
> > > I have attached my draft which is based on the following
> > comments and
> > > rationale:
> > >
> > > 1. The Policy needs to address both (1) Joining a Group as a
> > > Participant and (2) Subscribing to a List as a Follower.
> > In the
> > > current draft these two concepts were intertwined and
> > seemed to
> > > be fairly confusing. I have attempted to split these two
> > > concepts out into separate sections to the extent possible.
> > >
> > > 2. The introduction of the term "Contributor" is not needed
> since
> > > "Participant", which is already defined in the Bylaws, is
> > > sufficient. I have deleted usage of "Contributor". If we
> > wish
> > > to differentiate between Participants who do and do not
> > actually
> > > contribute postings to the Group List, then the term may be
> > > useful, but personally I do not believe we should be
> > encouraging
> > > the concept of being a "passive" participant in a Group by
> not
> > > contributing anything.
> > >
> > > 3. I propose that all Participants in a Group be automatically
> > > Subscribed to the Group List. If a Member has additional
> > > representatives who join a Group then they may need to
> > > Subscribe, but in my opinion the roster of Participants in a
> > > Group should automatically be included on the Group List.
> > > Likewise for the BoT and LC lists, those holding a seat on
> > > either body should be automatically subscribed to both Lists.
> > >
> > > I have made other changes to the text as I rearranged it, but I did
> > > not intentionally change the meaning of the existing text except as
> > > outlined above.
> > >
> > > I apologize that I do not have the document properly formatted,
> > but I
> > > have run out of time and will be in an offsite meeting all day
> > > tomorrow. As noted in an earlier email, I do not have edit
> > permission
> > > on the online version of the document. I am including it as a
> > PDF and
> > > MSWORD file.
> > >
> > > I am sending it in its current state for consideration and
> > discussion
> > > as appropriate.
> > >
> > > ...rogerM
> > >
> > >
> > >
> > > Roger Martin wrote:
> > >> Since I do not have "edit" privileges to the "Groups Email
> > Discussion
> > >> List Policy" and because I feel that these issues should be
> > discussed
> > >> by the entire list, I was going to posting my recommended changes
> > >> (and rationale) to the LC and BoT lists in an email.
> > >>
> > >> However, after spending some time on rewriting the policy, I have
> > >> decided to draft a new version.
> > >>
> > >> One of the primary difficulties is that while the title of this
> > draft
> > >> policy is "Groups Email Discussion List Policy", it actually also
> > >> includes, and to some degree confuses, the policy about joining
> > a WG
> > >> or DG.
> > >>
> > >> As a result, I am going to propose restructuring it and renaming
> it
> > >> to be "Policy for Joining Groups and Group Mailing Lists".
> > >>
> > >> I will post it for consideration as soon as I have completed the
> > >> redrafting of the document.
> > >>
> > >> ....rogerM
> > >>
> > >>
> > >>
> > >> /--
> > >> ******************************************
> > >> Roger Martin, Director of Standards
> > >> AOL
> > >> 22260 Pacific Blvd 41A:A03
> > >> Dulles, VA 20166
> > >> email: roger.martin at corp.aol.com <mailto:
> roger.martin at corp.aol.com>
> > >> AIM: rjmartin99
> > >> phone: 703-265-6203
> > >> mobile: 703-389-1547
> > >> *******************************************/
> > >
> >
> ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > LC mailing list
> > > LC at kantarainitiative.org <mailto:LC at kantarainitiative.org>
> > >
> >
> http://kantarainitiative.org/mailman/listinfo/lc_kantarainitiative.org
> > >
> >
> > --
> > J. Trent Adams
> > =jtrentadams
> >
> > Outreach Specialist, Trust & Identity
> > Internet Society
> > http://www.isoc.org
> >
> > e) adams at isoc.org <mailto:adams at isoc.org>
> > o) 703-439-2149
> >
> >
> >
> > _______________________________________________
> > Trustees mailing list
> > Trustees at kantarainitiative.org <mailto:
> Trustees at kantarainitiative.org>
> >
> http://kantarainitiative.org/mailman/listinfo/trustees_kantarainitiative.org
> >
> >
> >
> >
> > --
> > Joni Brennan
> > IEEE-ISTO
> > Liberty Alliance Project
> > Director of Operations
> > voice:+1 732-226-4223
> > email: joni @ projectliberty.org <http://projectliberty.org>
> > email: joni @ ieee-isto.org <http://ieee-isto.org>
> >
> >
> >
> >
>
> --
> J. Trent Adams
> =jtrentadams
>
> Outreach Specialist, Trust & Identity
> Internet Society
> http://www.isoc.org
>
> e) adams at isoc.org
> o) 703-439-2149
>
>
>
--
Joni Brennan
IEEE-ISTO
Liberty Alliance Project
Director of Operations
voice:+1 732-226-4223
email: joni @ projectliberty.org
email: joni @ ieee-isto.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kantarainitiative.org/pipermail/lc_kantarainitiative.org/attachments/20090630/8467a9b9/attachment.html>
More information about the LC
mailing list