|
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
|
|
|
|
At what point is a YASS inappropriate?
|
|
By Random Liegh , Section Dev Notes []
Posted on Fri Apr 30, 2004 at 08:35:54 AM PST
|
 |
|
I have set up a web server on my machine, and installed scoop on it. Mostly this is to archive funny slashdot troll posts and personal thoughts I don't want to entrust to husi.
Given the highly wanky nature of the site, a YAS would or would not be appropriate?
What are you lots' thoughts?
(147 comments) Comment >>
|
|
Building a Wiki on Scoop
|
|
By Driusan , Section Dev Notes []
Posted on Tue Apr 20, 2004 at 11:48:45 AM PST
|
|
|
I've been growing frustrated with ZWiki lately which has inspired me to try to try and build a wiki on top of Scoop (hence the reason for surreptitiously filing this bug in the hopes of using the same code for wiki revisioning, but ssh! Don't tell anyone.)
I think with autoformatting and the ability to store old versions of stories/pages/whatever most of the pieces needed to build a wiki are in place. So I'm just going to outline my plan to a) make sure it hasn't been done by someone else b) get feedback and make sure I'm not missing something blatantly obvious and c) let people know that I'm working on it.
(3 comments, 496 words in story) Full Story >>
|
|
test title
|
|
By rogy , Section Dev Notes []
Posted on Wed Apr 14, 2004 at 02:59:15 AM PST
|
|
|
asdfsadfíéáýé=šè¾tééegfe w
(1 comment) Comment >>
|
|
I like these diaries
|
|
By senorbunch , Section Dev Notes []
Posted on Wed Mar 10, 2004 at 08:46:46 PM PST
|
|
|
I stripped them out of my site, but now I want to put them back in.
(1 comment) Comment >>
|
|
Scoop on Mac OS X?
|
|
By kjb , Section Dev Notes []
Posted on Mon Dec 29, 2003 at 10:06:56 PM PST
|
|
|
I'm interested, as an excercise, in getting Scoop running on my Powerbook running Mac OS X.
(1 comment, 106 words in story) Full Story >>
|
|
Why is K5 so slow?
|
|
By dh003i , Section Dev Notes []
Posted on Thu Dec 25, 2003 at 10:56:53 PM PST
|
|
|
Why is Kuro5hin.org so slow? Is it because of Scoop, or the the server, or what? I'm trying to decide upon a weblog system to use, and I don't want my site to be as unstable and slow as K5 (half the time, there's some stupid modperl error).
(1 comment) Comment >>
|
|
ugh
|
|
By turmeric , Section Dev Notes []
Posted on Sat Aug 09, 2003 at 04:32:05 PM PST
|
|
|
i just wrote a several page story about how e-gold could be used to implement micropayments with scoop. unfortunately, scoop decided that it needed to small-caps all the letters in an a href link, which completely is stupid but also causes an error on the spiffy e-gold payment page i could have shown you. so i tried to click 'back' after 'preview' and guess what? scoop lost my whole story.
(1 comment) Comment >>
|
|
|
