You may recall that at the end of last year, I was interested in creating a Ravelry-equivalent for handweavers. I had thought about it, checked out a couple of content management systems, and in general was pretty gung-ho about it, except for one thing: I was NOT willing to maintain and administer it long-term. A six month commitment to build out a community website is one thing, but spending the rest of my life settling bulletin-board squabbles, managing users, etc. was not something I wanted to do – would take too much time away from weaving, cycling, and my other interests! So I let it be.
This morning, out of the blue, I got an email from Syne Mitchell, editor of WeaveZine. A woman named Claudia had emailed her about the possibility of setting up a weaving Ravelry, and was I still working on the project? I said no, it was back-burnered, but if someone was willing to do the administration and manage it long-term, I would love to set it up.
So Claudia and I have been corresponding and it seems likely that I will be working on creating a Ravelry-equivalent for weavers fairly soon, like within the next few months. Which will be good for me since it will give me experience in creating social networking/community sites and dealing with content management systems like Drupal, both of which are hot stuff on a resume. Also it will allow me to contribute something back to the handweaving community, which has been extremely supportive and helpful to me as a weaving novice.
This is going to be a huge project, so I need to clear the decks first. Which means moving forward as soon as possible with my “redo the website” project. Fortunately I have found someone to help me migrate the website, so as soon as my job situation stabilizes (hopefully in the next day or two) I can have her start work. Equally fortunately, I can parallel process this with my doubleweave studies – I wouldn’t want to give those up!
If you know of anyone else who might be interested in helping found a Ravelry equivalent for weavers, please let me know. I’m particularly interested in anyone with a technical background and/or experience with Drupal, but I’ll need help with beta testers and other nontechnical stuff too.