Can I repost my project?

September 18, 2006 9:49 AM

One of my previously posted projects has undergone a substantial change (ie. it's a free tool now, not subscription based). Do I repost it, not repost it, or assume that this mention (unlinked as to not taint this question) is good enough?
posted by Kickstart70 to Etiquette/Policy at 9:49 AM (13 comments total)

Considering the original post is less than 6 months old, and that you only have 2 links to entries in the projects page, this'll probably suffice, but it wouldn't be completely awful if you posted it anew there.
posted by crunchland at 9:57 AM on September 18, 2006

I don't think you should repost it. Every website changes. I'm not aware of any website or service that is a finished project. Given those facts, I would submit that updates/changes to projects shouldn't be reposted. Rather, people should wait to submit the project until it is substantially close to what the intended version will be. Viewers can then view it and decide for themselves if this is something they like or want to keep up with in the future. I think most people who care to offer input would be inclined to check up on the site in the future to see if the ideas are implemented.

If that isn't the policy, projects would be subjected to **Updated** posts and would suffer for redundancy. Moreover, there would have to be a new and unworkable standard of how significant of an update is necessary before it gets reposted. I suspect it would also encourage people to submit ideas prematurely, with the knowledge that they can submit updates.
posted by dios at 9:57 AM on September 18, 2006

I'd say don't, except that it's apparently OK for random folks to pay $5 to self-link their money-making schemes onto Projects before splitting. In other words, I agree with Dios in principle — but since I don't think Projects has any integrity to compromise, I think it's difficult to object if a contributing member wants to repost his project following a major overhaul. Context matters, and in this case I think you're OK.
posted by cribcage at 10:03 AM on September 18, 2006

My take is this: reposting a project should correspond to fundamental, project-defining changes. Short of that, let it lie.

What qualifies as a fundamental project-defining change is a tricky question, of course, but asking it of yourself and coming to a conclusion you feel honestly good about is enough of a due process to at least prevent ridiculous updates. The temptation to get something in front of mefites' eyes a second time can be strong—satisfy yourself that such is not coloring your judgement and you're probably on firm ground.
posted by cortex at 10:21 AM on September 18, 2006

reposting a project should correspond to fundamental, project-defining changes

Good to know.
posted by jonson at 10:43 AM on September 18, 2006

jonson: I think that definitely qualifies :) I thought about posting Baby Kickbutt (me=Kickstart, wife=j.butterfly) too, but felt weird about it.
posted by Kickstart70 at 10:49 AM on September 18, 2006

Kickstart70, what is your infant reading?
posted by Faint of Butt at 10:52 AM on September 18, 2006

jonson's pugs are truly outstanding pugs.
posted by riotgrrl69 at 10:55 AM on September 18, 2006

Faint of Butt: Reading? She's snoozing. But if you mean the shirt, it's one from UF (of which I am the community guy and head moderator/administrator).
posted by Kickstart70 at 11:19 AM on September 18, 2006

Baby Kickbutt is an AWESOME name. And a cute baby!
posted by jonson at 11:23 AM on September 18, 2006

REPOSTE!
posted by delmoi at 6:56 PM on September 18, 2006

It depends on the load on the service -- are there so many projects that we need to consider projects.metafilter.com a limited resource?

Unclear. Use your own judgement, thanks for asking!
posted by lupus_yonderboy at 8:07 PM on September 18, 2006

jonson's pugs are truly outstanding pugs
Apart from the odd looking one with hardly any fur.
posted by econous at 10:12 AM on September 19, 2006