mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl new-year's infrastructure resolutions
Date: Mon, 2 Jan 2017 13:23:19 -0500	[thread overview]
Message-ID: <20170102182319.GB1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LNX.2.20.13.1701022107220.2523@monopod.intra.ispras.ru>

On Mon, Jan 02, 2017 at 09:11:45PM +0300, Alexander Monakov wrote:
> On Mon, 2 Jan 2017, Rich Felker wrote:
> > > Have you considered github
> > 
> > Aside from that, using github for your issue tracker seems like a big
> > commitment/lock-in, if you want issue history to be something stable
> > and permanent, since I don't see any way to import/export the data.
> 
> I don't see why you say this; ways to work with issue data programmatically
> are documented at https://developer.github.com/v3/ (they use JSON).
> 
> For example, this query gives you JSON dump of musl-cross-make issues:
> 
> curl -i https://api.github.com/repos/richfelker/musl-cross-make/issues

Thanks, I wasn't aware of that. I think that makes it a lot more
plausible as a temporary solution for projects that want to move to
their own infrastructure at some point in the future, including
possibly for us, though I think we have other good leads now.

> Importing is also possible.

How do they (or rather do they) prevent you from falsifying posts by
other users in abusive ways?

Rich


  reply	other threads:[~2017-01-02 18:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 23:37 Rich Felker
2017-01-01 22:37 ` A. Wilcox
2017-01-02  2:31   ` Rich Felker
2017-01-02  2:33     ` Rich Felker
2017-01-02  5:32     ` A. Wilcox
2017-01-02  5:40       ` Rich Felker
2017-01-02  6:39 ` Khem Raj
2017-01-02 16:58   ` Rich Felker
2017-01-02 18:11     ` Alexander Monakov
2017-01-02 18:23       ` Rich Felker [this message]
2017-01-02 18:15     ` Solar Designer
2017-01-02 18:25       ` Rich Felker
2017-01-02 18:27   ` Kurt H Maier
2017-01-02 18:36     ` Rich Felker
2017-01-02 18:52       ` Kurt H Maier
2017-01-02 19:16         ` Rich Felker
2017-01-02 20:06           ` Kurt H Maier
2017-01-02 22:59             ` A. Wilcox
2017-01-02 23:09               ` Kurt H Maier
2017-01-02 19:10       ` Matias A. Fonzo
2017-01-02 19:18         ` Rich Felker
2017-01-02 19:28           ` Matias A. Fonzo
2017-01-03  1:20             ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170102182319.GB1555@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).