Archive for the 'General Blogginess' Category

No more blog (user) subscriptions

I turned off blog [user] subscriptions on the blogy blog (i.e. here, not http://orblogs.org). It was just getting to much traffic from auto-subscribe spammers, and little from actual citizens. It shouldn’t really matter, since we don’t use the subscription accounts anyway, except for an early plan to allow known subscribers to be post authors.

I had to go through and do a “best guess” as to whether accounts like “agniast8ed” from Russia was a human or auto-subscribe. For the most part I erred on the side of deletion.  If I deleted your account, and you’re a real human being, I apologize. But again, it doesn’t matter, there’s no reason to have an account unless you want to eventually post, and if that’s the case, I’d know about it anyway.

Account or no, you can still subscribe to the feed. It’s a slow feed, with not many updates– because there’s not to terribly much to update you on. The Oregon Blogs aggregator is running at a functional level, and those of us on the planning side are currently figuring out how to proceed with code sprints and improvements in the long term. The best thing you can do now is use it. And tell us about bugs, either by sending a shout to the mailing list or tweeting to @ORBlogs. This will help us continue the improvement of the aggregator.

Code Sprint! March 7th at CubeSpace

The ORBlogs community is having our first code sprint on March 7th at CubeSpace, from 11am until 4pm with celebration to follow. We thank the great folks at CubeSpace for donating the space for this code sprint, so be sure to lavish them with affection!

This code sprint will be a gathering open to everyone interested in taking the current Oregon Blogs Test Site and turning it into a working digg-style blog aggregator. As Bill states:

“I would really like to encourage everyone on the list to at least consider coming to the meetup!  As I have said before: whether or not you are a programmer, we are all developers, and we should own this as a  community.  I bet you all have some valuable input as to how the site should look and flow, and you can give us coders some very useful direction.”

Details will follow shortly about the main issues we will be tackling. Stay tuned both here and on the Groups Page for more information.

Test site fixed!

Hey gang, the test site is now working correctly again.  Hooray!  If you’re interested in the details, this was the fix.

Please go ahead and create yourself an account, add plenty of (appropriate) feeds, file issues for anything that is broken or otherwise obviously wrong, and chat us up on the mailing list with ideas for improvement!  Please don’t be shy, we need as many people beating on this thing and providing feedback as we can get!

When you are adding feeds, don’t worry about the checkbox that says “I own this blog/website”.  Add any sites you like, as long as they fit within the ORBlogs purview!  I believe we will eventually be getting rid of that checkbox and the current model of feed ownership, and moving to either a curated model or a community-managed model.  I could be wrong, though.  :)

If you are already on the mailing list, you may have noticed a couple of messages from TeamCity (our continuous integration server).  I set it up to directly notify the list on most build events; I believe it helps us toward our goals of agility and transparency.  If for some unlikely reason it becomes a burden, we can always turn it off or redirect it to a secondary mailing list.  Also, if you create yourself an account on the TeamCity server and want more than just “viewer” access, let me know and I’ll hook you up!

-Bill

Getting Things Done

Hi all!  John gave me rights to post here, so I thought I would abuse the privilege for a moment.

I feel like we have been stalling a bit, so I have done a few things recently to try to make the development process more transparent, as well as easier for anyone who wants to just jump in and do what they can, but may have been stymied by not knowing where to start.

I posted on the mailing list earlier today about what I have been doing, so go ahead over there for the details, and reply on-list (my preference), in the comments here, or via Twitter if you have any questions.

By the way, go ahead and consider this another call for development help.  Anyone have some #afterhours they want to contribute to this?  ;)

Cheers,
-Bill

Quick update

Thought a quick update on status would be good.

There are at least 4 people looking at the codebase, including me. This is a good sign because, although it’s complex and feature rich, it’s relatively clean and Patrick (@plightbo) has graciously provided a script to grab the dependencies, meaning going from “broken” to “not broken” is relatively painless.

Having awakened at 4:45 this morning (don’t ask), I was able to compile the codebase cleanly using his script (For the non-tech folks, this means that the engine runs, although there may be a few problems yet with brakes and steering, so you wouldn’t want your daughter to drive it yet).

I’m communicating with Patrick now about setting the code up on a server. Once that’s done, we will take AJ’s (@linuxaid) database and start connecting it.

Sam Klein stepped up to work on graphics, so when things are running, we’ll have a full graphics design, making a later search for such work unneeded. Thanks, Sam.

Right now the steps we need immediately to get the site running are:

  • Get the compiled codebase running on a test server.
  • Dump AJ’s database to the server and hook up the wires
  • Hook up AJ’s parser scripts to those wires to keep things updated

I’ll keep you updated here on how that’s going. Feel free to comment or send questions to the Google Groups List if you have them.

The Camel In Our Midst

Gil Taylor pointed out in his email to the Google Groups list that the current effort with ORBlogs is not working (rather than try to summize it, I suggest you read it because I may not judge it fairly).

I also suggest you read my reply just so that you don’t think I’m a thoughtful, intelligent person who calmly considers other people’s point of view before screaming at the top of his lungs.

In short, I’m embarrassed, and want to apologize. I’m sorry everyone. I’m sorry Gil.

There’s a large part of me that’s taken personal responsibility for trying to get ORBlogs back on the map. That responsibility- and subsequent accountability- is important for a successful effort. As I stated in my original post regarding ORBlogs- making one person responsible and accountable will give the community one single person to look to when they want to ask… well… just what Gil was asking:

Why the hell isn’t anything happening?

The one issue with being that person who takes on that accountability is that you have to both have the ability to get the job done, and have the skin thick enough to shrug stuff off. I suddenly wonder if I’ve been disingenuous in taking on this role.

Although there’s a part of me that wants to, I’m not going to give a list of things that we have accomplished, I think it’s fair enough to agree with Gil on where we are. ORBlogs is not yet live. Although I maintain my offense at the suggestion that we are a committee just meeting and not reaching consensus- I agree that the actual site is not running yet.

That’s been bothering me a great deal, and I was very happy when Kyle came forth with Ignoregon, because it seemed the best of both worlds. A functional, if basic, site for the immediate need- and another solid and active person to attack the BigBark code.

It seemed, in fact, like just what Gil was suggesting- and what we’ve all wanted.

So I think it was my earlier frustration with myself. It was anger, sadness and a great deal of pain at what’s happened personally. It was anger with my own lack of progress that I was reacting too. It wasn’t Gil’s comments about committees and camels which still sting just enough that I have to bring them up one more time even though it’s not a camel but a dead horse we’re talking about now (really, John, let it go!).

I was pretty forceful in my original post that we needed a point person, one person, to take responsibility. I didn’t actually think it would ever be ME (You’d never even heard of me before that!). I was stunningly honored that people would accept me, and suddenly felt that I had found a lot of friends. Still, we need to think seriously about this. My response to Gil was pretty irresponsible.

(By the way, that whole “friends” thing, oh and the italicized “active”- heck, half of this post- I can’t help it. We bloggers are writers first. I just can’t ignore those dramatic, touching bits. They shouldn’t sway you, however. Snap out of it.)

I’m sorry everyone. Seriously. I shouldn’t be speaking for ORBlogs, nor for AJ, Patrick, Rick or Kyle. If someone else wants to take over, I can turn over the domain, the blog, the Google groups account, the Goog-

(See- there I go, listing everything- even after I said I wouldn’t. Drama, I tell you.)

Okay, seriously. There are plenty of people out there better than me. Take over. Be someONE.

But you needn’t start from scratch. There’s that Java code just waiting. It’s right there- we’re pretty close.

By the way, Rick Turoczy has the keys to this house. AJ and Patrick have the keys to the code page. They- as anyone, should feel free to lock me out at any point.

Until then, I’ll just keep on chugging away, and realize that I owe Gil a beer for screaming at him. I really am sorry, Gil.