-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Bram,
First thing - could you put some whitespace/newlines in your future posts, please? It is very hard to read the walls of text like the last one. On 08/29/2014 07:46 PM, Bram Vaessen wrote: > I believe it is better to separate the documentation from the main > website. It's not really easy to explain, but try to look at it > from my perspective, from a general user. It wouldn't cross my mind > to ask you guys for full permission to edit your main website. I'm > not involved with the development of the project and even not you > offer it, I'm think "that's weird, I'm not going to edit the main > website, I'm just a general user". People are complaining that the documentation is hard to find already. Having it on a separate website from the main one would improve the discoverability how exactly? The permission issue can be easily handled by setting up roles and what not. However, the old Trac wiki website didn't do that, everyone could edit everything and there was never an issue. We are adults here, so nobody is going to vandalise the site. And if it happens, it is fairly easy to restore from backup and to ban the offender. We are not talking a website storing personal data and what not that could be stolen here. There is also a question of management of the OSG domain and the content - having it spread out over several entities that are not under the same control could be problematic, but that is something for Robert to judge. > If there is a wiki, or something similar, which is full devoted to > be a repository of knowledge on OSG (which is pretty big), then I > would consider editing or adding some information about a > particular part of the OSG system that I dealt with and learned > something about. For example something that took me a while to find > out, but that I thought should be general knowledge. Feel welcome to write it up and add it. I don't see how writing for a wiki or writing for Joomla is so significantly different from the content's point of view. We aren't talking raw HTML editing here. > But not something that needs a separate article or guide. It's > easy to argue that you can do anything with Joomla that you can do > with wiki, but that's not a very strong argument I think: if you > wouldn't use any content management system and gave users ftp > permission to your website, then technically, you can STILL do > anything that a wiki ... > Joomla to make a full documentation structure for OSG, sorry, I > just don't think Joomla is the right technology for that, even if > 'technically' everything is possible... Basically a very long-winded argument that you like a wiki formatting/content editing more than a regular page editing in Joomla. Did you actually try to use Joomla? I am not sure that a personal preference is a very strong argument. I like wikis too, but when is there is an established system already, there needs to be a stronger argument than that. As you are essentially proposing redoing the documentation section of the website from scratch, then there better is a very good reason for it, because someone would have to actually migrate/retype all that content again and then manage everything. That takes a non-trivial amount of work and time that nobody is actually paid for doing. Are *you* willing to put all that work into it? Jordi did spend a ton of time on the website already. Pages in a CMS are structured as well, while wiki is very easy to make an unholy mess out of unless someone actually manages it actively. The issue of logins - you would need to have a login for a wiki as well, otherwise it will be overflowing with spam and vandalized pages in no time. There is no army of editors like on Wikipedia to keep cleaning that here. The possibility of obtaining the CMS access could be made more visible, though. Regards, Jan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFUANwXn11XseNj94gRAgK2AJwJGtzoVyEw2onQyWoMQ10BAeb4kwCg8bc0 DRYgwkyJTwV1L/dxkLJgYvc= =UVFj -----END PGP SIGNATURE----- _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
