Good Afternoon,

We've been working through updating the various guidelines, and we're ready to get general feedback and questions on the updated job guidelines.

Feedback can either be provided through this form, via my Discord or GmodStore messages, or as a reply to this thread. If there are questions I'll post them and their answers in the index below. I'll also provide a list of changes, should we get feedback that requires changes to the draft.

We will be recieving comments for the next 2 weeks, ending on the 31st of October, after which point, we'll be making any final required changes, and implementing; expect a follow up announcement when this policy goes into effect.

Moving on, the draft:

Job Guidelines

In this section, we provide some guidelines and information about posting jobs, and the applications / hiring process.

Overall, we need to be clear that the jobs section is not a listings area, but instead has integration across the lifespan of a job, from applicants, acceptance, negotiations and review. Some of these guidelines may seem arbitrary or archaic, however, it allows these features to be utilised.

Job Listings

1. Your primary listing description must be in English.
2. You may also provide your listing description in other languages, however, the listing’s primary language must be English.
3. Jobs on this site should be relevant to Garry's Mod, or a Garry's Mod community.
4. ie. Making models, coding addons, developing websites for a Garry's Mod community would all be fine, a design studio site would not.
5. Do not post listings seeking multiple applicants.
6. One listing must be aimed at, and only accept, one applicant.
7. Many of the job listing tools only work with a single accepted applicant.
8. Be specific.
9. Don't say things like "I need a script" or "make me a map", explain in detail exactly what you're expecting from the person you're hiring.
10. Listings which will negotiate off-platform must state as such.
11. Applicants shouldn’t be surprised if they need to contact you off-platform to clarify and confirm terms with you.
12. Listings which negotiate off-platform must have the outcome of negotiations stored.
13. If you negotiate specific conditions for work, clarify milestones, or otherwise agree on conditions externally, take a screenshot / video of the outcome of those negotiations, and both parties agreeing to them.
14. Do not post a job seeking "staff for your community".
15. If you have a specific job you are hiring, that's fine, but be specific and it should be just for 1 applicant. Don't post jobs where you're trying to fill multiple "roles", even if they are paid.
16. Do not post jobs requesting an applicant to fill a role.
17. Jobs must have specific and measurable criteria for completion.
18. In simple terms, hire people to do something, not be something.
19. Do not post a job with a frivolous budget.
20. You are welcome to ask in our Discord or on our forum for price guidance, but using common sense gets you far in pricing your job.
21. Do not post jobs for rep farming.
22. This means if you discuss a job via Steam, do not post it here solely to get a +rep.
23. Discussing jobs with people and making agreements prior to posting is fine, however we'd recommend against posting jobs for pre-agreed work with developers you've worked with before
24. Do not post jobs regarding leaked content (PERP, SantosRP, Etc) or a content you don't have permission to edit (e.g. decompile a map while you are not allowed to)
25. Do not post jobs regarding offensive topics.
26. For example no jobs asking for Nazi content.
27. Do not create posts for the primary purpose of advertising your server / community.
28. If your job listing is to configure a gamemode (DarkRP jobs / shipments, setup, etc), the specifications must be clearly listed and enumerated.

Accepting Applicants

Once you’ve got applicants, you should do some things prior to accepting an applicant:

1. Do some basic research into the people you're hiring.
2. Check their reputation.
3. Check their steam account.
4. Check things they have created in the past.
5. Check the background of those you’re hiring and giving access to.
6. Some people pretending to be developers may want to gain access to your server to steal your content, licences or backdoor your server. 
7. If that happens, you will initially be held responsible for the license breaches.
8. Overall, be careful who you give access to.
9. Be a good customer.
10. Being aggressive, constantly changing requirements or attempting to withhold payments will likely result in you getting a negative rating, or may result in you being barred from creating jobs.
11. Pay as soon as the person you hired completed their work.

Applications

If you want to do private work for someone, you can browse through the job listings!

In this section, we provide some guidelines and information about posting applications. Failing to follow these could lead to your account reputation being lowered, or even being sanctioned.

1. Your application must be in English.
2. You may also provide your application in other languages, however, the application’s primary language must be English.
3. Don't apply for jobs just to gain access to servers to steal their licenses, backdoor or other such activity..
4. You may negotiate terms prior to starting work, but you should avoid re-negotiation afterwards.
5. You should allow the client to review your work, but you should also avoid being taken advantage of:
6. For maps or models, you can screen-share, provide screen-shots or videos for the person you're working for.
7. You shouldn't use a server to allow a client to play on a map, as they would be able to download and decompile the map from the server.
8. For GLua scripts, starting a P2P server or a dev server allows the client to test your work without handing over the code.