Difference between revisions of "Coders"

From FreekiWiki
Jump to navigation Jump to search
(mention rails, not just ruby. FGdiag isn't python anymore.)
 
(78 intermediate revisions by 14 users not shown)
Line 1: Line 1:
Coding at Free Geek
+
[[Category:Structure]]
 +
[[Category:Programs]]
  
Coders Workshops meet weekly on Tuesdays at 7:15. Coders Workshops are open to all, experienced and new coders alike. The only requirement is that you want to help and learn or teach in the process. We try to team up experienced folks with newbies. We only work on stuff we actually use, so your work is always needed.
+
==Intro==
 +
The coders group at Free Geek is the place you can learn or teach about software programming and development. This is informally organized around various projects, with some guidance from the [[Technocrats]] and some spillover with the [[ASS]]es. This is not very educationally focused, lacking any structure for shepherding people through the trying work of figuring out how to get stuff done.  If you want to contribute to a free software project and you can work fairly independently (or in small, self-forming groups of interested volunteers), go through the rest of this page and find something that piques your interest.
  
 +
==Coding Projects==
 
Here are some projects we are working on at Free Geek:
 
Here are some projects we are working on at Free Geek:
  
[[FGdb]] -- PHP code that talks to a PostgreSQL database.
+
[[FGdb]] -- This is Ruby ( http://www.ruby-lang.org/ ) on rails ( http://rubyonrails.org ) code that talks to a PostgreSQL database ( http://www.postgresql.org/ ).
  
[[FGDiag]] -- Python code used for testing gizmos.
+
[[FGdiag]] -- Miscellaneous code for testing gizmos. (mostly ruby)
  
 
[[Distro Implementation]] -- Figure out how to get the software onto the boxes we build, and how to make it work like we want it to.
 
[[Distro Implementation]] -- Figure out how to get the software onto the boxes we build, and how to make it work like we want it to.
Line 13: Line 16:
 
[[Other Coding Projects]] -- There are usually a variety of smaller tasks that need doing, often using shell scripting.
 
[[Other Coding Projects]] -- There are usually a variety of smaller tasks that need doing, often using shell scripting.
  
If any of the above projects interests you, you may want to join the coders. To do so:
+
==Getting Started==
 +
If any of the above projects interest you, you may want to join the coders. we're open to anyone so long as the work you do is done cooperatvely with other Free Geek volunteers and you're willing to let it be licensed under an open source license, preferably the GPL.
  
  - sign up for the coders mailing list http://lists.freegeek.org/listinfo/coders [[email lists for coders]]
+
To get started:
  - get an account on our development box. [[SSH for coders]]  
+
* Read Martin's stock [[New Coder Introduction]].
  - get a CVS account. [[CVS for coders]]  
+
 
  - get an RT account http://todo.freegeek.org/rt/ [[RT for coders]]  
+
===In the Portland, Oregon, USA area?===
  - Free Geek coders hang out on IRC at freenode.net on the #freegeek channel. [[IRC for coders]]
+
* Sign up for the coders mailing list http://lists.freegeek.org/listinfo/coders ([[email lists for coders]])
 +
** Post a message and introduce yourself
 +
** If you're in the Portland, Oregon area, you'll want to come down to Free Geek to meet the other local coders and get started.  Ask the front desk to meet a [[ASS | sysadmin]] or [[Technocrats | technocrat]].
 +
 
 +
===Somewhere else?===
 +
* Sign up for the coders mailing list http://lists.freegeek.org/listinfo/coders ([[email lists for coders]])
 +
** Post a message and introduce yourself
 +
** Say you're from out of town and we'll contact you about getting set up.
 +
* Coding is one of the few ways you can volunteer at Free Geek from a distance.
 +
 
 +
===Wherever you are:===
 +
* Coding is done by editing text files, see [[Text Editing for Coders]] for more info.
 +
* Get an account on the appropriate [[Free Geek Computers for Coders]].
 +
* Get an SVN account. ([[Subversion for Coders]])
 +
* Get an RT account http://todo.freegeek.org/ ([[RT for coders]])
 +
* Free Geek coders hang out on IRC at freenode.net ( http://freenode.net/ ) on the #freegeek channel. ([[IRC for coders]])
 +
 
 +
==Big Picture Stuff==
 +
* [[Rethinking Coders]] -- thoughts on how the coders program can be improved and where it's going.
 +
 
 +
[[Category: Coders]]

Latest revision as of 18:46, 17 September 2008


Intro

The coders group at Free Geek is the place you can learn or teach about software programming and development. This is informally organized around various projects, with some guidance from the Technocrats and some spillover with the ASSes. This is not very educationally focused, lacking any structure for shepherding people through the trying work of figuring out how to get stuff done. If you want to contribute to a free software project and you can work fairly independently (or in small, self-forming groups of interested volunteers), go through the rest of this page and find something that piques your interest.

Coding Projects

Here are some projects we are working on at Free Geek:

FGdb -- This is Ruby ( http://www.ruby-lang.org/ ) on rails ( http://rubyonrails.org ) code that talks to a PostgreSQL database ( http://www.postgresql.org/ ).

FGdiag -- Miscellaneous code for testing gizmos. (mostly ruby)

Distro Implementation -- Figure out how to get the software onto the boxes we build, and how to make it work like we want it to.

Other Coding Projects -- There are usually a variety of smaller tasks that need doing, often using shell scripting.

Getting Started

If any of the above projects interest you, you may want to join the coders. we're open to anyone so long as the work you do is done cooperatvely with other Free Geek volunteers and you're willing to let it be licensed under an open source license, preferably the GPL.

To get started:

In the Portland, Oregon, USA area?

Somewhere else?

Wherever you are:

Big Picture Stuff

  • Rethinking Coders -- thoughts on how the coders program can be improved and where it's going.