pbw wrote: > On Wednesday 15 March 2006 18:55, randy wrote: >> On Wed, March 15, 2006 3:03 pm, Matthew G wrote: >>> I'm totally against this. I think this is a really shitty idea. I >>> never liked vbulltin and I will never like it. If we really wanted to >>> share logins people would modify the source and do so. flyspry is >>> great, the wiki is great, and phpbb is great. Leave it as it is! >> Wow. >> >> What we really need is some better parenting from Matthew's parents. >> Respect and manners go a long way in this world. Your post is rude (no to >> mention you top posted). >> >>> On 3/14/06, pbw <[EMAIL PROTECTED]> wrote: >>>> I forgot to mention there's also a pretty decent integrated bug tracker >>>> system. An example - >>>> http://www.vbulletin.com/forum/bugs35.php .And an easy to manage >>>> newsletter >>>> system as well. >>>> >>>> On Tuesday 14 March 2006 03:35, pbw wrote: >>>>> Hey everyone, lately i've been doing some thinking on how to improve >>>> the >>>> >>>>> website and integrating things as easily and best as possible. Before >>>> the >>>> >>>>> flames on this being commercial software begin, just hear me out. >>>>> >>>>> With minimal - no effort and hacking of the source code we can have >>>> these >>>> >>>>> features: >>>>> >>>>> - Single login/registration for everything below >>>>> - Announcements on front page piping automatically piping discussion >>>> to >>>> >>>>> it's own thread in specified forum >>>>> - Blogs >>>>> - Gallery >>>>> - shared login with mediawiki >>>>> - An improved AUR system, with an accurate way to gauge package useage >>>>> (which i'll describe and show below) >>>>> - Shop >>>>> - Donations system which displays in real time and adds user to a >>>> thank you >>>> >>>>> page (unless they choose to be anonymous) >>>>> - Forum system lightyears better than phpbb (current info and userbase >>>>> simple to import) >>>>> - Very powerful (and easy) administration/privelage system >>>>> - RSS Feeds on every Area you choose to have them for >>>>> - even our user map can be integrated with no effort >>>>> - mailing list threads piped to specified forum and vise versa >>>>> >>>>> What i'm proposing is vBulletin. An owned license (one time lifetime >>>> fee) >>>> >>>>> is only 160$, and i feel with the extra donations this is well worth >>>> it, in >>>> >>>>> pretty much every way i can think of. >>>>> >>>>> AUR system: >>>>> >>>>> It probably will be easiest to show by example, so here it is - >>>>> http://www.vbulletin.org/forum/showthread.php?s=&threadid=108515 . The >>>> best >>>> >>>>> feature this offers us (along of course with being centralized), is >>>> the way >>>> >>>>> the voting would work. Right now, i know i'm guilty, but i just get >>>> too >>>> >>>>> lazy and forget to always click to vote on a package i use. And also >>>> alot >>>> >>>>> of the time i stop using said package. >>>>> >>>>> With this system, you click install, when you have installed a >>>> package, the >>>> >>>>> contributor can see exactly who installed and who hasnt (Which is good >>>> as a >>>> >>>>> way to nudge people who post for support, yet havent clicked >>>>> install/voted). People will be much more likely to vote/click install >>>> a >>>> >>>>> package here, since doing so will enable them to be notified via email >>>>> every time the package is updated. and when they uninstall and no >>>> longer >>>> >>>>> wish to be notified of updates, they just click uninstall. >>>>> >>>>> I know currently we have the rss feed for the aur which does similar, >>>> but >>>> >>>>> afaik it only shows new packages and not updated ones?. Which can be a >>>> pain >>>> >>>>> to always check to stay up to date. >>>>> >>>>> Anyways, give it some thought. I've been using and hacking up vB for >>>> quite >>>> >>>>> some time, so if you guys have any questions on other areas, just ask. >>>> I'll >>>> >>>>> post this on the forum as well. Don't take this as a flame on the >>>> current >>>> >>>>> website efforts. I just feel this would make things easier to manage >>>> and >>>> >>>>> stay organized, and better for the end user for the same reason. >>>>> >>>>> >>>>> Thanks for making it through my novel, >>>>> >>>>> -- Chris O'Reilly >> As to the idea of consolidating apps into one. I'm not fond of this idea >> for the simple fact that if the main application breaks, it could >> potentially take down the entire system. Having separate apps for wiki, >> forum, bugs, et al just seems more reliable. Furthermore, I think that the >> user experience wouldn't benefit from such a system. People have grown >> accustomed to the way these specific apps work (Forums, WIKI, bug >> trackers). Putting them together in an app that was initially built for >> forums might confuse the user and then your site becomes a pain to >> navigate and use. Not because it's designed badly, but because of the >> expectations of the user. I know there's no standard on how a WIKI should >> act, but of the several popular ones out there today, they all >> look/feel/act similar enough to be intuitive to a user who has used one >> before. >> >> I do like the idea of single logins, but I've already got a gazillion >> login/passwds... what's a few more? It's an exercise in memory retention. >> >> Just my 2 cents... >> r. >> >> >> >> _______________________________________________ >> arch mailing list >> [email protected] >> http://www.archlinux.org/mailman/listinfo/arch > > Thanks for the response randy, perhaps i explained poorly though. It is still > the exact same mediawiki. What it does is handles wiki logins and signups > through the main website. > > How it works is a website user is created and can access forums, blogs and > such, the mediawiki account isnt actually created then, it's created when the > user first logs into the mediawiki. It just pulls the info from the vB userdb > and uses that as the registration process instead of the user manually going > through the process, as well as the user profile and options. The link to > signup for the wiki is just changed to point to the website signup. Which i > agree isnt a big deal to those already signed up, but for future people it's > kinda nice. > > (for my own site) I'm also looking into changing it so that when someone > clicks "discussion" on a wiki article, that it auto creates a thread in the > wiki forum on the topic. And if the thread has already been created then it > just forwards to it. It's pretty much finished, i've just been > distracted/busy lately and havent went live. We already have a wiki > discussion forum, so i figure this way makes it neater and more organized. Of > course that's just personal pref though. > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch >
With modern browsers such as Firefox able to remember logins to such websites is it really that big a deal anymore to have to sign up to each one? Why waste time implementing a single login system that could be better spent on Arch Linux itself? You shouldn't be using highly regarded passwords on websites anyway. Robert Stoffers -- Ubuntu - [EMAIL PROTECTED] Townsville Linux Users Group - http://tlug.dnho.net Freenode Support Staff - irc.freenode.net _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
