We don't use github pull requests. You'll need to wait for a trac account, upload your SSH keys and then use the git trac extension ( https://github.com/sagemath/git-trac-command). See the developer manual for more details. David
On Thu, Jan 7, 2016 at 1:19 PM, Karan Desai <karandesai281...@gmail.com> wrote: > Hi David, > > I forked the repository and converted the README.txt to README.md in a > separate branch created from master. > > I haven't altered any content for now and the README has been changed from > this : > https://www.github.com/sagemath/sage > > ... to this: > https://github.com/karandesai-96/sage/tree/karandesai-96-readme-beautify > > While editing, I read the whole README, which gave me some good points to > know about sage, useful for me as a newbie ! > What should I do further ? It would be helpful if you mention the > hyperlink :) > I requested a trac account but haven't yet received any confirmation > e-mail. Should I fire up a pull request ? > If yes, to which branch - master or develop? > If no, I'll open a ticket as you instruct and wait for your as well as > fellow developers' suggestions. > > Thank You. > Karan > > On Thursday, January 7, 2016 at 6:04:33 PM UTC+5:30, David Roe wrote: >> >> >> >> On Wed, Jan 6, 2016 at 12:59 PM, Karan Desai <karandes...@gmail.com> >> wrote: >> >>> Hello developers, >>> >>> I recently put up a thread regarding contribution to sagemath. It has >>> been helpful to me, I want to be helpful to community in any possible way. >>> I was setting up the development environment, prefer Pycharm IDE for the >>> same. >>> I just forked the sage repository and built it from source, it took a >>> lot of time but it was built properly, with many warnings but no errors. >>> On https://www.github.com/sagemath/sage , the first and foremost thing >>> seen by someone visiting the repo is the README. >>> I can see it looks very flat and unmaintained, and as a .txt >>> I would like to convert it into a neat markdown file, and even improve >>> its content aligning to latest releases and fire up a pull request. >>> It isn't an enhancement to the product, but such chores should be done >>> to such a huge project. >>> This would potentially be my first contribution, and I'll get the push >>> to contribute more towards the product after I get the amazing feeling of >>> my contribution to be included within ! >>> So do I make a ticket for this README too ? I am asking it as it doesn't >>> directly enhance any part of the product. Please add in your views. >>> >> >> That sounds like a great way to get started. Glancing through >> README.txt, I would check to see if the comments about relocation are still >> accurate with the changes to binary builds on OS X 10.11. Are >> builds-from-source still relocatable? >> >> Opening a ticket and then working on converting it to Markdown sounds >> like a good way to proceed. >> David >> >>> >>> Thank You. >>> Karan. >>> >>> -- >>> 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+...@googlegroups.com. >>> To post to this group, send email to sage-...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/sage-devel. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- 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.
