How to find what to do - Revision history

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:54:05Z

Text replacement - "<translate1>" to "<translate>"

← Older revision		Revision as of 22:54, 2 February 2016
Line 1:		Line 1:
	<languages/>		<languages/>

	<~~translate1~~>		<translate>

	<!--T:1-->		<!--T:1-->

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:53:44Z

Text replacement - "<translate>" to "<translate1>"

← Older revision		Revision as of 22:53, 2 February 2016
Line 1:		Line 1:
	<languages/>		<languages/>

	<~~translate~~>		<translate1>

	<!--T:1-->		<!--T:1-->

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:52:32Z

Text replacement - "<languages1/>" to "<languages/>"

← Older revision		Revision as of 22:52, 2 February 2016
Line 1:		Line 1:
	<~~languages1~~/>		<languages/>

	<translate>		<translate>

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:51:55Z

Text replacement - "<languages/>" to "<languages1/>"

← Older revision		Revision as of 22:51, 2 February 2016
Line 1:		Line 1:
	<~~languages~~/>		<languages1/>

	<translate>		<translate>

Weng Xuetian: 7 revisions imported

2016-02-02T22:43:13Z

7 revisions imported

← Older revision	Revision as of 22:43, 2 February 2016
(No difference)

Weng Xuetian: Text replacement - "" to ""

2016-01-25T21:26:43Z

Text replacement - "<languages />" to "<languages/>"

← Older revision		Revision as of 21:26, 25 January 2016
Line 1:		Line 1:
	<languages />		<languages/>

	<translate>		<translate>

Weng Xuetian at 23:45, 19 December 2012

2012-12-19T23:45:20Z

← Older revision		Revision as of 23:45, 19 December 2012
Line 2:		Line 2:

	<translate>		<translate>

	<!--T:1-->		<!--T:1-->
	This passage is written to be general that can be also applied to other open source project. Many people use some program, and want to help with some project, but don't know what to do.		This passage is written to be general that can be also applied to other open source project. Many people use some program, and want to help with some project, but don't know what to do.

Weng Xuetian: Marked this version for translation

2012-12-19T23:45:11Z

Marked this version for translation

← Older revision		Revision as of 23:45, 19 December 2012
Line 2:		Line 2:

	<translate>		<translate>
			<!--T:1-->
	This passage is written to be general that can be also applied to other open source project. Many people use some program, and want to help with some project, but don't know what to do.		This passage is written to be general that can be also applied to other open source project. Many people use some program, and want to help with some project, but don't know what to do.

	== Find something that scratches your itch ==		== Find something that scratches your itch == <!--T:2-->

			<!--T:3-->
	The very first thing is, find something that scratches your itch. Fix bug that annoying you, implement features that you interest in. Especially for new feature, new feature have more possiblity to introduce bugs, thus why from project point of view, need some people to maintain the code in the future. Bugfixing is much more free, even if you work like "hit and run", nobody will complain about it.		The very first thing is, find something that scratches your itch. Fix bug that annoying you, implement features that you interest in. Especially for new feature, new feature have more possiblity to introduce bugs, thus why from project point of view, need some people to maintain the code in the future. Bugfixing is much more free, even if you work like "hit and run", nobody will complain about it.

	== Contact with developer ==		== Contact with developer == <!--T:4-->

			<!--T:5-->
	Secondly, ask developer about what do they think about it, even for bugfixing, it need to be fixed in the right place， due to Input method is relatively complex (If an application have complex internal state, it is complex).		Secondly, ask developer about what do they think about it, even for bugfixing, it need to be fixed in the right place， due to Input method is relatively complex (If an application have complex internal state, it is complex).

			<!--T:6-->
	If you wrote a long function but finally rejected by developer, it will make you feel quite bad, right?		If you wrote a long function but finally rejected by developer, it will make you feel quite bad, right?

	== Read the TODO-List ==		== Read the TODO-List == <!--T:7-->

			<!--T:8-->
	[[Todo-List]] is something that developers already have in the mind, just they still don't have time to implement yet, while usually it's filled with things that hard to do, but sometimes it will also have some trivial work, but maybe a little bit boring. Those are also work you can help with! It's human nature that people don't want to do some repeated non-creative work, but those are also necessary and will benefit the whole project.		[[Todo-List]] is something that developers already have in the mind, just they still don't have time to implement yet, while usually it's filled with things that hard to do, but sometimes it will also have some trivial work, but maybe a little bit boring. Those are also work you can help with! It's human nature that people don't want to do some repeated non-creative work, but those are also necessary and will benefit the whole project.

	== Conclusion ==		== Conclusion == <!--T:9-->
	Have fun with those open-source project! If you don't need to be under pressure that you have to finish something in some restricted time, just make yourself comfortable and have fun.		Have fun with those open-source project! If you don't need to be under pressure that you have to finish something in some restricted time, just make yourself comfortable and have fun.

			<!--T:10-->
	Well, actually, I have already seen lots of people show interested in some project, but also give up so quickly. It really doesn't matter if you do so, people have their own life and their own interest, we also respect that. No matter when you want to give up, just tell us in advance, so it would be more easier to rearrange the work and priority.		Well, actually, I have already seen lots of people show interested in some project, but also give up so quickly. It really doesn't matter if you do so, people have their own life and their own interest, we also respect that. No matter when you want to give up, just tell us in advance, so it would be more easier to rearrange the work and priority.

	</translate>		</translate>

Weng Xuetian at 19:11, 28 November 2012

2012-11-28T19:11:44Z

← Older revision		Revision as of 19:11, 28 November 2012
Line 4:		Line 4:
	This passage is written to be general that can be also applied to other open source project. Many people use some program, and want to help with some project, but don't know what to do.		This passage is written to be general that can be also applied to other open source project. Many people use some program, and want to help with some project, but don't know what to do.

	The very first thing is, find something that ~~scratch~~ your itch. Fix bug that annoying you, implement features that you interest in. Especially for new feature, new feature have more possiblity to introduce bugs, thus why from project point of view, need some people to maintain the code in the future. Bugfixing is much more free, even if you work like "hit and run", nobody will complain about it.		== Find something that scratches your itch ==

			The very first thing is, find something that scratches your itch. Fix bug that annoying you, implement features that you interest in. Especially for new feature, new feature have more possiblity to introduce bugs, thus why from project point of view, need some people to maintain the code in the future. Bugfixing is much more free, even if you work like "hit and run", nobody will complain about it.

			== Contact with developer ==

	Secondly, ask developer about what do they think about it, even for bugfixing, it need to be fixed in the right place， due to Input method is relatively complex (If an application have complex internal state, it is complex).		Secondly, ask developer about what do they think about it, even for bugfixing, it need to be fixed in the right place， due to Input method is relatively complex (If an application have complex internal state, it is complex).

			If you wrote a long function but finally rejected by developer, it will make you feel quite bad, right?

			== Read the TODO-List ==

			[[Todo-List]] is something that developers already have in the mind, just they still don't have time to implement yet, while usually it's filled with things that hard to do, but sometimes it will also have some trivial work, but maybe a little bit boring. Those are also work you can help with! It's human nature that people don't want to do some repeated non-creative work, but those are also necessary and will benefit the whole project.

			== Conclusion ==
			Have fun with those open-source project! If you don't need to be under pressure that you have to finish something in some restricted time, just make yourself comfortable and have fun.

			Well, actually, I have already seen lots of people show interested in some project, but also give up so quickly. It really doesn't matter if you do so, people have their own life and their own interest, we also respect that. No matter when you want to give up, just tell us in advance, so it would be more easier to rearrange the work and priority.

	</translate>		</translate>

Weng Xuetian at 21:23, 26 November 2012

2012-11-26T21:23:06Z

← Older revision		Revision as of 21:23, 26 November 2012
Line 1:		Line 1:
	<~~langauge~~ />		<languages />

	<translate>		<translate>
Line 6:		Line 6:
	The very first thing is, find something that scratch your itch. Fix bug that annoying you, implement features that you interest in. Especially for new feature, new feature have more possiblity to introduce bugs, thus why from project point of view, need some people to maintain the code in the future. Bugfixing is much more free, even if you work like "hit and run", nobody will complain about it.		The very first thing is, find something that scratch your itch. Fix bug that annoying you, implement features that you interest in. Especially for new feature, new feature have more possiblity to introduce bugs, thus why from project point of view, need some people to maintain the code in the future. Bugfixing is much more free, even if you work like "hit and run", nobody will complain about it.

	Secondly, ask developer about what do they think about it, even for bugfixing, it need to be fixed in the right ~~place~~.		Secondly, ask developer about what do they think about it, even for bugfixing, it need to be fixed in the right place， due to Input method is relatively complex (If an application have complex internal state, it is complex).



	</translate>		</translate>