totally hypothetical no really i swear
Okay, let's talk turkey here.
Let's go for a hypothetical situation: hypothetically, let's say there is a new journaling service out there that:
* functions like the LJ codebase, but with extra added features you've always wanted;
* has a critical mass of people you care about and total interoperability with LJ, IJ, JF, etc -- not just with RSS feeds;
* operates in a transparent fashion, with regular updates about the behind-the-scenes workings of the service;
* has no advertising and no corporate sponsorship;
* is owned & operated by 3-5 people (with strong internets business-running chops) who all use the service themselves and participate in the community;
* has clearly-defined, public policies, Terms of Service, and guidelines written in plain English;
* is responsive to user suggestions, either implementing them or explaining why they can't be implemented right now;
* maintains a public to-be-done list, roadmap, and goals, and sticks to it
* encourages community participation in the development and the direction of the service
* encourages & promotes creative expression as much as possible within the confines of law, and explains what's going on when limits have to be placed
Bearing this hypothetical service in mind, please answer the following poll honestly and then pimp it everywhere possible.
[Edit to clarify some points, since this is getting linked outside the usual circles, which I think is awesome: a). I'm not talking about a fannish-only enterprise; the hypothetical service would be welcoming of anybody & everybody and have a development model & goals catering to multiple uses of the service; b). I'm talking about a LiveJournal code fork, not a new clone site, with new and active development effort being put forth to fold "oh god we always wanted to do $foo" into the new codebase; c). assume, in your answers & reactions, that the people behind such a hypothetical service know exactly how much time, effort, money, technical know-how, effort, and money is involved in such an enterprise, having been down this road before; d). also assume that said people know the LJ codebase, infrastructure, and userbase inside and out.]
Please also take a second and answer this account level poll, of your kindness!
Poll
Let's go for a hypothetical situation: hypothetically, let's say there is a new journaling service out there that:
* functions like the LJ codebase, but with extra added features you've always wanted;
* has a critical mass of people you care about and total interoperability with LJ, IJ, JF, etc -- not just with RSS feeds;
* operates in a transparent fashion, with regular updates about the behind-the-scenes workings of the service;
* has no advertising and no corporate sponsorship;
* is owned & operated by 3-5 people (with strong internets business-running chops) who all use the service themselves and participate in the community;
* has clearly-defined, public policies, Terms of Service, and guidelines written in plain English;
* is responsive to user suggestions, either implementing them or explaining why they can't be implemented right now;
* maintains a public to-be-done list, roadmap, and goals, and sticks to it
* encourages community participation in the development and the direction of the service
* encourages & promotes creative expression as much as possible within the confines of law, and explains what's going on when limits have to be placed
Bearing this hypothetical service in mind, please answer the following poll honestly and then pimp it everywhere possible.
[Edit to clarify some points, since this is getting linked outside the usual circles, which I think is awesome: a). I'm not talking about a fannish-only enterprise; the hypothetical service would be welcoming of anybody & everybody and have a development model & goals catering to multiple uses of the service; b). I'm talking about a LiveJournal code fork, not a new clone site, with new and active development effort being put forth to fold "oh god we always wanted to do $foo" into the new codebase; c). assume, in your answers & reactions, that the people behind such a hypothetical service know exactly how much time, effort, money, technical know-how, effort, and money is involved in such an enterprise, having been down this road before; d). also assume that said people know the LJ codebase, infrastructure, and userbase inside and out.]
Please also take a second and answer this account level poll, of your kindness!
Poll