|
Sidebar
|
First email to contractor
Developer
Hello,
We are a XXX IT firm that delivers XXX based websites to clients. We are looking for one or more reliable developers to join our network of contractors.
- Strong XXX experience
- Can do everything without modifying the core
- Must be able to use a bug tracker
- Excellent communication skills, good English
- Excellent attention to detail, especially documentation
- Able to quickly orient yourself to projects already underway
- Anywhere from 10 to 40 hours per week over the next month
- Ability to use a bug tracking system
- Must use a versioning tool
- When will you be available?
- What is your QA process?
- How do you document a project?
- What's your website address?
- Do you have any references?
- How many are you?
- Where are you based?
We would like to set up a trial in order to establish a long term partnership.
We will give you an access to our bugtracker where you will find all you need to know about our processes, your trial tasks and the related project documentation.
For the trial period you will be paid at job completion. If we both decide to go further, then we will get you to sign our contract.
You will invoice us at the end of each month and be paid within 30 days.
Let me know if you need any more details and if you agree to such working process.
Kind regards,
Sysadmin
Hello,
We are a XXX IT firm that delivers XXX based websites to clients. We are looking for a sysadmin who:
- has strong skills in: ability to document, Centos, bind9, follow process and use a bugtracker, SSH, Apache, user management, Syslog, Postfix, filesystem, log analyzing, TCP/IP protocol, english
- Debian skilled,
- knows how to maintain: PHP, MySQL, LDAP, Git, Gitosis, Subversion
- understands business emergency, is able to answer promptly.
Our park is composed of XXX servers under XXX, for most of them they are XXX.
Your work will include:
- server installations,
- migration of servers & domains,
- server updates and checks,
- setting up client specific development environments,
- backup,
- creating and completing documentation.
- ...
Let me know if you need more details.
Kind regards,
Page last modified on Tuesday 10 of August, 2010 14:01:53 UCT
Wiki Syntax
For more information, please see
Wiki Page Editor
and
Wiki Syntax
Wiki Syntax |
Bold text __text__ |
Italic text 2 single quotes ('). ''text'' |
Underlined text ===text=== |
Colored text ~~#FFEE33:text~~ or ~~yellow:text~~. Will display using the indicated HTML color or color name. Color name can contain two colors separated by a comma. In this case, the first color would be the foreground and the second one the background. |
Deleted text 2 dashes "-". --text-- |
Headings !heading1, !!heading2, !!!heading3 |
Show/Hide !+, !!- show/hide heading section. + (shown) or - (hidden) by default. |
Autonumbered Headings !#, !!#, !+#, !-# ... |
Table of contents {toc}, {maketoc} prints out a table of contents for the current page based on structures (toc) or ! headings (maketoc) |
Horizontal rule ---- |
Text box ^Box content^ |
Centered text ::text:: |
Dynamic variables %Name% Inserts an editable variable |
External links use square brackets for an external link: [URL], [URL|link_description],[URL|link_description|relation] or [URL|description|relation|nocache] (that last prevents the local Wiki from caching the linked page; relation can be used to insert rel attribute for the link - useful e.g. for shadowbox).
For an external Wiki, use ExternalWikiName:PageName or ((External Wiki Name: Page Name)) |
Square Brackets Use [[foo] to show [foo]. |
Wiki References ((page)) or ((page|description)) for wiki references
, ((page|#anchor)) or ((page|#anchor|desc)) for wiki heading/anchor references
|
Lists * for bullet lists, # for numbered lists, ;Word:definition for definiton lists |
Indentation +, ++ Creates an indentation for each plus (useful in list to continue at the same level) |
Tables ||row1-col1|row1-col2|row1-col3 row2-col1|row2-col2|row2-col3|| |
Title bar -=Title=- |
Monospace font -+Code sample+- |
Line break %%% (very useful especially in tables) |
Multi-page pages Use ...page... to separate pages |
Non parsed sections ~np~ data ~/np~ Prevents wiki parsing of the enclosed data. |
Preformated sections ~pp~ data ~/pp~ Displays preformated text/code; no Wiki processing is done inside these sections (as with np), and the spacing is fixed (no word wrapping is done). ~pre~ data ~/pre~ also displayes preformatted text with fixed spacing, but wiki processing still occurs on the text. |
Comments ~tc~ Tiki Comment ~/tc~ makes a Tiki comment. It will be completely removed from the display, but saved in the file for future reference. ~hc~ HTML Comment ~/hc~ makes an HTML comment. It will be inserted as a comment in the output HTML; these are not normally displayed in browsers, but can be seen using "View Source" or similar. |
Direction {r2l}, {l2r}, {rm}, {lm}Insert resp. right-to-left and left-to-right text direction DIV (up to end of text) and markers for langages as arabic or hebrew. |
Special characters
~hs~ hard space,
~c~ ©,
~amp~ &,
~lt~ <,
~gt~ >,
~ldq~ “,
~rdq~ ”,
~lsq~ ‘,
~rsq~ ’,
~--~ —,
~bs~ \,
numeric between ~ for html numeric characters entity |
Because the Wiki paragraph formatting feature is on, all groups of non-blank lines are collected into paragraphs. Lines can be of any length, and will be wrapped together with the next line. Paragraphs are separated by blank lines.
|
|
Post new comment