Internal IT Policy

This is Nemein's internal IT Policy. It is provided as public resource to support transparency and explain our way of working with client data.

Work reporting

  • Work hours for all customer work is reported on the same day using OpenPSA Projects.
    • If suitable task can't be found it must be opened
    • All invoicing information in Projects must match project or maintenance agreement with the client
    • Work descriptions must be in language acceptable to the client, avoid terms "fixing" and "bugs"
    • Subcontractors also report their hours to the client projects for invoicing reasons
    • Salaries for hour workers are calculated from Projects on 15th of every month
  • All TODO items must be tracked via OpenPSA Support
    • Move all TODO emails to the Support inbox
    • Tell clients to send messages to support@nemein.com
    • Assign correct categories to TODO items
    • Monitor your Support ticket queue at least once a day
  • Expenses and mileages are reported using OpenPSA Projects
    • Write record ID from Projects to each receipt and deliver to financial admin

Information Management

  • Meetings and other time allocations are stored in OpenPSA Calendar
    • All meetings and personal engagements during office time must be kept up to date
  • Meeting notes and specifications are stored in HTML format to the appropriate client folder in Nemein Extranet
    • Ensure the client and possible partners have required permissions for accessing the Extranet folder
  • Contact information is stored into OpenPSA Sales
    • Received business cards must be typed in and then may be discarded
    • Clients-type companies will be automatically listed on nemein.com as references

Information Distribution

  • Interesting links must be shared via personal del.icio.us accounts
    • Use tag categories from the http://del.icio.us/bergie account where applicable
    • Ensure your del.icio.us account is aggregated to "Nemein research roll"
  • Blogging enables us to communicate with our client and developer connections in an informal fashion
    • Don't mention client names or specifics without permission
    • Blog all major new OpenPSA or other software features together with screenshots
    • Ensure your blog feed is aggregated to nemein.com, Planet Midgard and OpenPSA news
    • Build your blog with Midgard. It can be hosted on nemein.com
  • Fast documentation with the Markdown
    • Read the basics , and commit yourself to the Nemein's conventions listed below
    • Headings: use hash (#) characters, i.e.
      # Header1
      ## Header2
      ### Header3
    • Highlighting: use underscore (_) for emphasis and double underscore (__) for strong
    • Lists: use asterisk (*) for bullets
    • Links and attachments: use reference style, i.e.
      [Google][1] rocks! [Read more][2]

      [1]: http://www.google.com/ "THE search engine of the WWW"
      [2]: http://www.example.com/software/manual/ "The end user manual"
    • See this page in Markdown for reference

Security

  • Email
    • All emails must be GPG signed
    • Internal emails and emails with GPG-enabled partners must be encrypted
    • Use either webmail or SSL-encrypted IMAP for reading email
  • Backups
    • Synchronize your home directory to the devel.nemein.net server every week
 
 
Nemein - Open Source Consultancy

Copyright © 2001-2010 Nemein Oy, Finland. Built with Midgard CMS, XHTML and CSS with Web Standards in mind.