[Numpy-discussion] Re: welcome Raghuveer, Chris, Mateusz and Matt to the NumPy maintainers team

2024-01-27 Thread rgoswami

Welcome to the maintainers team, richly deserved, thanks for all the help so 
far and for taking on the responsibility of looking after your contributions :)

--- Rohit

On 1/27/24 5:13 PM, Melissa Mendonça  wrote:

Welcome all! Your contributions are greatly appreciated!

Cheers,

Melissa

On Fri, Jan 26, 2024 at 7:13 PM Stefan van der Walt via NumPy-Discussion 
mailto:numpy-discussion@python.org>> wrote:


__
On Fri, Jan 26, 2024, at 12:04, Ralf Gommers wrote:
> We've got four new NumPy maintainers! Welcome to the team, and
> congratulations to:
>
> - Raghuveer Devulapalli (https://github.com/r-devulap
> )
> - Chris Sidebottom (https://github.com/mousius
> )
> - Mateusz Sokół (https://github.com/mtsokol/
> )
> - Matt Haberland (https://github.com/mdhaber
> )

Fantastic! Your commit bits are well deserved, and your
contributions greatly appreciated.

I look forward to our continued work together.

Thank you,
Stéfan

___
NumPy-Discussion mailing list -- numpy-discussion@python.org

To unsubscribe send an email to numpy-discussion-le...@python.org

https://mail.python.org/mailman3/lists/numpy-discussion.python.org/

Member address: meliss...@gmail.com 


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: rgosw...@quansight.com


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com


[Numpy-discussion] Re: Policy on AI-generated code

2024-07-04 Thread rgoswami

From a quick look, it seems like some of these (the masked array ones) are 
trivial enough to not warrant inclusion and the ctypes snippet is obvious 
enough that copyright claims won't be an issue. In terms of broader policy I 
don't really have much to say, except that in general it is probably hopeless 
to enforce a ban on AI generated content.


--- Rohit

On 7/4/24 4:59 AM, Loïc Estève via NumPy-Discussion 
 wrote:

Hi,

in scikit-learn, more of a FYI than some kind of policy (amongst other
things it does not even mention explicitly "AI" and avoids the licence
discussion), we recently added a note in our FAQ about "fully automated
tools":
https://github.com/scikit-learn/scikit-learn/pull/29287

 From my personal experience in scikit-learn, I am very skeptical about
the quality of this kind of contributions so far ... but you know future
may well prove me very wrong.

Cheers,
Loïc

> Hi,
>
> We recently got a set of well-labeled PRs containing (reviewed)
> AI-generated code:
>
> https://github.com/numpy/numpy/pull/26827
> https://github.com/numpy/numpy/pull/26828
> https://github.com/numpy/numpy/pull/26829
> https://github.com/numpy/numpy/pull/26830
> https://github.com/numpy/numpy/pull/26831
>
> Do we have a policy on AI-generated code?   It seems to me that
> AI-code in general must be a license risk, as the AI may well generate
> code that was derived from, for example, code with a GPL-license.
>
> Cheers,
>
> Matthew
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> Member address: loic.est...@ymail.com
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: rgosw...@quansight.com


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com


[Numpy-discussion] Re: Policy on AI-generated code

2024-07-04 Thread rgoswami

Personally, I wouldn't (as a maintainer) take a decision to reject code based 
on if I feel it is generated by AI. It is much easier to rule on the quality of 
the contribution itself, and as noted, at least so far the AI only 
contributions are very probably not going to clear the barrier of being useful 
in their own right.

We are a large, visible project, but I think it is weirder to have a policy and 
fail to enforce it (e.g. don't use NumPy for military purposes, never us an AI 
tool etc). than to not have a specific policy at all.

--- Rohit

On 7/4/24 3:03 PM, Daniele Nicolodi  wrote:

On 04/07/24 12:49, Matthew Brett wrote:
> Hi,
>
> Sorry to top-post!  But - I wanted to bring the discussion back to
> licensing.  I have great sympathy for the ecological and code-quality
> concerns, but licensing is a separate question, and, it seems to me,
> an urgent question.

The licensing issue is complex and it is very likely that it will not 
get a definitive answer until a lawsuit centered around this issue is 
litigated in court. There are several lawsuits involving similar issues 
ongoing, but any resolution is likely to take several years.


Providing other, much more pragmatic and easier to gauge, reasons to 
reject AI generated contributions, I was trying to sidestep the 
licensing issue completely.


If there are other reasons why auto-generated contributions should be 
rejected, there is no need to solve the much harder problem of 
licensing: we don't want them regardless of the licensing issue.


Cheers,
Dan

___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: rgosw...@quansight.com


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com


[Numpy-discussion] Re: Welcome Joren Hammudoglu to the NumPy Maintainers Team

2024-08-19 Thread rgoswami

Thanks for your efforts and commitment to the project.
--- Rohit

On 8/19/24 6:05 AM, matti picus  wrote:

Welcome Joren, thanks for all the work
Matti


On Mon, Aug 19, 2024 at 1:41 PM Sebastian Berg
 wrote:
>
> Hi all,
>
> please join me in welcoming Joren (https://github.com/jorenham) to the
> NumPy maintainers team.
>
> Joren has done a lot of work recently contributing, reviewing, and
> maintaining typing related improvements to NumPy.
> We are looking forward to see new momentum to improve NumPy typing.
>
> Thanks for all the contributions!
>
> Cheers,
>
> Sebastian
>
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> Member address: matti.pi...@gmail.com
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: rgosw...@quansight.com


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com


[Numpy-discussion] Re: (no subject)

2024-09-23 Thread rgoswami

Hi, could you share some of the issues with OpenBLAS? It'd be great to discuss 
incorporating the new meson-build work (by me and Mateusz, here: 
https://github.com/HaoZeke/OpenBLAS/tree/mesonBasic) with the PR you've been 
working on.
--- Rohit

On 9/23/24 1:00 PM, "slobodan.miletic--- via NumPy-Discussion" 
 wrote:

Hi,

I made the second PR for full wheel with openblas. It is reviewed, but solution 
with openblas is not good enough, so I am investigating alternate options for 
cross compiling openblas.
While I am working on this I have one question about the wheel without 
OpenBLAS. As the job is now created on the main it can be triggered manually 
and the produced wheel can be used for publishing to PyPi. I'm wondering what 
the next steps are with this build. Is it planned for the wheel to be 
built/published without OpenBLAS and what would be the conditions for that.
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: rgosw...@quansight.com


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com