From nobody Sun Mar 1 20:08:08 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37BDF1A0056 for ; Sun, 1 Mar 2015 20:08:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.291 X-Spam-Level: * X-Spam-Status: No, score=1.291 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 Ki1mix31VMUq for ; Sun, 1 Mar 2015 20:08:00 -0800 (PST) Received: from nm5-vm0.bullet.mail.bf1.yahoo.com (nm5-vm0.bullet.mail.bf1.yahoo.com [98.139.213.150]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F8FE1A0037 for ; Sun, 1 Mar 2015 20:07:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1425269278; bh=/bxER8BC8NT+Q+TAoZg4JhoFkOwYHb5bi6jBYARptV8=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=GxBZt4NvF0ZteK18F53LINdsvaVY7fTqPP3q9jwqEyamoz1EZmZRrKyoFRpCBlwNSbDHypZwGppe0L38jtv5kIbTC7r1JNWbhiw444J0RGMLPz6uxtvPYH8OBciiHTgNajlLXpp5+s3tSIXHiJB6kMvMU2PbCxxBVyTKSaL+y4YWJI011kKGG9cWuwRUl9eEKzoFeUBRIvVydZ4tlWwDlLV+sgiisc+EPhDhzOOfIUE8XHLt1A8STwvyUcFWNRu53LG65yZS702tT3W4hSGMLtnmJIruJ3SGyr9vmdM4b9AOi0IHScTS77UhnS2AO2OW+zwH8jg4b1QCOMDjyWY1qQ== Received: from [66.196.81.173] by nm5.bullet.mail.bf1.yahoo.com with NNFMP; 02 Mar 2015 04:07:58 -0000 Received: from [98.139.212.223] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 02 Mar 2015 04:07:58 -0000 Received: from [127.0.0.1] by omp1032.mail.bf1.yahoo.com with NNFMP; 02 Mar 2015 04:07:58 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 332498.89951.bm@omp1032.mail.bf1.yahoo.com X-YMail-OSG: At958.sVM1m5gFSuijzpJzdVgiqMwCjNvJE6ZwcOdxjIILw5tk4miPX51lqQvVt AsI4EQUQsGN.mi4nmQLn6PdgEY3Xds10lcnySRsuiFJqhgDcpBGu.lEmZfsCIWakBJNs6dcuf1SR IFsyL2HSloj_2fU11kvlgIR75kUHCxRV5O9KmyFFgmFJzhY_x2mR9kNsDgkhCd3i_DGjHOjushsR IhUn4.wKlgy17E52L3E_Exf1cL50n9xqxC1ea6RQkL3kHm6AUQ5kFNLgOV050ZEOAx_8fKHsdgHu fjfYvDOYnTy6uw3anRDY_3GoQcaE.IyQ3A97aHV1I2fAB4DHGUvtSxmQz8n_NUtRE98q.fYHjvRw DVjyPIIeeGYi3JSLsapKROjgCJjpfQpQ46M7MXh0g_3v8vYcPVKyrsUR2xZZ4z.hQC76vN8by3ZJ J8BInX6dPmTy0vEpwUnuMr.LJmjyU0TTeSCVWXNW93cN2uhCDdHc.6LEYbMqo2Bgog69JwWrL7_. k9nH.hb2KwWVeACpBKoVXzyRxEcKi.j_kOud8QFCoo5xK6Q_6jfQGMtWTtPsVYDuzrs38sNRimn1 8xnYcM_bA_nnE5JI9a6_JGslLupX41dnatWNlmM8QQJkv_Jb2GyBpkLEc86_M2vFV0Fyn.RictTw Vlex8f4s6UDLJqtvZDuigzRpEiKRIqQ5Ho7xL5S9LUWjZm9nZ2RI0596oN.bQXKboHVjVZSpR2kN n8dkMPL66SPq1BSjxbGmsYMil2.4- Received: by 66.196.80.121; Mon, 02 Mar 2015 04:07:57 +0000 Date: Mon, 2 Mar 2015 04:07:56 +0000 (UTC) From: Kristin Burgh To: "codematch-develop@ietf.org" Message-ID: <1070000593.1289566.1425269277230.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1289565_495807537.1425269277182" Archived-At: Subject: Re: [Codematch-develop] Codematch-develop Digest, Vol 8, Issue 23 X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Kristin Burgh List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 04:08:07 -0000 ------=_Part_1289565_495807537.1425269277182 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable All -=C2=A0 I believe our updated Card Sort is ready to go out. Please let me know if you have any questions regarding the attached - I wou= ld like to formally launch this tomorrow (Monday - March 2), so please have= any comments, suggestions or updates in to me ASAP. https://conceptcodify.com/studies/AJDvCQAeNrm9nOO9rwNjsQDc/via/MlU1pQ4sRNef= S1iIfsYi4l3a/ In terms of distribution, I believe we had discussed using our respective s= ocial networks (e.g. - LinkedIn, Facebook, etc.) to capture survey results. I'd like to close this survey on Tuesday, March 10 and report the results d= uring the weekly meeting the following day. =C2=A0I hope that a week and a = half will be enough time to allow the developers to make any necessary chan= ges prior to Dallas. Kind Regards,=C2=A0=C2=A0Kristin=C2=A0=20 From: "codematch-develop-request@ietf.org" To: codematch-develop@ietf.org=20 Sent: Wednesday, February 25, 2015 11:06 AM Subject: Codematch-develop Digest, Vol 8, Issue 23 =20 ----- Forwarded Message ----- Send Codematch-develop mailing list submissions to =C2=A0=C2=A0=C2=A0 codematch-develop@ietf.org To subscribe or unsubscribe via the World Wide Web, visit =C2=A0=C2=A0=C2=A0 https://www.ietf.org/mailman/listinfo/codematch-develop or, via email, send a message with subject or body 'help' to =C2=A0=C2=A0=C2=A0 codematch-develop-request@ietf.org You can reach the person managing the list at =C2=A0=C2=A0=C2=A0 codematch-develop-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Codematch-develop digest..." Today's Topics: =C2=A0 1. Re: CodeMatch data model v3 (Kathleen Moriarty) =C2=A0 2. Re: Codematch-develop Digest, Vol 8, Issue 22 (Kristin Burgh) Hi Lisandro, I reached out to Pete Resnick, one of the Apps directors to see what he tho= ught. He does agree that something is missing. I think we can handle this in a few ways.=C2=A0 We need to be able to diffe= rentiate when code is requested from when a link is being made as the infor= mation on each will be different. =C2=A0 The data model would need a few elements to be optional, like mentor, resou= rces (estimated level of effort for coding).=C2=A0 You usually see this whe= n there is accompanying UML. Pete suggested a different name for CodeRequest, maybe MatchRequest with an= element for CodeRequest?=C2=A0 If we keep it at CodeRequest, I think minim= ally an attribute to designate if code is actually requested would be neces= sary - or we change this to MatchRequest with an attribute called CodeReque= st as a boolean (yes/no - for our team members that are not data model savv= y). Just some thoughts so the data model would be clear... On Tue, Feb 24, 2015 at 4:15 PM, Moriarty, Kathleen wrote: Hi Lisandro, Sent from my iPhone On Feb 24, 2015, at 5:41 AM, "Lisandro Zambenedetti Granville" wrote: If thinks are still not clear, I can try to provide examples. I think an explanation along with the data model will be necessary if no li= ne is included to show the code request isn't needed to link a project to a= specification.=C2=A0 That and examples will help developers as we proceed. Hello Kathleen Just to clarify: a CodeRequest is still needed to link projects to a specif= ication. The data model is not missing a link between projects and specific= ations; projects are are linked to specifications only through a CodeReques= t. What we have discussed so far is that the mentor field in the CodeReques= t is only meaningful for active projects, since already finished projects d= on=E2=80=99t need a mentor anymore. Let's chat about this tomorrow as I still don't see why a direct connection= between a project and specification can't be made.=C2=A0 Maybe it's to hav= e a grouping, but I'd like to talk through this a bit.=C2=A0 If you have an= example for tomorrow, that may help. Thank you,Kathleen Best regards, Lisandro Sent from my iPhone On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" wrote: Hello Kathleen I=E2=80=99m not an expert on data models, so I may be wrong. Today, CodeMat= ch is a relationship between Project and CodeRequest. I believe it is not p= ossible to have another relationship between Project and Specification name= d CodeMatch too. But let me ask you if you agree with the suggestion of =E2= =80=9Cfixing=E2=80=9D this issue by saying that =E2=80=9Ca Mentor is the pe= rson responsible for helping in the development of active projects=E2=80=9D= , implying that mentors have no role in already finished projects? In that = way, we don=E2=80=99t need to change the data model. Not that we could not = change it, but I believe keeping it simple is important. Best regards, Lisandro Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen escreveu: Hi, Sent from my iPhone On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" w= rote: Hi Kathleen,=C2=A0 To me, a CodeRequest is an explicit call for FUTURE developments. If someon= e is questing code, that=E2=80=99s because (additional?) code is required. = To help in the development of new code throughout new projects, mentors see= m to be mandatory. I agree with Lisandro's reasoning. If there's a code-match, it's because so= meone did a code request. Someone needed that code and he will get the appr= opriate "coding" help if the student has some support to do that work. Good point. We can have a different instance for those cases were there is no request, = thereby no need to provide a shepherd. They could be just "code opportunity= " and there's no commitment from anyone for those code-matches. In looking at the data model again, how about having the CodeMatch either b= e a fulfilled CodeRequest mapping a project to a specification or simply th= e connection between a project and specification.=C2=A0 This let's us keep = the terms and model simple which may be easier for users as they will have = less to understand in terms of our terminology.=C2=A0 Also keeping the data= model simpler should help reduce coding efforts. =C2=A0 However, if you want to advertise projects that already finished, mentors m= ake not sense indeed. But consider the following situation: there is a Code= Request for an specific protocol. That CodeRequest already finds previously= finished projects but still requires further code. In that case, the previ= ous projects don=E2=80=99t need a mentor, of course, but the new projects d= o. But because mentors are associated with CodeRequest (and not with projec= t), once we define a mentor to help in the new projects that mentor will be= also linked with the old projects too. In summary, old projects will alway= s have a mentor once new projects are required. If the link is to the same draft, but I suspect this will happen more with = draft revisions or drafts that extend base specifications. The whole issue resides in the fact that mentors are associated with CodeRe= quest. Previously, mentors were associated with individual projects (at tha= t point we were referring projects to as CodeMatches, before the last chang= e in the model). Here, we have some options: Yes, you are correct and I think my updated suggestion fixes this, but let = me know if I missed anything. 1) Assume that dummy mentors can be associated with CodeRequests that exist= only to advertise already finished projects, but we need to live with the = idea that once additional code is needed for those CodeRequests, a real men= tor will be assigned, and the finished project will inherit that new real m= entor. 2) Rollback the model back to associate mentors with projects, indicating t= hat mentors are optional. However, we may be imposing an administrative bur= den here. A third option could be to have active "code-requests" with mentors and "co= de-opportunities" (or a better name) for finished projects, other =C2=A0RFC= s, etc. with no mentor.=C2=A0 Or just to have two options for CodeMatches - with or without a CodeRequest= . Thanks!Kathleen=C2=A0 Christian Another option is checking how we tell the story. The question may be solve= d if we say that =E2=80=9Cmentors exist to help in the development of new p= rojects=E2=80=9D, implying that already finished projects has now associati= on with current mentors. Too simplistic? Best regards, Lisandro Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty escreveu: Lisandro, Thank you for your time and effort developing the data model with the team!= =C2=A0 This looks great from what we discussed.=C2=A0 From additional feedb= ack received from the IESG, the point was made that you may not always have= a shepherd.=C2=A0 If we want this to also advertise existing implementatio= ns (open source or proprietary) of existing RFCs, there should be flexibili= ty to demonstrate links between a CodeRequest (in this case an RFC) and a p= roject without having a mentor.=C2=A0 You would still have a coder or the p= roject owner that creates the link and it would be possible for others to c= onnect their project to that same published IETF or IRTF document. In that case, would the coder then also be connected to the CodeRequest so = there are multiple ways to make the connections? We would need search capabilities for coders looking for projects so they m= ight only see ones that have a mentor and I'm sure they would want to be ab= le to restrict their view to the projects they have time to code (1 FTE for= x weeks or months, etc.). Any other comments? Thank you,Kathleen On Sat, Feb 7, 2015 at 3:24 AM, Lisandro Zambenedetti Granville wrote: Dear all After one of our last meetings, a new data model (v3) for CodeMatch has bee= n defined. Please, find below the new version of such a data model. We trie= d to incorporate the comments received in the list as well as the suggestio= ns mentioned during the last meetings. Terms in this version are also align= ed with the list of terms previously shared by Kathleen in the mailing list= . Any feedback is welcomed. Best regards, Lisandro _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop --=20 Best regards,Kathleen _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop --=20 Best regards,Kathleen --=20 Best regards,Kathleen Good Morning/Afternoon/Evening Everyone -=C2=A0 I just wanted to let everyone know that I'll be sending out an updated vers= ion of the card-sort survey over this coming weekend. =C2=A0The aim is to b= e able to have as much feedback from a variety of different users as we can= get to help create the best possible prototypes in time for Dallas. If you have any questions, please feel free to contact me either via this e= mail thread or directly via "kmburgh@yahoo.com". Also - my apologies to you all - but I'll be about 30 minutes late to today= 's call/webex due to a scheduling conflict. Kind Regards,=C2=A0 Kristin=C2=A0 From: "codematch-develop-request@ietf.org" To: codematch-develop@ietf.org=20 Sent: Wednesday, February 25, 2015 9:30 AM Subject: Codematch-develop Digest, Vol 8, Issue 22 =20 ----- Forwarded Message ----- Send Codematch-develop mailing list submissions to =C2=A0=C2=A0=C2=A0 codematch-develop@ietf.org To subscribe or unsubscribe via the World Wide Web, visit =C2=A0=C2=A0=C2=A0 https://www.ietf.org/mailman/listinfo/codematch-develop or, via email, send a message with subject or body 'help' to =C2=A0=C2=A0=C2=A0 codematch-develop-request@ietf.org You can reach the person managing the list at =C2=A0=C2=A0=C2=A0 codematch-develop-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Codematch-develop digest..." Today's Topics: =C2=A0 1. Re: CodeMatch data model v3 (Kathleen Moriarty) Dear Wanderson, Yes, I am sure we will be able to help you and other volunteer developers f= igure out how to get started and to work as a team without having to attend= Dallas. Thank you. On Tue, Feb 24, 2015 at 7:11 PM, Wanderson Paim de Jesus wrote: Dear Kathleen, I'm afraid saying, but I had not planned attending the IETF in Dallas and I= 'm not aware about Code Sprint. If it is possible, after the Code Sprint such other collaborators could sen= d me the tools and manuals about the Codetracker. Best regards, De: "Kathleen Moriarty" Para: "Wanderson Paim de Jesus" Cc: "Christian O'Flaherty" , "Kathleen Moriarty" , codematch-develop@ietf.org, "Lisandro Zambenedetti G= ranville" Enviadas: Segunda-feira, 23 de fevereiro de 2015 11:46:59 Assunto: Re: [Codematch-develop] CodeMatch data model v3 Wanderson, We are glad to have your assistance! Dave Waltermire has also volunteered to help code and we may have 1-2 other= volunteers soon.=C2=A0 If anyone is attending the IETF in Dallas and will = be able to help us code, it may be a good idea to go to the Code Sprint Sat= urday before the meeting as you'll get the tools to install and learn more = about the datatracker.=C2=A0 Please let me know if you need more informatio= n on the Code Sprint. Thank you,Kathleen On Mon, Feb 23, 2015 at 7:14 AM, Wanderson Paim de Jesus wrote: Hi Kathleen, I find Codematch a good idea and hope being able to contribute with its suc= cess. Christian seems to be interest in coding too. Given that I'm not familiar w= ith datatracker, his support would be honestly welcome. Best regards, Wanderson De: "Kathleen Moriarty" Para: "Lisandro Zambenedetti Granville" Cc: "Christian O'Flaherty" , "Kathleen Moriarty" , codematch-develop@ietf.org, "Wanderson Paim de Jesus= " Enviadas: Sexta-feira, 20 de fevereiro de 2015 13:23:51 Assunto: Re: [Codematch-develop] CodeMatch data model v3 On Fri, Feb 20, 2015 at 6:23 AM, Lisandro Zambenedetti Granville wrote: Dear all Wanderson Paim (cc=E2=80=99ed in this message), who develop the prototype a= vailable at http://codematch.inf.ufrgs.br=C2=A0is also a volunteer to code = the CodeMatch backend. Excellent, it's great to have you on the team Wanderson!=C2=A0 Thank you fo= r volunteering! Best regards,Kathleen=C2=A0 Best regards, Lisandro Em 17/02/2015, =C3=A0(s) 15:19, Christian O'Flaherty e= screveu: I have a couple more volunteers for coding as well lined up.=C2=A0 There ma= y be more decisions to be made for that and prep for developers to get fami= liar with the datatracker and how it will be accessed. Although I never used datatracker as a coder I would like to be among the i= nitial volunteers for coding.=C2=A0 Christian=C2=A0 Thank you,Kathleen=C2=A0 Christian Thank you,Kathleen=C2=A0 Sent from my iPhone On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" wrote: Hello Kathleen I=E2=80=99m not an expert on data models, so I may be wrong. Today, CodeMat= ch is a relationship between Project and CodeRequest. I believe it is not p= ossible to have another relationship between Project and Specification name= d CodeMatch too. But let me ask you if you agree with the suggestion of =E2= =80=9Cfixing=E2=80=9D this issue by saying that =E2=80=9Ca Mentor is the pe= rson responsible for helping in the development of active projects=E2=80=9D= , implying that mentors have no role in already finished projects? In that = way, we don=E2=80=99t need to change the data model. Not that we could not = change it, but I believe keeping it simple is important. Best regards, Lisandro Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen escreveu: Hi, Sent from my iPhone On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" w= rote: Hi Kathleen,=C2=A0 To me, a CodeRequest is an explicit call for FUTURE developments. If someon= e is questing code, that=E2=80=99s because (additional?) code is required. = To help in the development of new code throughout new projects, mentors see= m to be mandatory. I agree with Lisandro's reasoning. If there's a code-match, it's because so= meone did a code request. Someone needed that code and he will get the appr= opriate "coding" help if the student has some support to do that work. Good point. We can have a different instance for those cases were there is no request, = thereby no need to provide a shepherd. They could be just "code opportunity= " and there's no commitment from anyone for those code-matches. In looking at the data model again, how about having the CodeMatch either b= e a fulfilled CodeRequest mapping a project to a specification or simply th= e connection between a project and specification.=C2=A0 This let's us keep = the terms and model simple which may be easier for users as they will have = less to understand in terms of our terminology.=C2=A0 Also keeping the data= model simpler should help reduce coding efforts. =C2=A0 However, if you want to advertise projects that already finished, mentors m= ake not sense indeed. But consider the following situation: there is a Code= Request for an specific protocol. That CodeRequest already finds previously= finished projects but still requires further code. In that case, the previ= ous projects don=E2=80=99t need a mentor, of course, but the new projects d= o. But because mentors are associated with CodeRequest (and not with projec= t), once we define a mentor to help in the new projects that mentor will be= also linked with the old projects too. In summary, old projects will alway= s have a mentor once new projects are required. If the link is to the same draft, but I suspect this will happen more with = draft revisions or drafts that extend base specifications. The whole issue resides in the fact that mentors are associated with CodeRe= quest. Previously, mentors were associated with individual projects (at tha= t point we were referring projects to as CodeMatches, before the last chang= e in the model). Here, we have some options: Yes, you are correct and I think my updated suggestion fixes this, but let = me know if I missed anything. 1) Assume that dummy mentors can be associated with CodeRequests that exist= only to advertise already finished projects, but we need to live with the = idea that once additional code is needed for those CodeRequests, a real men= tor will be assigned, and the finished project will inherit that new real m= entor. 2) Rollback the model back to associate mentors with projects, indicating t= hat mentors are optional. However, we may be imposing an administrative bur= den here. A third option could be to have active "code-requests" with mentors and "co= de-opportunities" (or a better name) for finished projects, other =C2=A0RFC= s, etc. with no mentor.=C2=A0 Or just to have two options for CodeMatches - with or without a CodeRequest= . Thanks!Kathleen=C2=A0 Christian Another option is checking how we tell the story. The question may be solve= d if we say that =E2=80=9Cmentors exist to help in the development of new p= rojects=E2=80=9D, implying that already finished projects has now associati= on with current mentors. Too simplistic? Best regards, Lisandro Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty escreveu: Lisandro, Thank you for your time and effort developing the data model with the team!= =C2=A0 This looks great from what we discussed.=C2=A0 From additional feedb= ack received from the IESG, the point was made that you may not always have= a shepherd.=C2=A0 If we want this to also advertise existing implementatio= ns (open source or proprietary) of existing RFCs, there should be flexibili= ty to demonstrate links between a CodeRequest (in this case an RFC) and a p= roject without having a mentor.=C2=A0 You would still have a coder or the p= roject owner that creates the link and it would be possible for others to c= onnect their project to that same published IETF or IRTF document. In that case, would the coder then also be connected to the CodeRequest so = there are multiple ways to make the connections? We would need search capabilities for coders looking for projects so they m= ight only see ones that have a mentor and I'm sure they would want to be ab= le to restrict their view to the projects they have time to code (1 FTE for= x weeks or months, etc.). Any other comments? Thank you,Kathleen On Sat, Feb 7, 2015 at 3:24 AM, Lisandro Zambenedetti Granville wrote: Dear all After one of our last meetings, a new data model (v3) for CodeMatch has bee= n defined. Please, find below the new version of such a data model. We trie= d to incorporate the comments received in the list as well as the suggestio= ns mentioned during the last meetings. Terms in this version are also align= ed with the list of terms previously shared by Kathleen in the mailing list= . Any feedback is welcomed. Best regards, Lisandro _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop --=20 Best regards,Kathleen _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop --=20 Best regards,Kathleen --=20 Best regards,Kathleen --=20 Wanderson --=20 Best regards,Kathleen _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop =20 _______________________________________________ Codematch-develop mailing list Codematch-develop@ietf.org https://www.ietf.org/mailman/listinfo/codematch-develop ------=_Part_1289565_495807537.1425269277182 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
<= span>All - 

I believe our updated Card Sort is ready to go out.<= /span>

Please let me know if you have any questions regarding the attached -= I would like to formally launch this tomorrow (Monday - March 2), so pleas= e have any comments, suggestions or updates in to me ASAP.

=

In terms of distribution, I believe we ha= d discussed using our respective social networks (e.g. - LinkedIn, Facebook= , etc.) to capture survey results.

I'd like to close this survey on Tues= day, March 10 and report the results during the weekly meeting the followin= g day.  I hope that a week and a half will be enough time to allow the= developers to make any necessary changes prior to Dallas.

Kind Regards,=  
 
Kristin 

From: "codematch-develop-request@ietf.org" <co= dematch-develop-request@ietf.org>
To: codematch-develop@ietf.org
Sent: Wednesday, February 25, 2015 11:06 AM
<= span style=3D"font-weight:bold;">Subject: Codematch-develop Dige= st, Vol 8, Issue 23

----- Forwarded Message= -----

Send Codematch-develop mailing list submissions to
 &= nbsp;  codematch-develop@ietf.org

To subsc= ribe or unsubscribe via the World Wide Web, visit
    https://www.ietf.org/mailman/listinfo/codematch-de= velop
or, via email, send a message with subject or body 'help' to    codematch-develop-request@ietf.org

You can reach t= he person managing the list at
    codematch-develop-owner@ietf.org<= /a>

When replying, please edit your Subject line so it is more speci= fic
than "Re: Contents of Codematch-develop digest..."

Today's To= pics:

  1. Re: CodeMatch data model v3 (Kathleen Moriarty)
=   2. Re: Codematch-develop Digest, Vol 8, Issue 22 (Kristin Burgh)
Hi Lisandro,

I reached out to Pete Resnick, one of the Apps directors to see what he th= ought.

He does agree that something is missing.

I think we can handle this in a few ways.  We n= eed to be able to differentiate when code is requested from when a link is = being made as the information on each will be different.  
<= br>
The data model would need a few elements to be optional, like= mentor, resources (estimated level of effort for coding).  You usuall= y see this when there is accompanying UML.

Pete su= ggested a different name for CodeRequest, maybe MatchRequest with an elemen= t for CodeRequest?  If we keep it at CodeRequest, I think minimally an= attribute to designate if code is actually requested would be necessary - = or we change this to MatchRequest with an attribute called CodeRequest as a= boolean (yes/no - for our team members that are not data model savvy).

Just some thoughts so the data model would be clear..= .

On Tue, Feb 24, 2015 at 4:15 PM, Moriarty, Kathleen <= span dir=3D"ltr"><kath= leen.moriarty@emc.com> wrote:
Hi Lisandro,

Sent from my iPhone

On Feb 24, 2015, at 5:41 AM, "Lisandro Zambenedetti Granville" <granville@inf.ufrgs.br> wrote:=

If thinks are still not clear, I can try to provide examples.

I think an explanation along with the data model will be necessary if no li= ne is included to show the code request isn't needed to link a project to a= specification.  That and examples will help developers as we proceed.=

Hello Kathleen

Just to clarify: a CodeRequest is still needed to link projects to a s= pecification. The data model is not missing a link between projects and spe= cifications; projects are are linked to specifications only through a CodeR= equest. What we have discussed so far is that the mentor field in the CodeRequest is only meaningful for act= ive projects, since already finished projects don=E2=80=99t need a mentor a= nymore.

 Let's chat about this tomorrow as I still don't see why a direct connection= between a project and specification can't be made.  Maybe it's to hav= e a grouping, but I'd like to talk through this a bit.  If you have an= example for tomorrow, that may help.

Thank you,
Kathleen

Best regards,

Lisandro

Sent from my iPhone

On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" <granville@inf.ufrgs.br> wrote:=

Hello Kathleen

I=E2=80=99m not an expert on data models, so I may be wrong. Today, Co= deMatch is a relationship between Project and CodeRequest. I believe it is = not possible to have another relationship between Project and Specification= named CodeMatch too. But let me ask you if you agree with the suggestion of =E2=80=9Cfixing=E2=80=9D this = issue by saying that =E2=80=9Ca Mentor is the person responsible for helpin= g in the development of active projects=E2=80=9D, implying that mentors hav= e no role in already finished projects? In that way, we don=E2=80=99t need to change the data model. Not that we could not change it, but I believe k= eeping it simple is important.

Best regards,

Lisandro

Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen <kathleen.moriarty@emc.com> escrev= eu:

Hi,

Sent from my iPhone

On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" <oflaherty@isoc.org> wrote:

Hi Kathleen, 

To me, a CodeRequest is an explicit call for FUTURE developments. If s= omeone is questing code, that=E2=80=99s because (additional?) code is requi= red. To help in the development of new code throughout new projects, mentor= s seem to be mandatory.

I agree with Lisandro's reasoning. If there's a code-match, it's becau= se someone did a code request. Someone needed that code and he will get the= appropriate "coding" help if the student has some support to do that work.=

Good point.

We can have a different instance for those cases were there is no requ= est, thereby no need to provide a shepherd. They could be just "code opport= unity" and there's no commitment from anyone for those code-matches.

In looking at the data model again, how about having the CodeMatch either b= e a fulfilled CodeRequest mapping a project to a specification or simply th= e connection between a project and specification.  This let's us keep = the terms and model simple which may be easier for users as they will have less to understand in terms of our t= erminology.  Also keeping the data model simpler should help reduce co= ding efforts.

 

However, if you want to advertise projects that already finished, ment= ors make not sense indeed. But consider the following situation: there is a= CodeRequest for an specific protocol. That CodeRequest already finds previ= ously finished projects but still requires further code. In that case, the previous projects don= =E2=80=99t need a mentor, of course, but the new projects do. But because m= entors are associated with CodeRequest (and not with project), once we defi= ne a mentor to help in the new projects that mentor will be also linked with the old projects too. In summary, old proj= ects will always have a mentor once new projects are required.
If the link is to the same draft, but I suspect this will happen more with = draft revisions or drafts that extend base specifications.

The whole issue resides in the fact that mentors are associated with C= odeRequest. Previously, mentors were associated with individual projects (a= t that point we were referring projects to as CodeMatches, before the last = change in the model). Here, we have some options:

Yes, you are correct and I think my updated suggestion fixes this, but let = me know if I missed anything.

1) Assume that dummy mentors can be associated with CodeRequests that = exist only to advertise already finished projects, but we need to live with= the idea that once additional code is needed for those CodeRequests, a rea= l mentor will be assigned, and the finished project will inherit that new real mentor.

2) Rollback the model back to associate mentors with projects, indicat= ing that mentors are optional. However, we may be imposing an administrativ= e burden here.

A third option could be to have active "code-requests" with mentors an= d "code-opportunities" (or a better name) for finished projects, other &nbs= p;RFCs, etc. with no mentor. 
Or just to have two options for CodeMatches - with or without a CodeRequest= .

Thanks!
Kathleen 


Christian


Another option is checking how we tell the story. The question may be = solved if we say that =E2=80=9Cmentors exist to help in the development of = new projects=E2=80=9D, implying that already finished projects has now asso= ciation with current mentors. Too simplistic?

Best regards,

Lisandro

Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty <kathleen.moriarty.ietf@gmai= l.com> escreveu:

Lisandro,

Thank you for your time and effort developing the data model with the = team!  This looks great from what we discussed.  From additional = feedback received from the IESG, the point was made that you may not always= have a shepherd.  If we want this to also advertise existing implementations (open source or proprietary) of= existing RFCs, there should be flexibility to demonstrate links between a = CodeRequest (in this case an RFC) and a project without having a mentor.&nb= sp; You would still have a coder or the project owner that creates the link and it would be possible for others to= connect their project to that same published IETF or IRTF document.

In that case, would the coder then also be connected to the CodeReques= t so there are multiple ways to make the connections?

We would need search capabilities for coders looking for projects so t= hey might only see ones that have a mentor and I'm sure they would want to = be able to restrict their view to the projects they have time to code (1 FT= E for x weeks or months, etc.).

Any other comments?

Thank you,
Kathleen

On Sat, Feb 7, 2015 at 3:24 AM, Lis= andro Zambenedetti Granville <granville= @inf.ufrgs.br> wrote:
Dear all

After one of our last meetings, a new data model (v3) for CodeMatch ha= s been defined. Please, find below the new version of such a data model. We= tried to incorporate the comments received in the list as well as the sugg= estions mentioned during the last meetings. Terms in this version are also aligned with the list of= terms previously shared by Kathleen in the mailing list. Any feedback is w= elcomed.

Best regards,

Lisandro

<codematchv3-3.png>

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.= org
https://www.ietf.org/mailman/listinfo/codematch= -develop




--

Best regards,
Kathleen

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.= org
https://www.ietf.org/mailman/listinfo/codematch= -develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop= @ietf.org
https://www.ietf.org/mailman/listinfo/cod= ematch-develop
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.= org
https://www.ietf.org/mailman/listinfo/codematch= -develop





--

Best regards,
Kathleen





--

Best regards,
Kathleen

Good Morning/Afternoon/Evening Everyone - 

I just wanted to let everyone know that I'll be sending out an updated = version of the card-sort survey over this coming weekend.  The aim is = to be able to have as much feedback from a variety of different users as we= can get to help create the best possible prototypes in time for Dallas.

If you have any questions, please feel free to contact me either via th= is email thread or directly via "kmburgh@yahoo.com".

Also - my apologies to you all - but I'll be about 30 minutes late to toda= y's call/webex due to a scheduling conflict.

Kind Regards, 

Kris= tin
 


=
From:= "codematch-develop-request@ietf.org" <codematch-develop-request@ietf.or= g>
To: codematch-dev= elop@ietf.org
Sent: We= dnesday, February 25, 2015 9:30 AM
Subject: Codematch-develop Digest, Vol 8, Issue 22
 =

----- Forwarded Mess= age -----

Send Codematch-develop mailing list submissions to
&nbs= p;   codematc= h-develop@ietf.org

To subscribe or unsubscribe via the World Wid= e Web, visit
    https://www.= ietf.org/mailman/listinfo/codematch-develop
or, via email, send a me= ssage with subject or body 'help' to
    codematch-develop-reque= st@ietf.org

You can reach the person managing the list at
&nb= sp;   codematch-develop-owner@ietf.org

When replying, please edit= your Subject line so it is more specific
than "Re: Contents of Codematc= h-develop digest..."

Today's Topics:

  1. Re: CodeMatch= data model v3 (Kathleen Moriarty)
Dear Wanderson,

Yes, I am sure we will be able to = help you and other volunteer developers figure out how to get started and t= o work as a team without having to attend Dallas.

= Thank you.

On Tue, Feb 24, 2015 at 7:11 PM, Wanderson P= aim de Jesus <wanderson.jesus@rnp.br> wrote:
Dear Kathleen,=

I'm afraid saying,= but I had not planned attending the IETF in Dallas and I'm not aware about= Code Sprint.

If it is possible, after the Code Sprint such other collaborat= ors could send me the tools and manuals about the Codetracker.
=

Best regards,

De: "Kathleen Moriarty" <kathleen.moriarty= .ietf@gmail.com>
Para: "Wanderson Paim de Jesus" <wanderson.jesus@rnp.br>
Cc: "Christian O'Flaherty" <ofl= aherty@isoc.org>, "Kathleen Moriarty" <kathleen.moriarty@emc.com>, codematch-develop@ietf.org, "Lisand= ro Zambenedetti Granville" <= granville@inf.ufrgs.br>
Enviadas: Segunda-feira, 23 de fev= ereiro de 2015 11:46:59

Assunto: = Re: [Codematch-develop] CodeMatch data model v3

Wanderson,

We are glad to have your assistance!

Dave Waltermire has also volunteered to help code and we = may have 1-2 other volunteers soon.  If anyone is attending the IETF i= n Dallas and will be able to help us code, it may be a good idea to go to t= he Code Sprint Saturday before the meeting as you'll get the tools to insta= ll and learn more about the datatracker.  Please let me know if you ne= ed more information on the Code Sprint.

Thank you,=
Kathleen

=
On Mon, Feb 23, 2015 at 7:14 AM, Wa= nderson Paim de Jesus <wanderson.jesus@rnp.br> wrote:
Hi Kathleen,<= /span>

I find Codematch a good= idea and hope being able to contribute with its success.
=
Christian seems to be interest in coding= too. Given that I'm not familiar with datatracker, his support would be ho= nestly welcome.
Best re= gards,

Wanderson=

De: "Kathleen Moriarty" <kathleen.moriarty.ietf@= gmail.com>
Para: "Lisandro Zambenedetti Granville" <granville@inf.ufrgs.br>
= Cc: "Christian O'Flaherty" <o= flaherty@isoc.org>, "Kathleen Moriarty" <kathleen.moriarty@emc.com>, codematch-develop@ietf.org, "Wan= derson Paim de Jesus" <wande= rson.jesus@rnp.br>
Enviadas: Sexta-feira, 20 de fevereiro = de 2015 13:23:51
Assunto: Re: [Codematch-develop] CodeMatch data = model v3




On Fri, Feb 20, 201= 5 at 6:23 AM, Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>= wrote:
Dear all

Wanderson Paim (cc=E2=80=99ed= in this message), who develop the prototype available at http://codemat= ch.inf.ufrgs.br is also a volunteer to code the CodeMatch backend.=

Excellent, it's great to have = you on the team Wanderson!  Thank you for volunteering!

=
Best regards,
Kathleen 

Best regards,

Lisandro

<= blockquote>
Em 17/02/2015, =C3=A0(s) 15:19, Christian O'Flaherty <oflaherty@isoc.org> escreveu:



I have a couple more volunteers for coding as well lined up.  The= re may be more decisions to be made for that and prep for developers to get= familiar with the datatracker and how it will be accessed.

Although I never used datatracker as a coder I would like to be among the i= nitial volunteers for coding. 

Christian 


Thank you,
Kathleen 

Christian


Thank you,
Kathleen 

Sent from my iPhone

On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" <granville@inf.ufrgs.br> wrote:=

Hello Kathleen

I=E2=80=99m not an expert on data models, so I may be wrong. Today, Co= deMatch is a relationship between Project and CodeRequest. I believe it is = not possible to have another relationship between Project and Specification= named CodeMatch too. But let me ask you if you agree with the suggestion of =E2=80=9Cfixing=E2=80=9D this = issue by saying that =E2=80=9Ca Mentor is the person responsible for helpin= g in the development of active projects=E2=80=9D, implying that mentors hav= e no role in already finished projects? In that way, we don=E2=80=99t need to change the data model. Not that we could not change it, but I believe k= eeping it simple is important.

Best regards,

Lisandro

Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen <kathleen.moriarty@emc.com> escrev= eu:

Hi,

Sent from my iPhone

On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" <oflaherty@isoc.org> wrote:

Hi Kathleen, 

To me, a CodeRequest is an explicit call for FUTURE developments. If s= omeone is questing code, that=E2=80=99s because (additional?) code is requi= red. To help in the development of new code throughout new projects, mentor= s seem to be mandatory.

I agree with Lisandro's reasoning. If there's a code-match, it's becau= se someone did a code request. Someone needed that code and he will get the= appropriate "coding" help if the student has some support to do that work.=

Good point.

We can have a different instance for those cases were there is no requ= est, thereby no need to provide a shepherd. They could be just "code opport= unity" and there's no commitment from anyone for those code-matches.

In looking at the data model again, how about having the CodeMatch either b= e a fulfilled CodeRequest mapping a project to a specification or simply th= e connection between a project and specification.  This let's us keep = the terms and model simple which may be easier for users as they will have less to understand in terms of our t= erminology.  Also keeping the data model simpler should help reduce co= ding efforts.

 

However, if you want to advertise projects that already finished, ment= ors make not sense indeed. But consider the following situation: there is a= CodeRequest for an specific protocol. That CodeRequest already finds previ= ously finished projects but still requires further code. In that case, the previous projects don= =E2=80=99t need a mentor, of course, but the new projects do. But because m= entors are associated with CodeRequest (and not with project), once we defi= ne a mentor to help in the new projects that mentor will be also linked with the old projects too. In summary, old proj= ects will always have a mentor once new projects are required.
If the link is to the same draft, but I suspect this will happen more with = draft revisions or drafts that extend base specifications.

The whole issue resides in the fact that mentors are associated with C= odeRequest. Previously, mentors were associated with individual projects (a= t that point we were referring projects to as CodeMatches, before the last = change in the model). Here, we have some options:

Yes, you are correct and I think my updated suggestion fixes this, but let = me know if I missed anything.

1) Assume that dummy mentors can be associated with CodeRequests that = exist only to advertise already finished projects, but we need to live with= the idea that once additional code is needed for those CodeRequests, a rea= l mentor will be assigned, and the finished project will inherit that new real mentor.

2) Rollback the model back to associate mentors with projects, indicat= ing that mentors are optional. However, we may be imposing an administrativ= e burden here.

A third option could be to have active "code-requests" with mentors an= d "code-opportunities" (or a better name) for finished projects, other &nbs= p;RFCs, etc. with no mentor. 
Or just to have two options for CodeMatches - with or without a CodeRequest= .

Thanks!
Kathleen 


Christian


Another option is checking how we tell the story. The question may be = solved if we say that =E2=80=9Cmentors exist to help in the development of = new projects=E2=80=9D, implying that already finished projects has now asso= ciation with current mentors. Too simplistic?

Best regards,

Lisandro

Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty <kathleen.moriarty.ietf@gmai= l.com> escreveu:

Lisandro,

Thank you for your time and effort developing the data model with the = team!  This looks great from what we discussed.  From additional = feedback received from the IESG, the point was made that you may not always= have a shepherd.  If we want this to also advertise existing implementations (open source or proprietary) of= existing RFCs, there should be flexibility to demonstrate links between a = CodeRequest (in this case an RFC) and a project without having a mentor.&nb= sp; You would still have a coder or the project owner that creates the link and it would be possible for others to= connect their project to that same published IETF or IRTF document.

In that case, would the coder then also be connected to the CodeReques= t so there are multiple ways to make the connections?

We would need search capabilities for coders looking for projects so t= hey might only see ones that have a mentor and I'm sure they would want to = be able to restrict their view to the projects they have time to code (1 FT= E for x weeks or months, etc.).

Any other comments?

Thank you,
Kathleen

On Sat, Feb 7, 2015 at 3:24 AM, Lis= andro Zambenedetti Granville <granville= @inf.ufrgs.br> wrote:
Dear all

After one of our last meetings, a new data model (v3) for CodeMatch ha= s been defined. Please, find below the new version of such a data model. We= tried to incorporate the comments received in the list as well as the sugg= estions mentioned during the last meetings. Terms in this version are also aligned with the list of= terms previously shared by Kathleen in the mailing list. Any feedback is w= elcomed.

Best regards,

Lisandro

<codematchv3-3.png>

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.= org
https://www.ietf.org/mailman/listinfo/codematch= -develop




--

Best regards,
Kathleen

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.= org
https://www.ietf.org/mailman/listinfo/codematch= -develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop= @ietf.org
https://www.ietf.org/mailman/listinfo/cod= ematch-develop
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.= org
https://www.ietf.org/mailman/listinfo/codematch= -develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop= @ietf.org
https://www.ietf.org/mailman/listinfo/cod= ematch-develop



--

Bes= t regards,
Kathleen



=

--

Best regards,
Kathleen



--
Wanderson




--

Best regards,
Kathleen

_______________________________________________
Codematc= h-develop mailing list
Codematch-develop@ietf.org
https://ww= w.ietf.org/mailman/listinfo/codematch-develop


=

_____________________________________________= __
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop


= ------=_Part_1289565_495807537.1425269277182-- From nobody Mon Mar 2 07:16:16 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF021A1AA9 for ; Mon, 2 Mar 2015 07:16:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 ULRemR6lAJde for ; Mon, 2 Mar 2015 07:16:05 -0800 (PST) Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C9A91A892B for ; Mon, 2 Mar 2015 07:09:48 -0800 (PST) Received: by lbiv13 with SMTP id v13so11999365lbi.1 for ; Mon, 02 Mar 2015 07:09:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nMK90T/LfGfHx3u8NZHDex8GULBONgquGDTL3XcJ6Lo=; b=HqjsH8UM1vvnAb4oVNr6Uq6JSMusaMLOvv0/c3bhN4yFhGCmXJR8eMlPS0X9adQ4iJ 5lBRJ5aXZfiDxGVb5cCa/MhWHlgmSWm92uIHwjRf4qa34P7Gr6FGbfP2ahHgLfGCXT+Z L4EMIjZvpO62FphN1rOss0GJZhgEsuhJ0GoMrb1QVcQ4Y3bcqypbzZh5QcTDYcWHXCMU o7caoVYNU2vRWIMlW4VwAbF/mu69vX4zQAZl4csZgdcmMIduXxp6PSKW/atgNy8OtW5I ug6aD4VehxoamtctpKZEeBXri7Lbq4MtCaSqLa3LcWv/9fHkoK56s4MeTQJxZczNuMci uYdQ== MIME-Version: 1.0 X-Received: by 10.152.183.165 with SMTP id en5mr25232697lac.0.1425308986552; Mon, 02 Mar 2015 07:09:46 -0800 (PST) Received: by 10.112.167.101 with HTTP; Mon, 2 Mar 2015 07:09:46 -0800 (PST) In-Reply-To: References: <1070000593.1289566.1425269277230.JavaMail.yahoo@mail.yahoo.com> Date: Mon, 2 Mar 2015 10:09:46 -0500 Message-ID: From: Kathleen Moriarty To: "codematch-develop@ietf.org" Content-Type: multipart/alternative; boundary=001a1134573cd6b59105104f9b09 Archived-At: Subject: Re: [Codematch-develop] Codematch-develop Digest, Vol 8, Issue 23 X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 15:16:13 -0000 --001a1134573cd6b59105104f9b09 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Kristin, Thanks for your work on the card sort! I moved around the boxes and wasn't sure what I should put in for all visitors vs. overview information. I view them similarly, so it was hard for me to tell what was meant by each heading. Also, I didn't have much in the coder bucket as there was no box that said "My Code Matches". The mentor owns the code requests, so that wasn't appropriate for that category. I also think the mailing list option will be tough, but maybe we will learn something from that. The tricky part will be that responses may depend on a persons knowledge of the IETF Trust and IPR policies as opposed to functionality. I would have put that one in a few categories, but for IPR reasons, selected the one that I did. Thanks, Kathleen On Mon, Mar 2, 2015 at 9:54 AM, Moriarty, Kathleen < kathleen.moriarty@emc.com> wrote: > > > Sent from my iPhone > > Begin forwarded message: > > *From:* Kristin Burgh > *Date:* March 1, 2015 at 11:07:56 PM EST > *To:* "codematch-develop@ietf.org" > *Subject:* *Re: [Codematch-develop] Codematch-develop Digest, Vol 8, > Issue 23* > *Reply-To:* Kristin Burgh > > All - > > I believe our updated Card Sort is ready to go out. > > Please let me know if you have any questions regarding the attached - I > would like to formally launch this tomorrow (Monday - March 2), so please > have any comments, suggestions or updates in to me ASAP. > > > https://conceptcodify.com/studies/AJDvCQAeNrm9nOO9rwNjsQDc/via/MlU1pQ4sRN= efS1iIfsYi4l3a/ > > In terms of distribution, I believe we had discussed using our > respective social networks (e.g. - LinkedIn, Facebook, etc.) to capture > survey results. > > I'd like to close this survey on Tuesday, March 10 and report the > results during the weekly meeting the following day. I hope that a week > and a half will be enough time to allow the developers to make any > necessary changes prior to Dallas. > > Kind Regards, > > *Kristin * > > ------------------------------ > *From:* "codematch-develop-request@ietf.org" < > codematch-develop-request@ietf.org> > *To:* codematch-develop@ietf.org > *Sent:* Wednesday, February 25, 2015 11:06 AM > *Subject:* Codematch-develop Digest, Vol 8, Issue 23 > > ----- Forwarded Message ----- > > Send Codematch-develop mailing list submissions to > codematch-develop@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/codematch-develop > or, via email, send a message with subject or body 'help' to > codematch-develop-request@ietf.org > > You can reach the person managing the list at > codematch-develop-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Codematch-develop digest..." > > Today's Topics: > > 1. Re: CodeMatch data model v3 (Kathleen Moriarty) > 2. Re: Codematch-develop Digest, Vol 8, Issue 22 (Kristin Burgh) > Hi Lisandro, > > I reached out to Pete Resnick, one of the Apps directors to see what he > thought. > > He does agree that something is missing. > > I think we can handle this in a few ways. We need to be able to > differentiate when code is requested from when a link is being made as th= e > information on each will be different. > > The data model would need a few elements to be optional, like mentor, > resources (estimated level of effort for coding). You usually see this > when there is accompanying UML. > > Pete suggested a different name for CodeRequest, maybe MatchRequest with > an element for CodeRequest? If we keep it at CodeRequest, I think > minimally an attribute to designate if code is actually requested would b= e > necessary - or we change this to MatchRequest with an attribute called > CodeRequest as a boolean (yes/no - for our team members that are not data > model savvy). > > Just some thoughts so the data model would be clear... > > On Tue, Feb 24, 2015 at 4:15 PM, Moriarty, Kathleen < > kathleen.moriarty@emc.com> wrote: > > Hi Lisandro, > > Sent from my iPhone > > On Feb 24, 2015, at 5:41 AM, "Lisandro Zambenedetti Granville" < > granville@inf.ufrgs.br> wrote: > > If thinks are still not clear, I can try to provide examples. > > I think an explanation along with the data model will be necessary if > no line is included to show the code request isn't needed to link a proje= ct > to a specification. That and examples will help developers as we proceed= . > > > Hello Kathleen > > Just to clarify: a CodeRequest is still needed to link projects to a > specification. The data model is not missing a link between projects and > specifications; projects are are linked to specifications only through a > CodeRequest. What we have discussed so far is that the mentor field in th= e > CodeRequest is only meaningful for active projects, since already finishe= d > projects don=E2=80=99t need a mentor anymore. > > Let's chat about this tomorrow as I still don't see why a direct > connection between a project and specification can't be made. Maybe it's > to have a grouping, but I'd like to talk through this a bit. If you have > an example for tomorrow, that may help. > > Thank you, > Kathleen > > Best regards, > > Lisandro > > Sent from my iPhone > > On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" < > granville@inf.ufrgs.br> wrote: > > Hello Kathleen > > I=E2=80=99m not an expert on data models, so I may be wrong. Today, Code= Match is > a relationship between Project and CodeRequest. I believe it is not > possible to have another relationship between Project and Specification > named CodeMatch too. But let me ask you if you agree with the suggestion = of > =E2=80=9Cfixing=E2=80=9D this issue by saying that =E2=80=9Ca Mentor is t= he person responsible for > helping in the development of active projects=E2=80=9D, implying that men= tors have > no role in already finished projects? In that way, we don=E2=80=99t need = to change > the data model. Not that we could not change it, but I believe keeping it > simple is important. > > Best regards, > > Lisandro > > Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen > escreveu: > > Hi, > > Sent from my iPhone > > On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" > wrote: > > Hi Kathleen, > > To me, a CodeRequest is an explicit call for FUTURE developments. If > someone is questing code, that=E2=80=99s because (additional?) code is re= quired. To > help in the development of new code throughout new projects, mentors seem > to be mandatory. > > > I agree with Lisandro's reasoning. If there's a code-match, it's because > someone did a code request. Someone needed that code and he will get the > appropriate "coding" help if the student has some support to do that work= . > > > Good point. > > > We can have a different instance for those cases were there is no > request, thereby no need to provide a shepherd. They could be just "code > opportunity" and there's no commitment from anyone for those code-matches= . > > > In looking at the data model again, how about having the CodeMatch eithe= r > be a fulfilled CodeRequest mapping a project to a specification or simply > the connection between a project and specification. This let's us keep t= he > terms and model simple which may be easier for users as they will have le= ss > to understand in terms of our terminology. Also keeping the data model > simpler should help reduce coding efforts. > > > > > However, if you want to advertise projects that already finished, > mentors make not sense indeed. But consider the following situation: ther= e > is a CodeRequest for an specific protocol. That CodeRequest already finds > previously finished projects but still requires further code. In that cas= e, > the previous projects don=E2=80=99t need a mentor, of course, but the new= projects > do. But because mentors are associated with CodeRequest (and not with > project), once we define a mentor to help in the new projects that mentor > will be also linked with the old projects too. In summary, old projects > will always have a mentor once new projects are required. > > If the link is to the same draft, but I suspect this will happen more > with draft revisions or drafts that extend base specifications. > > > The whole issue resides in the fact that mentors are associated with > CodeRequest. Previously, mentors were associated with individual projects > (at that point we were referring projects to as CodeMatches, before the > last change in the model). Here, we have some options: > > > Yes, you are correct and I think my updated suggestion fixes this, but > let me know if I missed anything. > > > 1) Assume that dummy mentors can be associated with CodeRequests that > exist only to advertise already finished projects, but we need to live wi= th > the idea that once additional code is needed for those CodeRequests, a re= al > mentor will be assigned, and the finished project will inherit that new > real mentor. > > 2) Rollback the model back to associate mentors with projects, > indicating that mentors are optional. However, we may be imposing an > administrative burden here. > > > A third option could be to have active "code-requests" with mentors and > "code-opportunities" (or a better name) for finished projects, other RFC= s, > etc. with no mentor. > > Or just to have two options for CodeMatches - with or without a > CodeRequest. > > Thanks! > Kathleen > > > Christian > > > Another option is checking how we tell the story. The question may be > solved if we say that =E2=80=9Cmentors exist to help in the development o= f new > projects=E2=80=9D, implying that already finished projects has now associ= ation with > current mentors. Too simplistic? > > Best regards, > > Lisandro > > Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty < > kathleen.moriarty.ietf@gmail.com> escreveu: > > Lisandro, > > Thank you for your time and effort developing the data model with the > team! This looks great from what we discussed. From additional feedback > received from the IESG, the point was made that you may not always have a > shepherd. If we want this to also advertise existing implementations (op= en > source or proprietary) of existing RFCs, there should be flexibility to > demonstrate links between a CodeRequest (in this case an RFC) and a proje= ct > without having a mentor. You would still have a coder or the project own= er > that creates the link and it would be possible for others to connect thei= r > project to that same published IETF or IRTF document. > > In that case, would the coder then also be connected to the CodeRequest > so there are multiple ways to make the connections? > > We would need search capabilities for coders looking for projects so > they might only see ones that have a mentor and I'm sure they would want = to > be able to restrict their view to the projects they have time to code (1 > FTE for x weeks or months, etc.). > > Any other comments? > > Thank you, > Kathleen > > On Sat, Feb 7, 2015 at 3:24 AM, Lisandro Zambenedetti Granville < > granville@inf.ufrgs.br> wrote: > > Dear all > > After one of our last meetings, a new data model (v3) for CodeMatch has > been defined. Please, find below the new version of such a data model. We > tried to incorporate the comments received in the list as well as the > suggestions mentioned during the last meetings. Terms in this version are > also aligned with the list of terms previously shared by Kathleen in the > mailing list. Any feedback is welcomed. > > Best regards, > > Lisandro > > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > > > -- > > Best regards, > Kathleen > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > > > > > -- > > Best regards, > Kathleen > > > > > > > -- > > Best regards, > Kathleen > > Good Morning/Afternoon/Evening Everyone - > > I just wanted to let everyone know that I'll be sending out an updated > version of the card-sort survey over this coming weekend. The aim is to = be > able to have as much feedback from a variety of different users as we can > get to help create the best possible prototypes in time for Dallas. > > If you have any questions, please feel free to contact me either via > this email thread or directly via "kmburgh@yahoo.com". > > Also - my apologies to you all - but I'll be about 30 minutes late to > today's call/webex due to a scheduling conflict. > > Kind Regards, > > Kristin > > > > ------------------------------ > *From:* "codematch-develop-request@ietf.org" < > codematch-develop-request@ietf.org> > *To:* codematch-develop@ietf.org > *Sent:* Wednesday, February 25, 2015 9:30 AM > *Subject:* Codematch-develop Digest, Vol 8, Issue 22 > > ----- Forwarded Message ----- > > Send Codematch-develop mailing list submissions to > codematch-develop@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/codematch-develop > or, via email, send a message with subject or body 'help' to > codematch-develop-request@ietf.org > > You can reach the person managing the list at > codematch-develop-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Codematch-develop digest..." > > Today's Topics: > > 1. Re: CodeMatch data model v3 (Kathleen Moriarty) > Dear Wanderson, > > Yes, I am sure we will be able to help you and other volunteer > developers figure out how to get started and to work as a team without > having to attend Dallas. > > Thank you. > > On Tue, Feb 24, 2015 at 7:11 PM, Wanderson Paim de Jesus < > wanderson.jesus@rnp.br> wrote: > > Dear Kathleen, > > I'm afraid saying, but I had not planned attending the IETF in Dallas > and I'm not aware about Code Sprint. > > If it is possible, after the Code Sprint such other collaborators could > send me the tools and manuals about the Codetracker. > > Best regards, > > ------------------------------ > *De: *"Kathleen Moriarty" > *Para: *"Wanderson Paim de Jesus" > *Cc: *"Christian O'Flaherty" , "Kathleen Moriarty" < > kathleen.moriarty@emc.com>, codematch-develop@ietf.org, "Lisandro > Zambenedetti Granville" > *Enviadas: *Segunda-feira, 23 de fevereiro de 2015 11:46:59 > > *Assunto: *Re: [Codematch-develop] CodeMatch data model v3 > > Wanderson, > > We are glad to have your assistance! > > Dave Waltermire has also volunteered to help code and we may have 1-2 > other volunteers soon. If anyone is attending the IETF in Dallas and wil= l > be able to help us code, it may be a good idea to go to the Code Sprint > Saturday before the meeting as you'll get the tools to install and learn > more about the datatracker. Please let me know if you need more > information on the Code Sprint. > > Thank you, > Kathleen > > On Mon, Feb 23, 2015 at 7:14 AM, Wanderson Paim de Jesus < > wanderson.jesus@rnp.br> wrote: > > Hi Kathleen, > > I find Codematch a good idea and hope being able to contribute with its > success. > > Christian seems to be interest in coding too. Given that I'm not > familiar with datatracker, his support would be honestly welcome. > > Best regards, > > Wanderson > > ------------------------------ > *De: *"Kathleen Moriarty" > *Para: *"Lisandro Zambenedetti Granville" > *Cc: *"Christian O'Flaherty" , "Kathleen Moriarty" < > kathleen.moriarty@emc.com>, codematch-develop@ietf.org, "Wanderson Paim > de Jesus" > *Enviadas: *Sexta-feira, 20 de fevereiro de 2015 13:23:51 > *Assunto: *Re: [Codematch-develop] CodeMatch data model v3 > > > > > On Fri, Feb 20, 2015 at 6:23 AM, Lisandro Zambenedetti Granville < > granville@inf.ufrgs.br> wrote: > > Dear all > > Wanderson Paim (cc=E2=80=99ed in this message), who develop the prototyp= e > available at http://codematch.inf.ufrgs.br is also a volunteer to code > the CodeMatch backend. > > > Excellent, it's great to have you on the team Wanderson! Thank you for > volunteering! > > Best regards, > Kathleen > > > Best regards, > > Lisandro > > Em 17/02/2015, =C3=A0(s) 15:19, Christian O'Flaherty > escreveu: > > > > I have a couple more volunteers for coding as well lined up. There may > be more decisions to be made for that and prep for developers to get > familiar with the datatracker and how it will be accessed. > > > Although I never used datatracker as a coder I would like to be among th= e > initial volunteers for coding. > > Christian > > > Thank you, > Kathleen > > > Christian > > > Thank you, > Kathleen > > Sent from my iPhone > > On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" < > granville@inf.ufrgs.br> wrote: > > Hello Kathleen > > I=E2=80=99m not an expert on data models, so I may be wrong. Today, Code= Match is > a relationship between Project and CodeRequest. I believe it is not > possible to have another relationship between Project and Specification > named CodeMatch too. But let me ask you if you agree with the suggestion = of > =E2=80=9Cfixing=E2=80=9D this issue by saying that =E2=80=9Ca Mentor is t= he person responsible for > helping in the development of active projects=E2=80=9D, implying that men= tors have > no role in already finished projects? In that way, we don=E2=80=99t need = to change > the data model. Not that we could not change it, but I believe keeping it > simple is important. > > Best regards, > > Lisandro > > Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen > escreveu: > > Hi, > > Sent from my iPhone > > On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" > wrote: > > Hi Kathleen, > > To me, a CodeRequest is an explicit call for FUTURE developments. If > someone is questing code, that=E2=80=99s because (additional?) code is re= quired. To > help in the development of new code throughout new projects, mentors seem > to be mandatory. > > > I agree with Lisandro's reasoning. If there's a code-match, it's because > someone did a code request. Someone needed that code and he will get the > appropriate "coding" help if the student has some support to do that work= . > > > Good point. > > > We can have a different instance for those cases were there is no > request, thereby no need to provide a shepherd. They could be just "code > opportunity" and there's no commitment from anyone for those code-matches= . > > > In looking at the data model again, how about having the CodeMatch eithe= r > be a fulfilled CodeRequest mapping a project to a specification or simply > the connection between a project and specification. This let's us keep t= he > terms and model simple which may be easier for users as they will have le= ss > to understand in terms of our terminology. Also keeping the data model > simpler should help reduce coding efforts. > > > > > However, if you want to advertise projects that already finished, > mentors make not sense indeed. But consider the following situation: ther= e > is a CodeRequest for an specific protocol. That CodeRequest already finds > previously finished projects but still requires further code. In that cas= e, > the previous projects don=E2=80=99t need a mentor, of course, but the new= projects > do. But because mentors are associated with CodeRequest (and not with > project), once we define a mentor to help in the new projects that mentor > will be also linked with the old projects too. In summary, old projects > will always have a mentor once new projects are required. > > If the link is to the same draft, but I suspect this will happen more > with draft revisions or drafts that extend base specifications. > > > The whole issue resides in the fact that mentors are associated with > CodeRequest. Previously, mentors were associated with individual projects > (at that point we were referring projects to as CodeMatches, before the > last change in the model). Here, we have some options: > > > Yes, you are correct and I think my updated suggestion fixes this, but > let me know if I missed anything. > > > 1) Assume that dummy mentors can be associated with CodeRequests that > exist only to advertise already finished projects, but we need to live wi= th > the idea that once additional code is needed for those CodeRequests, a re= al > mentor will be assigned, and the finished project will inherit that new > real mentor. > > 2) Rollback the model back to associate mentors with projects, > indicating that mentors are optional. However, we may be imposing an > administrative burden here. > > > A third option could be to have active "code-requests" with mentors and > "code-opportunities" (or a better name) for finished projects, other RFC= s, > etc. with no mentor. > > Or just to have two options for CodeMatches - with or without a > CodeRequest. > > Thanks! > Kathleen > > > Christian > > > Another option is checking how we tell the story. The question may be > solved if we say that =E2=80=9Cmentors exist to help in the development o= f new > projects=E2=80=9D, implying that already finished projects has now associ= ation with > current mentors. Too simplistic? > > Best regards, > > Lisandro > > Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty < > kathleen.moriarty.ietf@gmail.com> escreveu: > > Lisandro, > > Thank you for your time and effort developing the data model with the > team! This looks great from what we discussed. From additional feedback > received from the IESG, the point was made that you may not always have a > shepherd. If we want this to also advertise existing implementations (op= en > source or proprietary) of existing RFCs, there should be flexibility to > demonstrate links between a CodeRequest (in this case an RFC) and a proje= ct > without having a mentor. You would still have a coder or the project own= er > that creates the link and it would be possible for others to connect thei= r > project to that same published IETF or IRTF document. > > In that case, would the coder then also be connected to the CodeRequest > so there are multiple ways to make the connections? > > We would need search capabilities for coders looking for projects so > they might only see ones that have a mentor and I'm sure they would want = to > be able to restrict their view to the projects they have time to code (1 > FTE for x weeks or months, etc.). > > Any other comments? > > Thank you, > Kathleen > > On Sat, Feb 7, 2015 at 3:24 AM, Lisandro Zambenedetti Granville < > granville@inf.ufrgs.br> wrote: > > Dear all > > After one of our last meetings, a new data model (v3) for CodeMatch has > been defined. Please, find below the new version of such a data model. We > tried to incorporate the comments received in the list as well as the > suggestions mentioned during the last meetings. Terms in this version are > also aligned with the list of terms previously shared by Kathleen in the > mailing list. Any feedback is welcomed. > > Best regards, > > Lisandro > > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > > > -- > > Best regards, > Kathleen > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > > > > -- > > Best regards, > Kathleen > > > > > -- > > Best regards, > Kathleen > > > > -- > Wanderson > > > > > -- > > Best regards, > Kathleen > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > --=20 Best regards, Kathleen --001a1134573cd6b59105104f9b09 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Kristin,

Thanks for your work on the= card sort!

I moved around the boxes and wasn'= t sure what I should put in for all visitors vs. overview information.=C2= =A0 I view them similarly, so it was hard for me to tell what was meant by = each heading.

Also, I didn't have much in the = coder bucket as there was no box that said "My Code Matches".=C2= =A0 The mentor owns the code requests, so that wasn't appropriate for t= hat category.=C2=A0 I also think the mailing list option will be tough, but= maybe we will learn something from that. The tricky part will be that resp= onses may depend on a persons knowledge of the IETF Trust and IPR policies = as opposed to functionality.=C2=A0 I would have put that one in a few categ= ories, but for IPR reasons, selected the one that I did.

Thanks,
Kathleen
On Mon, Mar 2, 2015 at 9:54 AM, Moriarty, Kathl= een <kathleen.moriarty@emc.com> wrote:


Sent from my iPhone

Begin forwarded message:

From: Kristin Burgh <kmburgh@yahoo.com>
Date: March 1, 2015 at 11:07:56 PM EST
To: "codematch-develop@ietf.org" <codematch-develop@ietf.org>
Subject: Re: [Codematch-develop] Codematch-develop Digest, Vol 8,= Issue 23
Reply-To: Kristin Burgh <kmburgh@yahoo.com>

All -=C2=A0

I believe our updated Card Sort is ready to go out.<= /span>

Please let me know if you have any questions regardi= ng the attached - I would like to formally launch this tomorrow (Monday - M= arch 2), so please have any comments, suggestions or updates in to me ASAP.<= /div>


In terms of distribution, I believe we had discussed using= our respective social networks (e.g. - LinkedIn, Facebook, etc.) to captur= e survey results.

I'd like to close this survey on Tuesday, March 10 and= report the results during the weekly meeting the following day.=C2=A0 I ho= pe that a week and a half will be enough time to allow the developers to make any necessary changes prior to Dallas.

Kind Regards,=C2=A0
=C2=A0
Kristin=C2=A0

From: &= quot;codematch-develop-request@ietf.org" <codematch-develop-request@i= etf.org>
To: codematch-develop@ietf.org
Sent: Wednesday, February 25= , 2015 11:06 AM
Subject: Codematch-develop D= igest, Vol 8, Issue 23

----- Forwarded Message -----

Send Codematch-develop mailing list submissions to
=C2=A0=C2=A0=C2=A0 codematch-develop@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
=C2=A0=C2=A0=C2=A0 https://www.ietf.org/mailman/listinfo/codematch-develop
or, via email, send a message with subject or body 'help' to
=C2=A0=C2=A0=C2=A0 codematch-develop-request@ietf.org

You can reach the person managing the list at
=C2=A0=C2=A0=C2=A0 codematch-develop-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Codematch-develop digest..."

Today's Topics:

=C2=A0 1. Re: CodeMatch data model v3 (Kathleen Moriarty)
=C2=A0 2. Re: Codematch-develop Digest, Vol 8, Issue 22 (Kristin Burgh)
Hi Lisandro,

I reached out to Pete Resnick, one of the Apps directors to see what h= e thought.

He does agree that something is missing.

I think we can handle this in a few ways.=C2=A0 We need to be able to = differentiate when code is requested from when a link is being made as the = information on each will be different. =C2=A0

The data model would need a few elements to be optional, like mentor, = resources (estimated level of effort for coding).=C2=A0 You usually see thi= s when there is accompanying UML.

Pete suggested a different name for CodeRequest, maybe MatchRequest wi= th an element for CodeRequest?=C2=A0 If we keep it at CodeRequest, I think = minimally an attribute to designate if code is actually requested would be = necessary - or we change this to MatchRequest with an attribute called CodeRequest as a boolean (yes/no - for our team m= embers that are not data model savvy).

Just some thoughts so the data model would be clear...

On Tue, Feb 24, 2015 at 4:15 PM, Moriarty, Kathleen <kathleen.moriarty@emc.com> wrote:<= br>
Hi Lisandro,

Sent from my iPhone

On Feb 24, 2015, at 5:41 AM, "Lisandro Zambenedetti Granville" &l= t;granville@inf.ufrgs.br> wrote:

If thinks are still not clear, I can try to provide examples.

I think an explanation along with the data model will be necessary if no li= ne is included to show the code request isn't needed to link a project = to a specification.=C2=A0 That and examples will help developers as we proc= eed.

Hello Kathleen

Just to clarify: a CodeRequest is still needed to link projects to a s= pecification. The data model is not missing a link between projects and spe= cifications; projects are are linked to specifications only through a CodeR= equest. What we have discussed so far is that the mentor field in the CodeRequest is only meaningful for act= ive projects, since already finished projects don=E2=80=99t need a mentor a= nymore.

Let's chat about this tomorrow as I still don't see why a di= rect connection between a project and specification can't be made.=C2= =A0 Maybe it's to have a grouping, but I'd like to talk through thi= s a bit.=C2=A0 If you have an example for tomorrow, that may help.

Thank you,
Kathleen

Best regards,

Lisandro

Sent from my iPhone

On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" &l= t;granville@inf.ufrgs.br> wrote:

Hello Kathleen

I=E2=80=99m not an expert on data models, so I may be wrong. Today, Co= deMatch is a relationship between Project and CodeRequest. I believe it is = not possible to have another relationship between Project and Specification= named CodeMatch too. But let me ask you if you agree with the suggestion of =E2=80=9Cfixing=E2=80=9D this issue by= saying that =E2=80=9Ca Mentor is the person responsible for helping in the= development of active projects=E2=80=9D, implying that mentors have no rol= e in already finished projects? In that way, we don=E2=80=99t need to chang= e the data model. Not that we could not change it, but I believe keeping it = simple is important.

Best regards,

Lisandro

Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen <kathleen.m= oriarty@emc.com> escreveu:

Hi,

Sent from my iPhone

On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" <oflahe= rty@isoc.org> wrote:

Hi Kathleen,=C2=A0

To me, a CodeRequest is an explicit call for FUTURE developments. If s= omeone is questing code, that=E2=80=99s because (additional?) code is requi= red. To help in the development of new code throughout new projects, mentor= s seem to be mandatory.

I agree with Lisandro's reasoning. If there's a code-match, it= 's because someone did a code request. Someone needed that code and he = will get the appropriate "coding" help if the student has some su= pport to do that work.

Good point.

We can have a different instance for those cases were there is no requ= est, thereby no need to provide a shepherd. They could be just "code o= pportunity" and there's no commitment from anyone for those code-m= atches.

In looking at the data model again, how about having the CodeMatch either b= e a fulfilled CodeRequest mapping a project to a specification or simply th= e connection between a project and specification.=C2=A0 This let's us k= eep the terms and model simple which may be easier for users as they will have less to understand in terms of our t= erminology.=C2=A0 Also keeping the data model simpler should help reduce co= ding efforts.

=C2=A0

However, if you want to advertise projects that already finished, ment= ors make not sense indeed. But consider the following situation: there is a= CodeRequest for an specific protocol. That CodeRequest already finds previ= ously finished projects but still requires further code. In that case, the previous projects don=E2=80=99t n= eed a mentor, of course, but the new projects do. But because mentors are a= ssociated with CodeRequest (and not with project), once we define a mentor = to help in the new projects that mentor will be also linked with the old projects too. In summary, old projects wi= ll always have a mentor once new projects are required.
If the link is to the same draft, but I suspect this will happen more with = draft revisions or drafts that extend base specifications.

The whole issue resides in the fact that mentors are associated with C= odeRequest. Previously, mentors were associated with individual projects (a= t that point we were referring projects to as CodeMatches, before the last = change in the model). Here, we have some options:

Yes, you are correct and I think my updated suggestion fixes this, but let = me know if I missed anything.

1) Assume that dummy mentors can be associated with CodeRequests that = exist only to advertise already finished projects, but we need to live with= the idea that once additional code is needed for those CodeRequests, a rea= l mentor will be assigned, and the finished project will inherit that new real mentor.

2) Rollback the model back to associate mentors with projects, indicat= ing that mentors are optional. However, we may be imposing an administrativ= e burden here.

A third option could be to have active "code-requests" with = mentors and "code-opportunities" (or a better name) for finished = projects, other =C2=A0RFCs, etc. with no mentor.=C2=A0
Or just to have two options for CodeMatches - with or without a CodeRequest= .

Thanks!
Kathleen=C2=A0


Christian


Another option is checking how we tell the story. The question may be = solved if we say that =E2=80=9Cmentors exist to help in the development of = new projects=E2=80=9D, implying that already finished projects has now asso= ciation with current mentors. Too simplistic?

Best regards,

Lisandro

Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty <kath= leen.moriarty.ietf@gmail.com> escreveu:

Lisandro,

Thank you for your time and effort developing the data model with the = team!=C2=A0 This looks great from what we discussed.=C2=A0 From additional = feedback received from the IESG, the point was made that you may not always= have a shepherd.=C2=A0 If we want this to also advertise existing implementations (open source or proprietary) of existin= g RFCs, there should be flexibility to demonstrate links between a CodeRequ= est (in this case an RFC) and a project without having a mentor.=C2=A0 You = would still have a coder or the project owner that creates the link and it would be possible for others to connect= their project to that same published IETF or IRTF document.

In that case, would the coder then also be connected to the CodeReques= t so there are multiple ways to make the connections?

We would need search capabilities for coders looking for projects so t= hey might only see ones that have a mentor and I'm sure they would want= to be able to restrict their view to the projects they have time to code (= 1 FTE for x weeks or months, etc.).

Any other comments?

Thank you,
Kathleen

On Sat, Feb 7, 2015 at 3:24 AM, Lisandro Zambenedetti Granville <granville@inf.ufrgs.br> wrote:
Dear all

After one of our last meetings, a new data model (v3) for CodeMatch ha= s been defined. Please, find below the new version of such a data model. We= tried to incorporate the comments received in the list as well as the sugg= estions mentioned during the last meetings. Terms in this version are also aligned with the list of terms pr= eviously shared by Kathleen in the mailing list. Any feedback is welcomed.<= /div>

Best regards,

Lisandro

<codematchv3-3.png>

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop




--

Best regards,
Kathleen

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/cod= ematch-develop
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop





--

Best regards,
Kathleen





--

Best regards,
Kathleen

Good Morning/Afternoon/Evening Everyone -=C2=A0

I just wanted to let everyone know that I'll be = sending out an updated version of the card-sort survey over this coming wee= kend.=C2=A0 The aim is to be able to have as much feedback from a variety of different users a= s we can get to help create the best possible prototypes in time for Dallas= .

If you have any questions, please feel free to conta= ct me either via this email thread or directly via "kmburgh@yahoo.com".

Also - my apologies to you all - but I'll be about 30 = minutes late to today's call/webex due to a scheduling conflict.

Kind Regards,=C2=A0

Kristin
=C2=A0


From: &= quot;codematch-develop-request@ietf.org" <codematch-develop-request@i= etf.org>
To: codematch-develop@ietf.org
Sent: Wednesday, February 25= , 2015 9:30 AM
Subject: Codematch-develop D= igest, Vol 8, Issue 22

----- Forwarded Message -----

Send Codematch-develop mailing list submissions to
=C2=A0=C2=A0=C2=A0 codematch-develop@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
=C2=A0=C2=A0=C2=A0 https://www.ietf.org/mailman/listinfo/codematch-develop
or, via email, send a message with subject or body 'help' to
=C2=A0=C2=A0=C2=A0 codematch-develop-request@ietf.org

You can reach the person managing the list at
=C2=A0=C2=A0=C2=A0 codematch-develop-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Codematch-develop digest..."

Today's Topics:

=C2=A0 1. Re: CodeMatch data model v3 (Kathleen Moriarty)
Dear Wanderson,

Yes, I am sure we will be able to help you and other volunteer develop= ers figure out how to get started and to work as a team without having to a= ttend Dallas.

Thank you.

On Tue, Feb 24, 2015 at 7:11 PM, Wanderson Paim de Jesus <wanderson.jesus@rnp.br> wrote:
Dear Kathleen,

I'm afraid = saying, but I had not planned attending the IETF in Dallas and I'm not = aware about Code Sprint.

If it is possib= le, after the Code Sprint such other collaborators could send me the tools = and manuals about the Codetracker.

Best regards,

De: "Kathleen Moriarty" <kathleen.moriarty.= ietf@gmail.com>
Para: "Wanderson Paim de Jesus" <wanderson.jesus@rnp.= br>
Cc: "Christian O'Flaherty" <oflaherty@isoc.org>= ;, "Kathleen Moriarty" <kathleen.moriarty@emc.com>= , codematch-develop@ietf.org, "Lisandro Zambenedetti Granville"= <granville@inf.ufrgs.br>
Enviadas: Segunda-feira, 23 de fevereiro de 2015 11:46:59

Assunto: Re: [Codematch-develop] CodeMatch data model v3

Wanderson,

We are glad to have your assistance!

Dave Waltermire has also volunteered to help code and we may have 1-2 = other volunteers soon.=C2=A0 If anyone is attending the IETF in Dallas and = will be able to help us code, it may be a good idea to go to the Code Sprin= t Saturday before the meeting as you'll get the tools to install and learn more about the datatracker.=C2=A0 Pleas= e let me know if you need more information on the Code Sprint.

Thank you,
Kathleen

On Mon, Feb 23, 2015 at 7:14 AM, Wanderson Paim de Jesus <wanderson.jesus@rnp.br> wrote:
= Hi Kathleen,

I find Codematch a good id= ea and hope being able to contribute with its success.

Christian seems to be inte= rest in coding too. Given that I'm not familiar with datatracker, his s= upport would be honestly welcome.

Best regards,

Wanderson

De: "Kathleen Moriarty" <kathleen.moriarty.= ietf@gmail.com>
Para: "Lisandro Zambenedetti Granville" <granville@in= f.ufrgs.br>
Cc: "Christian O'Flaherty" <oflaherty@isoc.org>= ;, "Kathleen Moriarty" <kathleen.moriarty@emc.com>= , codematch-develop@ietf.org, "Wanderson Paim de Jesus" <w= anderson.jesus@rnp.br>
Enviadas: Sexta-feira, 20 de fevereiro de 2015 13:23:51
Assunto: Re: [Codematch-develop] CodeMatch data model v3




On Fri, Feb 20, 2015 at 6:23 AM, Lisandro Zambenedetti Granville <granville@inf.ufrgs.br> wrote:
Dear all

Wanderson Paim (cc=E2=80=99ed in this message), who develop the protot= ype available at http://codematch.inf.ufrgs.br=C2=A0is also a volunteer to code the C= odeMatch backend.

Excellent, it's great to have you on the team Wanderson!=C2=A0 Tha= nk you for volunteering!

Best regards,
Kathleen=C2=A0

Best regards,

Lisandro

Em 17/02/2015, =C3=A0(s) 15:19, Christian O'Flaherty <oflaherty@i= soc.org> escreveu:



I have a couple more volunteers for coding as well lined up.=C2=A0 The= re may be more decisions to be made for that and prep for developers to get= familiar with the datatracker and how it will be accessed.

Although I never used datatracker as a coder I would like to be among the i= nitial volunteers for coding.=C2=A0

Christian=C2=A0


Thank you,
Kathleen=C2=A0

Christian


Thank you,
Kathleen=C2=A0

Sent from my iPhone

On Feb 17, 2015, at 7:05 AM, "Lisandro Zambenedetti Granville" &l= t;granville@inf.ufrgs.br> wrote:

Hello Kathleen

I=E2=80=99m not an expert on data models, so I may be wrong. Today, Co= deMatch is a relationship between Project and CodeRequest. I believe it is = not possible to have another relationship between Project and Specification= named CodeMatch too. But let me ask you if you agree with the suggestion of =E2=80=9Cfixing=E2=80=9D this issue by= saying that =E2=80=9Ca Mentor is the person responsible for helping in the= development of active projects=E2=80=9D, implying that mentors have no rol= e in already finished projects? In that way, we don=E2=80=99t need to chang= e the data model. Not that we could not change it, but I believe keeping it = simple is important.

Best regards,

Lisandro

Em 14/02/2015, =C3=A0(s) 14:52, Moriarty, Kathleen <kathleen.m= oriarty@emc.com> escreveu:

Hi,

Sent from my iPhone

On Feb 13, 2015, at 11:13 AM, "Christian O'Flaherty" <oflahe= rty@isoc.org> wrote:

Hi Kathleen,=C2=A0

To me, a CodeRequest is an explicit call for FUTURE developments. If s= omeone is questing code, that=E2=80=99s because (additional?) code is requi= red. To help in the development of new code throughout new projects, mentor= s seem to be mandatory.

I agree with Lisandro's reasoning. If there's a code-match, it= 's because someone did a code request. Someone needed that code and he = will get the appropriate "coding" help if the student has some su= pport to do that work.

Good point.

We can have a different instance for those cases were there is no requ= est, thereby no need to provide a shepherd. They could be just "code o= pportunity" and there's no commitment from anyone for those code-m= atches.

In looking at the data model again, how about having the CodeMatch either b= e a fulfilled CodeRequest mapping a project to a specification or simply th= e connection between a project and specification.=C2=A0 This let's us k= eep the terms and model simple which may be easier for users as they will have less to understand in terms of our t= erminology.=C2=A0 Also keeping the data model simpler should help reduce co= ding efforts.

=C2=A0

However, if you want to advertise projects that already finished, ment= ors make not sense indeed. But consider the following situation: there is a= CodeRequest for an specific protocol. That CodeRequest already finds previ= ously finished projects but still requires further code. In that case, the previous projects don=E2=80=99t n= eed a mentor, of course, but the new projects do. But because mentors are a= ssociated with CodeRequest (and not with project), once we define a mentor = to help in the new projects that mentor will be also linked with the old projects too. In summary, old projects wi= ll always have a mentor once new projects are required.
If the link is to the same draft, but I suspect this will happen more with = draft revisions or drafts that extend base specifications.

The whole issue resides in the fact that mentors are associated with C= odeRequest. Previously, mentors were associated with individual projects (a= t that point we were referring projects to as CodeMatches, before the last = change in the model). Here, we have some options:

Yes, you are correct and I think my updated suggestion fixes this, but let = me know if I missed anything.

1) Assume that dummy mentors can be associated with CodeRequests that = exist only to advertise already finished projects, but we need to live with= the idea that once additional code is needed for those CodeRequests, a rea= l mentor will be assigned, and the finished project will inherit that new real mentor.

2) Rollback the model back to associate mentors with projects, indicat= ing that mentors are optional. However, we may be imposing an administrativ= e burden here.

A third option could be to have active "code-requests" with = mentors and "code-opportunities" (or a better name) for finished = projects, other =C2=A0RFCs, etc. with no mentor.=C2=A0
Or just to have two options for CodeMatches - with or without a CodeRequest= .

Thanks!
Kathleen=C2=A0


Christian


Another option is checking how we tell the story. The question may be = solved if we say that =E2=80=9Cmentors exist to help in the development of = new projects=E2=80=9D, implying that already finished projects has now asso= ciation with current mentors. Too simplistic?

Best regards,

Lisandro

Em 11/02/2015, =C3=A0(s) 23:17, Kathleen Moriarty <kath= leen.moriarty.ietf@gmail.com> escreveu:

Lisandro,

Thank you for your time and effort developing the data model with the = team!=C2=A0 This looks great from what we discussed.=C2=A0 From additional = feedback received from the IESG, the point was made that you may not always= have a shepherd.=C2=A0 If we want this to also advertise existing implementations (open source or proprietary) of existin= g RFCs, there should be flexibility to demonstrate links between a CodeRequ= est (in this case an RFC) and a project without having a mentor.=C2=A0 You = would still have a coder or the project owner that creates the link and it would be possible for others to connect= their project to that same published IETF or IRTF document.

In that case, would the coder then also be connected to the CodeReques= t so there are multiple ways to make the connections?

We would need search capabilities for coders looking for projects so t= hey might only see ones that have a mentor and I'm sure they would want= to be able to restrict their view to the projects they have time to code (= 1 FTE for x weeks or months, etc.).

Any other comments?

Thank you,
Kathleen

On Sat, Feb 7, 2015 at 3:24 AM, Lisandro Zambenedetti Granville <granville@inf.ufrgs.br> wrote:
Dear all

After one of our last meetings, a new data model (v3) for CodeMatch ha= s been defined. Please, find below the new version of such a data model. We= tried to incorporate the comments received in the list as well as the sugg= estions mentioned during the last meetings. Terms in this version are also aligned with the list of terms pr= eviously shared by Kathleen in the mailing list. Any feedback is welcomed.<= /div>

Best regards,

Lisandro

<codematchv3-3.png>

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop




--

Best regards,
Kathleen

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/cod= ematch-develop
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/cod= ematch-develop




--

Best regards,
Kathleen




--

Best regards,
Kathleen



--
Wanderson




--

Best regards,
Kathleen

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop



_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch= -develop


_______________________________________________
Codematch-develop mailing list
Codem= atch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop



--

Best regards,
Kath= leen
--001a1134573cd6b59105104f9b09-- From nobody Wed Mar 4 07:30:50 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A851A711A for ; Wed, 4 Mar 2015 07:30:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.062 X-Spam-Level: X-Spam-Status: No, score=-0.062 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 ulyDsusIMbNH for ; Wed, 4 Mar 2015 07:30:44 -0800 (PST) Received: from delivery3.ufrgs.br (delivery3.ufrgs.br [143.54.2.213]) by ietfa.amsl.com (Postfix) with ESMTP id 16B0E1A6F32 for ; Wed, 4 Mar 2015 07:30:31 -0800 (PST) Received: from delivery3.ufrgs.br (localhost [127.0.0.1]) by delivery3.ufrgs.br (Postfix) with ESMTP id 8F67D300515; Wed, 4 Mar 2015 12:30:28 -0300 (BRT) Received: from msa1.ufrgs.br (msa1.ufrgs.br [143.54.2.208]) by delivery3.ufrgs.br (Postfix) with ESMTP id 150771FD; Wed, 4 Mar 2015 12:30:28 -0300 (BRT) From: Lisandro Zambenedetti Granville Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Wed, 4 Mar 2015 12:30:25 -0300 Message-Id: To: codematch-develop@ietf.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-AV-Checked: ClamAV using ClamSMTP Archived-At: Cc: Kristin Burgh , Wanderson Paim de Jesus Subject: [Codematch-develop] Meeting today X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2015 15:30:49 -0000 Dear all I have 6 visiting professor in the university today and I=E2=80=99m = taking them to a closing lunch. I=E2=80=99m afraid I won=E2=80=99t be = able to be back on time for our meeting today. Best regards, Lisandro From nobody Wed Mar 11 07:07:09 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC091ACCE2 for ; Wed, 11 Mar 2015 07:07:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.739 X-Spam-Level: X-Spam-Status: No, score=0.739 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 BucsGLDnxkN8 for ; Wed, 11 Mar 2015 07:07:05 -0700 (PDT) Received: from delivery3.ufrgs.br (delivery3.ufrgs.br [143.54.2.213]) by ietfa.amsl.com (Postfix) with ESMTP id 619641ACCDF for ; Wed, 11 Mar 2015 07:07:05 -0700 (PDT) Received: from delivery3.ufrgs.br (localhost [127.0.0.1]) by delivery3.ufrgs.br (Postfix) with ESMTP id B524A300C4A for ; Wed, 11 Mar 2015 11:07:02 -0300 (BRT) Received: from msa1.ufrgs.br (msa1.ufrgs.br [143.54.2.208]) by delivery3.ufrgs.br (Postfix) with ESMTP id E114E2EB for ; Wed, 11 Mar 2015 11:07:02 -0300 (BRT) From: Lisandro Zambenedetti Granville Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: Date: Wed, 11 Mar 2015 11:06:55 -0300 To: codematch-develop@ietf.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-AV-Checked: ClamAV using ClamSMTP Archived-At: Subject: [Codematch-develop] IETF 92 presentation X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 14:07:08 -0000 Dear all I created a Power Point presentation for the upcoming IETF 92. It=E2=80=99= s a very first draft of it, to discuss with you. I uploaded the power = point file in out shared folder in Google Drive: = https://drive.google.com/folderview?id=3D0B-dir4eV4Ih1V2tQSDdNRndrdGc&usp=3D= sharing File name: IETF 92 Presentation.pptx This time, I didn=E2=80=99t convert it to Google Driver presentation = format, keeping the original Power Point format: it=E2=80=99s then = easier for us to edit it. Is today=E2=80=99s meeting confirmed? Best regards, Lisandro= From nobody Wed Mar 11 08:31:02 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 502881A887F for ; Wed, 11 Mar 2015 08:31:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.311 X-Spam-Level: X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 VbYgtgetTc4D for ; Wed, 11 Mar 2015 08:30:58 -0700 (PDT) Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA661A888C for ; Wed, 11 Mar 2015 08:30:58 -0700 (PDT) Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2BFUrIW007089 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 Mar 2015 11:30:57 -0400 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t2BFUrIW007089 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1426087857; bh=JOm+83eXFbkM9PG340JSo5FbrCU=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=J3NUKDUNI62oRwqbfLKo6tvSqlUvZO+sIr8Jq8Z7ALe7Oti71EZfJaJJJfuF4juiy 5XbVIVtRPR5qgPrXIdbdJW7jTt7427rkYdHQttwh+FIiko9rTAL3MHKLDhFCCSDXZI vb5BBPIdkX5UKy5ydCdBzqpiX/o/Txkd+KxzraiE= X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com t2BFUrIW007089 Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd54.lss.emc.com (RSA Interceptor); Wed, 11 Mar 2015 11:29:55 -0400 Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t2BFUdgp004219 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Mar 2015 11:30:39 -0400 Received: from MXHUB207.corp.emc.com (10.253.68.33) by mxhub30.corp.emc.com (128.222.70.170) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 11 Mar 2015 11:30:39 -0400 Received: from MX103CL02.corp.emc.com ([169.254.6.227]) by MXHUB207.corp.emc.com ([10.253.68.33]) with mapi id 14.03.0224.002; Wed, 11 Mar 2015 11:30:38 -0400 From: "Moriarty, Kathleen" To: Lisandro Zambenedetti Granville , "codematch-develop@ietf.org" Thread-Topic: [Codematch-develop] IETF 92 presentation Thread-Index: AQHQXATFRUOST35tNUGhvzjMKig4Y50XaC1Q Date: Wed, 11 Mar 2015 15:30:38 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.250.132.84] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com X-RSA-Classifications: DLM_1, public Archived-At: Subject: Re: [Codematch-develop] IETF 92 presentation X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 15:31:00 -0000 Hi Lisandro,=0A= =0A= Thank you1 The slides look great. I'll pull together intro slides and try= to frame them in a way that answers the questions I am asked most frequent= ly so we set the stage well for your overview of the prototype. I'll have = this done before our call next week, but hopefully sooner.=0A= =0A= Thanks,=0A= Kathleen=0A= ________________________________________=0A= From: Codematch-develop [codematch-develop-bounces@ietf.org] on behalf of L= isandro Zambenedetti Granville [granville@inf.ufrgs.br]=0A= Sent: Wednesday, March 11, 2015 10:06 AM=0A= To: codematch-develop@ietf.org=0A= Subject: [Codematch-develop] IETF 92 presentation=0A= =0A= Dear all=0A= =0A= I created a Power Point presentation for the upcoming IETF 92. It=92s a ver= y first draft of it, to discuss with you. I uploaded the power point file i= n out shared folder in Google Drive:=0A= =0A= https://drive.google.com/folderview?id=3D0B-dir4eV4Ih1V2tQSDdNRndrdGc&usp= =3Dsharing=0A= =0A= File name: IETF 92 Presentation.pptx=0A= =0A= This time, I didn=92t convert it to Google Driver presentation format, keep= ing the original Power Point format: it=92s then easier for us to edit it.= =0A= =0A= Is today=92s meeting confirmed?=0A= =0A= Best regards,=0A= =0A= Lisandro=0A= _______________________________________________=0A= Codematch-develop mailing list=0A= Codematch-develop@ietf.org=0A= https://www.ietf.org/mailman/listinfo/codematch-develop=0A= From nobody Wed Mar 11 08:42:36 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7371A0037 for ; Wed, 11 Mar 2015 08:42:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 CK-NdkaLaRf6 for ; Wed, 11 Mar 2015 08:42:33 -0700 (PDT) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C70441A000D for ; Wed, 11 Mar 2015 08:42:32 -0700 (PDT) Received: by lbdu10 with SMTP id u10so9743030lbd.4 for ; Wed, 11 Mar 2015 08:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1Kd795rNAETUGzdesEHsOz4f9SfHAIu3crUVm4XG33Y=; b=AUJiCfRHESB6Si/AHNSALBgyVVQ+LLjonye3dVzlk0QN73VXnp4H9uqe0qFRlZt8Sv r9RPbmnXJQg2p+6IS7UFMUitsVTydEXPBJie7ev9pGWzhelaSNAKG2N+2jA5hPofiUpA TsIt6thi35/T7ykly/NUIaKmIIovJ69mBT8FXrHelEoz470lcJGjt/SD/xE631czk1Bd 3zRCdDwnmWEttCnLMyMbptY8M0eC9YtFY3jcZQxVK+W1/cNGxWh5IWGFJ44hXDokrzFv 2Omwy/h3LwrV1LAdyZWoItmRpkfpdzK/hUUjqp2zG++HEfLIfZ2suLNZEPEtQWWrvUNU cKvg== MIME-Version: 1.0 X-Received: by 10.152.116.65 with SMTP id ju1mr14922467lab.32.1426088551251; Wed, 11 Mar 2015 08:42:31 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Wed, 11 Mar 2015 08:42:31 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Mar 2015 11:42:31 -0400 Message-ID: From: Kathleen Moriarty To: "Moriarty, Kathleen" Content-Type: multipart/alternative; boundary=001a11c3556c8403420511051dbb Archived-At: Cc: Lisandro Zambenedetti Granville , "codematch-develop@ietf.org" Subject: Re: [Codematch-develop] IETF 92 presentation X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 15:42:35 -0000 --001a11c3556c8403420511051dbb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes, I do plan to join the call today. I think Kristin can't make it, but a short call may be helpful to prep for IETF week. Thanks! On Wed, Mar 11, 2015 at 11:30 AM, Moriarty, Kathleen < kathleen.moriarty@emc.com> wrote: > Hi Lisandro, > > Thank you1 The slides look great. I'll pull together intro slides and > try to frame them in a way that answers the questions I am asked most > frequently so we set the stage well for your overview of the prototype. > I'll have this done before our call next week, but hopefully sooner. > > Thanks, > Kathleen > ________________________________________ > From: Codematch-develop [codematch-develop-bounces@ietf.org] on behalf of > Lisandro Zambenedetti Granville [granville@inf.ufrgs.br] > Sent: Wednesday, March 11, 2015 10:06 AM > To: codematch-develop@ietf.org > Subject: [Codematch-develop] IETF 92 presentation > > Dear all > > I created a Power Point presentation for the upcoming IETF 92. It=E2=80= =99s a very > first draft of it, to discuss with you. I uploaded the power point file i= n > out shared folder in Google Drive: > > > https://drive.google.com/folderview?id=3D0B-dir4eV4Ih1V2tQSDdNRndrdGc&usp= =3Dsharing > > File name: IETF 92 Presentation.pptx > > This time, I didn=E2=80=99t convert it to Google Driver presentation form= at, > keeping the original Power Point format: it=E2=80=99s then easier for us = to edit it. > > Is today=E2=80=99s meeting confirmed? > > Best regards, > > Lisandro > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > --=20 Best regards, Kathleen --001a11c3556c8403420511051dbb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, I do plan to join the call today.=C2=A0 I think Krist= in can't make it, but a short call may be helpful to prep for IETF week= .

Thanks!

On Wed, Mar 11, 2015 at 11:30 AM, Moriarty, Kathleen= <kathleen.moriarty@emc.com> wrote:
Hi Lisandro,

Thank you1=C2=A0 The slides look great.=C2=A0 I'll pull together intro = slides and try to frame them in a way that answers the questions I am asked= most frequently so we set the stage well for your overview of the prototyp= e.=C2=A0 I'll have this done before our call next week, but hopefully s= ooner.

Thanks,
Kathleen
________________________________________
From: Codematch-develop [codematch-develop-bounces@ietf.org] on behalf of Lisandro Zambenede= tti Granville [granville@inf.ufrg= s.br]
Sent: Wednesday, March 11, 2015 10:06 AM
To: codematch-develop@ietf.or= g
Subject: [Codematch-develop] IETF 92 presentation

Dear all

I created a Power Point presentation for the upcoming IETF 92. It=E2=80=99s= a very first draft of it, to discuss with you. I uploaded the power point = file in out shared folder in Google Drive:

https://drive.google.com/folderv= iew?id=3D0B-dir4eV4Ih1V2tQSDdNRndrdGc&usp=3Dsharing

File name: IETF 92 Presentation.pptx

This time, I didn=E2=80=99t convert it to Google Driver presentation format= , keeping the original Power Point format: it=E2=80=99s then easier for us = to edit it.

Is today=E2=80=99s meeting confirmed?

Best regards,

Lisandro
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop

_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop



--
=

Best regards,
Kathleen
--001a11c3556c8403420511051dbb-- From nobody Wed Mar 11 13:13:07 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A72D1A854D for ; Wed, 11 Mar 2015 13:13:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 H4b043QHW7Kn for ; Wed, 11 Mar 2015 13:13:03 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0695.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:695]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECF291A6FEF for ; Wed, 11 Mar 2015 13:13:02 -0700 (PDT) Received: from BLUPR0601MB770.namprd06.prod.outlook.com (10.141.254.139) by BLUPR0601MB772.namprd06.prod.outlook.com (10.141.254.140) with Microsoft SMTP Server (TLS) id 15.1.99.14; Wed, 11 Mar 2015 20:12:41 +0000 Received: from BLUPR0601MB770.namprd06.prod.outlook.com ([10.141.254.139]) by BLUPR0601MB770.namprd06.prod.outlook.com ([10.141.254.139]) with mapi id 15.01.0099.004; Wed, 11 Mar 2015 20:12:41 +0000 From: Christian O'Flaherty To: "codematch-develop@ietf.org" Thread-Topic: Goals for Kathleen "Slide" Thread-Index: AQHQXDe5yQmOSYal4022HN0m9Ss9vg== Date: Wed, 11 Mar 2015 20:12:40 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [200.7.87.87] authentication-results: ietf.org; dkim=none (message not signed) header.d=none; x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0601MB772; x-forefront-antispam-report: BMV:0; SFV:NSPM; SFS:(10009020)(6009001)(53754006)(92566002)(2501003)(77096005)(66066001)(99286002)(110136001)(87936001)(107886001)(2656002)(2351001)(36756003)(16236675004)(50986999)(122556002)(2900100001)(77156002)(102836002)(46102003)(40100003)(106116001)(54356999)(86362001)(229853001)(62966003)(450100001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR0601MB772; H:BLUPR0601MB770.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5001009)(5005006); SRVR:BLUPR0601MB772; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0601MB772; x-forefront-prvs: 0512CC5201 Content-Type: multipart/alternative; boundary="_000_D125EECE460FCoflahertyisocorg_" MIME-Version: 1.0 X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2015 20:12:40.7858 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0601MB772 Archived-At: Subject: [Codematch-develop] Goals for Kathleen "Slide" X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 20:13:05 -0000 --_000_D125EECE460FCoflahertyisocorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, On our call I suggested to share a list of "goals" that each of us have in = mind, which will help Kathleen to populate the slide for codematch goals. For us in LAC codematch will help as: a vehicle to engage with Universities a vehicle to engage with open source groups a source of topics to work on and report (events, task forces, call for pap= ers, researchers, etc.) An opportunity for people looking for jobs to become known A low barrier entry point to the IETF Christian --_000_D125EECE460FCoflahertyisocorg_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <8978A71A1D905F42995D15C0F1979CDE@namprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Hi all,

On our call I suggested to share a list of “goals” that ea= ch of us have in mind, which will help Kathleen to populate the slide for c= odematch  goals. 

For us in LAC codematch will help as:
a = ;vehicle to engage with Universities
a&nb= sp;vehicle to engage with open source groups 
a sour= ce of topics to work on and report (events, task forces, call for papers, r= esearchers, etc.)    
An o= pportunity for people looking for jobs to become known
A low = barrier entry point to the IETF

Christian

--_000_D125EECE460FCoflahertyisocorg_-- From nobody Wed Mar 11 16:13:48 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2AFF1A891D for ; Wed, 11 Mar 2015 16:13:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.599 X-Spam-Level: X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 NoL6rCzTj9hT for ; Wed, 11 Mar 2015 16:13:45 -0700 (PDT) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B911A870C for ; Wed, 11 Mar 2015 16:13:44 -0700 (PDT) Received: by labgd6 with SMTP id gd6so12202607lab.3 for ; Wed, 11 Mar 2015 16:13:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UlLHoMESJ4lq1hN2BND/9Ca8T9W/STvByT1pnp+BwNY=; b=KKh6ak4a9Cd50Xfv5GBhe/Vcu57mM7MwbVh47LPv6y6v/BZIC82fOTxvlmOXd2SAsA qGIwe94XPzqv+SqWyWIiTisqvCWjZ3RwQa3pd0+Lqqkl925+7ByZ5auwBF/JyB5n198A fE8646/SRGPtRkUOnAJZNyOcdPV+zusqCI27H/Tva+MT7tx+yF8JqUqFRVu3h94X138I 1meeJqJ9rNENdZL8enIxF/ohMTcAcpeInP4Deujksollx8b/zT65t9kv62To9fBPVGAO f3gTJrD83ROnRM7QKKLB0WNkThSLq3WtPsnd0pxyI9zswctJEH9wqlQKXsF7D8jxMVjt 7Fgw== MIME-Version: 1.0 X-Received: by 10.152.179.68 with SMTP id de4mr22300921lac.65.1426115623270; Wed, 11 Mar 2015 16:13:43 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Wed, 11 Mar 2015 16:13:43 -0700 (PDT) Date: Wed, 11 Mar 2015 19:13:43 -0400 Message-ID: From: Kathleen Moriarty To: "codematch-develop@ietf.org" Content-Type: multipart/alternative; boundary=001a11342ef2223dfe05110b6ba2 Archived-At: Subject: [Codematch-develop] Meeting times during IETF week X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 23:13:46 -0000 --001a11342ef2223dfe05110b6ba2 Content-Type: text/plain; charset=UTF-8 Hi team, I have a very booked schedule this meeting. There are a couple of possibilities for me, which mean skipping a session, but I'd like us to make progress. Would either of the following times work for everyone: Thursday between 9-11:30, maybe we could meet at 10 or 10:30 and I'd attend the first part of a session OR Thursday 15:20-17:20 If neither of those work, I think I may be into dinner times and will have to figure out what I have open still. Thank you! -- Best regards, Kathleen --001a11342ef2223dfe05110b6ba2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi team,

I have a very booked schedule = this meeting.=C2=A0 There are a couple of possibilities for me, which mean = skipping a session, but I'd like us to make progress.

Would either of the following times work for everyone:
Th= ursday between 9-11:30, maybe we could meet at 10 or 10:30 and I'd atte= nd the first part of a session

OR

Thursday 15:20-17:20

If neither of those = work, I think I may be into dinner times and will have to figure out what I= have open still.

Thank you!

--

Best re= gards,
Kathleen
--001a11342ef2223dfe05110b6ba2-- From nobody Thu Mar 12 05:19:14 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C74581A00A2 for ; Thu, 12 Mar 2015 05:19:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 0F-w181SPrlb for ; Thu, 12 Mar 2015 05:19:04 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0620.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:620]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399B61A008F for ; Thu, 12 Mar 2015 05:18:47 -0700 (PDT) Received: from [10.0.0.6] (24.61.221.93) by BY1PR0601MB1372.namprd06.prod.outlook.com (25.162.111.150) with Microsoft SMTP Server (TLS) id 15.1.106.15; Thu, 12 Mar 2015 12:18:26 +0000 From: Toral Cowieson Content-Type: multipart/alternative; boundary="Apple-Mail=_C93F2512-6FAC-4871-9694-CE0BC5C062F4" Message-ID: MIME-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Date: Thu, 12 Mar 2015 08:18:24 -0400 References: To: "codematch-develop@ietf.org" In-Reply-To: X-Mailer: Apple Mail (2.1510) X-Originating-IP: [24.61.221.93] X-ClientProxiedBy: BN3PR09CA0009.namprd09.prod.outlook.com (25.160.111.147) To BY1PR0601MB1372.namprd06.prod.outlook.com (25.162.111.150) Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0601MB1372; X-Forefront-Antispam-Report: BMV:1; SFV:NSPM; SFS:(10009020)(6049001)(51704005)(24454002)(377454003)(53754006)(82746002)(110136001)(2950100001)(19580395003)(77156002)(15395725005)(2351001)(69556001)(66066001)(19617315012)(107886001)(19580405001)(92566002)(42186005)(76176999)(50986999)(87976001)(40100003)(512954002)(83716003)(122386002)(1720100001)(86362001)(62966003)(77096005)(50226001)(46102003)(57306001)(33656002)(84326002)(15975445007)(36756003)(16236675004)(2501003)(450100001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY1PR0601MB1372; H:[10.0.0.6]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:BY1PR0601MB1372; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0601MB1372; X-Forefront-PRVS: 05134F8B4F X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Mar 2015 12:18:26.9153 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0601MB1372 Archived-At: Subject: Re: [Codematch-develop] Meeting times during IETF week X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 12:19:10 -0000 --Apple-Mail=_C93F2512-6FAC-4871-9694-CE0BC5C062F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Hi All, Based on Kathleen's availability, here's a Doodle poll to see what works = for the team to have a CodeMatch meeting during IETF week. Please note both options are local times in Dallas for Thursday, 26 = March (10:30-11:30 and 15:30-16:30) http://doodle.com/6xn4itearax7ccze Best regards, Toral On Mar 11, 2015, at 7:13 PM, Kathleen Moriarty = wrote: > Hi team, >=20 > I have a very booked schedule this meeting. There are a couple of = possibilities for me, which mean skipping a session, but I'd like us to = make progress. >=20 > Would either of the following times work for everyone: > Thursday between 9-11:30, maybe we could meet at 10 or 10:30 and I'd = attend the first part of a session >=20 > OR >=20 > Thursday 15:20-17:20 >=20 > If neither of those work, I think I may be into dinner times and will = have to figure out what I have open still. >=20 > Thank you! >=20 > --=20 >=20 > Best regards, > Kathleen > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop --Apple-Mail=_C93F2512-6FAC-4871-9694-CE0BC5C062F4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" http://doodle.com/6xn4itearax7= ccze

Best regards,
Toral


On Mar 11, 2015, at 7:13 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gm= ail.com> wrote:

Hi team,

I have a very booked schedule = this meeting.  There are a couple of possibilities for me, which = mean skipping a session, but I'd like us to make = progress.

Would either of the following times = work for everyone:
Thursday between 9-11:30, maybe we could = meet at 10 or 10:30 and I'd attend the first part of a = session

OR

Thursday = 15:20-17:20

If neither of those work, I think I = may be into dinner times and will have to figure out what I have open = still.

Thank you!

-- =

Best = regards,
Kathleen
_______________________________________________
Codematch-develop = mailing list
Codematch-develop@ietf.org<= br>https://www.ietf.org/mailman/listinfo/codematch-develop

= --Apple-Mail=_C93F2512-6FAC-4871-9694-CE0BC5C062F4-- From nobody Tue Mar 17 10:54:39 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4050C1A87AA for ; Tue, 17 Mar 2015 10:54:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 bM5lWlxl19VY for ; Tue, 17 Mar 2015 10:54:27 -0700 (PDT) Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 923671A87E8 for ; Tue, 17 Mar 2015 10:54:26 -0700 (PDT) Received: by ladw1 with SMTP id w1so15530561lad.0 for ; Tue, 17 Mar 2015 10:54:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=R2xxoTtGf4mjNY09rtSM89aLaH12goKpgkzfNlW4MQg=; b=NyoBh6F6rXvYJ3MKzjFhgZqawy1Bf0Mh6vwIcjsocZoty45G/q6elg/Ypx7iXHyaoM 7Xe9sJuhVNnjEnMbWrs8xiimXqI5w2Dpi+vGLSxmXcVacX+vkJCJ1vKISLs/udP7IHIO Y4axJPH8G7Pht52GcIeJhf6bnEoQKAmNJITbG0dAul2a5n8zweiLvJLwGj0Ud/Y1sYJV GwUsOM7AtsDhCTWpcKL4dvqy7KZKqIEW/+H9ZIA0+Pepws7n1o7xP06zO7Ex+dKuxifA omcyG6wqqgbKa1GEexa1Q29LIFM/BfvAm0Rjj+mC8pJKq1CrnMax2RRQhH1K65F2OGOl EGtA== MIME-Version: 1.0 X-Received: by 10.152.37.202 with SMTP id a10mr20247478lak.0.1426614865073; Tue, 17 Mar 2015 10:54:25 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Tue, 17 Mar 2015 10:54:25 -0700 (PDT) Date: Tue, 17 Mar 2015 13:54:25 -0400 Message-ID: From: Kathleen Moriarty To: "codematch-develop@ietf.org" Content-Type: multipart/alternative; boundary=089e01494056439aa005117fa84f Archived-At: Subject: [Codematch-develop] Meeting times at IETF92 X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 17:54:30 -0000 --089e01494056439aa005117fa84f Content-Type: text/plain; charset=UTF-8 Hello, If you have not filled out the doodle poll on times to meet during IETF 92, please do so! If these times don't work, I think I still have Monday dinner open. We'll need to book a room to meet, so please respond as soon as possible. http://doodle.com/6xn4itearax7ccze#table We should be able to start coding soon and want your help! -- Best regards, Kathleen --089e01494056439aa005117fa84f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

If you have not filled out the d= oodle poll on times to meet during IETF 92, please do so!=C2=A0 If these ti= mes don't work, I think I still have Monday dinner open.

=
We'll need to book a room to meet, so please respond as soon= as possible.

We should be able to start coding soon and want your help!

--

Best regards,
Kathleen
--089e01494056439aa005117fa84f-- From nobody Tue Mar 17 12:31:41 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D43271A88AD for ; Tue, 17 Mar 2015 12:31:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 m1Q1GarKrtMf for ; Tue, 17 Mar 2015 12:31:38 -0700 (PDT) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4019E1A88AB for ; Tue, 17 Mar 2015 12:31:38 -0700 (PDT) Received: by ladw1 with SMTP id w1so17830034lad.0 for ; Tue, 17 Mar 2015 12:31:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=K2+PUkOH4tOoMzaHobga55Wi0QZMegbcFuQMKwHRMMw=; b=LgNSOwO4N4DuojsQIVRvR5FMjV1Q36RxjblFaQ5C4gA88mkPoRmrbYceCSTe4VgLnk 5mXoPDK5lJ6Ef2u9aaqFzEg9L8x3sUgRPfw2niG7dhqxrXlAIIgUkRyLLNoshWqLhmJD hVBjE/frE90xMHvD8nIirJOFwBiSqzGRAXdW7lZAJtPJpOimFtsWWpYd+UA+jlt2PbBl hvrkL4zB17O1syfphL/lWImYsB15cdb1wBdmp5MBvHSulhsqe/wfUjE8cYEs20bZ+dVY j0ZWOY6HrAiNQp+8CCTEkYXO63AbNrmfUA/UtTKvycMz639DsAT91CVIojKmTLLJpcR+ 8YCQ== MIME-Version: 1.0 X-Received: by 10.152.37.202 with SMTP id a10mr20589747lak.0.1426620696782; Tue, 17 Mar 2015 12:31:36 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Tue, 17 Mar 2015 12:31:36 -0700 (PDT) Date: Tue, 17 Mar 2015 15:31:36 -0400 Message-ID: From: Kathleen Moriarty To: "codematch-develop@ietf.org" Content-Type: multipart/alternative; boundary=089e01494056dc6fc705118103c8 Archived-At: Subject: [Codematch-develop] Slides for Administrative Plenary X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 19:31:40 -0000 --089e01494056dc6fc705118103c8 Content-Type: text/plain; charset=UTF-8 Hello, I just added a few slides to the presentation Lisandro started for the IETF Administrative plenary. Please take a few minutes to review and comment. Also please let me know if I inadvertently left off anyones name that should be acknowledged as part of the team. https://docs.google.com/presentation/d/1Hhf3LvqEd8o4JEuH1cLPO7gNsoaE_VLM5JJPh4P_5fQ/edit#slide=id.p3 We'll review the slides on tomorrow's call as well. Thank you! -- Best regards, Kathleen --089e01494056dc6fc705118103c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I just added a few slides to the= presentation Lisandro started for the IETF Administrative plenary.=C2=A0 P= lease take a few minutes to review and comment.

Al= so please let me know if I inadvertently left off anyones name that should = be acknowledged as part of the team.

<= a href=3D"https://docs.google.com/presentation/d/1Hhf3LvqEd8o4JEuH1cLPO7gNs= oaE_VLM5JJPh4P_5fQ/edit#slide=3Did.p3">https://docs.google.com/presentation= /d/1Hhf3LvqEd8o4JEuH1cLPO7gNsoaE_VLM5JJPh4P_5fQ/edit#slide=3Did.p3
<= /div>

We'll review the slides on tomorrow's call= as well.

Thank you!
--

Best regards,
Kathleen
--089e01494056dc6fc705118103c8-- From nobody Tue Mar 17 13:14:01 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 939931A88BE for ; Tue, 17 Mar 2015 13:14:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.96 X-Spam-Level: X-Spam-Status: No, score=-1.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 G63zf3CyPpcT for ; Tue, 17 Mar 2015 13:13:58 -0700 (PDT) Received: from delivery2.ufrgs.br (delivery2.ufrgs.br [143.54.2.212]) by ietfa.amsl.com (Postfix) with ESMTP id 791411A88DC for ; Tue, 17 Mar 2015 13:13:57 -0700 (PDT) Received: from delivery2.ufrgs.br (localhost [127.0.0.1]) by delivery2.ufrgs.br (Postfix) with ESMTP id B456A20A3C5; Tue, 17 Mar 2015 17:13:54 -0300 (BRT) Received: from msa1.ufrgs.br (msa1.ufrgs.br [143.54.2.208]) by delivery2.ufrgs.br (Postfix) with ESMTP id 82D013007AA; Tue, 17 Mar 2015 17:13:54 -0300 (BRT) Content-Type: multipart/alternative; boundary="Apple-Mail=_DA03190D-44B2-415E-B4D6-7BC5B0B0495D" Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Lisandro Zambenedetti Granville In-Reply-To: Date: Tue, 17 Mar 2015 17:13:42 -0300 Message-Id: <3B2061DD-82A6-4968-9192-31A2405DB1EE@inf.ufrgs.br> References: To: Kathleen Moriarty X-Mailer: Apple Mail (2.2070.6) X-AV-Checked: ClamAV using ClamSMTP Archived-At: Cc: "codematch-develop@ietf.org" Subject: Re: [Codematch-develop] Slides for Administrative Plenary X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 20:14:00 -0000 --Apple-Mail=_DA03190D-44B2-415E-B4D6-7BC5B0B0495D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello Kathleen, I=E2=80=99ve included Wanderson=E2=80=99s name in the list. He coded the = current prototype. Lisandro > Em 17/03/2015, =C3=A0(s) 16:31, Kathleen Moriarty = escreveu: >=20 > Hello, >=20 > I just added a few slides to the presentation Lisandro started for the = IETF Administrative plenary. Please take a few minutes to review and = comment. >=20 > Also please let me know if I inadvertently left off anyones name that = should be acknowledged as part of the team. >=20 > = https://docs.google.com/presentation/d/1Hhf3LvqEd8o4JEuH1cLPO7gNsoaE_VLM5J= JPh4P_5fQ/edit#slide=3Did.p3 = >=20 > We'll review the slides on tomorrow's call as well. >=20 > Thank you! > --=20 >=20 > Best regards, > Kathleen > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop --Apple-Mail=_DA03190D-44B2-415E-B4D6-7BC5B0B0495D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hello Kathleen,

I=E2=80=99ve included Wanderson=E2=80=99s name in the = list. He coded the current prototype.

Lisandro

Em 17/03/2015, =C3=A0(s) 16:31, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> escreveu:

Hello,

I = just added a few slides to the presentation Lisandro started for the = IETF Administrative plenary.  Please take a few minutes to review = and comment.

Also please let me know if I inadvertently left off anyones = name that should be acknowledged as part of the team.

https://docs.google.com/presentation/d/1Hhf3LvqEd8o4JEuH1cLPO7g= NsoaE_VLM5JJPh4P_5fQ/edit#slide=3Did.p3

We'll review the slides = on tomorrow's call as well.

Thank you!
--

Best regards,
Kathleen
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop

= --Apple-Mail=_DA03190D-44B2-415E-B4D6-7BC5B0B0495D-- From nobody Tue Mar 17 13:18:45 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDC7B1A88DE for ; Tue, 17 Mar 2015 13:18:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham 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 i0bvikRIsUGj for ; Tue, 17 Mar 2015 13:18:43 -0700 (PDT) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F19A31A88CF for ; Tue, 17 Mar 2015 13:18:42 -0700 (PDT) Received: by qgf3 with SMTP id 3so19305441qgf.3 for ; Tue, 17 Mar 2015 13:18:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tS3aG+kzcIZJKTEdkpsdYJfLf4TqlCMjwfu7le1iaxc=; b=HIJUqQfJHWmUWP0bGfFJElsRZjsDps8rdFXN0ysWL9j0GXFKcaRAHUDCnfadZ0nqHU s7RiBiJnbXA9QE8NxnjkrRsROXXDrqQAWspWxAIkPhpmfNNsR1xD9BMtklTUEpotBbTt ESyuBZLUrnzBDTCbvKswWl2eSwk+YxwJUa2jjPuO64De34QuXNnfvV5zUOXbAJj4J42k pOMACrZcoaXYjv37eKtmfQ+PH0vkKirAaH9EpV4Wxo9kXmkv+ca+4TheahfT4N3pjRGj /Vu/m2VLtxpuoQAdTb2iJTJdyx1N75vMewZppQQYUnLt9zrKTBekacy1eFBq54uyXcb2 qxVA== X-Received: by 10.140.25.208 with SMTP id 74mr81569736qgt.58.1426623522216; Tue, 17 Mar 2015 13:18:42 -0700 (PDT) Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id l49sm10385770qgd.21.2015.03.17.13.18.40 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Mar 2015 13:18:41 -0700 (PDT) From: Kathleen Moriarty X-Google-Original-From: Kathleen Moriarty Content-Type: multipart/alternative; boundary=Apple-Mail-EBBA9F59-1F4E-4725-B34B-7231055F0987 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (11D257) In-Reply-To: <3B2061DD-82A6-4968-9192-31A2405DB1EE@inf.ufrgs.br> Date: Tue, 17 Mar 2015 16:18:41 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: <3B2061DD-82A6-4968-9192-31A2405DB1EE@inf.ufrgs.br> To: Lisandro Zambenedetti Granville Archived-At: Cc: "codematch-develop@ietf.org" Subject: Re: [Codematch-develop] Slides for Administrative Plenary X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 20:18:45 -0000 --Apple-Mail-EBBA9F59-1F4E-4725-B34B-7231055F0987 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thank you, Lisandro! Sorry for my oversight, Wanderson! Sent from my iPhone > On Mar 17, 2015, at 4:13 PM, Lisandro Zambenedetti Granville wrote: >=20 > Hello Kathleen, >=20 > I=E2=80=99ve included Wanderson=E2=80=99s name in the list. He coded the c= urrent prototype. >=20 > Lisandro >=20 >> Em 17/03/2015, =C3=A0(s) 16:31, Kathleen Moriarty escreveu: >>=20 >> Hello, >>=20 >> I just added a few slides to the presentation Lisandro started for the IE= TF Administrative plenary. Please take a few minutes to review and comment.= >>=20 >> Also please let me know if I inadvertently left off anyones name that sho= uld be acknowledged as part of the team. >>=20 >> https://docs.google.com/presentation/d/1Hhf3LvqEd8o4JEuH1cLPO7gNsoaE_VLM5= JJPh4P_5fQ/edit#slide=3Did.p3 >>=20 >> We'll review the slides on tomorrow's call as well. >>=20 >> Thank you! >> --=20 >>=20 >> Best regards, >> Kathleen >> _______________________________________________ >> Codematch-develop mailing list >> Codematch-develop@ietf.org >> https://www.ietf.org/mailman/listinfo/codematch-develop >=20 --Apple-Mail-EBBA9F59-1F4E-4725-B34B-7231055F0987 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Thank you, Lisandro!

Sorry for my oversight, Wanderson!

Sent from my iPhone
<= div>
On Mar 17, 2015, at 4:13 PM, Lisandro Zambenedetti Granville <granville@inf.ufrgs.br> wrote:<= br>
Hello Kathleen,

I=E2=80=99ve included Wanderson=E2=80=99= s name in the list. He coded the current prototype.

Lisandro

Em 17= /03/2015, =C3=A0(s) 16:31, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>= escreveu:

Hello,

I just added a few slides to the presentation Lisandro started for th= e IETF Administrative plenary.  Please take a few minutes to review and= comment.

Also ple= ase let me know if I inadvertently left off anyones name that should be ackn= owledged as part of the team.
https://docs.google.com/presentation/d/1Hhf3LvqEd8o4JEuH1cLPO7gNsoa= E_VLM5JJPh4P_5fQ/edit#slide=3Did.p3
=
We'll review the slides on tomorrow's c= all as well.

Thank= you!
--

Best regards,
Kathleen
_______________________________________________
Codematch-deve= lop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailma= n/listinfo/codematch-develop

= --Apple-Mail-EBBA9F59-1F4E-4725-B34B-7231055F0987-- From nobody Mon Mar 23 12:16:21 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F22381AD49F for ; Mon, 23 Mar 2015 12:16:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 xTY2gMIh29dy for ; Mon, 23 Mar 2015 12:16:19 -0700 (PDT) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D924F1AD47E for ; Mon, 23 Mar 2015 12:16:18 -0700 (PDT) Received: by laae1 with SMTP id e1so10161293laa.2 for ; Mon, 23 Mar 2015 12:16:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A0ikJtokvu32Tw+fltiFvfzpf0CyBBSzZC2wrA4QXFI=; b=RXvlsVZGObqyFvnFz7BcOcV3Sahl4MHpSmbPcvkI8K+5AFRpzFzz0R3viN4FLjYifH uZCih5KNvVpFI12LgowyKBRTKnA+BHD/+XwEjXx+UAzvCEv+H3pKhUHLzgA/rLkcYxlm qRIkyWrtRaNYV13m0Qx4m04p9RdKMF3oXGDyVZx+K883FEqxFovWeszgQBspRYuQkPx2 8HOJAbMeEgQ/y6YhViwzPwv+Cm68o3AQRFStKK0qmICqnEgmPiASS1/cIj3gIsLlQ/4V IeIlH8HKd3dlYL809rYcfvN2D7ubpjo/qfxMPS+C43Fi1Wkftm7jd00qB6zRVjoEw1Y4 CQ8Q== MIME-Version: 1.0 X-Received: by 10.152.42.171 with SMTP id p11mr461149lal.75.1427138177352; Mon, 23 Mar 2015 12:16:17 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Mon, 23 Mar 2015 12:16:17 -0700 (PDT) Date: Mon, 23 Mar 2015 15:16:17 -0400 Message-ID: From: Kathleen Moriarty To: "codematch-develop@ietf.org" Content-Type: multipart/alternative; boundary=001a11c356561b4b8f0511f98094 Archived-At: Subject: [Codematch-develop] Thursday meeting at IETF X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 19:16:21 -0000 --001a11c356561b4b8f0511f98094 Content-Type: text/plain; charset=UTF-8 Hi, If you haven't responded on the Doodle poll with your choice of meeting times, please do. Right now, it looks like we will be meeting 3:30-4:30PM. http://doodle.com/6xn4itearax7ccze#table Thanks. -- Best regards, Kathleen --001a11c356561b4b8f0511f98094 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

If you haven't responded on the= Doodle poll with your choice of meeting times, please do.=C2=A0 Right now,= it looks like we will be meeting 3:30-4:30PM.


Thanks.
=
--

B= est regards,
Kathleen
--001a11c356561b4b8f0511f98094-- From nobody Mon Mar 23 12:53:20 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D09D1A037A for ; Mon, 23 Mar 2015 12:53:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 3hDYggLvZ5v8 for ; Mon, 23 Mar 2015 12:53:17 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0626.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::626]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E48991A034F for ; Mon, 23 Mar 2015 12:53:16 -0700 (PDT) Received: from dhcp-a4f9.meeting.ietf.org (31.133.164.249) by DM2PR0601MB780.namprd06.prod.outlook.com (10.242.173.140) with Microsoft SMTP Server (TLS) id 15.1.118.21; Mon, 23 Mar 2015 19:52:59 +0000 MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_E1C8BCB7-EFB7-4142-BAD5-8BEA9E99F341" From: Christian O'Flaherty In-Reply-To: Date: Mon, 23 Mar 2015 14:52:44 -0500 Message-ID: <98FCC2C9-BDA9-4D81-BA95-C8C30CFF2D67@isoc.org> References: To: Kathleen Moriarty X-Mailer: Apple Mail (2.2070.6) X-Originating-IP: [31.133.164.249] X-ClientProxiedBy: AM3PR04CA0049.eurprd04.prod.outlook.com (10.242.16.49) To DM2PR0601MB780.namprd06.prod.outlook.com (10.242.173.140) Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB780; X-Microsoft-Antispam-PRVS: X-Forefront-Antispam-Report: BMV:1; SFV:NSPM; SFS:(10009020)(24454002)(51704005)(39224004)(377454003)(66066001)(15395725005)(62966003)(69556001)(87976001)(57306001)(82746002)(19580405001)(15975445007)(77096005)(42186005)(2950100001)(83716003)(92566002)(77156002)(86362001)(19580395003)(84326002)(50986999)(50226001)(76176999)(33656002)(512954002)(46102003)(106356001)(110136001)(40100003)(36756003)(19617315012)(122386002)(7099025)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB780; H:dhcp-a4f9.meeting.ietf.org; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:DM2PR0601MB780; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB780; X-Forefront-PRVS: 05245CA661 X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Mar 2015 19:52:59.0352 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB780 Archived-At: Cc: "codematch-develop@ietf.org" Subject: Re: [Codematch-develop] Thursday meeting at IETF X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 19:53:19 -0000 --Apple-Mail=_E1C8BCB7-EFB7-4142-BAD5-8BEA9E99F341 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Do we have a meeting room? (sorry if it was discussed before, but I = couldn't found it in my emails) Christian O'Flaherty - oflaherty@isoc.org Regional Development - Internet Society=20 Skype/Gmail/Yahoo!: christian.oflaherty=20 Phone: +598 98769636 > On Mar 23, 2015, at 2:16 PM, Kathleen Moriarty = wrote: >=20 > Hi, >=20 > If you haven't responded on the Doodle poll with your choice of = meeting times, please do. Right now, it looks like we will be meeting = 3:30-4:30PM. >=20 > http://doodle.com/6xn4itearax7ccze#table = >=20 > Thanks. >=20 > --=20 >=20 > Best regards, > Kathleen > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop --Apple-Mail=_E1C8BCB7-EFB7-4142-BAD5-8BEA9E99F341 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" Do we have a meeting room? (sorry if it was discussed before, = but I couldn't found it in my emails)

Christian O'Flaherty - oflaherty@isoc.org
Regional Development - Internet Society 
Skype/Gmail/Yahoo!:  christian.oflaherty 
Phone: +598 98769636

On Mar 23, 2015, at 2:16 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:

Hi,

If you haven't responded on the Doodle = poll with your choice of meeting times, please do.  Right now, it = looks like we will be meeting 3:30-4:30PM.

http://doodle.com/6xn4itearax7ccze#table

Thanks.

--

Best regards,
Kathleen
_______________________________________________
Codematch-develop mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop

= --Apple-Mail=_E1C8BCB7-EFB7-4142-BAD5-8BEA9E99F341-- From nobody Mon Mar 23 12:53:55 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7641A0395 for ; Mon, 23 Mar 2015 12:53:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 ABJnl335TY_Z for ; Mon, 23 Mar 2015 12:53:52 -0700 (PDT) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A40B31A037A for ; Mon, 23 Mar 2015 12:53:51 -0700 (PDT) Received: by labe2 with SMTP id e2so67683197lab.3 for ; Mon, 23 Mar 2015 12:53:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sJqwWO3pAyHlhTBiIO55XeFL6WZWVs5DNl2WFN6eRDI=; b=PECNWg15cmqe9y0BHuVz1nVTtHsHzzZk62S2vz9d/yLz1+gx/EKEsBZB8Qfy1oyLvd UUdPRXA79GxH5t1z5GFh4cPdt2FlGj8T3n6w9pYb2YMcSzDWKKq2L50vVxq+cwSax2q/ fdmG3BndpkTxmNmzlSeWRzlvBO/a5fWv13252vJaPm2Y/34v5nJcBTCk31ZyTyiLSiNE wcJJcLEi1IqLG3PydX/8WC0zmLXJVDXa/3A//oHQ54D/jgNeUuyy1b+UiUmilzPLPPY9 +T95iXIZV7xZt8Xj0gJKIiXUndUp+l05Q8C1CqCg5h4pwjnqLQj8+C/i1f0W2r8s/g+3 D1Lw== MIME-Version: 1.0 X-Received: by 10.112.188.227 with SMTP id gd3mr807312lbc.0.1427140430150; Mon, 23 Mar 2015 12:53:50 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Mon, 23 Mar 2015 12:53:50 -0700 (PDT) In-Reply-To: <98FCC2C9-BDA9-4D81-BA95-C8C30CFF2D67@isoc.org> References: <98FCC2C9-BDA9-4D81-BA95-C8C30CFF2D67@isoc.org> Date: Mon, 23 Mar 2015 15:53:50 -0400 Message-ID: From: Kathleen Moriarty To: "Christian O'Flaherty" Content-Type: multipart/alternative; boundary=001a11c36aa862424c0511fa066d Archived-At: Cc: "codematch-develop@ietf.org" Subject: Re: [Codematch-develop] Thursday meeting at IETF X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 19:53:53 -0000 --001a11c36aa862424c0511fa066d Content-Type: text/plain; charset=UTF-8 Not yet, do you have one we could use? If not, we can request one. Thank you! On Mon, Mar 23, 2015 at 3:52 PM, Christian O'Flaherty wrote: > Do we have a meeting room? (sorry if it was discussed before, but I > couldn't found it in my emails) > > Christian O'Flaherty - oflaherty@isoc.org > Regional Development - Internet Society > Skype/Gmail/Yahoo!: christian.oflaherty > Phone: +598 98769636 > > On Mar 23, 2015, at 2:16 PM, Kathleen Moriarty < > kathleen.moriarty.ietf@gmail.com> wrote: > > Hi, > > If you haven't responded on the Doodle poll with your choice of meeting > times, please do. Right now, it looks like we will be meeting 3:30-4:30PM. > > http://doodle.com/6xn4itearax7ccze#table > > Thanks. > > -- > > Best regards, > Kathleen > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > -- Best regards, Kathleen --001a11c36aa862424c0511fa066d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Not yet, do you have one we could use?=C2=A0 If not, we ca= n request one.

Thank you!

On Mon, Mar 23, 2015 at 3:52 PM, Chr= istian O'Flaherty <oflaherty@isoc.org> wrote:
Do we have a m= eeting room? (sorry if it was discussed before, but I couldn't found it= in my emails)

Christ= ian O'Flaherty -=C2=A0oflaherty@isoc.org
Regional Development - Internet Society=C2= =A0
Skype/Gmail/Yahoo!: =C2=A0christian.oflaherty=C2=A0
Phone: +598 9= 8769636

On Mar 23, 2= 015, at 2:16 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> = wrote:

Hi= ,

If you haven't responded on the Doodle poll with y= our choice of meeting times, please do.=C2=A0 Right now, it looks like we w= ill be meeting 3:30-4:30PM.


Thanks.
<= br>
--

Best regards,
Kath= leen
_______________________________________________
Codematch-develop mailin= g list
C= odematch-develop@ietf.org
https://www.ietf.org/mailman/li= stinfo/codematch-develop




--

Best regards,
Kathleen=
--001a11c36aa862424c0511fa066d-- From nobody Mon Mar 23 12:57:39 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F2D1ACE6F for ; Mon, 23 Mar 2015 12:57:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 ei6ZddTSChLK for ; Mon, 23 Mar 2015 12:57:36 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0668.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::668]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA9731A0282 for ; Mon, 23 Mar 2015 12:57:32 -0700 (PDT) Received: from dhcp-8dc4.meeting.ietf.org (31.133.141.196) by CY1PR0601MB1375.namprd06.prod.outlook.com (25.163.21.149) with Microsoft SMTP Server (TLS) id 15.1.118.21; Mon, 23 Mar 2015 19:57:13 +0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_57E687E9-8493-436B-8A57-CAF67FF414AC" MIME-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Toral Cowieson In-Reply-To: Date: Mon, 23 Mar 2015 14:57:00 -0500 Message-ID: References: <98FCC2C9-BDA9-4D81-BA95-C8C30CFF2D67@isoc.org> To: Kathleen Moriarty X-Mailer: Apple Mail (2.1510) X-Originating-IP: [31.133.141.196] X-ClientProxiedBy: AM3PR06CA024.eurprd06.prod.outlook.com (10.141.192.142) To CY1PR0601MB1375.namprd06.prod.outlook.com (25.163.21.149) Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1375; X-Microsoft-Antispam-PRVS: X-Forefront-Antispam-Report: BMV:1; SFV:NSPM; SFS:(10009020)(24454002)(51704005)(39224004)(377454003)(52604005)(40100003)(62966003)(83716003)(122386002)(66066001)(50226001)(19580395003)(82746002)(110136001)(69556001)(42186005)(86362001)(46102003)(87976001)(19617315012)(50986999)(33656002)(84326002)(77156002)(19580405001)(15975445007)(16236675004)(15395725005)(2950100001)(36756003)(106356001)(92566002)(76176999)(512954002)(57306001)(7099025)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1375; H:dhcp-8dc4.meeting.ietf.org; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CY1PR0601MB1375; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1375; X-Forefront-PRVS: 05245CA661 X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Mar 2015 19:57:13.2462 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1375 Archived-At: Cc: "codematch-develop@ietf.org" , Christian O'Flaherty Subject: Re: [Codematch-develop] Thursday meeting at IETF X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 19:57:38 -0000 --Apple-Mail=_57E687E9-8493-436B-8A57-CAF67FF414AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Hi Christian and Kathleen, I'll close the Doodle poll Tuesday at noon local time and then send out = meeting room details to the group. =20 Thanks for checking. Toral On Mar 23, 2015, at 2:53 PM, Kathleen Moriarty = wrote: > Not yet, do you have one we could use? If not, we can request one. >=20 > Thank you! >=20 > On Mon, Mar 23, 2015 at 3:52 PM, Christian O'Flaherty = wrote: > Do we have a meeting room? (sorry if it was discussed before, but I = couldn't found it in my emails) >=20 > Christian O'Flaherty - oflaherty@isoc.org > Regional Development - Internet Society=20 > Skype/Gmail/Yahoo!: christian.oflaherty=20 > Phone: +598 98769636 >=20 >> On Mar 23, 2015, at 2:16 PM, Kathleen Moriarty = wrote: >>=20 >> Hi, >>=20 >> If you haven't responded on the Doodle poll with your choice of = meeting times, please do. Right now, it looks like we will be meeting = 3:30-4:30PM. >>=20 >> http://doodle.com/6xn4itearax7ccze#table >>=20 >> Thanks. >>=20 >> --=20 >>=20 >> Best regards, >> Kathleen >> _______________________________________________ >> Codematch-develop mailing list >> Codematch-develop@ietf.org >> https://www.ietf.org/mailman/listinfo/codematch-develop >=20 >=20 >=20 >=20 > --=20 >=20 > Best regards, > Kathleen > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop --Apple-Mail=_57E687E9-8493-436B-8A57-CAF67FF414AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" Hi = Christian and Kathleen,

I'll close the Doodle poll = Tuesday at noon local time and then send out meeting room details to the = group.  

Thanks for = checking.
Toral



On Mar 23, 2015, at 2:53 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gm= ail.com> wrote:

Not yet, do you have one we could use?  If not, we can = request one.

Thank you!

On Mon, Mar 23, = 2015 at 3:52 PM, Christian O'Flaherty <oflaherty@isoc.org> = wrote:
Do we have a meeting room? (sorry if it = was discussed before, but I couldn't found it in my = emails)

oflaherty@isoc.org
Regional Development - = Internet Society 
Skype/Gmail/Yahoo!: =  christian.oflaherty 
Phone: +598 98769636

On Mar = 23, 2015, at 2:16 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> = wrote:

Hi,

If you haven't responded on the = Doodle poll with your choice of meeting times, please do.  Right = now, it looks like we will be meeting = 3:30-4:30PM.

<= br>
Thanks.

--

Best regards,
Kathleen
_______________________________________________
Codematch-develop = mailing list
Codematch-develop@ietf.org
https://www.ietf.org/mailman/listinfo/codematch-develop<= /a>



--

Best regards,
Kathleen
_______________________________________________
Codematch-develop = mailing list
Codematch-develop@ietf.org<= br>https://www.ietf.org/mailman/listinfo/codematch-develop

= --Apple-Mail=_57E687E9-8493-436B-8A57-CAF67FF414AC-- From nobody Mon Mar 23 12:57:49 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984661ACE6F for ; Mon, 23 Mar 2015 12:57:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 73uX8zWiOZK9 for ; Mon, 23 Mar 2015 12:57:40 -0700 (PDT) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A6861A1A36 for ; Mon, 23 Mar 2015 12:57:39 -0700 (PDT) Received: by lbbug6 with SMTP id ug6so32032345lbb.3 for ; Mon, 23 Mar 2015 12:57:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sEh7GRPY5OhwbBkuUQ9r1ni/n10IwCB22J42DlqkchI=; b=gTFvHz8wvmq2o2O/4S5VgtmxFAHcR6rJdkvLnelbxKheG7eHgjY2W6sBQKiMYJKGxT 9RKaMh7XNe+h7EytuOXP6BTBPMjFFlEwph3J32xQ5hcdC4ztiIvyP4J3nrfdzXEhFB8h Twm53bE6Z1qunrwmWPsXktLbK4BugvpaQbzYOYAajeeX/Ly3Z4Sjjd8BR8xQcJj9FwBs vmVBNwZ/ClpZZas34VWtgLHTBl1FDwcE1Wb+ZRw9Oj9d1BWO1WghQJOLLyLdrBMBd38l sYlOvNi1H9jBX76NbufkbyQwx3borF1A8uhkSPaNl3/XqqaO8uH1BcHsF63BE5WWfAhj cg3w== MIME-Version: 1.0 X-Received: by 10.152.228.166 with SMTP id sj6mr559760lac.113.1427140657922; Mon, 23 Mar 2015 12:57:37 -0700 (PDT) Received: by 10.112.167.101 with HTTP; Mon, 23 Mar 2015 12:57:37 -0700 (PDT) In-Reply-To: References: <98FCC2C9-BDA9-4D81-BA95-C8C30CFF2D67@isoc.org> Date: Mon, 23 Mar 2015 15:57:37 -0400 Message-ID: From: Kathleen Moriarty To: Toral Cowieson Content-Type: multipart/alternative; boundary=001a1134352cf5c8b90511fa1373 Archived-At: Cc: "codematch-develop@ietf.org" , Christian O'Flaherty Subject: Re: [Codematch-develop] Thursday meeting at IETF X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 19:57:44 -0000 --001a1134352cf5c8b90511fa1373 Content-Type: text/plain; charset=UTF-8 Thank you, Toral! On Mon, Mar 23, 2015 at 3:57 PM, Toral Cowieson wrote: > Hi Christian and Kathleen, > > I'll close the Doodle poll Tuesday at noon local time and then send out > meeting room details to the group. > > Thanks for checking. > Toral > > > > > On Mar 23, 2015, at 2:53 PM, Kathleen Moriarty < > kathleen.moriarty.ietf@gmail.com> wrote: > > Not yet, do you have one we could use? If not, we can request one. > > Thank you! > > On Mon, Mar 23, 2015 at 3:52 PM, Christian O'Flaherty > wrote: > >> Do we have a meeting room? (sorry if it was discussed before, but I >> couldn't found it in my emails) >> >> Christian O'Flaherty - oflaherty@isoc.org >> Regional Development - Internet Society >> Skype/Gmail/Yahoo!: christian.oflaherty >> Phone: +598 98769636 >> >> On Mar 23, 2015, at 2:16 PM, Kathleen Moriarty < >> kathleen.moriarty.ietf@gmail.com> wrote: >> >> Hi, >> >> If you haven't responded on the Doodle poll with your choice of meeting >> times, please do. Right now, it looks like we will be meeting 3:30-4:30PM. >> >> http://doodle.com/6xn4itearax7ccze#table >> >> Thanks. >> >> -- >> >> Best regards, >> Kathleen >> _______________________________________________ >> Codematch-develop mailing list >> Codematch-develop@ietf.org >> https://www.ietf.org/mailman/listinfo/codematch-develop >> >> >> > > > -- > > Best regards, > Kathleen > _______________________________________________ > Codematch-develop mailing list > Codematch-develop@ietf.org > https://www.ietf.org/mailman/listinfo/codematch-develop > > > -- Best regards, Kathleen --001a1134352cf5c8b90511fa1373 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you, Toral!

On Mon, Mar 23, 2015 at 3:57 PM, Toral Cowieson <co= wieson@isoc.org> wrote:
Hi Christian and Kathleen,

<= div>I'll close the Doodle poll Tuesday at noon local time and then send= out meeting room details to the group. =C2=A0

Thanks fo= r checking.
Toral<= /font>




On Mar 23, 2015, at 2:53 PM, Kathleen Moriarty <kathleen.moriar= ty.ietf@gmail.com> wrote:

Not yet, do you have one we could use?=C2=A0 If not, we can reque= st one.

Thank you!

On Mon, Mar 23, 2015 at 3:52 PM, Christian = O'Flaherty <oflaherty@isoc.org> wrote:
Do we have a meeting = room? (sorry if it was discussed before, but I couldn't found it in my = emails)

Christian O'Flaherty -=C2= =A0oflaherty@isoc.o= rg
Regional Development - Internet Society=C2=A0
Skype/Gmail/Yaho= o!: =C2=A0christian.oflaherty=C2=A0
Phone: +598 98769636
=

On Mar 23, 2015, at 2:16 = PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:
<= br>
Hi,

If yo= u haven't responded on the Doodle poll with your choice of meeting time= s, please do.=C2=A0 Right now, it looks like we will be meeting 3:30-4:30PM= .


Thanks.

--

Best regards,
Kathleen
_______________________________________________
Codematch-develop mailin= g list
C= odematch-develop@ietf.org
https://www.ietf.org/mailman/li= stinfo/codematch-develop




--

Best regards,
Kathleen
_______________________________________________
Codematch-develop mailin= g list
C= odematch-develop@ietf.org
https://www.ietf.org/mailman/li= stinfo/codematch-develop




-- =

Best regards,<= /div>
Kathleen
--001a1134352cf5c8b90511fa1373-- From nobody Tue Mar 24 15:12:05 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06421A1A9D for ; Tue, 24 Mar 2015 15:12:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 ZLyFjjKCMYoH for ; Tue, 24 Mar 2015 15:12:03 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0607.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::607]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22CAB1A0404 for ; Tue, 24 Mar 2015 15:12:03 -0700 (PDT) Received: from [172.16.70.117] (69.15.241.124) by CY1PR0601MB1375.namprd06.prod.outlook.com (25.163.21.149) with Microsoft SMTP Server (TLS) id 15.1.118.21; Tue, 24 Mar 2015 22:11:45 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Toral Cowieson In-Reply-To: Date: Tue, 24 Mar 2015 17:11:45 -0500 Content-Transfer-Encoding: 7bit Message-ID: References: To: "codematch-develop@ietf.org" X-Mailer: Apple Mail (2.1510) X-Originating-IP: [69.15.241.124] X-ClientProxiedBy: DM2PR07CA0016.namprd07.prod.outlook.com (10.141.52.144) To CY1PR0601MB1375.namprd06.prod.outlook.com (25.163.21.149) Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1375; X-Microsoft-Antispam-PRVS: X-Forefront-Antispam-Report: BMV:1; SFV:NSPM; SFS:(10009020)(6009001)(6049001)(39224004)(36756003)(2950100001)(23726002)(77096005)(2501003)(558084003)(50466002)(47776003)(92566002)(2351001)(107886001)(82746002)(76176999)(57306001)(110136001)(229853001)(66066001)(50226001)(97756001)(42186005)(46406003)(40100003)(450100001)(83716003)(62966003)(122386002)(33656002)(50986999)(77156002)(86362001)(87976001)(46102003)(7099025)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1375; H:[172.16.70.117]; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:CY1PR0601MB1375; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1375; X-Forefront-PRVS: 0525BB0ADF X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Mar 2015 22:11:45.0351 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1375 Archived-At: Subject: [Codematch-develop] CodeMatch Meeting Details -- Thursday, 26 March X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2015 22:12:04 -0000 Here are the details for Thursday's CodeMatch meeting: Thursday, 26 March 3:30-4:30pm Central (local time) Fairmont Hotel, Vista Room in South Tower See you all there! Toral From nobody Mon Mar 30 18:55:37 2015 Return-Path: X-Original-To: codematch-develop@ietfa.amsl.com Delivered-To: codematch-develop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37811A0451 for ; Mon, 30 Mar 2015 18:55:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.6 X-Spam-Level: X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham 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 ieszuaDWLp6w for ; Mon, 30 Mar 2015 18:55:35 -0700 (PDT) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C911A044F for ; Mon, 30 Mar 2015 18:55:35 -0700 (PDT) Received: by qcay5 with SMTP id y5so2841737qca.1 for ; Mon, 30 Mar 2015 18:55:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:mime-version:date :subject:message-id:to; bh=kdenrf4GqxtL+7ksi0NwZMgxPz1tvLNVAK+qnKgvYLo=; b=hrSHWj9wSubApUefqrxWPchZyYO9DGyDdaejtRJNaslWV9i/p7AG+rICLVLjO+Fm2J VVBYhJ0YJNa0ZF3syADnkZP6nGCkr75xpoUiFpY+sHj66Ngs6/846qYuT7nXXBqq8tH9 Z7JjVZgswO+WsgQ5rgp3ckDOzc+if9w1IYU/IxN7xiRDjL4KjipB/HH9MnbG75eLzhON PzmXDKhUlV5ZDvfGwTHrWisABUwydwBK7BRroBK4EAFHYf17B7eL0SsdGIzvxczC2Ev+ VbLXnTu5tRmbRABZU0gNi6jCiHyePwYBWbsgBTyr4SoRKuUVRtKvFgpBEy3sW9wSBtvp cz0g== X-Received: by 10.140.165.198 with SMTP id l189mr47076403qhl.93.1427766934739; Mon, 30 Mar 2015 18:55:34 -0700 (PDT) Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id r28sm7761254qkh.12.2015.03.30.18.55.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 30 Mar 2015 18:55:33 -0700 (PDT) From: Kathleen Moriarty X-Google-Original-From: Kathleen Moriarty Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Mon, 30 Mar 2015 21:55:33 -0400 Message-Id: <0BE775D7-770A-4412-8271-BD19E96E9D1B@gmail.com> To: codematch-develop@ietf.org X-Mailer: iPhone Mail (11D257) Archived-At: Subject: [Codematch-develop] Wednesday call agenda X-BeenThere: codematch-develop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 01:55:36 -0000 Hi, It was great seeing everyone last week in Dallas! As discussed, we'll cover= 3 topics on Wednesday's call: 1. Feedback from UX testing so we can integrate it into the prototype as we a= re close to starting development. 2. Overview of what resources we'll need to support CodeMatch with AMS team.= 3. Discussions on programming to the datatracker. If Suresh can make this c= all, we'll focus on what we need to know about the environment. If he can't= make the call, we can discuss the plan for code sprints and organizing work= . In any case, we'll cover one of this this week and the other next week. I'll send some pointers to previous discussions on programming to this list t= omorrow. Thank you, Kathleen=20 Sent from my iPhone=