Topic: New Modsite Ideas :D (Read 75751 times)

Charles Kingsley · « **Reply #25 on:** April 23, 2009, 09:17:42 AM »

Adding anope versions is a dirty hack yes

Yeah, think it rhymed with crash?

Andrew B. · « **Reply #26 on:** April 23, 2009, 09:22:34 AM »

Maybe. Or did it rhyme with Hike.

Charles Kingsley · « **Reply #27 on:** April 23, 2009, 09:28:41 AM »

Amanda Folson · « **Reply #28 on:** April 23, 2009, 02:12:52 PM »

Yeah the color thing has come up before - But we had the idea of color coding them by type (bs/cs/etc) Or by trusted/non-trusted/broken...something along those lines. It could go a few ways. I like the idea of color coding nicks (like we do on here) to show who is what.

Amanda Folson · « **Reply #29 on:** April 23, 2009, 04:12:13 PM »

After some poking I found a thread that basically says Module Author requests will be denied unless someone can produce some work. I agree with this, however it might be nice to allow anyone to post modules (will still need to be approved) and make competent people module authors. We could give them the same rights as people in the contrib group. Thoughts?

Charles Kingsley · « **Reply #30 on:** April 23, 2009, 04:16:56 PM »

I think anyone should be able to share work without any privileges/etc as I see that level of collaboration key to the furthering of the provision. - However, the current fashion where people apply for author status before being able to upload is ridiculous thus as you say, I decline them all until they post a module on here or so which isn't ideal.

Contributor privileges are global we need to remember that and we should be careful with what we attach to them, but I do think we should maximise the idea of a Module Author group within LDAP which we can use once people have proved their worth or so....

More input is needed I think from more people; you all have a voice, use it.

Amanda Folson · « **Reply #31 on:** April 23, 2009, 04:21:22 PM »

I meant local privs - the contrib votes would hold more weight if we implemented a new voting system, but if we introduced this group they'd have the same rank as contribs maybe without all the perms. Wouldn't necessarily have to be an ldap thing. It just means we've seen they can probably make educated decisions on modules.

Charles Kingsley · « **Reply #32 on:** April 23, 2009, 04:23:23 PM »

I wonder whether a localised reputation system would be wise though or whether whatever we do should be carried over into other 'services'.

mooncup · « **Reply #33 on:** April 23, 2009, 04:25:08 PM »

I don't think things that are specific to one aspect of the site (ie module author privs) should necessarily be made global. Surely being an "official module author" or whatever shouldn't really affect your forum posts or bugzilla access. I think keeping the contributor status for people who are trusted and are not devs is a good idea - maybe the top module authors could be rewarded with contributor status, and module author could be kept local to the modules site.

Charles Kingsley · « **Reply #34 on:** April 23, 2009, 04:26:36 PM »

I'd think that if users are on here asking for help with modules it makes sense to identify fellow module authors?

mooncup · « **Reply #35 on:** April 23, 2009, 04:29:05 PM »

I suppose so, but we don't want to get to the stage where ldap contains a tonne of localised statuses that are only used by one part of the site.

For one, what happens if someone is a contributor /and/ module author?

Charles Kingsley · « **Reply #36 on:** April 23, 2009, 04:30:18 PM »

Highest rank prevails.

LDAP can handle more than a couple of groups easily so that's not a limitation beyond us making something messy perhaps down the line.

mooncup · « **Reply #37 on:** April 23, 2009, 04:31:13 PM »

Well then we probably need to decide what ranks we're going to have and the order the ranking will go in.

Charles Kingsley · « **Reply #38 on:** April 23, 2009, 04:33:01 PM »

Low on the list of priorities I'd say besides if we're clever the ldap backend can hold more than 1 role and depending upon the tertiary service pull in a relevant (replicated if needed) group.

eg. You could be a module author and a bugzilla helper which could be two "usergroups" where group0 is pulled by the forum and group1 pulled by bugzilla where if null it pulls group0.

Theory is there, just depends upon what we actually want to set out to achieve.

mooncup · « **Reply #39 on:** April 23, 2009, 04:37:31 PM »

Ok then.

* mooncup readies his if functions.

I actually wonder if we could add a rank field to the ldap groups, which would make all the code at this end faster and prettier :3

Charles Kingsley · « **Reply #40 on:** April 23, 2009, 04:39:43 PM »

Not saying whether that's a good way of doing it or not mate, depends what we want to set out and achieve.

I think the basis is to try and make some love with the modsite; we need to look at what module users want and ofc what the author wants.

Charles Kingsley · « **Reply #41 on:** April 23, 2009, 04:43:45 PM »

<Fersure> chaz: Would it be possible to have decent version control for modules? i.e.: svn or git?

How could we authenticate this against ldap?

Charles Kingsley · « **Reply #42 on:** April 23, 2009, 04:45:56 PM »

<zomg> mmm, dont really like the svn thing
<zomg> People might start usin us to host any old crap
<mooncup> But also a nice idea
<chaz> not if we restrict it
<mooncup> nah zomg
<chaz> ie, the repos is created in the name of the module.
<mooncup> make people register with ldap first
<chaz> or whether we can control a repos for module author with subdirs for the module.
<chaz> potential is there.
<chaz> mind you though; it's a tricky one to implement.
<DukePyrolator> \o/
<zomg> Yeah but thats to stop me from putting anope2 under ircd_tssync

<zomg> what*

Charles Kingsley · « **Reply #43 on:** April 23, 2009, 04:46:15 PM »

Scratch that, pain in the ass to maintain.

mooncup · « **Reply #44 on:** April 23, 2009, 04:46:20 PM »

I don't know what protocols svn uses etc, but if it's http I think we could have a php script that parses it and sends it to ldap, then adds it to the svn. Though all svns would show from the script's ip not the user's.

Amanda Folson · « **Reply #45 on:** April 23, 2009, 04:50:58 PM »

Getting it on there isnt an issue, securing it is. How do you stop me from hosting Another project on there very quietly without watching EVERY commit.

Charles Kingsley · « **Reply #46 on:** April 23, 2009, 04:52:38 PM »

<chaz> decent controls from our end.
<zomg> Yeah, but as you said itd be a pain in the ass
<mooncup> as long as we moderated it well
<mooncup> chaz: you made 2 posts in under 20 seconds.
<chaz> =)
<DukePyrolator> hehe
<mooncup> ew forum
<mooncup> I think this svn idea is a goodun
<mooncup> but needs work
<mooncup> tell me about svn plz
<mooncup> like, the protocol
<chaz> google?

<mooncup> >_>
<zomg> I just cant think of any good way to limit what people add to it
<mooncup> http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_svn/protocol
<mooncup> >:3
<mooncup> zomg: moderation
<mooncup> remove shit
<mooncup> basically
<chaz> easy.
<chaz> limit each author to 1meg

<mooncup> http://uk2.php.net/svn
<mooncup> there is a php svn api
<chaz> enforce a naming convention or something to further restrict t the idea.
<mooncup> but I think I'd basically be coding an entire svn client
<chaz> who knows.
<chaz> we need foundations tbh.
<mooncup> just to post other people's svns
<mooncup> unless I could pass on the raw data after authenticating
<chaz> far easier to increment version numbers automatically for people when they upload something.
<mooncup> The alternative (better way) would be to mod the svn server
<mooncup> so that it auths using ldap
<chaz> makes you wonder why you bother with svn at that point
<chaz> unless we can make it work from command line its fruitless.
<zomg> Put it on the forummmmmmm that way I dont have to log this

Amanda Folson · « **Reply #47 on:** April 23, 2009, 04:58:05 PM »

mooncup · « **Reply #48 on:** April 23, 2009, 05:03:09 PM »

http://blogs.open.collab.net/svn/2009/03/subversion-with-apache-and-ldap-updated.html

This would be better than doing it clientside methinks.

Amanda Folson · « **Reply #49 on:** April 23, 2009, 06:06:55 PM »

I'm still not sure SVN is the way to go. Honestly the current system works - we just need to change the tables and backend code a little bit in order to have 1) Two modules with the same name 2) Multiple modules with different versions at the same time. The modsite does indeed store all of the old versions as well. We just need to show them.

News:

Author Topic: New Modsite Ideas :D (Read 75751 times)