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
|
|
|
default-char-set=BIG5 with mysqld would cause scoop to die randomly
|
|
By mark2 , Section Code [] Posted on Wed Feb 26, 2003 at 12:00:00 PM PST
|
|
finally, i got scoop installed on my test bed. what stop me is that scoop always crash the httpd child process randomly.
once i trace to Apache::Session::Mysql, i can't get thru. except changing mysqld settings. i found that i have initially setup mysqld with default-char-set=BIG5, of course, i live in Hong Kong. then i switched back to latin1, the default. then restart everything, and scoop now ran w/o fault, for 6hrs.
(4 comments, 156 words in story) Full Story >>
|
Top-level comment loses subthread
|
|
By floydian , Section Code [] Posted on Fri Jan 31, 2003 at 12:00:00 PM PST
|
|
OK, so I noticed this little bug while reading some stuff over at K5. It goes a little like this:
(2 comments, 125 words in story) Full Story >>
|
Ampersands in link URLs incorrectly handled in digest
|
|
By haflinger , Section Code [] Posted on Sun Jan 12, 2003 at 12:00:00 PM PST
|
|
Scoop often translates the ampersand character into & which mostly is a good idea. However, it shouldn't perform this translation in URLs. It does so when it formats the digest for sending.
(5 comments, 90 words in story) Full Story >>
|
CSS, SPAN, DIV, and HTML4
|
|
By j1mmy , Section Code [] Posted on Tue Jan 07, 2003 at 12:00:00 PM PST
|
|
I've been working on setting up a Scoop site these last few days. I've found that Scoop uses FONT and TABLE elements liberally and makes no attempt whatsoever to leverage CSS.
(9 comments, 265 words in story) Full Story >>
|
Seeking help w/open queue problems
|
|
By ip4noman , Section Code [] Posted on Sun Nov 24, 2002 at 12:00:00 PM PST
|
|
We've just converted http://www.Smokedot.org to open queue. But some things are not working right.
I've posted this to scoop-help, but received no response.
(16 comments, 447 words in story) Full Story >>
|
user-submitted content object updates
|
|
By day , Section Code [] Posted on Tue Nov 19, 2002 at 12:00:00 PM PST
|
|
i plan to implement a mechanism for editing content objects via a web interface. i would like to keep it generalized, so i'm looking for ideas and concerns.
(2 comments, 333 words in story) Full Story >>
|
RFC: Moderation/trust changes
|
|
By rusty , Section Code [] Posted on Mon Oct 21, 2002 at 12:00:00 PM PST
|
|
For a while now, K5 has been operating ok with the addition of the "wipe
ratings" button. Basically, this allows us to negate harm from people
who decide to go on a little rating vendetta and screw with someone
else. However, it's manual admin work that *should* be unnecessary
within the system. Consdering that it needs to be done, this indicates
to me that there is a problem somewhere.
The problem, at heart, is that there's not enough rating going on. If
there was a lot of rating, the system would have a lot more inertia and
be basically resistant to one person's injection of noise. The problem
right now is that there's so little signal that a little bit of noise
can cause problems.
(83 comments, 868 words in story) Full Story >>
|
Returning A Story To The Edit Queue
|
|
By jeffy124 , Section Code [] Posted on Sun Sep 08, 2002 at 12:00:00 PM PST
|
|
On April 18, Rusty added
a long-awaited Edit Queue to Scoop, the code that
operates our beloved Kuro5hin.org. The basic purposes of this was to provide
two hours in which the author of an article can receive editorial feedback (eg,
you misspelled this word, this is sentence is unclear, etc.), without having
votes to worry about until the article looked perfect in the eyes of the author.
After the optional two hours (or shorter if the author chooses), the story would
move into the traditional Moderation Queue where voting would take place. Once a
story is up for voting, edits by the author cannot be made. Or so we thought.....
Scoop developers, especially Rusty, to warn you now, you may require of yourselves
brown
paper bags while reading and dealing with this article.
(19 comments, 369 words in story) Full Story >>
|
|
|