Schematics: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by the same user not shown)
Line 12: Line 12:


== Other Resources ==
== Other Resources ==
* [http://wiki.call-cc.org/ Chicken Scheme] - the implementation we use.
* [http://call-cc.org/ Chicken Scheme] - the implementation we use.
* [https://www.noisebridge.net/mailman/listinfo/schemers Mailing List]
* [http://projecteuler.net Project Euler]
* [http://projecteuler.net Project Euler]
* [http://www.ic.unicamp.br/~meidanis/courses/mc336/2006s2/funcional/L-99_Ninety-Nine_Lisp_Problems.html 99 Lisp Problems]
* [http://www.ic.unicamp.br/~meidanis/courses/mc336/2006s2/funcional/L-99_Ninety-Nine_Lisp_Problems.html 99 Lisp Problems]

Latest revision as of 18:28, 15 April 2011

Schematics is a companion meetup for the sunday Schemers meet. As the sunday meet is currently more of a high-level casual discussion-group, what we're aiming for is more of a structured class, where the content each week is a custom presentation based upon who's showing that week and what problems they ran into during that week while working on a designated collaborative project for the group. Another main foci would be documenting all our findings which would result in a scheme book of sorts, where instead of having future schemers having to traverse the web and get their (often confusing) information from a variety of sources, everything would be compiled neatly and cleanly into one source where everything is easy to understand. This would serve as a handy reference for our existing members, and, if done properly, would immensely help any future schemers who catch wind of it.

Projects[edit]

Please take a look at the following page, add any of your own ideas if you have 'em, and speak up on the mailing list or at the meet. Basic workflow is this: find the project you want to contribute to in the organization, and fork it. After you've made some changes you want to commit, send us a pull request. We'll go over the changes as a group, and possibly commit them into the main repo.

Active[edit]

Code Management[edit]

is done via github. After you sign up, send off an email to Chris and you'll be added to the schematics organization. Basic workflow goes like this: find the project you want to contribute to on the organization's page and fork it; after you've finalized the commit(s) you want to add, send us a pull request. We'll look over the changes as a group, and possibly commit them into the main repo.

Other Resources[edit]