cloudstack-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: Typical process for getting approval for events/sponsorship
Date Tue, 09 Apr 2013 23:21:16 GMT

I guess the source of my confusion here is what "PMC approval" actually
means, in practice. My knee-jerk reaction was that private@ should be CCed
or something. But I guess, as a project, we are free to say that we're
going to be doing event/sponsership proposals on marketing@ and they can
pass by lazy consensus there. And if you're a PMC member and you want input
into that, then you had better subscribe to the marketing@ list. Does that
sound about right? If so, I expect we'll want to at least write that down

I also expect that we should add a step to the event/sponsorship approval
process that includes *notifying* ConCom, but makes it explicit that this
isn't an approval step. Is the preferred address for
that? And would you prefer it as a CC on the original proposal, or as a
notification once the proposal passes?


On 9 April 2013 23:56, Ross Gardler <> wrote:

> Hi Noah,
> As with so many things around here it's all a little ill-defined. My
> reading of the tea leaves would say...
> - Since you are seeking permission to spend third party cash supporting an
> ASF project, and are not using foundation level brands to further a
> companies interests beyond a specific project there is no need to seek
> approval from ConCom
> - You do need approval from the project PMC to use project branding at
> these events. It is up to the PMC to decide how that approval is sought. I
> note that your wiki page at [1] has some pretty good guidelines for when
> such approval is needed (note my statement above means you can relax
> the one about event sponsorship, assuming nobody here disagrees with me).
> - As for how to get PMC approval I would, again, suggest this is up to the
> PMCs. I'm always in favour of using lazy consensus as much as possible. So
> if your PMC were to agree with my view then a mail to the designated list
> (sometimes people want to keep financial information private) plus a
> minimum of 72 hours for objections to be raised would be sufficient. Such a
> policy can always be revisited if people start to abuse it.
> Originally ConCom approval was required for all events. However, we have no
> switched to a model of lazy consensus on the use of project brands since we
> were failing to give a timely response in some cases. Where ConCom should
> be involved is if you are using foundation level brands.
> It's also good practice (if not required) to notify ConCom of events your
> PMC has approved since we might be able to help get the word out and/or
> support your efforts in other ways.
> [ASIDE: See you at LinuxTag in May]
> Ross
> [1]
> On 9 April 2013 23:32, Noah Slater <> wrote:
> > (Note the mixing of public and private lists.)
> >
> > ConCom folks,
> >
> > Please see this thread:
> >
> >     Events Approval
> >
> >
> > The first email should be enough. No need to read it all.
> >
> > So, what I'm wondering is: what is the typical process for getting
> > approval for events or event sponsorship like this?
> >
> > Does ConCom need to be notified every time? Or is there a threshold? So,
> > for example, if you're just doing a small meet-up, then there's no need.
> >
> > Also, I understand that project PMCs typically need to approve events,
> > sponsorship, and branding proposals. Do you know how this is usually
> done?
> > Would an a proposal like that be made to the dev@ list? Is that
> > sufficient to demonstrate PMC approval? Or are these requests usually
> CCed
> > to private@ also? Note in this instance, the request as made to
> marketing@,
> > which is a public list, but was split off from dev@ for convenience.
> >
> > Thanks!
> >
> > --
> > NS
> >
> --
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message