added first time

CVS version numbers

indonesian/News/press/1997.wml: INITIAL -> 1.1 
indonesian/News/press/1998.wml: INITIAL -> 1.1 
indonesian/News/press/1999.wml: INITIAL -> 1.1 
indonesian/News/press/2000.wml: INITIAL -> 1.1 
indonesian/News/press/index.wml: INITIAL -> 1.1 
indonesian/News/weekly/contributing.wml: INITIAL -> 1.1 
indonesian/News/weekly/index.wml: INITIAL -> 1.1 
indonesian/News/weekly/oldurl.wml: INITIAL -> 1.1 
indonesian/intro/index.wml: INITIAL -> 1.1 
indonesian/intro/license_disc.wml: INITIAL -> 1.1 
indonesian/intro/search.wml: INITIAL -> 1.1

3 files changed, 206 insertions, 0 deletions

diff --git a/indonesian/intro/index.wml b/indonesian/intro/index.wml
new file mode 100644
index 00000000000..2c2913c05b4
--- /dev/null
+++ b/indonesian/intro/index.wml
@@ -0,0 +1,18 @@
+#use wml::debian::template title="Introduction to Debian"
+#use wml::debian::translation-check translation="1.3"
+
+<p><a href="about">Tentang Debian</a>.
+
+<p><a href="free">Apa artinya <em>Free</em>?</a>.
+
+# <p><a href="license_disc">Perbandingan Antar Lisensi Perangkat Lunak</a>.
+
+<p><a href="why_debian">Alasan Memilih Debian</a>.
+
+# <p><a href="cooperation">Cooperation with the FSF</a>.
+
+<p><a href="organization">Struktur Organisasi Debian</a>.
+
+<p><a href="search">Informasi Untuk Menggunakan Mesin Pencari</a>.
+
+<p><a href="cn">Halaman-halaman Situs Web Tersedia Dalam Berbagai Bahasa</a>.
diff --git a/indonesian/intro/license_disc.wml b/indonesian/intro/license_disc.wml
new file mode 100644
index 00000000000..76b0bf9e052
--- /dev/null
+++ b/indonesian/intro/license_disc.wml
@@ -0,0 +1,135 @@
+#use wml::debian::template title="Comparison of Software Licenses"
+#use wml::debian::translation-check translation="1.10"
+
+<p><strong>******Dokumen ini sedang dalam pengembangan*******</strong>
+
+<p>People who have been around Open Software tend to develop very strong
+opinions about licenses. Beginners don't worry about them as much
+since they are more concerned with finishing the task at hand and
+don't understand the long term implications of choosing software with
+one license over another (it is doubtful that there
+many people who understand the nuances of licensing that don't have
+strong opinions on the matter).
+
+<p>Over the years a number of licenses have gained prominence as they
+give software authors the type of control over their creations that
+most developers desire. It is still common to find software that has
+no copyright visible or contains a unique license developer by the
+author. The last can be quite annoying to distributors of software
+(both on-line and people who create CDs) as many of these licenses
+contain <a href="#mistakes">common mistakes</a> which make the software
+difficult to distribute.
+
+<p>What follows is a list of common Free (Open) software licenses and
+some good and bad points of each.
+Only the points in the license relevant to the discussion are shown.
+Also, many points are listed under the heading "GOOD/BAD".
+These are points that can be either good or bad, depending on your point of 
+view.
+
+<ul>
+<li>The <a href="http://www.gnu.org/">GNU General Public License (GPL)</a>.
+	
+   <br>
+   <b>Sekilas:</b> source code must be made available; software may be 
+   sold; derived works must use the same license
+	
+   <br>
+   <b>Kebaikan:</b> There is good reason this is the most used license for
+   Free (Open) software. It does a good job of protecting the rights of 
+   software developers and the availability of source code guarantees that
+   users won't have to worry about losing support in the future.
+
+   <br>
+   <b>Kebaikan/Keburukan:</b> Software released using the GPL can not be 
+   incorporated into commercial software. Whether this is actually a bad thing 
+   depends on your point of view. People developing commercial software often 
+   feel frustrated when there is a solution available that can't be used because
+   of conflicts in licensing. Of course, there is nothing stopping them from
+   contacting the author and seeing if they can buy a version using a different
+   license. Most people who release software using the GPL do not consider these
+   restrictions bad, because it allows others to use and improve the software 
+   while it prevents (for all practical purposes) others from making money off 
+   of their hard work without his permission. 
+
+<li>Lisensi Artistik
+   <a href="http://language.perl.com/misc/Artistic.html">http://language.perl.com/misc/Artistic.html</a>.
+
+   <br>
+   <b>Sekilas:</b> 
+   
+   <br>
+   <b>Kebaikan:</b> 
+
+   <br>
+   <b>Keburukan:</b> 
+
+<li><a href="../misc/bsd.license">Lisensi gaya BSD</a>.
+	
+   <br>
+   <b>Sekilas:</b> Binaries and source code must contain the license; 
+   advertising must acknowledge the developers listed in the license
+
+   <br>
+   <b>Kebaikan/Keburukan:</b> Companies that want an executable to be generally
+   available (possibly for free) without releasing the source code often like
+   this license. A good example is a company that wants to release a driver
+   for a graphics card. Open Source advocates would prefer that the company
+   release hardware specifications anyway. If the development of drivers for 
+   XFree86 is indicative, the best drivers are those written with source 
+   available. Companies are only making their products look bad by releasing 
+   proprietary drivers that are slow and buggy. They can also save development 
+   costs by letting others develop the driver for them.
+
+   <br>
+   <b>Kebaikan/Keburukan:</b> Anyone may take the source, modify it, and release
+   the result without releasing the changes. Whether you think this is good or
+   bad is a personal preference.
+
+</ul>
+
+<hr>
+
+<p><a name="mistakes">Some common mistakes in self-written licenses</a>:
+
+<ul>
+
+   <li>Either not allowing, or restricting for-profit sale of the software. 
+   This makes it difficult to distribute the software on CD. People often make 
+   the mistake of using terms that are not well defined, such as 'reasonable 
+   cost'. It is better to simply use one of the licenses mentioned above as 
+   they accomplish the same thing without resorting to such phrases. For 
+   example, by allowing anyone to distribute the software, the GPL keeps the 
+   costs down by the usual market forces. If someone is selling a CD with a 
+   high profit margin it won't be long before competitors enter the market and 
+   sell for a lower price.
+	
+   <br>Note: the Artistic License does use the term `Reasonable copying fee', 
+   but qualifies the term in an attempt to make it less vague.
+
+   <li>Not allowing distribution of modified versions of the software. This 
+   hinders distribution of the software by certain groups. For example, since
+   Debian distributes compiled software, it is often necessary to modify the 
+   source to get it to compile or to make it comply with the
+   <a href="ftp://tsx-11.mit.edu/pub/linux/docs/linux-standards/fsstnd/">FSSTND</a>. 
+   But by doing this, we are then not allowed to distribute it.
+
+   <li>Requiring that all changes to the software be reported to the author. 
+   While it is a good idea to report changes/improvements to the author so they
+   can be more widely distributed, making it a requirement can cause problems. 
+   How many people know where they will be in 5 years? Simply change it to 
+   'Any changes to the software should be reported to the author'. Most people 
+   will.
+	
+   <br>This clause is usually included to prevent branch projects from 
+   developing. History has shown that, as long as development on the original 
+   code doesn't stall, branches will only succeed if some other force drives 
+   the split.
+
+   <li>Stating that the software is public domain, but then adding constraints 
+   (such as not allowing sale for profit). Either something is public domain or
+   it isn't - there is no middle ground. Such licenses are meaningless and it is
+   likely that the extra conditions would not be upheld in court.
+
+</ul>
+
diff --git a/indonesian/intro/search.wml b/indonesian/intro/search.wml
new file mode 100644
index 00000000000..de10d20a30b
--- /dev/null
+++ b/indonesian/intro/search.wml
@@ -0,0 +1,53 @@
+#use wml::debian::template title="Information on how to use the Debian search engine"
+#use wml::debian::translation-check translation="1.6"
+
+<p>Mesin pencarian Debian yang ada di
+<a href="http://search.debian.org/">http://search.debian.org/</a> dapat 
+digunakan untuk beberapa tipe pencarian yang berbeda, tergantung kebutuhan 
+anda.
+
+<h3>Pencarian Sederhana</h3>
+
+<p>Cara termudah adalah dengan mengisikan sebuah kata pada kotak pencarian,
+lalu menekan enter (atau klik pada tombol <em>Cari</em>). Mesin pencarian akan
+memberikan semua halaman web pada situs yang mengandung kata tersebut.
+
+<p>Satu tingkat di atasnya adalah pencarian dengan menggunakan lebih dari
+satu kata. Pilihan anda adalah:
+<dl compact>
+<dt><em>pencarian halaman mengandung semua kata</em>
+  <dd>menghasilkan halaman-halaman yang mengandung semua kata yang anda ketik.
+<dt><em>pencarian halaman yang mengandung apa pun kata yang diketik</em>
+  <dd>menghasilkan halaman-halaman yang mengandung apa pun kata yang anda
+  ketik.
+</dl>
+
+<h3>Pencarian Menggunakan Boolean</h3>
+
+<p>Jika pencarian sederhana tidak mencukupi, mungkin
+<a href="http://www.foldoc.org/foldoc/foldoc.cgi?query=boolean">boolean</a>
+dapat memenuhi kebutuhan anda. Anda dapat menggunakan <em>and</em> (= dan),
+<em>or</em> (= atau), <em>not</em> (= bukan) dan kombinasi dari ketiganya.
+
+<p><b>&amp; - logika DAN </b> akan memberikan hasil yang mengandung
+kedua kata yang disediakan. Contoh "gcc &amp; patch" akan mencari URL-URL yang
+mengandung kata "gcc" dan "patch".
+
+<p><b>| - logika ATAU</b> akan memberikan hasil yang mengandung salah satu
+maupun kedua kata yang disediakan. Contoh "gcc | patch" akan mencari URL-URL
+yang mengandung kata "gcc" ataupun "patch".
+
+<p><b>~ - logika BUKAN</b> menyaring sebuah kata dari hasil pencarian. Biasanya
+digunakan bersamaan dengan logika DAN ( &amp; ) untuk membuang sebagian
+hasil pencarian. Contoh, "gcc & ~patch" akan mencari URL-URL yang mengandung
+kata "gcc" dan tidak mengandung kata "patch". Hanya dengan menuliskan "~patch"
+tidak akan memberikan hasil apa-apa. Karena, pertama, anda tidak mencari 
+sesuatu apapun, sehingga tidak memberikan hasil apa-apa. Lalu, pada daftar
+kosong tersebut anda mencoba membuang halaman yang mengandung kata "patch",
+yang tentu saja tidak menghasilkan apa-apa.
+
+
+<p><b>() - pengelompokan</b> menambah kompleksitas di mana anda dapat
+mengelompokan kumpulan logika-logika secara bersamaan. Contoh "(gcc | make)
+&amp; ~patch" akan mencari semua URL yang mengandung salah satu dari kata "gcc"
+dan "make" atau keduanya tetapi tidak mengandung kata "patch".