Menu
▾
▴
Re: [Slashcode-general] Renaming the fork of Slashcode
|
From: George T. <geo...@gm...> - 2011-02-09 08:17:21
|
When everyone involved with Slashdot, up to and including the founder, says it's time to fork the project, I think that answers my question and makes our course clear. Rob, I'm glad you spoke up. I want to tell you personally that I think the value of Slash as a tool for civil discussion has been underestimated by pretty much everyone. I've spent more than my share of time in public meetings. Generally, the worse the chair of the meeting is, the more the meeting is likely to suck. The less the assembled stick to an agenda duly compiled, the more the meeting is likely to take forever. The less willing the assembled are to submit to an equal limit on the number of times and the amount of time speakers may speak, the more the meeting is likely to end in insults, hurt feelings and nothing accomplished. That goes for online "meetings," too. The first time I got online, in 1983, I joined a discussion and immediately got into a flame war. I still occasionally found myself doing so twenty years later. Most newspaper sites have terribly moderated comment sections. Those that have good ones are labor-intensive; moderation requires moderators. Slashdot found the right formula for having a civil discussion online: let everyone moderate...but "in moderation," rendered automatically and meta-moderated to minimize human bias error. That you released the code open-source at all is our good fortune. That it wasn't clear to others how to use it, or to you and yours how to package it so that they would, does not diminish the achievement. I for one am ready to implement it as is (...as long as I can get it installed; we'll see in the next few days ;-). I think I can speak for a few people when I say we're looking forward to trying to put Slash into contexts where more people can benefit from the civil discussions that it can enable. It would be great if you were to keep checking in with us, and lending moral support if nothing else, as we try. All right. Fork it. == George On Tue, Feb 8, 2011 at 4:58 PM, Rob Malda <ma...@sl...> wrote: > First, let me state that I originated Slashcode and Slashdot. I also > managed our engineering team for a decade or so. These days I run the > editorial group, which is already which doesn't write code of any type > ;) So while I have meetings with people who are responsible for these > things, they don't report to me and I can't boss them around. > > I think it probably would be better if a new name was picked that > implied legacy. I believe (although I could be wrong on this) that > trademarks might have actually been made at some point in the lifespan > of the project. I could be wrong, but I'd rather not have any > complication or confusion on anyone's part. > > I'd love to see you guys do something great. For Slashdot anyway, > releasing the code was always a cool side project, but we never got > contributions back enough to justify the engineering man hours we put > into the public releases. From a journalism & freedom of information > perspective, I loved seeing sites based on our system pop up. But you > can't put that into a budget... > > If the fork managed to produce useful patches, that might convince > people to get a new version on our end out so we could get exciting > new awesome features on Slashdot too. But I suspect it would take > some significant stuff to make that something that would be seriously > considered. > > > > On Tue, Feb 8, 2011 at 4:17 PM, Alexandre Leroux > <ale...@ec...> wrote: >> >> I think the point is instead of 'forking and renaming' slashcode, would >> be to just update slashcode and continue to use its name. If former >> developers agrees of course (why wouldn't they?). >> >> good luck - >> >> Alex >> -- >> Alexandre Leroux, M.Sc., ing. >> Section de la réponse aux urgences environnementales / >> Environmental Emergency Response Section >> Centre météorologique canadien / Canadian Meteorological Centre >> Environnement Canada / Environment Canada >> ale...@ec... - (514) 421-5024 >> >> >> On 02/08/11 16:13, Marc G. Fournier wrote: >>> But, that is what we are doing ... forking hte project, and workingot >>> re-vitalize it ... once we get the initial infrastructure in place, we'll >>> do an announce to this list, and make a request to Jamie et al to put >>> something on the main page of the slashcode web site pointing ppl to the >>> new site ... >>> >>> On Tue, 8 Feb 2011, George Taft wrote: >>> >>>> Well, after sleeping on it, I have a new thought. >>>> >>>> To date, "Slash" has been the Software. "Slashcode" has been the >>>> "Slash Open Source Project," as the site at slashcode.com calls >>>> itself. >>>> >>>> The Software, those of us still here agree, has utility and is worth >>>> continuing to develop. But users have almost all drifted away because >>>> the Project has suffered from a profound lack of attention. That would >>>> be because those of us still here all but do not include the Slashdot >>>> team, who greatly reduced their priority to the Project in favor of >>>> Slashdot itself. >>>> >>>> I notice that Chris Nandor, the last person to post an article at >>>> slashcode.com, <a >>>> href="http://use.perl.org/~pudge/journal/40493">stopped working for >>>> Slashdot/GeekNet as of 2010Q4.</a> He put the use.perl.org site on >>>> hiatus before he quit. I'm betting that he no longer considers >>>> Slashcode a priority, either. Jamie McCarthy, the second-to-last to >>>> post an article, works for GeekNet but not Slashdot. (Jamie has >>>> contacted us with words of encouragement.) >>>> >>>> All this begs the question: why have we not asked the Slashdot team if >>>> they wouldn't mind if someone else took over altogether the "Slash >>>> Open Source Project" that is slashcode.com? >>>> >>>> == George >>>> >>>> >>>> >>>> On Tue, Feb 8, 2011 at 10:18 AM, Marc G. Fournier <sc...@hu...> wrote: >>>>> On Tue, 8 Feb 2011, Andre-John Mas wrote: >>>>> >>>>>> Or a small variation: >>>>>> >>>>>> SlashCode-NG >>>>> I could go for that one ... any nay's on that? >>>>> >>>>> >>>>>> On 8-Feb-2011, at 10:07, Marc G. Fournier wrote: >>>>>> >>>>>>> Cute :) >>>>>>> >>>>>>> None of them *really* ring though, now do they? :) >>>>>>> >>>>>>> Just so that we don't get hung up on a name and never actually move >>>>>>> forward with the critical stuff, u nless anyone has something that >>>>>>> *rings* >>>>>>> to put forward, does anyone have any disagreements with just going with: >>>>>>> >>>>>>> SlashTNG >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, 7 Feb 2011, George Taft wrote: >>>>>>> >>>>>>>> Oh, I love this thread. I like Backslash and Solidus. I came up with: >>>>>>>> >>>>>>>> Slashback >>>>>>>> Slasher >>>>>>>> Slashout >>>>>>>> >>>>>>>> Slapdash >>>>>>>> StrikeThat >>>>>>>> >>>>>>>> SlashAndBurn >>>>>>>> SlashAndCarry >>>>>>>> SlashCut >>>>>>>> SlashedPotatoes >>>>>>>> SlashinthePan >>>>>>>> >>>>>>>> Things that slash: >>>>>>>> -- pirates; swashbucklers >>>>>>>> -- a spare in bowling >>>>>>>> -- a slash is a stroke; stricken; struck >>>>>>>> >>>>>>>> == George >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Feb 7, 2011 at 6:34 PM, Marc G. Fournier <sc...@hu...> >>>>>>>> wrote: >>>>>>>>> As far as domains are concerned, both are already taken ... :( >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, 7 Feb 2011, Larson, Timothy E. wrote: >>>>>>>>> >>>>>>>>>>> 'k, since SlashCode belongs to the Slashdot folks, we need to rename >>>>>>>>>>> th >>>>>>>>>>> efork ot someting different ... I want like to somehow keep some sort >>>>>>>>>>> of >>>>>>>>>>> 'history in the name' ... anyone got better then SlashTNG? PortalSC >>>>>>>>>>> (SC >>>>>>>>>>> == Slashcode)? Something better ... ? >>>>>>>>>> Backslash (Slash is back)? >>>>>>>>>> >>>>>>>>>> Solidus (the typography geek in me comes out)? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Tim >>>>>>>>>> -- >>>>>>>>>> Tim Larson >>>>>>>>>> App Admin, Intercall Production Services >>>>>>>>>> >>>>>>>>>> >>>>>>>>> ---- >>>>>>>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>>>>>>>> sc...@hu... http://www.hub.org >>>>>>>>> >>>>>>>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio >>>>>>>> XE: >>>>>>>> Pinpoint memory and threading errors before they happen. >>>>>>>> Find and fix more than 250 security defects in the development cycle. >>>>>>>> Locate bottlenecks in serial and parallel code that limit performance. >>>>>>>> http://p.sf.net/sfu/intel-dev2devfeb >>>>>>>> _______________________________________________ >>>>>>>> Slashcode-general mailing list >>>>>>>> Sla...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/slashcode-general >>>>>>>> >>>>>>> ---- >>>>>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>>>>>> sc...@hu... http://www.hub.org >>>>>>> >>>>>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>>>>>> Pinpoint memory and threading errors before they happen. >>>>>>> Find and fix more than 250 security defects in the development cycle. >>>>>>> Locate bottlenecks in serial and parallel code that limit performance. >>>>>>> http://p.sf.net/sfu/intel-dev2devfeb >>>>>>> _______________________________________________ >>>>>>> Slashcode-general mailing list >>>>>>> Sla...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/slashcode-general >>>>>>> >>>>>> >>>>> ---- >>>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>>>> sc...@hu... http://www.hub.org >>>>> >>>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>>>> >>>> ------------------------------------------------------------------------------ >>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>>> Pinpoint memory and threading errors before they happen. >>>> Find and fix more than 250 security defects in the development cycle. >>>> Locate bottlenecks in serial and parallel code that limit performance. >>>> http://p.sf.net/sfu/intel-dev2devfeb >>>> _______________________________________________ >>>> Slashcode-general mailing list >>>> Sla...@li... >>>> https://lists.sourceforge.net/lists/listinfo/slashcode-general >>>> >>> >>> ---- >>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>> sc...@hu... http://www.hub.org >>> >>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> Slashcode-general mailing list >>> Sla...@li... >>> https://lists.sourceforge.net/lists/listinfo/slashcode-general >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Slashcode-general mailing list >> Sla...@li... >> https://lists.sourceforge.net/lists/listinfo/slashcode-general >> > > > > -- > Pants are Optional > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > |
