Present, absent and so on

• present: netforce, emily, netforce, megalive, webrat
• absent: runemaste

Agenda

Team Status

Some things are not working as they should and some members complaint about it. Time to discuss!

Moved: Will be discussed with last points

JOTI

JOTI 2011 is coming closer. What needs to be done before, how will we handle things?

* We will clean out servers that are slow and so on:
Actions:
- Figure out what inspircd does and what creates the maxuserlimit of 1K
- Inventory Servers
--> Payload test
--> Select stable
--> Select fastest
--> Select Best connected
--> Test speeds between servers and select links on that

- Roger is JOTI Coord we will ask him and council for their requirements. Answer by next council meeting

Temp olines:

People should use http://sco.scoutlink.net/sco/svsmgmt/request-oline/
We will remind them on time to do so.		
Request per email are only answered with "do it via sco"		

HowTo JOTI powered by TechTeam		
we will write up how things should be requested and so on

SCO:
 - Emergency Button for reset of rights in a channel (eg mlock)
  - Sends email to all council members plus techteam when used with detailled information
  - Can be used by tempirops, ircops and ccs
  - maybe revokation of rights

Assistant Sub Team

We need to find members and establish the Sub Team.

Requirements:
 - Technical knowledge (basics) of DNS: TCP/IP
 - Good knowlegde and know how to lookup info for services and ircd
 - trustworthy
 - willing to learn
 - survive some questions
 - about 3 members
 - should be really active
 - preferred from different geographic regions
anti requirements:
 - people looking only for power
 - people we can't work together (eg very rude and offensive in public mails)
 !! everbody sends pro and cons to mailinglist for each of them. we will make a decision there.

Tools

• We need a BugTracker for SCO development

- connection to git would be good
- not too overloaded with crap
- test some:
 -- jira (license?)
 -- redmine
 -- others
- report back
http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems

• Do we want to keep current Ticketing System or do we want something else (eg. OTRS)

- we check with not that high priority for alternatives
- requirements (additional to what we have)
 -- merging
 -- splitting
 -- queues
 -- multiple incoming mail adresses (usable for many teams)
 -- ticket states (stalling, waiting, todo)
 -- does not mess up emails with code in them
- test otrs and maybe change to it

• Migration to GIT

We will migrate from svn to git because it is sooo much cooler... and for some real reasons also :)
- netforce will do migration of svn to git
- migration of scripts and sco is task for everyone
- netforce set up a wiki page with some rules for using git at techteam

• Which other tools would make our life easier

hopefully we are happy with what we will have soon

• Do we offer Webservicesfor all?

- ssl mandatory
- dunno if it is secure (sucks!)

-it stays non public test  --> add htpass

• Password management cPassManmaybe?

we will test it on tt 
 - check if it is secure

Technical stuff

• Do we want to takeover scoutlink.net / scoutlink.org

we need ipv6 glues which we currently cant get if it stays registered via scoutnet.be
old ns servers (ns1) appear randomly and then do not work
we want to change the glue records
faster fixing of the whole domain when scoutnet breaks again.
-> bring it up to council

• Do we want central Auth? LDAP....

yes
start small (only username, pass, mail)
increase amount of data in future (eg dns, opers, and so on)
not yet sure if slave or master (really rw and so on)
there are more important things like backup documentation

• Documentation & Backup

- redesign backup
- document in own wiki article
- monthly check if everything is fine (backup + restore)
- monitoring backups

- document E V E R Y T H I N G in wiki

Communication

• How do we make sure that everybody in the team knows what is happening so everyone can have their say
• How do we keep it simple AND informative
• Which decisions are necessary to tell users/theteam/council about (and how) so we improve our communication with the whole network.

- wiki should have two sections per article. one techie compatible one for the outer world
- send mail plus globals before bigger network changes. Also put a note on website (your choice) / check back with other techies. Send these notifications early enough and then remind users again when starting
- really big things: 1 week before, normal: 1 day, small: 1 hour, just a poop: do it right now
- better send too much notifications that to few. only tell what needs to be told but do not leave important info