June 18th, 2002

Project Board; plan 2

Earlier I made some mentions in various places about an lj_dev "Project Board" where developers could find projects that need to be done and get paid for completing them.

It sounded like a great idea, and I started listing dozens of projects in doc/todo.txt, but there was one hard part to it.... setting the price values. I don't want to spend all my time fighting with people over what the correct relative pricing on items should be because really, I have no clue.... some projects don't seem as hard until you start doing it.

So, here's the new plan, which so far jproulx, sherm, and supersat think sounds cool:

* I list projects I want to see done, but I don't set price values.

* The community votes on who gets paid and how much. But how? Read on...

* Anybody that got paid in month 'n' gets to cast votes for month 'n+1', weighted on how much they got paid the previous month.

* You can vote for as many people as you like, giving them all your own weightings. 40% to user_a, 10% to user_b, and 50% to supa_hacka.

* You can't vote for yourself.

* At the end of the month, the pot is split up amongst everybody with votes, based on everybody's weightings, weighted by their resultant weightings in the last month.

* The "pot" will have a minimum publicized amount each month, but it could be increased if a lot of stuff gets done in that month.

The only potential problem I see with this plan is clans forming to vote for each other, but if that happens, I'll notice and stop voting for them, along with everybody else, and they'll drop out of the system. But I think everybody that'd be doing LJ hackin' would be more mature than that.

Basically, this is a project board with automatic pricing, and encourages more inter-developer communication and status updates.

Also, supersat is putting up a Bugzilla for LJ, based on earlier work done by bostonsteamer and his friend for a school project.

just chilling on the internet
  • casey

using LJ as a news source

I'm working on using Livejournal's code for a news site. The plan is to run the LJ code on our own server and have only one community and a couple users set up, so that the staff can post their entries through the LJ client to the community. However, it'd be nice to be able to use the comment system as a "message board," and thus have account registration available for the purpose of posting comments only.

This brings up some complications. Is there a way to not allow the creation of/posting to journals? That is, there would be one journal which could be posted to (the main news site), and it would be a community that certain users have access to. All other journals would be non-existent, because we're really not in a position to host lots of journals.
The idea behind doing this is for the customization of the LJ system pages to match the rest of the news site. This will eliminate confusion and hopefully allow a bit more control over everything going on with the site.

So I guess my main question is, is there a way to make it so that users don't have journals to post to? This reminds me of a discussion I seem to remember a long time ago about the possibility of "comment accounts" being a type of account that could be made in which the user existed only to post comments. I think it was shot down because having an empty journal didn't take up any more disk space, so it wasn't a problem.

Seemed like this was an interesting way to see how LJ can match up against news scripts, which I often find bulky and annoying to deal with. To have the staff able to post articles through the LJ client, something they're intimately familiar with, sounded like a fun idea.