I was trying to show someone a dev forum post for a position I had open but they couldn’t open the link because they weren’t part of the forums. I think everyone should be able to see (but not post) into Collaboration.
8 Likes
I’m mixed when it comes to this.
I support, because members who aren’t in the developer forum could see it, but on the other hand, you could get flooded with requests by non-devforum members, some of which have never opened studio in their lives.
4 Likes
I think your use case here is quite slim, if you want to do it like that, it’s probably better to allow for people to put them in #bulletin-board so that they are shareable. I for one know that if everyone could see those posts, as @Starception said, I would get flooded with inexperienced and time wasting applicants. Perhaps allow new members to see it but not post?
Hey guys!
We like this suggestion. We like the idea of developers being able to advertise their open positions to non-members and New Members.
To add some further context, non-members of the Developer Forum cannot send private messages.
With that said, we want to gauge interest in this idea. Please vote below if you have an opinion in this matter:
Should the Collaboration category be visible to non-members?
- Make Collaboration visible to non-members
- Keep Collaboration invisible to non-members
0 voters
4 Likes
We want the best people to see this, not just the members. Let them see! It does us no harm.
Edit: By making it easier for them to get work with devs, they’re able to prove themselves much more easily and will help us remove the glass ceiling to join the dev community.
2 Likes
portfolios should be visible, collaboration threads should not be. especially with dev groups putting out applications, it could cause a lot of fluff to come in
18 Likes
Most people post a discord account anyway. This can get more people engaged!
1 Like
Yeah I see no harm in letting everyone see job roles that are available
I would prefer a public subforum and private one. There are some projects I could see wanting to be public, and others not.
24 Likes
I’m willing to give it a shot. Perhaps they could be limited to link-only cases, so that way they can’t freely browse (and become potential bothers if people are looking for another forum member to help), and so in cases like OP’s, they can see the details they need.
I think it would make details on games, which people are looking for help with, will become even more vague than they are already, as will give away even ore surprises to a wider audience… quite concerning imo.
Accidentally voted visible but I meant invisible woops.
I think that there should be a public version of collaboration, and a private version. Some projects I believe only members should hear/know about to apply.
2 Likes
I’d love to see an influx of more people seeing my collaboration threads, so yeah it would be a fun thing to have! Maybe a public and a private section
2 Likes
I don’t think there is any glass ceiling at all, if you have good games, and you know what you’re doing, even to a small degree you will get accepted into the devforums if you apply and if you don’t due to attitude etc, then do we really want people like that applying for our game positions anyway?
More importantly, when I put something up in #collaboration I am reassured by the fact that if the person who applies ends up scamming me or doing something wrong, I can contact devrel and have them removed from the forums. Also, it’s a sign that they are a community member of good standing, and that they, to a certain degree, know what they’re doing.
7 Likes
If collaboration is Members only I know that the person has passed some form of moderation. It’s the only reason I come to the DevForum when finding people to hire.
It used to be that only great people were allowed in. At least let us keep the minimum qualifications 
2 Likes
I think that opens up alot of opportunities for non members to find work.
1 Like
Portfolios should be made publicly visible while recruitment should be split into public and private categories.
1 Like
I don’t see any harm in letting everyone view collaboration, it’s not like it’s impacting who you choose out of all the candidates who apply to work with you.
I can definitely see the pros and cons of this.
-
Not all developers are a part of the developer forum, and I feel it would be fair in that sense to give them the same opportunity for work. The membership of the forum isn’t an automatic sign you’re a “better developer” than someone who isn’t.
-
However as others have mentioned, there’s the problem with not knowing the moderation history of the individual, and not knowing if they participate in scams. Again though, this should be at the discretion of the developer choosing who to collaborate with (it’s fairly easy to tell who’s legit and who’s not by looking at their previous work).
Portfolios should definitely be made open for public viewing, and I have mixed feelings about collaboration offers but I am leaning towards the idea of making it open to view. I feel the benefits definitely outweigh the risks.
1 Like