<?xml version="1.0" encoding="utf-8"?>
<!-- generator="" -->
<?xml-stylesheet href="/components/com_jcomments/tpl/default/style.css?v=10" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom"  xml:lang="en-gb">
	<title type="text">For Developers</title>
	<subtitle type="text">OpenFoundry provides essential tools and services through its service platform for users to develop Open Source Software Projects, the operating funds comes from the National Science Council and the Research Center for Information Technology Innovation of Academia Sinica Taiwan.</subtitle>
	<link rel="alternate" type="text/html" href="https://www.openfoundry.org"/>
	<id>https://www.openfoundry.org/for-developers</id>
	<updated>2025-09-23T14:01:56Z</updated>
	<generator uri="http://joomla.org" version="1.5"></generator>
<link rel="self" type="application/atom+xml" href="https://www.openfoundry.org/en/for-developers?format=feed&amp;type=atom" />
	<entry>
		<title>Upstreaming your code - a primer</title>
		<link rel="alternate" type="text/html" href="https://www.openfoundry.org/en/for-developers/8239--linux-"/>
		<published>2011-01-10T11:59:33Z</published>
		<updated>2011-01-10T11:59:33Z</updated>
		<id>https://www.openfoundry.org/en/for-developers/8239--linux-</id>
		<author>
			<name>Armijn Hemel &amp; Ralf Baechle 林誠夏/翻譯</name>
		<email>lucien@citi.sinica.edu.tw</email>
		</author>
		<summary type="html">Copyright © 2011 Armijn Hemel &amp; Ralf Baechle .&lt;br /&gt;This work is available under the &lt;a href=&quot;https://creativecommons.org/licenses/by/3.0/&quot; target=&quot;_blank&quot;&gt;Creative Commons Attribution 3.0 Unported license&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;This document describes what steps chip vendors need to take to successfully upstream their code into the mainline Linux kernel.  
</summary>
		<content type="html">Copyright © 2011 Armijn Hemel &amp; Ralf Baechle .&lt;br /&gt;This work is available under the &lt;a href=&quot;https://creativecommons.org/licenses/by/3.0/&quot; target=&quot;_blank&quot;&gt;Creative Commons Attribution 3.0 Unported license&lt;/a&gt;.&lt;br /&gt; &lt;br /&gt;This document describes what steps chip vendors need to take to successfully upstream their code into the mainline Linux kernel.  
</content>
	</entry>
	<entry>
		<title>Working with the community</title>
		<link rel="alternate" type="text/html" href="https://www.openfoundry.org/en/for-developers/8128-2010-08-30-15-26-59"/>
		<published>2010-08-30T15:22:32Z</published>
		<updated>2010-08-30T15:22:32Z</updated>
		<id>https://www.openfoundry.org/en/for-developers/8128-2010-08-30-15-26-59</id>
		<author>
			<name>Armijn Hemel 葛冬梅/翻譯</name>
		<email>tmk2005@citi.sinica.edu.tw</email>
		</author>
		<summary type="html">1. What is &quot;the community&quot;? &lt;br /&gt;&lt;br /&gt;In open source software the concept of 'the community' is important, because it is the core unit to run the open source software development. Often a community consists of developers of the software, users of the software and other interested people. 
</summary>
		<content type="html">1. What is &quot;the community&quot;? &lt;br /&gt;&lt;br /&gt;In open source software the concept of 'the community' is important, because it is the core unit to run the open source software development. Often a community consists of developers of the software, users of the software and other interested people. 
</content>
	</entry>
	<entry>
		<title>Useful tips for releasing Open Source code with commercial products</title>
		<link rel="alternate" type="text/html" href="https://www.openfoundry.org/en/for-developers/8127-2010-08-30-15-14-41"/>
		<published>2010-08-30T14:48:52Z</published>
		<updated>2010-08-30T14:48:52Z</updated>
		<id>https://www.openfoundry.org/en/for-developers/8127-2010-08-30-15-14-41</id>
		<author>
			<name>Armijn Hemel 葛冬梅/翻譯</name>
		<email>tmk2005@citi.sinica.edu.tw</email>
		</author>
		<summary type="html">1. BusyBox configuration &lt;br /&gt;&lt;br /&gt;You need to provide the configuration that was used to build BusyBox as part of the source code. Depending on the version of BusyBox this is a file called Config.h (BusyBox 0.60.5 and earlier) or .config (1.00-pre1 and later). 
</summary>
		<content type="html">1. BusyBox configuration &lt;br /&gt;&lt;br /&gt;You need to provide the configuration that was used to build BusyBox as part of the source code. Depending on the version of BusyBox this is a file called Config.h (BusyBox 0.60.5 and earlier) or .config (1.00-pre1 and later). 
</content>
	</entry>
	<entry>
		<title>宣告授權條款的方式</title>
		<link rel="alternate" type="text/html" href="https://www.openfoundry.org/en/for-developers/1884-2010-07-13-09-48-09"/>
		<published>2008-12-22T16:08:18Z</published>
		<updated>2008-12-22T16:08:18Z</updated>
		<id>https://www.openfoundry.org/en/for-developers/1884-2010-07-13-09-48-09</id>
		<author>
			<name>webmaster</name>
		<email>contact@openfoundry.org</email>
		</author>
		<summary type="html">&lt;p&gt;選定授權條款之後，接下來就是要讓他人知道您程式的授權內容，也就是要宣告程式的授權條款。就目前大部分的自由軟體授權條款規定來看，並沒有一定必須遵守的宣告方式，所以重點在於：要讓他人可以清楚明確地知道您程式是採用自由軟體的方式來授權。&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
</summary>
		<content type="html">&lt;p&gt;選定授權條款之後，接下來就是要讓他人知道您程式的授權內容，也就是要宣告程式的授權條款。就目前大部分的自由軟體授權條款規定來看，並沒有一定必須遵守的宣告方式，所以重點在於：要讓他人可以清楚明確地知道您程式是採用自由軟體的方式來授權。&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
</content>
	</entry>
	<entry>
		<title>為自己的程式選擇授權條款</title>
		<link rel="alternate" type="text/html" href="https://www.openfoundry.org/en/for-developers/1883-2010-07-13-09-51-31"/>
		<published>2008-12-22T15:55:51Z</published>
		<updated>2008-12-22T15:55:51Z</updated>
		<id>https://www.openfoundry.org/en/for-developers/1883-2010-07-13-09-51-31</id>
		<author>
			<name>webmaster</name>
		<email>contact@openfoundry.org</email>
		</author>
		<summary type="html">&lt;p&gt;您自己寫了一個程式，想要用自由軟體的方式來授權，這時候應該如何做？當然就是要選擇一份授權條款。鑄造場在這邊擇要地提供一些選擇授權條款的考量因素，供您參考。&lt;/p&gt;
</summary>
		<content type="html">&lt;p&gt;您自己寫了一個程式，想要用自由軟體的方式來授權，這時候應該如何做？當然就是要選擇一份授權條款。鑄造場在這邊擇要地提供一些選擇授權條款的考量因素，供您參考。&lt;/p&gt;
</content>
	</entry>
	<entry>
		<title>修改或取用的注意事項</title>
		<link rel="alternate" type="text/html" href="https://www.openfoundry.org/en/for-developers/1882-2010-07-13-09-53-10"/>
		<published>2008-12-22T14:55:50Z</published>
		<updated>2008-12-22T14:55:50Z</updated>
		<id>https://www.openfoundry.org/en/for-developers/1882-2010-07-13-09-53-10</id>
		<author>
			<name>webmaster</name>
		<email>contact@openfoundry.org</email>
		</author>
		<summary type="html">&lt;p&gt;您當然可以修改自由軟體的原始碼，或者是取用原始碼到自己正在撰寫的新程式當中，但是有些規定必須要注意與遵守。由於各授權條款間的內容差異頗大，有時甚至南轅北轍，因此以下所列僅為鑄造場認為較重要的幾點注意事項，並無法涵蓋所有授權條款的完整內容，以及個別的特殊規定。不過，下列前兩項是很基本的的要求，鑄造場建議您一定要遵守，後兩項要求在各條款間的規定就頗有差異，您若仍有疑問或有必要進一步了解相關細節的話，請參考法政中心的&lt;a href=&quot;https://www.openfoundry.org/law-and-licensing&quot;&gt;各授權條款的中文介紹&lt;/a&gt;，或來信鑄造場詢問。&lt;/p&gt;
</summary>
		<content type="html">&lt;p&gt;您當然可以修改自由軟體的原始碼，或者是取用原始碼到自己正在撰寫的新程式當中，但是有些規定必須要注意與遵守。由於各授權條款間的內容差異頗大，有時甚至南轅北轍，因此以下所列僅為鑄造場認為較重要的幾點注意事項，並無法涵蓋所有授權條款的完整內容，以及個別的特殊規定。不過，下列前兩項是很基本的的要求，鑄造場建議您一定要遵守，後兩項要求在各條款間的規定就頗有差異，您若仍有疑問或有必要進一步了解相關細節的話，請參考法政中心的&lt;a href=&quot;https://www.openfoundry.org/law-and-licensing&quot;&gt;各授權條款的中文介紹&lt;/a&gt;，或來信鑄造場詢問。&lt;/p&gt;
</content>
	</entry>
</feed>
