summaryrefslogtreecommitdiff
path: root/index.mdwn
blob: b57c0684d73af6046c3414d00f8291131fde1660 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
[[!meta title="Ick—continuous integration system"]]

[[img ick-logo.svg width=300 height=300 class=float_right]]

**Ick** will be a continuous integration system. It is currently in
development, and will hopefully reach the first ALPHA release in the
not too distant future.

Motto
=============================================================================

CI should be fun.

Why yet another CI system?
=============================================================================

**Ick** aims to become a system that's less hassle to set up or
operate or keep running than any other publically available
self-hosted system, without compromising correctness or security.

See [[origin|blog/2017/10/10/origin]] for a description of how Ick got
started.


Manifesto
=============================================================================

Continuous integration (CI) is powerful tool for software development.
It should not be tedious, fragile, or annoying. It should be quick and
simple to set up, and work quietly in the background unless there's a
problem in the code being built and tested.

A CI system should be simple, easy, clear, clean, scalable, fast,
comprehensible, transparent, reliable, and boost your productivity to
get things done. It should not be a lot of effort to set up, require a
lot of hardware just for the CI, need frequent attention for it to
keep working, and developers should never have to wonder why something
isn't working.

A CI system should be flexible to suit your build and test needs. It
should support multiple types of workers, as far as CPU architecture
and operating system version are concerned.

Also, like all software, CI should be fully and completely free
software and your instance should be under your control.

(Ick is nothing of this yet, but it will try to become all of it. In
the best _possible_ taste.)


Download
=============================================================================

* Source code for git: [browser](http://git.liw.fi/ick2/), git (`git://git.liw.fi/ick2`)
  * Source for this website:
    [browser](http://git.liw.fi/ick.liw.fi),
    git (`git://git.liw.fi/ick.liw.fi`)
* Debian packages: [code.liw.fi](https://liw.fi/code/): Add to your
  APT sources: `deb http://code.liw.fi/debian unstable main`
* Ansible playbook: [browser](http://git.liw.fi./ick2-ansible/),
  git (`git://git.liw.fi/ick2-ansible`)


Project management
=============================================================================

Latest meetings:

[[!inline pages="page(blog/*) and tagged(meeting)" 
  limit=3 template=titlepage archive=yes trail=no feeds=no]]

More info:

* Project [[governance]].
* [[Architecture]]
* [[Process desciption|pm]]
  * [[Current and past projects|projects]]
  * [[Tasks to do if you want to help|tasks]]
* [[Roadmap to ALPHA-1|roadmap]]
* [[Development blog|blog]] (see [[feeds|blog_feed]] also).
* [[Tips on various topics|tag/tip]]
* [[Issue tracking|issues]] ([direct link](http://ick-devel.liw.fi/))
  - Any mails sent to `ick-devel@liw.fi` get imported into the
    issue tracking automatically.
  - See list of [[suggestions for getting started|getting-started]].
* IRC: `#ick` on irc.oftc.net.