Add welcome information for new developers #30
Assignees
Labels
enhancement
New feature or request
Comments
|
@DGajewska has suggested they are interested in putting an initial thing together. So I and @bensagar-ea have happily volunteered to work with them on getting something initially proposed. Feel free to log initial suggestions and ideas here though. |
|
@Cruikshanks Mandy actually asked me to get one of these together a while ago, so I've been working on a draft myself! I can add it here if you'd like? |
|
@irisfaraway yes please! It would be really good to see what you've got and not let your hard work go to waste :) |
irisfaraway
added a commit
that referenced
this issue
Jan 16, 2020
This was raised in #30 - luckily I was asked to get one of these together a while ago, and have been working on it in the background! But this repo does seem like a natural home for it. The guide is mostly about getting access to various tools, sharing links to various standards, and encouraging people to get on Slack and come to meetups.
|
I think some kind of info pack would be really helpful. |
irisfaraway
added a commit
that referenced
this issue
Mar 16, 2020
This was raised in #30 - luckily I was asked to get one of these together a while ago, and have been working on it in the background! But this repo does seem like a natural home for it. The guide is mostly about getting access to various tools, sharing links to various standards, and encouraging people to get on Slack and come to meetups.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a common discussion point, not just amongst new starters, about where to go to find stuff. Hot on the tails of this is
Surely the home for such a thing is here? So this issue is about adding content to this project specifically targetted for new users (and perhaps to re-acquaint those of us a bit longer in the tooth).
Even if it's just a list of links to other contents, it will at least highlight and bring together the key things we think people need to know to get cracking in their role as a developer in Defra.
The text was updated successfully, but these errors were encountered: