From Fedora Project Wiki

(Created page with '{|border="1" |-style="color: white; background-color: #3074c2; font-weight: bold" | DATE || TIME || WHERE |- | 2009-09-08 || From ''12:00'' to ''21:00'' UTC (8am -> 5pm EDT) || ...')
 
Line 44: Line 44:


Here are some things to look at:
Here are some things to look at:
*  
* [[QA:Testcase_Sharing_Simple_Filesharing| Simple file sharing]]
 


=== Issues that were identified ===
=== Issues that were identified ===

Revision as of 18:27, 3 September 2009

DATE TIME WHERE
2009-09-08 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-fit-and-finish)


What to test?

The topic of this Fedora Test Day will be sharing of various things over the network. This includes files, and music, but also remote desktop functionality.

Who's available

The following people have agreed to be available for testing, workarounds, bug fixes, and general discussion: Matthias Clasen, Bastien Nocera, Tomas Bzatek, Lennart Poettering.


Prerequisites for Test Day

  • Two computers, connect by a network
  • A good mood. Remember; while we are poking into things that may make us angry or frustrated, we are doing it to make things better
  • An up-to-date rawhide installation. See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. If that feels too risky to you, we also have recent rawhide live images available that allow you to participate without risking your existing installation. Tips on using a live image are available at FedoraLiveCD.
Architecture SHA1SUM Size
i686
x86_64

Finally, if you don't have a rawhide installation and don't want to download an iso, your input will still be valuable if it is based on F11.

How to test

Sharing and discovery of shared resources in local networks often uses mDNS as provided by the avahi package. Unfortunately, the default firewall configuration does not allow this to work, so you will have to turn off the firewall using system-config-firewall or simply by running

/sbin/service iptables off

for most of these tests.

Here are some things to look at:

Issues that were identified

Tester Description Bug references Status

Things that work alright

Tester Description