Editing Help:Contents

== In the Beginning ==

<b>What the heck is this place?</b><br>
So Cina, Nate, and a guy named Aubry were all working on similar cellular projects using the [[GM862 Cellular Module]] but each project was different enough that we could not collaborate directly. However, we noticed that there was enough overlap between projects that certain things should be shared. Things like the audio biasing circuit, the power supply, and the footprint for various exotic parts. We wanted an easy way to share this information with others as well, and the concept of Open Circuits was born.<br><br>

We got the framework up (Cina is a pimp) in about 24hours. Even if you are completely new to Wikis, we're sure you'll find things fairly straight forward. Please use the following template (edit this change and copy/paste) into your posting as a starting point.<br>

Note: As you can see from the history of this site at Help:Contents, the User:Chazegh originally set up this site.

== Tips on Reading Open Circuits ==

See:  [[Tips on Using Open Circuits]]

== The Engine ==

The Wiki Engine is: [http://www.mediawiki.org/wiki/MediaWiki Welcome to MediaWiki.org]  There is a lot of info on working with the Wiki there.  

----

== Want to know [[How to delete spam]]? ==

----

== FAQ ==

=== Cam Files ===

Why can't I upload a *.cam file. It is used by Eagle for cam processors. There should be a better why to get help than posting to this page. --[[User:Linuxvolts|Linuxvolts]] 19:58, 23 May 2007 (PDT)

Would also be useful to upload zip files, these could contain any file type or archives of several file types.  Probably should be a file size limit. [[russ_hensel]] feb '08.

Answer?
I would sugjest something like sourceforge, bounty forge and others look around a CMS with drupal or joomla support can make your page building more automated and less fine grain work.

=== C Code and Files ===
How would I add my c code for my processor?
Answer:
C or other code that is just text can be put on any page, formatting may be a bit funny but anyone can cut and paste the code into their editor. I have found that you can get nice formatting if tabs are expanded to spaces ( many text editors will do this, Crimson Editor for example )  Make sure each line begins with at least one space.  For more complicated projects with multiple files a zip file capibility ( not available now ) would be nice [[russ_hensel]]  For low volume I, ( [[russ_hensel]] ), will ftp files to my space on comcast's ftp site, contact me.

I would sugest something like sourceforge, bounty forge and others look around a CMS with drupal or joomla support can make your page building more automated and less fine grain work.  They have CVS & Subversion.

=== Upload Graphic Files ===

Answer<br>
Upload with "upload file" link on left margin on most pages.

=== Messages to Users ===

Try to keep public discussions, go to the user's talk page and put a message there. ( how do you get there: go to the user's page, press discussion at the top of page. )  If a discussion is more general go to the topic and then press discussion.  See: [http://www.usemod.com/cgi-bin/mb.pl?BackRoomDecision BackRoomDecision]

=== unlinking section titles ===

Currently at Open Circuits, many section titles are active links.
However, someone at Wikipedia once wrote:
: ''"Section headings should not themselves contain links" -- [http://en.wikipedia.org/wiki/Wikipedia:Linking Wikipedia: Wikipedia: Linking]''

Do their reasons for avoiding such links apply to Open Circuits?
--[[User:DavidCary|DavidCary]] 00:35, 26 January 2010 (UTC)

=== How Can I Help ===


See [[we_love_volunteers]]
@@ Line 62: / Line 62: @@
 See [[we_love_volunteers]]
-I want to share my knowledge regarding HOBBY Level
-Electronics
-Robotics
-Aeronautics( Basic Concept to Make Electric RC airplane )
-Computer Hardware
-Email : kumarcomputricks@gmail.com
-[[Category:Community]]