couchdb-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Kowalski <...@kowalski.gd>
Subject Re: [NOTICE] CouchDB logo process & decision
Date Mon, 30 Mar 2015 17:54:21 GMT
I asked Infra for such an app and we got a an instance running for us :)

On Sun, Mar 29, 2015 at 4:27 PM, Noah Slater <nslater@apache.org> wrote:

> Okay, last email for now. Been chatting to Robert on IRC about how this
> would work. Looks like there are multiple vote types. Guess we'd pick the
> one that makes the most sense for choosing a new logo. (Note, this is the
> tool we use for picking new Board members, new project Chairs, and so on.)
> Also, there is a hosted version we can use internally.
>
> On Sun, 29 Mar 2015 at 16:23 Noah Slater <nslater@apache.org> wrote:
>
> > Oops, meant to link: http://steve.apache.org/
> >
> > On Sun, 29 Mar 2015 at 16:08 Noah Slater <nslater@apache.org> wrote:
> >
> >> Few days late to this, and I don't want to muddy the waters, especially
> >> after the work to clear them was done by "set of people who are not me",
> >> but... Apache has this cool Single Transferable Vote (STV) tool that we
> >> could use for Step 2 of your plan there.
> >>
> >> Basically, it works like this: we load all of the options into the
> system
> >> once we're ready to vote, and then we send out a vote email to everyone
> who
> >> wishes to vote. Those people then log in, and arrange the logos in the
> >> order that they prefer them. Once that's over, the system uses the STV
> algo
> >> to give us an ordered list of most prefered logos.
> >>
> >> I'm not sure if this would limit the vote to just committers or not. But
> >> if this is something we think could work for this, we can check that out
> >> and see what's involved in getting this set up for us.
> >>
> >> On Tue, 24 Mar 2015 at 03:22 Johs Ensby <johs@b2w.com> wrote:
> >>
> >>> Joan,
> >>> corrected my post on https://www.linkedin.com/groups?home=&gid=4547164
> <
> >>> https://www.linkedin.com/groups?home=&gid=4547164> accordingly
> >>> johs
> >>>
> >>> > On 24 Mar 2015, at 03:12, Joan Touzet <wohali@apache.org> wrote:
> >>> >
> >>> > Thanks, Johs. I proposed this approach during the weekly IRC meeting
> >>> > last week, and the PMC members present agreed. We reviewed the
> >>> discussion
> >>> > on the PMC mailing list and Robert took the great action of writing
> >>> > it up and formalising it for this list.
> >>> >
> >>> > Teamwork!
> >>> >
> >>> > -Joan
> >>> >
> >>> > ----- Original Message -----
> >>> > From: "Johs Ensby" <johs@b2w.com>
> >>> > To: marketing@couchdb.apache.org
> >>> > Sent: Monday, March 23, 2015 7:54:48 PM
> >>> > Subject: Re: [NOTICE] CouchDB logo process & decision
> >>> >
> >>> > Community is fantastic, especially with a healthy dose of leadership
> >>> > Like this:)
> >>> > johs
> >>> >
> >>> >> On 24 Mar 2015, at 00:20, Robert Kowalski <
> robertkowalski@apache.org>
> >>> wrote:
> >>> >>
> >>> >> Hi everyone,
> >>> >>
> >>> >> I would like to give you an update regarding the process for the
new
> >>> >> logo design. Sorry that it took so long and for the confusion,
but
> we
> >>> >> finally found a way to decide on the logo and move forward regarding
> >>> >> this topic. The process will have three steps:
> >>> >>
> >>> >>
> >>> >> Step 1 - You can still submit proposals and we will also propose
the
> >>> >> old CouchDB logo as a possible candidate until April 5
> >>> >>
> >>> >>
> >>> >> Step 2 - We will then run a public vote for all committers on this
> >>> >> mailing list (marketing@couchdb.apache.org)  (see “Non-technical
> >>> >> decision” in our bylaws [1]) by April 20. This vote will inform
the
> >>> >> decision made in Step 3.
> >>> >>
> >>> >>
> >>> >> Step 3 - The PMC will vote on a final decision by May 18, which
will
> >>> >> take the public vote as significant input. The PMC can decide to
go
> >>> >> with the results of the public vote, or make its own choice.
> >>> >>
> >>> >>
> >>> >> [1] http://couchdb.apache.org/bylaws.html#types
> >>> >
> >>>
> >>>
>

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