|
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
949 comments, 0 new
by rudedude, Announcements
New Music Site ... in Scoop
991 comments, 0 new
by MightyD, Announcements
Trees and Things is Coming Out
741 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
493 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
|
|
|
|
Censorship feature for autors
|
|
By Sinsemihl , Section Code []
Posted on Sun Sep 19, 2004 at 12:00:00 PM PST
|
 |
|
We are currently setting up a new Scoop site (looove that piece of software!) that acts as a 'shadow site' to an existing one, a place where (trusted) users can vent steam, rant and have fun without really hurting anyone. Still, I don't want anything offensive to leak into the realm of those that are not logged in, if only for legal reasons, and I pretty much know how I want it be done. Here, I am asking experienced folks for a hint on the best implementation of a way to hide arbitrary parts of posts at the author's discretion.
(17 comments, 256 words in story) Full Story >>
|
|
Time to clean up the HTML code?
|
|
By boxed , Section Code []
Posted on Fri Sep 17, 2004 at 12:00:00 PM PST
|
|
|
The scoop engine is very powerful and flexible but it still uses antique non-valid HTML without CSS which increases the bandwidth costs of the server unneccessarily while making it harder to make skins and making it impossible to use the site from certain devices with small screens.
(18 comments, 278 words in story) Full Story >>
|
|
Box: rdf_feeds_boxed
|
|
By phill , Section Code []
Posted on Tue Jun 22, 2004 at 12:00:00 PM PST
|
|
|
I'm not particularly fond of the one rdf box with all the links lumped inside. I had played around with a system to seperate the rdf feeds into boxes and then allow the user to determine their position as well as turn them off from the page they were displayed on. This is a slimed down version of that idea, minus the arrangement options.
There are four parts: rdf_feeds_boxed, rdf_feeds_single, box_rdf_box, and hiderdf_box.
(12 comments, 1054 words in story) Full Story >>
|
|
User Prefs
|
|
By janra , Section Code []
Posted on Sun May 16, 2004 at 12:00:00 PM PST
|
|
|
Well, I'm getting tired of waiting for somebody to test my patches so 1.0 be released before starting new development, so I say to hell with waiting.
Here is my plan for re-doing user prefs so they're easy for admins to customize and easy for developers to add to.
(12 comments, 823 words in story) Full Story >>
|
|
Comments: easy way to go one level up
|
|
By paugq , Section Code []
Posted on Thu May 06, 2004 at 12:00:00 PM PST
|
|
|
Imagine you see an attractive-titled comment and it's level 5. It renders to be very interesting comment, and now you'd like to read the comment in level 4 this comment is answering. The only way you can do it is going to the story, then clicking the comment in level 4.
(8 comments, 109 words in story) Full Story >>
|
|
Need help.
|
|
By Vladinator , Section Code []
Posted on Sat Apr 10, 2004 at 12:00:00 PM PST
|
|
|
If there is one thing I would change about scoop, it is this:
(9 comments, 101 words in story) Full Story >>
|
|
autoformatting
|
|
By j1mmy , Section Code []
Posted on Sun Mar 28, 2004 at 12:00:00 PM PST
|
|
|
I ran across this perl script that's basically a more robust version of scoop's autoformat, if it interests anyone.
(5 comments, 32 words in story) Full Story >>
|
|
Semi password protect scoop site
|
|
By singing fish , Section Code []
Posted on Mon Feb 02, 2004 at 12:00:00 PM PST
|
|
I have a location based scoop site which will be used by a small number of academic researchers, and I'd like to make it so that only individuals who are logged in can access the scoop portion of the site, effectively disabling anonymous users. I really don't want to use .htaccess files as I don't want my users to have to log in every time they use the site. I will only have a small number of users, so I'm happy to hand roll the account creation process.
What I was thinking was that:
- http://here.mydomain.edu.au is accessible to all.
- http://here.mydomain.edu.au/login.html provides a page to login to the scoop part of the site.
- All requests to http://here.mydomain.edu.au/scoop/* from non-logged in users get redirected to the login page.
I've had a look at Scoop.pm, which seems to be the place to modify the code in, but I'm really not sure where to start the modificatoin process.
I tried to post a message to scoop help several times, but was thwarted by the mailing list telling me they couldn't verify my email address, so I've posted here instead.
Thanks for any help.
Kieren
(12 comments) Comment >>
|
|
|
