Re: [Numpy-discussion] NumPy Proposal

[Melissa Mendonça]

Hello, Kiran, thank you for your proposal.

It would be good to see examples of technical writing - remember that the
Season of Docs program is meant for people with some experience in that
area, so if you have anything to share, please do.

Cheers,

Melissa

On Mon, May 3, 2021 at 5:11 PM KiranKhanna  wrote:

> Respected ma’am / sir
>
>
>
>   I am Kiran Khanna , I am a B.Tech second year Computer
> science with AI engineering student . I am very interested to contribute in
> the NumPy organization . I have attached my proposal below , Guide me how I
> can improve myself .
>
>
>
> Thanking You,
>
> Your faithfully ,
>
> Kiran Khanna
>
>
>
> Sent from Mail  for
> Windows 10
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoD '21 Statement of Interest

[Melissa Mendonça]

Thank you, Mukilika - I really like your ideas for tutorials! The timeline
also looks fine to me.

Cheers,

Melissa

On Mon, May 3, 2021 at 9:07 AM Mukulika Pahari 
wrote:

> Hello everyone,
> I am attaching my Statement of Interest for GSoD 2021 below. I would love
> to know everyone's thoughts on it.
>
> Thank you!
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] GSoD 2021 - Statement of Interest

[Melissa Mendonça]

Hello, Mahesh

Yes, the timeline looks fine.

Cheers,

Melissa

On Sun, May 2, 2021 at 2:08 PM Mahesh S  wrote:

> Hello there Melissa,
>
> Thank You for your valuable suggestion.Actually , I am planning for a
> high-impact work. I have already started reading the User-Guide and working
> out small projects using NumPy to understand it further, to prepare an
> in-depth proposal, which will include changes which I mentioned in my brief
> proposal, reorganizing content, addressing issues in the GitHub tracker and
> all. One doubt from my side is regarding the timeline. Currently I am
> planning to prepare the proposal with the GSoD Timeline that is from June
> 16 2021 and ends on November 16th 2021 with four evaluation phases ,
> Is there any specific timeline from the community or Am I free to follow
> the same?
>
> And  as of now, I am planning to set an order in which the tasks needed to
> be done , which I will share in the first draft of my proposal which I will
> submit by this week, later changes can be done as per suggestions from the
> mentors and community.
>
> Thank You
> Mahesh
>
> On Sun, May 2, 2021 at 7:05 PM Melissa Mendonça 
> wrote:
>
>> Hello, Mahesh
>>
>> While you work on this, it may be interesting to keep in mind that we are
>> looking for high-impact work that can be done in the timeframe of the GSoD
>> program - examples would be reorganizing content in a section of the
>> documentation, creating new complete document pages on some subject or
>> concept. It may be worth familiarizing yourself with the documentation (I
>> won't suggest reading all of it as it's huge!) to get an idea for the
>> different sections. One idea would be to focus on the user guide, which
>> contains several sub-pages, and check for improvements that can be done
>> there.
>>
>> Cheers,
>>
>> Melissa
>>
>> On Fri, Apr 30, 2021 at 9:28 AM Mahesh S 
>> wrote:
>>
>>> Hi there,
>>>
>>> The current documentation of NumPy is really good but a bit more
>>> improvement can be made to it, which is the prime objective of my project.
>>> The improvements which I mentioned in my brief proposal are strategies that
>>> can be applied to every documentation to make it better.
>>>
>>> Apart from general improvements most the documentation related issues in
>>> the NumPy's GitHub issue tracker
>>> 
>>>  will
>>> be addressed. . Some needs more technical information and help from the
>>> community. Some are due to the lack of visual aids. Most of them will be
>>> addressed and improvements will be made such that similar issues will not
>>> be generated in future.
>>> Rearranging of sections in the User Guide
>>>  can be done
>>> after further discussions
>>>
>>> Some examples regarding the need of restructuring and duplication are
>>> given in the attached document. Apologies in advance if my observations are
>>> inaccurate or nitpicks. The given doc is just a very brief one. An in-depth
>>> proposal with all the planned changes along with solutions to close as many
>>> issues in the tracker will be prepared. I am getting familiar with the
>>> community and NumPy.
>>>
>>>
>>> On Thu, Apr 29, 2021 at 9:54 PM Melissa Mendonça 
>>> wrote:
>>>
 Hello, Mahesh

 Thank you for your proposal. One thing I would say is that some of the
 things you are suggesting are already there - for example, the How-tos and
 Explanations section - but I agree they can be improved!

 Another question I could pose is about duplication of content: can you
 give examples of duplicated content that you found in the docs?

 Cheers,

 Melissa

 On Wed, Apr 28, 2021 at 12:33 AM Mahesh S 
 wrote:

> Hello,
>
> I am Mahesh from India. I am interested in doing Google Season of Docs
> with NumPy on the project HIGH-LEVEL RESTRUCTURING AND END-USER FOCUS -
> NumPy
>
> I have past experience in documentation writing with WordPress and
> have completed *Google Summer of Code 2018 *with KDE. I have been an
> open source enthusiast and contributor since 2017.My past experience with
> coding ,code documentation , understanding code bases ,will help achieve
> this task without much input from your end. I have about four years
> experience working with Open-Source and currently working as a *Quality
> Assurance specialis*t . I have delivered technical talks at
> international conferences (KDE-Akademy) and was *mentor of Google
> Code-In* also. All these makes me the best candidate for the project.
>
> I am attaching a brief proposal for the work along with this mail. A
> more in-depth  A more in depth proposal with timelines , all planned
> strategies , document structures will be submitted after more discussion
> with the mentors and community.
> I am ready to start 

Re: [Numpy-discussion] Prospective technical writer for GSoD 2021 under NumPy

[Melissa Mendonça]

Hello, Ronnie

Thank you for your interest!

Based on our projects page, do you have any specific ideas for working on
NumPy? Because the deadline for hiring technical writers is so close (May
17) it might be worth thinking of writing your Statement of Interest as
soon as possible.

Let me know if you have further questions.

Cheers,

Melissa

On Mon, May 3, 2021 at 4:21 AM Ronnie Gandhi 
wrote:

> Hello,
>
> I am Ronnie Gandhi, a Computer Science undergrad from IIT Roorkee in my
> final year.I am interested in working on NumPy's documentation problem
> statement "HIGH-LEVEL RESTRUCTURING AND END-USER FOCUS - NumPy".
>
> I have successfully completed *GSoD2020
> *(my
> display name is Krezhairo) under *LibreOffice*, I have done* GSoC 2019*,
> and *2020 *under CGAL, and I have been contributing to open-source
> development for quite a while. I have also done Data Science internships at
> *Microsoft*, Hyderabad in 2019 and 2020.
>
> I am very well versed with GitHub, git, and CLI tools. Also from my past
> GSoD2020 experience I know Sphinx, Markdown, reStructuredText, XML as well.
>
> In terms of technical writing experience,
>
>- Under the Season of Docs 2020 program, I was given an opportunity to
>populate the wiki pages for the Calc functions of LibreOffice. I updated
>and populated the wiki pages for 340 of Calc functions in many categories
>for which the documentation was quite shallow and incomplete on the wiki
>pages.
>   - For some of the examples of previous technical writing that I
>   have successfully completed in GSoD 2020 under LibreOffice where I
>   edited/populated 340+ sparse wiki pages of Calc functions. Some of the
>   examples are as follows:
>   -
>  
> https://wiki.documentfoundation.org/Documentation/Calc_Functions/YIELDDISC
>
>  -
>  
> https://wiki.documentfoundation.org/Documentation/Calc_Functions/CHIDIST
>
>  -
>  https://wiki.documentfoundation.org/Documentation/Calc_Functions/SIN
>
>  -
>  
> https://wiki.documentfoundation.org/Documentation/Calc_Functions/DAVERAGE
>  -
>  
> https://wiki.documentfoundation.org/Documentation/Calc_Functions/Guidelines
>   If you want to look into more examples, you can find them here:
>   
> https://wiki.documentfoundation.org/Documentation/Calc_Functions/List_of_Functions
>  (this
>   is the new link where the "Find Functions" page is shifted sorry for the
>   blank page)
>
>
>
>- I have also had created the developer docs as a part of my GSoC2019
>and GsoC2020 program updating my progress under CGAL org. (some
>screenshots to the work since it is behind login wall
>
> )(although
>no important data)
>
> For my c++ experience,
>
>- My GSoC2019
>
> 
> and GSoC2020
>
>  
> projects
>were completely in C++ and Qt5 (my display name is Krezhairo).
>
> For my python experience,
>
>- As a data scientist intern at Microsoft, a large part of my work was
>in python and jupyter notebook. I have had multiple occasions to use NumPy.
>
> My GitHub link: https://github.com/RonnieGandhi
>
> I am attaching my detailed resume for your reference.
>
> Looking forward to hearing from you soon.
>
> Kind regards,
> Ronnie
>
>
>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Catching array shape errors using the type checker

[bas van beek]

Hi Matthew and Pradeep,

Do you know if the typing summit will be recorded and if these will be made 
available later?
While I’d love to attend the live event, this is unfortunately not possible due 
to other obligations that day.

Regards, Bas

From: NumPy-Discussion 
 On Behalf Of 
Matthew Rahtz
Sent: 04 May 2021 22:17
To: numpy-discussion@python.org
Cc: Pradeep Kumar Srinivasan 
Subject: [Numpy-discussion] Catching array shape errors using the type checker

Hi all,

Tl;dr: come to our talk Catching Tensor Shape Errors Using the Type Checker at 
the PyCon 2021 Typing Summit next week! 
https://us.pycon.org/2021/summits/typing/

Longer version: over the past year a small group of us have been thinking about 
how to use Python's type system to make tensor/array shape information more 
visible, and to catch shape errors automatically using type checkers. In this 
talk we'll discuss our tentative solution, talking about a) how it works, b) 
some examples of what it looks like in practice, and c) what its limitations 
are.

Hope to see you there!
Matthew and Pradeep
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] NumPy Proposal

[KiranKhanna]

HelloI am Second year B.Tech Computer with AI student , In every semester we are suppose to right research paper and report , One of our  research paper got publish in IEEE and recently I have started writing some blogs . In Numpy I have done two projects based on Data science and Machine learning . I have attached a link to our research paper .https://ieeexplore.ieee.org/document/9243510  Sent from Mail for Windows 10 From: Melissa MendonçaSent: 05 May 2021 02:28To: Discussion of Numerical PythonSubject: Re: [Numpy-discussion] NumPy Proposal Hello, Kiran, thank you for your proposal.  It would be good to see examples of technical writing - remember that the Season of Docs program is meant for people with some experience in that area, so if you have anything to share, please do. Cheers, Melissa On Mon, May 3, 2021 at 5:11 PM KiranKhanna  wrote:Respected ma’am / sir   I am Kiran Khanna , I am a B.Tech second year Computer science with AI engineering student . I am very interested to contribute in the NumPy organization . I have attached my proposal below , Guide me how I can improve myself . Thanking You,Your faithfully ,Kiran Khanna Sent from Mail for Windows 10 ___NumPy-Discussion mailing listNumPy-Discussion@python.orghttps://mail.python.org/mailman/listinfo/numpy-discussion 
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

[Sebastian Berg]

Hi all,

Our bi-weekly triage-focused NumPy development meeting is Wednesday,
May 5th at 11 am Pacific Time (18:00 UTC).
Everyone is invited to join in and edit the work-in-progress meeting
topics and notes:
https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg

I encourage everyone to notify us of issues or PRs that you feel should
be prioritized, discussed, or reviewed.

Best regards

Sebastian




___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Catching array shape errors using the type checker

[Matthew Rahtz]

Hi all,

Tl;dr: come to our talk *Catching Tensor Shape Errors Using the Type
Checker* at the PyCon 2021 Typing Summit next week!
https://us.pycon.org/2021/summits/typing/

Longer version: over the past year a small group of us have been thinking
about how to use Python's type system to make tensor/array shape
information more visible, and to catch shape errors automatically using
type checkers. In this talk we'll discuss our tentative solution, talking
about a) how it works, b) some examples of what it looks like in practice,
and c) what its limitations are.

Hope to see you there!
Matthew and Pradeep
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion