Administrator, Developer, Editor permissions
14 posts,
5 voices
96 posts
|
When creating a new user, it’s possible to select all of the options (Administrator, Developer, Editor) because they’re check boxes. Should these not be mutually exclusive and therefore radio buttons? Surely Administrator has all the privileges of Developer and Editor? This isn’t explained in the docs. Thanks. |
1493 posts
|
I think that’s right. It would be worth raising this as an issue, and surprised we haven’t already. :) Maybe that’s because Frog users are so clever they know only to choose one! ;)
Right again. I thought it was, but I see that’s still just the barest of essentials from Philippe’s early “wiki” documentation. In fact, there is more info on the Frog Wikipedia page! But this can be remedied. |
|
96 posts
|
Hi David, Sorry – just picked this up – I didn’t get email notification even though ‘Monitor topic’ is checked. I’ll go back and check my other threads. Thanks for the confirmation. Frog has a wiki?! I was just about to write a post suggesting one! It would be great if the site was updated so these things were prominent – especially from the forum view – I need to keep going back to home page to get to docs, etc. And the Google tracker is very hard to track down. Or do you mean http://en.wikipedia.org/wiki/Frog_CMS ? If so, I mean a wiki on this domain to enhance / replace the docs section. |
651 posts
|
@DavidONE – the main problem with having (or not having it) a wiki on madebyfrog.com is that only Philippe has access to the system which means we’re somewhat handicapped. All development related stuff is available on the google code site, including a wiki who’s main audience is the team working on Frog core. |
|
96 posts
|
I wasn’t sure how things were set up – whether their was a team or just Philippe. I guess we’re in trouble if Philippe is the only one with access to the system and he gets hit by a charging rhino one day. ;) Yeah, I know about the Google Code project – but my point was that no one else is going to unless they stumble across a thread in the forum where it happens to get mentioned. It doesn’t really encourage community involvement with it ‘hidden’. For the sake of 2 minutes work, links to home, docs, Google Project added to the top of the forum would help everyone. Likewise, if the documentation is under the control of just one or two people it’s going to be a burden on them and not as comprehensive as if the community were able to edit it. See https://wiki.ubuntu.com/ for one good example. Is this topic worth a separate thread? Is Frog going to move towards a project that encourages community involvement, or does Philippe wish to maintain control over all aspects? |
|
1493 posts
|
Hmmm! That moved on quickly from user role permissions! :) I think everyone would like to see the Frog “core team” growing, but that is more easily said than done. About the Google Code pages. If anyone ever tried to get the source for Frog, they would find it in a hurry! Meanwhile, no effort has been spared in bringing its attention to even the most casual Frog user on the official MadeByFrog site! And up above, yes, when I said there was “more info on the Frog Wikipedia page”, I did mean the Frog Wikipedia page! :) I suppose I should have linked it. |
|
651 posts
|
I have no problem with users contributing, nor do I have any problems with a wiki. I do feel however that the Google Code based wiki (though nice) is unsuitable for end-user documentation. (I think it is more suited to the project devs) That may be a personal preference though. Personnaly, I’d like to see DokuWiki get installed on the madebyfrog.com site. @David… I’d like to point out that having a community and having users contribute to Frog is not the same as having them become “core team” members. Most open source projects have a core team with only a few members and a large community of contributing users. That they are not part of the “core team” does not mean they or their contributions are less valuable. (Far from it.) |
|
96 posts
|
David, > …no effort has been spared in bringing its [Google Code] attention to even the most casual Frog user on the official MadeByFrog site! Except, as I’ve already pointed out :), by providing a link in the main menu on each page (along with links in the forum menu back to home + docs). I hadn’t noticed it was mentioned on the download page – and I guarantee many others won’t. That’s my point: make it easy for people, not a requirement that they have to read every line of every page to find something that is useful for everyone who wants to contribute. As the project and community grows, these details become increasingly important. mvdkleijn, I agree that the Google Code wiki is unsuitable – and also agree with DokuWiki as a preferred choice. It’s easy to install, customise and for end users to contribute. I’d also prefer to see all docs consolidated in to the one wiki, avoiding duplication and fragmentation. The wiki could then be arranged in to sections for core devs, front-end devs and another for end users. |
|
651 posts
|
@DavidONE – Agreed. I think we already asked Philippe once to add DokuWiki to the site.. I’ll ask him again though since you, I and David (and I think many others) would welcome a decent wiki integrated into the site. |
|
96 posts
|
:) Coincidentally, there’s a shiny, new version released today – http://www.splitbrain.org/projects/dokuwiki |
257 posts
|
Can I raise a really objective point which is that as we move towards a version 1.0.0 release I feel that a more integrated website would be in order and I feel that this conversation is going in the opposite direction. We have the site which has its own feel, a forum which is independent, an SVN server through google interface and we are now proposing a Wiki based on another system… something feels wrong here and I think it is because of the hard work that people are putting in (especially Martijn) to allow development of more user orientated experience. I would personally prefer that we build the features that Frog needs as individual plugins which can be shared. So a forum plugin, an SVN plugin and a WIKI plugin and roll the whole thing into ONE site. Admittedly we can’t have the power of the separate applications out of the box but I think over time we can make some amazing opportunities for people to get involved. I hope people can see that point as well. BTW in answer to the original post thread, I think that checkboxes are actually better, especially as Frog grows more mature and different user permissions become available… |
|
651 posts
|
I’m not quite sure how to take that… :-) I would welcome anyone who wants to write a wiki plugin for Frog so we could place that on the madebyfrog.com site. From personal experience with developing a wiki system, I can say its no mean feat to get right. I certainly don’t have the time (right now) to do it. As long as the DokuWiki is integrated into the madebyfrog.com site in terms of look-and-feel and (preferably) also make use of the same user ids, I’m fine with that. I don’t want it to become more or less a seperate entity (in terms of look-and-feel) like this forum. My intention would be to keep the Google Code stuff for developers and have it contain Frog Core development information only. Apart from the issue tracker though.. :-) |
541 posts
|
is there a nice wiki in ruby I can migrate in PHP ? no just kidding ;) I will take the time to install this dokuwiki ( hope this week ) but for the point of this topic I just want to let you know why I have choose checkbox instead of radio: this is simple it’s just because I hope people will use this user permission system if they need additional right. If we want to make this application to be as flexible as possible I think the right (permission) have to be by name and not by value like unix right. But this is my opinion! And I agree that for now it look a little bit weird to have checkbox instead of radio. I hope everyone will understand my today poor english ;) |