Hi, Jonno. A great starting point is to act as a thorough tester. If you find things in Spyder that just seem to be broken, open up an issue here and describe what you're seeing:
http://code.google.com/p/spyderlib/issues/list If you're feeling more adventurous, get setup to run Spyder directly from that latest development source as described here: http://code.google.com/p/spyderlib/wiki/NoteForBetaTesters#Running_directly_from_source That will require some familiarity with Mercurial, and if that's new territory a small investment in understanding distributed version control is worth your time regardless of which project you're working on. Running from source will expose you to potentially more bugs, and that helps the project. Running from the source tree also gives you the flexibility to move around to different source revisions very easily. After reporting a few bugs you just might find yourself feeling the itch to try your hand at fixing one! Hope this helps, Jed On Thu, Apr 19, 2012 at 10:01 AM, Jonno <[email protected]> wrote: > All, > > I've been using Spyder for over a year now and love the project. I'd > like to help in some capacity although I'm a very part-time Pythonista > and not an experienced programmer. > Please let me know how I can contribute. > > Jonno. > > -- > You received this message because you are subscribed to the Google Groups > "spyder" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/spyderlib?hl=en. > > -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
