SoylentNews - User contributions [en]

SoylentNews:Sandbox

2015-03-15T23:29:15Z

FunPika: WikiRC test.

{{SoylentNews:Sandbox/Header}}

Test<ref>Test reference</ref>

WikiRC test 1 2 3

== References ==
<references />

SoylentNews:Sandbox

2015-03-15T20:24:16Z

FunPika: WikiRC test.

{{SoylentNews:Sandbox/Header}}

Test<ref>Test reference</ref>

WikiRC test 1 2

== References ==
<references />

SoylentNews:Sandbox

2015-03-15T19:51:45Z

FunPika: WikiRC test.

{{SoylentNews:Sandbox/Header}}

Test<ref>Test reference</ref>

WikiRC test 1

== References ==
<references />

SoylentNews:Sandbox

2015-03-15T19:34:01Z

FunPika: WikiRC test.

{{SoylentNews:Sandbox/Header}}

Test<ref>Test reference</ref>

== References ==
<references />

Template:Spam

2014-12-20T14:47:12Z

FunPika: Fix parameter.

<includeonly>
{{Speedy|it is spam}}
</includeonly>

Template:Speedy

2014-12-20T14:46:42Z

FunPika: Add parameter.

<div style="border:1px solid red;">
This page is a candidate for '''speedy deletion''' because {{{1}}}. If you would like to contest this deletion, please do so on this page's [[{{TALKPAGENAME}}|talk page]].
</div>
<noinclude>
Any pages this template is placed onto will be added to [[:Category:Candidates for speedy deletion]].
</noinclude>
<includeonly>
[[Category:Candidates for speedy deletion]]
</includeonly>

Template:Spam

2014-12-20T14:45:36Z

FunPika: Make this use the existing speedy template.

<includeonly>
{{Speedy|spam}}
</includeonly>

SoylentNews:Sandbox

2014-11-27T20:26:03Z

FunPika: test

{{SoylentNews:Sandbox/Header}}

Test<ref>Test reference</ref>

TEST123 Test WikiRC

== References ==
<references />

Wikirc

2014-11-27T20:24:28Z

FunPika: Redirected page to WikiRC

#REDIRECT [[WikiRC]]

SoylentNews:Sandbox

2014-11-27T20:20:00Z

FunPika: TEST

{{SoylentNews:Sandbox/Header}}

Test<ref>Test reference</ref>

TEST123

== References ==
<references />

MediaWiki:Sitenotice

2014-11-16T03:21:45Z

FunPika: We are well past October 29 now.

IRC links

2014-09-15T23:50:13Z

FunPika: added Category:IRC using HotCat

Links that used to be in the topic in #soylent on IRC that were moved here to avoid cluttering it.

*IRC Logs: http://logs.sylnt.us/
*Wiki: [[SoylentNews]]
*Code: http://sylnt.us/code
*Got bugs? http://sylnt.us/bugs
*Get Involved: [[SoylentNews#Get_Involved]]
*Who's Who: [[WhosWho]]
*Submit Stories: http://sylnt.us/submit
*Latest code and testing on Dev Server: http://sylnt.us/dev

[[Category:IRC]]

SoylentNews:Services roots

2014-09-15T23:45:43Z

FunPika: FunPika moved page SoylentNews:Services roots to SoylentNews:Beryllium roots

#REDIRECT [[SoylentNews:Beryllium roots]]

SoylentNews:Beryllium roots

2014-09-15T23:45:42Z

FunPika: FunPika moved page SoylentNews:Services roots to SoylentNews:Beryllium roots

'''Beryllium roots''' are users on the SoylentNews wiki who have root on [[Beryllium]] and have some additional abilities on the wiki itself, but are not members of the [[Wiki]] team.

The rights assigned to Beryllium roots include:
* The ability to [[Special:LockDB|lock]] and [[Special:UnlockDB|unlock]] the database. (Normally available to [[SoylentNews:Bureaucrats|bureaucrats]])
* The ability to modify the [[Special:Interwiki|interwiki table]]. (Normally available to [[SoylentNews:Administrators|administrators]])
* Are [[SoylentNews:Autoconfirmed users|autoconfirmed]] regardless of number of edits or how long their account has been registered for.
* Can edit any page on the wiki, including fully protected pages and interface (MediaWiki: namespace) messages such as [[MediaWiki:Sidebar]].

== Automatically generated list of Beryllium roots ==
{{Special:ListUsers/developer}}

[[Category:Wiki]]

SoylentNews:Beryllium roots

2014-09-15T23:45:27Z

FunPika: Update to say Beryllium instead of services.

MediaWiki:Tag-blanking-description

2014-09-15T23:34:29Z

FunPika: Tag description.

This edit blanked a substantial part of the article.

Tagged by filter [[Special:AbuseFilter/3|3]].

Finances1

2014-09-15T23:14:32Z

FunPika: Create based on revision 8459 in Finances/Archive.

Rewrite coming very soon. This page was extremely dated and has been archived [[Finances/Archive|here]].

Historic:Finances/Archive

2014-09-15T23:12:50Z

FunPika: FunPika moved page Finances to Finances/Archive without leaving a redirect: Outdated page that needs to be rewritten.

'''Update:'''This project will be non-profit and community-driven.

'''Note:'''This page is archival

I'm not wedded to for-profit, and realize that people want assurances about selling out in the future &c.

I'm going to put this issue off and post no substantive position until we have a working site and get a chance to catch our breath. This will take about 2 weeks, maybe 4 if we're unlucky.

People can then make proposals and we can discuss assurances and whatnot. If you can hold off on your misgivings until then, we can work on getting the site up and running.

Please continue to discuss, only note that I won't be responding to these issues for awhile.

You can leave comments in the space below.

=Business=
Slashdot was originally run using 10 full time employees ([[http://strom.com/awards/237.html|source]]).

Summary of the business history on [[wikipedia:Slashdot|Wikipedia]].

The direction we are headed towards is some type of NFP. Staff are discussing and contacting various organizations as how best to proceed. This will require incorporation, which is also being pursued.

== Business model variants ==
*[[ForProfit|Centralised, for profit]];
*[[PureContent|A pure content provider, community provides web servers]]
*[[Distributed|Fully decentralised architectures]].

== Ideas on how to make money to finance the operation ==
* What makes Slash so good? The comments section! Why? Because it brings together a large group of smart and intelligent IT professionals who share their collective knowledge.
* -> This is value!
* -> Who has money to spend? Managers, finance guys, etc.
* -> What do they need? Expertise.
* => (1) How about crowdsourcing answers for questions they have? Like "What the heck is WebRTC?", "What are the costs of implementing XYZ in my company?", "Who has experience with XYZ? Why should or shouldn't I buy it?", "How can I solve problem XYZ?"-> Sell "ask Slash" posts with an additional "professional review by mods with a lot of karma" feature. Introduce extra karma/virtual gold coins for those who contribute with valuable answers to these "ask Slash professional" posts.
* ==> the idea is to make money out of the explicit value Slash has, namely its community/commenters.

* Below is a copy from [[FeatureList#Article_submission]] - '''To have funds for all that''', we could use:
** That tipping system (mentioned in moderation section of [[FeatureList]]), and everytime you tip someone else a very tiny fraction of that tip goes to [this project]. <-- I like this [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 23:15, 14 February 2014 (MST)
** Also payments from people desperate to post in thread (or story) where they have moderated (if we decide that this feature is useful, and if it is thread or whole story) - also in moderation section of [[FeatureList]]. <-- mentioned elsewhere that this is not a good idea (people with money shouldn't have more say) [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 23:15, 14 February 2014 (MST)
** Failed submitters, who had to give back their cryptocoin reward for their submission plus some extra fraction because their story was hated after it was submitted (think Roland Piquepaille) as mentioned in [[FeatureList]] (they can't submit new stories if they don't give back their payments).
** Also we can simply hope for money from cryptocoin donations address. IMHO that is quite possible if we make this site good.
** We might consider ''paying subscribers'' using cryptocoin.
** Make a "featured product/serivce -> ask for review" section that charges for having a product reviewed

Historic:Finances/Archive

2014-09-15T23:11:50Z

FunPika: Undo revision 8459 by The Mighty Buzzard (talk)

HowToAcceptSelfSignedCertsForHttps

2014-09-06T20:51:28Z

FunPika: /* Firefox */ Put both screenshots into a gallery tag.

Parent: [[UserExperience]]

A number of sites including Soylentnews, in places, use self signed certs for https encryption.

The first time you go to such a site, you will see some sort of warning from your browser. The exact nature of that warning varies, each browser handles it a little differently. What is important is that you need to use whatever facility is provided to tell your browser that it is ok to continue on connecting, and, unless you want to deal with that message every time you visit the site, you need to tell it to remember your choice.

==Some examples of typical browser warnings==

Below, I have loosely recorded the steps I had to take with some of the browsers I have available here and some other instructions from various places. If you are having trouble, reading through these - even if your exact browser is not here - may help a bit. You can at least get a rough ideas of what is required.

===Internet Explorer===

( from http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/topic/com.ibm.rational.rrdi.admin.doc/topics/t_browser_ss_cert.html )

Ignore the warning message and proceed to the website. A certificate error is displayed in the address bar.

Click Certificate error in the address bar.

Click View certificates.

Click the Certification Path tab

Select the root certificate and click View Certificate.

Click Install Certificate to start another Certificate Import wizard.

Note: If the Install Certificate button remains disabled, you must click Tools > Internet options > Content > Certificates > Trusted Root Certificate Authorities and import the root certificate manually.

Click Next.

Select Place all certificates in the following store, click Browse, select Trusted Root Certificate Authorities, click OK and click Next.

Click Finish.

Click Yes to import the root signer certificate into Internet Explorer’s certificate trust store

Click OK to close the Certificate Import wizard.

Click OK twice to close the Certificate window.

Close all instances of Internet Explorer.

Repeat step 1. Internet Explorer does not warn you about the untrusted certificate. If the browser warns you about mismatched certificate address, click Tools > Internet Options > Advanced. Scroll down and clear the Warn about certificate address mismatch check box. Click OK. Close Internet Explorer and repeat step 1.

===Firefox===
(Is probably similar to other browsers using the Firefox engine)

* Select 'I Understand the Risks'

* Select 'Add Exception'

* Make sure 'Permanently store this exception' is checked

* Select 'Confirm Security Exception'
<gallery>
File:Firefox connection untrusted.png|Connection untrusted screen in Firefox
File:Firefox add security exception.png|Add security exception screen in Firefox
</gallery>

===Opera===

(Note the very newest versions of Opera are using a diffderent engine)

-- Mac Version 10.10.0

'Warning this page may not be secure'

'You need to approve or reject the loading of this page'
/Help/ /Reject/ /Approve/

-select security tab, see:

The certificate for "www.xxxxx.org" is signed by the unknown Certificate Authority
"www.xxxxx.org". It is not possible to verify that this is a valid certificate.

/X/ Remember my choice for this certificate

Then select the main /Approve/ button.

===Safari===

(Is probably similar to other browsers using the 'Webkit' engine)

-- Mac Version 4.1.3

'Safari can't verify the identity of the website www.xxxxx.org'

/Show Certificate/ /Cancel/ /Continue/

- select show certificate

- select Trust Setting

- select When using this certificate, /Always Trust/

- select /Continue/

===Google Chrome===

(from http://stackoverflow.com/questions/7580508/getting-chrome-to-accept-self-signed-localhost-certificate )

Using Chrome, hit a page on your server via HTTPS and continue past the red warning page (assuming you haven't done this already).

Open up Chrome Settings > Show advanced settings > HTTPS/SSL > Manage Certificates.

Click the Authorities tab and scroll down to find your certificate under the Organization Name that you gave to the certificate.

Select it, click Edit, check all the boxes and click OK. You may have to restart Chrome.

You should get the nice green lock on your pages now.

EDIT: I tried this again on a new machine and the certificate did not appear on the Manage Certificates window just by continuing from the red untrusted certificate page. I had to do the following:

On the page with the untrusted certificate (https:// is crossed out in red), click the lock > Certificate Information.

Click the Details tab > Export. Choose PKCS #7, single certificate as the file format.

Then follow my original instructions to get to the Manage Certificates page. Click the Authorities tab >

Import and choose the file to which you exported the certificate, and make sure to choose PKCS #7, single certificate as the file type.

If prompted certification store, choose Trusted Root Certificate Authorities

Check all boxes and click OK. Restart Chrome.

====Google Chrome, Mac OS X and Self-Signed SSL Certificates====

(Another approach, from http://www.robpeck.com/2010/10/google-chrome-mac-os-x-and-self-signed-ssl-certificates/ )

By Rob Peck · Published 6 October 2010 · apache, apple, linux, networking, security, mac, osx

I've been using Google Chrome as my primary browser for the last few months. Sorry, Firefox, but with all the stuff I need to work installed, you're so slow as to be unusable. Up to and including having to force-quit at the end of the day. Chrome starts and stops quickly But that's not the purpose of this entry. The purpose is how to live with self-signed SSL certificates and Google Chrome.

Let's say you have a server with a self-signed HTTP SSL certificate. Every time you hit a page, you get a nasty error message. You ignore it once and it's fine for that browsing session. But when you restart, it's back. Unlike Firefox, there's no easy way to say "yes, I know what I'm doing, ignore this." This is an oversight I wish Chromium would correct, but until they do, we have to hack our way around it.

Caveat: these instructions are written for Mac OS X. PC instructions will be slightly different at PCs don't have a keychain, and Google Chrome (unlike Firefox) uses the system keychain.

So here's how to get Google Chrome to play nicely with your self-signed SSL certificate:

On your web server, copy the crt file (in my case, server.crt) over to your Macintosh. I scp'd it to my Desktop for ease of work.

** These directions has been updated. Thanks to Josh below for pointing out a slightly easier way.**

In the address bar, click the little lock with the X. This will bring up a small information screen. Click the button that says "Certificate Information."

Click and drag the image to your desktop. It looks like a little certificate.

Double-click it. This will bring up the Keychain Access utility. Enter your password to unlock it.

Be sure you add the certificate to the System keychain, not the login keychain. Click "Always Trust," even though this doesn't seem to do anything.

After it has been added, double-click it. You may have to authenticate again.

Expand the "Trust" section.

"When using this certificate," set to "Always Trust"

That's it! Close Keychain Access and restart Chrome, and your self-signed certificate should be recognized now by the browser.

This is one thing I hope Google/Chromium fixes soon as it should not be this difficult. Self-signed SSL certificates are used *a lot *in the business world, and there should be an easier way for someone who knows what they are doing to be able to ignore this error than copying certificates around and manually adding them to the system keychain.

[[Category:User experience]]

HowToAcceptSelfSignedCertsForHttps

2014-09-06T20:47:09Z

FunPika: /* Firefox */ Remove one of the screenshots for now, these are going further into the other sections than I would like.

HowToAcceptSelfSignedCertsForHttps

2014-09-06T20:45:08Z

FunPika: /* Firefox */ Simplify instructions, add screenshots.

File:Firefox add security exception.png

2014-09-06T20:30:39Z

FunPika: An example of Firefox's add security exception screen. Category:User experience

An example of Firefox's add security exception screen.
[[Category:User experience]]

File:Firefox connection untrusted.png

2014-09-06T20:25:59Z

FunPika: An example of Firefox's SSL connection untrusted screen. In this case viewing a site using a CAcert certificate in a Firefox profile that does not recognize CAcert. Category:User experience

An example of Firefox's SSL connection untrusted screen. In this case viewing a site using a CAcert certificate in a Firefox profile that does not recognize CAcert.
[[Category:User experience]]

HowToAcceptSelfSignedCertsForHttps

2014-09-06T20:12:26Z

FunPika: added Category:User experience using HotCat

==How To Accept Self Signed Certs For Https==

So, the first time you go to the site, you will see some sort of warning from your browser. The exact nature of that warning varies, each browser handles it a little differently. What is important is that you need to use whatever facility is provided to tell your browser that it is ok to continue on connecting, and, unless you want to deal with that message every time you visit the site, you need to tell it to remember your choice.
Some examples of typical browser warnings

Below, I have loosely recorded the steps I had to take with some of the browsers I have available here. If you are having trouble, reading through these - even if your exact browser is not here - may help a bit. You can at least get a rough ideas of what is required.
Internet Explorer
Firefox

-- Mac Version 3.6
This Connection is Untrusted

/Get me out of here/

You have asked Firefox to connect
securely to www.homeviva.demmers.org, but we can't confirm that your connection is secure.

Normally, when you try to connect securely,
sites will present trusted identification to prove that you are
going to the right place. However, this site's identity can't be verified.

What Should I Do?

If you usually connect to
this site without problems, this error could mean that someone is
trying to impersonate the site, and you shouldn't continue.

Technical Details

www.homeviva.demmers.org uses an invalid security certificate.

The certificate is not trusted because it is self-signed.

The certificate is only valid for homerun.demmers.org

(Error code: sec_error_untrusted_issuer)

- select 'I Understand the Risks'

If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if
you trust the site, this error could mean that someone is tampering with your connection.

Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification.

- select /Add Exception/

- select /X/ permanently store this exception

- select /Confirm Security Exception/

-- Version X.6

Opera

-- Mac Version 10.10.0

'Warning this page may not be secure'

'You need to approve or reject the loading of this page'
/Help/ /Reject/ /Approve/

-select security tab, see:

The certificate for "www.homeviva.demmers.org" is signed by the unknown Certificate Authority
"www.homeviva.demmers.org". It is not possible to verify that this is a valid certificate.

/X/ Remember my choice for this certificate

Then select the main /Approve/ button.

Safari

-- Mac Version 4.1.3

'Safari can't verify the identity of the website www.viva.demmers.org'

/Show Certificate/ /Cancel/ /Continue/

- select show certificate

- select Trust Setting

- select When using this certificate, /Always Trust/

- select /Continue/

[[Category:User experience]]

Wiki

2014-09-06T20:12:08Z

FunPika: /* Todo */ Add todo item for adding stuff to categories.

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin/bureaucrat
| UTC-4 (EST/EDT)
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

=== Inactive ===
'''Note: These are members of the wiki team who have lost their onwiki flags such as admin due to inactivity. If they return, they can receive their flags back by contacting any [[SoylentNews:Bureaucrats|bureaucrat]].'''
{| class="wikitable" width="100%"
!colspan="3"|Inactive Wiki Team members
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| Cactus
| admin/bureaucrat (demoted due to inactivity in September 2014)
| ?
|-
| Yahwotqa
| admin (demoted due to inactivity in March 2014)
| ?
|-
| Sfm
| admin (demoted due to inactivity in March 2014)
| ?
|}

== Todo ==

*Find a way to categorize all of the pages on the wiki. See [[Special:UncategorizedCategories]], [[Special:UncategorizedFiles]], [[Special:UncategorizedPages]], and [[Special:UncategorizedTemplates]]. If anyone wants to help with this, copying the contents of [[User:FunPika/common.js]] to [[Special:MyPage/common.js]] will make it easier.

== Documentation ==
* The wiki is hosted on [[Beryllium]].
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

Style:Typography

2014-09-06T20:07:30Z

FunPika: added Category:User experience using HotCat

=== [http://en.wikipedia.org/wiki/Golden_ratio Golden Ratio] of Proportionality ===
[http://www.pearsonified.com/2011/12/golden-ratio-typography.php This resource] is summarised for our purposes here and pertains to '''Line length, Line height and Font Size''':
* The Golden Ratio is approximately = 1.618
* Line height increases with increasing font size, and increasing line length.
** Landscape view has long line lengths
** Portrait view has short line lengths
* The screen orientation should be sensed to determine optimal line width: use media queries.
* Font style will have implications on perceived line widths, as stunted fonts versus tall fonts produce a different overhead whitespace.
See [http://http://www.pearsonified.com/wp-content/uploads/2011/12/line-height-vs-line-width.png Line Height versus Line Width] at pearsonified.com for a thumbnail guide to font size / line height selection.
* The same website provides a calculator:
See [http://www.pearsonified.com/typography/ Typography Calculator]
==== Why do Golden Ratios work for visual appearance? ====
* The brain is geared for nature, in which natural logarithms and other well known patterns such as the Golden Ratio, are ubiquitous.

=== General Guidelines for Font Choice ===
* The actual font face chosen is a matter of '''taste, practicality and evidence basis'''
==== Taste ====
* The current fashion is to use sans-serif fonts, however with increasing display desity and the fact that sans-serif has been in vogue a long time, this fashion is set to change back to serif
* Titles should continue to be sans-serif, as we are a tech / geek oriented site and this font choice has been usual in such circles for many decades.
==== Practicality ====
* Old screen displays come in at around 96 pixels per inch
* New screen displays come in at 200+ pixels per inch:
** Smartphones exceed 300 pixels per inch
** Retina and similar high resolution displays are 250+ pixels per inch
* Web browsers are now re-interpreting pixel and point sizes to make sure that fonts are not impossibly small on high resolution displays
** This is bad because no two web browsers are using the same methods for this fudge factor
** We therefore need to start using a more practical methods than px and pt for size definition. The use of em is probably the best option now.
==== Evidence Basis ====
* Older studies for screen fonts relied on lower resolution displays than those currently being manufactured. Their validity is now doubtful.
** [http://people.dsv.su.se/~jpalme/internet-course/font-report.html A Swedish study by Julia Barrantes and Elahe Jalili Baleh ] showed (at 96 pixels per inch):
*** 80 characters per line is faster to read than 40
*** Times New Roman is ''much more'' readable than Verdana at equal pixel size
*** Arial is ''somewhat more'' readable than Verdana
* Microsoft, based on their studies, have retired Verdana and Arial in favour of the Calibri family of fonts
** This is a sans-serif font but differs from the others in that it is thinner in points to become lighter, which the studies showed improves readability.
* Neuroscience gives a lot of insight as to why some fonts and visual layouts are better than others
** The retina has nearly all of its resolution concentrated in the centre of vision, where there is maximal colour and contrast discernment. The size of this area is small, about the size of two thumbs in front of you, arms outstretched.
*** The significance of this is that the eye takes in a certain line-length before it must flick across to the next set of text. If the text is tiny, the eye must rest in one place for longer while the cortex processes the information before it can flick across, and it is likely to flick across a smaller distance if the text is small (eg: sitting far away, or text too small). The reader will subconsciously adjust the distance from eye to page depending on the text size and display width. If there is a great mismatch between text size and display width, the processing work is too great, which is interpreted as discomfort.
*** This is the reason why studies show consistency in their results on readability. The evidence is believable because the mechanism is well understood.
** The peripheral vision is dedicated to motion detection and lacks colour or detail. The perception that peripheral vision is complete is an illusion, as the brain invents the colours and textures of your peripheral vision based on experience and what has been captured in the central vision.
** The blind spot (upper-outer vision) is necessary due to the blood supply to the retina, and is located such that the opposite eye can compensate for it, but not always.
** The eye enhances what you see by center-surround antagonism:
*** Bright and dark shade is sent to the visual cortex, which processes the signal
*** If the contrast between bright and dark is low, the cortex amplifies the difference to enhance edge and texture detection
*** If there is a lot of shadow and many lines and details, the visual cortex '''has to work harder''' to process this information and make sense of it.
*** On the other hand, the visual cortex of primates is adapted to detecting vertical and horizontal lines and their intersections over lines or curves in other directions
** The accessory visual cortex interprets shapes. The harder this is, the more work it takes to read.
*** Most of advanced readers recognize words as shapes rather than reading individual letters. This is aided by the use of familiar fonts which give a regular shape for a given word.
*** Placing serifs on letters enhances the uniqueness of their shape and this is why serif text is more readable. However modern taste is for simplicity and minimalism, and older displays handled serif text poorly, which is why sans-serif text is largely used.
==== Lessons ====
* Minimal lines, shades and distracting images should be used, to aid focus on the content (text) of the site.
* Font choice should be a compromise between aesthetics and readability. It is for this reason that, as displays became more photo-realistic, Microsoft chose Calibri, as it borders on being a serif font in many respects, but is recognized as sans serif. Microsoft's research in font readability has, at least until recently, been ahead of the others.
* We should consider returning to the use of a minimal serif, or borerline sans-serif font, rather than Verdana which is a classic sans-serif font and arguably a bit dated.
* As fonts are very inexpensive (less than $100) we could consider buying a font that suits our needs.

=== General Guidelines for Styles ===
==== Drop Caps ====
* Drop-caps will not be used, as we are not aiming for magazine style and we do not consistently have long articles. If used, Drop caps should only be used in the top article in any given page, never in the lower half of a page.
==== Block Quote ====
* Blockquotes should be indented, approx 0.50cm from the left justification of normal text, however in fact this should be some fixed ratio of line height.
** However to maintain tidy left flush design, a tick but lightly shaded vertical rule (3.30 pt thickness, for example) should run along the left margin
** Text should be approximatley 0.5cm justified from the vertical rule
** A suggested shade of the left margin-bar is 5%, in keeping with the border used in Code (see below)
* Using the vertical rule allows blockquotes to be nested. Over-nesting should be avoided and prevented, as it begins to be ugly beyond the 2nd tier.

==== Code ====
* Code should be monospace
* Code boxes should have a standard maximum height and generally have automatic vertical and horizontal scroll-bars
* Code could be in a very lightly shaded (eg: 2.5%) box, with a hairline border of twice the weight (eg: 5% shade).
* Text should have equal padding around it, about half the size that of block quote
==== Colour ====
* Colour should be used very sparingly
* If any colour is used, it becomes a method of branding the project and should conform to the overall skin of the site
** Only one hue apart from black should be use in text formatting and this should be a named colour, having a standardized ratio of RGB.
** The only possible exception to this rule is marking links as having been followed. In this case, possibly a grey shade is best, or the matched color to the chosen hue from a recognized color wheel (ideally one intended for a two tone design)

[[Category:User experience]]

Wiki

2014-09-06T20:05:30Z

FunPika: /* Todo */ Pretty sure all of this is done.

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin/bureaucrat
| UTC-4 (EST/EDT)
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

=== Inactive ===
'''Note: These are members of the wiki team who have lost their onwiki flags such as admin due to inactivity. If they return, they can receive their flags back by contacting any [[SoylentNews:Bureaucrats|bureaucrat]].'''
{| class="wikitable" width="100%"
!colspan="3"|Inactive Wiki Team members
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| Cactus
| admin/bureaucrat (demoted due to inactivity in September 2014)
| ?
|-
| Yahwotqa
| admin (demoted due to inactivity in March 2014)
| ?
|-
| Sfm
| admin (demoted due to inactivity in March 2014)
| ?
|}

== Todo ==

*Nothing currently

== Documentation ==
* The wiki is hosted on [[Beryllium]].
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

Wiki

2014-09-06T19:34:29Z

FunPika: /* Who we are */ Add bureaucrat on mrcoolbp's entry.

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin/bureaucrat
| UTC-4 (EST/EDT)
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

=== Inactive ===
'''Note: These are members of the wiki team who have lost their onwiki flags such as admin due to inactivity. If they return, they can receive their flags back by contacting any [[SoylentNews:Bureaucrats|bureaucrat]].'''
{| class="wikitable" width="100%"
!colspan="3"|Inactive Wiki Team members
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| Cactus
| admin/bureaucrat (demoted due to inactivity in September 2014)
| ?
|-
| Yahwotqa
| admin (demoted due to inactivity in March 2014)
| ?
|-
| Sfm
| admin (demoted due to inactivity in March 2014)
| ?
|}

== Todo ==

* Upload existing externally hosted images onto the wiki.
* Install more anti-spam extensions if needed
* When MediaWiki 1.23.0 is released (likely late April), remove the <code>$wgPhpCli = false;</code> line from LocalSettings.php, since it should no longer be necessary. [[mediawikiwiki:Manual:Job queue]]

== Documentation ==
* The wiki is hosted on [[Beryllium]].
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

SoylentNews:Flood

2014-09-06T19:22:44Z

FunPika: added Category:Wiki using HotCat

The '''Flooders''' user right is one that [[SoylentNews:Administrators|administrators]] and [[SoylentNews:Bureaucrats|bureaucrats]] can grant themselves to temporarily hide their edits from [[Special:RecentChanges]], if they anticipate making an unusually large amount of edits in a short period of time.

[[Category:Wiki]]

SoylentNews:Check user

2014-09-06T19:21:47Z

FunPika: added Category:Wiki using HotCat

The '''Check user''' group gives access to [[Special:CheckUser]] and allows determining the IP addresses of logged in users, as well as what logged in users have used a certain IP address. At the moment, this should '''only''' be used for the purposes of determining if blocking an IP range may be effective against users posting spam on the wiki.

[[Category:Wiki]]

Wiki

2014-09-06T19:16:50Z

FunPika: /* Who we are */ Create inactive section, move Cactus to it. Add previous wiki team members demoted due to inactivity as well.

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin
| UTC-4 (EST/EDT)
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

=== Inactive ===
'''Note: These are members of the wiki team who have lost their onwiki flags such as admin due to inactivity. If they return, they can receive their flags back by contacting any [[SoylentNews:Bureaucrats|bureaucrat]].'''
{| class="wikitable" width="100%"
!colspan="3"|Inactive Wiki Team members
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| Cactus
| admin/bureaucrat (demoted due to inactivity in September 2014)
| ?
|-
| Yahwotqa
| admin (demoted due to inactivity in March 2014)
| ?
|-
| Sfm
| admin (demoted due to inactivity in March 2014)
| ?
|}

== Todo ==

* Upload existing externally hosted images onto the wiki.
* Install more anti-spam extensions if needed
* When MediaWiki 1.23.0 is released (likely late April), remove the <code>$wgPhpCli = false;</code> line from LocalSettings.php, since it should no longer be necessary. [[mediawikiwiki:Manual:Job queue]]

== Documentation ==
* The wiki is hosted on [[Beryllium]].
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

IRC links

2014-08-26T23:57:40Z

FunPika: Create page to move the links cluttering the topic in #soylent to.

MediaWiki:Sitenotice id

2014-08-26T23:49:59Z

FunPika: Created page with "1"

MediaWiki:Sitenotice

2014-08-26T23:49:22Z

FunPika: Restore notice with next date.

The next SoylentNews PBC Board of Directors meeting will be on Wednesday, September 3 at 23:00 UTC (7:00pm EDT) in [irc://irc.sylnt.us/staff #staff] ([ircs://irc.sylnt.us:6697/staff SSL]) ([http://irc.sylnt.us/?channels=#staff Webchat]).

MediaWiki:Sitenotice

2014-08-26T23:32:46Z

FunPika: Meeting over.

MediaWiki:Sitenotice

2014-08-25T00:48:33Z

FunPika: Might as well just advertise the meeting here too.

The next SoylentNews PBC Board of Directors meeting will be on Tuesday, August 26 at 23:00 UTC (7:00pm EDT) in [irc://irc.sylnt.us/staff #staff] ([ircs://irc.sylnt.us:6697/staff SSL]) ([http://irc.sylnt.us/?channels=#staff Webchat]).

File:Irciv.png

2014-08-22T23:17:11Z

FunPika: added Category:IRC using HotCat

[[Category:IRC]]

File:Windows-Geany-Sidebar.png

2014-08-22T23:16:27Z

FunPika: added Category:Development using HotCat

The lightweight Geany IDE has a very useful "SideBar" to the left of your screen that will show all Packages, Sub-procedures, Variables and etc. for easy navigation of large code.

Geany's SideBar can show Documents (Project files) and Inspect the currently open file.

[[Category:Development]]

File:Windows-Eclipse-Navigator.png

2014-08-22T23:15:58Z

FunPika: added Category:Development using HotCat

The Eclipse IDE with the EPIC plug-in installed has a powerful "Navigator" panel to the left of your screen that will show all Packages, Sub-procedures, Variables and etc. for easy navigation of large code-bases.

Aside: Eclipse is also actively checking dependent files and is indicating that there's is over 100 issues with interdependencies in the Plugins folder.

[[Category:Development]]

Board Meetings Rules of Order

2014-08-22T23:11:31Z

FunPika: added Category:Board of Directors using HotCat

==Board Meeting - Rules of Order==
This is first DRAFT of a guide to running [[SoylentNews_PBC_Board_of_Directors|Board Meetings of SoylentNews PBC]].

==Overview:==
This document lays out guidelines for conducting Board Meetings of SoylentNews PBC.
Its intent is to facilitate an open and efficient meeting whereby input is solicited and decisions can be made in a cordial and effective manner.
It is presented here as a guide, steps that are suggested as a means to conduct meetings. In the course of running a meeting, it may be necessary, at the chair's discretion, to deviate from this format.

==Steps in the Running of a Meeting:==
These are the primary steps of running a board meeting:

===Call to Order / Open the Meeting===
This step in the proceedings serves an important function in notifying the attendees that the meeting is starting. It is a time to end idle chit-chat and embark on official proceedings.

The Chair introduces himself/herself and calls the meeting to order.

===Board Meeting vs Staff Meeting===
This step is important so as to set the tone of the meeting. Whereas a Staff Meeting has a potentially large number of participants who can vote, at a Board Meeting, only Board Members may do so.

The Chair states this is a Board Meeting and that only official Board Members are permitted to vote.

===Take Attendance===
For an official Board Meeting to take place according to the Bylaws, there must be a quorum of Board Members. To ascertain this, the Chair takes attendance by position and asks for each Board Member to introduce themself.
<ol>
<li>President
<li>Treasurer
<li>Secretary
</ol>

===Verify Quorum===
In order for the Board Meeting to proceed there must be a quorum. The Chair quotes the relevant passage from the Bylaws and verifies that a quorum is present, so that the meeting may proceed.

The Chair verifies that a quorum is present.

===Verify Meeting is Valid===
In order for a Board Meeting to be valid, (TODO: may be incorrect word; verify) there must have been sufficient advance notice to the Board Members, or, lacking adequate advance notice, all Board Members being present, agree to hold the meeting.

The Chair verifies that proper advance notice has been given.

If proper advance notice has not been given, the Chair then asks each Board Member if they are willing to proceed with the meeting and have no objections to doing so.

===Minutes of the Last Board Meeting===
For the record, the Chair reports on the minutes of the last Board Meeting, and any decisions which were made at that time. These will have been independently sent via e-mail to each Board Member and accepted as valid, also by e-mail.

===Present the Agenda===
To keep the Board Meeting on track, it is important to present an agenda that has been agreed upon in advance.

To facilitate discussion, each agenda item should be numbered sequentially so it can be easily referred to.

The Chair presents the Agenda to the Board.

===Process Agenda Items - motions, discussion, and votes===
The foregoing items were a necessary preparation for the real work to be performed during the Board Meeting.

===For Each Agenda Item:===
<ol>
<li>The Chair presents the Agenda Item to the Board.
<li>The Chair opens the floor for discussion.
It is incumbent upon the Chair to try and keep the discussion on topic sufficiently so that progress is made, yet not be so authoritative as to thwart discussion. It is a delicate balance that requires courtesy, gentleness, kindness, and firmness.

It may serve to just let the discussion run as it will. If things get heated, confrontational, or too intertwined to easily follow the discussion, the Chair may need to be more direct. In such a case, each person who wishes to speak should request the Floor from the Chair. The Chair will use his/her best judgement but would generally grant the Floor to requesters in the order requested. Each person will have their opportunity to present their input. At the conclusion of which, the speaker should cede the Floor. Failing that, the Chair may ask the speaker if they cede the Floor.

<li>The Chair asks if someone would like to present a motion.
<li>The Chair summarizes the motion and presents it to the Board for further discussion, if necessary.

No new Motions may be entertained until the current Motion is handled.

Board Members may choose to:
<ol>
<li>Table the Motion until the next Board Meeting.
Oftentimes this comes with an agreement that a Board Member or assignee will take responsibility for investigating something and bringing their findings back to the Board.
<li>Offer and agree to an amendment to the motion.
 (This requires a Second and a vote in the affirmative to proceed.)
<li>Vote on the Motion.
</ol>
<li>If the Motion is still pending, the Chair again puts the Motion before the board and asks the Board Members to vote "Aye" to vote in favor of the Motion or vote "Nay" to vote against the Motion.
<li>The Chair tallies the vote and reports the Board's decision.
<li>TODO: If there is a tie, does the Chair have a vote to break the tie?
</ol>

===New Business===
In the course of the foregoing discussion other items may come up which the Board may wish to address. Further, there may have been new items of business that came up since the time that the Agenda was established.

Whatever the case, the Chair inquires if there is any New Business to be discussed.
<ul>
<li>If there is no New Business, then proceed to the next heading and "Summarize the Meeting".
<li>If there is New Business, the Chair follows the steps outlined in the preceding section For Each Agenda Item.
</ul>

===Summarize the Meeting and, if any, the Assignments===
At this point, the Chair summarizes the Motions decided, the decisions made, and who has been assigned responsibility for each of them.

===Adjourn===
<ul>
<li>The Chair asks if there is a Motion to Adjourn.
<li>The Chair asks for a Second.
<li>Upon receipt of a Second, the Chair puts it up to a vote to Adjourn the meeting.
<li>The Chair announces "the Meeting is Adjourned".
</ul>

[[Category:Board of Directors]]

Issues to Be Raised at the Next Board Meeting

2014-08-22T23:11:21Z

FunPika: added Category:Board of Directors using HotCat

If there is an issue that you would like to be raised at the next Board meeting, please include it in the list below. The list will be cleared following each meeting. If you feel that your issue was not adequately addressed at the meeting, please feel free to add it to the list again, with additional detail as needed, and it will be raised at the following meeting.

==Next meeting==
Time: Sunday, August 24, 23:59 UTC (7:59pm EDT) 
Place: irc.sylnt.us:6667/6697#staff ([http://50.116.18.95:3989/ Webchat]) 
Chair: To Be Determined

==Issues==
* Issue 1:
* Issue 2:
* Issue 3:

[[Category:Board of Directors]]

SoylentNews PBC Board of Directors

2014-08-22T23:11:09Z

FunPika: added Category:Board of Directors using HotCat

==Introduction==

The Board of Directors of SoylentNews PBC (the "Corporation") has general responsibility for managing the business of the Corporation. The Board derives its powers from the Bylaws of the Corporation, Article III ("Directors"), Section 1 ("Powers"):

<blockquote>"The business of the Corporation shall be managed by or under the direction of a Board of Directors who may exercise all the powers of the Corporation except as otherwise provided by law, by the Certificate of Incorporation, or by these Bylaws."</blockquote>

The Board elects Officers (President, Treasurer, Secretary, etc.), and makes other decisions, usually focusing on issues that may have financial or legal consequences for the Corporation, (e.g., opening bank accounts, issuing shares of stock, etc.).

==Board Meetings==

The Board holds meetings, usually on SoylentNews's IRC #staff channel (http://chat.soylentnews.org/). Logs of these meetings are linked below.

All users and members of the public are invited to attend Board Meetings. However, to maintain order, and depending on attendance at any given meeting, not all attendees may be given .voice.

If there is an issue that you would like to be raised at the next Board meeting, please edit the following page to include your issue:

[[Issues_to_Be_Raised_at_the_Next_Board_Meeting|Issues to Be Raised at the Next Board Meeting]]

==Board Meeting Minutes==
[[Board_of_Directors_Meeting_-_July_8,_2014|Board of Directors Meeting - July 8, 2014]]

[[Board_of_Directors_Meeting_-_July_16,_2014|Board of Directors Meeting - July 16, 2014]]

[[Board_of_Directors_Meeting_-_August_20_2014|Board of Directors Meeting - August 20, 2014]]

[[Board_of_Directors_Meeting_-_August_21_2014|Board of Directors Meeting - August 21, 2014]]

==Procedure and "Rules of Order"==

[[Board_Meetings_Rules_of_Order|Board Meetings Rules of Order]] - Policies and procedures for conducting board meetings ('''note:''' this is a draft)

[[Category:Board of Directors]]

Category:Board of Directors meetings

2014-08-22T23:10:55Z

FunPika: Make subcategory of Category:Board of Directors.

This category contains the logs of all past [[SoylentNews PBC Board of Directors|Board of Directors]] meetings.

[[Category:Board of Directors]]

Category:Board of Directors

2014-08-22T23:10:21Z

FunPika: Create category for all other Board related pages, will also add the meetings category as a subcategory.

This category contains any pages related to the [[SoylentNews PBC Board of Directors|Board of Directors]].

[[Category:Categories]]

Wiki

2014-08-21T20:22:44Z

FunPika: /* Documentation */

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin
| UTC-4 (EST/EDT)
|-
| Cactus
| admin/bureaucrat
| ?
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

== Todo ==

* Upload existing externally hosted images onto the wiki.
* Install more anti-spam extensions if needed
* When MediaWiki 1.23.0 is released (likely late April), remove the <code>$wgPhpCli = false;</code> line from LocalSettings.php, since it should no longer be necessary. [[mediawikiwiki:Manual:Job queue]]

== Documentation ==
* The wiki is hosted on [[Beryllium]].
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

Wiki

2014-08-21T20:22:33Z

FunPika: /* Documentation */ Change "service linode" link to Beryllium.

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin
| UTC-4 (EST/EDT)
|-
| Cactus
| admin/bureaucrat
| ?
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

== Todo ==

* Upload existing externally hosted images onto the wiki.
* Install more anti-spam extensions if needed
* When MediaWiki 1.23.0 is released (likely late April), remove the <code>$wgPhpCli = false;</code> line from LocalSettings.php, since it should no longer be necessary. [[mediawikiwiki:Manual:Job queue]]

== Documentation ==
* The wiki is hosted on the [[Beryllium]]
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

Wiki

2014-08-21T20:15:57Z

FunPika: /* Dependencies */ Remove version numbers that aren't really important. Add some PHP extensions that MediaWiki uses.

==Welcome==
This wiki serves many purposes including documentation, useful links, and team contacts. Suggestions have been made that would greatly expand the scope of the wiki. If you'd like to become officially involved or have any questions contact '''wiki@soylentnews.org'''. Also, if you are on IRC you can look for FunPika (who leads this team) or mrcoolbp.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Wiki|Wiki Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| FunPika
| Leader
| UTC-4 (EST/EDT)
|-
| mrcoolbp
| admin
| UTC-4 (EST/EDT)
|-
| Cactus
| admin/bureaucrat
| ?
|-
| cosurgi
| admin
| UTC+2 (CEST)
|}
<section end=whoarewe />

== Todo ==

* Upload existing externally hosted images onto the wiki.
* Install more anti-spam extensions if needed
* When MediaWiki 1.23.0 is released (likely late April), remove the <code>$wgPhpCli = false;</code> line from LocalSettings.php, since it should no longer be necessary. [[mediawikiwiki:Manual:Job queue]]

== Documentation ==
* The wiki is hosted on the [[Soylent-services|service linode]]
* MySQL password is in the wiki's LocalSettings.php file.
* Documentation for the recent changes IRC bot is at [[WikiRC]].

=== Responsibilities ===
* At the moment we are mainly just dealing with spam, vandalism, etc. that shows up on the wiki.

=== Competencies ===
* Familiarity with how MediaWiki works (manual is [[mediawikiwiki:Help:Contents|here]]).

== Dependencies ==
See also [[Special:Version]] for automatically generated information about what software the wiki is running.
* MediaWiki {{CURRENTVERSION}} (most recent [https://git.wikimedia.org/branches/mediawiki%2Fcore.git stable branch] (ex. REL1_23))
* Apache2
* PHP
** apc extension
** iconv extension
** intl extension
** mbstring extension
** mysql extension
** zlib extension
* MySQL
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

[[Category:Teams]]
[[Category:Wiki]]

Category:Board of Directors meetings

2014-08-21T20:03:01Z

FunPika: added Category:Categories using HotCat

This category contains the logs of all past [[SoylentNews PBC Board of Directors|Board of Directors]] meetings.

[[Category:Categories]]

Staff Meeting 21 August 2014

2014-08-21T20:02:29Z

FunPika: added Category:Staff meetings using HotCat

Log of staff meeting held on IRC in channel #Staff on 2014-08-21 from 01:06 to 02:52 UTC:

[01:06:13] * juggs motions 1st point of agenda for staff meeting 1. Staff meetings should not tag on board meetings. No-one likes to be summoned to a meeting 2 hours early. 
[01:07:15] <NCommander> paulej72: no ;.; 
[01:07:20] * NCommander needs food at some point 
[01:07:24] <NCommander> I think we're ready to go 
[01:07:36] <NCommander> juggs: the point been made 
[01:07:40] <NCommander> And will be honored 
[01:08:17] <Bytram> juggs: already agreed. see: <a href="http://logs.sylnt.us/%23staff/2014-08-21.html#00:56:51" target="_blank">http://logs.sylnt.us</a> 
[01:08:28] -!- LaminatorX [LaminatorX!~470ab0b6@23-00-716-777.dhcp.stls.mo.charter.com] has joined #staff 
[01:08:33] <juggs> who's chairing, who's minuting, what's on the agenda? 
[01:08:58] * NCommander will chair 
[01:09:02] <NCommander> volunteers for minuting? 
[01:09:05] * LaminatorX will be back once he puts his kids to bed. 
[01:09:09] <Bytram> I'd be happy to chair, but I don;tknow what's on the agenda 
[01:09:15] <Bytram> :/ 
[01:09:26] <juggs> I don't think we have an agenda 
[01:09:56] <Bytram> if I have an agenda to work from, I'll chair and minute. 
[01:10:13] <NCommander> I don't think we have an agenda, I was planning to just go to everyone and ask what they wanted to discuss 
[01:10:28] <TheMightyBuzzard> Bytram, just minute. 
[01:10:40] <Bytram> TheMightyBuzzard: okay. 
[01:10:47] <NCommander> So, lets go right down the list 
[01:10:54] <NCommander> audioguy: floor is yours, anything to bring up? 
[01:10:58] <audioguy> Agenda item: further discusssion of the pressing issue of stock, with emphasis on looking for specific solutions to contribute to the board 
[01:11:13] * TheMightyBuzzard kicks audioguy 
[01:11:25] <audioguy> Or has everyone had enough? 
[01:11:29] <Bytram> $buritto audioguy 
[01:11:59] * NCommander whacks audioguy 
[01:12:04] * matt_ is ready for more =) 
[01:12:05] <NCommander> Its a fair point though 
[01:12:07] <TheMightyBuzzard> audioguy, is a meeting about it tomorrow. might as well save it until then. 
[01:12:24] <audioguy> OK, I guess never mind that :-) 
[01:12:24] * NCommander loves long discussions, was great in debate class <g> 
[01:12:45] <paulej72> NCommander: you a master debater 
[01:13:01] <NCommander> paulej72: also known as being stubborn 
[01:13:05] <juggs> Agenda item: Team leads who are long time absent from position. It should be up to team leads to bring matters to staff meetings, that is not possible with absent team leads. 
[01:13:22] <NCommander> juggs: will bring that up after going through everyone 
[01:13:26] <audioguy> All I really have is some stuff related to possible virtual server changes, which are probably best left to a dev meeting, in the imnterest not not boring others to death 
[01:13:27] <NCommander> audioguy: if nothing else, I'm moving on 
[01:13:32] <NCommander> Ok 
[01:13:35] <paulej72> I am the team leader for most of the groups 
[01:13:39] <NCommander> Azrael: anything to bring up? 
[01:13:46] -!- LaminatorX has quit [Quit: Web client closed] 
[01:13:55] <juggs> paulej72, yep that makes sense. 
[01:14:29] <audioguy> One possibbility - the situation with abuse of unicode. 
[01:14:46] <audioguy> (cross teams ) 
[01:15:27] <Bytram> audioguy: good point; i've seen several (as in maybe a dozen or two) such posts... which were downmodded to oblivion =) 
[01:15:29] <TheMightyBuzzard> audioguy, i think pj mostly handled that already. no more vertical overflow. 
[01:15:54] * NCommander mulls 
[01:15:56] <TheMightyBuzzard> it now takes up no more space than the same # of lines of ascii text would 
[01:15:58] <NCommander> Maybe we shold go by team 
[01:16:01] <NCommander> It will be more effective 
[01:16:09] <NCommander> But lets bring up the UTF-8 stuff while we're here 
[01:16:22] <Bytram> audioguy: fwiw, I tried to go 'outside' the comment box with &rtl; and &ltm; and variants and could not do so on dev.soylentnews.org 
[01:16:32] <audioguy> So the plan is justy let them be modded down? I am a little woried about spammers posting ads in foeigjn languages and linking to them in emails, that sort of thing 
[01:16:33] <NCommander> There's bene an uptick in downmods since the update landed 
[01:16:36] * Bytram hasn't tried it on production 
[01:17:08] <NCommander> audioguy: I'm open to ideas to preventing more abuse on this front. I don't want to loose the feature, especially since its long been a sticking point at the other site 
[01:17:16] <audioguy> I assume javascript is already not permitted. 
[01:17:40] <NCommander> audioguy: the javascript rule is that it has to fallback sanely 
[01:17:43] <Bytram> audioguy: I tried it a few times, could not get it past the filters... TheMightyBuzzard -- what say you? 
[01:17:44] <TheMightyBuzzard> audioguy, permitted... well you can put some in but it will just show as source. 
[01:17:46] <paulej72> slash has a white list of tags 
[01:18:08] <paulej72> <script> will get removed 
[01:18:21] <Bytram> audioguy: are you talking about javascript in URLs? 
[01:18:31] <audioguy> I don't want to lose it either, just trying to fimd out if we need to deal with this new world better. Also wondering: what if people enage in exteneded conversations in a foeign language, is this an 'English' site 
[01:18:44] <audioguy> or in the text 
[01:18:53] <Bytram> audioguy: e.g.: <a href="jaascript: blah blah blah">stuf<a/> 
[01:19:14] <audioguy> What if jihadis start postimng stuff in rabic that is extremely imflammatory, etc. 
[01:19:17] <TheMightyBuzzard> Bytram, links are stripped of script tags 
[01:19:20] <Bytram> well, you get the idea; I could not get that kind of stuff past the filters. 
[01:19:22] <NCommander> audioguy: well, at some point, I want to see user-created nexuses/ ala subreddits 
[01:19:27] <NCommander> Which should allow non-English 
[01:20:03] <Bytram> audioguy: "The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way. " 
[01:20:17] <Bytram> appears following *ever* story... 
[01:20:18] <audioguy> Some of these characters can also be used to create misleading links htt alook ok but actually go somewhere else - are links forced to 7 bit? 
[01:20:32] <NCommander> audioguy: moot point, we now have unicode URLs 
[01:20:33] <Bytram> as for the stories themselves, i think the Ediors can handle that. =) 
[01:20:35] <paulej72> audioguy: that one we have to fix 
[01:20:44] <TheMightyBuzzard> audioguy, idn links are currently broken. nothing but ascii gets through. 
[01:20:51] <Bytram> audioguy: ^^^ 
[01:21:01] <TheMightyBuzzard> so once we fix it that can become an issue but not yet 
[01:21:04] <Bytram> idn == International Domain Names 
[01:21:09] <audioguy> I think that is GOOD, ascii only. (for links) 
[01:21:26] <NCommander> audioguy: except that its perfectly valid now to have non-ascii URLs -_-; 
[01:21:26] <TheMightyBuzzard> s'actually not. i'd like the code to support IDNs 
[01:21:34] <Bytram> atm, yes, but will be a problem down the line. Whole rat's nets of issues to watch for. 
[01:21:34] <paulej72> I think we will have an indicator that a link contains urf 
[01:21:39] * NCommander would love to see the ability to load the UI in other languages 
[01:21:52] <audioguy> Few in use yet though. 
[01:21:57] <TheMightyBuzzard> paulej72, not yet but it was proposed. 
[01:22:15] <paulej72> TheMightyBuzzard: “will have” 
[01:22:26] <Bytram> at this point, I just want to take a moment to publicly thank TheMightyBuzzard for all his hard work blugeoning slashcode into handling UTF-8 characters. 
[01:22:29] <TheMightyBuzzard> stupid eyeballs, betraying me again 
[01:22:41] <NCommander> audioguy: point taken 
[01:23:03] <TheMightyBuzzard> Bytram, all part of my master plan to hurry up meta-moderation 
[01:23:08] <audioguy> HELL YES! Good going, of mighty bird! 
[01:23:09] <Bytram> lOL! 
[01:23:12] <NCommander> Right now, lets just keep an eye on it. The new CSS fixes shold prevent the worst of the abuse, and if it gets even worse, then we take more drastic steps 
[01:23:13] <NCommander> k? 
[01:23:24] <TheMightyBuzzard> sounds good 
[01:23:26] <paulej72> NCommander: that would be really hard to do, but not impossible. You would need to pull out all of the text in the templates an put them into lookup templates 
[01:23:41] <NCommander> paulej72: nah, just plug gettext into template tool 
[01:23:49] <NCommander> Pretty sure thats already supported 
[01:23:50] <TheMightyBuzzard> you admin types always have the banhammer if necessary 
[01:23:51] * Bytram is reminded of the page-widening trolls of the other site... we'll deal with 'em as they come up; can't plan for *everyuthing* 
[01:24:01] <NCommander> paulej72: its a future thing now 
[01:24:12] <NCommander> My immediate priority is porting this hot mess to Apache 2 
[01:24:20] <NCommander> Which is the last of the major shit to get me to sleep at nice 
[01:24:21] <NCommander> *night 
[01:24:35] <juggs> *nite 
[01:24:50] <paulej72> *day 
[01:24:55] <NCommander> ............. 
[01:24:59] <Bytram> NCommander: the benefit being... we can to a realse that is supported? (.e.g security fixes) 
[01:24:59] <NCommander> you guys suck 
[01:25:09] <NCommander> Bytram: bingo 
[01:25:13] <NCommander> And more recent perl 
[01:25:23] <NCommander> We're still stuck on 5.10, which I know caused pain in unicode world 
[01:25:31] <TheMightyBuzzard> perl++ 
[01:25:31] <Bender> �karma - �perl: 1 
[01:25:57] -!- LaminatorX [LaminatorX!~470ab0b6@23-00-716-777.dhcp.stls.mo.charter.com] has joined #staff 
[01:25:57] <Bytram> elephant in the living room here: how are we going to regression test everything? 
[01:26:24] <Bytram> or, do we let the community do the alpha testing when we roll it out? 
[01:26:28] <NCommander> Bytram: usual matter, upgrade on a weekend and collect the bits as users step on landmines 
[01:26:29] <audioguy> users, like evderyone else does. :-) 
[01:26:31] <paulej72> on prod, let the users find the bugs 
[01:27:03] <Bytram> ugh. 
[01:27:08] <audioguy> I see great agreement on this. :-) 
[01:27:15] <Bytram> LOL, but ugn. *UGH*!!!!!!! 
[01:27:25] <NCommander> That's why we have a community, right? 
[01:27:25] <TheMightyBuzzard> Bytram, you're our resident bug hunter. you can break anything. 
[01:27:47] <NCommander> Ok, so I think we've covered UTF-8, Apache2 
[01:27:49] <Bytram> You have *no* idea; them bugs *swarm* me, I tells ya! 
[01:28:01] <NCommander> I had some editoral stuff to bring up, but without a LaminatorX ... 
[01:28:11] <prospectacle> what about test.soylentnews.org for enthusiastic breakers-of-things to break things in the soon-to-be-released, and report what they broke via submitting an article 
[01:28:18] * LaminatorX has returned. 
[01:28:25] <paulej72> yeah ugh, but I have tried to have people find bugs on dev, but no love. Even when testing on staff, there was till bugs that we did not find until deploy on prod 
[01:28:27] <NCommander> prospectacle: that causes bad juju 
[01:28:36] * NCommander remembers improved threading 
[01:28:38] <NCommander> >.<; 
[01:28:44] <TheMightyBuzzard> prospectacle, dev is generally usable for that. your account on live will likely let you log in there. 
[01:28:53] <prospectacle> ok thanks 
[01:28:58] <NCommander> at some point, we need to refresh dev's database 
[01:29:04] <paulej72> unless it is newer than April 
[01:29:06] <NCommander> Ok, so UTF-8, Apache2 
[01:29:10] <NCommander> Anything else on the dev side? 
[01:29:17] <TheMightyBuzzard> yep, i got a few 
[01:29:19] <Bytram> prospectacle: heads up, though... it's hard to tell what has been merged into it at any given time. 
[01:29:53] <prospectacle> Does the general public know about dev? I mean some weird people might like trying to find bugs. 
[01:29:56] <TheMightyBuzzard> 14.10: any objections to it being mostly a minor and quick bug/issue release? 
[01:30:13] <TheMightyBuzzard> clear off a hell of a lot of small ones and leave the biggies for 14.12? 
[01:30:23] <paulej72> none here, and I have lots of bug fixes 
[01:30:33] <NCommander> TheMightyBuzzard: I'd like to land the Apache2 upgrade if finished in 14.10 
[01:30:36] <LaminatorX> An occasional dev shutout on site news wouldn't be a bad thing. 
[01:30:41] <NCommander> prospectacle: its been brought up a few times 
[01:30:41] <paulej72> or 14.!3 
[01:30:55] <TheMightyBuzzard> NCommander, i'd like to land m2 in there too but i see it running long like unicode did. 
[01:31:26] <NCommander> TheMightyBuzzard: land it, but ship disabled 
[01:31:28] <NCommander> Not a big issue 
[01:31:31] <Bytram> NCommander: and I brought up some ideas on basic moderation with TheMightyBuzzard this AM, which might compound the situion 
[01:31:44] <paulej72> NCommander: tackel Apache 2 if you want the rest or use will do the minor bug fixes 
[01:31:48] <NCommander> Bytram: we need to compare notes, as I had thoughts for moderation that I've yet to get implemented 
[01:31:54] <NCommander> but apache2 is a big sticker 
[01:31:56] <TheMightyBuzzard> okay, item 2: that^^ 
[01:31:58] <Bytram> NCommander: works for me. 
[01:32:14] * NCommander nods 
[01:32:18] <NCommander> Anything else on dev? 
[01:32:18] <TheMightyBuzzard> moderation changes in prep for m2. those would also fit well in with a light release. 
[01:32:25] <TheMightyBuzzard> one more 
[01:32:52] <TheMightyBuzzard> ddns for subscribers. pitched it to audioguy the other day and he was generally in favor. 
[01:33:06] <Bytram> TheMightyBuzzard: ddns? 
[01:33:19] <NCommander> dyanmic dns? 
[01:33:25] <Bytram> .topic Staff meeting in progress. 
[01:33:25] juggler changed topic of #staff to: Staff meeting in progress. 
[01:33:31] <TheMightyBuzzard> dynamic dns. like get a hostname of bytramlikescheese.ddns.soylentnews.org that's always yours. 
[01:33:36] <paulej72> is there an open source ddns cleint 
[01:33:42] <TheMightyBuzzard> several 
[01:33:53] <LaminatorX> As in, my host.soylentnews.org? 
[01:34:01] <audioguy> This is easy to do just with bind config files. 
[01:34:04] <Bytram> TheMightyBuzzard++ interesting. *always* mine? You mean so long as I continue my subscription? =) 
[01:34:04] <Bender> �karma - �themightybuzzard: 1 
[01:34:15] <paulej72> I would use another domin for that stuff. 
[01:34:25] <TheMightyBuzzard> LaminatorX, probably need to make it whatever.ddns.soylentnews.org to avoid confusion 
[01:34:26] <audioguy> agreed ^^ 
[01:34:34] <audioguy> another domain. 
[01:34:36] <TheMightyBuzzard> or our shortening domain 
[01:34:44] * NCommander isn't 100% sure this is useful, but ok :-) 
[01:34:46] <paulej72> no not the .us one 
[01:34:48] <LaminatorX> Sylnt.us then 
[01:34:56] <LaminatorX> Or not 
[01:35:04] <paulej72> too many restrictions on that domain 
[01:35:07] <Bytram> TheMightyBuzzard: I like the idea of "whatever.ddns.soylentnews.org" as it will provide us free 'advertising' for the main site 
[01:35:17] <TheMightyBuzzard> NCommander, it's not especially. think of it as another gold star. 
[01:35:19] <audioguy> We have a lot of domains already voted as 'winners' 
[01:35:33] <NCommander> indeed 
[01:35:41] <paulej72> Bytram: that could lead us to being blocked by different spam lists 
[01:35:52] <TheMightyBuzzard> fair point 
[01:35:52] <NCommander> Let's try and get togheter a need/want/wish list for the next two releases 
[01:35:59] <NCommander> Put it on the wiki/brainstorm/etc. 
[01:35:59] <audioguy> Subscribers only. 
[01:36:05] <Bytram> paulej72: yeah, you're right. darn! 
[01:36:35] <TheMightyBuzzard> s'it for me. 
[01:36:38] <NCommander> k 
[01:36:40] <audioguy> Aother is to allow people to use us as slave, those are always needed and trivial to do. 
[01:36:42] <NCommander> I think that covers dev 
[01:36:57] <paulej72> I have sysop stuff 
[01:37:39] <audioguy> go 
[01:37:45] <NCommander> Lets go to sysop 
[01:37:45] <NCommander> paulej72: 
[01:37:51] <paulej72> We need to get our documentation up to date. I have spent too much time trying to fix things recently and I had no idea where the shit was 
[01:38:12] <audioguy> Ok: here is what I have in the works: 
[01:38:24] <paulej72> I know I am guilty of not documenting, so I am trying to fix this up. 
[01:38:33] * NCommander is semi-guilty on this 
[01:38:43] <NCommander> BIggest thing I need to document is the backup mechanism 
[01:38:57] <audioguy> I am just finishing up some dns stuff and have a backlog of notes. I want to finish the twiki install next, and move suitable stuff over to it. I think that will help 
[01:39:19] <paulej72> audioguy: whcih system did you install twiki on 
[01:39:35] <audioguy> Thsi will give us a place to put slightly mnore sensitive stuff than the public wiki 
[01:39:56] <audioguy> It isn't yet, really, I want ot pom staff ,achjine boron. 
[01:40:01] <audioguy> want it on 
[01:40:13] <audioguy> (this is limited to staff) 
[01:40:15] <paulej72> ok 
[01:40:51] <paulej72> I think we should go ahead with the plan to move stuff off of bery and move ti to boron and carbon as appropriate. 
[01:41:07] <audioguy> I will send a note to either stafflist or admin list with more details when the time comes 
[01:41:25] <paulej72> nitrogen could be moved to as well, but I was think of using that as a backup irc server. 
[01:42:00] <NCommander> I'll be happy retiring bery 
[01:42:07] <audioguy> re that move - I have been wanting to chamge main mail comfig for a while, this is a golden opportunity to just move that to the existing mail server on boron. This is all low usage staff mail 
[01:42:09] <NCommander> That machine has long been the odd man out 
[01:42:30] <NCommander> audioguy: do wait a bit before doing that 
[01:42:40] * NCommander is going to upgrade boron to 14.04 this week 
[01:42:44] <Bytram> paulej72: is there some kimd of report which gives system 'stats' on each of our servers? CPU Usage, RAM Usage, Swap, etc.? Would be nice to get a daily report. 
[01:42:48] <audioguy> I don't do such things without a preannounce and clear plan. 
[01:42:55] <NCommander> audioguy: cool :-) 
[01:43:05] <NCommander> Bytram: there was icinga 
[01:43:09] <NCommander> We should probably resurrect that 
[01:43:10] <audioguy> unlike SOME around here. :-) 
[01:43:22] <paulej72> NCommander: when I mentioned to xlefay about setting up a backup irc on nitrogen he mention that we should move that server to the London DC. 
[01:44:03] <paulej72> icina is still there, I just cant figure out how to set it up. 
[01:44:15] <Bytram> NCommander: not just *was*, still is: <a href="https://sentinel.soylentnews.org/" target="_blank">https://sentinel.soylentnews.org</a> 
[01:44:50] <NCommander> oh, it got fixed 
[01:44:50] <paulej72> lright now it give an error on carbon, because I switch the default webserver to nginx. 
[01:44:53] <NCommander> sentinel poofed for awhile 
[01:45:12] <Bytram> NCommander: yup, but it was un-poofed. 
[01:45:24] <paulej72> plus the new severs are not bein monitored 
[01:45:34] <NCommander> ugh 
[01:45:48] <NCommander> FIxing that last bit would be relatively easy 
[01:46:53] <audioguy> Do we NEED icinga? Has it EVER solved a problem or found one for us that was not already knoen? 
[01:47:02] <audioguy> known 
[01:47:10] <Bytram> From what I can tell, icinga is more about watching/checking for things running or not; does not give system 'loads'. 
[01:47:18] <NCommander> adding loads won't be hard 
[01:47:25] <NCommander> YOu can report anything via shell scripts and such 
[01:47:26] <juggs> mrtg 
[01:47:33] <NCommander> If someone wants to go through and setup nagios or mrtg though 
[01:47:35] <NCommander> be my guest 
[01:47:45] <audioguy> When something stops running we get pretty fast feedback from users. 
[01:47:58] <paulej72> igcina was xlefay’s baby 
[01:48:14] <juggs> NCommander, why are you not recommending Landscape? 
[01:48:19] <juggs> ;) 
[01:48:36] <audioguy> Landscape was running too 
[01:48:41] <Bytram> okay, I forgot... what was it we were discussing? 
[01:48:44] <audioguy> how many do we need? 
[01:48:52] <juggs> quite 
[01:49:21] <paulej72> consoldating servers and monitoring 
[01:49:23] <NCommander> juggs: because I'm going to be leaving my employeer soon, and unliekly to get it for free :-P 
[01:49:42] <juggs> rsyslog, snmp trap it - it doesn't matter. Make a fucking decision how you are going to monitor load and do it. 
[01:49:57] <juggs> And set alerts 
[01:50:07] <NCommander> Right, so moving onto consoldating stuff 
[01:50:11] <audioguy> How about real sysadmins actually checking logs 
[01:50:17] <NCommander> or not 
[01:50:21] <Bytram> ummm, what was decided on documenting the systems? 
[01:50:35] * NCommander coughs 
[01:50:40] <NCommander> Sorry, I got distracted 
[01:50:44] * Bytram offers another lozenge 
[01:50:44] <NCommander> On the documentation front 
[01:50:46] <paulej72> NCommander: needs to bust out his fast keyboard 
[01:51:02] <NCommander> I have: document backup systems (NCommander), document other stuff (paul) 
[01:51:09] <NCommander> probably need to be more specific on identifying doc gaps 
[01:51:12] <Bytram> got it. thank 
[01:51:41] <Bytram> paulej72: whenever you find an area lacking docs, can you just add it to some central place, like on the wiki? 
[01:51:48] <audioguy> backup system a good start 
[01:52:05] <paulej72> we should copy key config files for all of our services and put them in twiki 
[01:52:25] <audioguy> Yes, I will start doig that once I have it set up. 
[01:52:35] <Bytram> not the documention itself, but at least start a list of areas which are lacking. 
[01:52:42] <Bytram> great! 
[01:52:44] <paulej72> Bytram: that would almost be as much work as fixing the docs 
[01:53:05] <audioguy> I believe some documentaion belogs in the connfig files, so it is handy when needed. 
[01:53:14] <audioguy> config files 
[01:53:59] <NCommander> What is needed is a list of where we got coverage gaps 
[01:54:00] <Bytram> I don't much care *where*, but if there were one place where you could note when you stumble on an area that is deficient, it can (eventually) get tackled 
[01:54:13] <paulej72> Plus we need to make sure all of our system have the same settings where possible and proper fallbacks. Lithium was not setup with both ldap and kerberos servers 
[01:54:29] <Bytram> NCommander: exactly. Rather than a massive search, just build up a list over time as we stumble over the gaps. 
[01:54:39] <audioguy> The main wiki for now, until I get twiki fully up. (few days, finishing some stuff on dns) 
[01:55:46] <NCommander> anyone volunteering to take that list? 
[01:55:48] * NCommander sees himself somewhat swamped for the rest of the week 
[01:55:52] <NCommander> *take to compiling 
[01:56:35] <paulej72> I have been working through the sysamin wiki pages so I can put down what is missing. 
[01:56:38] <audioguy> I am doing this as I move through various things, but we all see different views of the system as we work on different things. 
[01:56:53] <audioguy> MAke a page for 'missing docs' there 
[01:56:54] <Bytram> NCommander: I'd say just grow it organically. Just note it when you find it... maybe toss in a sentinel string "HERE NEED BE DOCUMENTATION" and move on. 
[01:56:55] <NCommander> Alright 
[01:57:05] <NCommander> ONe last note 
[01:57:14] <NCommander> Any object if I upgrade boron to 14.04? 
[01:57:15] -!- LaminatorX_ [LaminatorX_!~470ab0b6@23-00-716-777.dhcp.stls.mo.charter.com] has joined #staff 
[01:57:21] * NCommander is likely going to do it tongiht 
[01:57:50] <Bytram> what's on it ? and what depends on what it is running? and what does boron depend on, too? 
[01:57:51] <paulej72> yes, I want the backup docs wirten first. 
[01:58:05] <audioguy> is the other dns machine fully finctional? We need at least one functional dns for the li domain to work. 
[01:58:15] -!- LaminatorX has quit [Ping timeout: 244 seconds] 
[01:58:34] <audioguy> we all log in on boron. Just don't mess that one up. :-) 
[01:58:35] LaminatorX_ is now known as LamnatorX 
[01:58:37] <NCommander> audioguy: helium is fully operational again 
[01:58:43] <NCommander> so LDAP/DNS is fine 
[01:58:48] <NCommander> paulej72: ask and you shall receive 
[01:59:00] <audioguy> main concern is logioms then, I think 
[01:59:01] <paulej72> SystemAdministration/Backups 
[01:59:04] <audioguy> logins 
[01:59:29] <NCommander> audioguy: you can get in via linode console worst case scenario, and I can setup a different box as a login one if needed 
[01:59:48] <audioguy> I don't have access to linode console. 
[02:00:10] <paulej72> javascript adversion 
[02:00:19] -!- FunPika has quit [Ping timeout: 244 seconds] 
[02:00:24] <audioguy> no problem is done quickly at any rate. 
[02:00:24] <NCommander> paulej72: you can get into it via SSH 
[02:00:33] <NCommander> ANyway 
[02:00:39] <NCommander> anything else on sysops? 
[02:00:40] <audioguy> I was wondering about that 
[02:00:44] <paulej72> NCommander: that is thee thing, the password files may not be accessble to log in as root 
[02:01:02] <NCommander> THat's why I keep a local backup of it 
[02:01:18] <paulej72> we should have them emailed to the sysop staff. 
[02:01:32] <NCommander> probably safer just to put it on t-wiki 
[02:01:36] <Bytram> email == postcard 
[02:01:42] <audioguy> yes, not emailed! 
[02:02:00] <audioguy> put them in boron root where we can grab over secure ssh 
[02:02:04] <paulej72> not if we loose twiki and ssh on boron at the same time 
[02:02:23] <NCommander> audioguy: they're on helium in roots home folder which all sysops can get 
[02:02:24] <audioguy> We shouldnot put passwords on twiki. 
[02:02:25] <paulej72> if twiki is on boron that is a possibility 
[02:02:50] <paulej72> NCommander: that is if boron is not being upgraded at the time 
[02:03:09] <audioguy> Then we all need to just grab a copy from helium now. 
[02:03:16] <paulej72> yes 
[02:03:40] <NCommander> paulej72: I'm not upgrading it this instant 
[02:03:45] <NCommander> If I do it tonight, it will be around midnight AKDT 
[02:04:00] <audioguy> you know we are in staff, not a non public place right now. :-) 
[02:04:13] <audioguy> just thought I wouod point that out. :-) 
[02:04:21] <paulej72> yes I know, but in this case with boron down our only access to the other servers is via lish. 
[02:04:29] * NCommander notes that nothing here is private; we've got most of the configuration on the wiki already 
[02:04:48] <NCommander> paulej72: boron shoul donly be down during the reboot 
[02:04:48] <paulej72> Should we set up as sceconday ssh entrance on carbon? 
[02:04:57] <NCommander> I'll set that up 
[02:04:57] <audioguy> yes, but eay to forget, in the heat of things - it has happened before. 
[02:05:06] <TheMightyBuzzard> NCommander, you know you just doomed it, yes? 
[02:05:09] <NCommander> I"ll tempt enable public login on carbon during the upgrade 
[02:05:18] <NCommander> TheMightyBuzzard: yup :-) 
[02:05:36] <paulej72> hydrogen was susposed to be down only a few minutes 
[02:07:12] <NCommander> paulej72: technically speaking, its still up, just varnish is stopped :-P 
[02:07:30] <paulej72> NCommander: the other issue that we need to look into is reducing gluster memeory usage 
[02:07:44] <paulej72> I meant helium :) 
[02:07:46] <NCommander> that too 
[02:08:03] <NCommander> paulej72: helium was up, it just had some booting issues yours truly caused originally 
[02:08:52] <paulej72> do we have db riplication working yet? 
[02:09:10] <NCommander> yeah 
[02:09:20] <NCommander> But I don't hae it setup a second reader on slash yet 
[02:09:28] * NCommander is getting to the point he has to go 
[02:09:31] <TheMightyBuzzard> paulej72, move all of the logs out of the glustered area 
[02:09:35] <NCommander> Let's try and wrap this up quickly 
[02:09:51] <paulej72> I have nothing else pressing 
[02:10:15] * NCommander nods 
[02:10:17] <NCommander> Editoral team? 
[02:10:24] * TheMightyBuzzard is consulting over IM 
[02:10:33] * NCommander had something to bring up, but its not urgent, and can take it to email 
[02:10:38] -!- mechanicjay [mechanicjay!~jhowe@Soylent/Staff/Sysop/mechanicjay] has joined #staff 
[02:10:38] -!- mode/#staff [+v mechanicjay] by juggler 
[02:10:42] <audioguy> they are probably all asleep by now :-) 
[02:10:45] <LamnatorX> One moment, let me switch to a proper keyboard. 
[02:10:48] -!- LamnatorX has quit [Quit: Web client closed] 
[02:11:30] -!- LaminatorX [LaminatorX!~470ab0b6@Soylent/Staff/Editor/LaminatorX] has joined #staff 
[02:11:30] -!- mode/#staff [+v LaminatorX] by juggler 
[02:11:42] <LaminatorX> Alright, ready. 
[02:11:45] * NCommander didn't intend this to be a four hour long slosh 
[02:11:47] <NCommander> Seriously sorry guys 
[02:12:51] <NCommander> LaminatorX: your floor 
[02:13:06] <LaminatorX> I'm happy with where we are staffwise. While each batch of new Editors suffers 50% attrition, we've got enough keepers now to handle two of us on leave simultaneously without straining the rest unduly. 
[02:13:10] -!- Ethanol-fueled [Ethanol-fueled!~62b0c2de@cp88-216-234-862.sd.sd.cox.net] has joined #staff 
[02:13:14] <paulej72> NCommander: just a quick fyi on the ipv4 backend links between boron and hydrogen/fluorine the spped is about half of the hydrogen to fluorine link 
[02:13:58] <paulej72> LaminatorX: is there any that need their perms removed yet? 
[02:14:43] <NCommander> paulej72: ugh 
[02:14:56] <NCommander> LaminatorX: that's good to hear 
[02:15:01] * NCommander fuck it, brins up his point 
[02:15:04] <LaminatorX> We could probably do that for some of the early ones who've been idle for months. Let's wait a smidge longer though, I think 6 months idle is a nice round number, and we're not quite there yet. 
[02:15:15] <NCommander> eh, no 
[02:15:20] * NCommander is going to rathole us for 30 minutes 
[02:15:32] <NCommander> LaminatorX: I removed girlwhoisplugged out awhile ago 
[02:15:41] <NCommander> Not sure who else might need permission removal 
[02:16:34] <LaminatorX> Dopefish and Cactus haven't posted in months as well. I don't have a problem with GWWPO being removed, though would've like to have been consulted. 
[02:17:11] <paulej72> I thought he raged-quit or something 
[02:17:19] <NCommander> LaminatorX: I did that quite a long time ago, I was just menthoning it now 
[02:17:53] <paulej72> cant remember the specifics 
[02:17:57] <LaminatorX> Gotcha. No ragequits from Editors, it seems. We seem to die with a whimper. 
[02:18:30] <TheMightyBuzzard> wait till you see a sysadmin ragequit. can be a thing of horror and awe. 
[02:19:03] <Ethanol-fueled> WHy was GirlWhoWasPluggedOut removed? 
[02:19:09] <audioguy> unlikely with present crew. 
[02:19:12] <LaminatorX> GungnirSniper rounds out the missing list. 
[02:19:14] <paulej72> that is why you need to pet your sysadmins from time to time 
[02:19:20] <Ethanol-fueled> Not that I care, I'm just kinda chuckling and curious. 
[02:19:47] <NCommander> Ethanol-fueled: disappeared 
[02:19:48] <paulej72> Ethanol-fueled: MIA for too long 
[02:19:52] <LaminatorX> Zizban hadn't posted in a few weeks, but may just be in a back-to-school mode. 
[02:19:56] <Ethanol-fueled> Flaked out, eh? Bummer. 
[02:20:21] <audioguy> privileges are easily restored 
[02:20:27] <Ethanol-fueled> School is a bitch, and the only reason why I'm not offering to help more (under a less-offensive alias, of course). Sorry guys. 
[02:20:28] <paulej72> Zizban did say he would be irregular for a while 
[02:20:51] <LaminatorX> I' not kidding about 50% attrition, this is less fun than it seems from the outside. 
[02:20:52] * NCommander hates to do this, but I kinda need to bug out 
[02:20:54] <Bytram> NCommander: I'm assuming that this is separate and distinct from the list of editors that appears at the bottom of a page and which shows what each editor was last working on? 
[02:20:58] <NCommander> Can someone else take over for me? 
[02:21:12] <NCommander> Bytram: that list is anyone whoe ver held admin privs, the stats table for them isn't cleared out 
[02:21:14] <LaminatorX> It is that list, but that list is also historical. 
[02:21:30] <LaminatorX> you'll note Barrabas is still on that list. 
[02:21:37] <paulej72> I need to fix that. It bugs me 
[02:21:47] * NCommander notes I think aside from IRC, this is the last thing to cover so I cna probably stick for 10 more mintues 
[02:21:47] <Bytram> yup, and several others... hence my mentioning it. 
[02:21:50] <juggs> Is this still the staff meeting? are we going alphabetically or by section? I dozed off I think 
[02:21:53] <NCommander> paulej72: its a table somewhere in the DB 
[02:21:56] <NCommander> juggs: staff meeting 
[02:22:03] <NCommander> We need a better way to having this in the future 
[02:22:05] <juggs> fuck me 
[02:22:12] <paulej72> I nominate Bytram as our new meeting chair 
[02:22:34] <TheMightyBuzzard> seconded 
[02:22:43] <audioguy> unless there are other issues in editorial maybe we should just end? 
[02:22:45] <Bytram> I'd be willing, but my schedule is a bit, varied. 
[02:22:58] <paulej72> all those opposed 
[02:23:00] <Bytram> umm, QA/test? 
[02:23:04] <LaminatorX> We are quite grateful for working UTF-8. 
[02:23:21] <LaminatorX> I have nothing pressing. Status report is: good. 
[02:23:22] <paulej72> Bytram: just for the rest of this meeting 
[02:23:47] <TheMightyBuzzard> awe, i was feelin a perfectly good coup 
[02:23:53] <Bytram> ok, I *had* volunteered at the outset, IIRC =) 
[02:24:23] <juggs> Did irc get a look in... or was that covered by paulej72 ? 
[02:24:43] <paulej72> No we have not discussed that 
[02:25:01] <Bytram> and at some point I'd like to bring up "QA and Test" 
[02:25:21] <LaminatorX> Any other questions for Editorial, or shal I yield? 
[02:25:39] <paulej72> none 
[02:26:12] <Bytram> LaminatorX: do you have any issues/suggestions with the story submission/edin process? 
[02:26:20] <Bytram> s/edin/edit/ 
[02:27:26] <LaminatorX> If I were to make a wishlist, a larger edit-box with larger type would be nice. 
[02:27:44] <paulej72> LaminatorX: can do. 
[02:28:08] <audioguy> We need an 'old guy' skin that has larger type. :-) 
[02:28:14] <Bytram> LaminatorX: I noticed there is a 'drag' handle at the lower right-hand corner of the edit box. 
[02:28:19] <paulej72> can do as well 
[02:28:35] <Bytram> and a couple of "Ctrl-+" increases the font size (at least with FireFox) 
[02:28:43] <paulej72> Bytram: that is only on some borwosers 
[02:28:43] <TheMightyBuzzard> we need a oldschool skin too where blockquotes are prepended by a > and unstyled 
[02:28:52] <audioguy> yeah, I do that 
[02:29:04] <paulej72> TheMightyBuzzard: that is the vt100 theme 
[02:29:05] <audioguy> works on opera too 
[02:29:17] <TheMightyBuzzard> paulej72, yep yep 
[02:29:27] <LaminatorX> The type on the page overall is fine, the edit box is just smaller. It never occurred to me to enlarge the whole page. 
[02:29:44] <Bytram> hth 
[02:30:27] <LaminatorX> As far as flaggin spam submissions for admins to block, it would be nice to move them into a different queue like the way the Hold function works. 
[02:30:27] <paulej72> LaminatorX: I had that on my peronal todo list to fix at some point. Going to make a lot of boxes in the admin section larger and easir to edit in. 
[02:30:48] <audioguy> bump the font size in css on the form, I often do that. 
[02:31:16] <juggs> NCommander, I see no meeting, it is out of control. /me motions to exclude NCommander from the chair in future. 
[02:31:38] * NCommander is barely here at the moment 
[02:31:47] <NCommander> juggs: I passed chair off awhile ago 
[02:31:56] <juggs> uch 
[02:32:04] <LaminatorX> I'm happy to have an interface discussion with devs outside of the global staff meeting. 
[02:32:04] <audioguy> Blame Bytram :-) 
[02:32:27] * Bytram accepts blame 
[02:32:55] <Bytram> Is that it for Editorial? 
[02:32:55] <audioguy> We should just end. 
[02:33:08] <Bytram> QA/Test 
[02:33:12] <audioguy> 3 hours 32 minutes 
[02:33:21] <LaminatorX> Editorial has nothing else to bring-up. (Feel free to email me with your kettle-of-fish, NCommander.) 
[02:33:48] <Bytram> Testing of UTF-8 was a challenge... 
[02:34:19] <Bytram> TheMightyBuzzard: kept finding areas in the code which were not amenable to allowing UTF-8 chars through correctly, so it was a moving target. 
[02:34:39] <Bytram> He did a *great* job of keeping me in the loop, so to speak. 
[02:34:59] <TheMightyBuzzard> easy with one dev n one qa 
[02:35:07] <TheMightyBuzzard> gets complicated from there 
[02:35:08] <Bytram> I've hit at in a number of nefarious ways, but don't know how much of the code actually got covered. 
[02:35:26] <Bytram> so, far, though. it *seems* to be holding up well. 
[02:35:58] * Bytram should really write up a doc covering unicode, UTF-8, IDN, RFCs, etc. 
[02:36:02] <paulej72> not enough as we found bugs after deploy, but utf8 is a very large test sruface 
[02:36:28] <TheMightyBuzzard> fat woman vs midget big, yep 
[02:36:48] <paulej72> fat woman vs a filed mouse 
[02:37:08] <Bytram> if I had a specification which listed exactly what was to be changed from a user's perspective, as well as what was going to/from the DB, then I could have provided better coverage... still given from what we started with, I'd say we got a bunch of nasties out of the way before deploy. 
[02:37:48] <Bytram> Am mentioning this primarily to put a stae in the ground for futre reference. 
[02:37:51] <TheMightyBuzzard> prolly a good idea. 
[02:38:00] <paulej72> Bytram: part of the issue here is we are still learing where all of the code is located in slash 
[02:38:11] <TheMightyBuzzard> true dat 
[02:38:13] <Bytram> *exactly* 
[02:38:23] <TheMightyBuzzard> and then promptly forgetting half of what we learned. 
[02:38:38] <LaminatorX> Is there documentation of the overall archetechture going on as part of the effort? 
[02:38:40] <Bytram> now that we have some 'institutional' knowledge, it would be good to record it (maybe as some kind of post-mortem). 
[02:38:55] <paulej72> we don’t know what the whole scope od a chenge is until we aply it and see where it breaks 
[02:39:19] <Bytram> paulej72++ bingo 
[02:39:19] <Bender> �karma - �paulej72: 10 
[02:39:40] * TheMightyBuzzard makes notes 
[02:39:59] <Bytram> but, as we find new edges and corners while developing, it woud be helpful if someone could make a note so the rest of us don't have to skin our knuckles, too. 
[02:40:15] <paulej72> I am trying to put that knowledge inot the git commits 
[02:40:16] <Bytram> one other thing 
[02:40:16] <TheMightyBuzzard> damned fine idea. 
[02:40:44] <Bytram> the site experienced some, instability, for a few days... 
[02:41:03] <Bytram> paulej72++ you did a phenomenal job getting things back up and running. 
[02:41:03] <Bender> �karma - �paulej72: 11 
[02:41:13] <paulej72> many out of band deploys right now 
[02:41:24] * Bytram has no idea how but suspects a secret stash of dilithium crystals 
[02:41:51] <Bytram> that's my report. 
[02:42:04] <paulej72> nah I just stopped th server that was running shitty. 
[02:42:10] -!- NCommander has quit [Ping timeout: 244 seconds] 
[02:42:14] <Bytram> and, if nobody else has anything, I make a motion to adjourn 
[02:42:38] <LaminatorX> 2nded 
[02:42:42] <paulej72> Bad thing is I have not been able to figure out why it is acting shitty. 
[02:42:45] <paulej72> Does juggs have IRC stuff 
[02:43:08] <paulej72> or did sleep get to him first 
[02:43:17] <Bytram> actually, that just reminded me. 
[02:43:22] <matt_> [22:36] * juggs fades out of existence for now 
[02:43:27] <matt_> ^from #soylent 
[02:43:38] <Bytram> the LOGIN msg of the day lsits a bunch of folks running IRC. are they still all active? 
[02:43:59] <Bytram> here it comes... 
[02:44:00] <Bytram> * - ============================================================== 
[02:44:01] <Bytram> * - # The IRC staff: # 
[02:44:01] <Bytram> * - # # 
[02:44:01] <Bytram> * - # * xlefay - Team leader # 
[02:44:01] <Bytram> * - # * Landon - Member # 
[02:44:04] <Bytram> * - # * MrBluze - Member # 
[02:44:06] <Bytram> * - # * Kobach - Member # 
[02:44:08] <Bytram> * - # * FunPika - Member # 
[02:44:08] <paulej72> no, but I had other thing on my todo lit to fix that 
[02:44:10] <Bytram> * - # # 
[02:44:12] <Bytram> * - ============================================================== 
[02:44:14] <Bytram> * - # If you require any assistance, please /join #help # 
[02:44:16] <Bytram> * - ============================================================== 
[02:44:24] <Bytram> paulej72: great! thanks a bunch! 
[02:44:43] <LaminatorX> I believe MrBluze departed after the name vote. 
[02:44:54] <Bytram> nod nod 
[02:45:19] * Bytram needs to be going 
[02:45:35] <Ethanol-fueled> MrBluze left as well, eh? 
[02:45:45] <Bytram> Does IRC have a report? 
[02:45:57] <TheMightyBuzzard> kobach split too, no? 
[02:46:06] <paulej72> yes 
[02:46:24] <TheMightyBuzzard> basically down to landon and... well really just landon on that list. 
[02:46:45] <LaminatorX> FunPika was here earlier. 
[02:46:51] <TheMightyBuzzard> ya? sweet 
[02:46:58] <Ethanol-fueled> xlefay is lurking. 
[02:47:12] <Bytram> I may be mistaken, but I think xlefay is in more of an 'inactive' state than a 'quit' state. 
[02:47:36] <paulej72> but he could show up at any time and be more active. 
[02:47:39] <TheMightyBuzzard> bout my understanding too 
[02:48:38] <mechanicjay> I miss my buddy xlefay 
[02:48:39] <TheMightyBuzzard> should probably reorganize that list to reflect the current situation though. even if nobody ever reads the motd. 
[02:49:00] <Bytram> a quick check suggests his last msg on IRC was about 9 days ago... " Just can't be as active on IRC as I used to be, got actual stuff to do nowadays :(" 
[02:49:29] <Bytram> not certain, but that's the best I can tell on short notice using crutchy's ~last command on #Soylent 
[02:49:34] <paulej72> I think the only thing that Juggs wanted to bring up is staff abuing their IRC privs by kicking people and oping bots that should not be 
[02:49:39] <LaminatorX> I imagine that will be most of us at one point or another. 
[02:49:47] <Ethanol-fueled> Bytram, what set kobach off? 
[02:50:02] <Bytram> no idea at all. 
[02:50:24] <Bytram> I may have confused him with MrBluze 
[02:50:35] <TheMightyBuzzard> i only ever .kick the real bastards. only that TheMightyBuzzard guy so far. 
[02:50:45] <Bytram> Ok, if there's nothing else in re: IRC... do I hear a motion to adjourn? 
[02:51:01] <LaminatorX> Said motion is cuttently on the table. 
[02:51:10] <paulej72> kobach got upset when we called him out on abusing his irc privs 
[02:51:10] <Bytram> vote 
[02:51:11] <LaminatorX> s/tt/rr 
[02:51:16] <TheMightyBuzzard> move it out the way then to make room for the pizza 
[02:51:18] <audioguy> yeah 
[02:51:23] <TheMightyBuzzard> aye 
[02:51:33] <Bytram> aye 
[02:51:38] <LaminatorX> eye 
[02:51:45] <matt_> i 
[02:51:55] <paulej72> I 
[02:52:22] <Bytram> from the chair's perspective, the motion is carried and I hereby call this staff meeting adjourned. 
[02:52:27] * Bytram raps imaginary gavel 

[[Category:Staff meetings]]