Doyle ,'Life of the Party'
A thread to discuss naming threads, board policy, new thread suggestions, and anything else that has to do with board administration and maintenance. Guaranteed to include lively debate and polls. Natter discouraged, but not deleted.
Current Stompy Feet: Jon B, P.M. Marcontell, Liese S., amych, msbelle, shrift, Dana, Laura
Stompy Emerita: ita, DXMachina
I can also see something like a rewrite of the bookmark system to allow something delicious-like, with public bookmarks and tagging and really good search
That, I could get behind. But I have zero comprehension of what that would involve from a tech or labo(u)r standpoint.
I totally love the idea of a Buffista Knowledgebase wiki.
I use pbworks' wiki format with my students, and it's incredibly user friendly and low maintenance. The creator invites participants, so any Buffista who wanted access would just have to have the admin(s) send an email invite or create a username. Super easy peasy.
I'm against anything where you have to have a separate authentication mechanism. We can install any wiki on this server we want. That's not a problem. The issue is having it be an organic outgrowth of this system. Something externally hosted never can be.
Even if anyone was going to volunteer to send invites out to every single registered Buffista, who's going to stay on top of that?
Oh, that's fine. I wasn't saying it was a better option, ita. I don't have a clue what b.org is capable of internally, so I was just throwing it out there. It's great if we can build it into our own space.
A wiki definitely sounds like the best thing to me, in terms of organizing things. But I can see the authentication issue.
Even if anyone was going to volunteer to send invites out to every single registered Buffista, who's going to stay on top of that?
Could we post a notice somewhere like Press, saying if you want an invite, do this, and they do it and get an invite by some automated system? So that a human doesn't have to monitor and send invites manually? I know nothing about this, as is probably obvious; I just really like automating processes.
I actually take back what I said about no one using it if it wasn't a thread-- I really meant I didn't think anyone would use it if it was off-site. An on-site wiki would be perfect, but I think that any solution that does not call for a lot of work on the side of the developers is good (like the thread solution as envisioned by Strega).
if you want an invite, do this, and they do it and get an invite by some automated system? So that a human doesn't have to monitor and send invites manually?
What's to stop someone from doing that and signing up as Zenkitty and doing all sorts of stuff under your name?
That's a big reason to have them the same. Transparency of identity.
I haven't taken an in depth look yet, but TWiki *might* be flexible enough to allow single authentication: [link]