Another approach is to use Terminal (a.k.a shell or command prompt) to create/edit (must be performed as super-user, see sudo) the file:
adding the line:
save and reboot. New files/folders (including files changed by save as) will allow everyone read/write.
This works by changing the default file creation permissions for programs, whereas the ACL approach works in terms of access rules bound to particular files and folders.
Without this tweak, files are created allowing user: read-write, group & other: read-only.
If you are sharing between multiple computers, you need to do this for all computers that will use the share.
If you have existing files and folder in the shared area, you need to make them all readable/writable by everyone using:
sudo chmod -R og+w <shared-folder-name>
The command reads in English as change mode, recursive through all sub folders and files, other & group permissions add write access, starting at folder with .
This approach is mentioned in forums to work with at least as early as 10.6 and still works on 10.7.
Other factors still affect access to content. For example, permissions set in the Sharing control panel, home folder permissions/ACLs, and when using Terminal any umask in effect for the shell.
Look up umask and Posix file permissions for details on these Unix concepts. In the write ups, the word directory is Unix parlance synonymous with folder. You will also encounter the terms UID and GID: user and group IDs, which define the Posix ownership of running programs (processes). Note that UIDs and GIDs are numbers which may be the same or different for a given user name across different computers. These numbers are assigned to names in the order accounts are created on a given computer, typically starting with ID 501. Home networks lack a mechanism to harmonize these assignments across computers. Therefore on network shares a file may appear to belong to different users because the user ID to user name binding is determined from the perspective of computer is accessing the file. So shares really always allows everyone to access files to various degrees of everyone. In other words, the Posix "other" permission is an indefinite limit on access ranging from allowing a quite predictable but apparently uncertain degree of access depending on the user IDs assigned on different computers. This leads to apparently absurd variations in experiences, where on some networks, for example a setup with only one user account ever created on each Mac, will be able to share without any permissions tweaks because all accounts will have the same UID (501, no matter what the accounts are named) whereas another network using multiple user accounts per Mac will see problems right away. So some groups will never struggle with this, whereas some others may see problems that develop over time, or problems which appear/disappear spontaneously, depending on when/how additional user accounts are created/used with the shared folder.
It's a mystery why Apple has left such a festering usability defect in the configuration of such an otherwise easy to enable file sharing capability.
On external disks, this problem is addressed with the "Ignore permissions on this volume" option. There may be a similar feature for apple file sharing, but where is it.
If you roll you own Samba service config there are other mechanisms for handling these problems, but Samba is not at all easy to use.