Difference between revisions of "Contribution"
(→Become a beta tester) |
(→Introduction) |
||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Welcome Contribution}} | {{Welcome Contribution}} | ||
− | + | {{Navbar Contributor Page}} | |
==Introduction== | ==Introduction== | ||
Requests to help GhostBSD [http://www.ghostbsd.org/contribute on GhostBSD home page.] | Requests to help GhostBSD [http://www.ghostbsd.org/contribute on GhostBSD home page.] | ||
+ | There are a lot of [[Projects]] were you can help. | ||
+ | |||
+ | ==Code of Conduct== | ||
+ | If you like to help, to ask for help or wish to give your opinion please consider our [[Code of Conduct]]. | ||
+ | |||
+ | ==Wiki Contribution== | ||
+ | |||
+ | If you like to contribute to this GhostBSD wiki, we will meet us on the [[Wiki Contributor Page]]. | ||
+ | |||
+ | |||
+ | ==Porters Guideline== | ||
+ | |||
+ | If you like to contribute to the GhostBSD development please read the [[Porters Guideline]]. | ||
{{:Join us}} | {{:Join us}} | ||
Line 15: | Line 28: | ||
{{:We Need Feedback!}} | {{:We Need Feedback!}} | ||
− | + | {|class="wikitable" style="width:95%;background:#FFFFFF; border:2px solid #008000;text-align:center;padding: 10px" | |
+ | |- | ||
+ | !colspan="2"|'''Back to the''' [[image:Icon Disti GhostBSD.png|50px|link=Main Page]]'''Wiki Main Page''' | ||
+ | |} | ||
Line 30: | Line 46: | ||
[[Category:Contribution]] | [[Category:Contribution]] | ||
− |
Latest revision as of 06:36, 30 August 2020
Welcome to the Contribution Page. |
Contribution | ||
---|---|---|
Development Contributor Page | Code of Conduct | Wiki Contributor Page |
Back to Wiki Main Page |
Contents
- 1 Introduction
- 2 Code of Conduct
- 3 Wiki Contribution
- 4 Porters Guideline
- 5 Join the GhostBSD Team
- 6 Writers
- 7 Designers
- 8 Developers
- 9 Communicators
- 10 Translators
- 11 Web Developers or Administrators
- 12 Become A Beta Tester
- 13 Introduction
- 14 How To Do That
- 15 Download the latest development release
- 16 Reporting issues
- 17 Eric Turgeon, [08.04.20 13:46] on Telegram
- 18 We need Feedback
Introduction[edit]
Requests to help GhostBSD on GhostBSD home page.
There are a lot of Projects were you can help.
Code of Conduct[edit]
If you like to help, to ask for help or wish to give your opinion please consider our Code of Conduct.
Wiki Contribution[edit]
If you like to contribute to this GhostBSD wiki, we will meet us on the Wiki Contributor Page.
Porters Guideline[edit]
If you like to contribute to the GhostBSD development please read the Porters Guideline.
Join the GhostBSD Team[edit]
If you want to take an active hand in making GhostBSD even better, there are many ways you can help. What role do you want to fill?
This is a starting point.
There are many ways to participate in GhostBSD, this page is just your starting spot. Financial contributions are discussed on the funding page. Making changes to the GhostBSD wiki is discussed on the wiki editing page.
Writers[edit]
Description of this role: Writers write website content, manuals, guides, blog posts, and articles.
- Skills you possess or want to learn
- Writing, editing, grammar, technical, explaining complex ideas well, teaching, XML, Wiki markup, technical knowledge
Team/Project | Example tasks |
---|---|
Docs |
|
Articles |
|
News |
|
Development Docs |
|
If your interested please contact us.
Designers[edit]
Description of this role: Designers create artwork, logos, website, and user interface designs.
- Skills you possess or want to learn
- Ink scape, GIMP, OO.org, design, usability/interaction
Team/Project | Example tasks |
---|---|
Design |
|
Fonts |
|
Usability |
|
If your interested please contact us.
Developers[edit]
Description of this role: Developers write new features, track down bugs, and help package software.
- Skills you possess or want to learn
- Programming, Packaging, Debugging, BSD
Team/Project | Example tasks |
---|---|
Infrastructure |
|
Release Engineering |
|
Internationalization(I18n) |
|
Packaging and Porting |
|
Bug triage |
|
Usability |
|
Websites |
|
Fonts |
|
Testing |
|
If your interested please contact us.
Communicators[edit]
Description of this role: Communicators interact with people at events and online!
- Skills you possess or want to learn
- People skills, event organization, customer service/support, enthusiasm
Team/Project | Example tasks |
---|---|
Ambassadors |
|
Free Media |
|
Marketing |
In addition, * support the efforts of other GhostBSD projects to spread GhostBSD and help provide a central repository of ideas and information that can be used to deliver GhostBSD to new audiences. |
Mentoring |
|
Support/help |
|
Usability |
|
Fonts |
|
If you are interested, please contact us.
Translators[edit]
Description of this role: Translators, these help to maintain & expand ghostbsd supported languages.
- Skills you possess or want to learn
- English, Non-English native language, technical knowledge, diff, PO, translation, babel tool (kbabel, etc.)
Team/Project | Example tasks |
---|---|
Work with Fonts |
|
Work with OS Developer |
|
Work with I18n (internationalization) |
|
If your interested please contact us.
Web Developers or Administrators[edit]
Description of this role: Web developers administrators build and maintain the website infrastructure.
- Skills you possess or want to learn
- Php, HTML, CSS, Drupal, Media Wiki, Web app development, system administration
Team/Project | Example tasks |
---|---|
Infrastructure |
|
Release Engineering |
|
Websites |
|
If your interested please contact us.
Become A Beta Tester[edit]
Introduction[edit]
If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the GhostBSD community is by reporting problems you encounter while using GhostBSD.
If you have a spare system, or virtual machine, you can also download and try out the latest stable, beta or release candidate available. These versions are still in testing and have not been officially released yet. Having as many people as possible using GhostBSD on many different hardware configurations assists the project in finding and fixing bugs. This makes using GhostBSD better for everyone. Subscribing to the GhostBSD Development mailing list is a good way to keep up-to-date on the availability of testing snapshots and any major bugs that are found within a snapshot.
If becoming a tester interests you, subscribe to the development mailing list. As new testing versions become available they will be announced on this list. You will also be able to see what problems other testers are finding and can check to see if the problem exists on your hardware as well.
Anyone can become a beta tester. Follow these tips so that you can accurately describe your findings so they can be fixed as soon as possible:
- before sending an email, search the testing mailing list to see if anyone else has reported a similar problem.
- when reporting a new issue, use a descriptive subject in your email that includes the error and the version of GhostBSD. Ideally, the subject should be short (8 words or less), and contains key words about the error. An example would be "bxPKG on 3.0-BETA1 Error while fetching".
- ensure that the body of your email includes the GhostBSD version and architecture (e.g. 3.0-BETA1, Gnome 32-bit ISO version).
- give a short (2-3 sentences) description of how to recreate the error. If there is an error message, include its text.
- include any other info that may be useful (e.g. this seems to work on my 32 bit system or this used to work on 2.5).
- if the problem appears to be hardware related, include a copy of /var/run/dmesg.boot as this file shows the hardware that was probed the last time the GhostBSD system booted.
How To Do That[edit]
If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the GhostBSD community is by reporting problems you encounter while using GhostBSD.
If you have a spare computer system or virtual machine, try our latest alpha, beta or release candidate snapshot. These versions are still in testing and have not been officially released yet. Having as many people as possible using GhostBSD on many different hardware configurations assists the project in finding and fixing bugs. This makes using GhostBSD better for everyone.
To become a tester, contact us at one of the following online locations:
- Telegram at https://t.me/ghostbsd
- The IRC channels are
#ghostbsd
and#ghostbsd-dev
on irc://irc.freenode.net. - You can access the IRC channel via our web user interface.
- The forums are available at http://forums.ghostbsd.org/
Download the latest development release[edit]
The latest installation media for testing can be found here.
Reporting issues[edit]
Everyone is eligible to become a beta tester. To aid us in fixing problems as quickly as possible, please accurately report findings using these tips:
- Before reporting a bug, search the forum to see if anyone else has reported a similar problem.
- When reporting a new issue, use a descriptive subject that includes the error and the version of GhostBSD. Ideally, the subject should be concise and contain key words about the error.
- Ensure that the body of the bug report includes the GhostBSD version.
- Give a good description of how to recreate the error. If there is an error message, include its text.
- Include any additional info that may be useful.
- If the problem appears to be hardware related, include a copy of the
dmesg.boot
file located in the /var/run directory.
Eric Turgeon, [08.04.20 13:46] on Telegram[edit]
We moved our project management to GitHub and we will be using GitHub for bug and feature reports.
- If you need to report a bug related to the ISO or installation report them at
ISO-Issues. - If you need to report a bug related to OS, kernel, drivers report them at
Kernel issues - If you need to report a bug related to software report them at
Software issues
- If you need help or want to give feedback please visit
GhostBSD-Forum
or
on Telegram
Eric Turgeon, [08.04.20 13:47]
- I think an new feature request should go at ghostbsd-build.
We need Feedback[edit]
If you find some typographical or grammar error in our documentation, if you have thought of a way to make this manual better, we would love to hear from you! You can report it by the Problem Report system, documentation forums or the docs mailing list.
When submitting any error be sure to mention the specific page and some of the surrounding text so we can find it easily.
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it.
Also you can create a login account and fix it yourself. Your contributions are welcomed, however link spam or other unwanted additions will be removed swiftly and mercilessly. You simply have to create a login account in order to assist.
Back to the Wiki Main Page |
---|