|
From: | nikita pinto |
Subject: | Re: Contribution to Communications Toolbox? |
Date: | Thu, 24 Mar 2016 10:24:51 +0530 |
Also, is there any way you'll would recognize my contributions?Maybe in the form of a certificate or a letter, because it's something that I'd like to have on my work profile when applying to Graduate programs?Nevertheless, I'd still love to contribute to the toolbox.Nikita.On Sun, Mar 20, 2016 at 9:04 AM, nikita pinto <address@hidden> wrote:Hi Mike,
I've already checked out the missing functions list.
I'll go through your guidelines and submit functions as and when I complete them.
Thanks for the opportunity,
Nikita.
> On Mar 20, 2016, at 7:49 AM, Mike Miller <address@hidden> wrote:
>
>> On Sat, Mar 19, 2016 at 11:46:55 +0530, nikita pinto wrote:
>> Hi,
>>
>> I'm an Electronics and Telecommunication Engineering Undergraduate senior
>> from India.
>> Is there an opportunity for me to contribute to the communications toolbox?
>> I have experience in Matlab, and I'm also working on function development
>> for Scilab.
>> The work I'm doing is related to the Communications toolbox. So given my
>> experience, I feel like I can help out with whatever functions are left to
>> be coded. I checked the Source Forge page and it seems that I've already
>> implemented some of the functions that are yet to be coded.
>
> Yes please. If you have specific functions you'd like to contribute to
> the communications package, you can post them on our patch tracker:
>
> https://savannah.gnu.org/patch/?func=additem&group=octave
>
> Take a look at the contribution guidelines and the missing function list
> for the communications package, and feel free to email me or the mailing
> list if you have any questions about contributing:
>
>
> https://www.gnu.org/software/octave/doc/interpreter/Contributing-Guidelines.html#Contributing-Guidelines
> http://wiki.octave.org/Mercurial
> http://wiki.octave.org/Commit_message_guidelines
> http://wiki.octave.org/Communications_package
>
> --
> mike
[Prev in Thread] | Current Thread | [Next in Thread] |