Q1: I am looking for the project "Sandbox", where is it?
A1: The place to go to is https://forge.roe.ac.uk/trac/Sandbox. There you will find the wiki for the project. You can also go to https://forge.roe.ac.uk/trac, it lists all the projects.
Q2: I've found the wiki for the project I'm interested in, but it says "BROWSER_VIEW privileges are required to perform this operation"!?
A2: That seems to be a project that allows only certain named users read access. You should fill in the NewUserForm and e-mail your user application as instructed in the form. You should also contact the people who run the project so that they can give your user account access to the project.
Q3: Never mind the wiki, I want to raise a bug report!?
A3: The wiki includes the ticketing system where bugs and issues are tracked. "Read access" (or "user access") includes the ability to create and add to tickets. On some projects this is possible anonymously, on others you may need a user account (see the NewUserForm to apply for one) and that account then needs to be given "user access" to the project.
Q4: Actually, there are no bugs, I would like to look at the source code!?
A4: The wiki includes a "source browser", which shows you the contents of the project's repository of "source files". It is quite a good browser, you can see how files and directories have been changed over time, and you can see the old versions (they are called revisions), too.
Q5: I can read the wiki, but I can't edit the pages in it!?
A5: This is what we call "developer access". All projects restrict write access to developers on the project. To be a developer you need a user account and that user account has to be in the developer group of the project.
Q6: What is "user access" and what is "developer access"? And what is a user account anyway?
A6: The access rules for each project are different. Each project has a bunch of developers, these are user accounts with write access to the project. Each project also gives read access, either anonymously or to a bunch of named user accounts. Read access includes creating and adding to tickets. To read a project that grants anonymous read access you don't need a user account. To read other projects you need (i) a user account so you can tell them who you are, and (ii) your user account needs to be in the user group of the project. To write within a project you need a user account and your user account needs to be in the developer group of the project.
Q7: Can I be a user and a developer on a project?
A7: A developer is given more access than a "mere user". If you are a developer already, you have all the access a mere user has and more. So if your user account is in the developer group of a project, it should not be explicitly in the user group of the same project.
Q8: Can I be a user on one project and developer on another?
A8: Yes. Each project maintains its own list of developers and users.
Q9: Can I use one user account on one project and another user account (a different user name) on another project?
A9: No. Your web browser asks you only once who you are. You can then log into any project without being prompted for your user name and password. If you really have access to different user accounts, you have to restart your web browser to use a different account. That is possible, but the idea is that one person has one user account and one user account is used by one person only.
Q10: I want to fix the source code. I suppose I have to be a developer of the project for that?
Q11: I want to download quite a few source files, and an old revision of them. Surely there must be a better way than to view each file through the wiki's source browser?
A11: Yes there is. The repository is a Subversion (SVN, svn) repository. You install an svn client on your work station, and you use that to checkout (download) the files.
Q12: Ah, ok. I've read the SVN book. What do I tell my svn client where the repository is?
A12: Given a project name like "Sandbox", the svn repository is at https://forge.roe.ac.uk/svn/Sandbox. You cannot view https://forge.roe.ac.uk/svn to see what repositories there are.
Q13: Actually, I haven't read the SVN book. Is it any good?
A13: Yes, very good. And on-line. Go to http://svnbook.red-bean.com. It has the book for various versions, including Subversion 1.4.2, which runs on this server.