From: David Pirotte <david@altosw.be>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: proposal: move Kawa web-site to kawa-lang.org
Date: Tue, 15 Nov 2016 20:38:00 -0000 [thread overview]
Message-ID: <20161115183808.4af68ec3@capac> (raw)
In-Reply-To: <f349fddf-7aeb-0b9e-5d50-71c3140290d0@bothner.com>
[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]
Hello Per,
> ...
> What I'm concerned about is the user-visible URLs. I really don't like
> www.gnu.org/software/kawa - it's way too long.
Ok, but for me, it's perfect, because, to me, a lot more important then 'just'
existing, is that it's part of gnu. In my experience, nobody (almost ever) types a
url anyway, rather, we search and click. Searching for 'scheme' 'kawa' (using
duckduckgo.com) gives me, as the first entry,
Kawa: The Kawa Scheme language - gnu.org
It is an extension of the long-established Scheme language...
gnu.org/software/kawa/index.htm
[ for info, kawa-lang.org does not even appear in the first page (like 50
[ entries or so)
> Plain kawa.gnu.org would be a big improvement. However, kawa-lang.org has
> the benefit that it follows a familiar template: racket-lang.org,
> scala-lang.org, ruby-lang.org.
Ok, but really not important to me, the important thing is it is part of gnu
> When it comes to git, Savannah's support is pretty bare-bones. I don't
> see any support for pull requests, the web viewer appears to be just that (a
> viewer), and the issue tracker has zero integration.
that's exactly what I want, any precisely nothing more, hence cgit is the
best of the best, imo
Fine, different opinion again I guess: (a) I really [but like really] totally
dislike 'pull request' work flow, and cgit is the best interface ever, all others
are marketing crap, and (b) afaic, the best tracker is https://debbugs.gnu.org/
a bug mailing list and mailman commands .. these 2, I can handle absolutely
everything without to have to use a browser, and the least possible GUI I have to
use the best...
Finally, I will never ever (I'm not the only one) create an account on gitlab,
neither github of course, this is, to me, totally crazy, but the world is ...
Anyway, my 2c
David.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-11-15 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 2:11 Per Bothner
2016-11-13 11:54 ` Andrea Bernardini
2016-11-13 12:03 ` Andrea Bernardini
2016-11-13 15:15 ` Per Bothner
2016-11-14 0:47 ` Per Bothner
2016-11-14 21:44 ` Andrea Bernardini
2016-11-13 17:54 ` David Pirotte
2016-11-13 18:21 ` Per Bothner
2016-11-15 20:38 ` David Pirotte [this message]
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=20161115183808.4af68ec3@capac \
--to=david@altosw.be \
--cc=kawa@sourceware.org \
--cc=per@bothner.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).