|
What is Scoop
|
Scoop is a "collaborative media application". It falls somewhere between a
content management system, a web bulletin board system, and a weblog.
Scoop is designed to enable your website to become a community. It empowers
your visitors to be the producers of the site, contributing news and discussion,
and making sure that the signal remains high.
More >>
Check out what other people have done with Scoop.
|
|
New Scoop Sites
|
rudepeople.com in need of a makeover
950 comments, 0 new
by rudedude, Announcements
New Music Site ... in Scoop
991 comments, 0 new
by MightyD, Announcements
Trees and Things is Coming Out
743 comments, 0 new
by 3fingerspointback, Announcements
TalkLeft Moves to Scoop
636 comments, 0 new
by TalkLeft, Announcements
SciScoop Science Forum
518 comments, 0 new
by sciencebase, Announcements
New Site: "Field Gulls" Unofficial Seattle Seahawks Blog
514 comments, 0 new
by Paul Shrug, Announcements
More New Scoop Sites...
|
|
Where can I get Scoop
|
|
You can download the latest release tarball: scoop_1.1.8.tar.gz
You can grab the nightly build. Note: This is generated automatically from the current CVS, and may not be reliable! Get that here: scoop-1.1-nightly.tar.gz
The developers strongly recommend CVS as the primary way to obtain Scoop, since releases tend to have pretty long delays between them. If you have CVS installed, do the following:
cvs -d:pserver:anonymous@ scoop.versionhost.com:/cvs/scoop login
cvs -z3 -d:pserver:anonymous@ scoop.versionhost.com:/cvs/scoop co scoop
The above is two commands; each one must be on a single line. When prompted for a password for anonymous, enter 'anonymous' (without the quotes). For more CVS info, "Open Source Development with CVS" is an excellent online reference.
|
|
Where can I get help
|
|
There are several sources of information and support for Scoop. The first place to look is the scoop-help mailing list. You can browse the archives, or join the list. If you want to post a question, joining the list is strongly recommended. You can also join the #scoop IRC channel on SlashNET.
For documentation, there is the (largely complete) Scoop administrator's guide. You can also read the current
README and
INSTALL files, from Scoop WebCVS (username and password are both "anonymous"). The admin guide is also included with Scoop, in the doc/ directory.
If you have new feature ideas or requests, or descriptions of something you're working on for Scoop, this site is the place to submit them. You can also search this site for information. If you want to get your hands dirty, or have any questions about developing for Scoop, there is also the Scoop-dev list. You can browse the archives, or join the list.
Bug reports and patches should be filed on the Scoop Bug Muncher.
If you have any problems with this site or your user account, e-mail the Admin
|
|
|
|
Defining stories <--> objects associations
|
|
By sleeper22 , Section Code []
Posted on Sun Sep 08, 2002 at 12:00:00 PM PST
|
 |
A mechanism for establishing many-to-many relationships betweeen stories and other records in the database.
(8 comments, 667 words in story) Full Story >>
|
|
a shopping cart for scoop
|
|
By sleeper22 , Section Code []
Posted on Sat Sep 07, 2002 at 12:00:00 PM PST
|
|
|
Here's some proposed design ideas for a general shopping cart feature for scoop.
(2 comments, 1104 words in story) Full Story >>
|
|
scoop on Xitami?
|
|
By sethadam1 , Section Code []
Posted on Sun Sep 01, 2002 at 12:00:00 PM PST
|
|
|
I run both Linux and Windows at home. I have played with Scoop before, but since I just set up a new server, I have been using the super fast, super flexible Xitami web server to serve my web pages locally. I don't know too much about it other than the fact that it is apparently widely used, cross platform, and extremely easy to administer. Has anyone ever attempted to get a Scoop site to work with Xitami?
(8 comments, 146 words in story) Full Story >>
|
|
Changing a last five comments box from perl to Scoop box
|
|
By phill , Section Code []
Posted on Tue Aug 13, 2002 at 12:00:00 PM PST
|
|
|
I've been trying to mold scoop into a better version of what I wrote a while ago and I've hit a stump. Is there a scoop equivilant to this perl code? (it just takes the last 5 comments on a particular story and formats them for a box)
(5 comments, 177 words in story) Full Story >>
|
|
How to get a thread in one query
|
|
By KWillets , Section Code []
Posted on Tue Jun 18, 2002 at 12:00:00 PM PST
|
|
|
In a recent story, it was mentioned that the Comments.pm code has a very clumsy way of retrieving and constructing the comments tree.
There are a number of semi-established methods for getting all the nodes in a tree or subtree in one query. I'll try to enumerate all of them, in the hope that one method will be adopted.
I'm willing to work on whatever solution seems workable.
(5 comments, 618 words in story) Full Story >>
|
|
Better Section List
|
|
By tneff , Section Code []
Posted on Wed May 08, 2002 at 12:00:00 PM PST
|
|
|
One thing I didn't like about the default Scoop distribution was that the section links in the header (block section_links) was just a hard-coded list of HREF's that you have to remember to edit every time you add, remove or change a section -- and it stays static for every visitor, regardless of whether they have the privilege to see all the sections listed. So I fixed it...
(3 comments, 239 words in story) Full Story >>
|
|
Edit Queue?
|
|
By UncleMikey , Section Code []
Posted on Tue May 07, 2002 at 12:00:00 PM PST
|
|
|
So, does CVS contain everything needed to make the edit queue work? I've just updated, and I see *some* of the relevant pieces, but not all, and an article I just submitted to my site as a test did not have any options for pushing it to the edit queue...
(161 comments) Comment >>
|
|
|
