From fperez.net at gmail.com Wed Dec 21 22:02:17 2016 From: fperez.net at gmail.com (Fernando Perez) Date: Wed, 21 Dec 2016 19:02:17 -0800 Subject: [IPython-dev] Code of Conduct and Community Guidelines PR ready for feedback Message-ID: Hi all, it has taken us far longer than it should, but thanks to the persistent work of a number of folks on the team, we finally have a PR ready for public feedback! https://github.com/jupyter/governance/pull/23/ These community guidelines/CoC documents were inspired by the ones from the Django team (https://www.djangoproject.com/conduct), which seemed to us as having some important qualities: - Validated by real-world experience from a large and active project and community. - It highlights the positive reasons why all guidelines are the way they are: across the guide, there's an emphasis on how it is a guide for building a better community in the face of complex and challenging interactions, rather than simply a laundry list of "mandated don'ts". I personally find that approach much more productive in the long run. I want to emphasize that while the PR appears as mostly mine, this work was done in conjunction with many others mostly during our most recent in-person project meeting at Cal Poly, and this PR should be seen as the official proposal from the project's Steering Committee and other core developers present at that meeting. We welcome input and feedback on the PR and are open to clarifying/refining specifics, but we're committed to moving forward with something very much along these lines. If someone feels very strongly that we should not have these guidelines in the first place, it may not be worth your time trying to argue that point, as the decision to adopt them is a done deal. Multiple people have helped with the drafting and tuning of these documents for our project, even if we started with the excellent base provided by the Django team. I'd like to particularly thank Reese Netro (without her dedication this task would have lingered in my perpetually late todo list til who knows when), Ana Ruvalcaba, Carol Willing and Yuvi Panda, who put in a lot of extra time to make it happen, as well as the excellent points about CoCs made by Safia Abdalla in her newsletter ( http://tinyletter.com/captainsafia). Please provide any feedback you may have on the PR, as usual, and we'll all do our best to respond. We'd like to merge this sooner rather than later (ideally by the new year, though given folks' travel/holiday schedule we may slip by a few days). One final note: if you'd like to help us with translations of these docs, great!! We have an issue open for that: https://github.com/jupyter/governance/issues/28. Thanks again everyone, and sorry this took so long :) Cheers, -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail -------------- next part -------------- An HTML attachment was scrubbed... URL: From fperez.net at gmail.com Fri Dec 23 17:19:01 2016 From: fperez.net at gmail.com (Fernando Perez) Date: Fri, 23 Dec 2016 14:19:01 -0800 Subject: [IPython-dev] Code of Conduct and Community Guidelines PR ready for feedback In-Reply-To: References: Message-ID: On Wed, Dec 21, 2016 at 7:02 PM, Fernando Perez wrote: > > it has taken us far longer than it should, but thanks to the persistent > work of a number of folks on the team, we finally have a PR ready for > public feedback! > > https://github.com/jupyter/governance/pull/23/ > oops, one more thing I completely forgot to include in the original email! While we have framed the composition of the committee that would handle this as the responsibility of the Steering Council, it doesn't mean its *members* have to be all from the SC, quite the opposite. We want, and should have, a mix, so we'd love to ask for folks from the community who'd like to volunteer to be part of this team, whether you are in the SC or not. If you'd like to do so via PR, feel free to comment in the PR issue with a short note about why you'd like to help and any relevant experience you may have (if so, it's not like we're asking for a CV, but it helps if you have already participated in similar setups elsewhere). If you prefer to do so privately, feel free to send a short email to conduct at jupyter.org. Thanks to everyone who has responded on the PR with input/fixes/questions, I'll be back on it shortly :) Cheers f -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Tue Dec 27 08:50:46 2016 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Tue, 27 Dec 2016 14:50:46 +0100 Subject: [IPython-dev] GitHub Automation, migrating issues. Message-ID: Hi all, [Cross posting IPython-dev and Jupyter Google group] Hope you are enjoying the lasts few days of 2016 ! I've been recently working on GitHub automation, in particular we have local scripts that we need to run locally to do some common tasks on github, like migrating issues, backporting PR... etc. It is a bit inconvenient as you have to interrupt your workflow, go to a terminal, and issues commands you never remember the syntax, and need to copy/past issues url. So I decided to write a bot to do some of these chores for us when it is mentioned. Right now it only respond to a limited number of commands, but you should be able to activate it on any repository and it will respond to commands as long as you are admin (migration requires you to be admin on both repositories, for example). You do _not_ need to host it. It is hardcoded (for now) to respond only to me, but I can easily whitelist more people if asked[4]. For now I've name it Mr Meeseeks, which you will understand if you've seen Rick and Morty season 1. Otherwise you can watch the relevant part [1]. Here is the first example of usage on the IPython and Jupyter org[2]: > @Meeseeksdev[bot] migrate to jupyter/qtconsole Replicated issue ipython/ipython#1322 to jupyter/qtconsole#177 [3] Mr Meeseeks also know how to backport PR for small repositories (cherry pick -m merge commit) and submit a PR on the branch you;d like to backport to. On a merged PR: > @Meeseeksdev[bot] backport to 1.x I'm hoping to extend that a bit to extend the functionalities and let user tag/untag (with a limited set of tag ?). There is a bunch of possibility but right now this is using a GitHub Beta API so things possible are limited. At some point it could allow a number of truster user to be able have a finer grain permission model than GitHub and let everyone access to issue tagging/closing/opening, restarting test without always giving commit rights. I'm thinking about how to have per org/repo configuration/customisation/isolation. I'm also hoping to convince GitHub to extend their API to allow for automatic fixes on PR and/or help to find workaround the limitations. This mail is already a bit long, I'll develop how we can improve this somewhere else. If you have any questions ... Cheers, -- Matthias [1]: Warning, "Rick and Morty" is known to have harsh language and character behavior. This extract should be relatively gentle though. https://www.youtube.com/watch?v=qUYvIAP3qQk (duration 1min8sec) [2]: https://github.com/ipython/ipython/issues/1322#issuecomment-269317754 [3]: https://github.com/jupyter/qtconsole/issues/177 [4]: https://github.com/MeeseeksBox/ From jon.freder at gmail.com Tue Dec 27 11:47:14 2016 From: jon.freder at gmail.com (Jonathan Frederic) Date: Tue, 27 Dec 2016 16:47:14 +0000 Subject: [IPython-dev] [jupyter] GitHub Automation, migrating issues. In-Reply-To: References: Message-ID: I love the name of the bot! On Tue, Dec 27, 2016, 5:50 AM Matthias Bussonnier < bussonniermatthias at gmail.com> wrote: > Hi all, > > [Cross posting IPython-dev and Jupyter Google group] > > Hope you are enjoying the lasts few days of 2016 ! > > I've been recently working on GitHub automation, in particular we have > local scripts that we need to run locally to do some common tasks on > github, like migrating issues, backporting PR... etc. > > It is a bit inconvenient as you have to interrupt your workflow, go to > a terminal, and issues commands you never remember the syntax, and > need to copy/past issues url. So I decided to write a bot to do some > of these chores for us when it is mentioned. > > Right now it only respond to a limited number of commands, but you > should be able to activate it on any repository and it will respond to > commands as long as you are admin (migration requires you to be admin > on both repositories, for example). You do _not_ need to host it. > > It is hardcoded (for now) to respond only to me, but I can easily > whitelist more people if asked[4]. > > For now I've name it Mr Meeseeks, which you will understand if you've > seen Rick and Morty season 1. Otherwise you can watch the relevant > part [1]. > > Here is the first example of usage on the IPython and Jupyter org[2]: > > > @Meeseeksdev[bot] migrate to jupyter/qtconsole > > Replicated issue ipython/ipython#1322 to jupyter/qtconsole#177 [3] > > Mr Meeseeks also know how to backport PR for small repositories > (cherry pick -m merge commit) and submit a PR on the branch you;d like > to backport to. On a merged PR: > > > @Meeseeksdev[bot] backport to 1.x > > I'm hoping to extend that a bit to extend the functionalities and let > user tag/untag (with a limited set of tag ?). There is a bunch of > possibility but right now this is using a GitHub Beta API so things > possible are limited. > > At some point it could allow a number of truster user to be able have > a finer grain permission model than GitHub and let everyone access to > issue tagging/closing/opening, restarting test without always giving > commit rights. I'm thinking about how to have per org/repo > configuration/customisation/isolation. I'm also hoping to convince > GitHub to extend their API to allow for automatic fixes on PR and/or > help to find workaround the limitations. > > This mail is already a bit long, I'll develop how we can improve this > somewhere else. > > If you have any questions ... > > Cheers, > -- > Matthias > > [1]: Warning, "Rick and Morty" is known to have harsh language and > character behavior. This extract should be relatively gentle though. > https://www.youtube.com/watch?v=qUYvIAP3qQk (duration 1min8sec) > [2]: https://github.com/ipython/ipython/issues/1322#issuecomment-269317754 > [3]: https://github.com/jupyter/qtconsole/issues/177 > [4]: https://github.com/MeeseeksBox/ > > -- > You received this message because you are subscribed to the Google Groups > "Project Jupyter" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jupyter+unsubscribe at googlegroups.com. > To post to this group, send email to jupyter at googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jupyter/CANJQusUXf0nigFYmmMLfbVhdLnbn8gOW8sMiXQ-HL2Hqz51cWg%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From varunaseneviratna at gmail.com Wed Dec 28 03:11:53 2016 From: varunaseneviratna at gmail.com (Varuna Seneviratna) Date: Wed, 28 Dec 2016 13:41:53 +0530 Subject: [IPython-dev] Why does Ipython console does not start from inside spyder when Kaspersky Internet Security is running? Message-ID: Ipython Console starts from inside Spyder when Kaspersky Internet Security 2016 is not running But otherwise the Ipython console displays the two lines 'Kernel died restarting, Kernel died restarting' and stops responding. The OS is Windows 10 Thanks, Varuna -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Wed Dec 28 05:33:56 2016 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Wed, 28 Dec 2016 11:33:56 +0100 Subject: [IPython-dev] Why does Ipython console does not start from inside spyder when Kaspersky Internet Security is running? In-Reply-To: References: Message-ID: Hi Varuna, Kaspersky Internet Security is likely blocking some connections Spyder and IPython are making to each other as it is incorrectly finding them suspicious. I would go into Kaspersky settings and try to find a setting to whitelist Spyder/IPython and deactivate any filtering for them. I don't have this software available, but I found this, which may guide you through the steps: https://support.kaspersky.com/11146#block1 Cheers, -- M On Wed, Dec 28, 2016 at 9:11 AM, Varuna Seneviratna wrote: > Ipython Console starts from inside Spyder when Kaspersky Internet Security > 2016 is not running But otherwise the Ipython console displays the two lines > 'Kernel died restarting, Kernel died restarting' and stops responding. The > OS is Windows 10 > > > Thanks, > Varuna > > > > > > > > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > From damianavila at gmail.com Wed Dec 28 07:26:37 2016 From: damianavila at gmail.com (=?UTF-8?Q?Dami=C3=A1n_Avila?=) Date: Wed, 28 Dec 2016 09:26:37 -0300 Subject: [IPython-dev] [jupyter] GitHub Automation, migrating issues. In-Reply-To: References: Message-ID: Nice work Matthias! Thanks! 2016-12-27 13:47 GMT-03:00 Jonathan Frederic : > I love the name of the bot! > > On Tue, Dec 27, 2016, 5:50 AM Matthias Bussonnier < > bussonniermatthias at gmail.com> wrote: > >> Hi all, >> >> [Cross posting IPython-dev and Jupyter Google group] >> >> Hope you are enjoying the lasts few days of 2016 ! >> >> I've been recently working on GitHub automation, in particular we have >> local scripts that we need to run locally to do some common tasks on >> github, like migrating issues, backporting PR... etc. >> >> It is a bit inconvenient as you have to interrupt your workflow, go to >> a terminal, and issues commands you never remember the syntax, and >> need to copy/past issues url. So I decided to write a bot to do some >> of these chores for us when it is mentioned. >> >> Right now it only respond to a limited number of commands, but you >> should be able to activate it on any repository and it will respond to >> commands as long as you are admin (migration requires you to be admin >> on both repositories, for example). You do _not_ need to host it. >> >> It is hardcoded (for now) to respond only to me, but I can easily >> whitelist more people if asked[4]. >> >> For now I've name it Mr Meeseeks, which you will understand if you've >> seen Rick and Morty season 1. Otherwise you can watch the relevant >> part [1]. >> >> Here is the first example of usage on the IPython and Jupyter org[2]: >> >> > @Meeseeksdev[bot] migrate to jupyter/qtconsole >> >> Replicated issue ipython/ipython#1322 to jupyter/qtconsole#177 [3] >> >> Mr Meeseeks also know how to backport PR for small repositories >> (cherry pick -m merge commit) and submit a PR on the branch you;d like >> to backport to. On a merged PR: >> >> > @Meeseeksdev[bot] backport to 1.x >> >> I'm hoping to extend that a bit to extend the functionalities and let >> user tag/untag (with a limited set of tag ?). There is a bunch of >> possibility but right now this is using a GitHub Beta API so things >> possible are limited. >> >> At some point it could allow a number of truster user to be able have >> a finer grain permission model than GitHub and let everyone access to >> issue tagging/closing/opening, restarting test without always giving >> commit rights. I'm thinking about how to have per org/repo >> configuration/customisation/isolation. I'm also hoping to convince >> GitHub to extend their API to allow for automatic fixes on PR and/or >> help to find workaround the limitations. >> >> This mail is already a bit long, I'll develop how we can improve this >> somewhere else. >> >> If you have any questions ... >> >> Cheers, >> -- >> Matthias >> >> [1]: Warning, "Rick and Morty" is known to have harsh language and >> character behavior. This extract should be relatively gentle though. >> https://www.youtube.com/watch?v=qUYvIAP3qQk (duration 1min8sec) >> [2]: https://github.com/ipython/ipython/issues/1322# >> issuecomment-269317754 >> [3]: https://github.com/jupyter/qtconsole/issues/177 >> [4]: https://github.com/MeeseeksBox/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Project Jupyter" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jupyter+unsubscribe at googlegroups.com. >> To post to this group, send email to jupyter at googlegroups.com. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/jupyter/CANJQusUXf0nigFYmmMLfbVhdLnbn8gOW8sMiXQ-HL2Hqz51cWg%40mail. >> gmail.com. >> For more options, visit https://groups.google.com/d/optout. >> > > _______________________________________________ > IPython-dev mailing list > IPython-dev at scipy.org > https://mail.scipy.org/mailman/listinfo/ipython-dev > > -- *Dami?n Avila* -------------- next part -------------- An HTML attachment was scrubbed... URL: From fperez.net at gmail.com Fri Dec 30 17:21:39 2016 From: fperez.net at gmail.com (Fernando Perez) Date: Fri, 30 Dec 2016 14:21:39 -0800 Subject: [IPython-dev] [jupyter] GitHub Automation, migrating issues. In-Reply-To: References: Message-ID: On Tue, Dec 27, 2016 at 5:50 AM, Matthias Bussonnier < bussonniermatthias at gmail.com> wrote: > Hi all, > > [Cross posting IPython-dev and Jupyter Google group] > > Hope you are enjoying the lasts few days of 2016 ! > > I've been recently working on GitHub automation, in particular we have > local scripts that we need to run locally to do some common tasks on > github, like migrating issues, backporting PR... etc. > [...] Matthias, this is excellent, many thanks! Once you're happy with the workflow and perhaps a few more folks have kicked the tires, this would make a great little team tutorial/demo that we can record and have available for the future... Happy New Year! Cheers f -------------- next part -------------- An HTML attachment was scrubbed... URL: