Village Pump (policy)

From Bohemia Interactive Community
Revision as of 17:54, 11 August 2006 by Kronzky (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Discuss existing and proposed policies.

Australians in Vietnam

Since Australians in Vietnam is coming out shortly, should it become its own category, or should it stay underneath VBS?

Blocking Policy

The blocking policy page needs to be defined. Right now I've forwarded it to the Guidelines, but it should probably have it own specific rules.


Image Restrictions

I'm thinking we will need to limit the number of images Mods' can have per page to prevent a mass uploading of images. I'm thinking about a number of of 5 - 7 images limit. Assuming 1 -2 pics for logo, 4 pics max for screen shots. It isn't a problem yet, but could in the future. Thoughts? hoz 17:00, 20 July 2006 (CEST)

Sounds like a good number. But can that restriction be limited to just Mod pages? After all, I could imagine somebody putting up pages listing all units, with descriptions and pictures, etc. (like [this one] for VBS1), which could be quite useful. --Kronzky 17:23, 20 July 2006 (CEST)
Yes this would apply to the user pages as well. Again these are just thoughts. Thanks for the input. hoz

How about this for the guidelines, under the "Images" section:

  • You can have up to 7 images on your personal, clan or mod page that is hosted on this Wiki (this includes any sub-pages). For articles describing features of BI games this limit does not apply.

Other Formats

Talking about images - what would the chances be of allowing other content to be uploaded (e.g. PBOs, P3Ds, SQMs)?
It would be quite useful for examples and tutorials, so that one wouldn't have to rely on outside sources.
Of course, the danger would be that this could turn into an addon-depository... --Kronzky 18:14, 21 July 2006 (CEST)

IMHO PBOs aren't common part of tutorial, so they shouldn't be upoadedable. All other file types you listed above are simple text - probably uploading compressed files (zip, rar, 7z, not PBO - other formats are more easy to manipulate with and we don't want be addon repository) can be useful. Size limit for this archive must be strict, I think < 30KB should be enought for scripts. (100 lines of code - 1.3K zip archive, 2000 lines - 26K). How for P3Ds? --Djura 20:35, 23 July 2006 (CEST)
The reason I was suggesting PBOs was that we could be sure that their content would be OFP specific, whereas with zipped formats people could be uploading all kinds of crap. Via a PBO you could upload mission files, addons, or even islands. And since tutorials should only use standard textures anyway, all an addon-PBO would contain would be the P3D and config file anyway.
If you do wanna use zip files for uploading P3Ds you would probbably need a size limit of at least 10K. I just checked a few of my very basic test vehicles (that are really' bare bones platforms), and they compress to between 10-20K --Kronzky 23:38, 23 July 2006 (CEST)
In PBO can be IMHO .doc as well. But I agree now with PBO's as ideal format for uploading. And about size limit, 0,5MB shoul be enought for examples and not enought for addons. --Djura 09:43, 24 July 2006 (CEST)

The question arose if people can/should upload videos. I think not, to save some of BI's traffic, as with videos it can get pretty fast pretty full. --raedor 18:43, 25 July 2006 (CEST)

Also request was made for small PBO files used for examples. Personally I'm against it, an external link to one of the great content sites for tutorials, examples should do just fine. hoz 19:38, 25 July 2006 (CEST)

I guess the question comes down to what the purpose of this site is...
Is it an 'educational' resource, to help people build missions & addons, or is it a more general 'marketing' site, to spread the word about BIS products? In case of the first, an occasional video could be permitted if it demonstrates something that would otherwise be impossible to do with descriptions or pictures. If it's the second case, then I guess the more the better...;) --Kronzky 19:59, 25 July 2006 (CEST)
I would say give links, it cuts down on the size of the pages. plus, there are already enough
websites that provide addon downloads. But on another note, having videos demonstraigning
tips would not be a bad idea, there aren't many websites out there like that. -- Sophion-Black 01:48, 26 July 2006 (CEST)


Downloads - category, list or anything else?

I'm confused about Downloads. In my first idea it should be only list of link to pages, witch use Box Download. If we want special page with all downloads, it shouldn't be category page, it should be sipmle list. IMHO the best solution is to have download boxes at pages witch offer download, category Downloads shoul be category for this pages and all downloads have at Download list too. Do you agree? --Djura 19:26, 23 July 2006 (CEST)

move talk converation to here, no need to bug Suma's talk, we can discuss here and try not bug BI when they can be busy building ArmA, from my understanding we are to try and run the wiki as a community and BI will guide us if we need guideance. On the note of download links, I'm not sure we want the Wiki to be come a respository of download links that maybe prone to failure. There are other sites that host missions and addons. Just some thoughts. hoz 19:57, 23 July 2006 (CEST)
Wiki should descript products and allow possibility to retrive them. I don't want create huge link repository... --Djura 20:05, 23 July 2006 (CEST)
Yeah - There are enough addon-sites out there already. They're doing a pretty good job, and I don't see why we should be duplicating their job. There's also enough redundance so that even if one goes down, most addons would still be readily available from others. --Kronzky 23:49, 23 July 2006 (CEST)


VBS Policy

I think we need some clear guidelines from BI with regard to the VBS policy so that the wiki sysops have a clear message. Do we allow VBS pics on user pages? Do we allow links to VBS sites? anything else? How do we handle such edits, with a template? hoz 18:45, 25 July 2006 (CEST)

Removed the "no edits" proposal: the VBS page is already protected. --raedor 19:04, 25 July 2006 (CEST)
VBS is to be integrated into the wiki in the same manner as other BI products, the only 'rule' I would suggest is to ask people to describe which product they are using when they post to avoid confusion. Yes we will allow VBS pics and links to VBS sites. We would like the wiki to become a resource for all Real Virtuality users, VBS included. The VBS Resources page and forum will remain open for the foreseeable future as an additional resource. Military customers will need to use their discretion. Any queries should be directed to vbs@bistudio.com or the VBS Resources forum at http://www.vbsresources.com/forum - snYpir, Lead Developer VBS2, 11:17, 27 July 2006 (AEST)
My understanding of the Community Guidelines is that in order to protect the interests of the gaming community, to prevent the unfair negative commercial exploitation of community content, and to provide a clear channel for Bohemia Interactive to support the specific needs of military and professional customers, that the guidelines for the whole of the Community site and content is restricted for non-commercial (prohibiting military, government, and other professional) use only. Commercial customers would need to contact Bohemia Interactive directly for their contract documentation and support, to meet their specific requirements and to prevent Intellectual Property contamination. Shinraiden 06:38, 27 July 2006 (CEST)

Edited the VBS policy draft. hoz 18:16, 27 July 2006 (CEST)

To clarify, the wiki EULA will be modified to allow use by military customers (currently it specifies entertainment only), and the non-commercial clause will be defined; 3rd party use of wiki content for redistribution or resale is prohibited, but military users will be able to use all wiki content to assist in the use of VBS for training or experimentation. All contibutors to the wiki should understand that any content submitted here could be used by military customers, without permission! - snYpir, Lead Developer VBS2


Copyright

Going by snYpir's posts, and considering that we need a copyright policy for all content on this site anyway (not just for VBS), should we perhaps adopt a Creative Commons license like this?

Content posted on this site will be covered under the following creative commons license:

  • Attribution. You must attribute the work in the manner specified by the author or licensor.
  • Noncommercial. You may not use this work for commercial purposes.
  • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.

Which means that any user - private, commercial or military - can use any content from site for their own entertainment, training or experimentation. It is not allowed though, to resell content from this site, unless either BI or the content owner have given written authorization to do so.

For questions regarding OFP/ArmA related content, please contact ofp@bistudio. For VBS content contact vbs@bistudio.com or the VBS Resources forum.

Any content that only consists of links to other sites is not affected by this license.

--Kronzky 02:21, 6 August 2006 (CEST)

As you may already know there is a EULA currently posted on the dislaimer page, although it will shortly be re-worded to allow for uses other than entertainment. The creative commons license would potentially be suitable for non-BI users of the wiki. As per the current EULA, BI alone retains the right to use content posted here commercially, and all users will need to be aware of this. From my perspective, the danger is not that military people or academics are using content on this site (there are many organisations out there who use our engine for purposes other than entertainment), but that a 3rd party company will copy and sell content for monetary gain, and this must be prohibited - snYpir, Lead Developer VBS2, 08:49, 6 August 2006 (CEST)
Since the legal aspects will be covered in the EULA, and there won't really be any special rules for VBS anymore, can we then remove the relevant section in the Disclaimer as well as the Guidelines? The requirement for image labeling (to indentify which game a screnshot was taken in) has already been defined in the revised Image Guidelines. --Kronzky 23:25, 6 August 2006 (CEST)
I will discuss this with Placebo on Monday morning and let you know ;) - snYpir, Lead Developer VBS2, 00:48, 7 August 2006 (CEST)

Multilingual articles

Is it already possible to make them and if so, how it is done?

I don't think non-English articles would currently be accepted, since it states in the Guidelines that "this Wiki's offical language is English. Avoid writing in any other languages[...]".--Kronzky 03:44, 28 July 2006 (CEST)
The problem I see with allowing other languages, is it would take a great many people to maintain the different languages and over the long haul would add alot more work and perhaps inconsistencies between articles. I just don't see it happening IMO. hoz 03:32, 28 July 2006 (CEST)
In this case I would remove this proposal
BTW, T D, don't forget to sign your posts (it makes it easier to know who one is talking to). And I know how easy it is to forget - happens to me all the time...;) --Kronzky 18:44, 28 July 2006 (CEST)


News
post | watch

News about BI and this Wiki.

Policy
post | watch

Discuss existing and proposed, new policies.

Proposals
post | watch

New proposals that are not policy related.

Things To Do
post | watch

Areas of the Biki that need attention.

Assistance
post | watch

Request assistance for the creation and update of content.

Technical
post | watch

Technical issues related to the MediaWiki software.

Miscellaneous
post | watch

Topics that do not fit into any other category.