Main Page: Difference between revisions

From GNU MediaGoblin Wiki
Jump to navigation Jump to search
mNo edit summary
 
(54 intermediate revisions by 37 users not shown)
Line 1: Line 1:
= Want to Join the MediaGoblin Community? =
該aquapon園丁只設置了,一般都是很高興能執行他們的系統,並能夠得到進入魚生產質量上乘的肥料為他或她的植物。許多初來乍都太激動了,他們完成了破壞他們的系統。你擁有這一切提前啟動的得當,重要的是拿東西慢是肯定的。在複合養殖系統中,小魚吃什麼飼料給他們製造有用的,這再排泄廢物這將是對尿液和糞便的方法。通常情況下,魚的糞便抽上長出的床,它肯定是由細菌轉化。 <br><br>通過提供礫石,hydroton,或其他廉價複合養殖膨脹介質。因此,問題仍然是。怎麼我收到我的系統有足夠的細菌?這可能是簡單的。細菌是在我們周圍的空氣一應俱全。永遠不要買的細菌。這些細菌會聚集的地方肯定是有食品,所有這些。食品獨家型是液態廢物的風格。當然,氨,同時它是一個相關聯的處理氮正常使用。 <br><br>硝化細菌消除浪費和轉換那些已經無害的魚和有利於植物的物質。這個週期被稱為硝化作用。保證了硝化過程成為。有需要應beenough菌處理的魚的排泄物很快將整個系統運行的水平。通常是相當簡單的量的水達的成長空間轉換可能低至1:1或高達1〜3本質上,較長區域的細菌必須繼續,為廢物管理的更多容量,你會得到。許多系統都可以真的只是為這些小動物來控制更多的表面介質的系統。在我看來,媒體基於系統最完善的位於系統讓自己開始。 <br><br>有幾個人真正使用尿氨通常的原因,雖然這會污染他們的系統。提前添加你的魚,只是把帽子用大量每50加侖氨的水系統。在幾個星期內,你可以測試你的水(在使用水族館檢測試劑盒)來發現的氨你有,數額亞硝酸鹽和究竟有多少硝酸鹽存在。對於充足的硝酸鹽,但沒有太多的氨,你所有的設置去。現在可以安全的魚。添加魚,並協助您複合養殖系統採取結構!<br><br>For those who have any kind of questions relating to where along with how you can make use of [http://www.myfarm.com.tw/services.html 家庭自種], you are able to email us at our page.

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

We observe the [https://www.djangoproject.com/conduct/ Django code of conduct]. Be welcoming, friendly, and patient!

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

== Visit MediaGoblin Live Instances ==

Browse MediaGoblin [[Live instances|live instances]], add new ones and comment on those that appear to be down.

=How Can you help ?=

== File Bugs / Triage Bugs ==

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

* [[File Bugs]] -- notes on filing new bugs/issues/feature requests
* [[Feature Ideas]] -- notes on possible features
* [[Triage Bugs]] -- notes on triaging

== Send Encouragement / Spread the Word ==

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See [https://mediagoblin.org/pages/join.html our join page] for links.


== Write Documentation / Edit Documentation ==

* [[ManualStandards]] - covers the standards for writing the user manual (forthcoming.)

== Test MediaGoblin ==

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?

* [[User Experience]] - user experience testing. Includes link to an instance you can try!
* [[UnitTests|Unit Tests]] - all about the unit tests
* [[Manual_Functional_Testing|Manual Functional Testing]] - a great way to get to know MediaGoblin.


== Translate MediaGoblin ==

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources.
Translating MediaGoblin is very easy with a web interface, so there is no programming knowledge required at all.

* [[Translations]] - How to translate stuff or update the translations


== Run your own MediaGoblin Instance ==

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

The primary documentation for this is at [http://docs.mediagoblin.org http://docs.mediagoblin.org] but here are some additional tips:

* [[Configure_MediaGoblin|Configuration]] - Learn about MediaGoblin configuration files and file options.
* [[Deployment]] - General deployment advice
* [[Virtual Machine Hosting]] - Deploy your own publicly available MediaGoblin server using [http://aws.amazon.com/free/?utm_source=adwords&utm_medium=cpc&utm_campaign=CPC_Google_AWS_ec2&utm_content=TextV01_PP_V01_EC2&trk=CPC_Google_AWS_ec2 Amazon's free EC2 tier].

= Technical project documentation =

The technical docs, that are more finished and the ones that are better maintained near the code (so they stay up to date) are in the more technical chapters of the [http://docs.mediagoblin.org/ main documentation].
* [[Storage]] - How MediaGoblin's internal storage system works.
* [[Processing]] - What happens after you submit your image/video/etc? Processing! More about that.
* [https://gitorious.org/mediagoblin/mediagoblin/blobs/master/extlib/README External Library Policy] - covers use of external libraries
* [[User:Cwebber/braindumps]] - Chris Webber's braindumps (you can help refactoring these into real sections of the site!)
* [[Multiple media support]] - Design plan for multiple media support

== Write Code / Fix Code ==

MediaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

* [[HackingHowto|Hacking]] - notes on making and sending in code contributions
** [[BeginnersCorner|Beginner's Corner]] - resources for those who are new to Python or Git.
** ''Started from an older version of the Hacking Howto? We switched from buildout->virtualenv, so look at [[Moving from buildout to virtualenv]] for information on how to move over.''
* [[Git workflow]] - How to go about submitting patches via git.
* [[Code review tips]] - Tips on how to go about doing local code review

== Write a plugin ==

If you start, you'll find some basic documentation [http://docs.mediagoblin.org/#part-4-developer-s-zone| in the docs site]

You've made a plugin ? List it here :

[[Available_Plugins|Available plugins]]

You've written a plugin ? You got some tips to share ? A tutorial idea ? Please do :
[[PluginsTips|Plugins Tips]]

= Android client =

See [[Android Client]]

= Inner workings of the secret sanctum =

* [[ReleaseProcess|Release Process]] - covers the release process
* [[Update the website]] - Learn how to update mediagoblin.org!

=FAQ=

[[GMG FAQ]]

Latest revision as of 01:11, 17 October 2023

Want to Join the MediaGoblin Community?

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

We observe the Django code of conduct. Be welcoming, friendly, and patient!

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

Visit MediaGoblin Live Instances

Browse MediaGoblin live instances, add new ones and comment on those that appear to be down.

How Can you help ?

File Bugs / Triage Bugs

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

Send Encouragement / Spread the Word

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See our join page for links.


Write Documentation / Edit Documentation

  • ManualStandards - covers the standards for writing the user manual (forthcoming.)

Test MediaGoblin

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?


Translate MediaGoblin

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources. Translating MediaGoblin is very easy with a web interface, so there is no programming knowledge required at all.

  • Translations - How to translate stuff or update the translations


Run your own MediaGoblin Instance

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

The primary documentation for this is at http://docs.mediagoblin.org but here are some additional tips:

Technical project documentation

The technical docs, that are more finished and the ones that are better maintained near the code (so they stay up to date) are in the more technical chapters of the main documentation.

Write Code / Fix Code

MediaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

Write a plugin

If you start, you'll find some basic documentation in the docs site

You've made a plugin ? List it here :

Available plugins

You've written a plugin ? You got some tips to share ? A tutorial idea ? Please do :

Plugins Tips

Android client

See Android Client

Inner workings of the secret sanctum

FAQ

GMG FAQ