9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sean Hinchee <henesy.dev@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Software preservation in the post-hg era
Date: Mon, 30 Mar 2020 18:11:10 -0700	[thread overview]
Message-ID: <CADmmOS8HHVHLUED3MZne0zpHcjxaPSTtYMpXb8-X=FB_-aeQ8Q@mail.gmail.com> (raw)

In the wake of Bitbucket removing hg (Mercurial) support [1], I feel
it's topical to bring up software preservation for the plan9
community.

A lot of community contributed software has been put up on Bitbucket
or other hg hosts over time (RIP Google Code), but no consolidated
effort, to my knowledge, seems to have been made to index, let alone
mirror, this software.

For now, as a stop-gap, I've made a GitHub organization in which I've
consolidated most of what I had indexed from Bitbucket and a few other
places.

Thanks to people like Ori Bernstein, we have a native git client for
plan9 [3]; without a native client, this kind of transition wouldn't
be nearly as simple, thank you.

I'm more than happy to add anyone interested in the curation of this
archive to the GitHub organization. It would be nice to have spare
hands around to add README's, mkfiles, and attributions where they
have been missed or never existed.

In the long term, it would be nice to have a federated or otherwise
decentralized solution to pooling community contributed software,
especially keeping in mind ease of mirroring and picking up old
projects as contributors come and go.

The contrib/ directory on sources and 9front are fine and good, but
they are centralized. I don't have a proposed solution to this
problem, but it would be nice to have ideas or insight posted ☺.

I recognize that GitHub is also centralized and doesn't solve the
centralization problem, but at least git is really straightforward to
mirror with multiple remotes, etc. and having an index/archive is
valuable at least to me.

If anyone has further thoughts, anything they want added, or any lists
or indices of works they want archived/mirrored, I would love to see
these posted.

If anyone wants to mirror the archive, that would be wonderful. I was
considering mirroring everything to a remote in sr.ht in the future,
but haven't gotten around to it.

As a footnote, there's a decent git client written in Go that works
alright on plan9 [4], but it's slow and memory intensive at the
moment.

Cheers,
Sean

[1] https://twitter.com/traverser/status/1244398479591563265
[2] https://github.com/Plan9-Archive
[3] https://github.com/oridb/git9
[4] https://github.com/driusan/dgit

             reply	other threads:[~2020-03-31  1:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  1:11 Sean Hinchee [this message]
2020-03-31  1:52 ` Fazlul Shahriar
2020-03-31 14:45 ` ori
2020-03-31 16:59   ` Lucio De Re
2020-03-31 18:37   ` Dave MacFarlane
2020-03-31 19:08     ` Sigrid Solveig Haflínudóttir
2020-04-01 10:47     ` Charles Forsyth
2020-03-31 18:39 ` Xiao-Yong Jin
2020-04-01  1:00 ` Fazlul Shahriar
2020-05-07 14:15 ` Dave MacFarlane
2020-05-10  4:25   ` Lucio De Re
2020-05-10 16:27     ` hiro
2020-05-10  4:51   ` Jens Staal
2020-05-10 19:04     ` ori
2020-05-10 19:13     ` Dave MacFarlane
2020-05-10 18:37 ` Jim Manley

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='CADmmOS8HHVHLUED3MZne0zpHcjxaPSTtYMpXb8-X=FB_-aeQ8Q@mail.gmail.com' \
    --to=henesy.dev@gmail.com \
    --cc=9fans@9fans.net \
    /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.
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).