|
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
|
New Music Site ... in Scoop
0 comments, 0 new
by MightyD, Announcements
Another new scoop site!
4 comments, 0 new
by nemsis, Announcements
Trees and Things is Coming Out
1 comment, 0 new
by 3fingerspointback, Announcements
TalkLeft Moves to Scoop
2 comments, 0 new
by TalkLeft, Announcements
SciScoop Science Forum
1 comment, 0 new
by sciencebase, Announcements
New Site: "Field Gulls" Unofficial Seattle Seahawks Blog
1 comment, 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
|
|
|
|
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.
(1 comment, 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.
(7 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.
(1 comment, 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:
(2 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.
(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
(4 comments) Comment >>
|
|
Getting parameters in 'story_summary'
|
|
By phill , Section Code []
Posted on Fri Jan 16, 2004 at 12:00:00 PM PST
|
|
|
I am trying to move some of the changes that I've made to the scoop code into boxes so that I can move my site to a scoop host.
I'm at an impasse, however. I am trying to modify the topic_img tag inside the story_summary block so I've replaced it with a box that does the same thing with one major difference: I cannot get the tid so I can check whether or not it is a diary story. I've tried adding my $story=shift; and I've looked through the code in lib/Scoop. I can't seem to find a $S->somthingarouther that will return the tid or even the section. Any thoughts?
(6 comments) Comment >>
|
|
Updated hotlist_flex box
|
|
By hulver , Section Code []
Posted on Mon Dec 08, 2003 at 12:00:00 PM PST
|
|
|
I've done some changes to the hotlist_flex box from the SBE.
1. To make it actually work with the changes to the story table.
2. Steal k5's "Clear all" and "Clear user" functions.
3. Sort it in name order
4. Speed the diary hotlist up a bit. This was doing at least one query for every user on the hotlist. I've changed it to do only one query.
Update [2003-12-11 23:8:16 by Mostly Harmless]: applied a patch from hulver so if the box is now broken, it's probably my fault :-)
(9 comments, 1475 words in story) Full Story >>
|
|
|
