Well, that was quite motivating !
I agree with you, to be a developer, you need to be a user. 
While Sagemath has served me very well at times, I feel it is time for me 
to reciprocate, and help it become slightly better than before, as a result 
of my contribution ! 
I will take a few days, probably a week to try to understand the framework 
as a whole, and pick up a small part of it and go deep within to see how 
things work specifically for that ! :-)

Thank You, and Happy 2k16 !
Karan.

On Saturday, January 2, 2016 at 10:52:28 PM UTC+5:30, Nathann Cohen wrote:
>
> Hellloooooooo Karan, 
>
> Welcome here. Sage-devel is where we have all general discussions 
> related to Sage's development (the other occur on each Trac ticket). 
> You can ask anything here and we'll try to help as efficiently as we 
> can, though sometimes the answers will already be available in the 
> Developer's Manual. 
>
> This developer's manual is probably the starting point you are looking 
> for: 
>
>     http://doc.sagemath.org/html/en/developer/index.html 
>
> It will tell you many things about our procedures, though you need not 
> read all of it before starting, of course ! Browse it, know that it 
> exists, so that you will know in the future which of your questions 
> may find their answer there. 
>
> In Sage we write Python code mainly, with some weird mix of Python and 
> C/C++ called Cython. You will see it used whenever we want more speed 
> than Python provide, and you can open any of our .pyx files if you are 
> curious about it. 
>
> Mathematically speaking, I do not find Sage as complicated as I would 
> have first expected.... though I admittedly work in an area which is 
> not very very deep/complicated. None of us understands everything that 
> Sage contains: we do not know all the maths at once, but for each 
> file/folder you will find somebody here who knows and understands its 
> content. Some of us also have a wider view of things, like Volker 
> Braun who is our release manager: all our code, despite being 
> mathematically specific, has to be well-organised and interoperate 
> well. Plus it all has to compile/run on a wealth of different 
> platforms, and that is a distinct kind of knowledge that not everybody 
> has. 
>
> I have not contributed to many open-source softwares, but I believe in 
> one thing: to be a developer, you must first be a user. Use Sage for 
> whatever you like/need, and if you ever find something 
> [missing/wrong/dangerous/undocumented/badly documented] .... do 
> something about it. Which can start by sending a message to 
> sage-devel, to make sure that we all agree that it has to change. 
>
> A developer is merely a user who is unhappy about the software and 
> intends to set things right. 
>
> Good luck, 
>
> Nathann 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to