https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&user=Dawnfoster&feedformat=atomYocto Project - User contributions [en]2024-03-28T17:51:34ZUser contributionsMediaWiki 1.39.5https://wiki.yoctoproject.org/wiki/index.php?title=BletchleyPark&diff=15999BletchleyPark2015-09-28T14:48:58Z<p>Dawnfoster: added logistics for the day of details. Removed names of those not attending.</p>
<hr />
<div>This page is for information related to an extracurricular trip to Bletchley Park before ELCE. Note that this is *not* a sponsored event of any kind.<br />
<br />
== Logistics ==<br />
<br />
For those of us making the trip, meet at the Bletchley Park train station at 9:50am on Saturday, October 3. We'll do a tour, find some lunch mid-day and wrap up around 4pm.<br />
<br />
== What ==<br />
<br />
Leave for ELCE a couple of days early and spend two nights near Bletchley Park, Buckinghamshire, a historical place in the world of computing. Spend the day Friday 2 October and/or Saturday 3 October at Bletchley Park. Make sure to arrive in Dublin by Sunday 4 October.<br />
<br />
* [http://www.tnmoc.org/ The National Museum of Computing at Bletchley Park]<br />
* [http://www.bletchleypark.org.uk/ Bletchley Park Museum]<br />
<br />
== When ==<br />
<br />
October 2-4, 2015<br />
<br />
For reference, ELCE starts Monday, 5 October 2015, and continues through Weds, 7 October. YP Developer Day is planned for Thurs 8 Oct, and the OpenEmbedded General Assembly and EU Developer's Meeting is planned for Friday 9 Oct.<br />
<br />
== How ==<br />
<br />
Lodging: currently in research. There are several small inns and also several AirBNBs in the area, so group housing (with private rooms) is a possibility in the range of £100/night.<br />
<br />
Arrival options: TBD (train from Heathrow, group car)<br />
<br />
Departure options under discussion:<br />
* train back to Heathrow, flight to Dublin<br />
* train & ferry to Dublin (http://www.seat61.com/Ireland.htm#.VbEVHflVhBc)<br />
* rent a car as a group & drive to ferry<br />
* <strike>swim</strike><br />
<br />
=== Lodging ===<br />
<br />
Bletchley Park is about 11 minutes drive from Milton Keynes, the nearby commerce center. There are rail stops at both locations.<br />
<br />
Options include:<br />
* figuring it out individually<br />
* finding a group rate at a pub or hotel<br />
* finding an AirBNB large enough for everyone interested<br />
* other ideas?<br />
<br />
Here's one AirBNB option in Silverstone, about 20 minutes away:<br />
https://www.airbnb.com/rooms/7436921<br />
<br />
or a hotel in Milton Keynes itself:<br />
http://www.yelp.co.uk/biz/jurys-inn-hotel-milton-keynes-2?osq=lodging<br />
<br />
=== Travel in Milton Keynes / Bletchley ===<br />
<br />
It occurred to me at some point that lodging options might depend on the availability of a rental car, although Uber and taxis also exist. If anyone has specific experience locally we'd love to hear it. <br />
<br />
=== Travel to Dublin ===<br />
<br />
Rail: There is a system of train-to-ferry called RailSail via Virgin Trains and Irish Ferries. The train leaves Milton Keynes at 8:56am. Riders switch to the ferry in Holyhead, Wales, and arrive in Dublin at 5:25pm, at a cost of £42-47. There is a second trip that day leaving at 12:04pm and arriving at 7:15pm. <br />
<br />
Car: It is possible to rent a car in Milton Keynes and drive to either Liverpool or Holyhead to catch a ferry. It could save 1-2 hours over going by rail, but might involve a few side trips, a pub lunch...<br />
<br />
Car #2: A much longer route would be going down through Swansea to Pembroke, ferry to Wexford, Ireland, and then drive up the Irish west coast to Dublin. This adventure would take about 12 hours to complete.<br />
<br />
Plane: Going back to Heathrow is probably the most expedient and least fun method. An hour and a half train costs about £44 and there are many cheap flights to Dublin daily.<br />
<br />
== Who ==<br />
<br />
Please add yourself to this list to be included in communications about this event.<br />
<br />
* Jefro<br />
* David Anders (Sep 26th to Oct 4th)<br />
* Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=BletchleyPark&diff=15232BletchleyPark2015-07-24T00:37:28Z<p>Dawnfoster: /* Who */</p>
<hr />
<div>This page is for information related to an extracurricular trip to Bletchley Park before ELCE. Note that this is *not* a sponsored event of any kind - it is <br />
<br />
== What ==<br />
<br />
Leave for ELCE a couple of days early and spend two nights near Bletchley Park, Buckinghamshire, a historical place in the world of computing. Spend the day Friday 2 October and/or Saturday 3 October at Bletchley Park. Make sure to arrive in Dublin by Sunday 4 October.<br />
<br />
* [http://www.tnmoc.org/ The National Museum of Computing at Bletchley Park]<br />
* [http://www.bletchleypark.org.uk/ Bletchley Park Museum]<br />
<br />
== When ==<br />
<br />
October 2-4, 2015<br />
<br />
For reference, ELCE starts Monday, 5 October 2015, and continues through Weds, 7 October. YP Developer Day is planned for Thurs 8 Oct, and the OpenEmbedded General Assembly and EU Developer's Meeting is planned for Friday 9 Oct.<br />
<br />
== How ==<br />
<br />
Lodging: currently in research. There are several small inns and also several AirBNBs in the area, so group housing (with private rooms) is a possibility in the range of £100/night.<br />
<br />
Arrival options: TBD (train from Heathrow, group car)<br />
<br />
Departure options under discussion:<br />
* train back to Heathrow, flight to Dublin<br />
* train & ferry to Dublin (http://www.seat61.com/Ireland.htm#.VbEVHflVhBc)<br />
* rent a car as a group & drive to ferry<br />
* <strike>swim</strike><br />
<br />
== Who ==<br />
<br />
Please add yourself to this list to be included in communications about this event.<br />
<br />
* Jefro<br />
* David Anders (Sep 26th to Oct 4th)<br />
* David Cobbley<br />
* Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=User:Dawnfoster&diff=15231User:Dawnfoster2015-07-24T00:37:11Z<p>Dawnfoster: Blanked the page</p>
<hr />
<div></div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=BKMs_for_Package_Updating&diff=275BKMs for Package Updating2010-11-10T21:08:18Z<p>Dawnfoster: Blanked the page and redirected it to the correct location</p>
<hr />
<div>#REDIRECT [[Best_Known_Methods_(BKMs)_for_Package_Updating]]</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=241Launch Plan October 20102010-10-26T22:09:52Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Final decision on where the FAQ lives & move it if necessary - Scott</s><br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release, announcements and conference presentation announcing Yocto<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
* Final round of testing links to make sure they work - Dave<br />
** http://www.yoctoproject.org/community/bugs - test bugzilla links<br />
** http://www.yoctoproject.org/download - test all links, esp download / mirrors<br />
** http://www.yoctoproject.org/community<br />
** http://www.yoctoproject.org/community/discussions<br />
** http://www.yoctoproject.org/community/documentation<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Processes_and_Activities&diff=240Processes and Activities2010-10-26T22:00:32Z<p>Dawnfoster: </p>
<hr />
<div>Welcome to the Processes and Activities Page!<br />
<br />
* [[BKMs for Package Updating]]<br />
* [[SDK Generator]]<br />
* [[QA]]<br />
* [[Kernel]]<br />
* [[Core]]<br />
* [[Bugzilla Configuration and Bug Tracking]]<br />
* [[Yocto Release Engineering]]</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Distro&diff=239Distro2010-10-26T21:58:57Z<p>Dawnfoster: /* Releasing Yocto */</p>
<hr />
<div>#REDIRECT [[Yocto Release Engineering]]</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Release_Engineering&diff=238Yocto Release Engineering2010-10-26T21:57:24Z<p>Dawnfoster: moved distro to this page</p>
<hr />
<div>== Yocto Linux Release Engineering Procedures ==<br />
<br />
This document describes release engineering procedures for the Yocto Linux project. <br />
<br />
While this is intended to be a living document, this process is becoming more stable now that we're entering M3. Further changes will be considered if they are accompanied with strong reasoning and evidence of improvement.<br />
<br />
== Naming Conventions ==<br />
<br />
Official/public releases will use the following scheme: '''X.Y.Z'''<br />
<br />
* X = major release number<br />
* Y = minor release number<br />
* Z = minor rev release number<br />
<br />
Major release number changes imply compatibility changes with previous releases. Minor release number changes imply significant changes up to, but not including compatibility changes. Minor rev number changes are for minor issues such as simple bugfixes, security updates, etc. <br />
<br />
Nightly releases will be named using the following scheme: '''image-name-0.8.0-date-buildnum.extension''', where date is the datestamp of the build, e.g, 20100715, and buildnum is a build counter, e.g, 1, 2, 3, in case more than one build is generated the same day.<br />
<br />
Milestone releases will be named using the following scheme: '''image-name-0.8.0-date-milestonenum-buildnum.extension''', where the field definitions are the same as above with the addition of milestonenum, e.g. M3.<br />
<br />
Our first public release (October) will be 0.9.0, with a 1.0.0 release to follow in Spring 2011.<br />
<br />
== Release Procedure for Yocto ==<br />
<br />
Notes on the things that need to be done:<br />
<pre><br />
Set DISTRO_VERSION in poky.conf<br />
git commit -a -m "Pinky 3.1.2 Release"<br />
git tag -a pinky-3.1.2 -m "Tag Pinky 3.1.2"<br />
git archive pinky-3.1.2 | bzip2 > /tmp/poky-pinky-3.1.2.tar.bz2<br />
scp /tmp/poky-pinky-3.1.2.tar.bz2 o-hand.com:/srv/www/pokylinux.org/releases/poky-pinky-3.1.2.tar.bz2<br />
<br />
cd docmentation/handbook<br />
make<br />
scp -r poky-handbook.tgz poky-handbook.html poky-handbook.pdf *.png *.xml *.css *.svg o-hand.com:/srv/www/pokylinux.org/releases/purple-3.2/doc/<br />
<br />
Edit Poky web pages (three version references, two in wordpress, one on the front page)<br />
Post on Poky Blog<br />
Port on Poky mailing list<br />
</pre><br />
<br />
== Types of Releases ==<br />
<br />
==== Internal/Nightly Releases ====<br />
<br />
Nightly releases can be considered a "base class" of the release system. Weekly releases are generated directly from them, and otherwise the nightly release build status serves as a fundamental health status of the builds. Nightly releases are built directly from poky master and '''failures should be immediately addressed or the offending changes reverted'''.<br />
<br />
==== Internal/QA Weekly Releases ====<br />
<br />
These releases are the basic unit of internal progress for the Yocto project.<br />
<br />
Every Wednesday (mid-day US Pacific time), the nightly build will generate a release which gets submitted to QA that evening (the start of China's Thursday).<br />
<br />
If this weekly release passes initial testing from QA, the QA team will continue on to run their full weekly test suite.<br />
<br />
If the weekly release does ''not'' pass initial testing from QA, the QA team will report this to the distro team and the distro team will focus on addressing these issues the next day. If the distro team lead believes these changes will resolve the reported issues, he/she will submit the nightly build for that day to QA again. <br />
<br />
Weekly releases will be made available to the QA team via a web-accessible directory on the autobuilder. Within this directory, a tarball of all of the above components will be available to make downloading the release more convenient. <br />
<br />
==== Internal/QA Milestone Releases ====<br />
<br />
These releases are performed at the end of a milestone period and are used to measure our progress in delivering new features to Yocto Linux.<br />
<br />
To generate a milestone release, a snapshot of poky master is taken and pushed to a builds/milestone branch. This branch then serves as a stabilization branch, allowing poky master to continue feature development. builds/milestone can then be improved by pulling in fixes via cherry-picking from poky master.<br />
<br />
The Release Criteria are the Milestone requirements as defined in [[OSEL-1.0-schedule]]. If features are missing, a decision based on input from the management team needs to approve exceptions to the release criteria.<br />
<br />
==== Official/public releases ====<br />
<br />
These are the final, QA-tested, manager-approved releases of Yocto Linux which will '''WOW''' our customers and change the future of embedded Linux devices. Words can barely describe the awesomeness of these SDK and filesystem images!<br />
<br />
== Release Components ==<br />
<br />
Yocto Linux includes a number of software components to be included in each release. These include:<br />
<br />
==== Distro Components ====<br />
<br />
* Bootable QEMU images of minimal and sato for the following architectures: qemux86, qemux86-64, qemuarm, qemumips, qemuppc<br />
** A bootable QEMU image consists of a kernel file, a kernel modules tarball, and root filesystem tarball<br />
* Non-emulated machine targets (e.g, netbook, emenlow) will include appropriate images (e.g, live images) of minimal and sato.<br />
<br />
==== SDK Components ====<br />
<br />
* meta-toolchain tarballs for the following host/target combinations: i586/[arm|i586|mips|ppc|x86_64], x86_64/[arm|i586|mips|ppc|x86_64]<br />
* Bootable SDK images for the following architectures: qemux86, qemux86-64, qemuarm, qemumips, qemuppc<br />
* SDK plugins for the following IDEs: Anjuta, Eclipse<br />
<br />
Currently the SDK plugins are not being generated with the remaining build output. Jessica and Scott will need to define a process for this that makes sense before public release. There are issues to be take into consideration such as how the plugins are distributed (Anjuta and Eclipse have their own plugin repositories, for example). <br />
<br />
==== Other components ====<br />
<br />
* gitinfo - a file which includes information about which commit the images were built from<br />
* Changelog - a file which includes git log information between the last released version and the newly built version<br />
* Bugfixes - a list of bugs, extracted from the Changelog, that were fixed between the last released version and the newly built version<br />
<br />
== Official/public Release Procedures ==<br />
<br />
A sign-off process needs to be established for official/public Yocto releases, which would include QA and possibly managerial signatures. <br />
<br />
24 hours before the release is made public, the release images would be mirrored to external locations and allow time for the blog and mailing list announcements to be written. The final steps in releasing would be ready to be performed in a matter of seconds:<br />
<br />
* Move the release directory from a staging area into the public web server area<br />
* Push the web site update including new release information<br />
* Post the pre-written release announcement on the blog and mailing lists<br />
<br />
===Steps to release Yocto ===<br />
<br />
Run an autobuilder "generate-release" build. This will create images in /srv/www/vhosts/autobuilder.pokylinux.org/generate-release/<datestamp>/. Rename these files with the appropriate release name and version (Scott will have a script to do this by the next release). <br />
<br />
For post-Green releases, there will be a release staging area that will be used to mirror the output before the files are released on the public web site.<br />
<br />
On release branch:<br />
* Set DISTRO_VERSION in poky.conf<br />
* Update handbook references to stable release (introduction.xml, master branch needs this too)<br />
* Update version reference and updated date in handbook (poky-handbook.xml)<br />
* git commit -a -m "Purple 3.2 Release"<br />
* git tag -a purple-3.2 -m "Tag Purple 3.2"<br />
* git archive purple-3.2 --prefix=purple-3.2/ | bzip2 > /tmp/poky-purple-3.2.tar.bz2 scp /tmp/poky-purple-3.2.tar.bz2 o- hand.com:/srv/www/pokylinux.org/releases/poky-purple-3.2.tar.bz2<br />
On master branch:<br />
* Set DISTRO_VERSION in poky.conf to new version<br />
* Update version reference and updated date in handbook (poky-handbook.xml)<br />
<br />
* cd handbook<br />
* make<br />
* scp -r poky-handbook.tgz poky-handbook.html poky-handbook.pdf *.png *.xml *.css *.svg o-hand.com:/srv/www/pokylinux.org/releases/purple-3.2/doc/<br />
* scp -r poky-handbook.tgz poky-handbook.html *.png *.xml *.css *.svg o-hand.com:/srv/www/pokylinux.org/releases/doc/<br />
(or copy across by hand when remotely connected to machine?)<br />
* Edit web pages (website is controlled from a git repo) <br />
**support/index.php<br />
**getit/index.php<br />
**index.php<br />
**poky-wp-theme/common-funcs.inc<br />
**poky-wp-theme/front-page.php<br />
* Post release announcement on Blog <br />
* Post release announcement on mailing list</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=237Launch Plan October 20102010-10-26T21:36:56Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Final decision on where the FAQ lives & move it if necessary - Scott</s><br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release, announcements and conference presentation announcing Yocto<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
* Final round of testing links to make sure they work - Dave<br />
** http://www.yoctoproject.org/community/bugs - test bugzilla links<br />
** http://www.yoctoproject.org/download - test all links, esp download / mirrors<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=235Community Guidelines2010-10-26T21:23:03Z<p>Dawnfoster: /* Wiki Guidelines */</p>
<hr />
<div>==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our [http://www.yoctoproject.org/tos Terms of Service].<br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our [http://www.yoctoproject.org/community/discussions mailing lists]<br />
* Search the [http://www.yoctoproject.org/ Yocto Project website]<br />
<br />
==Wiki Guidelines==<br />
<br />
You can [http://www.yoctoproject.org/community/documentation learn more about our documentation] on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas on the Yocto Project website.<br />
* '''Must be a registered user''': If you want to edit the wiki, you need to [[Special:UserLogin|create an account]] and confirm your email address (you'll get an email after registering with a confirmation link). Anyone can create an account.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
[http://www.yoctoproject.org/community/discussions More information about our mailing lists] can be found on the Yocto Project website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
[http://www.yoctoproject.org/community/discussions More information about our IRC channels] can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
* '''Web access''': If you don't normally use IRC and want to try it out, you can use the [http://webchat.freenode.net/ freenode Web IRC] chat.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the [http://www.yoctoproject.org/community/bugs Yocto Bugzilla].<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
What to do if you find a bug<br />
* '''Search first''': Try to avoid filing duplicates by searching to see whether your issue has already been filed.<br />
* '''Ask''': You can ask on our mailing lists or IRC channels to see if anyone has seen this issue before to gather more details or see if someone has a workaround.<br />
* '''Submit a bug report''': Give us as many details as possible about what happened and how your issue can be reproduced.<br />
* '''Track our progress''': Get feedback from the development community and track resolution status.<br />
* '''Provide a fix''': Use the tools, project wiki and git source repository in the Yocto Project to fix the problem yourself. <br />
<br />
Learn more about [[Bugzilla_Configuration_and_Bug_Tracking|our process for reporting bugs]].<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=234Launch Plan October 20102010-10-26T20:30:26Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Final decision on where the FAQ lives & move it if necessary - Scott</s><br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release, announcements and conference presentation announcing Yocto<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
* Final round of testing links to make sure they work (test from website downloads pages, etc.) - Dave<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=233Launch Plan October 20102010-10-26T19:28:28Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Final decision on where the FAQ lives & move it if necessary - Scott</s><br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release, announcements and conference presentation announcing Yocto<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=232Launch Plan October 20102010-10-26T19:18:54Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* Final decision on where the FAQ lives & move it if necessary - Scott<br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release, announcements and conference presentation announcing Yocto<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=231Launch Plan October 20102010-10-26T19:12:57Z<p>Dawnfoster: /* Schedule for October 26 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release, announcements and conference presentation announcing Yocto<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=230Launch Plan October 20102010-10-26T19:11:57Z<p>Dawnfoster: </p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out on mailing lists, etc.<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''7am UK / 11pm Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''9am UK / 1am Pacific'''<br />
* Publish press release - Amanda<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave<br />
<br />
'''8pm UK / Noon Pacific'''<br />
* Dinner presentation - Dirk</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=229Launch Plan October 20102010-10-26T19:10:27Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out on mailing lists, etc.<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''am Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=228Launch Plan October 20102010-10-26T19:09:51Z<p>Dawnfoster: /* Schedule for October 26 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* 9am UK / 1am Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out on mailing lists, etc.<br />
* 8pm UK / Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=227Launch Plan October 20102010-10-26T19:08:25Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Finish any last minute content changes - Scott<br />
* Announcement blog post - Dave<br />
* <s>Create checklist - Dawn</s><br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* <s>Fix permissions so that anonymous users can't edit pages - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project:General_disclaimer&diff=226Yocto Project:General disclaimer2010-10-26T18:47:40Z<p>Dawnfoster: Created page with 'Please adhere to our Community Guidelines and [http://www.yoctoproject.org/tos Terms of Service] when contributing to the Yocto Project wiki.'</p>
<hr />
<div>Please adhere to our [[Community Guidelines]] and [http://www.yoctoproject.org/tos Terms of Service] when contributing to the Yocto Project wiki.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project:About&diff=225Yocto Project:About2010-10-26T18:45:42Z<p>Dawnfoster: Created page with 'The Yocto Project™ is an open source collaboration project that provides templates, tools and methods to help you create custom Linux-based systems for embedded products regard…'</p>
<hr />
<div>The Yocto Project™ is an open source collaboration project that provides templates, tools and methods to help you create custom Linux-based systems for embedded products regardless of the hardware architecture. The Yocto Project includes the Poky Build System as one of its components, which is a derivative of and is compatible with the OpenEmbedded Build System.<br />
<br />
[http://www.yoctoproject.org/ Learn more about the Yocto Project] by visiting the project home page.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project:Privacy_policy&diff=223Yocto Project:Privacy policy2010-10-26T18:44:53Z<p>Dawnfoster: Created page with '[http://www.yoctoproject.org/privacy Privacy Policy] for the Yocto Project.'</p>
<hr />
<div>[http://www.yoctoproject.org/privacy Privacy Policy] for the Yocto Project.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=221Launch Plan October 20102010-10-26T18:40:07Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* <s>Publish FAQ - Scott</s><br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* <s>Minor wiki cleanup - Dawn</s><br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Fix permissions so that anonymous users can't edit pages - Dawn / Mike<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=220Launch Plan October 20102010-10-26T18:39:34Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Fix permissions so that anonymous users can't edit pages - Dawn / Mike<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=219Launch Plan October 20102010-10-26T18:37:06Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
* Add Yocto logo and favicon to the wiki - Richard<br />
* Fix permissions so that anonymous users can't join - Dawn / Mike<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=218Community Guidelines2010-10-26T18:32:27Z<p>Dawnfoster: /* Overview and General Guidlines */</p>
<hr />
<div>==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our [http://www.yoctoproject.org/tos Terms of Service].<br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our [http://www.yoctoproject.org/community/discussions mailing lists]<br />
* Search the [http://www.yoctoproject.org/ Yocto Project website]<br />
<br />
==Wiki Guidelines==<br />
<br />
You can [http://www.yoctoproject.org/community/documentation learn more about our documentation] on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas on the Yocto Project website.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
[http://www.yoctoproject.org/community/discussions More information about our mailing lists] can be found on the Yocto Project website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
[http://www.yoctoproject.org/community/discussions More information about our IRC channels] can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
* '''Web access''': If you don't normally use IRC and want to try it out, you can use the [http://webchat.freenode.net/ freenode Web IRC] chat.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the [http://www.yoctoproject.org/community/bugs Yocto Bugzilla].<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
What to do if you find a bug<br />
* '''Search first''': Try to avoid filing duplicates by searching to see whether your issue has already been filed.<br />
* '''Ask''': You can ask on our mailing lists or IRC channels to see if anyone has seen this issue before to gather more details or see if someone has a workaround.<br />
* '''Submit a bug report''': Give us as many details as possible about what happened and how your issue can be reproduced.<br />
* '''Track our progress''': Get feedback from the development community and track resolution status.<br />
* '''Provide a fix''': Use the tools, project wiki and git source repository in the Yocto Project to fix the problem yourself. <br />
<br />
Learn more about [[Bugzilla_Configuration_and_Bug_Tracking|our process for reporting bugs]].<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=217Community Guidelines2010-10-26T18:32:04Z<p>Dawnfoster: added a few more links</p>
<hr />
<div>==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our [http://www.yoctoproject.org/tos Terms of Service[.<br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our [http://www.yoctoproject.org/community/discussions mailing lists]<br />
* Search the [http://www.yoctoproject.org/ Yocto Project website]<br />
<br />
==Wiki Guidelines==<br />
<br />
You can [http://www.yoctoproject.org/community/documentation learn more about our documentation] on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas on the Yocto Project website.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
[http://www.yoctoproject.org/community/discussions More information about our mailing lists] can be found on the Yocto Project website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
[http://www.yoctoproject.org/community/discussions More information about our IRC channels] can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
* '''Web access''': If you don't normally use IRC and want to try it out, you can use the [http://webchat.freenode.net/ freenode Web IRC] chat.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the [http://www.yoctoproject.org/community/bugs Yocto Bugzilla].<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
What to do if you find a bug<br />
* '''Search first''': Try to avoid filing duplicates by searching to see whether your issue has already been filed.<br />
* '''Ask''': You can ask on our mailing lists or IRC channels to see if anyone has seen this issue before to gather more details or see if someone has a workaround.<br />
* '''Submit a bug report''': Give us as many details as possible about what happened and how your issue can be reproduced.<br />
* '''Track our progress''': Get feedback from the development community and track resolution status.<br />
* '''Provide a fix''': Use the tools, project wiki and git source repository in the Yocto Project to fix the problem yourself. <br />
<br />
Learn more about [[Bugzilla_Configuration_and_Bug_Tracking|our process for reporting bugs]].<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=208Launch Plan October 20102010-10-26T18:03:24Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - Richard<br />
* Remove access control from the Drupal website - Richard<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - Dave<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dave</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=207Launch Plan October 20102010-10-26T17:20:46Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* <s>Publish BSP Guide on website - Mike</s><br />
* <s>Upload release notes - Dawn</s><br />
* <s>Add Google Analytics to Drupal - Mike</s><br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* <s>Get rid of unverified next to blog author & see if we can display name instead of userid - Mike</s><br />
* <s>Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike</s><br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=189Launch Plan October 20102010-10-26T16:20:00Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* Publish BSP Guide on website - Mike<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* Get rid of unverified next to blog author & see if we can display name instead of userid - Dawn<br />
* Need to figure out what to do about logging in to post comments - disable comments - Dawn / Mike<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=188Launch Plan October 20102010-10-26T16:18:35Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* Publish BSP Guide on website - Mike<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* Get rid of unverified next to blog author & see if we can display name instead of userid - Dawn<br />
* Need to figure out what to do about logging in to post comments - Dawn / Mike<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=187Launch Plan October 20102010-10-26T16:01:01Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* Publish BSP Guide on website - Mike<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* <s>Fix links to guides to open in a new window - Dawn</s><br />
* Minor wiki cleanup - Dawn<br />
* <s>Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn</s><br />
* Get rid of unverified next to blog author & see if we can display name instead of userid - Dawn<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=186Launch Plan October 20102010-10-26T15:56:59Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* <s>Get BSP Guide content finished - Scott</s><br />
* Publish BSP Guide on website - Mike<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
* Get rid of unverified next to blog author & see if we can display name instead of userid - Dawn<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=182Launch Plan October 20102010-10-26T14:37:13Z<p>Dawnfoster: /* Schedule for October 26 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
<br />
==Schedule for October 26==<br />
* 7am UK / 11pm Pacific (Oct 25) - Code goes live and open websites (no announcements).<br />
* ??am UK / xam Pacific - Press release published by the Linux Foundation.<br />
* 9am UK / 1am Pacific - Conference presentation from LF announcing Yocto<br />
* 9am UK / 1am Pacific - Announcements can go out.<br />
* Noon Pacific - Dirk's presentation.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=174Launch Plan October 20102010-10-26T14:15:51Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
<br />
==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control and redirection - Richard<br />
** Remove password protection from yoctoproject.org (sub)domains - Richard<br />
** Swap default site redirection and name for lists.* and wiki.* - Richard<br />
* Make meta-demo public - Richard<br />
* Remove password protection from autobuilder - Scott G.<br />
* Upload final version of the eclipse plugin - Jessica<br />
* Upload final Yocto release images and tarballs - ???<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=171Launch Plan October 20102010-10-26T14:10:16Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
<br />
==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Push code out - Richard<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
** Mailing lists<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=170Launch Plan October 20102010-10-26T14:05:40Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Upload release notes - Scott / Mike<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
<br />
==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Push code out - Richard<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=169Launch Plan October 20102010-10-26T14:03:59Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
<br />
==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Push code out - Richard<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=166Launch Plan October 20102010-10-26T14:00:49Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
* Confirm that I can remove this text from home page: "You’ve just landed on the Yocto Project home site." - Dawn<br />
<br />
==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=165Launch Plan October 20102010-10-26T13:57:07Z<p>Dawnfoster: </p>
<hr />
<div>==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn<br />
<br />
==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=164Launch Plan October 20102010-10-26T13:56:27Z<p>Dawnfoster: /* Pre-Launch To-Do List for Oct 25 */</p>
<hr />
<div>==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn<br />
<br />
==Pre-Launch To-Do List for Oct 25==<br />
* <s>Create checklist - Dawn</s><br />
* Add your to do items & make sure launch checklist is good - ALL<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=163Launch Plan October 20102010-10-26T13:54:02Z<p>Dawnfoster: /* Launch Checklist */</p>
<hr />
<div>==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already?<br />
<br />
'''8am Pacific'''<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn<br />
<br />
==Pre-Launch To-Do List for Oct 25==<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Launch_Plan_October_2010&diff=162Launch Plan October 20102010-10-26T13:53:21Z<p>Dawnfoster: Launch checklist</p>
<hr />
<div>==Schedule for October 26==<br />
* 8am Pacific - Code goes live and open websites (no announcements).<br />
* xxam Pacific - Press release published by the Linux Foundation.<br />
* Noon Pacific - Dirk's presentation.<br />
* Noon Pacific - Announcements can go out.<br />
<br />
==Launch Checklist==<br />
Do we have this already? Something like this:<br />
'''8am Pacific'''<br />
* Remove access control from the following sites - Richard<br />
** Yocto wiki<br />
* Remove access control from the Drupal website - Kip<br />
'''xxam Pacific'''<br />
* Publish press release - Amanda<br />
'''Noon Pacific'''<br />
* Rebrand bugzilla with Yocto logo - Richard<br />
* Post announcement to mailing lists - David<br />
* Post to LWN - Dirk<br />
* Post to Twitter account - Dawn<br />
<br />
==Pre-Launch To-Do List for Oct 25==<br />
* Finish any last minute content changes - Scott<br />
* Get BSP Guide content finished - Scott<br />
* Publish BSP Guide on website - Scott<br />
* Add Google Analytics to Drupal - Mike<br />
* Publish FAQ - Scott<br />
* Announcement blog post - Dave<br />
* Fix links to guides to open in a new window - Kip / Scott<br />
* Minor wiki cleanup - Dawn</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=96Community Guidelines2010-10-22T22:00:07Z<p>Dawnfoster: /* Bugzilla Guidelines */</p>
<hr />
<div>Note: <span style="background:#FFFF00">Highlighted</span> items require links to be added. Dawn will add links as those pages become available.<br />
<br />
==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our <span style="background:#FFFF00">Terms of Service</span><br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our <span style="background:#FFFF00">mailing lists</span><br />
* Search the <span style="background:#FFFF00">yoctoproject.com website</span><br />
<br />
==Wiki Guidelines==<br />
<br />
You can <span style="background:#FFFF00">learn more about our documentation</span> on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas of MeeGo.com.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our mailing lists</span> can be found on the Yocto website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our IRC channels</span> can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
* '''Web access''': If you don't normally use IRC and want to try it out, you can use the [http://webchat.freenode.net/ freenode Web IRC] chat.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the <span style="background:#FFFF00">Yocto Bugzilla</span>.<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
What to do if you find a bug<br />
* '''Search first''': Try to avoid filing duplicates by <span style="background:#FFFF00">searching</span> to see whether your issue has already been filed.<br />
* '''Ask''': You can ask on our mailing lists or IRC channels to see if anyone has seen this issue before to gather more details or see if someone has a workaround.<br />
* '''Submit a bug report''': Give us as many details as possible about what happened and how your issue can be reproduced.<br />
* '''Track our progress''': Get feedback from the development community and track resolution status.<br />
* '''Provide a fix''': Use the tools, project wiki and git source repository in the Yocto Project to fix the problem yourself. <br />
<br />
<span style="background:#FFFF00">Learn more about reporting bugs and our process for submitting patches</span>.<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=95Community Guidelines2010-10-22T21:59:43Z<p>Dawnfoster: /* Bugzilla Guidelines */ updated with introductory info about reporting bugs</p>
<hr />
<div>Note: <span style="background:#FFFF00">Highlighted</span> items require links to be added. Dawn will add links as those pages become available.<br />
<br />
==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our <span style="background:#FFFF00">Terms of Service</span><br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our <span style="background:#FFFF00">mailing lists</span><br />
* Search the <span style="background:#FFFF00">yoctoproject.com website</span><br />
<br />
==Wiki Guidelines==<br />
<br />
You can <span style="background:#FFFF00">learn more about our documentation</span> on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas of MeeGo.com.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our mailing lists</span> can be found on the Yocto website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our IRC channels</span> can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
* '''Web access''': If you don't normally use IRC and want to try it out, you can use the [http://webchat.freenode.net/ freenode Web IRC] chat.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the <span style="background:#FFFF00">Yocto Bugzilla</span>.<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
'''What to do if you find a bug'''<br />
* '''Search first''': Try to avoid filing duplicates by <span style="background:#FFFF00">searching</span> to see whether your issue has already been filed.<br />
* '''Ask''': You can ask on our mailing lists or IRC channels to see if anyone has seen this issue before to gather more details or see if someone has a workaround.<br />
* '''Submit a bug report''': Give us as many details as possible about what happened and how your issue can be reproduced.<br />
* '''Track our progress''': Get feedback from the development community and track resolution status.<br />
* '''Provide a fix''': Use the tools, project wiki and git source repository in the Yocto Project to fix the problem yourself. <br />
<br />
<span style="background:#FFFF00">Learn more about reporting bugs and our process for submitting patches</span>.<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=85Community Guidelines2010-10-22T20:44:54Z<p>Dawnfoster: /* IRC Guidelines */ added link to freenode webchat</p>
<hr />
<div>Note: <span style="background:#FFFF00">Highlighted</span> items require links to be added. Dawn will add links as those pages become available.<br />
<br />
==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our <span style="background:#FFFF00">Terms of Service</span><br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our <span style="background:#FFFF00">mailing lists</span><br />
* Search the <span style="background:#FFFF00">yoctoproject.com website</span><br />
<br />
==Wiki Guidelines==<br />
<br />
You can <span style="background:#FFFF00">learn more about our documentation</span> on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas of MeeGo.com.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our mailing lists</span> can be found on the Yocto website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our IRC channels</span> can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
* '''Web access''': If you don't normally use IRC and want to try it out, you can use the [http://webchat.freenode.net/ freenode Web IRC] chat.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the <span style="background:#FFFF00">Yocto Bugzilla</span>.<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Search first''': Try to avoid filing duplicates by <span style="background:#FFFF00">searching</span> to see whether your issue has already been filed.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Using_the_Wiki&diff=19Using the Wiki2010-10-21T21:46:10Z<p>Dawnfoster: /* Formatting */ typo</p>
<hr />
<div>A few basic instructions for how to use the Yocto wiki.<br />
<br />
==Creating a Page==<br />
<br />
Before creating a new page, you should first make sure that a page on your topic does not already exist:<br />
# In the search box in the upper right corner, enter your topic.<br />
# If the exact topic exists, the page will open.<br />
# If there are related pages, you will get a search results page. Check if your topic is in the results.<br />
# If your topic does not exist, choose '''create this page'''.<br />
<br />
==How to edit a page==<br />
<br />
If you'd like to change a page.<br />
<br />
# Make sure that you are logged in.<br />
# Click the '''Edit''' link.<br />
# Enter your changes in the box.<br />
# In the '''Summary''' box, enter a short explanation of what you did.<br />
# Click '''Show preview''' if you want to check your changes.<br />
# Click '''Save page'''.<br />
<br />
==Formatting==<br />
<br />
The Yocto uses MediaWiki formatting (the same as used on Wikipedia, for example). For simple formatting, use the buttons above the edit box. For more information see:<br />
<br />
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Cheatsheet]<br />
* [http://www.mediawiki.org/wiki/Help:Contents General MediaWiki user help]<br />
* [http://www.mediawiki.org/wiki/Manual:Contents MediaWiki manual]<br />
* [http://www.mediawiki.org/wiki/Extension:EmbedVideo Embedding Video]<br />
<br />
Credit: These instructions were based on the [http://wiki.meego.com/Wiki_contribution_guidelines MeeGo Wiki contribution guidelines] used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Using_the_Wiki&diff=18Using the Wiki2010-10-21T21:45:47Z<p>Dawnfoster: added credit link</p>
<hr />
<div>A few basic instructions for how to use the Yocto wiki.<br />
<br />
==Creating a Page==<br />
<br />
Before creating a new page, you should first make sure that a page on your topic does not already exist:<br />
# In the search box in the upper right corner, enter your topic.<br />
# If the exact topic exists, the page will open.<br />
# If there are related pages, you will get a search results page. Check if your topic is in the results.<br />
# If your topic does not exist, choose '''create this page'''.<br />
<br />
==How to edit a page==<br />
<br />
If you'd like to change a page.<br />
<br />
# Make sure that you are logged in.<br />
# Click the '''Edit''' link.<br />
# Enter your changes in the box.<br />
# In the '''Summary''' box, enter a short explanation of what you did.<br />
# Click '''Show preview''' if you want to check your changes.<br />
# Click '''Save page'''.<br />
<br />
==Formatting==<br />
<br />
The Yocto uses MediaWiki formatting (the same as used on Wikipedia, for example). For simple formatting, use the buttons above the edit box. For more information see:<br />
<br />
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Cheatsheet]<br />
* [http://www.mediawiki.org/wiki/Help:Contents General MediaWiki user help]<br />
* [http://www.mediawiki.org/wiki/Manual:Contents MediaWiki manual]<br />
* [http://www.mediawiki.org/wiki/Extension:EmbedVideo Embedding Video]<br />
<br />
Credits: These instructions were based on the [http://wiki.meego.com/Wiki_contribution_guidelines MeeGo Wiki contribution guidelines] used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=17Main Page2010-10-21T21:26:16Z<p>Dawnfoster: /* Welcome to the Yocto Project Wiki! */</p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
* [[Planning and Governance]]<br />
* [[Release Procedure]]<br />
* [[Community Guidelines]]</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Community_Guidelines&diff=16Community Guidelines2010-10-21T21:25:07Z<p>Dawnfoster: moved wiki instructions to a new page and minor edits, updates, format changes.</p>
<hr />
<div>Note: <span style="background:#FFFF00">Highlighted</span> items require links to be added. Dawn will add links as those pages become available.<br />
<br />
==Overview and General Guidlines==<br />
<br />
We want to keep the Yocto Community a great place to participate, but we need your help to keep it that way. While we have specific guidelines for various tools, in general, you should:<br />
<br />
* '''Be nice''': Be courteous and polite to fellow members of the list.<br />
* '''Respect other people''': No regional, racial, gender or other abuse will be tolerated.<br />
* '''Keep it clean''': Keep the language clean (no swearing)<br />
* '''Be helpful''': Be patient with new people and be willing to jump in to answer questions.<br />
* '''Stay calm''': The written word is always subject to interpretation, so give people the benefit of the doubt and try not to let emotions get out of control.<br />
* '''Keep it legal''': Make sure that you have the legal right to post your content and are not violating copyright or other laws.<br />
* '''Adhere to Terms of Service''': All community contributions are also subject to our <span style="background:#FFFF00">Terms of Service</span><br />
<br />
==Read Before Contributing - Search for existing answers==<br />
'''IMPORTANT: Before you contribute, be sure that you have done a thorough search to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.<br />
* Search this wiki<br />
* Search our <span style="background:#FFFF00">mailing lists</span><br />
* Search the <span style="background:#FFFF00">yoctoproject.com website</span><br />
<br />
==Wiki Guidelines==<br />
<br />
You can <span style="background:#FFFF00">learn more about our documentation</span> on the Yocto website, and if you are unfamiliar with MediaWiki syntax, we have a short how-to document with instructions for [[Using the Wiki]].<br />
<br />
Creating articles in the wiki is a collaborative process. After you have written your piece others may:<br />
* Edit<br />
* Alter<br />
* Adapt<br />
* Add<br />
<br />
So don't worry about making your article perfect the first time through. Don't hesitate to add content you think is useful and don't hesitate to make edits where you think you can help. There's always somebody to fix anything that breaks.<br />
<br />
<br />
'''Posting Guidelines'''<br />
<br />
Here are a few guidelines to keep in mind when using the Yocto wiki:<br />
* '''Search first''': Before creating a new page or making significant contributions to a page, please do a quick search to make sure that you aren't duplicating existing content on the wiki or other areas of MeeGo.com.<br />
* '''Contribute''': The wiki is a resource for anyone to use. Just keep the content relevant, that is anything related to Yocto as long as it meets our other guidelines should be appropriate.<br />
* '''Make improvements''': If you find a typo or inaccurate information, just fix it.<br />
* '''Respect links''': Please provide [http://www.mediawiki.org/wiki/Help:Redirects redirects] when you move content. Many people use the wiki and may have created bookmarks or linked to your content.<br />
<br />
'''The Wiki is Public'''<br />
<br />
Everything in the wiki is public.<br />
<br />
Every edit and every new page created goes into the [[Special:RecentChanges|recent changes]] feed, which means that people will see your edits even if you haven't yet linked to a page.<br />
<br />
Once it's out there, it's public. <br />
* Technically, administrators can delete things, but the wiki content may be mirrored, has feeds and is in the Google cache, so deleting something doesn't make it go away.<br />
* When you delete content from a page, the original content will still remain in the history for that page.<br />
<br />
==Mailing List Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our mailing lists</span> can be found on the Yocto website.<br />
<br />
'''Keep It Short'''<br />
<br />
Remember that thousands of copies of your message will exist in mailboxes:<br />
* Keep your messages as short as possible. <br />
* Avoid including log output (select only the most relevant lines, or place the log on a website or in a [http://pastebin.com/ pastebin] instead)<br />
* Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only). <br />
<br />
'''Use Proper Posting Style'''<br />
<br />
* '''No HTML or Rich Text''': Set your mailer to send only plain text messages to avoid getting caught in our spam filters.<br />
* '''Do not top post''': Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.<br />
* '''Using interleaved posting''': Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.<br />
* '''Use links''': Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.<br />
* '''Don't include attached files''': Instead of including attached files, please upload your file to the [[Special:Upload|this wiki]] or another website and post a link to the file from your email message.<br />
<br />
'''Do Not Hijack Threads'''<br />
<br />
Post new questions or new topics as new threads (new email message). Please do not reply to a random thread with a new question or start an unrelated topic of conversation in an existing thread. This creates confusion and makes it much less likely that you will get a response. <br />
<br />
'''Do Not Cross Post'''<br />
<br />
Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.<br />
<br />
'''Subscribers Only'''<br />
<br />
Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up. <br />
<br />
'''Additional Resources'''<br />
* [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf Mailing list guidelines by Shakthi Kannan (PDF)]: Great guideline summary and examples of posting styles.<br />
<br />
==IRC Guidelines==<br />
<br />
<span style="background:#FFFF00">More information about our IRC channels</span> can be found on the Yocto website.<br />
<br />
Here are a few IRC guidelines:<br />
* '''Don't post chunks''': Avoid posting big chunks of text - use [http://pastebin.com/ pastebin] or a similar service to shorten it to a link. <br />
* '''Register your Nickname''': To avoid confusion and make sure you always have the same name on IRC, you should [http://freenode.net/faq.shtml#userregistration register your nick].<br />
* '''Pick the right channel''': if you aren't sure, you should start in our main #yocto channel.<br />
* '''More information''': this [http://irchelp.org/irchelp/ircprimer.html IRC primer] for new users and the [http://freenode.net/channel_guidelines.shtml general IRC guidelines] from freenode are also useful resources.<br />
<br />
==Bugzilla Guidelines==<br />
<br />
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in the <span style="background:#FFFF00">Yocto Bugzilla</span>.<br />
<br />
* '''Be patient with others''': Sometimes people post imperfect bug reports. In case of missing information kindly tell reporters how to provide it, and/or suggest what they can do to improve the bug report.<br />
* '''Search first''': Try to avoid filing duplicates by <span style="background:#FFFF00">searching</span> to see whether your issue has already been filed.<br />
* '''Stay on topic''': Don't start endless debates on topics not directly related to the scope of a specific bug report.<br />
* '''Use proper quoting practices''': Avoid quoting complete previous comments by stripping unneeded lines, and avoid answering above the quoted text.<br />
<br />
==Guideline Violations - 3 Strikes Method==<br />
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who are making our community an unpleasant place.<br />
* First occurrence: Public reminder that the behavior is inappropriate according to our guidelines.<br />
* Second occurrence: Private message warning the user that any additional violations will result in removal from the community.<br />
* Third occurrence: Depending on the violation, may include account deletion or banning. <br />
<br />
'''Notes:'''<br />
* Obvious spammers are banned on first occurrence. This is necessary to keep the community free of spam.<br />
* Violations are forgiven after 6 months of good behavior.<br />
* Minor formatting / style infractions will be dealt with through education, not the 3 strikes process.<br />
* Extreme violations of a threatening, abusive, destructive or illegal nature will be addressed immediately and are not subject to 3 strikes.<br />
* Contact [[User:Dawnfoster|Dawn Foster]] to report abuse or appeal violations (mistakes happen & will be corrected).<br />
<br />
==Credits==<br />
* [http://wiki.meego.com/Community_guidelines MeeGo Community Guidelines] were the basis for the Yocto Guidelines used under the [http://creativecommons.org/licenses/by/3.0/legalcode Creative Commons Attribution 3.0 License]<br />
* [http://fedoraproject.org/wiki/Communicate/MailingListGuidelines Fedora Mailing List Guidelines] used as a starting point under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 Unported] license.</div>Dawnfosterhttps://wiki.yoctoproject.org/wiki/index.php?title=Using_the_Wiki&diff=15Using the Wiki2010-10-21T21:21:30Z<p>Dawnfoster: Created page - removing it from guidelines</p>
<hr />
<div>A few basic instructions for how to use the Yocto wiki.<br />
<br />
==Creating a Page==<br />
<br />
Before creating a new page, you should first make sure that a page on your topic does not already exist:<br />
# In the search box in the upper right corner, enter your topic.<br />
# If the exact topic exists, the page will open.<br />
# If there are related pages, you will get a search results page. Check if your topic is in the results.<br />
# If your topic does not exist, choose '''create this page'''.<br />
<br />
==How to edit a page==<br />
<br />
If you'd like to change a page.<br />
<br />
# Make sure that you are logged in.<br />
# Click the '''Edit''' link.<br />
# Enter your changes in the box.<br />
# In the '''Summary''' box, enter a short explanation of what you did.<br />
# Click '''Show preview''' if you want to check your changes.<br />
# Click '''Save page'''.<br />
<br />
==Formatting==<br />
<br />
The Yocto uses MediaWiki formatting (the same as used on Wikipedia, for example). For simple formatting, use the buttons above the edit box. For more information see:<br />
<br />
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Cheatsheet]<br />
* [http://www.mediawiki.org/wiki/Help:Contents General MediaWiki user help]<br />
* [http://www.mediawiki.org/wiki/Manual:Contents MediaWiki manual]<br />
* [http://www.mediawiki.org/wiki/Extension:EmbedVideo Embedding Video]</div>Dawnfoster