Re: [Python-Dev] Very old git mirror under github user "python-git"

2016-02-28 Thread Georg Brandl 
On 02/27/2016 11:45 PM, Matthias Bussonnier wrote:
> Hi all, 
> 
> 
>> On Feb 27, 2016, at 14:21, Alexander Walters > > wrote:
>>
>> Can we even ask github to pull it down and reasonably expect them to comply?
>>  Their entire model is built on everyone forking everyone else.
> 
> Why the model is everyone forking, some of the help page of GitHub actually 
> tell
> you to contact GitHub support, like if you desire to "detach" a fork. 
> 
> Every reasonable requests I made to GitHub and the few interactions I had with
> the support always went well. 
> This did include asking GitHub to contact user as their pages were confusing,
> and might be misleading others.
> 
> So I would suggest 
> 
> 1) asking GitHub to contact author, potentially forwarding him/her a message
> from this list asking him/her to bring that down or transfer the control to 
> you.
> That should be easy to do as it will not force GitHub to provide anyone with 
> the
> emails of the the owner of python-git.
> 
> 2) in the case of no response from author ask politely GitHub that the repo is
> confusing for user, and ask what they can do about that.

These are both fine.  Although I don't see much confusion; there's bound to be
hundreds of forks of CPython, if not already, then definitely once we move to
GitHub.

> 3) If still nothing can be done make a DMCA request. You can likely argue that
> the logo/name are used without PSF content. 
> https://help.github.com/articles/dmca-takedown-policy/ 

Please no.  There is absolutely no call using such a blunt instrument, just for
a case of minor inconvenience.  It could also be blown up into a PR disaster,
probably rightly so.

cheers,
Georg

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Very old git mirror under github user "python-git"

2016-02-28 Thread Chris Angelico 
On Mon, Feb 29, 2016 at 4:46 AM, Georg Brandl  wrote:
> Although I don't see much confusion; there's bound to be
> hundreds of forks of CPython, if not already, then definitely once we move to
> GitHub.

Forks made within the GitHub interface aren't usually confusing. Up
the top of this repo, you can see where its upstream is, and therefore
where you would go to find the official version of this project:

https://github.com/Rosuav/appension

So a fork-esque that predates the official repo is a different beast.
+1 for asking GitHub to contact the owner, since it's not
intrinsically obvious who's maintaining that.

ChrisA
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Very old git mirror under github user "python-git"

2016-02-28 Thread Brett Cannon 
On Sun, 28 Feb 2016 at 09:58 Chris Angelico  wrote:

> On Mon, Feb 29, 2016 at 4:46 AM, Georg Brandl  wrote:
> > Although I don't see much confusion; there's bound to be
> > hundreds of forks of CPython, if not already, then definitely once we
> move to
> > GitHub.
>
> Forks made within the GitHub interface aren't usually confusing. Up
> the top of this repo, you can see where its upstream is, and therefore
> where you would go to find the official version of this project:
>
> https://github.com/Rosuav/appension
>
> So a fork-esque that predates the official repo is a different beast.
> +1 for asking GitHub to contact the owner, since it's not
> intrinsically obvious who's maintaining that.
>

Since this isn't being pushy I'm +1 as well. But who's going to ask?
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Very old git mirror under github user "python-git"

2016-02-28 Thread Chris Angelico 
On Mon, Feb 29, 2016 at 5:07 AM, Brett Cannon  wrote:
>
>
> On Sun, 28 Feb 2016 at 09:58 Chris Angelico  wrote:
>>
>> On Mon, Feb 29, 2016 at 4:46 AM, Georg Brandl  wrote:
>> > Although I don't see much confusion; there's bound to be
>> > hundreds of forks of CPython, if not already, then definitely once we
>> > move to
>> > GitHub.
>>
>> Forks made within the GitHub interface aren't usually confusing. Up
>> the top of this repo, you can see where its upstream is, and therefore
>> where you would go to find the official version of this project:
>>
>> https://github.com/Rosuav/appension
>>
>> So a fork-esque that predates the official repo is a different beast.
>> +1 for asking GitHub to contact the owner, since it's not
>> intrinsically obvious who's maintaining that.
>
>
> Since this isn't being pushy I'm +1 as well. But who's going to ask?

Someone who has the authority to represent Python, I hope. A member of
the PSF board?

ChrisA
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Very old git mirror under github user "python-git"

2016-02-28 Thread Paul Sokolovsky 
Hello,

On Sun, 28 Feb 2016 18:46:36 +0100
Georg Brandl  wrote:

[]

> > 3) If still nothing can be done make a DMCA request. You can likely
> > argue that the logo/name are used without PSF content. 
> > https://help.github.com/articles/dmca-takedown-policy/ 
> 
> Please no.  There is absolutely no call using such a blunt
> instrument, just for a case of minor inconvenience.  It could also be
> blown up into a PR disaster, probably rightly so.

I can't believe my eyes that I read such a thread already. The poor
repo clearly states it's unofficial mirror. Some dudes without much
clue (*1) submit pull requests against it. So what - someone getting
jealous? Well deserved - there could have been support for the leading
version control system and very popular hosting site long, long
ago.

But well, if you want those pull requests, go and add friendly note to
each along the lines "Hi, you submitted your PR against unattended,
unofficial mirror, there's now official Py repo at ..., we encourage
you to resubmit your patch against it". Nope, shutdown/exterminate.


*1: See username of the submitter of
https://github.com/python-git/python/issues/12

> 
> cheers,
> Georg

-- 
Best regards,
 Paul  mailto:[email protected]
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Very old git mirror under github user "python-git"

2016-02-28 Thread M.-A. Lemburg 
On 28.02.2016 18:46, Georg Brandl wrote:
> On 02/27/2016 11:45 PM, Matthias Bussonnier wrote:
>> Hi all, 
>>
>>
>>> On Feb 27, 2016, at 14:21, Alexander Walters >> > wrote:
>>>
>>> Can we even ask github to pull it down and reasonably expect them to comply?
>>>  Their entire model is built on everyone forking everyone else.
>>
>> Why the model is everyone forking, some of the help page of GitHub actually 
>> tell
>> you to contact GitHub support, like if you desire to "detach" a fork. 
>>
>> Every reasonable requests I made to GitHub and the few interactions I had 
>> with
>> the support always went well. 
>> This did include asking GitHub to contact user as their pages were confusing,
>> and might be misleading others.
>>
>> So I would suggest 
>>
>> 1) asking GitHub to contact author, potentially forwarding him/her a message
>> from this list asking him/her to bring that down or transfer the control to 
>> you.
>> That should be easy to do as it will not force GitHub to provide anyone with 
>> the
>> emails of the the owner of python-git.
>>
>> 2) in the case of no response from author ask politely GitHub that the repo 
>> is
>> confusing for user, and ask what they can do about that.
> 
> These are both fine.  Although I don't see much confusion; there's bound to be
> hundreds of forks of CPython, if not already, then definitely once we move to
> GitHub.
> 
>> 3) If still nothing can be done make a DMCA request. You can likely argue 
>> that
>> the logo/name are used without PSF content. 
>> https://help.github.com/articles/dmca-takedown-policy/ 
> 
> Please no.  There is absolutely no call using such a blunt instrument, just 
> for
> a case of minor inconvenience.  It could also be blown up into a PR disaster,
> probably rightly so.

I frankly don't understand what all the fuzz is about. The repo
in question hasn't been touched in 7 years. It refers to Python 2.7
alpha 0.

It also clearly reads "Unofficial Python SVN auto-updating mirror",
so there's no confusion either.

The talk about DMCA requests really doesn't apply. Python is
open-source. Anyone can fork it, at any version they like, as
long as the license is respected.

The trademark use is also perfectly in line with our TM policy.
The logo is a bit blurred, but that's really the only nit I could
find.

Asking the owner to take the repo down is still a good thought,
but there's definitely nothing wrong with it per se.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Feb 28 2016)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...   http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...   http://zope.egenix.com/

2016-02-19: Released eGenix PyRun 2.1.2 ...   http://egenix.com/go88

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
  http://www.malemburg.com/

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] [ANNOUNCE] fuzzpy

2016-02-28 Thread Brian Cain 
##

*---*
*fuzzpy: CPython fuzz tester is now available   *
*   *
*   Version 0.8 *
*https://bitbucket.org/ebadf/fuzzpy/*
*---*

I am pleased to announce the creation of a coverage-guided fuzz tester for
CPython.  It's a pretty small wrapper around LLVM's libFuzzer that enables
some powerful testing logic.  AFL (American Fuzzy Lop) is another popular
fuzzer lately -- libFuzzer is very similar in concept to AFL.  From what
I've read on list archives, Victor Stinner had previously done some good
fuzz testing on CPython using fusil.  This project should expand on that
concept.

I'd love to get feedback, suggestions, patches and anything else the list
can offer.


Q: What is fuzzpy for?
A: It's primarily for testing CPython itself, but could also be used for
individual python projects too.  Pure-python projects will be the simplest
to integrate at this point.  Also, interesting test cases output by fuzzpy
may end up being useful in testing others such as pypy, pyston, etc.

Q: What is a fuzz tester?
A: It modifies inputs to a test case in order to find unique/rare failures.

Q: What does "coverage-guided" mean?
A: It means that libFuzzer is able to witness the specific code executed as
a result of a given test case.  It feeds this information back into an
engine to modify the test cases to optimize for coverage.

Q: How can I help?
A1: donate cycles: build the project and crank away on one of the existing
tests.  Relative to other common fuzzing, it's awfully slow, so consider
throwing as many cycles as you can afford to.
A2: contribute tests: write a ~10-line python script that exercises a
feature that you think could benefit from fuzz testing.
A3: if there's interest, I can accept cryptocoin donations to purchase
cycles on a cloud server.


##


-- 
-Brian
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com