From tcaswell at gmail.com Sun Sep 2 20:50:48 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Sun, 2 Sep 2018 20:50:48 -0400 Subject: [Matplotlib-devel] tag signing housekeeping note Message-ID: Folks, I am going to change what key I am signing tags with starting with v3.0. I have signed the new key with the old one. I have been signing tags with 0x57fa4540dd4efcf7 and in the future will be signing with 0x9e027116943d6a8b (specifically, the subkey 0xBCD928050D713D75) and published both to the mit pgp servers and to keybase [1-3]. You can also get both keys in one block from gtihub [4]. The new public key is pasted below. Tom [1] https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9E027116943D6A8B [2] https://pgp.mit.edu/pks/lookup?op=vindex&search=0x57FA4540DD4EFCF7 [3] https://keybase.io/tacaswell [4] https://github.com/tacaswell.gpg ----- -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBFuMQ9YBEADDaJNOaGpG/11Zsg/e2I4Z2iCWsxTF8WH+fuEX/9FwPG1jdHeo ZroYFw5AMWbCXgXEzw4DMyTNkQRerf5lMsWppwUFQyu1Fsy4Qpom2yqt+HZgh+Hn BVkr6T/ixRnwmWsw1y+F2T7LuJbw8Lg3aq4Mng5I+V1RZeRWp7TUc05mmCrQXt/v A3clWlf1MKU9Tco7iICp7lIdp7AsitkJGJ6iBV38y55IkwV+hNEib7hYarbk1o3c G+JSDQnVI91Y7Gs1rPsgtRK+yVoqsgP6hGbkxjJuS+WFyS4eitNF5V7a4Cnf78It +/4EqZ3G2E6RLqfn4Clj6rWCJIZUrz/VxkMbSdfxhx8xnFG9bge8sNK4McBKAykP qil1W1DJbCnFTTnItVXnJxPhhkFv7SkpaceUm6vhNVZAplLyCf6r5UUH93b9qhg5 DU7hrPUPbBWL/t2py/hijZWuZjwD26SM1rN7OC3l0BCxbagxMM9RrFlnHAyPj9fu EqPrLTLTpziaDbVpFSnryOYeC5ZsDnrTn40u7ajeSqdLYpP+CiYKRb7SqUaG0ZIO Mgi+qwzO5DViCU5qLJiSp+2fEgPvjpugjnhqUpwM2rBDAYgG7fAq0rXVlheC1TQd /+jDPQmjLCWxm5vEl87BSzAD9hK5ABI84GJS2Qu/6ms8mdcD4K7dKb7TvQARAQAB tCVUaG9tYXMgQSBDYXN3ZWxsIDx0Y2Fzd2VsbEBnbWFpbC5jb20+iQJRBBMBCgA7 AhsDBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAFiEElrczTXYQ7j5or/5YngJxFpQ9 aosFAluMT6cCGQEACgkQngJxFpQ9aosVNg/+Odn9qzENupRtTLfxDR6gGOigWKrj cGdHP+f5h25IolhOZ3p80OVGw0lHRG/mqQWO8DfrV+XLoadzdLHC9IifVSGNCOxX X9C7ZIREJx/UkCkcHuIoIxrtzW2o+c2GI5AFUp2JWs5+mJcQ2Du7kQypO1vi8uEH UG+wqC8BNGFWbKl+Q9uojcDgyEIDmf7uqlnm7q8CXuA0Db0OZx5L0LTaLLIUUrgP aV8uzApJwk2sxRNfKeXzy6xPXtJMeHXXrFqQzNqLPTDE2AOVBuKu7pckxwYM2+GT vJaOOWRo1s+J6fIucvnQeTSUhjNAZqXbv+lK538zzKQi3Dlm6em73EC4e6DUNHXk U45aN80jL545eYomSzCtCv4lX5gaByHHLY6QJS1/iuHY0vqJ41dKw/laKbv2c7XQ FpYeWyl3INeeILHSamVsgPVJZ0jPedvV9DtWFU7cQleI40ZKn4auGfBQmt0V+wtR cswgUwkstvsP1SuwMej92z1KKjZM+dgCR3J2qAXuXnXXoNfCGTfmlwCtexp19vme VWPVdXb4hSSfPC0hbW6qNoWJx8PxNTKqnfjzEvjaKm/XQuNGqmBW54nWvnJlFAUo EVjdN4/gF0fJyzapKBk8q9pBaYDi1Qbr2pBJ/b5f6KzZk1RQjXosWiE1GPsskwCI lhBF+OG4HDjy+MaJATMEEAEKAB0WIQSsR/cdsnXs0LPaRuhX+kVA3U789wUCW4xI 4AAKCRBX+kVA3U7897hfB/9EmJ4Y5prkkYfiU0/QuxeAMNwJzUGDoK2jXO9VdFt2 svkOMhVUSNVUrVu5fh4n6UQmIlZcpafXD3gYGERd8cYV5R24KpGcTCRQatOhrPZ5 xRm5NZYAFZG/uEKthBFrIDo/qjfW4e1BGOV+2tAEKwKeQosdBN/fogcvCGa+m/8t PAGYBLuSZl4S5ltxvGwz+WFEl8TTBP/ljRY0fjLi/3+uMrsqzl9LZD6VdkMLQ2y8 CJhEHkDFgRKlWk0hVij874Q6WENWlU0yq61HpRw2U658K/NQwUs0lg9Vw1LxdlJc H0bgDY3CrrvObmZzyC3oRHbfpFNsiG73wb+BcUz5SkVQtCNUaG9tYXMgQSBDYXN3 ZWxsIDx0Y2Fzd2VsbEBibmwuZ292PokCTgQTAQoAOBYhBJa3M012EO4+aK/+WJ4C cRaUPWqLBQJbjEtWAhsDBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEJ4CcRaU PWqLokMP/1+u0rv4UE8VBWre3nO/ghWSL++8t4Y6cnvVyY9Tc6aS4p7SrOQH+k30 CMhtgm/YqyiPiX1UOyb1jVtw8rJFhWdTTkOlipTo+bDt5Vl2qcCajT+x7gl4I8Qo an/vbOa6vO/yVxo0vXf5Q83I2vnt3LedxNhYeWGlZ6H84ikLJAjKoCe9tWD3fzdl C/DgOXlsMc19ZuhaFzqFcm161NbkchqotZ1iHYzKWIH9P3dat6qTgLxjNiZAykXB xEC46ECV0OXcCDEjnUnuxn2OdX7Byc43fbstB6fKOotbWIUk3tb2wm3M/bsuwjMP yf/fhTdVA/NI7PSiTDGRG7H2cpe97KxB8Qw5zBSWfJpZgq63ER3G/LADOX7Y2c6o FROfQG/wFaCgxjNsTCBUJymtoPUTZS1pYQrbMiB7V5YTz98dW+4/p8sJ8ZWR7HT5 8A3XgXOD0824N2+5HrdlWVOCjZRyrGaFvPKrIBR/DIJ0uA4urlsauvIzWJcUhgQi itSw7t9tPaTcLzKrShElEw8Wqs6Mg7sEGYQSD6J6FTJbPlLgrBY+MaHs/TQE3/r0 PS5vrkKMTG7XSSWap5ddmHq51Vj1LP8T7U1DIZlUHVSBsmkWi3etKrYa2PRLO6xt 8X6WiOlZocQVASBkGRCW95ez2B7ihEDYpGQbOLnHXFcKYrrPIWBruQINBFuMSk4B EADsTox9y9huh8ReawmzExQuDOjRrRL8xeYt3JKeDRJvy2tt4b07M+kxyVImfdnv e/2ziT83+g39YGi0aA9FTTOuYHo3IRgB/blhLxxUD+L9glouCq2eUWrQmGdo5ENz fJHH0+wLeI0zXNJGw6ItgVjbCYZDaDZf/WGK+rDISumoqrZ6+yBPV+0btLhf0n93 fo/1fNSl1ko4SsyCOPj4Ib6G41Gl5T6IxZT5WZWTkzIuP28m6mnRWIrL1ttuJ0b9 eu643kT5UdMB6+G9wf0TiwJqNICVdjgAVvZhcFwJ3JUwssh7S5450N2o0EKtKkRc VTroAJh5+xW+GDZ62Ga5pdE9dpf9vG0Tp53NhopSNUdV7h5X7BK/UFgvyaTwpjPd u/48TSDmyb/5XYwYq5IzFRZr//wuTG7qCKUKre/DXovVCgAok5fOCXYFOPq//U5G 5yhgLHowJ9iLRQyU2X7vPepHMyjMf14WBJpM95Zz+HdOUN1QfvbgVQDhCB0tIxc4 PrmZQjkcOCpU65w56pca1bB3qtu6OH3O5Z4B12k7ZxKjby/Dp54VVwYNEVazGdo6 1oO8CLvSWg42nPo6OuXdWicTnfWF8cwMFBc2+D2xnU2el98fVFaxgBoBpvUmwoWJ o6NKzThoHep5d8ZZ01O+Wztoj5RtLqV6QVtegO/M0dt2KwARAQABiQRsBBgBCgAg FiEElrczTXYQ7j5or/5YngJxFpQ9aosFAluMSk4CGwICQAkQngJxFpQ9aovBdCAE GQEKAB0WIQSxhz21VURtzMy3P9y82SgFDXE9dQUCW4xKTgAKCRC82SgFDXE9dSZt EACejFQLKJ0Igquxoegpc0CLXfDg3nukLkNexCaKaOvN8hScMU2diJOVzJTksFJS K3y1E+cKR7BZ6iYbl9nxi3PIb3yetYMccJCBbIbQLcmHFLgVWNM/fG+i/+Np7zXQ GcubaLm96kb4kcY1Oq3V2PLOuWmkLI0yqYoWbz/BEpEkMnFbI3jDmM3bPA74sOFN 0LcHGPBbZjSrbxggtxWb+KN72jJLhIm/2MlE+Bq4Wvf5lxSpF06RyQ8YzhXoIH9h eB5W3k4KWQVJzjL9KARN33ee7cf2HbHLDK4gpDZm5200ORRUHq2zKClLXjrm9oSe GDEPywm0XAGAwRrVmEhRXKV1iXNUxBK0xXpN1d0WYziaV1EFJCHBibwx6OvdMdaL bt0JErVx0AFadQzxjKEnO5EOifKVKjEXv0vrd5PeqOPpzydpeetO1z2FQ68tF7vr 5RgQyU6ZcFRlIq/Txim2kz0ZTfgsCn73LIRoJL8y/CExxeG3YmmpJJXipZaNmdxp BHsm+1BrEsn9Q72EIXucsup4Zn2oiqtXp2gSjR6AXF+Wr7nBiAU8pxsbGanU+QMB D5mIdcLsGC1EUKt5J34JKeY42AtirXLF4v1L9h68KGATGYeUXSBxoQIEXzffbPBU t5Y7H93yUnUbxZRSSUPKq2A9f/pW8XWDq0vHJkr6v9HNaTM5EACH6GnglyNV5AAX Ug22vU2P4bQX3OaxKD+sAfF164H65QbPuJZlp58oywFgeyi24yOS8Fj9Lh8Jul7Z 1N/JiO5fHk7iLnDKXZASZR+Hnywa6lpbM8o9LeGhMFx8/rEDbkyzijq+OZtRx17e kXxfLHP48VKRGRb+vfEQmuekC28/GQSy/u1IMCifuRqYA1v9YWNqGaSJfGbBImDA LxO9+M8qXLUwBYVVhe6+Gh/Ge3I71xzpqr5OUnTickefPojGxZKiGWtqEZgdIOcq 7HCsg6Fm3rXETkHNywGepSYtK6GN5U0aygkB2MFxNZPE6hsz/TQFuzX1AxKDlWir OcxCrn3TMxxAU9mc2iqb1CJiPIg02B1xS6VjYYYgAwrwCJrNE1RGkg3a8JDiBiai X9CJUEuqA6CvntczWBHSGnv+ptUrYDQT8oaOThnGyXElKyNqZt6dIffCcy7UXOnu JGyPO4LTSlE2ZWJHgcYKr6N1wUV+UhU14bruoC3b9taGoi0mB0SpoTcv5CJ7Uz71 axi+826G/EZp3ysWQD2LY98nEsS3tH14sH6kzGhd5IIUw2asaq5hVKvU6AKbTUbB m9nbprtO24tFlENcPjpo1OTcXy9p4e9lmaheADsvmtBs3c6oPsCro/e6f9eWDOQA 8a8+HZKF6wTh/usz5hK/tzFraLv1h7kCDQRbjErQARAAxweL70TsHQNAvCgpBVM7 8vS2m4lKuP23AwzpQ15q9us+P/0b/YhDCMb86XIMhcMthPb90cK1DbjHb68EoAFl uCGzhAu+dnANFwxuuTjyMrrJA7GkX6GioNeaDumcCGnKxLtV72xAsgtSqL1NKGa2 1iEqEGPB/QmUUou7ktuVDoS9Lo8BOL0B8WmFJEjazJ+d5+BYU+cOGcdPA1gR0Ctw x37XB2nOFHwvqRpQkcYE8+MMCNk2uyfCwA4US0nYfHgPinTpItJPtQ1nKvmGm/d6 xywyIELiqRuK+/RIccsf83u9+HU4pZZUh7d066j6Ecgb6O8+S8Tr08RNrGhXyUJY sWOyRqUVd1GI1S48GZXprX9J/zOznQQOHT7BPKDjRl6TZc4G9xAPTqAQ0nHkOQmx Z9Vb9PZuQmr3MDmchj8TfUuDuoejsdSkpgIuKBBfVQDCmLNSZIgp9W41+Ags6vUJ DpdqXgpIr3rnEB6u2L5ME2FGzOrYTAZgA3J5ux4/WvN2i9GzklwmG6XXBBEd4zMw GLd0DP/5+ixvKdaDeE085R+bRg5U7BqWZRjEttkw9JeljbI0C/t3CyMYOgBJAIl/ VTTn2Lu1n87M3y8WGK0lgwAptAbcEMRo6gffr0TYaO1x3EAF1y6upQWkMDPUjYXX yj1J/5q+MxdrsQZJLwudfYEAEQEAAYkCNgQYAQoAIBYhBJa3M012EO4+aK/+WJ4C cRaUPWqLBQJbjErQAhsMAAoJEJ4CcRaUPWqLJJcQAJN5JOBmwgEdhxnsqmlfM5RU RG9h3fyRhlQfZgp7mNpMbq+yHgXdv6t/Vzjtswi6nulFLNR7F1oIS5gTpTpPtgNS NOHeLoY5eXHawLAIP+3laECa/0sLUyCShHSgu/Xj0qpRimAcd68+sLzkDG4V5CKi Rx8dGAx7fAdjIX8POQasWKy4PFmsmdKszni6Q5uEXsKOMt1+wLUzc/YuOx9NK/0J iV+CUATFiIbuWdugSBhuE2TMyx4b66EDszEaGXcxHJ90Mm0L7nvVjwdQf7ghojN9 yRqOk9Z4+YbpX/zyIEZysdpFxYhjYZEhLG/Sq7e4yp8ttwWYfjSli3egR9sB3W5e mHKkN86ZY7jRQV3uPNw0BxaMja+IYJOMVNKvIXplL3+oAwGzmoMeTInJHQuIbIXj rHcsmIhvxFTLk8JNFrSqqAV4HiGD5cwlOELSDek7jRXDo67DsIWJK49MuH70a28N lLGMvvoN9zWnG0DJRO5qRXAaLkG58Oy2dKlKCZrxrf0KegKc71nsHlO+rvvSqpJO X2ZAmcf+5owLeEZSjAuRr1NIkOUmEGZOVaKzhmoL9ba0vj5AEX422KuivdoqdXSX WIEnV2xjkpLDTv88QqVub9MYqBN4iSutaslgS3QF8ZtiTlwQQwd7/q9N1IkGL0Y8 U7yHNPimMA2r0DegnWgkuQINBFuMSvwBEADWcUpzCX12B8Sz/ZagLJXF0eq55AOL Zrs8aHqBodJgPDQ6UdpADd+iHpCKNJq3AP5CdQfxs+yOQ5rrlWQGKQJ9qCLueAKq gaea92zi8g92Vzx+lqe/5CR+HhJZKPWSZ9lbWXN+99xrYkgY4JarVh4GNfamM9y/ HbVpvRvQoIA1EcaepfgFe1zi5XgETSliFxcubS4WbmnmgHcGcbjnzdVJuXSop7Fc PMEMfdkENNIBHWI2yuEkO3CYWDlmopilsYxO5gaG8vFgUdIBdU0n91H2TioANIko I8idFVvdAajtpXWKMPKbBgzw+TrKr7Ncg02w8Q2Jt4RzJd0xyMSW+NK6VZhypP6E utXTutu1IY9Yes8OOO/xIB73EHkyk20NUejMmdeEfep0lfBvKNKQoVG9k6fvyhHG DV8PpjEQYNRlFHb5zYLrESbw4HR11xfsAxijn3ACdM5x2w3GhA4jPvlyjH18su1f oEdBk7SOuGK8/p4yEvXo4DULsj4lixPnjwV55n9V7BG9pnY6xrUuC0h87E4VRmSs +aoACxVArb+6uZr7PrUgesOFsq4bN9Zh00T9PYOweaiQypOHpe0ydgZ4qzyn/6dy KS3LI9juzQgtxeBWaRc2a5lFhDTsxRJjLRc/X/V2TD7KxyVAmvMJffP3JS006N/2 VKYwTydTbW0DIwARAQABiQI2BBgBCgAgFiEElrczTXYQ7j5or/5YngJxFpQ9aosF AluMSvwCGyAACgkQngJxFpQ9aovzURAAlAstrUfKk2uPRg0Vf5Vq4PGZTJBMFQC6 yoZaaxFIaA8QZbrZqiHcK2U3hZ+3X5k6Q5wf7s5EWZyExvvoJoU9NbJscIFwfZed h2R20tctQtt/C2oEiaGb0WRtd1Os1sWtYz6EYteZEMc/Vug02xNRK8YgdqjjiNc8 EYF1fLwyUa7VAMomzOTGu5ykbPd9r/HIP3cwAcnIHzYOwDeETm/YWvrzp77s9DEX QnuvmLnFRsIK0B/9uWtBFyPrGrs2kjhPQxm1yK0WufSV5IOsY+J5oGHFHj5StnoD ddbT4ci6m9jp0az2T6jGt3RFid2tu7c6u/57oBWfKCY9xL16Uztw2fW+P0w+W5sa Z9xxAWaM3CcopTbrf/IyKSPPeOyjuo9M4/PPRd4EZGbg/bCwlVGp402nG2TBn7dD yj4Uvs8FC/oa9q/zVAQgT6nHiVjunjEJo5KAhp/w6dTmj3nSFn1GTJdDp66jMXO1 1ODHJvnZ0QiT6CUlqVrEsZ47asnV11BDPt7XdpW/FA5BsDfg9+LYIUrNWUrGRfcc iiBBFZg6/iUEqb7rPI9uCACkddjMa0xQo45djOtOwYAz1kRFzGRl+3UBs8Uu6q9j siu0LJW8kFR5VPJ4828yKVdR1phuaVmVdqWDMed0Pew1J5bkPwTIxUXMntg+U2Qy FoKI6h3JE4u5Ag0EW4x0owEQAL5NhO9DIZnGlYRzjUwhNWpFbt1E1pxfq5VusZrA 8Qy4z64yRQmcnnCJXZVGkYUNF+KvL9z/HOjvptJTFCrvMGbrTk5iOoKLC2NdyPyB 8Ct6j++96FDfRMivzCgOghkWGkzN7JvOlvv+85okHR+SxXoBmXdXHU08vdoOHEF1 d21joKz4E8pHbpZfa6/hFuObtO3sWzE2oOGiD1tIGAWUTI/AdfMcitVHtmdu+4HS Q337fNLsW0ReEG4ASN8zVEFxzo36/GNYIs8xSHUAMm8N4iC/ZrPs2X50RdyI1gF4 VjOpFEJ2ENy1Y3ME3jcFaZ0uuu6lK5dV44DdKPjZAYl7yrBSAzEL6juf/yxr4ABt F+6g50wBfvB+hedh9zcfM6NJUD7o2u7nDRoycU0u+vNmvXl+rJ3OJacNbYsipHn9 HO+Eehu+GbHbUgMLlMHvkIm+Fdmp+6yGj3zYTfvwTNApOoBUuuCLgAMymLd6RIUf ALPtOTKCqDLn3rOH9s51sk6dGlBVzaCb+DyDC6qcE6eONiy6gb3LgiMQFWNvjiWv tFd28nxtZuSP71za4h7Ed9mP+T4YCTobqUru8hEDaD2cqCK3D+AYDA3ttLwh8dHJ KTu4j4kTlmqxZX7CHRhs3coERnjIK38QhoEQrKEO2wkbp1kBTXNN+MU3EeVg7i+w hVVjABEBAAGJAjYEGAEKACAWIQSWtzNNdhDuPmiv/lieAnEWlD1qiwUCW4x0owIb IAAKCRCeAnEWlD1qiyvUD/46j0EGXUt5/9xsdwP9K6L9EzL/cxjd+H2S7DwLRE1n Mp1BcU3zg3m65WWWha16bbFM5J3OOfxty6O5jBMdJrnF3wLJtXka7EptTBxrRACn 6RY9Az7yjH+ZZF6i8Sytr8PVW6/guzOUPdS3c0SWSahURv4ZuzMh5eBRvjAY3hJB WCp9rXUwsE5NHMcnLSHxn95nhXOmPf814g+1Q2Hup6WslIoDLIXOBwuJBASahNqK ASnDIQ5rCW1ye8M1yRp/C22QB3DHbwfinoquqOYQupY72NxNa+rcTKEjQx3QBT2g KE7LDkTOPF2OHZ7HBJ5u85bk7hxVl+UPrESkNFzAH1IUoxe91Uhnz4bt9AQ75F87 8+YTZ22BnbxurIvdTuHwvoM7JU76YREf5bntOLRaf7e/Zdp8BjuzTpaK1Vs7o2X5 RbGjIvWXmLPuAevO3z9Mh9a2TN38X57l36PgR3Lcc1FJ54Jp2ecjkwbEna8zMu18 v2drqyAI7JZlZDBBhueE+koB6Wc7wKukxB+oCXQd2eXkGmuLQ4Zic8WUGFVm1h/m WQxcsrbeAL68Xf55/L+B2oA9ePOFPxbvEBnIO7mWb0xAeRkuULj7Xx0yDVeTxs9B 4HS8tLsywZJOY+IGjZziWn1yVjAA0JRDg9XMuhtM/Uq2X0PO5f2U/vU0VFGFNXKr 8Q== =NLEk -----END PGP PUBLIC KEY BLOCK----- -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jklymak at uvic.ca Mon Sep 10 13:35:30 2018 From: jklymak at uvic.ca (Jody Klymak) Date: Mon, 10 Sep 2018 10:35:30 -0700 Subject: [Matplotlib-devel] weekly call Message-ID: <146BA4E2-040A-43C2-81FA-A755423774EF@uvic.ca> Hi all Agenda for this weeks call: https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--AMZL~29lQguRD8kFyBxN1P~DAg-aAmENlkgepgsMeDZtlsYu Call at 15:00 EDT. See co-ordinates in agenda? Cheers, Jody -- Jody Klymak http://web.uvic.ca/~jklymak/ From tcaswell at gmail.com Tue Sep 18 00:12:51 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 18 Sep 2018 00:12:51 -0400 Subject: [Matplotlib-devel] REL: v3.0.0 Message-ID: Folks, I just tagged 3.0.0! Wider announcement once the wheels are built (likely tomorrow night) and the docs are published. Thank you to everyone who worked on this release (130+) over the last 6 months. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Tue Sep 18 02:45:43 2018 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Tue, 18 Sep 2018 08:45:43 +0200 Subject: [Matplotlib-devel] REL: v3.0.0 In-Reply-To: References: Message-ID: Congratulation and nice work ! Get some well deserved rest ! -- Matthias On Tue, 18 Sep 2018 at 06:13, Thomas Caswell wrote: > Folks, > > I just tagged 3.0.0! > > Wider announcement once the wheels are built (likely tomorrow night) and > the docs are published. > > Thank you to everyone who worked on this release (130+) over the last 6 > months. > > Tom > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Tue Sep 18 20:43:56 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 18 Sep 2018 20:43:56 -0400 Subject: [Matplotlib-devel] [REL] Matplotlib 3.0.0 Message-ID: Folks, Happy to announce Matplotlib 3.0.0! This is the first version of Matplotlib to only support Python 3. If you need Python 2.7 support the 2.2.x LTS series will continue to receive critical bug-fixes until 2020. Highlights of this release include: - GUI backend is selected at run-time based on what toolkits are installed. A GUI toolkit will not be selected on a headless server. - New cyclic color map *twilight* - Improvements to automatic layout of titles, ticks, and GridSpec - Many bug fixes! For the full details see https://matplotlib.org/users/whats_new.html and https://matplotlib.org/api/api_changes.html for whats new and API changes respectively. For packagers: Matplotlib no longer depends on six or pytz. A big thank you to everyone who worked on this release in terms of commits (~130 people have commits), reporting issues, and review. I expect there to be a v3.0.1 release in the next month or so. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Wed Sep 19 10:03:12 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Wed, 19 Sep 2018 10:03:12 -0400 Subject: [Matplotlib-devel] [REL] Matplotlib 3.0.0 In-Reply-To: References: Message-ID: Folks, A small update, when I uploaded the wheels yesterday I only uploaded about half of them [1] and did not check my work carefully enough. This has been rectified, sorry to everyone who had installs fail his morning. Tom [1] I downoladed one of the wheels from http://wheels.scipy.org/ twice, the browser helpfully added (1) to the name, when I when to upload everything twine got half way through and failed out on that file. I thought it had done everything else, but it had actually only done everything up to that file. On Tue, Sep 18, 2018 at 8:43 PM Thomas Caswell wrote: > Folks, > > Happy to announce Matplotlib 3.0.0! > > This is the first version of Matplotlib to only support Python 3. > > If you need Python 2.7 support the 2.2.x LTS series will continue to > receive critical bug-fixes until 2020. > > Highlights of this release include: > > - GUI backend is selected at run-time based on what toolkits are > installed. A GUI toolkit will not be selected on a headless > server. > - New cyclic color map *twilight* > - Improvements to automatic layout of titles, ticks, and GridSpec > - Many bug fixes! > > For the full details see https://matplotlib.org/users/whats_new.html > and https://matplotlib.org/api/api_changes.html for whats new and API > changes respectively. > > For packagers: Matplotlib no longer depends on six or pytz. > > A big thank you to everyone who worked on this release in terms of commits > (~130 people have commits), reporting issues, and review. > > I expect there to be a v3.0.1 release in the next month or so. > > Tom > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Fri Sep 21 16:46:12 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Fri, 21 Sep 2018 16:46:12 -0400 Subject: [Matplotlib-devel] welcome Ernest to the team Message-ID: Folks, Happy to announce that Ernest (aka @ImportanceOfBeingErnest) has accepted an invitation to join the team! Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Fri Sep 21 16:53:47 2018 From: ben.v.root at gmail.com (Benjamin Root) Date: Fri, 21 Sep 2018 16:53:47 -0400 Subject: [Matplotlib-devel] welcome Ernest to the team In-Reply-To: References: Message-ID: He wasn't on the team already? Surely, just an administrative oversight! Welcome aboard! (officially) On Fri, Sep 21, 2018 at 4:46 PM Thomas Caswell wrote: > Folks, > > Happy to announce that Ernest (aka @ImportanceOfBeingErnest) has accepted > an invitation to join the team! > > Tom > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Fri Sep 21 17:34:49 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Fri, 21 Sep 2018 17:34:49 -0400 Subject: [Matplotlib-devel] Steering council bootstrapping Message-ID: Folks, I have opened https://github.com/matplotlib/governance/pull/5 to start the process of filling out the steering council with Eric Firing and Ryan May being the first 2 people on it. I would like Ryan and Eric to publicly accept (I asked them privately already) and then we can merge that PR and have non-trivial steering council! The first order of business is to sort out what we want the steering council to look like long term. Our current governance documents are modeled on jupyter, but I think we should diverge a bit. - I would like to think of being on the council as a responsibility / obligation / service rather than an honor or acknowledgement of previous work to the community (we also need to pin down what work the council has to do ;) ) - cap the size of the council to 5 or 7. Much bigger, it gets unweilding to schedule things / get things done, much smaller we may not capture the diversity perspective we need. The requirement of odd came up in some of the core python discussion if you let "the status queue" have a vote, but I still lean towards an odd number as then it is BDFL + even number (see below). - have terms on the council (2 - 3 years?). If we cap the size and want to be able to bring new people on, we need a standard way to also roll people off (as a physicist, conservation of numbers is very important to me). This also gives people on the council a graceful way off if they want it. Given the first point, it seems like a good idea to give people a time horizon for what they have signed up for. I don't think we should have any sort of term limits. 2-3 years seems short enough you can see the end, but long enough to get stuff done (at our glacial pace!). - We should stagger the terms so every were we do 2 on / 2 off (hence why I like the odd number total). If we go with a 5 person council, terms would be 2 years, if we go with 7 terms would be 3 years. - follow the model NF used for their board election: completely open nomination, endorsement by a small group (in their case, projects leads of all the sponsored projects), and final selection be the existing board / council. There are some details to work about about the middle group (everyone with a commit bit? + a list of "power users" ? + leads of important down-stream projects? + ??). Would it be the full council or the remaining n-2 people for the final selection? - have a named secretary responsible for making sure votes / decisions happen - not have any explicit limits on commits / activity / etc. Trust the above process to pick the right people. - I could see making the case both for and against have an "outside" person on the council In terms of responsibilities, I am thinking things like - writing and managing grants - organizing mettings / workshops - CoC issues (sorting out what to do about CoC is the next order of business) - approving the distrobution of commit bits - developing high-level road maps (things like "we should overhaul color handling to better address X, Y, Z") - sorting out what to spend money on (this includes the finance sub-committee) - sorting out process (do we want to revive / enforce MEPs? branching details (maybe that is too in the weeds?)) [this may or may not be a list of things I have not done but feel I should be doing] I do not think the council should be responsible for: - day-to-day code reviews / operation (this is running enough fine as it is) - detailed feature review / design (ex "Should we spell feature X of the color overhaul as foo or bar" or "what color should the bike shed be") (do not want to make the council a bottle neck in the implementation process). I am not sure if this is better to discuss this on the mailing list or on github. I lean towards mailing list for now until we start talking about exact wordings of things. Sorry this is all over the place in terms of high level / low level. I have been thinking about this for a while and finally opted to get it out of my head in what ever state it was in ;) Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From antony.lee at institutoptique.fr Sat Sep 22 11:12:25 2018 From: antony.lee at institutoptique.fr (Antony Lee) Date: Sat, 22 Sep 2018 17:12:25 +0200 Subject: [Matplotlib-devel] Steering council bootstrapping In-Reply-To: References: Message-ID: Thank you for taking care of this. In general, I don't have a strong opinion about the setup of the steering committee or its responsibilities. However, given that you mentioned CoC issues, and based on the recent threads on numpy-discussion regarding numpy's CoC and on python-dev regarding "import this", I believe that CoC issues are perceived sufficiently differently on the two sides of the Atlantic that I would like to propose that the SC should (aim to) include at least one non-North-American member (also as there are quite a few of us among the core devs). Note that I am explicitly NOT making myself a candidate to a SC position. I'm also perfectly happy with the current 3-member SC; this is simply a suggestion for later additions to the SC. Antony On Fri, Sep 21, 2018 at 11:37 PM Thomas Caswell wrote: > Folks, > > I have opened https://github.com/matplotlib/governance/pull/5 to start > the process of filling out the steering council with Eric Firing and Ryan > May being the first 2 people on it. I would like Ryan and Eric to publicly > accept (I asked them privately already) and then we can merge that PR and > have non-trivial steering council! > > The first order of business is to sort out what we want the steering > council to look like long term. > > Our current governance documents are modeled on jupyter, but I think we > should diverge a bit. > > - I would like to think of being on the council as a responsibility / > obligation / service rather than an honor or acknowledgement of previous > work to the community (we also need to pin down what work the council has > to do ;) ) > - cap the size of the council to 5 or 7. Much bigger, it gets unweilding > to schedule things / get things done, much smaller we may not capture the > diversity perspective we need. The requirement of odd came up in some of > the core python discussion if you let "the status queue" have a vote, but I > still lean towards an odd number as then it is BDFL + even number (see > below). > - have terms on the council (2 - 3 years?). If we cap the size and want > to be able to bring new people on, we need a standard way to also roll > people off (as a physicist, conservation of numbers is very important to > me). This also gives people on the council a graceful way off if they want > it. Given the first point, it seems like a good idea to give people a time > horizon for what they have signed up for. I don't think we should have any > sort of term limits. 2-3 years seems short enough you can see the end, but > long enough to get stuff done (at our glacial pace!). > - We should stagger the terms so every were we do 2 on / 2 off (hence why > I like the odd number total). If we go with a 5 person council, terms > would be 2 years, if we go with 7 terms would be 3 years. > - follow the model NF used for their board election: completely open > nomination, endorsement by a small group (in their case, projects leads of > all the sponsored projects), and final selection be the existing board / > council. There are some details to work about about the middle group > (everyone with a commit bit? + a list of "power users" ? + leads of > important down-stream projects? + ??). Would it be the full council or the > remaining n-2 people for the final selection? > - have a named secretary responsible for making sure votes / decisions > happen > - not have any explicit limits on commits / activity / etc. Trust the > above process to pick the right people. > - I could see making the case both for and against have an "outside" > person on the council > > In terms of responsibilities, I am thinking things like > - writing and managing grants > - organizing mettings / workshops > - CoC issues (sorting out what to do about CoC is the next order of > business) > - approving the distrobution of commit bits > - developing high-level road maps (things like "we should overhaul color > handling to better address X, Y, Z") > - sorting out what to spend money on (this includes the finance > sub-committee) > - sorting out process (do we want to revive / enforce MEPs? branching > details (maybe that is too in the weeds?)) > > [this may or may not be a list of things I have not done but feel I should > be doing] > > I do not think the council should be responsible for: > - day-to-day code reviews / operation (this is running enough fine as it > is) > - detailed feature review / design (ex "Should we spell feature X of the > color overhaul as foo or bar" or "what color should the bike shed be") (do > not want to make the council a bottle neck in the implementation process). > > I am not sure if this is better to discuss this on the mailing list or on > github. I lean towards mailing list for now until we start talking about > exact wordings of things. > > Sorry this is all over the place in terms of high level / low level. I > have been thinking about this for a while and finally opted to get it out > of my head in what ever state it was in ;) > > Tom > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From efiring at hawaii.edu Sat Sep 22 14:37:58 2018 From: efiring at hawaii.edu (Eric Firing) Date: Sat, 22 Sep 2018 08:37:58 -1000 Subject: [Matplotlib-devel] Steering council bootstrapping In-Reply-To: References: Message-ID: On 2018/09/21 11:34 AM, Thomas Caswell wrote: > I would like Ryan and Eric to publicly accept (I asked them privately > already) and then we can merge that PR and have non-trivial steering > council! > I accept, thank you. Eric From efiring at hawaii.edu Sat Sep 22 14:42:33 2018 From: efiring at hawaii.edu (Eric Firing) Date: Sat, 22 Sep 2018 08:42:33 -1000 Subject: [Matplotlib-devel] Steering council bootstrapping In-Reply-To: References: Message-ID: <70e0952f-351c-e230-56b3-b60d7b1261b7@hawaii.edu> Independently of the CoC, I think that having at least one non-North-American member is highly desirable. Eric On 2018/09/22 5:12 AM, Antony Lee wrote: > Thank you for taking care of this. > > In general, I don't have a strong opinion about the setup of the > steering committee or its responsibilities.? However, given that you > mentioned CoC issues, and based on the recent threads on > numpy-discussion regarding numpy's CoC and on python-dev regarding > "import this", I believe that CoC issues are perceived sufficiently > differently on the two sides of the Atlantic that I would like to > propose that the SC should (aim to) include at least one > non-North-American member (also as there are quite a few of us among the > core devs). > > Note that I am explicitly NOT making myself a candidate to a SC > position.? I'm also perfectly happy with the current 3-member SC; this > is simply a suggestion for later additions to the SC. > > Antony > > On Fri, Sep 21, 2018 at 11:37 PM Thomas Caswell > wrote: > > Folks, > > I have opened https://github.com/matplotlib/governance/pull/5?to > start the process of filling out the steering council with Eric > Firing and Ryan May being the first 2 people on it.? I would like > Ryan and Eric to publicly accept (I asked them privately already) > and then we can merge that PR and have non-trivial steering council! > > The first order of business is to sort out what we want the steering > council to look like long term. > > Our current governance documents are modeled on jupyter, but I think > we should diverge a bit. > > - I would like to think of being on the council as a responsibility > / obligation / service rather than an honor or acknowledgement of > previous work to the community (we also need to pin down what work > the council has to do ;) ) > - cap the size of the council to 5 or 7.? Much bigger, it gets > unweilding to schedule things / get things done, much smaller we may > not capture the diversity perspective we need.? The requirement of > odd came up in some of the core python discussion if you let "the > status queue" have a vote, but I still lean towards an odd number as > then it is BDFL?+ even number (see below). > - have terms on the council (2 - 3 years?).? If we cap the size and > want to be able to bring new people on, we need a standard way to > also roll people off (as a physicist, conservation of numbers is > very important to me).? This also gives people on the council a > graceful way off if they want it.? Given the first point, it seems > like a good idea to give people a time horizon for what they have > signed up for.? I don't think we should have any sort of term > limits.? 2-3 years seems short enough you can see the end, but long > enough to get stuff done (at our glacial pace!). > - We should stagger the terms so every were we do 2 on / 2 off > (hence why I like the odd number total).? If we go with a 5 person > council, terms would be 2 years, if we go with 7 terms would be 3 years. > - follow the model NF used for their board election: completely open > nomination, endorsement by a small group (in their case, projects > leads of all the sponsored projects), and final selection be the > existing board / council.? There are some details to work about > about the middle group (everyone with a commit bit??+ a list of > "power users" ??+ leads of important down-stream projects??+ ??). > Would it be the full council or the remaining n-2 people for the > final selection? > - have a named secretary responsible for making sure votes / > decisions happen > - not have any explicit limits on commits / activity / etc.? Trust > the above process to pick the right people. > - I could see making the case both for and against have an "outside" > person on the council > > In terms of responsibilities, I am thinking things like > ?- writing and managing grants > ?- organizing mettings / workshops > ?- CoC issues (sorting out what to do about CoC is the next order > of business) > ?- approving the distrobution of commit bits > ?- developing high-level road maps (things like "we should overhaul > color handling to better address X, Y, Z") > ?- sorting out what to spend money on (this includes the finance > sub-committee) > ?- sorting out process (do we want to revive / enforce MEPs? > branching details (maybe that is too in the weeds?)) > > [this may or may not be a list of things I have not done but feel I > should be doing] > > I do not think the council should be responsible for: > ?- day-to-day code reviews / operation? (this is running enough > fine as it is) > ?- detailed feature review / design (ex "Should we spell feature X > of the color overhaul as foo or bar" or "what color should the bike > shed be") (do not want to make the council a bottle neck in the > implementation process). > > I am not sure if this is better to discuss this on the mailing list > or on github.? I lean towards mailing list for now until we start > talking about exact wordings of things. > > Sorry this is all over the place in terms of high level / low > level.? I have been thinking about this for a while and finally > opted to get it out of my head in what ever state it was in ;) > > Tom > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > From rmay31 at gmail.com Sat Sep 22 15:24:38 2018 From: rmay31 at gmail.com (Ryan May) Date: Sat, 22 Sep 2018 15:24:38 -0400 Subject: [Matplotlib-devel] Steering council bootstrapping In-Reply-To: References: Message-ID: I accept. I agree as well about non-North America membership. Ryan On Fri, Sep 21, 2018 at 5:37 PM Thomas Caswell wrote: > Folks, > > I have opened https://github.com/matplotlib/governance/pull/5 to start > the process of filling out the steering council with Eric Firing and Ryan > May being the first 2 people on it. I would like Ryan and Eric to publicly > accept (I asked them privately already) and then we can merge that PR and > have non-trivial steering council! > > The first order of business is to sort out what we want the steering > council to look like long term. > > Our current governance documents are modeled on jupyter, but I think we > should diverge a bit. > > - I would like to think of being on the council as a responsibility / > obligation / service rather than an honor or acknowledgement of previous > work to the community (we also need to pin down what work the council has > to do ;) ) > - cap the size of the council to 5 or 7. Much bigger, it gets unweilding > to schedule things / get things done, much smaller we may not capture the > diversity perspective we need. The requirement of odd came up in some of > the core python discussion if you let "the status queue" have a vote, but I > still lean towards an odd number as then it is BDFL + even number (see > below). > - have terms on the council (2 - 3 years?). If we cap the size and want > to be able to bring new people on, we need a standard way to also roll > people off (as a physicist, conservation of numbers is very important to > me). This also gives people on the council a graceful way off if they want > it. Given the first point, it seems like a good idea to give people a time > horizon for what they have signed up for. I don't think we should have any > sort of term limits. 2-3 years seems short enough you can see the end, but > long enough to get stuff done (at our glacial pace!). > - We should stagger the terms so every were we do 2 on / 2 off (hence why > I like the odd number total). If we go with a 5 person council, terms > would be 2 years, if we go with 7 terms would be 3 years. > - follow the model NF used for their board election: completely open > nomination, endorsement by a small group (in their case, projects leads of > all the sponsored projects), and final selection be the existing board / > council. There are some details to work about about the middle group > (everyone with a commit bit? + a list of "power users" ? + leads of > important down-stream projects? + ??). Would it be the full council or the > remaining n-2 people for the final selection? > - have a named secretary responsible for making sure votes / decisions > happen > - not have any explicit limits on commits / activity / etc. Trust the > above process to pick the right people. > - I could see making the case both for and against have an "outside" > person on the council > > In terms of responsibilities, I am thinking things like > - writing and managing grants > - organizing mettings / workshops > - CoC issues (sorting out what to do about CoC is the next order of > business) > - approving the distrobution of commit bits > - developing high-level road maps (things like "we should overhaul color > handling to better address X, Y, Z") > - sorting out what to spend money on (this includes the finance > sub-committee) > - sorting out process (do we want to revive / enforce MEPs? branching > details (maybe that is too in the weeds?)) > > [this may or may not be a list of things I have not done but feel I should > be doing] > > I do not think the council should be responsible for: > - day-to-day code reviews / operation (this is running enough fine as it > is) > - detailed feature review / design (ex "Should we spell feature X of the > color overhaul as foo or bar" or "what color should the bike shed be") (do > not want to make the council a bottle neck in the implementation process). > > I am not sure if this is better to discuss this on the mailing list or on > github. I lean towards mailing list for now until we start talking about > exact wordings of things. > > Sorry this is all over the place in terms of high level / low level. I > have been thinking about this for a while and finally opted to get it out > of my head in what ever state it was in ;) > > Tom > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -- Ryan May -------------- next part -------------- An HTML attachment was scrubbed... URL: From jklymak at uvic.ca Mon Sep 24 13:34:00 2018 From: jklymak at uvic.ca (Jody Klymak) Date: Mon, 24 Sep 2018 10:34:00 -0700 Subject: [Matplotlib-devel] Weekly Call: Message-ID: <558D5075-4764-41AB-B162-C49EAF1A173C@uvic.ca> Hi all, Please add agenda items, and call in... https://paper.dropbox.com/doc/Matplotlib-meeting-agenda--ANn85fQYY31fowJz9mQPE_V4Ag-aAmENlkgepgsMeDZtlsYu Thanks! Jody -- Jody Klymak http://web.uvic.ca/~jklymak/ From tcaswell at gmail.com Mon Sep 24 14:50:49 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Mon, 24 Sep 2018 14:50:49 -0400 Subject: [Matplotlib-devel] contract work? Message-ID: Folks, Out of curiosity, who on this list is able and willing to do Matplotlib work on small/short-term contracts (either through NumFOCUS or directly from a company)? Feel free to email me privately if you do not want to respond openly about this. Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Mon Sep 24 15:22:32 2018 From: pmhobson at gmail.com (Paul Hobson) Date: Mon, 24 Sep 2018 12:22:32 -0700 Subject: [Matplotlib-devel] contract work? In-Reply-To: References: Message-ID: Tom, Could elaborate a bit? Would NumFocus be the client? In other words, who would be writing and who would be receiving invoices? -Paul On Mon, Sep 24, 2018 at 11:51 AM Thomas Caswell wrote: > Folks, > > Out of curiosity, who on this list is able and willing to do Matplotlib > work on small/short-term contracts (either through NumFOCUS or directly > from a company)? > > Feel free to email me privately if you do not want to respond openly > about this. > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmay31 at gmail.com Mon Sep 24 15:45:52 2018 From: rmay31 at gmail.com (Ryan May) Date: Mon, 24 Sep 2018 15:45:52 -0400 Subject: [Matplotlib-devel] contract work? In-Reply-To: References: Message-ID: I'm able and interested. Ryan On Mon, Sep 24, 2018 at 2:51 PM Thomas Caswell wrote: > Folks, > > Out of curiosity, who on this list is able and willing to do Matplotlib > work on small/short-term contracts (either through NumFOCUS or directly > from a company)? > > Feel free to email me privately if you do not want to respond openly > about this. > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -- Ryan May -------------- next part -------------- An HTML attachment was scrubbed... URL: From juichenieder-nabb at yahoo.co.uk Mon Sep 24 21:25:19 2018 From: juichenieder-nabb at yahoo.co.uk (OceanWolf) Date: Tue, 25 Sep 2018 01:25:19 +0000 (UTC) Subject: [Matplotlib-devel] contract work? In-Reply-To: References: Message-ID: <1207410879.17331499.1537838719260@mail.yahoo.com> If I think I understand you correctly, then yes, please let me know :) From: Ryan May To: Thomas Caswell Cc: matplotlib development list Sent: Monday, 24 September 2018, 21:49 Subject: Re: [Matplotlib-devel] contract work? I'm able and interested. Ryan On Mon, Sep 24, 2018 at 2:51 PM Thomas Caswell wrote: Folks, Out of?curiosity, who on this list is able and willing to do Matplotlib work on small/short-term contracts (either through NumFOCUS or directly from a company)? Feel free to email me privately if you do not want to respond openly about?this. Tom -- Thomas Caswell tcaswell at gmail.com_______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel -- Ryan May _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Mon Sep 24 21:50:24 2018 From: ben.v.root at gmail.com (Benjamin Root) Date: Mon, 24 Sep 2018 21:50:24 -0400 Subject: [Matplotlib-devel] contract work? In-Reply-To: <1207410879.17331499.1537838719260@mail.yahoo.com> References: <1207410879.17331499.1537838719260@mail.yahoo.com> Message-ID: Is this going to be like bug bounty work, or contract work to add specific features, or something more high-level than that? On Mon, Sep 24, 2018 at 9:25 PM OceanWolf via Matplotlib-devel < matplotlib-devel at python.org> wrote: > If I think I understand you correctly, then yes, please let me know :) > > > ------------------------------ > *From:* Ryan May > *To:* Thomas Caswell > *Cc:* matplotlib development list > *Sent:* Monday, 24 September 2018, 21:49 > *Subject:* Re: [Matplotlib-devel] contract work? > > I'm able and interested. > > Ryan > > On Mon, Sep 24, 2018 at 2:51 PM Thomas Caswell wrote: > > Folks, > > Out of curiosity, who on this list is able and willing to do Matplotlib > work on small/short-term contracts (either through NumFOCUS or directly > from a company)? > > Feel free to email me privately if you do not want to respond openly > about this. > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > -- > Ryan May > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Tue Sep 25 10:23:52 2018 From: tcaswell at gmail.com (Thomas Caswell) Date: Tue, 25 Sep 2018 10:23:52 -0400 Subject: [Matplotlib-devel] contract work? In-Reply-To: References: <1207410879.17331499.1537838719260@mail.yahoo.com> Message-ID: Sorry for being cryptic. For context Ryan May and my self are at the NumFOCUS sustainability workshop [1] and one of the themes is how to connect companies (who have problems the want solved, cash, but developers with knowledege to fix the problems) with developers (who know how to solve the problems, but may not have time or motivation to solve said problems). Not everyone can take money for work (due to either contract or visia restrictions) so if a company came to me and said "We need issue XXX fixed, we can pay you $$", I do not know who I could direct that to. At this point it is all very preliminary, there is currently no money on offer and I can see several ways to organize this (through NumFOCUS, through one of several companies (both US and EU based) with varying business models, and direct freelance work). I am just testing the waters and starting to build an internal list of people who are available. Tom [1] https://www.numfocus.org/forum2018 On Mon, Sep 24, 2018 at 9:50 PM Benjamin Root wrote: > Is this going to be like bug bounty work, or contract work to add specific > features, or something more high-level than that? > > On Mon, Sep 24, 2018 at 9:25 PM OceanWolf via Matplotlib-devel < > matplotlib-devel at python.org> wrote: > >> If I think I understand you correctly, then yes, please let me know :) >> >> >> ------------------------------ >> *From:* Ryan May >> *To:* Thomas Caswell >> *Cc:* matplotlib development list >> *Sent:* Monday, 24 September 2018, 21:49 >> *Subject:* Re: [Matplotlib-devel] contract work? >> >> I'm able and interested. >> >> Ryan >> >> On Mon, Sep 24, 2018 at 2:51 PM Thomas Caswell >> wrote: >> >> Folks, >> >> Out of curiosity, who on this list is able and willing to do Matplotlib >> work on small/short-term contracts (either through NumFOCUS or directly >> from a company)? >> >> Feel free to email me privately if you do not want to respond openly >> about this. >> >> Tom >> >> -- >> Thomas Caswell >> tcaswell at gmail.com >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> >> >> -- >> Ryan May >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> > -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Tue Sep 25 13:40:08 2018 From: pmhobson at gmail.com (Paul Hobson) Date: Tue, 25 Sep 2018 10:40:08 -0700 Subject: [Matplotlib-devel] Fwd: [Numpy-discussion] PR Cleanup In-Reply-To: References: Message-ID: Would the MPL team be interested in something like this? -p ---------- Forwarded message --------- From: Marten van Kerkwijk Date: Tue, Sep 25, 2018 at 10:36 AM Subject: Re: [Numpy-discussion] PR Cleanup To: Discussion of Numerical Python Hi Chuck, Over at astropy we have a bot that sends a warning to PRs that have not received any commits for 5 months [1] and closes them if nothing happens in the next month, asking to open an issue instead. Despite my apprehensions, I found this worked quite well, drawing back attention to forgotten PRs (and forcing one to consider if they best remain forgotten). Would there be interest in such a scheme? All the best, Marten p.s. We don't do anything with issues. [1] Text of the astropy-bot warning: Hi humans [image: wave] - this pull request hasn't had any new commits for approximately 5 months. *I plan to close this in a month if the pull request doesn't have any new commits by then.* In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary. If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock. You may also consider sending a reminder e-mail about it to the astropy-dev mailing list . *If you believe I commented on this pull request incorrectly, please report this here .* _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion at python.org https://mail.python.org/mailman/listinfo/numpy-discussion -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Tue Sep 25 13:58:45 2018 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Tue, 25 Sep 2018 10:58:45 -0700 Subject: [Matplotlib-devel] Fwd: [Numpy-discussion] PR Cleanup In-Reply-To: References: Message-ID: I haven't looked too much into the astro-py bot, but I believe there is this github integration that does it: > https://github.com/apps/stale We all know that less things to maintain is always better. I haven't used it much either, but seen it in a couple of places. -- M On Tue, 25 Sep 2018 at 10:40, Paul Hobson wrote: > Would the MPL team be interested in something like this? > -p > > ---------- Forwarded message --------- > From: Marten van Kerkwijk > Date: Tue, Sep 25, 2018 at 10:36 AM > Subject: Re: [Numpy-discussion] PR Cleanup > To: Discussion of Numerical Python > > > Hi Chuck, > > Over at astropy we have a bot that sends a warning to PRs that have not > received any commits for 5 months [1] and closes them if nothing happens in > the next month, asking to open an issue instead. Despite my apprehensions, > I found this worked quite well, drawing back attention to forgotten PRs > (and forcing one to consider if they best remain forgotten). > > Would there be interest in such a scheme? > > All the best, > > Marten > > p.s. We don't do anything with issues. > > [1] Text of the astropy-bot warning: > > Hi humans [image: wave] - this pull request hasn't had any new commits > for approximately 5 months. *I plan to close this in a month if the pull > request doesn't have any new commits by then.* > > In lieu of a stalled pull request, please consider closing this and open > an issue instead if a reminder is needed to revisit in the future. > Maintainers may also choose to add keep-open label to keep this PR open > but it is discouraged unless absolutely necessary. > > If this PR still needs to be reviewed, as an author, you can rebase it to > reset the clock. You may also consider sending a reminder e-mail about it > to the astropy-dev mailing list > . > > *If you believe I commented on this pull request incorrectly, please > report this here .* > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion at python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: