Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Establish By-lines and conduct for Job Board use #56

Open
bnvk opened this issue Feb 28, 2017 · 1 comment
Open

Establish By-lines and conduct for Job Board use #56

bnvk opened this issue Feb 28, 2017 · 1 comment

Comments

@bnvk
Copy link
Member

bnvk commented Feb 28, 2017

The job board is seeing an increasing number of postings. Hooray 馃榿 Considering, some jobs are for gratis, while some involve money, as that confusion such as the Apache Camel logo can occur, I think it's important for us as a community to establish how we want the Job Board to be used and engaged with as it matures.

Some starting points:

  • How to handle cases (like Apache camel) where organization vs. individuals post
  • What is proper and desired methods for OSD designers to apply and engaging with job poster
  • What is the right balance of fairness for applying / accepting gigs repeatedly
  • What aspects of negotiating / accepting gigs should happen on OSD job board vs. privately
@elioqoshi
Copy link
Member

Definitelly want to help shape this as well. This needs quite a bit of work and discussion so I'm going to give this some proper thought a bit later.

I want to add that we should try to cater to most posters, as we might lose credibility if a lot of jobs are posted and most of them are not followed up. However, on the other hand, that is sometimes not so surprising, as most jobs are gratis, and no matter how much we want to help, we gotta pay bills. I tend to do 2 pro-bono gigs for every paid gig I do, but I think that a minimum financial incentive helps quite a lot to spark interest. I have seen especially a rise in the number of Web Design related jobs, where we lack contributions to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants