StrategyWiki:Meetings

Anyone is welcome to attend the meetings, which are held on IRC in the #SW-Meeting channel. If you are using the wiki's mibbit client, someone will likely link you, or you can type in /join #SW-Meeting.

Complete logs of all the proceedings of meetings can be found here. For older logs, try here. New logs are generally added within a few hours after the meeting ends.

September 5, 2009 minutes

 * 1) Status of ABXY
 * 2) *We will be working with Howard Ha to help grow our website.
 * 3) *His first task is to help with the acquisition of GamerWiki, which we would like to own and operate by the end of September.
 * 4) *Procyon will keep everyone updated with news as it develops.
 * 5) Site traffic
 * 6) *We have had our traditional "back to school" dip in traffic, but we are still growing well and are doing much better than last year at the same time.
 * 7) *We exceeded 1,000,000 pageviews last month.
 * 8) MediaWiki updates
 * 9) *Prod rolled out updates to MediaWiki (v. 1.15.1) and extentions over Labor Day weekend, including the MultipleUpload extension.
 * 10) *Of most importance were various security related fixes. For a full list of new features, see the MediaWiki changelog.
 * 11) Wikia tools
 * 12) *Opinions were given on Wikia's new rich-text editor, created for the purpose of making editing easier. Consensus from those that knew of it was generally negative, due to it not using templates and leaving weird markup behind.
 * 13) *Wikia's category helper tool was mentioned, and while met a more positive reception, may not be ultimately useful for us given the large amount categories we employ.
 * 14) Policy changes/additions
 * 15) *It was brought to everyone's attention that we have some new policies, as well as changes to an existing one.
 * 16) *Scope, Languages and External links are all in the stage, and would benefit from discussion and/or changes made to their pages.
 * 17) *Collapsible elements in guide Tables of Contents is still an open issue on the staff lounge.
 * 18) Installing the Gadgets extension
 * 19) *Skizzerz has suggested we install this extension, which would enable administrators to write JavaScript tools, which users could then enable/disable from their preferences.
 * 20) *It was noted that scripts would have to go through a verification process before being added to the official Gadgets for the site.
 * 21) MMO guides
 * 22) *It was noted that MapleStory brings in a huge amount of our traffic, and ways in which we can further capitalize on MMO traffic was discussed at length.
 * 23) *Many ideas were advanced with regards to creating another "MapleStory":
 * 24) *#The hard work of a dedicated admin is necessary, e.g. IsaacGS' contributions to MapleStory.
 * 25) *#MMO communities may be turned off by not having their own, independent space, meaning they would rather contribute to MyMMO.com rather than strategwiki.org/MyMMO.
 * 26) *Creating sub-domains or sub-wikis (somewhat like a wiki farm) was suggested as a way to entice MMO communities and give them a greater feeling of autonomy.
 * 27) *Some issues inevitably arose:
 * 28) *#How would being structured as mymmo.strategywiki.org as opposed to strategywiki.org/mymmo affect technical issues, such as navigating between guides and search engine results?
 * 29) *#How much leeway would be given to stray from core StrategyWiki styles and guidelines?
 * 30) *#Giving certain rights to be used solely on one guide would require either separate wikis or a specific (probably not yet written) extension.
 * 31) Firefox site-tracking
 * 32) *It is beneficial for our users to install a site-tracker add-on to Firefox, which lends more importance to our pageviews, much like Nielsen boxes do for television.
 * 33) *Alexa-only add-on
 * 34) *Combination Google, Alexa, and Compete pagerank add-on

August 1, 2009 minutes

 * 1) Business with Echelon
 * 2) *We cannot get in contact with Echelon, therefore the expectations of our potential investor/partner have soured.
 * 3) *Steps are being taken to establish Abxy LLC as the institutional owner of StrategyWiki.org.
 * 4) *#Domains are now held under an account established on Abxy's behalf.
 * 5) *#Abxy has filed for trademark of "StrategyWiki".
 * 6) *Based on his actions (or inactions), it may be that the future of StrategyWiki is of little importance to Echelon.
 * 7) Licensing
 * 8) *Pros and cons of a switch from GFDL to CC-BY-SA license are discussed, with general consensus that we have more to gain by switching.
 * 9) *A vote is called for switching licenses: 7 in favor, 0 against
 * 10) Tekken reskin
 * 11) *The Tekken ad reskin was a success thanks to Teddy and Prod
 * 12) New site skins
 * 13) *Teddy is working on a new look for both ABXY and StrategyWiki in hopes of creating an updated, more cohesive and more intuitive interface.
 * 14) *A link to a mockup is provided and preliminary thoughts are discussed.
 * 15) *To give Teddy some feedback (especially on color scheme, typography, spacing), PMs (on ABXY?) and the Google group are the preferred contact methods.
 * 16) *Some discussion of how well the two sites are integrating commences with the outcome that although there is little crossover at this point, it is the goal of both sites to become more integrated with each other.
 * 17) Evaluation of past month
 * 18) *This is a new feature of the monthly meetings where we reflect on the events of the last month and give opinions on what we should start, continue and stop doing.
 * The floor is opened for individual comments.

Specific issues

 * 1) Staff inactivity
 * 2) *It is noted that activity from staff members has dropped in the last few months.
 * 3) *The general response is that everyone is rather busy this summer (jobs, school, preparation for both, etc.).
 * 4) *Specifically, there is a call to action for the milk project and a general increase in activity for issues on the staff lounge.
 * 5) *#Prod will look into reactivating the MultipleUpload extension.
 * 6) *#Collapsible elements for use on guide Tables of Contents is discussed, and generally approved with the understanding that non-JavaScript users will still have access to the full Table of Contents through the link in the Header Nav and on the main page.
 * 7) YouTube/external links
 * 8) *Najzere's opinion is that linking externally, especially to YouTube, for walkthrough information is potentially damaging to StrategyWiki's viewership.
 * 9) *In a couple more updates to MediaWiki (v. 1.16), functionality for embedded videos will be available and use of the feature will be discussed at that time.
 * 10) *Cons to linking externally: it takes users offsite, helps the competition, and in the case of videos reminds users that there is a "prettier" ("better", to some) way to get the information we provide.
 * 11) *Pros to linking externally: highly detailed information need not be compiled and maintained by us, in the case of videos, it can make understanding of complex or detailed actions easier to understand.
 * 12) *The debate is lengthy; in the end the general feeling is that the issue hasn't hit critical mass yet, video walkthrough sites aren't killing us yet, so we can start on an external links/YouTube guideline, but it isn't a major concern at this time.
 * 13) *Specific instructions for current problem areas (mainly Deus Ex) is to move YouTube links to the talk page and get content written.
 * 14) *In general, we don't want to duplicate walkthrough information in external links.
 * 15) Relaxing standards for Featured Guides
 * 16) *The question of why the standards for Featured Guides are so strict was raised, and the general consensus was that only the best of the best should be on the main page, and we don't want too many.
 * 17) *Some alternatives were suggested, such as a monthly "Spotlight" for really good guides, and the ability to promote guides to completion stage 5 without promoting them to featured status.
 * 18) *Further discussion of the "Spotlight" option will be on the forums.
 * 19) Current partnerships
 * 20) *The question of whether we're getting as much as we're giving for some of our partners (specifically Bulbapedia) was raised.
 * 21) *It was explained that they are linking to us nicely, as can be seen on their main game pages (for example, Red and Blue), and any concerns were alleviated.
 * 22) *It was tentatively suggested that a partnership with the Final Fantasy Wiki be attempted, though it is unlikely, since they have a strong walkthrough section of their own.
 * 23) Staff solidarity
 * 24) *The issue of presenting a united front to users was brought up.
 * 25) *It was generally accepted as a good idea to limit arguments in front of users, and to instead start a new dialogue on the administrator's talk page.
 * 26) *If any staff members are having issues with other admin that they feel aren't being resolved among themselves, they are urged to contact Procyon either on or offline.