Opened 11 years ago

Closed 11 years ago

#680 closed Task/To do item (fixed)

Launch blog site

Reported by: alfredo Owned by: Jamie McClelland
Priority: High Component: Tech
Keywords: new site Cc:
Sensitive: no


I'd like to propose launching our new website and our blogs site on Wednesday (March 10). This is because I think they are ready and I don't think any of us has come up with a reason not to.

This is especially true because after working on it together yesterday, Jamie and I are convinced that we should not use Drupal 6 on the blogs site yet and should launch the site in 5. Not only does Drupal 6 not have the cck support (which is not critical for blogs site at this point), it lacks image module support (which is in dev stage) and image assist support (which isn't there at all). This would therefore preclude the easy uploading and insertion into nodes of images as an option for us. That changes the character of any site, in my opinion and I think Jamie agrees with that.

While we could probably get around some of the third party module issues, the entire picture is one of transition and instability. We just can't be sure this version is going to work right, especially since it has integrated Openid so quickly into core. That integration is largely untested.

What's more, what we're seeing of the Openid module on Drupal requires at least some hacking (as Jamie has done to the 5 one). Hacking stuff in Drupal core is a huge risk and so my hunch is that Openid on 6 is not going to solve our problems without extension or hacking and that would be even more tricky in core (in 6).

It seems, at this point, that 6 would require compromises that aren't acceptable. Jamie and I have agreed that we should launch with our blogs site at 5.

Everybody should check these sites again, please. Anything that would stop launch should immediately be pointed out.


Change History (12)

comment:1 Changed 11 years ago by Jamie McClelland

I think the blogs site is just about ready to go and could be launched March 10. Daniel's wiki page is a really useful way to see what tickets are still open. I don't thin any of them should preclude a launch.

I also think that page could be filled out more so when we launch we could send people to the page.

Speaking of launching, how are we launching? Are we launching it as and ask a dozen people or so to try it out? Or are we launching it as and sending out a Lowdown telling people about it?

I have a few more issues with - I think we may want to hold off on that launch a little longer. I will open tickets with those issues now.

comment:2 Changed 11 years ago by Jamie McClelland

I just added some new tickets with the keyword: If you search on the key word they should show up. None of them are huge - but it might take us a week to get through them.

comment:3 Changed 11 years ago by alfredo

The blogs site is ready and the email asking for "testers" is out. We should see what people do for a week or so and then probably go into a launch plan.

I also believe the new site is ready but we need to think about appropriate content (like in news and member profiles).

This should be a discussion this coming week (March 30 week)

comment:4 Changed 11 years ago by Jamie McClelland

Summary: Launch main site and blog site this week (March 10)Launch blog site

I'm changing the subject to reflect that fact that the main site has already been launched.

comment:5 Changed 11 years ago by Jamie McClelland

Keywords: added; blogsmf removed

comment:6 Changed 11 years ago by alfredo

Can we deal with the rss issue finally? At this point, I'm ready to go along with everything if that's what it takes to get the blogs site up and running. Well, almost anything. :-)

comment:7 Changed 11 years ago by Jamie McClelland

I just posted a proposed compromise on the RSS issue.

There are a handful of open tickets on Does anyone see issues that should stop a launch? I think #682 is potentially the most serious and #695 should be easy to fix. I'm not sure if either should hold up the launch. Thoughts?

comment:8 Changed 11 years ago by alfredo

We shouldn't delay and I completely agree with the compromise you proposed.

Ticket #695 is something I can and should fix in about ten minutes sometime over the weekend although it can take a long time to figure out where the error is. Daniel's done a great job fixing these errors so I think these guys are probably in my modules or on the site itself (some kind of code in a block or something).

Ticket #682 would require an investigation about where, in blogs, the site name is not being transmitted. It could be a module bug but it's much more likely that the problem resides in the way we're handling the user experience on the site: maybe I did something in module code that affects the login system and doesn't pass the site name variable? That's highly possible and it's probably fixable but it's one of those "could take five minute if you're lucky but make sure you have several hours".

I wouldn't hold the site back for that since it doesn't really affect the site functionality or user experience.

What I'd suggest doing is getting the Jamie compromise stuff ready and launchin. The idea of launching this before June is very exciting. It completes the suite of major site changes we have made in this organization and we now have very capable and solid member experience systems.

It is among our most effective arguments for being a member. We should all be pleased and proud. :-)

Let's make a launch date?

comment:9 Changed 11 years ago by Jamie McClelland

Ok - is now launched. is still around - but is password protected to avoid anyone thinking they are on the real site (user: mayfirst, password: mayfirst).

comment:10 Changed 11 years ago by Daniel Kahn Gillmor

Keywords: added; removed

comment:11 Changed 11 years ago by Daniel Kahn Gillmor

I've retagged all the open tickets related to the blogging site with, and updated mfpl_blogging to include an auto-generated list of the relevant tickets. There are about a dozen open, of varying severity.

But since the point of this ticket has been resolved (the site is launched), i'm closing this one.

comment:12 Changed 11 years ago by Daniel Kahn Gillmor

Resolution: fixed
Status: newclosed

uh, i'm really closing this one :P

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.