Entry tags:
Some changes to how we're using this community
As well as the addition of ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_docs_training that ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
ivorygates has already mentioned, we're also going to be making a few changes to how we're running dw_docs itself.
First off, we're going to be moderating entries on this community. As I write this, there are 576 members here, and we're taking this step now to keep the number of entries here manageable and make sure that everything stays on topic. We want for this to be a community that anyone interested in documentation can read without being snowed under with the volume of entries.
Things that will be on topic here:
Notable things that won't be on topic:
We're not going to switch over to being a moderated community for a couple of days yet at least. We want to give you all time to spot anything we might have missed before we do this. I'll also add that we're still going to be keeping open membership here, and we won't be screening comments. It will only be top-level entries that we'll be moderating.
As I mentioned above, we're not going to be taking suggestions for improvements in entries to this community any more. Instead, we'll be posting a "suggestions box" entry every month, and then having people comment there with their suggestions and feedback. We'll also keep a link to the current suggestions box thread in our profile. This way, people who are interested will be able to track comments on the entry, but people who aren't interested will be able to stay subscribed to the community without having to sit through all the suggestions posts.
We'll be going through the suggestions as they come in, and then migrating them over to a master list of Things That Need To Be Done which our hard working doc team (and doc trainees!) will be able to work off without having to track around the community looking for what's already been dealt with and what hasn't.
Again, we'll be waiting at least a couple of days before we implement this, so we can make any changes we need to based on your feedback.
dw_docs_training that ivorygates has already mentioned, we're also going to be making a few changes to how we're running dw_docs itself.First off, we're going to be moderating entries on this community. As I write this, there are 576 members here, and we're taking this step now to keep the number of entries here manageable and make sure that everything stays on topic. We want for this to be a community that anyone interested in documentation can read without being snowed under with the volume of entries.
Things that will be on topic here:
- Any announcements ivorygates and I make (for example, "we need volunteers for this project!").
- Summaries of which FAQs we've changed recently.
- Discussion of broad-stroke documentation issues (for instance, "how do we best handle accessibility in our FAQs?").
- People from other Dreamwidth projects keeping us informed of things that will be relevant to documentation (for example, "hey, we're going to be adding this big new feature soon so you might want to start documenting it now".
Notable things that won't be on topic:
- Suggestions for things that need adding or changing (see below for how we're going to be handling these.
- General Dreamwidth suggestions, which belong in dw_suggestions.
- The actual process of writing things or questions about this, which will be going in dw_docs_training.
We're not going to switch over to being a moderated community for a couple of days yet at least. We want to give you all time to spot anything we might have missed before we do this. I'll also add that we're still going to be keeping open membership here, and we won't be screening comments. It will only be top-level entries that we'll be moderating.
As I mentioned above, we're not going to be taking suggestions for improvements in entries to this community any more. Instead, we'll be posting a "suggestions box" entry every month, and then having people comment there with their suggestions and feedback. We'll also keep a link to the current suggestions box thread in our profile. This way, people who are interested will be able to track comments on the entry, but people who aren't interested will be able to stay subscribed to the community without having to sit through all the suggestions posts.
We'll be going through the suggestions as they come in, and then migrating them over to a master list of Things That Need To Be Done which our hard working doc team (and doc trainees!) will be able to work off without having to track around the community looking for what's already been dealt with and what hasn't.
Again, we'll be waiting at least a couple of days before we implement this, so we can make any changes we need to based on your feedback.
no subject
The other question I have is, what needs documenting at this stage? I know there's a bunch of styles related stuff, but that's being handled mainly by
Things I'm happy to volunteer for:
- occasionally going through the FAQs and making sure everything is tidy and accurate and in the right categories
- trying to gather together information which is scattered all over comments to official posts and the Wiki and Support request ICs and actually make it into documentation
- writing new docs, eg the Guides that we said we'd do and didn't quite get finished by Open Beta
- training newbies, if you haven't already got that covered
Or do you have a better idea?no subject
And sure, doing drafts of the missing Guides would be great.