From 870755492d9da4414722cbef397206f98e2a84d2 Mon Sep 17 00:00:00 2001 From: distix ticketing system Date: Sun, 1 Apr 2018 08:36:05 +0000 Subject: imported mails --- .../cur/.this-dir-not-empty/.empty/empty-file | 0 .../new/.this-dir-not-empty/.empty/empty-file | 0 .../Maildir/new/1522571765.M471353P19349Q1.koom | 137 +++++++++++++++++++++ .../tmp/.this-dir-not-empty/.empty/empty-file | 0 .../4bbc9995f89d40c59451b743be4a4811/ticket.yaml | 6 + 5 files changed, 143 insertions(+) create mode 100644 tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/cur/.this-dir-not-empty/.empty/empty-file create mode 100644 tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/.this-dir-not-empty/.empty/empty-file create mode 100644 tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522571765.M471353P19349Q1.koom create mode 100644 tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/tmp/.this-dir-not-empty/.empty/empty-file create mode 100644 tickets/4bbc9995f89d40c59451b743be4a4811/ticket.yaml diff --git a/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/cur/.this-dir-not-empty/.empty/empty-file b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/cur/.this-dir-not-empty/.empty/empty-file new file mode 100644 index 0000000..e69de29 diff --git a/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/.this-dir-not-empty/.empty/empty-file b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/.this-dir-not-empty/.empty/empty-file new file mode 100644 index 0000000..e69de29 diff --git a/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522571765.M471353P19349Q1.koom b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522571765.M471353P19349Q1.koom new file mode 100644 index 0000000..7ad841b --- /dev/null +++ b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522571765.M471353P19349Q1.koom @@ -0,0 +1,137 @@ +Return-Path: +X-Original-To: distix@pieni.net +Delivered-To: distix@pieni.net +Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221]) + by pieni.net (Postfix) with ESMTPS id 03CE542BC6 + for ; Sun, 1 Apr 2018 08:35:03 +0000 (UTC) +Received: from platypus.pepperfish.net (unknown [10.112.101.20]) + by yaffle.pepperfish.net (Postfix) with ESMTP id D7C86417AB + for ; Sun, 1 Apr 2018 09:35:02 +0100 (BST) +Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1f2YS6-0006cB-Qd; Sun, 01 Apr 2018 09:35:02 +0100 +Received: from koom.pieni.net ([88.99.190.206] helo=pieni.net) + by platypus.pepperfish.net with esmtpsa (Exim 4.80 #2 (Debian)) + id 1f2YS5-0006aV-KL + for ; Sun, 01 Apr 2018 09:35:01 +0100 +Received: from exolobe3 (62-78-212-250.bb.dnainternet.fi [62.78.212.250]) + by pieni.net (Postfix) with ESMTPSA id 1298742BC6 + for ; Sun, 1 Apr 2018 08:35:01 +0000 (UTC) +Message-ID: <1522571699.2971.5.camel@liw.fi> +From: Lars Wirzenius +To: ick discussions +Date: Sun, 01 Apr 2018 11:34:59 +0300 +X-Mailer: Evolution 3.22.6-1+deb9u1 +Mime-Version: 1.0 +X-Pepperfish-Transaction: fd69-0633-0679-0c3b +X-Pepperfish-Transaction-By: platypus +Subject: What's needed before ick is ready for others to use? +X-BeenThere: ick-discuss@ick.liw.fi +X-Mailman-Version: 2.1.5 +Precedence: list +List-Id: discussions about the ick CI system +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +Content-Type: multipart/mixed; boundary="===============1981900298181275554==" +Mime-version: 1.0 +Sender: ick-discuss-bounces@ick.liw.fi +Errors-To: ick-discuss-bounces@ick.liw.fi + + +--===============1981900298181275554== +Content-Type: multipart/signed; micalg="pgp-sha512"; + protocol="application/pgp-signature"; boundary="=-k/tR+cykGEvElN27YF+k" + + +--=-k/tR+cykGEvElN27YF+k +Content-Type: text/plain; charset="UTF-8" +Content-Transfer-Encoding: quoted-printable + +This morning I've been pondering on the following question: should I +try to achieve "ready for others to use" as soon as possible, or +should I concentrate on making sure all existing functionality is of +high quality? + +The big difference is that the former would hopefully result in +contributions from others sooner, the latter is would hopefully avoid +a deluge of bug reports. + +I am leaning towards the former. Perfectionism is good, but it makes +things take a really long time and if things take too long, I get de- +motivated. "Write shit, but fix it quickly." + +So what would it take for ick to be ready for others to use? Note that +it doesn't have to be perfect, it needs to work just well enough that +others are able to do at least something useful with it. + +Here's my list, and I would appreciate feedback on this. Quick first +reactions are fine, no need to polish and do deep thinking. + +* ick builds and publishes its own .deb packages. Presumably +this=3DC2=3DA0 +=C2=A0 would mean others can do the same for their own projects. + +* Ick has at least a rudimentary notification system. The current +=C2=A0 approach is to run "watch icktool status" and that's not really +=C2=A0 good enough. Notification by email would be enough, I think. + +* Uses Qvisqve for authentication. The current approach of having +=C2=A0 every API client create its own access tokens is silly. + +* ick constructs a build graph of all pipelines at the starts of +a=3DC2=3DA0 +=C2=A0 build. This means that it won't be necessary to trigger each +=C2=A0 pipeline by hand and opens up a future where executing different +=C2=A0 actions concurrently on different workes is a possibility. + +* ick can do incremental builds by populating the workspace from=3DC2=3DA0 +=C2=A0 previous build. This means that if one source file changes, it's +=C2=A0 no longer necessary to do a full build. + +What do you all think? Is there something you can think of that ick +must do before you'd be willing to give it a try? +--=-k/tR+cykGEvElN27YF+k +Content-Type: application/pgp-signature; name="signature.asc" +Content-Description: This is a digitally signed message part +Content-Transfer-Encoding: 7bit + +-----BEGIN PGP SIGNATURE----- + +iQIzBAABCgAdFiEETNTnrewG6wEE1EJ3bC+mFux6IDEFAlrAmbMACgkQbC+mFux6 +IDGh+Q//R5fHOa3UO+wHPdS0CUQUiaZcshq8EDq37+IV40+6H82rAAxwv4CeTRyp +bRw9mTZXUNw+vhpjApnhdbC+vq6W/9hbRzZo+wLeQNufsK4CFVJvvgHwIA0lG4EH +HDtsIaO2tal5whf8qVWinkeuacEQ1cFh7T5Lz+W/QTwdiZF/GpqU9+eSzRF4vNYU +5uW5mqgNEbGT5gdz1jtucgHM1z9lKK0o7iSze3AKNqwws5zsF//bjMT0wbeuF5AQ +wm3C1iM56AMUj+f0rSQEFv02QgYD6zxhB7gvBKK6Ll2ps6Sn1ESM0waftYI3hlih +DYAXVTkE+a0QRCHm8ta5CRnFSNppELCGj/dA0TBTP6RHChWTnjoG1X6FnFpQzjH6 +L0WRO+QKzd0u58jl6aLPPlLa7uJBDVkoFiGQ+9iPiJTLf2FAxtO1UgXodqRr+F9m +3WxnDezbHn9PyH7b4ABdnCLv5LYSfx1HuYLr2pByTIaoqcO1tbrYL1F9tbI0Hpqb +ekNEV2v0uEiuEXrtItS+UHlMmG39mQegGrBw49TE0hVM2z+6Fzqdj5zWtk4Xot4S +TryPZ5N3KLmpzVYg8ebb4wT6y8Wjvsn9ByLh+V2mfGVCH4DGIgA64iCLgrbVpJlR +yxIEablzSYXFOzTiqt62zLdxDgNmWGXXWBxfkYbbt8mnLT08lWo= +=p7VL +-----END PGP SIGNATURE----- + +--=-k/tR+cykGEvElN27YF+k-- + + + +--===============1981900298181275554== +Content-Type: text/plain; charset="us-ascii" +MIME-Version: 1.0 +Content-Transfer-Encoding: 7bit +Content-Disposition: inline + +_______________________________________________ +ick-discuss mailing list +ick-discuss@ick.liw.fi +https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi + +--===============1981900298181275554==-- + + diff --git a/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/tmp/.this-dir-not-empty/.empty/empty-file b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/tmp/.this-dir-not-empty/.empty/empty-file new file mode 100644 index 0000000..e69de29 diff --git a/tickets/4bbc9995f89d40c59451b743be4a4811/ticket.yaml b/tickets/4bbc9995f89d40c59451b743be4a4811/ticket.yaml new file mode 100644 index 0000000..e882655 --- /dev/null +++ b/tickets/4bbc9995f89d40c59451b743be4a4811/ticket.yaml @@ -0,0 +1,6 @@ +status: +- open +ticket-id: +- 4bbc9995f89d40c59451b743be4a4811 +title: +- What's needed before ick is ready for others to use? -- cgit v1.2.1