On 17/01/04 11:56 -0800, Cory R. King wrote: > Heh, it's hard to reply to a .txt attachment :-) Sorry about that. I typed it up outside of my mail program. > > -- etc. -- > The big thing I have not checked in yet is scoop plugins. Through plugins, > I think that everything I envision could be done /w no forks of the central > code base. The only caveat to that is we'd need to make the current comment > system and story system plugins. > > There are some other things I've done, but not checked in: > > - CSS Support > - Better themes (still needs work though) > - Better block editor (which is tightly coupled with themes) > - Menu system Themes definitely need work. I don't know jack shit about CSS, but I know that people have successfully gotten it to work with Scoop. What they did exactly, I have no idea. Block editor: makes sense. Menu system: I'm not exactly sure what you mean. > > Other things? > > - People have been clamoring for scoop to work on non mysql databases. panner's been working on this forever. Perhaps we can get what he's been working on into CURRENT so we can at least have some idea where he's gotten. > > These are things on my mind for future work: > > - A way to elegantly distribute stories across multiple, independent scoop > sites. The story system would be like RDF on crack. Users could post > stories to the "scoop network" from the scoop site of their choice, and > other scoop sites could vote (or the editors could just force in) those > stories into their own scoop site. Very cool things could happen with this. > > > - A way to share user information across scoop sites. User information > could be housed in a central repository and shared across scoop sites. I've done some work on this very subject for distributed scoop. There was some disagreement between hillct and I how to go about it, but I do have some stuff that could be used. It's nowhere near usability yet, but at the very least Scoop can use sockets for communication now. > > - Get rid of all the freaking vars and make some decisions on our own! > Scoop has more admin preferences then any piece of software I've worked on. > We should sit down and talk about what scoop should and should not do. I > hate to say it, but having such an easy way to just pull new vars out of our > ass has really made the site control page a mess. I do it all the time! This sounds like an issue for Scoop Lite to deal with. I don't have a problem dealing with the vars personally, but I see how it could be confusing. If nothing else, I think administrators should have some control over what exactly they get to configure. I think the biggest issue right now, though, is to get Scoop 1.0 out. After that, we can go whole hawg with all this other stuff. That's a big reason I haven't worried too much about doing stuff with CURRENT besides syncing it with the main Scoop codebase periodically. -j > > > -----Original Message----- > > From: scoop-dev-admin at lists.sourceforge.net [mailto:scoop-dev- > > admin at lists.sourceforge.net] On Behalf Of Jeremy Bingham > > Sent: Friday, January 16, 2004 8:47 PM > > To: scoop-dev at lists.sourceforge.net > > Subject: [Scoop-dev] Scoop 1.0, CURRENT, CVS, etc. > > > > I managed to find some time today to cobble some stuff together about > > some of my thoughts on Scoop development, including Scoop 1.0, > > Scoop-CURRENT, the CVS stuff, and some other things. You will find the > > file attached to this email. > > > > -j > > > > ---------------------------------------------- > > /* You are not expected to understand this. */ > > > > Captain_Tenille > > http://www.satanosphere.com/ > > http://www.kuro5hin.org/ > > jeremy at satanosphere.com > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Scoop-dev mailing list > Scoop-dev at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/scoop-dev -- ---------------------------------------------- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ http://www.kuro5hin.org/ jeremy at satanosphere.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.kuro5hin.org/pipermail/scoop-dev/attachments/20040117/206a7ca4/attachment.bin