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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Written guidance on how to make a job on OSD successful #393

Open
Erioldoesdesign opened this issue Aug 4, 2022 · 11 comments
Open

Written guidance on how to make a job on OSD successful #393

Erioldoesdesign opened this issue Aug 4, 2022 · 11 comments
Assignees
Labels
content Writing and/or design of content Documentation Documentation and updates for open source design repos good first issue Small tasks with clear documentation about how and in which place you need to fix things in.

Comments

@Erioldoesdesign
Copy link
Member

We don't have guidance docs about how a job poster can make their job successful.

Let's start a thread here on how to write an article - which could then be used in comms related to posting a job about how to make the post successful.

Ideas:

  • Add a hello and contact info to your forum post when a job is approved
  • Check the forum post at least once per month/when able to
  • Answer questions for the designers, typical questions include etc....
@Erioldoesdesign Erioldoesdesign added content Writing and/or design of content good first issue Small tasks with clear documentation about how and in which place you need to fix things in. Documentation Documentation and updates for open source design repos labels Aug 4, 2022
@Dibyajyoti2002
Copy link

Hi , I was thinking about working on this issue , but before doing that , I just wanted to clarify something . Should the person working on this issue provide a documented approach and some tips on how to make a job post successful?

@jdittrich
Copy link
Member

…working on this issue provide a documented approach and some tips on how to make a job post successful?

Yes!

@Erioldoesdesign mentioned a few best practices, and I think it would also be good to provide a faux job example and why it is good. (Clear task, goals for the task, target group defined, contact person clear…)

Maybe start on an etherpad or gdoc or the like, in case you want to get quick feedback?

@Erioldoesdesign
Copy link
Member Author

Hi , I was thinking about working on this issue , but before doing that , I just wanted to clarify something . Should the person working on this issue provide a documented approach and some tips on how to make a job post successful?

Agreed with @jdittrich sounds like a perfect way to start a doc with some mock examples and the rest of the OSD community can help out by reviewing :)

@subz3r0o0
Copy link

hi, if this issue is still open i would love to contribute

@Erioldoesdesign
Copy link
Member Author

hi, if this issue is still open i would love to contribute

Go for it this is a open issue that will serve as the basis for a document that can be openly collaborated on

@subz3r0o0
Copy link

is this along the lines of what youre looking for? https://docs.google.com/document/d/1TvMIyV4AMG2y5y7Yy9WvdrgxEUEuA7366FZzaWIpz0c/edit?usp=sharing - and could i make any pull requests to push this into any repos?

@subz3r0o0
Copy link

is this ok, i sent an email also
:))

@Erioldoesdesign
Copy link
Member Author

@subz3r0o0 can you give me access to your google document please - I sent a request for access via my email accounts or you can open up the document for public viewing so I can take a read and make any suggestion :)

@subz3r0o0
Copy link

Hi, I changed the access rights - is it ok now?
Thanks

@subz3r0o0
Copy link

subz3r0o0 commented Apr 24, 2024

After finalising the writing, I plan to move it to a Canva document for aesthetic purposes. Does it have to be uploaded as a markdown file?

@Erioldoesdesign
Copy link
Member Author

@subz3r0o0 Amazing work - i'm blown away at how detailed and thoughtful your work on this issue is 👏 🚀

I've added some extra examples and edited some words - feel free to accept or reject those in the google document as you see fit :) (I will not be upset if you don't like my writing 😄 )

I would recommend this be added both as a .md file in the jobs repository and also an article on the website: https://opensourcedesign.net/articles/

I would also think it would be great to add as a forum post. If you want to make a visually exciting version in Canva do go ahead and we can upload the open doc files or .pdf to the repo for people to see but also embed in the article page :)))))))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Writing and/or design of content Documentation Documentation and updates for open source design repos good first issue Small tasks with clear documentation about how and in which place you need to fix things in.
Development

No branches or pull requests

4 participants