Dev.SN ♥ developers
Sections
Dev.SN
from the soylent-news-is-(even-more)-people dept.
It's amazing what a small group of dedicated people can achieve in such a short amount of time. I'd like to thank you on behalf of the entire Soylent Staff, for helping us build a new community - a community of the users, by the users, and for the users.
It's been a week (only a week!) since first rollout, and extrapolating from our usage we're serving 5 million pageviews per month. That's huge. For comparison, Slashdot serves an estimated 15 million pageviews per month.
The pageview rate is also climbing - we passed the 2 million mark somewhere around our 9th day online. We'll soon need a higher service tier.
The site's estimated value grew from $43 (Tue) to $639 (Fri) to $2000 (Tue - today). Woot!
It's been a wild ride! Read more about it below.
The sys team is building the infrastructure to support a mainstream site. We purchased 3 more linodes (full year, for a 10% savings), which are being provisioned for development, test, and production. The dev team is preparing a turn-key slashcode package that developers can run locally, and we have already started to see bug fixes appear in the live site, with more to come.
The style team has a long list of planned improvements, and the content groups have been feeding us a steady supply of delicious article summaries, spirited debate (IRC, forums), plans and roadmaps (Wiki, status posts), with contributions from many other groups. We have our own customer relations person!
I promised that the project would be community driven, and we are largely that. Each overlord has agreed to run their department by community consensus, only making executive decisions when there is no general agreement, or if there is a global overriding concern. This is working well. For the majority of cases consensus is clear and feels "clearly the right decision". For a split consensus, both choices seem equally good so it doesn't matter which one we choose.
The overlords have authority to make decisions in their area, which means people can get involved with areas that interest them without wading through everything. If you would like to participate, come join us!
Global issues will be decided by community vote. Notable votes coming up will be 1) Choosing a permanent name, 2) Choosing a business model, and 3) Choosing revenue streams. I have researched these and have notes and observations to set before the community as a starting point for discussion.
That's my next step: setting down the notes for discussion, some background information (such as projected expenses), and orchestrating the voting process. Once the business/financial models have been chosen we can start building a proper business.
It looks like we've got ourselves a winner!
(Score: 5, Insightful) by chebucto on Friday February 28 2014, @02:24AM
I disagree; putting stories out with no schedule would bury the ones published first.
One change I would like to see is more frequent stories; perhaps every half hour or every hour. Doing that depends on getting more stories submitted, though, and that part is up to the users.
(Score: 1) by quadrox on Friday February 28 2014, @02:27AM
Buried? Haven't we all learned how to scroll on a webpage? Aren't you doing that anyway when you login for the first time after a period of absence, e.g. In the morning?
(Score: 1) by hubie on Friday February 28 2014, @10:54AM
It's not as simple as just scrolling. Stories get pushed to yesterday's news, and when you click that button to load them, the first N stories on that page are the ones that were at the bottom of the previous page, so you only end up picking up a relatively few extra stories on your current page, so then you need to click the button for the previous day stories . . .
(Score: 5, Insightful) by Popeidol on Friday February 28 2014, @03:34AM
I like the queueing system for a few reasons:
One addition that could help could be a field to mark each item in the queue by time-sensitivity. A breaking story about scotland adopting Bitcoin as their national currency would automatically be bumped ahead of the piece about interesting historic trends in heatsink manufacturing (which can really go up anytime).