IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Helping the mentoring project with making matches

Alissa Cooper <alissa@cooperw.in> Thu, 13 December 2018 00:01 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C54130F6A for <tools-development@ietfa.amsl.com>; Wed, 12 Dec 2018 16:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=I7cDKjTL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QkVG030a
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mELjgSQ7nF_r for <tools-development@ietfa.amsl.com>; Wed, 12 Dec 2018 16:01:12 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81E8A130F58 for <tools-development@ietf.org>; Wed, 12 Dec 2018 16:01:12 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 6600A11DA; Wed, 12 Dec 2018 19:01:11 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 12 Dec 2018 19:01:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=2 2vswSsYN6JuQLPrk14/IMf1bO0Kgkqb9qUevc/FL2Q=; b=I7cDKjTLcWGhaeTc6 N71QJe+p/IRKqC2QgnRCtQAq4NjPmKQ9L7wr6rYZRcGgRyUJ77Lz5kPYn2US8W70 aw0c5gFL6+DqSe5Ez1JZDuGveyV2EsEsumHHNbwq6Y1wDzuktnQdFbzdZ3+qS8LZ ODtwAVvW1V5LCjtoeP26+87RuD4V0IXt6R0uA/f14rDhX/yyn5dRcp9Q6XdXfbhF 4/uio58pWtyPoEARxHHFvFIvEADVqWzPzSI0fwUXpP9cqnakAd02MnaLo4S186Lb GBnt7/LQXFoTpx9xjPcedVZLqkUI/E6AzzzFXNyG09zgt8QY2c742lCuEqzqobQr QFHvw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=22vswSsYN6JuQLPrk14/IMf1bO0Kgkqb9qUevc/FL 2Q=; b=QkVG030av7JnXZkm6SJuMRM4bHT1JBypGd/ZqDTdjJi9aDy3raVfkacpr GJvrnZ3bjB7liKpgl8IQ5uYbjERZHgjwTx+rv6cR5DpshBK3JY0+6tDje6kzbSJj RoCcN4zdE/UiQHRuVRI8TPZPrgdoEtK/9P4PoEWf8jn3TqnGOfAo4PEANnEbnPTK D2fL53a5d4zyOe0B8Erh+68xuzgiJZuGclwwavlCHiWal7uZ7cvTs1qOl6OXuBE+ xvnW3RpGa9FpBF4ZcR2Ca+QqZfL9TeMgucsNknNZLenJ0Z/4fKbtunaYXQk8cido RBbQqwBASM2UmMLSEG3gOuO7aRhqg==
X-ME-Sender: <xms:RqERXEUn4Gg2W3oa3JvKtjdxIsaTrW3UQ8dtjFgJ8HbuAmCRxLXUEg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudehuddgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjff fgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceo rghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrgh enucfkphepudejfedrfeekrdduudejrdekjeenucfrrghrrghmpehmrghilhhfrhhomhep rghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:RqERXCfxe9YQHNRc-99zu4a0k7csH-2Ld2GHmIKWiqb0QdXdzBZwNA> <xmx:RqERXBb_4v-iZ0-4nVZbzBY_F96LjMKZxnvfuw7PTzzohlz5E90XyA> <xmx:RqERXG7ohkCxrmplkjtXEUTEvEMpuBnRTHBBgXj_kB3TbXcswaUq_g> <xmx:RqERXPcJyvVyBpEtMn0V4ZcuwkNMf4ZO9yfH3sHDWWKszGFIU4qmDg> <xmx:RqERXJy7KXBxpvsEW9ndSi9421fuzR7EzuimBcq8JohLgxJEW06yCQ> <xmx:R6ERXMrapA-pIxjCtSZ_jE_MPNozLkqQ8awAkMA8Bcg3YxfvPS3ONQ>
Received: from rtp-vpn5-219.cisco.com (unknown [173.38.117.87]) by mail.messagingengine.com (Postfix) with ESMTPA id 22B55E40A1; Wed, 12 Dec 2018 19:01:10 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <8c503fa7-7ad7-2c60-6e42-34a782fa74a9@nostrum.com>
Date: Wed, 12 Dec 2018 16:01:08 -0800
Cc: IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA7B37CE-03EE-4D9C-9B77-1D1287A6AAD8@cooperw.in>
References: <8c503fa7-7ad7-2c60-6e42-34a782fa74a9@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/GBIilZVLagcJJ4Bu4_xCU4y6KrI>
Subject: Re: [TOOLS-DEVELOPMENT] Helping the mentoring project with making matches
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2018 00:01:14 -0000

Hi Robert,

> On Dec 12, 2018, at 2:31 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> I had a conversation today with Wes Hardaker to go over what the mentoring team is looking for to help with matching guides to participants.
> 
> The minimal set of information is simpler than what's in ticket 2622.

Could you elaborate on what that minimal set is?

Also, given the subject line, is functionality to actually make the matches part of the minimal set?

Alissa

> 
> My gut reaction is that a simple standalone django application would work (and could be constructed keeping gdpr compliance in mind), and could be built with volunteer effort. If we were to create such a thing, do you think there would be any issues with finding a place to host it under ietf.org?
> 
> fwiw - I continue to think that this particular bit of survey-like behavior shouldn't be bound to the registration system. I can see where adding the ability to add meeting-specific survey questions could be useful though.
> 
> RjS
> 
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development

v2.23.0 | Report a Bug | By Email