SoylentNews - User contributions [en]

Wiki

2016-09-17T11:35:56Z

Janek Kozicki: /* Who we are */ added my timezone (I did this before, right?)

==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'''
|-
| mrcoolbp
| admin/bureaucrat
| UTC-4 (EST/EDT)
|-
|Sir Finkus
|bureaucrat/janitor
|UTC-8(PST)
|-
| cosurgi
| bureaucrat/janitor
| UTC+2
|-
|}
<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)
| ?
|-
| FunPika
| Leader (demoted due to inactivity)
| ?
|-
|}

== 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]]

Traditional moderation

2014-04-07T20:13:33Z

Janek Kozicki: added link to previous page history

(This is a subpage of [[Moderation|Moderation, you can go back to see other features planned.]], original history of this page, before it was moved is [http://wiki.soylentnews.org/w/index.php?title=FeatureList&action=history here])

* I forget who suggested this originally, but in addition to the above constraints, only allow users to moderate a subset of any particular article's comments.
::This seems like a bad idea. A moderator should be allowed access to any comment under an article. Maybe set a limit on how many points they can burn in a particular article, but don't make some comments off-limits based on an arbitrary randomization process.

* '''Moderation Engine'''
::{| class="wikitable"
|+ Moderation tags (default scores)
|-
! Mod Up
! Points
! Mod Down
! Points
|-
| Interesting
| +1
| Offtopic
| -1
|-
| Informative
| +1
| Troll/Spam
| -1
|-
| Insightful
| +1
| Groupthink ('''New''')
| -1 (or -0.5?)
|-
| Underrated
| +0.5 ('''New''')
| Overrated
| -0.5 ('''New''')
|-
| Funny
| +0.5 ('''New''')
| Flamebait
| -0.5 ('''New''')
|-
| Devils Advocate ('''New!''')
| +1
| Jibberish ('''New!''')
| -1
|}

::::'''Also suggested:''' Bullshit, I_disagree, Controversial

* Users assign own weights to tags in the range -2.0 -> 2.0 with 0.5 increments
* System rounds x.5 towards 0 in comment spill / threshold logic, display capped at -1 and 5.
* A score for the default weights is saved for the comment for use by article spill (for googlebot or "load all comments" from anonmyous user)
* An optional cryptocoin tipping system, when you like someone's post you can give him a small cryptocoin tip. That might also work as an additional moderating system. Non-moderators could mod-up comments (Insightful, Funny, etc) by eg. 0.5 points by spending some money.

* I think it would be good to display both the positive mods and negative mods on a comment in a concise form (so you could see that this comment is generally regarded both Insightful.... but also Flamebait) <== Or a total of positive and negative comments to take up less space (This could be done via a hover text showing: Modded up XX times, Modded down XX times, total score: XX, and have the hover be over the +5, etc whatever)
* I like the idea of a system that allows users to have mod points on a regular basis. That way they do not feel like they have to use up all their points on comments that don't deserve them. A much better quality of moderation should do a better job of making the best comments float to the top.
* Let users set both ends of their moderation based comment 'scope'. To see the highlights, set at +4 and above. To look for abusive moderations, set to display 0 and below. (And I'm sure that someone will want to browse "only the 3's", so the system should allow that too). It was also suggested that we have a method to filter out posts from AC.

'''Discussion: Ability to comment and moderate in the same article'''
* What about not-posting in the thread where you moderated? Good or bad rule? Maybe if you really must post, allow cryptocoin paying for post? (eg. "Warning: you have moderated in this thread (or whole story), if you really want to post you need to spend cryptocoin on that" (??)) Not posting in the thread is okay, and much better than disallowing the whole story.
* I believe the ability to add a comment to an article after you have already moderated in that tree is a benefit. But can also see a path for abuse. While not a fan of Cryptocoin, what about letting a moderator add a comment, but at a cost of a mod point ??

===Moderation strategy===
* Chops instead of Karma
* Chops are derived from:
:: Articles accepted for submission
::: But NOT articles self-authored on a channel you're an editor of
:: Comments that are replied to by others without a troll/flamebait modifier
:: Positive moderation (as judged by the mod action with respect to their own point value weights... so if they think funny is bad, it counts against you)
:: Positive metamoderation outcome (see below) Discussion required
* Registered users that have used the site > [threshold] days, posted > [threshold] times, and have positive chops get moderation duty (possibly [x] mod points per day?)
* The more chops, the more mod points per day, with a total cap for unused points

'''Meta-moderation'''
Meta-moderation is a check and balance system that acts to identify bad moderators. It works best when a large number of users are available and willing to evaluate a comment's existing moderaton values
* Meta-moderation is available to users that have used the site > [big threshold] days and have > [threshold] chops
* Metamoderation is not "special", a meta-mod capable user can see a random selection of recent mods at any time and metamod.
* Metamod takes 2 mod points <==Wouldn't adding a cost for Meta-moderation decrease the pool of users willing to use it?
:::Metamod actions are like moderation actions, you spend modpoints on them. But they are twice as expensive as direct moderation. The theory is that users with more chops (and thus more modpoints to throw around) are more likely to spend some of them on metamoderation.
:::Alternatively.... Meta-mod should be open to all in good standing for RANDOM comments. Maybe allow burning 2 mod points to meta-mod a specific comment?
* Metamod can spend a mod point to "re-roll" and see a new set of random moderations
* A moderation is undone when it's "score" goes negative. It is "reapplied" when it goes positive. If the score dips to -3, the moderation is removed entirely. Default moderation value should be > 0, possibly 2 ??
* A user is not rewarded or punished for the metamod specifically
* A running total of positive and negative meta-moderations against them is calculated
::Receiving a threshold for positive or negative meta-mod counts result in fixed deltas in chops (Proposed Values)
+5 positive yields +1 chops 5 negative meta-mods -1 chpos score
+10 positive yields +2 chops 10 negative meta-mods -2 chops score
+15 positive yields +3 chops 15 negative meta-mods -3 chops score

* Your current chops as of more than 4 weeks ago is rolled into a fixed amount capped at 1.5 times the "Excellent" value and 1.5 times the most negative "Worst Poster" value.
* On a weekly basis a task is run across all accounts that collects chop point actions since the last summarization date forward a week (actions that happened about 3 weeks ago), applies these to the last +4 weeks ago score, truncates it to the ranges above, and stores it in the database with the new summarization date for that user's account.
* This prevents a user from "banking" actions that give them more chops to only later be a jerk.
* However it lets you be a bit grumpy in the short term since the value can go above the thresholds when calculating the current display/privs value (query all the outstanding chop actions for this user, add the point values to the historic value, store it for easy reference later, cached for an hour)

== Misc ==

From Danny B. on ARS:Try something novel.
::How about being able to mod and feedback on ads!

Funding

2014-04-07T20:00:23Z

Janek Kozicki: added link back

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

* '''To have funds for all that''', we could use (check also [[Finances]]):
** That tipping system (mentioned above in moderation), and everytime you tip someone else a very tiny fraction of that tip goes to altslashdot.
** 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).
** Failed submitters, who had to give back their reward plus some extra fraction because their story was hated after it was submitted (think Roland Piquepaille) as mentioned above.
** 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

What did not work

2014-04-07T20:00:07Z

Janek Kozicki: added link back

*Feature that worked was the karma system allowed users to voluntarily disable the advertisement, made them feel happy even though it did nothing different for the business.
*Feature that did not work: Adding a sponsored poll / slashvertising
*Not being able to uniquely identify Anonymous Cowards (to track them in a thread, something like how 4chans "identified" anon works, I guess)

*slashdot for mobile has always been terrible. i was rarely able to login on my android phone. ~crutchy

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

Article Topics

2014-04-07T19:59:53Z

Janek Kozicki: added link back

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

Slashdot had a set of article topics. These are the ones that are linked from the front page, but there are more that aren't visible:
* Stories
* Submissions
* Popular
* Blog
* Ask Slashdot
* Book Reviews
* Games
* Idle
* Your Rights Online
* Cloud
* Hardware
* Linux
* Management
* Mobile
* Science
* Security
* Storage

In retrospect, we can probably do better:
* Stories
* Submissions (The Firehose)
* Popular
* Blog (Communication from site administrators)
* Journal (The last 10 journal entries in the system)
* Ask Slashdot
* Games
* Hardware
* Linux
* Medicine
* Mobile
* Reviews
* * Book Reviews
* * Hardware Reviews
* * Software Reviews
* Science
* Security
* Storage
* Your Rights

We also need a way to see all the possible topics.

Article submission

2014-04-07T19:59:38Z

Janek Kozicki: added link back

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

* Editor:
** UTF-8
** MathJax (mentioned earlier)
** ability to check links inline during writing the submission. To see how it works just try writing email in gmail. Everytime when you add a link, there's an option right below it to "check link"

* Encouraging submitting good articles:
** Everytime when a story gets accepted, the submitter gets a small cryptocoin reward (as we know - very easy to automate this). Since we are very poor (at least at start) we will not pay a fixed amount, but a small percentage of all cryptocoins owned by altslashdot.
** If a story gets accepted but is hugely downvoted later (think Roland Piquepaille), the submitter must give back his reward to be able to submit a new story. In fact even better if he had to give back a tiny fraction more cryptocoin than he received.
*Is there a path to remove a bad editor ? <=== I'm not very fond of emacs

Engine requirements

2014-04-07T19:59:18Z

Janek Kozicki: added link back

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

* '''Be mindful of bandwidth and the amount of processing done by the server when building any features. One extra character balloons into many megabytes of expensive bandwidth and consumption of server resources. Each feature that bloats a page response or causes the server to process something increases costs--KEEP COSTS DOWN!'''
* UTF-8 clean for anything that doesn't end up in a URL (i.e. tags, titles, channel names, user names)
** Of course, some combining marks would have to be filtered, and the resulting text round-tripped through NFD->NFC to prevent certain types of attacks against users or making text difficult to index.
* [http://blog.stackoverflow.com/2011/04/stack-exchange-partners-with-mathjax/ MathJax] support both in comments and in submissions
:: Mathjax is the math rendering engine used on [http://stackexchange.com/ stackexchange] and will allow scientific discussion between us (people who read math).
* Channels (like yro, science, politics, apple) as first class objects
** "Primary" channels that have DNS shorthand (http://apple.altslash.org/ being equiv to http://altslash.org/ch/apple/)
** "Secondary" channels that users could create and play editor that use the more verbose syntax (http://altslash.org/ch/baseball/) that is reminiscent of subreddits
** User channels (i.e. journals, as we've always had)
* Display user IDs
* Javascript Optional
** I enjoy having the comment rating slider for example, but main functionality should be accessible with lynx at the least!

* Submission queues for all channels with membership at the discretion of the channel owner; being able to submit also implies up/downvoting submissions and tagging
:: Editors/channel owners only
:: List of users who can submit
:: All of my friends (for user journals)
:: All users with mod status
:: All registered users
:: Everyone

* Articles are also first class objects
:: Perma-link independant of channel
:: Articles are tagged by topic(s) as well as channel
:: Articles are automatically archived
:: Archive is easily searchable, and should be referenced when submissions are edited.
:: Articles can be cross-posted to other channels by a channel owner (built into the UI if the editor manages more than one channel)
* Comment key features
:: Comments are first class objects, just as before, just like articles
:: Comments can be edited for a short period of time by owner
::: HOWEVER: Edited comments get a new ID and it links to older versions in the new one. This detail is made prominent to viewer if a comment reply happened before an edit.
:: Allow alternate markup options (bbcode, markdown, wiki markup)
::: Provide a mapping to actual div and styles that will be applied, or HTML equivalent codes

* Allow moderation in same article that you've posted in; only disallow moderation '''to your own reply chain'''.
** You're obviously not allowed to moderate in your own accepted or posted article (treating all comments as replies)
** Does "reply chain" include parent? If not, how do we deal with threadjacking:
**# AC posts first comment on a new article (let's presume it's an upmod-worthy comment, not fristpsot)
**# I post my unrelated comment as a reply to AC's FP, in order to achieve greater visibility
**# I downmod the AC to -1
**# Now AC is invisible to anyone with threshold != -1 (including many with mod points and threshold=0, who would have modded AC up on his own merits)
**# Unless/until users with threshold=-1 and mod points happen by to rectify things, my comment is now the first thing most users see.
**# ??? ''(sorry, can't resist...)''
**# Profit!
***Actually, not just the immediate parent like I said, but 'all' ancestor comments. Otherwise as step 1.5 I just reply with an AC troll (which someone else will rightfully downmod), then in step 2 I reply to ''that''; now that the original AC first post is my comment's gp, so I can still downmod it.
** ''' Good point ''' you should be prevented from moderating any children '''and''' ancestors of your posts (but sibling chains are still fair game)

General requirements

2014-04-07T19:59:02Z

Janek Kozicki: added link back

* Cool new colour
* OAuth provider, could be useful when we integrate other means of communication (e.g. forums, IRC)
* RSS feed, including comments.

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

Historic:Moderation

2014-04-07T19:58:42Z

Janek Kozicki: small fix

What kind of moderation system? How it would handle communities of different size and homogenity? Discuss.

* Mostly [[Traditional moderation|traditional /. moderation]], with tweaks, though.
* [[Extended moderation|Complex variants]] for very "nerdy" sities.

(This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]])

Extended moderation

2014-04-07T19:58:19Z

Janek Kozicki: added link back

(This is a subpage of [[Moderation|Moderation, you can go back to see other features planned.]])

A discussion about some complex "nerdy" variants of the [[Traditional moderation|traditional moderation]], probably not apt for a typical /. style news site.

== Is it really about "beta"? ==
It is claimed the reason of migrating out of slashdot is the "beta". But is it really so? Let's try to do some speculations...

"Beta" is said to be made to fit tastes of the younger audience, flowing recently en masse to Slashdot - in fact, stats show, that Slashdot is currently
accesses mosltly from... schools. The same audience is, though, often scorned upon by the "low uids" as the reason of progressively "destroying the old Slashdot".
Now, we could conclude, that the deeper reason for both beta and discussion quality are really kids. But it seems, it is still not so simple.

Let us consider an example. So, (i) a bunch of teenagers mods ups some old joke, as things like that still amuse and educate them. Now, a low uid hates that.
But, despite that, (ii) the younger and the older Slashdot might still share some common interests - be it some comment insightfull for all, so a single site might make
sense. How to agree that? Would some special sort of moderation be able to please both of the discussed groups?

Attach your proposals below.

== A local moderation ==
The moderation and metamoderation work globally now - it is one of the factors which decide, how many mod points a user gets. What about making it '''also''' local? A moderating or metamoderating user would express his/her preferences in this way. An example: it turns out, the user X likes comments of "low uids", but dislikes comments frequently moderated by teenagers? So the system increases that user's "experience", what translates to '''mods of experienced users being somewhat more visible by this particular user, as opposed to mods of the school crowd'''. In other words, there would not be a single score, seen by all -- a user by moderating would tune, or bias the scoring according to his/her needs. Meanwhile, a kid might still admire, and mod up with "novice points", old jokes, but also high-quality school-grade educational comments.

This might be made even more complex -- a dynamic [[wikipedia:cluster analysis|cluster analysis]] might find out by itself groups of users with common tastes, and somewhat tune the scoring to their likes. And, if the said kid writes a quality comment, modded up by experienced users, it would in turn move the kid a bit in the direction of a cluster of "low uids".

Surely, a careful tuning of the system might be needed. To alleviate that a bit and to make the local moderation opt-in, every user might be given a choice of his/her sweet spot between a "flat" and an "adaptable" scoring.

== Nonlinear moderation ==

Hand out more points but make the relationship between score and points exponential.

Traditional moderation

2014-04-07T19:57:51Z

Janek Kozicki: added link back

(This is a subpage of [[Moderation|Moderation, you can go back to see other features planned.]])

* I forget who suggested this originally, but in addition to the above constraints, only allow users to moderate a subset of any particular article's comments.
::This seems like a bad idea. A moderator should be allowed access to any comment under an article. Maybe set a limit on how many points they can burn in a particular article, but don't make some comments off-limits based on an arbitrary randomization process.

* '''Moderation Engine'''
::{| class="wikitable"
|+ Moderation tags (default scores)
|-
! Mod Up
! Points
! Mod Down
! Points
|-
| Interesting
| +1
| Offtopic
| -1
|-
| Informative
| +1
| Troll/Spam
| -1
|-
| Insightful
| +1
| Groupthink ('''New''')
| -1 (or -0.5?)
|-
| Underrated
| +0.5 ('''New''')
| Overrated
| -0.5 ('''New''')
|-
| Funny
| +0.5 ('''New''')
| Flamebait
| -0.5 ('''New''')
|-
| Devils Advocate ('''New!''')
| +1
| Jibberish ('''New!''')
| -1
|}

::::'''Also suggested:''' Bullshit, I_disagree, Controversial

* Users assign own weights to tags in the range -2.0 -> 2.0 with 0.5 increments
* System rounds x.5 towards 0 in comment spill / threshold logic, display capped at -1 and 5.
* A score for the default weights is saved for the comment for use by article spill (for googlebot or "load all comments" from anonmyous user)
* An optional cryptocoin tipping system, when you like someone's post you can give him a small cryptocoin tip. That might also work as an additional moderating system. Non-moderators could mod-up comments (Insightful, Funny, etc) by eg. 0.5 points by spending some money.

* I think it would be good to display both the positive mods and negative mods on a comment in a concise form (so you could see that this comment is generally regarded both Insightful.... but also Flamebait) <== Or a total of positive and negative comments to take up less space (This could be done via a hover text showing: Modded up XX times, Modded down XX times, total score: XX, and have the hover be over the +5, etc whatever)
* I like the idea of a system that allows users to have mod points on a regular basis. That way they do not feel like they have to use up all their points on comments that don't deserve them. A much better quality of moderation should do a better job of making the best comments float to the top.
* Let users set both ends of their moderation based comment 'scope'. To see the highlights, set at +4 and above. To look for abusive moderations, set to display 0 and below. (And I'm sure that someone will want to browse "only the 3's", so the system should allow that too). It was also suggested that we have a method to filter out posts from AC.

'''Discussion: Ability to comment and moderate in the same article'''
* What about not-posting in the thread where you moderated? Good or bad rule? Maybe if you really must post, allow cryptocoin paying for post? (eg. "Warning: you have moderated in this thread (or whole story), if you really want to post you need to spend cryptocoin on that" (??)) Not posting in the thread is okay, and much better than disallowing the whole story.
* I believe the ability to add a comment to an article after you have already moderated in that tree is a benefit. But can also see a path for abuse. While not a fan of Cryptocoin, what about letting a moderator add a comment, but at a cost of a mod point ??

===Moderation strategy===
* Chops instead of Karma
* Chops are derived from:
:: Articles accepted for submission
::: But NOT articles self-authored on a channel you're an editor of
:: Comments that are replied to by others without a troll/flamebait modifier
:: Positive moderation (as judged by the mod action with respect to their own point value weights... so if they think funny is bad, it counts against you)
:: Positive metamoderation outcome (see below) Discussion required
* Registered users that have used the site > [threshold] days, posted > [threshold] times, and have positive chops get moderation duty (possibly [x] mod points per day?)
* The more chops, the more mod points per day, with a total cap for unused points

'''Meta-moderation'''
Meta-moderation is a check and balance system that acts to identify bad moderators. It works best when a large number of users are available and willing to evaluate a comment's existing moderaton values
* Meta-moderation is available to users that have used the site > [big threshold] days and have > [threshold] chops
* Metamoderation is not "special", a meta-mod capable user can see a random selection of recent mods at any time and metamod.
* Metamod takes 2 mod points <==Wouldn't adding a cost for Meta-moderation decrease the pool of users willing to use it?
:::Metamod actions are like moderation actions, you spend modpoints on them. But they are twice as expensive as direct moderation. The theory is that users with more chops (and thus more modpoints to throw around) are more likely to spend some of them on metamoderation.
:::Alternatively.... Meta-mod should be open to all in good standing for RANDOM comments. Maybe allow burning 2 mod points to meta-mod a specific comment?
* Metamod can spend a mod point to "re-roll" and see a new set of random moderations
* A moderation is undone when it's "score" goes negative. It is "reapplied" when it goes positive. If the score dips to -3, the moderation is removed entirely. Default moderation value should be > 0, possibly 2 ??
* A user is not rewarded or punished for the metamod specifically
* A running total of positive and negative meta-moderations against them is calculated
::Receiving a threshold for positive or negative meta-mod counts result in fixed deltas in chops (Proposed Values)
+5 positive yields +1 chops 5 negative meta-mods -1 chpos score
+10 positive yields +2 chops 10 negative meta-mods -2 chops score
+15 positive yields +3 chops 15 negative meta-mods -3 chops score

* Your current chops as of more than 4 weeks ago is rolled into a fixed amount capped at 1.5 times the "Excellent" value and 1.5 times the most negative "Worst Poster" value.
* On a weekly basis a task is run across all accounts that collects chop point actions since the last summarization date forward a week (actions that happened about 3 weeks ago), applies these to the last +4 weeks ago score, truncates it to the ranges above, and stores it in the database with the new summarization date for that user's account.
* This prevents a user from "banking" actions that give them more chops to only later be a jerk.
* However it lets you be a bit grumpy in the short term since the value can go above the thresholds when calculating the current display/privs value (query all the outstanding chop actions for this user, add the point values to the historic value, store it for easy reference later, cached for an hour)

== Misc ==

From Danny B. on ARS:Try something novel.
::How about being able to mod and feedback on ads!

Historic:Moderation

2014-04-07T19:56:57Z

Janek Kozicki: added link back

What kind of moderation system? How it would handle communities of different size and homogenity? Discuss.

* Mostly [[Traditional moderation|traditional /. moderation]], with tweaks, though.
* [[Extended moderation|Complex variants]] for very "nerdy" sities.

This is a subpage of [[FeatureList|Feature list, you can go back to see other features planned.]]

UserExperience

2014-04-06T18:18:32Z

Janek Kozicki: /* Who we are */

The User Experience team devlopes art, CSS, and other UI elements and is connected with the Dev team. Take a look around here, if you'd like to help, contact '''style@soylentnews.org''' or MrBluze on IRC.

There's a lot of documentation on [[CssWork|CSS work being done]] and you can find some notes on future [[Style:UI_Design|UI Design here]].

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| UTC+10 (AEST)
|-
| audioguy
| ?
| UTC-8 (PST)
|-
| FrogBlast
| Art Team
| ?
|-
| shogun
| HTML
| ?
|-
| moo_kuh
| Testing
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}
<section end=whoarewe />

==Todo==
*Define single column layout requirements - nearly done.
*Work with FrogBlast to get the full icon set done - in progress.
*Review/upgrade logo/banner art (with FrogBlast) - in progress.
*Typographic and typesetting guidelines (with LaminatorX) - awaiting feature request, then work with CSS ppl on a specification
*Weekly comic

[[Category:Teams]]
[[Category:User experience]]

Development

2014-04-05T09:52:15Z

Janek Kozicki: /* Who we are */

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72<ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| Team Leader for Dev
| UTC-4 (EST/EDT)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| right hand man to paulej72 and second in command for Dev.
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| UTC+2
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

==Notes==
<references />

[[Category:Development]]
[[Category:Teams]]

Development

2014-04-05T09:48:54Z

Janek Kozicki: /* Who we are */

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable"
!colspan="3"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72<ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| Team Leader for Dev
| UTC-4 (EST/EDT)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| right hand man to paulej72 and second in command for Dev.
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| UTC+2
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

==Notes==
<references />

[[Category:Development]]
[[Category:Teams]]

Editors

2014-04-04T22:00:39Z

Janek Kozicki: /* Who we are */

The editorial team refines and accepts story submissions. Contact: '''editors@soylentnews.org'''.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| UTC-7 (MST)
|-
| janrinok
| editor
| UTC+2 (CET)
|-
| MrBluze
| editor
| UTC+10 (AEST)
|-
| girlwhowaspluggedout
| editor
| ?
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| Cactus
| miscellaneous
| ?
|}
<section end=whoarewe />

==Projects==

*Create and Submit a press release
*Continue to develop editorial process (see Documentation below)
*Documentation pages (FAQ, "Authors" page) <- LaminatorX is working on FAQ

==Documentation==

*A [[Story_Style|Story Style]] document outlines editorial guidelines, it may need additional refining and ratification eventually.
* [[Submission_guidelines|Submission Guidelines]] - Notes to all users regarding the formatting of submissions and relevant rules.
* [[Editing_Process|The Editing Process]] - builds on the Story Style and Submission Guidelines to describe <b>how</b> the editing process is carried out.

==Dependencies==
*Main Website (slash)
**editor privledges

[[Category:Teams]]
[[Category:Editorial team]]

UserExperience

2014-04-04T21:59:05Z

Janek Kozicki: /* Who we are */

The User Experience team devlopes art, CSS, and other UI elements and is connected with the Dev team. Take a look around here, if you'd like to help, contact '''style@soylentnews.org''' or MrBluze on IRC.

There's a lot of documentation on [[CssWork|CSS work being done]] and you can find some notes on future [[Style:UI_Design|UI Design here]].

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| UTC+10 (AEST)
|-
| audioguy
| ?
| UTC-8 (PST)
|-
| FrogBlast
| Art Team
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}
<section end=whoarewe />

==Todo==
*Define single column layout requirements - nearly done.
*Work with FrogBlast to get the full icon set done - in progress.
*Review/upgrade logo/banner art (with FrogBlast) - in progress.
*Typographic and typesetting guidelines (with LaminatorX) - awaiting feature request, then work with CSS ppl on a specification
*Weekly comic

[[Category:Teams]]
[[Category:User experience]]

IRC

2014-04-04T21:56:49Z

Janek Kozicki: /* Who we are */

Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Kobach
| Co-leader | Chief Bacon Officer
| UTC-5 (us/central)
|-
| MrBluze
| Member
| UTC+10 (AEST)
|-
| Landon
| Member
| ?
|-
| FunPika
| Member
| ?
|}
<section end=whoarewe />

==Current Projects==

===Chat bot (Python)===
* ELIZA module that uses Futurama personalities (to match the bot's current nick)
* Modify bot logging to match existing formats (mIRC preferably)

===Services (C)===
* Single sign on against the website (coordinate with NCommander)
* Get the web IRC to use the website's sessions to sign in

===Documentation===
*Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)

==Dependencies==
*servers
*bots

[[Category:Teams]]
[[Category:IRC]]

Editors

2014-04-03T18:17:35Z

Janek Kozicki: /* Who we are */

The editorial team refines and accepts story submissions. Contact: '''editors@soylentnews.org'''.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| UTC-7 (MST)
|-
| janrinok
| editor
| UTC+2 (CET)
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| Cactus
| miscellaneous
| ?
|}
<section end=whoarewe />

==Projects==

*Create and Submit a press release
*Continue to develop editorial process (see Documentation below)
*Documentation pages (FAQ, "Authors" page) <- LaminatorX is working on FAQ

==Documentation==

*A [[Story_Style|Story Style]] document outlines editorial guidelines, it may need additional refining and ratification eventually.
* [[Submission_guidelines|Submission Guidelines]] - Notes to all users regarding the formatting of submissions and relevant rules.
* [[Editing_Process|The Editing Process]] - builds on the Story Style and Submission Guidelines to describe <b>how</b> the editing process is carried out.

==Dependencies==
*Main Website (slash)
**editor privledges

[[Category:Teams]]
[[Category:Editorial team]]

WhosWho

2014-04-03T18:17:16Z

Janek Kozicki: /* Administration */ added mattie_p timezone

Development

2014-04-03T18:04:30Z

Janek Kozicki: /* Who we are */ and another small fix

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable"
!colspan="4"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72<ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| Team Leader for Dev
| UTC-4 (EST/EDT)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| right hand man to paulej72 and second in command for Dev.
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| UTC+2
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

==Notes==
<references />

[[Category:Development]]
[[Category:Teams]]

Development

2014-04-03T18:04:03Z

Janek Kozicki: /* Who we are */ small fix

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable"
!colspan="4"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72<ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| Team Leader for Dev
| UTC-4 (EST/EDT)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| right hand man to paulej72 and second in command for Dev.
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| (TZ+2)
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

==Notes==
<references />

[[Category:Development]]
[[Category:Teams]]

SystemAdministration-OLD-2024

2014-04-03T18:02:53Z

Janek Kozicki: /* Who we are */ 19:51 < paulej72> cosurgi: mechanicjay is EST/EDT

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| UTC-4 (EST/EDT)
|-
| NCommander
| Member
| UTC-5
|-
| robind
| Member
| ?
|-
| Audioguy
| Member
| UTC-8 (PST)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

* [[soylent-www]] - Primary Apache and slash server for main site.
* soylent-db -- mysql server, holds the slash database
* slashcott - Holds the slashcott site, development machine
* [[soylent-services]] - mail, wiki, other services as needed

==Known Problems==

* '''Need cron job to backup server'''
* There are errors in the zone file in the spf TXT record -- Mechanicjay would be happy to fix this and clean up the zone file in general, but needs linode manager access from NCommander.
* No init script for Apache.
* Broken https configuration
** Mostly fixed, Slash is the problem child now

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turn off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)

[[Category:Teams]]
[[Category:System administration]]

WhosWho

2014-04-03T17:56:08Z

Janek Kozicki: /* IRC */ link it

IRC

2014-04-03T17:55:48Z

Janek Kozicki: moved table here

Contact '''chat@soylentnews.org''' if you are interested in working on one of these projects. Also, the [[SoylentNews:IRC|IRC Page]] has information about getting started with IRC.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Kobach
| Co-leader | Chief Bacon Officer
| UTC-5 (us/central)
|-
| MrBluze
| Member
| ?
|-
| Landon
| Member
| ?
|-
| FunPika
| Member
| ?
|}
<section end=whoarewe />

==Current Projects==

===Chat bot (Python)===
* ELIZA module that uses Futurama personalities (to match the bot's current nick)
* Modify bot logging to match existing formats (mIRC preferably)

===Services (C)===
* Single sign on against the website (coordinate with NCommander)
* Get the web IRC to use the website's sessions to sign in

===Documentation===
*Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)

==Dependencies==
*servers
*bots

[[Category:Teams]]
[[Category:IRC]]

WhosWho

2014-04-03T17:54:28Z

Janek Kozicki: /* Wiki */ link it

Wiki

2014-04-03T17:54:10Z

Janek Kozicki: moved table here

==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}} ([https://git.wikimedia.org/log/mediawiki%2Fcore.git/refs/heads/REL1_22 REL1_22 branch])
* Apache 2.x (whatever CentOS is providing I assume)
* PHP 5.3.3 (MediaWiki [[mediawikiwiki:Manual:Installation guide#Summarized_installation_guide|recommends]] at least 5.3.5 because of [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4645 CVE-2010-4645], although that is probably patched in CentOS's version)
* MySQL 5.1.73
* ImageMagick for image thumbnailing
* Git for updating
* MediaWiki Extensions listed on [[Special:Version]]

__FORCETOC__

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

WhosWho

2014-04-03T17:52:50Z

Janek Kozicki: /* Community Support */ link it

CommunitySupport

2014-04-03T17:52:30Z

Janek Kozicki: move tables

==Welcome==
This site is made possible by (and for) the insightful community of users. There are many ways to participate. Of course, [http://soylentnews.org/submit.pl submitting stories] or commenting on them is the most obvious way to get involved. You can also submit ideas for new projects in [[Suggestions]], or bugs and "feature requests" on the [https://github.com/SoylentNews/slashcode/issues bug tracker on github].

If you'd like to get more closely involved by working with a team, you should contact them directly. Start at the [[WhosWho]] or [[TeamPages|Team Pages]]. For example the [[Development|Development Team]] can always use perl experience, and the [[Editors]] team are looking to expand their time zone coverage. If you have any questions or are not sure where to start you can send an email to '''suggestions@soylentnews.org'''.

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

==Documentation==

This team:
*Answers support and contact emails
*Tracks volunteers and staff
*Collects [[Suggestions]]
Goals for the future:
*Utilize community feedback selecting suggestions for implementation
*Investigate staff and community '''[[CommunicationSystems|Communication Systems]]'''

==Dependencies==

Dependencies for this group include:
*SN Mailboxes and forwards:
**admin@SN
**suggestions@SN
**mail is hosted on [[Soylent-services|beryllium]]
*IRC Bot
**!suggestion (currently de-activated)

==Projects==

*Propose Vote on Staff [[CommunicationSystems|Communication System]]
*Organize regular staff meetings (bi-weekly?)

*New (final) Name Vote (mrcoolbp, audioguy, MrBluze)
**New Names Shortlist '''(will be revised)'''
***soylentnews
***port119.net
***baconnews.org baconnews.net (baconnews.'''net''' was suggested as it can be "BNN")
***nerdcard.net
***geekcard.org
***dailybacon.org
***ionews.org

*Migrate mailing list addresses to new @SN.org addresses
*Develop process for becoming staff (get @SN.org email, get on mailing list, privileges, orientation booklet, etc.)
*Get email and IRC "!suggestions" piped directly to wiki)
*Contact CmdrTaco via twitter?

[[Category:Teams]]
[[Category:Community support]]

WhosWho

2014-04-03T17:50:50Z

Janek Kozicki: /* Content */ link it

Editors

2014-04-03T17:50:29Z

Janek Kozicki: moved table here

The editorial team refines and accepts story submissions. Contact: '''editors@soylentnews.org'''.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| UTC+2 (CET)
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| Cactus
| miscellaneous
| ?
|}
<section end=whoarewe />

==Projects==

*Create and Submit a press release
*Continue to develop editorial process (see Documentation below)
*Documentation pages (FAQ, "Authors" page) <- LaminatorX is working on FAQ

==Documentation==

*A [[Story_Style|Story Style]] document outlines editorial guidelines, it may need additional refining and ratification eventually.
* [[Submission_guidelines|Submission Guidelines]] - Notes to all users regarding the formatting of submissions and relevant rules.
* [[Editing_Process|The Editing Process]] - builds on the Story Style and Submission Guidelines to describe <b>how</b> the editing process is carried out.

==Dependencies==
*Main Website (slash)
**editor privledges

[[Category:Teams]]
[[Category:Editorial team]]

WhosWho

2014-04-03T17:48:10Z

Janek Kozicki: /* Style/User Experience */ and link it

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev@SoylentNews.org ([[#Development|Development]])
*editors@SoylentNews.org ([[#Content|Content]])
*suggestions@soylentNews.org ([[#Community Support|Community Support]])
*wiki@SoylentNews.org ([[#Wiki|Wiki]])
*chat@SoylentNews.org ([[#IRC|IRC]])
*style@SoylentNews.org ([[#Style|Style/User Experience]])
*art@SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| ?
|-
| mrcoolbp
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{#lst:Development|whoarewe}}

==Sysops==

{{#lst:SystemAdministration|whoarewe}}

==Style/User Experience==

{{#lst:UserExperience|whoarewe}}

==Content==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| UTC+2 (CET)
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| Cactus
| miscellaneous
| ?
|}

==Community Support==
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mrcoolbp
| Leader
| UTC-4 (EST/EDT)
|-
| xlefay
| ?
| UTC+2 (CEST)
|}

==Wiki==
{| 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)
|}

==IRC==
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Kobach
| Co-leader | Chief Bacon Officer
| UTC-5 (us/central)
|-
| MrBluze
| Member
| ?
|-
| Landon
| Member
| ?
|-
| FunPika
| Member
| ?
|}

==Notes==
<references />

UserExperience

2014-04-03T17:47:50Z

Janek Kozicki: moved table here

The User Experience team devlopes art, CSS, and other UI elements and is connected with the Dev team. Take a look around here, if you'd like to help, contact '''style@soylentnews.org''' or MrBluze on IRC.

There's a lot of documentation on [[CssWork|CSS work being done]] and you can find some notes on future [[Style:UI_Design|UI Design here]].

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| ?
|-
| audioguy
| ?
| UTC-8 (PST)
|-
| FrogBlast
| Art Team
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}
<section end=whoarewe />

==Todo==
*Define single column layout requirements - nearly done.
*Work with FrogBlast to get the full icon set done - in progress.
*Review/upgrade logo/banner art (with FrogBlast) - in progress.
*Typographic and typesetting guidelines (with LaminatorX) - awaiting feature request, then work with CSS ppl on a specification
*Weekly comic

[[Category:Teams]]
[[Category:User experience]]

SystemAdministration-OLD-2024

2014-04-03T17:45:38Z

Janek Kozicki: /* Who we are */ small fix

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[SystemAdministration|Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| ?
|-
| NCommander
| Member
| UTC-5
|-
| robind
| Member
| ?
|-
| Audioguy
| Member
| UTC-8 (PST)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

* [[soylent-www]] - Primary Apache and slash server for main site.
* soylent-db -- mysql server, holds the slash database
* slashcott - Holds the slashcott site, development machine
* [[soylent-services]] - mail, wiki, other services as needed

==Known Problems==

* '''Need cron job to backup server'''
* There are errors in the zone file in the spf TXT record -- Mechanicjay would be happy to fix this and clean up the zone file in general, but needs linode manager access from NCommander.
* No init script for Apache.
* Broken https configuration
** Mostly fixed, Slash is the problem child now

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turn off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)

[[Category:Teams]]
[[Category:System administration]]

WhosWho

2014-04-03T17:45:04Z

Janek Kozicki: /* Sysops */ and link it here.

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev@SoylentNews.org ([[#Development|Development]])
*editors@SoylentNews.org ([[#Content|Content]])
*suggestions@soylentNews.org ([[#Community Support|Community Support]])
*wiki@SoylentNews.org ([[#Wiki|Wiki]])
*chat@SoylentNews.org ([[#IRC|IRC]])
*style@SoylentNews.org ([[#Style|Style/User Experience]])
*art@SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| ?
|-
| mrcoolbp
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{#lst:Development|whoarewe}}

==Sysops==

{{#lst:SystemAdministration|whoarewe}}

==Style/User Experience==
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| ?
|-
| audioguy
| ?
| UTC-8 (PST)
|-
| FrogBlast
| Art Team
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}

==Content==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| UTC+2 (CET)
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| Cactus
| miscellaneous
| ?
|}

==Community Support==
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mrcoolbp
| Leader
| UTC-4 (EST/EDT)
|-
| xlefay
| ?
| UTC+2 (CEST)
|}

==Wiki==
{| 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)
|}

==IRC==
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Kobach
| Co-leader | Chief Bacon Officer
| UTC-5 (us/central)
|-
| MrBluze
| Member
| ?
|-
| Landon
| Member
| ?
|-
| FunPika
| Member
| ?
|}

==Notes==
<references />

SystemAdministration-OLD-2024

2014-04-03T17:44:26Z

Janek Kozicki: /* Who we are */ added nice table here.

[[TeamPages]] - parent, [[Development]]

==Welcome==

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

==Who we are==
<section begin=whoarewe />
{| class="wikitable" width="100%"
!colspan="3"|'''[[Development|Dev/Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| ?
|-
| NCommander
| Member
| UTC-5
|-
| robind
| Member
| ?
|-
| Audioguy
| Member
| UTC-8 (PST)
|}
<section end=whoarewe />

==Index of Development Pages and Resources==

===Servers===

* [[soylent-www]] - Primary Apache and slash server for main site.
* soylent-db -- mysql server, holds the slash database
* slashcott - Holds the slashcott site, development machine
* [[soylent-services]] - mail, wiki, other services as needed

==Known Problems==

* '''Need cron job to backup server'''
* There are errors in the zone file in the spf TXT record -- Mechanicjay would be happy to fix this and clean up the zone file in general, but needs linode manager access from NCommander.
* No init script for Apache.
* Broken https configuration
** Mostly fixed, Slash is the problem child now

==Work Notes==
DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

==Resources==
* [[SystemAdministration/AccessInstruction|Access Instructions]] - how to get on the nodes, get around, and kerberos for users primer
* [[SystemAdministration/GroupPermissions|Group Permissions]] - understanding our LDAP groups, what machines they can access, and where you can sudo
* [[SystemAdministration/LDAPManagementForDummies|LDAP Management for Dummies]] - how to do basic shit in that source of miserary known as LDAP
* [[SystemAdministration/TheRiseAndFallOfNewNodeManagement|The Rise And Fall Of New Node Management]] - from bash to fully intergrated node, this doc has it
* [[SystemAdministration/TheHitchhikersGuideToTheli694-22Domain|The Hitchhikerr's Guide to The li694-22 Domain]] - machine list, general information
* [[SystemAdministration/KerberosAdministration|Kerberos Administration Or Everything You Wanted To Know About Kerberos But Were Afraid To Ask]]
* [[DnsRecords]] - copy of the zone file pasted from the machine that was accidentally turn off
* [[EmergencyProcedures|Emergency Technical Procedures]] - in case of fire, break glass (Read before messing with servers)

[[Category:Teams]]
[[Category:System administration]]

Development

2014-04-03T17:35:35Z

Janek Kozicki: /* Who we are */ @nick

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable"
!colspan="4"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72<ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| Team Leader for Dev
| (EST/EDT current TZ-4)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| right hand man to paulej72 and second in command for Dev.
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| (TZ+2)
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

==Notes==
<references />

[[Category:Development]]
[[Category:Teams]]

Development

2014-04-03T17:32:44Z

Janek Kozicki: added refs

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable"
!colspan="4"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72
| Team Leader for Dev <ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| (EST/EDT current TZ-4)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy
| right hand man to paulej72 and second in command for Dev.<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| (TZ+2)
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

==Notes==
<references />

[[Category:Development]]
[[Category:Teams]]

WhosWho

2014-04-03T17:32:19Z

Janek Kozicki: added references

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev@SoylentNews.org ([[#Development|Development]])
*editors@SoylentNews.org ([[#Content|Content]])
*suggestions@soylentNews.org ([[#Community Support|Community Support]])
*wiki@SoylentNews.org ([[#Wiki|Wiki]])
*chat@SoylentNews.org ([[#IRC|IRC]])
*style@SoylentNews.org ([[#Style|Style/User Experience]])
*art@SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| ?
|-
| mrcoolbp
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{#lst:Development|whoarewe}}

==Sysops==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Development|Dev/Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| ?
|-
| NCommander
| Member
| UTC-5
|-
| robind
| Member
| ?
|-
| Audioguy
| Member
| UTC-8 (PST)
|}

==Style/User Experience==
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| ?
|-
| audioguy
| ?
| UTC-8 (PST)
|-
| FrogBlast
| Art Team
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}

==Content==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| ?
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| mrcoolbp
| editor
| UTC-4 (EST/EDT)
|-
| Cactus
| miscellaneous
| ?
|}

==Community Support==
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mrcoolbp
| Leader
| UTC-4 (EST/EDT)
|-
| xlefay
| ?
| UTC+2 (CEST)
|}

==Wiki==
{| 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)
|}

==IRC==
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Kobach
| Co-leader | Chief Bacon Officer
| UTC-5 (us/central)
|-
| MrBluze
| Member
| ?
|-
| Landon
| Member
| ?
|-
| FunPika
| Member
| ?
|}

==Notes==
<references />

Development

2014-04-03T17:30:14Z

Janek Kozicki: /* Who we are */ added references, does it correcly transclude?

[[TeamPages]] - parent, [[SystemAdministration]]

==Welcome==
We are currently looking for volunteers to help develop SoylentNews slashcode. Anyone willing is free to help, but '''we really need good perl devs'''. Slashcode is based heavily on perl and most pages have some type of perl code on them. We also seek non-perl devs, there is plenty of stuff that you can do without touching the code too much.

Our code is hosted on GitHub at https://github.com/SoylentNews/slashcode. Have a look and see how you can contribute. Bugs are now on [https://github.com/SoylentNews/slashcode/issues GitHub Bugs].

Volunteers should send an email to [mailto:dev@soylentnews.org dev@soylentnews.org] expressing your areas of interest and what your coding strengths are. Also you can hop onto [[SoylentNews:IRC]] and join the #dev channel. Come by and express your interest to paulej72, audioguy, or mrcoolbp.

Currently we are undergoing a bit of a reorganization and we hope to have more information available here soon about our short term and long term goals for the code.

== Who we are ==
<section begin=whoarewe />
{| class="wikitable"
!colspan="4"|'''[[Development|Dev Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| paulej72
| Team Leader for Dev <ref name="paulej72_notes">Working on template and css issues on the site, main bug herder. - email:[mailto:paulej72@soylentnews.org paulej72@soylentnews.org] [[Paulej72WorkNotes]]</ref>
| (EST/EDT current TZ-4)
|-
| Ncommander
| The real head of Dev, but due to time constrains of being the head of SN, only a member.
| UTC-5
|-
| audioguy
| right hand man to paulej72 and second in command for Dev.<ref name="audioguy_notes">See [[AudioGuyWorkNotes]] for current todo and working notes - documentation of system and cleanup of css to get things into a ste that new templates and Themes can be made.</ref>
| UTC-8 (PST)
|-
| FatPhil
| perl/mysql odd-jobber, some ubuntu/sys knowledge too
| (TZ+2)
|-
| martyb/bytram
| secondary bug herder, Database (in training)
| UTC-4 (EST/EDT)
|}
<section end=whoarewe />

== Index of Development Pages and Resources ==

Note: Any sort of code posted onto the wiki can now be syntax highlighted using the <nowiki><syntaxhighlight></nowiki> tag. It will default to perl, but can be changed to other languages. For example <nowiki><syntaxhighlight lang="sql"></nowiki>. More documentation is at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]].

* [[ImportantDevelopmentLinks]] - Place to put urls for the repositories, etc. (Use current page for now, this page not needed - YET)
* [[DevelopmentWorkCurrentlyInProgress]] - what we are working on at this moment
* [[CodingStyleForOurPerlChanges]] - Suggested style for perl code changes
* [[DevelopmentVMHowto]] - How to get your own Slash code up in a Virtual Machine using VirtualBox
* [[CssWork]] - pages for ongoing css work
* [[SlashDocumentationIndex]] - A single place to find Slash docs, one day it will be organized and accurate
* [[IncidentLog]] - Documentation of how incidents occurred and how they were mitigated
* [[GitUse]] - Tutorial/advice on how to use git
* [[Dev/Sys|To-do]] - A list of items in the pipeline collected from various places

== Work Notes ==

* [[AudioGuyWorkNotes]]
* [[Paulej72WorkNotes]]

== Resources ==

* [[SystemAdministration]] - See this section for actual server details and procedures
* GitHub https://github.com/SoylentNews/slashcode: Slashcode Repository and Issue Tracker
* Wiki: Documentation and work logs
**hosted on the svc linode
* IRC: real time chat for team communications
* Slashcott.org: temporary testing server in use until we get ones setup on Linode.
* Mailman Dev Mailing list: for non-real-time discussions that need a good paper trail.
* http://dev.mysql.com/doc/refman/5.5/en/index.html - Official docs for mysql we use
* https://perl.apache.org/start/index.html - modperl docs (We use version 1 with Apache 1.3)
* http://remote.demmers.org/~audioguy/manual/ - Apache 1.3 docs don't seem to be on the Apache site any more, here they are.
** http://remote.demmers.org/~audioguy/manual/misc/API.html but this is what is important to understand slash workings with mod perl.

== Slashcode Primer ==

Slashcode is a complex beast. Here is the listing of the repo:

<blockquote><code><pre>Bundle
Slash
bin
docs
httpd
plugins
sbin
sql
tagboxes
themes
utils
</pre></code></blockquote>

We really are only concerned with three of these directories: Slash, plugins, and themes. The first directory, Slash, is the home of the slash.pm module and its related code. The module, slash.pm, does all of the back end work of slashcode. It provides a set of APIs that are used to generate pages and manipulate the database. This is where the heavy perl coding is done. We definitely need help with this section in both expanding our knowledge and working with the code. (As I started on this from a css/html slant I do not have a good idea of what is here --pauej72)

The second main part of the system are the themes. In this case we have only one theme called slashcode. The theme is broken down into pieces the first is htdocs. htdocs is all of the static html files, perl files that directly start page generation events, the css files, images, and other static code. The second part of the theme is the templates. These templates are loaded into the database an are used by slash to layout the data from different sources and turn them into html files that apache can send to the user. Templates re a mixture of perl, slash coding, and html. Templates use slash calls to load other templates and usually each template leaves a breadcrumb in the final html with a start and end comment with the template's name and id. These breadcrumbs make it easy to find out which template file is generating the particular piece of html that you need to change.

Slashcode also has a plugin architecture that allows certain system to be bolted on to the main system. The main system is basically articles, comments and users. The pulgins add the admin interface, the messaging system, enhanced login, journals, and other things. The files for these plugging are in the plugins folder, not in the theme folder. The issue with plugins is that it contains both front end code such as templates, css and pl files, it also has perl modules that are loaded into the perl engine.

The rest of the directories are used for build and install purposes and probably will not need to be modified regularly.

This is a work in progress so please check back here for more.

== Development VM ==

(audiogy note - will leave this here for the moment, it belongs on its own page as referenced above)

The Dev VM can be downloaded from http://torrents.soylentnews.org/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: http://torrents.soylentnews.org/.

Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

The VM has port forwarding setup to you local system for ssh and http.

<blockquote><code>ssh: 8022<br/>
http; 1337</code></blockquote>

For ssh your connection string should be:

<blockquote><code>ssh slash@127.0.0.1 -p 8022</code></blockquote>

For websites, apache will use the name localhost instead of 127.0.0.1 so you will need to use:

<blockquote><code>http://localhost:1337 </code></blockquote>

Apache is turned off in the VM. You will need to turn it on using the command:

<blockquote><code>apachectl start</code></blockquote>

The slash user home directory is in /srv/slashdev/. The slashcode GitHub repository is located in slashcode. This is where you will make changes to the code you want to test. The actual slashcode install is located in slash.

The first thing you should probably do is update the repo to the latest version. cd to slashcode and run git pull.

Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and give chmod it to 755.

deployslash.sh

<blockquote><code>#! /bin/sh<br/>
<br/>
echo === Install from git repo ===<br/>
echo<br/>
cd /srv/slashdev/slashcode<br/>
make USER=slash GROUP=slash SLASH_PREFIX=/srv/slashdev/slash install<br/>
<br/>
echo<br/>
echo<br/>
echo === Clean up CSS and install Templates ==<br/>
echo<br/>
rm -rf /srv/slashdev/slash/site/slashdev/htdocs/*css<br/>
<br/>
/srv/slashdev/slash/bin/symlink-tool -U<br/>
/srv/slashdev/slash/bin/template-tool -U<br/>
<br/>
echo<br/>
echo<br/>
echo === Restart Apache ===<br/>
echo<br/>
/srv/slashdev/apache/bin/apachectl restart<br/>
</code></blockquote>

This script will be part of the next version of the Dev VM.

To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:

<blockquote><code> git remote add {name} {url-to-your-GitHub-repo}<br/>
git fetch {name}<br/>
git checkout {name}/master</code></blockquote><br/>

Redeploy slash and you are working from your own repo. As you may have noticed the primary work is being done on the master branch. You will not need to worry about the other branches of the code for now.

Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers.

Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

crutchy has some additional notes on git here: [[User:Crutchy#Git.2FGitHub]] and some notes on the slashdev vm here: http://soylentnews.org/~crutchy/journal/114

[[Category:Development]]
[[Category:Teams]]

WhosWho

2014-04-03T17:12:51Z

Janek Kozicki: /* Style/User Experience */

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev@SoylentNews.org ([[#Development|Development]])
*editors@SoylentNews.org ([[#Content|Content]])
*suggestions@soylentNews.org ([[#Community Support|Community Support]])
*wiki@SoylentNews.org ([[#Wiki|Wiki]])
*chat@SoylentNews.org ([[#IRC|IRC]])
*style@SoylentNews.org ([[#Style|Style/User Experience]])
*art@SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| ?
|-
| mrcoolbp
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{Development team}}
==Sysops==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Development|Dev/Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| ?
|-
| NCommander
| Co-leader
| UTC-5
|-
| robind
| backup leader
| ?
|}

==Style/User Experience==
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| ?
|-
| audioguy
| ?
| ?
|-
| FrogBlast
| Art Team
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}

==Content==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| ?
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| Cactus
| miscellaneous
| ?
|}

==Community Support==
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mrcoolbp
| Leader
| UTC-4 (EST/EDT)
|-
| xlefay
| ?
| UTC+2 (CEST)
|}

==Wiki==
{| 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)
|}

==IRC==
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Landon
| ?
| ?
|-
| MrBluze
| ?
| ?
|-
| Kobach
| Chief Bacon Officer
| UTC-5 (us/central)
|-
| FunPika
| ?
| ?
|}

see also: the now out-of-date [[Staff list]].

WhosWho

2014-04-03T17:04:30Z

Janek Kozicki: /* IRC */

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev@SoylentNews.org ([[#Development|Development]])
*editors@SoylentNews.org ([[#Content|Content]])
*suggestions@soylentNews.org ([[#Community Support|Community Support]])
*wiki@SoylentNews.org ([[#Wiki|Wiki]])
*chat@SoylentNews.org ([[#IRC|IRC]])
*style@SoylentNews.org ([[#Style|Style/User Experience]])
*art@SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| ?
|-
| mrcoolbp
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{Development team}}
==Sysops==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Development|Dev/Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| ?
|-
| NCommander
| Co-leader
| UTC-5
|-
| robind
| backup leader
| ?
|}

==Style/User Experience==
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| ?
|-
| audioguy
| ?
| ?
|-
| FrogBlast
| Art Team Director CEO
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}

==Content==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| ?
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| Cactus
| miscellaneous
| ?
|}

==Community Support==
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mrcoolbp
| Leader
| UTC-4 (EST/EDT)
|-
| xlefay
| ?
| UTC+2 (CEST)
|}

==Wiki==
{| 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)
|}

==IRC==
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Landon
| ?
| ?
|-
| MrBluze
| ?
| ?
|-
| Kobach
| Chief Bacon Officer
| UTC-5 (us/central)
|-
| FunPika
| ?
| ?
|}

see also: the now out-of-date [[Staff list]].

WhosWho

2014-04-03T17:03:05Z

Janek Kozicki: set column widths to 20%,40%,40%

In the interest of getting questions to the right people on via email or IRC, this is a summary of who is involved in SoylentNews. If you'd like to work with a team directly, try the [[TeamPages]]. Please add yourself here if you are actively working on the project.

==Team Contacts==

Teams are guided by leaders that may occasionally change. Teams can always be contacted directly at the following addresses:

*dev@SoylentNews.org ([[#Development|Development]])
*editors@SoylentNews.org ([[#Content|Content]])
*suggestions@soylentNews.org ([[#Community Support|Community Support]])
*wiki@SoylentNews.org ([[#Wiki|Wiki]])
*chat@SoylentNews.org ([[#IRC|IRC]])
*style@SoylentNews.org ([[#Style|Style/User Experience]])
*art@SoylentNews.org ([[#Art|Art]])

==The Man Behind The Curtain==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| NCommander
| Site-wide responsibility
| UTC-5
|}

==Administration==
{| class="wikitable" width="100%"
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mattie_p
| General Manager/Head Team Leader/Lead Cat herder
| ?
|-
| mrcoolbp
| [[CommunitySupport]]
| UTC-4 (EST/EDT)
|}

==Development==

{{Development team}}
==Sysops==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Development|Dev/Sysop Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| mechanicjay
| Co-leader
| ?
|-
| NCommander
| Co-leader
| UTC-5
|-
| robind
| backup leader
| ?
|}

==Style/User Experience==
{| class="wikitable" width="100%"
!colspan="3"|'''[[UserExperience|User Experience Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| MrBluze
| Team Leader
| ?
|-
| audioguy
| ?
| ?
|-
| FrogBlast
| Art Team Director CEO
| ?
|-
| shogun - HTML
| ?
| ?
|-
| moo_kuh - Testing
| ?
| ?
|-
| PrestonL
| CSS / Bug Testing
| ?
|-
| mtrycz
| User Interface
| ?
|-
| CynicGalahad
| Website Design
| ?
|}

==Content==
{| class="wikitable" width="100%"
!colspan="3"|'''[[Editors|Editors Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| LaminatorX
| Team Leader
| ?
|-
| Dopefish
| editor
| ?
|-
| mattie_p
| editor
| ?
|-
| janrinok
| editor
| ?
|-
| MrBluze
| editor
| ?
|-
| girlwhowaspluggedout
| editor
| ?
|-
| Cactus
| miscellaneous
| ?
|}

==Community Support==
{| class="wikitable" width="100%"
!colspan="3"|'''[[CommunitySupport|Community Support Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| mrcoolbp
| Leader
| UTC-4 (EST/EDT)
|-
| xlefay
| ?
| UTC+2 (CEST)
|}

==Wiki==
{| 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)
|}

==IRC==
{| class="wikitable" width="100%"
!colspan="3"|'''[[IRC|IRC Team Main Page]]'''
|-
| style="width: 20%; background-color: #f2f2f2;"|
'''nick'''
| style="width: 40%; background-color: #f2f2f2;"|
'''position'''
| style="width: 40%; background-color: #f2f2f2;"|
'''timezone'''
|-
| xlefay
| Team leader
| UTC+2 (CEST)
|-
| Landon
| ?
| ?
|-
| MrBluze
| ?
| ?
|-
| Kobach
| Chief Bacon Officer
| UTC-4 (us/central)
|-
| FunPika
| ?
| ?
|}

see also: the now out-of-date [[Staff list]].

WhosWho

2014-04-03T16:55:54Z

Janek Kozicki: set table width to 100%

WhosWho

2014-04-03T16:47:56Z

Janek Kozicki: Added timezone information, reformatted everything into tables.

WhosWho

2014-04-03T16:16:45Z

Janek Kozicki: /* Community Support */ added timezones for Community Support

WhosWho

2014-04-03T16:14:05Z

Janek Kozicki: /* Wiki */ testing addition of timezone information.

WhosWho

2014-03-30T19:35:39Z

Janek Kozicki: /* Wiki */

User:Janek Kozicki

2014-02-20T16:25:41Z

Janek Kozicki: Created page with "Hi, Sometimes I do a little editing of our wiki."

Hi,

Sometimes I do a little editing of our wiki.

Engine requirements

2014-02-13T17:57:38Z

Janek Kozicki: added science channel

* '''Be mindful of bandwidth and the amount of processing done by the server when building any features. One extra character balloons into many megabytes of expensive bandwidth and consumption of server resources. Each feature that bloats a page response or causes the server to process something increases costs--KEEP COSTS DOWN!'''
* UTF-8 clean for anything that doesn't end up in a URL (i.e. tags, titles, channel names, user names)
** Of course, some combining marks would have to be filtered, and the resulting text round-tripped through NFD->NFC to prevent certain types of attacks against users or making text difficult to index.
* [http://blog.stackoverflow.com/2011/04/stack-exchange-partners-with-mathjax/ MathJax] support both in comments and in submissions
:: Mathjax is the math rendering engine used on [http://stackexchange.com/ stackexchange] and will allow scientific discussion between us (people who read math).
* Channels (like yro, science, politics, apple) as first class objects
** "Primary" channels that have DNS shorthand (http://apple.altslash.org/ being equiv to http://altslash.org/ch/apple/)
** "Secondary" channels that users could create and play editor that use the more verbose syntax (http://altslash.org/ch/baseball/) that is reminiscent of subreddits
** User channels (i.e. journals, as we've always had)
* Display user IDs
* Javascript Optional
** I enjoy having the comment rating slider for example, but main functionality should be accessible with lynx at the least!

* Submission queues for all channels with membership at the discretion of the channel owner; being able to submit also implies up/downvoting submissions and tagging
:: Editors/channel owners only
:: List of users who can submit
:: All of my friends (for user journals)
:: All users with mod status
:: All registered users
:: Everyone

* Articles are also first class objects
:: Perma-link independant of channel
:: Articles are tagged by topic(s) as well as channel
:: Articles are automatically archived
:: Archive is easily searchable, and should be referenced when submissions are edited.
:: Articles can be cross-posted to other channels by a channel owner (built into the UI if the editor manages more than one channel)
* Comment key features
:: Comments are first class objects, just as before, just like articles
:: Comments can be edited for a short period of time by owner
::: HOWEVER: Edited comments get a new ID and it links to older versions in the new one. This detail is made prominent to viewer if a comment reply happened before an edit.
:: Allow alternate markup options (bbcode, markdown, wiki markup)
::: Provide a mapping to actual div and styles that will be applied, or HTML equivalent codes

* Allow moderation in same article that you've posted in; only disallow moderation '''to your own reply chain'''.
** You're obviously not allowed to moderate in your own accepted or posted article (treating all comments as replies)
** Does "reply chain" include parent? If not, how do we deal with threadjacking:
**# AC posts first comment on a new article (let's presume it's an upmod-worthy comment, not fristpsot)
**# I post my unrelated comment as a reply to AC's FP, in order to achieve greater visibility
**# I downmod the AC to -1
**# Now AC is invisible to anyone with threshold != -1 (including many with mod points and threshold=0, who would have modded AC up on his own merits)
**# Unless/until users with threshold=-1 and mod points happen by to rectify things, my comment is now the first thing most users see.
**# ??? ''(sorry, can't resist...)''
**# Profit!
***Actually, not just the immediate parent like I said, but 'all' ancestor comments. Otherwise as step 1.5 I just reply with an AC troll (which someone else will rightfully downmod), then in step 2 I reply to ''that''; now that the original AC first post is my comment's gp, so I can still downmod it.
** ''' Good point ''' you should be prevented from moderating any children '''and''' ancestors of your posts (but sibling chains are still fair game)