Giter Site home page Giter Site logo

natestemen / rudin Goto Github PK

View Code? Open in Web Editor NEW
22.0 22.0 4.0 966 KB

A version of "Principles of Mathematical Analysis" by Walter Rudin :book: (IN NEED OF NEW CONTRIBUTORS)

Home Page: https://natestemen.github.io/rudin

License: GNU General Public License v3.0

TeX 91.88% Python 8.12%
analysis math mathematical-analysis textbook walter-rudin

rudin's Introduction

it's nate

I like to:

  • ๐Ÿงฎ do mathy things
  • ๐Ÿ‘ฉ๐Ÿผโ€๐Ÿ’ป get computers to do things for me
  • ๐ŸŽต listen to music
  • ๐Ÿ›€๐Ÿป this is supposed to be relaxing, I don't just like bathing
  • ๐Ÿšต๐Ÿปโ€โ™€๏ธ ride my bike

I like thinking about making quantum computing a reality for everyone, education/pedagogy, and privacy.

For work, you'll find me as a "member of technical staff" at Unitary Fund.

my pronouns are he/they

rudin's People

Contributors

epsilon-less-than-0 avatar natestemen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

rudin's Issues

make compilation of sections and chapters work

I set up the basics with the subfiles package, but there are quite a few things that are not working at the moment. Would be good to get this working, especially as the project grows.

What should our review process look like?

As of now, it is @epsilon-less-than-0 and I working on this we haven't been using anything of a review process besides kind of just looking over things (if that). This isn't how it really should be done, and is especially not good if anyone else wants to contribute because they won't have committing access to the master branch.

I propose that we have a branch for each section of the book. Once we have finished a section, we put together a pull request and assign it to the either myself or @epsilon-less-than-0. The reviewer will be responsible for reading over the content and making sure it is clear and pedagogical, among other things (like being error free, but the PR author should have already done this). This may not be the most ideal solution, but it is better than both of us committing to master and not having a good review process.

We could also have branches for each chapter, then have larger pull requests, but I kind of like the idea of having smaller pull requests. Easier to review and takes much less time.

@epsilon-less-than-0 what are you're thoughts?

Lots of latexmk generated files

Once the project has been fully set up with the subfiles package, we will be able to use latexmk to compile chapters and sections independently. This will generate lots of files that we don't care about (at least not for github). They will be ignored by the gitignore file, but it would just be nice to have a script to clean up all these files at once. I think this could be done relatively easily with a makefile, but I'm not all that familiar with make.

lots of biblatex errors

am really stuck with the biblatex errors. cant seem to get rid of them and im not into the whole "oh well the document looks good so dont worry about it attitude". would be good to quiet biblatex down properly.

Change license to GPL

I'd suggest we should change the current license of the project to GPL. WTFPL (the one we currently have) is great, but it does kind of mean that someone could take the project, and go to some publishing company, get them to publish it without our consent and make a bunch of money off of it.

GPL would require any derivative work to also have a GPL license which is cool.

Do you have any thoughts on this @epsilon-less-than-0?

PDF

Hi there!

First off, thanks so much for taking the time and effort in making this.

I don't have all the LaTex dependencies installed on my laptop. I tried compiling this on overleaf and ran into a couple of errors. I would really appreciate if you could maintain an updated pdf of the notes along with the LaTex source code. It would really helpful. Thanks!

Compiling with latexmk gives "biber" error

sh: 1: biber: not found
Latexmk: Errors, so I did not complete making targets
Latexmk: Failure to make the files correctly
    ==> You will need to change a source file before I do another run <==
Collected error summary (may duplicate other messages):
  biber 00-finite-countable-and-uncountable-sets: Could not open biber log file for '00-finite-countable-and-uncountable-sets'

=== Watching for updated files. Use ctrl/C to stop ...
^CLatexmk: User typed ctrl/C or ctrl/break.  I'll finish.
Collected error summary (may duplicate other messages):
  biber 00-finite-countable-and-uncountable-sets: Could not open biber log file for '00-finite-countable-and-uncountable-sets'
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs of latex/pdflatex.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.