Assignments I like having a request assigned to me as opposed to picking one for myself - it seems to work better that way as it's actually a challenge that requires thinking and planning, and contributes to the quality of the fic. It is complicated for you, I know, but overall I think it is the better way to organise things, when compared to a publicly random method, or asking authors to select from requests. It also doesn't rely on authors all being online at the same/similar time, and so someone who only has weekly access or something won't hold up the queue or be stuck with a request they can't write.
Participation I suspect that adding barriers to registration may discourage new participants, and might get you a reputation as 'elitist'. What might work is having a group of proven authors on standby, and if someone defaults and doesn't request an extension, requests get automatically passed on to someone in that group, rather than chasing the author for a progress report. It would mean having a diverse group of authors, so that all the requests could be covered - not everyone is willing to try out a new character on short notice.
Forum A Yahoo!Group would need to be active all year round and/or monitored in case of spam - I've been noticing that after a couple of months of inactivity in ones I am/was a part of, the spambots seem to appear. I like the idea of having it all on the site, but again, it's a lot of work for you. vo_xmas runs on LJ but the fics are submitted to the moderator lennongirl and are posted by her, and then the author's identities revealed a week later. That could work, and you could set up a moderating account to post from so that two or three people could do the posting. The coding is simpler that way, and it's all still in the one place. Self-loading again means that everyone has to be online around a certain time, or people might have to wait for their fics. Around Christmas it usually gets harder to get everyone online, as well. Another thing I thought of is that LJ and it's comment system generally makes it easier for a reader to leave a comment/feedback, and means that author's email addresses don't have to be posted with the fic, as they can track the entry or visit regularly to read their feedback.
Content Story length and restrictions are fine the way they are, I think, but requests could be done in a different format - perhaps separating the "what i will/will not read" from the "what i will/will not write" to make the differences clearer for the person who is assigned that request, or asking the requester to specify three words the fic needs to be based around, or a scenario, or a theme. I don't think adding RPS will help much - there are many many RPS exchanges around, both general and pairing-specific, and because RPS seems to attract more people the exchange may well end up too large to handle. Perhaps adding art as a possibility might work, although there would possibly be an imbalance of people asking for/requesting art.
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2007-02-01 09:04 pm (UTC)Assignments
I like having a request assigned to me as opposed to picking one for myself - it seems to work better that way as it's actually a challenge that requires thinking and planning, and contributes to the quality of the fic. It is complicated for you, I know, but overall I think it is the better way to organise things, when compared to a publicly random method, or asking authors to select from requests. It also doesn't rely on authors all being online at the same/similar time, and so someone who only has weekly access or something won't hold up the queue or be stuck with a request they can't write.
Participation
I suspect that adding barriers to registration may discourage new participants, and might get you a reputation as 'elitist'.
What might work is having a group of proven authors on standby, and if someone defaults and doesn't request an extension, requests get automatically passed on to someone in that group, rather than chasing the author for a progress report. It would mean having a diverse group of authors, so that all the requests could be covered - not everyone is willing to try out a new character on short notice.
Forum
A Yahoo!Group would need to be active all year round and/or monitored in case of spam - I've been noticing that after a couple of months of inactivity in ones I am/was a part of, the spambots seem to appear. I like the idea of having it all on the site, but again, it's a lot of work for you.
Another thing I thought of is that LJ and it's comment system generally makes it easier for a reader to leave a comment/feedback, and means that author's email addresses don't have to be posted with the fic, as they can track the entry or visit regularly to read their feedback.
Content
Story length and restrictions are fine the way they are, I think, but requests could be done in a different format - perhaps separating the "what i will/will not read" from the "what i will/will not write" to make the differences clearer for the person who is assigned that request, or asking the requester to specify three words the fic needs to be based around, or a scenario, or a theme.
I don't think adding RPS will help much - there are many many RPS exchanges around, both general and pairing-specific, and because RPS seems to attract more people the exchange may well end up too large to handle. Perhaps adding art as a possibility might work, although there would possibly be an imbalance of people asking for/requesting art.