Menu
▾
▴
slashcode-development
|
From: CertIndex.com W. <web...@ce...> - 2000-12-09 11:24:25
|
Greetings, After talking with Krow/Brian we'll be undertaking the most desirable task of creating a plugin to make the story submission queue open. Due to our own internal timeline, this must be done this following week. Therefore, I would appreciate any comments, suggestions, feature requests, etc. to be emailed to me by 0:00 Wednesday GMT. Ciao, k |
|
From: Chris N. <pu...@po...> - 2000-12-09 12:31:45
|
At 3:25 -0800 2000.12.09, CertIndex.com Webmaster wrote: >After talking with Krow/Brian we'll be undertaking the most desirable task >of creating a plugin to make the story submission queue open. Due to our own >internal timeline, this must be done this following week. Therefore, I would >appreciate any comments, suggestions, feature requests, etc. to be emailed >to me by 0:00 Wednesday GMT. Is this an RFC? An RFC usually details a plan that people can comment on. I don't really have any idea what it is that you propose to do. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-09 12:36:41
|
We cannot document *how* we will do this since we don't even yet know *what* all people would like to see done. The Request For Comment isn't with regards to technical design but rather 'business' design. You must document what before you can document how, and this is what we want. Does this make it more clear to you? Ciao, k ----- Original Message ----- From: "Chris Nandor" <pu...@po...> To: <sla...@li...> Cc: <sla...@li...> Sent: Saturday, December 09, 2000 4:25 AM Subject: Re: [Slashcode-development] RFC for Open Story Submission Queue plugin > At 3:25 -0800 2000.12.09, CertIndex.com Webmaster wrote: > >After talking with Krow/Brian we'll be undertaking the most desirable task > >of creating a plugin to make the story submission queue open. Due to our own > >internal timeline, this must be done this following week. Therefore, I would > >appreciate any comments, suggestions, feature requests, etc. to be emailed > >to me by 0:00 Wednesday GMT. > > Is this an RFC? An RFC usually details a plan that people can comment on. > I don't really have any idea what it is that you propose to do. > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development > |
|
From: Chris N. <pu...@po...> - 2000-12-09 13:13:25
|
At 4:38 -0800 2000.12.09, CertIndex.com Webmaster wrote: >We cannot document *how* we will do this since we don't even yet know *what* >all people would like to see done. The Request For Comment isn't with >regards to technical design but rather 'business' design. You must document >what before you can document how, and this is what we want. Does this make >it more clear to you? No, because I still have no idea what it is that you are talking about. That's the point. You want to create a "plugin to make the story submission queue open." What does that mean? -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-09 13:27:26
|
Sorry, that being one of the most requested features of Slash I assumed you and the others on this list would know what I was referring to. Simply put, it creates the ability for the registered users of a Slash site to vote on which submissions to the story queue are posted and which are not. Now are you clear? Ciao, k ----- Original Message ----- From: "Chris Nandor" <pu...@po...> To: <sla...@li...> Cc: <sla...@li...> Sent: Saturday, December 09, 2000 5:12 AM Subject: Re: [Slashcode-development] RFC for Open Story Submission Queue plugin > At 4:38 -0800 2000.12.09, CertIndex.com Webmaster wrote: > >We cannot document *how* we will do this since we don't even yet know *what* > >all people would like to see done. The Request For Comment isn't with > >regards to technical design but rather 'business' design. You must document > >what before you can document how, and this is what we want. Does this make > >it more clear to you? > > No, because I still have no idea what it is that you are talking about. > That's the point. You want to create a "plugin to make the story > submission queue open." What does that mean? > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development > |
|
From: Chris N. <pu...@po...> - 2000-12-09 14:35:17
|
At 5:29 -0800 2000.12.09, CertIndex.com Webmaster wrote: >Sorry, that being one of the most requested features of Slash I assumed you >and the others on this list would know what I was referring to. Simply put, >it creates the ability for the registered users of a Slash site to vote on >which submissions to the story queue are posted and which are not. Now are >you clear? Only partially. I've actually only seen anything like this requested only once. I've many times seen people request the ability for users to post stories, but only once seen anyone ask to vote on stories. And what happens when they vote? Are they automatically posted? These are the kinds of details I would need in order to comment on it reasonably. Simply detail what it will do, as you see it, and note that it is subject to change. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-09 15:12:14
|
I did simply detail what it will do, as we see it. I'm sorry if I'm not being clear but I've discussed it with a non-trivial number of people before referring to it only by 'open story submission queue plugin,' no further explanation needed. I would like to be clear to the point where everyone, even you, could understand, but sadly I do not have any time available to further clarify what we'll be coding. People who *really* want this feature will know exactly what we're setting out to do and will have already thought about it a considerable amount, considering how popular of a feature request it is. Thus they will be more the people we seek comments from. Hopefully well get ya on the next feature we code. ;) That's very likely considering we now have a developer dedicated to Slash development full time. Ciao, k ----- Original Message ----- From: "Chris Nandor" <pu...@po...> To: <sla...@li...> Cc: <sla...@li...> Sent: Saturday, December 09, 2000 6:34 AM Subject: Re: [Slashcode-development] RFC for Open Story Submission Queue plugin > At 5:29 -0800 2000.12.09, CertIndex.com Webmaster wrote: > >Sorry, that being one of the most requested features of Slash I assumed you > >and the others on this list would know what I was referring to. Simply put, > >it creates the ability for the registered users of a Slash site to vote on > >which submissions to the story queue are posted and which are not. Now are > >you clear? > > Only partially. I've actually only seen anything like this requested only > once. I've many times seen people request the ability for users to post > stories, but only once seen anyone ask to vote on stories. And what > happens when they vote? Are they automatically posted? These are the > kinds of details I would need in order to comment on it reasonably. Simply > detail what it will do, as you see it, and note that it is subject to > change. > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development > |
|
From: Chris N. <pu...@po...> - 2000-12-09 15:30:34
|
At 7:14 -0800 2000.12.09, CertIndex.com Webmaster wrote: >I did simply detail what it will do, as we see it. I'm sorry if I'm not >being clear but I've discussed it with a non-trivial number of people before >referring to it only by 'open story submission queue plugin,' no further >explanation needed. Well, now you are publcially asking for comments, and further explanation is needed. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-09 16:03:12
|
Further explanation is needed by you, apparently, but with all do respect, you don't speak for everyone. As I've already stated, I've spoken with plenty of people who didn't need even as much clarification as I've given you to know exactly what I am referring to. We don't *need* feedback. We already have all of our needs designed into the plugin. I thought I would give everyone on this list the opportunity to give me feedback because I'm kind and if there was something someone wanted that wouldn't be too difficult, we would go ahead and code it for them. As stated, sadly I do not have the time available it would take obviously to detail every feature to the level *everyone* would understand. If this bothers you, please feel free to ignore this thread; there's nothing more I can do, regrettably. Ciao, k ----- Original Message ----- From: "Chris Nandor" <pu...@po...> To: <sla...@li...> Cc: <sla...@li...> Sent: Saturday, December 09, 2000 7:29 AM Subject: Re: [Slashcode-development] RFC for Open Story Submission Queue plugin > At 7:14 -0800 2000.12.09, CertIndex.com Webmaster wrote: > >I did simply detail what it will do, as we see it. I'm sorry if I'm not > >being clear but I've discussed it with a non-trivial number of people before > >referring to it only by 'open story submission queue plugin,' no further > >explanation needed. > > Well, now you are publcially asking for comments, and further explanation > is needed. > > -- > Chris Nandor pu...@po... http://pudge.net/ > Open Source Development Network pu...@os... http://osdn.com/ > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development > |
|
From: elijah w. <el...@st...> - 2000-12-09 17:42:35
|
> Further explanation is needed by you, apparently, but with all do respect, > you don't speak for everyone. As I've already stated, I've spoken with you need to explain in detail the way in which your story submission queue plugin works. you have NOT explained it in any reasnoable sense, other than saying that it will exist. chris is right, it *does* merit explanation. even for those of us who have a vague sense of what you are doing- we'd like to make sure that you are on the 'right path' and aren't wasting your time on something that's going to be blatantly useless to everyone else :) so please do explain it instead of being hostile to nandor... thanks. elijah |
|
From: CertIndex.com W. <web...@ce...> - 2000-12-09 18:00:54
|
First of all, I was not hostile towards him, you'll see I took the time to interact with him 4 or 5 times. Don't get huffy with me because I don't agree with Chris, that's irrational and immature. Politics are not appreciated nor welcome. " you need to explain in detail the way in which your story submission queue plugin works. " Once again, how do you expect me to detail exactly HOW it works when we haven't even finished decided WHAT all it will do? What it will do would be done if we were not taking the time, regrettably, to ask others for what they would like to see in it so we can use OUR time to make this more useful for other people. If we did not do this, and the 'what' part was done, I wouldn't even be mailing the list because there would be no point. Look this is a very simple concept. We will be developing an open submission queue plugin for Slash. Email me everything you would like to see in it and THEN we will come back with a final RFC on final feature set, logic, and *implementation*. I don't understand why What (Business logic) and How (Technical logic) are such confusing concepts to most techies. I will not further clarify this. Not only is the horse beaten, but the very molecules it is made of are so strained it's cm's from vapourising. I'm ready and eager to get down to code. Ciao, k ----- Original Message ----- From: "elijah wright" <el...@st...> To: <sla...@li...> Sent: Saturday, December 09, 2000 9:52 AM Subject: Re: [Slashcode-development] RFC for Open Story Submission Queue plugin > > > Further explanation is needed by you, apparently, but with all do respect, > > you don't speak for everyone. As I've already stated, I've spoken with > > you need to explain in detail the way in which your story submission queue > plugin works. you have NOT explained it in any reasnoable sense, other > than saying that it will exist. chris is right, it *does* merit > explanation. even for those of us who have a vague sense of what you are > doing- we'd like to make sure that you are on the 'right path' and aren't > wasting your time on something that's going to be blatantly useless to > everyone else :) > > so please do explain it instead of being hostile to nandor... thanks. > > elijah > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development > |
|
From: elijah w. <el...@st...> - 2000-12-09 19:12:01
|
> First of all, I was not hostile towards him, you'll see I took the time to > interact with him 4 or 5 times. Don't get huffy with me because I don't > agree with Chris, that's irrational and immature. Politics are not > appreciated nor welcome. be extremely careful when you use rhetoric like "even you"- it pisses a large number of people off and is not the best PR :) anyway, point taken. please don't name-call, though. > Once again, how do you expect me to detail exactly HOW it works when we > haven't even finished decided WHAT all it will do? What it will do would be > done if we were not taking the time, regrettably, to ask others for what i am asking what your vision of it thus far is. otherwise you're really not doing anything more than asking the community to define your project goals for you in their entirety. that's the hard part. not the code. :) > Look this is a very simple concept. We will be developing an open submission > queue plugin for Slash. Email me everything you would like to see in it and > THEN we will come back with a final RFC on final feature set, logic, and > *implementation*. that's not such a simple concept when you have provided next to no information on what your planned stance is. do you have one? at all? don't ask people who read your message to waste their time coming up with a feature set critique unless you already have one in mind as a basis. and the story submission queue concept isn't simple. doing a one-shot implementation is "easy", doing one that works will be harder. > I don't understand why What (Business logic) and How (Technical logic) are > such confusing concepts to most techies. they aren't. but you haven't provided this list with either. i'm asking you to be rhetorically clear and provide a clear picture of what it is that you're asking, the basis for your assumptions, your ideas thus far, and your envisioned goal. in the absence of that, however, here are some ideas: * submission method modularization (email, http, nntp linkages) * administrative override (so that the trolls don't mod up a story as a prank) * settable limits on the speed with which a story can be modded up before an automated mechanism decides a bot is doing the modding; logging of accounts used in this fashion * graphing of story-submitters and frequency (libgd-perl is your friend) * a configurable point system that can handle multiple levels of users, differing moderation values, and various point assignments from each. * the ability to assign different point values to different categories- something may deserve +5 points from a newbie if posted to a "tech" section, +8 points from a recognized "strong-supporter-or-friend-of-admin, but only 3 points from a newbie in "politics" and 5 from the aforementioned strong supporter. this puts responsibility for categorization in the hands of the users. i'd like to see dropdown javascript boxes (or whatever) allowing the story submitter to give the top 3 categories they see fitting and their point values. form submit boxes with regex/match-parsing would work just as well. * RDF / RSS exports of the story submission queues * items in queue web-accessible via some means other than the story moderation page- i'd like to be able to get to a raw dump of the stories. i don't really care how- NNTP or mysql or postgres with a simple page that just dumps the data would be fine. of course, that page will need controls on how quickly it can be dumped- perhaps the perl script responsible for that can log accesses from IP's and slow itself down accordingly? * a weird idea i just had- what if slashcode could parse in the rdf/rss headlines from other sites and include THOSE into the story submission queue? it might not be such a bad idea to be able to choose to see headlines frmo other relevant sites in a one-shot format, rather than the full-on slash frontpage format. working on flexibility here rather than what most people would want... ~elijah |
|
From: Eric D. <eri...@ja...> - 2000-12-09 19:29:00
|
> > in the absence of that, however, here are some ideas: > > * submission method modularization (email, http, nntp linkages) Um, email submission might be a cool idea.... > > * administrative override (so that the trolls don't mod up a story as a > prank) Great idea > > * settable limits on the speed with which a story can be modded up before > an automated mechanism decides a bot is doing the modding; logging > of accounts used in this fashion Is that really a problem? I think the logging of story moderations by users is a good idea. > > * graphing of story-submitters and frequency (libgd-perl is your friend) Hmm.........another good idea > > * a configurable point system that can handle multiple levels of users, > differing moderation values, and various point assignments from each. Again, great idea > > * the ability to assign different point values to different categories- > something may deserve +5 points from a newbie if posted to a > "tech" section, +8 points from a recognized > "strong-supporter-or-friend-of-admin, but only 3 points from a newbie in > "politics" and 5 from the aforementioned strong supporter. this puts > responsibility for categorization in the hands of the users. i'd like > to see dropdown javascript boxes (or whatever) allowing the story > submitter to give the top 3 categories they see fitting and their point > values. form submit boxes with regex/match-parsing would work just as > well. > * RDF / RSS exports of the story submission queues > * items in queue web-accessible via some means other than the story > moderation page- i'd like to be able to get to a raw dump of the > stories. i don't really care how- NNTP or mysql or postgres with a > simple page that just dumps the data would be fine. of course, that > page will need controls on how quickly it can be dumped- perhaps the > perl script responsible for that can log accesses from IP's and slow > itself down accordingly? > * a weird idea i just had- what if slashcode could parse in the rdf/rss > headlines from other sites and include THOSE into the story submission > queue? it might not be such a bad idea to be able to choose to see > headlines frmo other relevant sites in a one-shot format, rather than > the full-on slash frontpage format. working on flexibility here rather > than what most people would want... I don't know about these others, but one thing I'd like to see or perhaps hack out one of these days, is that if you submit a story to a section that has extra data, say, book reviews, the user can enter those data fields when doing the original post. Right now in Slash 1.0.9 I think you can only enter those fields while in the Admin area..... |
|
From: elijah w. <el...@st...> - 2000-12-09 22:18:59
|
> > in the absence of that, however, here are some ideas: > > * submission method modularization (email, http, nntp linkages) > Um, email submission might be a cool idea.... now that i am not rushing to take garbage to the trash dump (i'm at my parent's house for the holidays and their garbageman doesn't like large non-household-trash like Dell boxes... what i really had in mind wrt nntp was the ability to accept story submissions via newsgroup crossposting. basically, to make it really easy to tie a web frontend to a newsgroup and have selected things migrate out of the NNTP backend and into the mysql||postgres db. it might be just as productive if someone wrote an NNTP+LDAP backend to run alongside slash... but i'm not volunteering for that :) > > * administrative override (so that the trolls don't mod up a story as a > > prank) > Great idea thanks. next clarification: i'd like to have the administratievly overridden entries stashed somewhere that the users can still get at them if they want. obviously there's likely to be a huge mess of such posts; perhaps use a configurable threshold of space wasted by natalie portman and grits posts? 10mb or 2500 posts sound like a reasonable backlog? or is that too much? (10MB is peanuts these days, imho...) it'll take a hell of a long time before anyone comes close to that with a smallish site :) > > * settable limits on the speed with which a story can be modded up before > > an automated mechanism decides a bot is doing the modding; logging > > of accounts used in this fashion > > Is that really a problem? I think the logging of story moderations by users is a > good idea. well, botted posts hit kuro5hin pretty hard last summer. that was sad. if story-moderations are not random-selection based (like the slashdot comment modding) then there needs to be a facility to make sure that an individual doesn't multiply moderate the story in the queue. i personally think it'd be pretty cool to be able to go to the story queue page, see what's there (as a logged in user, probably) and then vote up everything i thought was worth seeing. another brief idea- maybe story moderation is something that some admins might want to restrict to either logged in users or a subset usergroup. that probably needs to be settable with little trouble. slashdot, having an established troll community, probably wouldn't be able to do mass-open-moderation on its story queue. other sites might, though. authenticated users should always be weighted more heavily than anonymous users, imho. maybe that threshold needs to be an algorithm with a tunable constant for teh difference. set it to zero to turn it off, perhaps? how about a moderate-up-a-random-story button that selects from the stories with at least minimum_number of positive votes? :) > > * graphing of story-submitters and frequency (libgd-perl is your friend) > Hmm.........another good idea someone could probably gut MRTG or simply rig it up to do this. that might be a good project even outside of the concept of the story moderation queue. it'd be a nice bolt-on. [a side-thought; i'm only subscribed to this one list. should i be brainstorming somewhere else? or is this a tolerable place for that?] > I don't know about these others, but one thing I'd like to see or > perhaps hack out one of these days, is that if you submit a story to a > section that has extra data, say, book reviews, the user can enter > those data fields when doing the original post. Right now in Slash > 1.0.9 I think you can only enter those fields while in the Admin > area..... i think that's a really cool idea. and i appreciate your positive feedback on my ranting from earlier this afternoon :) i really like slashdot but i need it to do some more stuff.... *grin* i eventually want to use it as a discussion forum for my students, but it needs a bit more fine-grained tuning before it'll serve as i like :) is that extra data stuff something that could be done template-style? is there a forum where people post things they'd eventually like to see a slash-like system do? i occasionally have a wacky plugin idea or something and it'd be nice to be able to do something with it other than just sit on it and hope i get un-busy eventually.. ~elijah |
|
From: Eric D. <eri...@ja...> - 2000-12-10 02:46:56
|
elijah wright wrote: > what i really had in mind wrt nntp was the ability to accept story > submissions via newsgroup crossposting. basically, to make it really easy > to tie a web frontend to a newsgroup and have selected things migrate out > of the NNTP backend and into the mysql||postgres db. it might be just as > productive if someone wrote an NNTP+LDAP backend to run alongside slash... > but i'm not volunteering for that :) > Yeah, I don't know about that. Kinda seems redundant in my opinion. I really would not like to see my slash site spammed with all that Usenet crap that gets posted (IE: Porn and stuff) > thanks. next clarification: i'd like to have the administratievly > overridden entries stashed somewhere that the users can still get at them > if they want. obviously there's likely to be a huge mess of such posts; > perhaps use a configurable threshold of space wasted by natalie portman > and grits posts? 10mb or 2500 posts sound like a reasonable backlog? or > is that too much? (10MB is peanuts these days, imho...) it'll take a > hell of a long time before anyone comes close to that with a smallish site > :) Do you mean like filtering out comments by certain posters? Is that what your getting at? That might be an idea, or perhaps being able to filter out Trolls and stuff would be good too. Of course, that would only be available for articles that haven't been dumped out of the database yet (IE: still able to comment on). I know there are times I'd like to filter out some of the crap in comments to get to the meat. Like a lot of the stuff on Slashdot lately has been unrelated to the articles, especially the 20-30 first post people...... > well, botted posts hit kuro5hin pretty hard last summer. that was sad. > > if story-moderations are not random-selection based (like the slashdot > comment modding) then there needs to be a facility to make sure that an > individual doesn't multiply moderate the story in the queue. i personally > think it'd be pretty cool to be able to go to the story queue page, see > what's there (as a logged in user, probably) and then vote up everything i > thought was worth seeing. > > another brief idea- maybe story moderation is something that some admins > might want to restrict to either logged in users or a subset > usergroup. that probably needs to be settable with little > trouble. slashdot, having an established troll community, probably > wouldn't be able to do mass-open-moderation on its story queue. other > sites might, though. > > authenticated users should always be weighted more heavily than anonymous > users, imho. maybe that threshold needs to be an algorithm with a tunable > constant for teh difference. set it to zero to turn it off, perhaps? > > how about a moderate-up-a-random-story button that selects from the > stories with at least minimum_number of positive votes? :) > Yeah, well, I kinda like the idea of the stories I see are "human" approved. Kind of organizes the discussions. I'm a little confused as to why you'd want that........seems a lot of work for something that might not really be all that useful....... > i think that's a really cool idea. and i appreciate your positive > feedback on my ranting from earlier this afternoon :) i really like > slashdot but i need it to do some more stuff.... *grin* i eventually > want to use it as a discussion forum for my students, but it needs a bit > more fine-grained tuning before it'll serve as i like :) > Well, when this "Bender" thing is more stable I'd love to add some stuff to it, but right now........I'm scared. I like my 1.0.9 setup, and I've tweaked it, and am going to tweak it a little more to do the submission thing I mentioned. > is that extra data stuff something that could be done template-style? I don't think so. Doesn't look like it. It seems fairly easy to do. I just need to sit down and do it......... > is there a forum where people post things they'd eventually like to see a > slash-like system do? i occasionally have a wacky plugin idea or > something and it'd be nice to be able to do something with it other than > just sit on it and hope i get un-busy eventually.. Perhaps someone should write a PLUGIN WISH LIST or something on slashcode so people can write what they'd like to see Bender do......... |
|
From: elijah w. <el...@st...> - 2000-12-10 03:01:24
|
> Yeah, I don't know about that. Kinda seems redundant in my opinion. I > really would not like to see my slash site spammed with all that > Usenet crap that gets posted (IE: Porn and stuff) yeah. its pretty easy to set up a private group, though... for larger orgs hosting many smaller groups under their umbrella, though (like universities; mine already has listservs on a per-course basis and everything stored in LDAP campus-wide...) this kind of yummy goodness makes a solution very efficient and appealing :) > Do you mean like filtering out comments by certain posters? Is that > what your getting at? That might be an idea, or perhaps being able to > filter out Trolls and stuff would be good too. Of course, that would > only be available for articles that haven't been dumped out of the > database yet (IE: still able to comment on). not what i meant, but its a good idea :) * let the user establish regexes for articles that automatically get dumped. killfiles, basically. i was more or less suggesting a clicky-box to dump an article into a different queue as inappropriate. > I know there are times I'd like to filter out some of the crap in > comments to get to the meat. Like a lot of the stuff on Slashdot > lately has been unrelated to the articles, especially the 20-30 first > post people...... i hate those :) (sometimes i think anything with ' fp' anywhere in it should get sh*tcanned... i can't think of any words in english with that string in them..) > > how about a moderate-up-a-random-story button that selects from the > > stories with at least minimum_number of positive votes? :) > > Yeah, well, I kinda like the idea of the stories I see are "human" > approved. Kind of organizes the discussions. yep :) > I'm a little confused as to why you'd want that........seems a lot of > work for something that might not really be all that useful....... oh, the random story approval button was just a whiz-bang idea that might be kind of cute- i wasn't taking it seriously :) > Well, when this "Bender" thing is more stable I'd love to add some > stuff to it, but right now........I'm scared. I like my 1.0.9 setup, > and I've tweaked it, and am going to tweak it a little more to do the > submission thing I mentioned. hehehehehehe :) > Perhaps someone should write a PLUGIN WISH LIST or something on > slashcode so people can write what they'd like to see Bender > do......... if someone would just post a story with that as the title so we can muckity-muck around in a thread there? * plugin idea: i want to see a plugin/system implemented where i can get posts to a thread via email or via digests at regular intervals/size increments ~elijah |
|
From: Brian A. <br...@ta...> - 2000-12-10 05:49:45
|
elijah wright wrote: > [a side-thought; i'm only subscribed to this one list. should i be > brainstorming somewhere else? or is this a tolerable place for that?] That is exactly what this list is for. > feedback on my ranting from earlier this afternoon :) i really like > slashdot but i need it to do some more stuff.... *grin* i eventually > want to use it as a discussion forum for my students, but it needs a bit > more fine-grained tuning before it'll serve as i like :) In my list of plugins, Malda has a request in for discussions that are not linked to stories. What features were you looking for? Somewhere also in my list is a comment plugin that is not linked to stories. > is there a forum where people post things they'd eventually like to see a > slash-like system do? i occasionally have a wacky plugin idea or > something and it'd be nice to be able to do something with it other than > just sit on it and hope i get un-busy eventually.. This is the place for bringing up plugins. When I get a chance I will be putting up a plugin registry on slashcode.com. -Brian |
|
From: Patrick G. <cap...@sl...> - 2000-12-10 17:21:49
|
Brian Aker wrote: > elijah wright wrote: > > [a side-thought; i'm only subscribed to this one list. should i be > > brainstorming somewhere else? or is this a tolerable place for that?] > That is exactly what this list is for. > > > feedback on my ranting from earlier this afternoon :) i really like > > slashdot but i need it to do some more stuff.... *grin* i eventually > > want to use it as a discussion forum for my students, but it needs a bit > > more fine-grained tuning before it'll serve as i like :) I don't think the stories being posted based upon users "moderating" or "voting" the story as being visible will necessarily necessitate a plugin. Well, if one were to make submissions a plugin, and modify it to allow some sort of voting of approval. I'm not sure. This needs to be explained in further detail though, as it involves the story submission process, moderation, and abuse protection (as well as other things I'm not even considering). If something like this is to happen, it'd be best to make use of the people on this list to perhaps come up with ideas for implementing this feature. I would however like to say that we're trying to get bender released, and right now we're in the stage of bug and performance testing, and any additional features should wait until the code is released. I'm also not sure if this feature is being thought of as being implemented with MAIN or Bender. If anything like this is to happen, it should be based upon Bender, as that's the codebase that will accomodate any sort of plugins or modifications, as that will soon be the current codebase within a month or so. > > In my list of plugins, Malda has a request in for discussions that > are not linked to stories. What features were you looking for? > Somewhere also in my list is a comment plugin that is not linked > to stories. > This is already the case in the current codebase. You just have to create a discussion by going to comments.pl with a "made-up" sid, that discussion is then created, which is then listed in a full list of current discussions which can be viewed upon loading comments.pl without an sid. Maybe I'm not thinking about the same thing. :) > > > is there a forum where people post things they'd eventually like to see a > > slash-like system do? i occasionally have a wacky plugin idea or > > something and it'd be nice to be able to do something with it other than > > just sit on it and hope i get un-busy eventually.. > This is the place for bringing up plugins. When I get a chance I will be > putting up a plugin registry on slashcode.com. > > -Brian > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development -- Patrick Galbraith Open Source Development Network Senior Software Developer 50 Nagog Park Slash Code Development Team Acton, MA 01720 "Energy and Persistence conquer all things". Benjamin Franklin |
|
From: Jason R. <ja...@ar...> - 2000-12-09 19:20:25
|
How about this: If you receive no responses on you RFC, what will this thing do? We have nothing to comment on. CertIndex.com Webmaster wrote: > First of all, I was not hostile towards him, you'll see I took the time to > interact with him 4 or 5 times. Don't get huffy with me because I don't > agree with Chris, that's irrational and immature. Politics are not > appreciated nor welcome. > > " you need to explain in detail the way in which your story submission queue > plugin works. " > > Once again, how do you expect me to detail exactly HOW it works when we > haven't even finished decided WHAT all it will do? What it will do would be > done if we were not taking the time, regrettably, to ask others for what > they would like to see in it so we can use OUR time to make this more useful > for other people. If we did not do this, and the 'what' part was done, I > wouldn't even be mailing the list because there would be no point. > > Look this is a very simple concept. We will be developing an open submission > queue plugin for Slash. Email me everything you would like to see in it and > THEN we will come back with a final RFC on final feature set, logic, and > *implementation*. > > I don't understand why What (Business logic) and How (Technical logic) are > such confusing concepts to most techies. > > I will not further clarify this. Not only is the horse beaten, but the very > molecules it is made of are so strained it's cm's from vapourising. I'm > ready and eager to get down to code. > > Ciao, > k > > ----- Original Message ----- > From: "elijah wright" <el...@st...> > To: <sla...@li...> > Sent: Saturday, December 09, 2000 9:52 AM > Subject: Re: [Slashcode-development] RFC for Open Story Submission Queue > plugin > > > > > > > Further explanation is needed by you, apparently, but with all do > respect, > > > you don't speak for everyone. As I've already stated, I've spoken with > > > > you need to explain in detail the way in which your story submission queue > > plugin works. you have NOT explained it in any reasnoable sense, other > > than saying that it will exist. chris is right, it *does* merit > > explanation. even for those of us who have a vague sense of what you are > > doing- we'd like to make sure that you are on the 'right path' and aren't > > wasting your time on something that's going to be blatantly useless to > > everyone else :) > > > > so please do explain it instead of being hostile to nandor... thanks. > > > > elijah > > > > _______________________________________________ > > Slashcode-development mailing list > > Sla...@li... > > http://lists.sourceforge.net/mailman/listinfo/slashcode-development > > > > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > http://lists.sourceforge.net/mailman/listinfo/slashcode-development -- "Jason C. Richey" <ja...@ar...> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X