From balchandani.sanchit at gmail.com Sun Dec 1 04:01:49 2019 From: balchandani.sanchit at gmail.com (Sanchit Balchandani) Date: Sun, 1 Dec 2019 14:31:49 +0530 Subject: [Inpycon] PyConf Hyderabad 2019 | DevSprints Message-ID: Hi All, We are looking for Devsprint mentors for PyConf Hyderabad 2019 [1]. Devsprints will happen on 7th Dec at IIIT Hyderabad. To know about PyConf Hyderabad Devsprints please check this link [2]. If you are interested in mentoring for Devsprint, please submit a proposal by editing the GitHub wiki link [3]. Projects should be based primarily on Python but we are open to other open-source languages as well. Please reach out to us here[4] if you want any more details. [1]- https://pyconf.hydpy.org/2019/ [2]- https://github.com/HydPy/hydpyconf2019/wiki/PyConf-Hyderabad-2019-Devsprint [3]- https://github.com/HydPy/hydpyconf2019/wiki/PyConf-Hyderabad-2019-Devsprint/_edit [4]- contact at hydpy.org Thanks, Sanchit -------------- next part -------------- An HTML attachment was scrubbed... URL: From joinalahmed at gmail.com Mon Dec 2 13:28:02 2019 From: joinalahmed at gmail.com (JOINAL AHMED) Date: Mon, 2 Dec 2019 23:58:02 +0530 Subject: [Inpycon] Pyconf Hyderabad 2019 Tickets Message-ID: Hi, I have 2 tickets for Pyconf Hyderabad, wont be able to attend due to health issues. If anyone needs them, please connect with me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zerothabhishek at gmail.com Tue Dec 17 05:59:36 2019 From: zerothabhishek at gmail.com (Abhishek Yadav) Date: Tue, 17 Dec 2019 16:29:36 +0530 Subject: [Inpycon] Plagiarism at PyCon India Message-ID: Hello all, Hope you all had a good conference and are doing well. I'd like to bring your attention towards the problem of plagiarism. As a part of our work at the CFP workgroup this year we noticed quite a few instances of plagiarism. Content of some talk proposals seemed plagiarised, and some were reported to be. And there was a serious complain too after the event concluded. Since I could not find a policy or precedent on how to deal with it, we had to handle the complain in a somewhat ad-hoc manner. On a superficial level, it might seem simple, but when we go in to the intricacies there are things beyond common sense. Things such as - how much punishment is adequate ? What should be the mode and timeline of investigation? When should the content be taken down - at the beginning or at the end of the investigation ? Who should we consult when the technicalities of copyright laws are involved ? Also, we felt that the general attitude seems to be casual about this. Folks submitted slides from their colleagues presuming its okay since its the same company. Folks even lifted the entire content from someone else's website - one person even build a case for his talk (plagiarised) because his previous talk (also probably plagiarised) was selected. In the absence of clear consequences, it is easy to gamble - whats the worst that can happen ? In some cases, its also non-malicious. For example, there's this image: [1] that appears in far too many talks/proposals. People probably just copy it from the internet assuming its okay because everyone else is using it. PyCon India is (or has become) reputed enough to be watched everywhere (The complain this year was from a major American university). I think its time to have a serious policy on plagiarism, and to also educate the community better. I have put together a proposal in the form of pull request here - https://github.com/zerothabhishek/policies/pull/1/files Please take a look, and add your comments and suggestions right there. We're ideally looking for a consensus on things like acceptable punishments, steps to investigate, privacy etc, and the proposal can serve as a baseline. Plagiarism can be a big blot on our otherwise sincere effort as a community. And our inability to handle it professionally further degrades our reputation. Lets find a way to deal with it together. Regards, Abhishek [1] https://imgur.com/a/9FFWEza -------------- next part -------------- An HTML attachment was scrubbed... URL: