Oh yea, sorry, I mean that thier writers of that pages will be the only
normal users to have access to that pages. Admis have access to the
whole wiki anyway!
Il 08/05/2014 16:49, Jonathan Aquilina ha scritto:
I think point two admins should still have access regardless. lets say
the writing goes MIA or no longer works for the project then at least
an admin can maintain the page etc.
On Thu, May 8, 2014 at 4:46 PM, [email protected]
<mailto:[email protected]> <[email protected]
<mailto:[email protected]>> wrote:
I think we need another thread for this.
My idea is to:
- Write support for GUI&settings, instrument plugins, VST support
and *lock their pages*: admins only will update them when necessary
- Leave translations of these pages *unlocked until they are
finished*, then lock them and leave access to that page only to
the ones who wrote them
- Leave all other pages*unlocked* (those may be guides for effects
plugins or any other thing that may be interesting)
I think it's not a problem if a user writes a random page about
himself. The real matter of the wiki is to write support for most
important features of the program and protect it.
As far as I know, mediawiki is able to do what I wrote, and I
think other wiki softwares will be too.
If this is too difficult to do, then I think what you wrote is fine.
It would be also good to have a (?) button in all the instrument
plugins which makes the user go directly to the right wiki page.
~DeRobyJ
Il 08/05/2014 15:21, Jonathan Aquilina ha scritto:
The question becomes do we want people to be able to
register to put up content or lock it down to where an admin would add
users to keep spam at a minimum.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
LMMS-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/lmms-devel
--
Jonathan Aquilina
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
