public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Thomas Zander <zander@javalobby.org>
Cc: mauve-discuss@sources.redhat.com, tromey@redhat.com
Subject: Re: Some issues..
Date: Thu, 15 Apr 2004 22:14:00 -0000	[thread overview]
Message-ID: <1082067248.1986.45.camel@elsschot.wildebeest.org> (raw)
In-Reply-To: <200404031504.41093.zander@javalobby.org>

[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]

Hi,

On Sat, 2004-04-03 at 15:04, Thomas Zander wrote:
> Hmm;
> I spent a couple of days running with the snapshot which I downloaded from
> the webpage (http://sources.redhat.com/mauve/) until I found out is _very_
> far from recent (which the 'snapshot' seemed to imply)
> I must say its pretty bad that the snapshot is over a year old!!
> I suggest to remote the snapshot; or have up-to-date versions created
> nightly.

So sorry about that. I asked around and Tom will install a script on
sources to make sure we get fresh snapshots up again. (Thanks Tom!)

> I looked at the homepage and found a 'breaking news' that I found rather
> dubious; it looks like its been there for ages since the 'sidebar' does
> not work (on either konqueror or on mozilla), the 'logo design' leads to a
> dead link, the 'contribute'  page is empty..

We really need to update the website.
If someone wants to then they can get the website files with:
cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/mauve checkout htdocs

BTW see http://sources.redhat.com/cgi-bin/cvsweb.cgi/?cvsroot=mauve for
other modules like verify and "wonka" (the visual test engine).

> Please make the project seem 'less dead' to the passing eye!!  If Red-hat
> does not do anything; what about moving the project to sourceforge or
> savannah ??

It isn't really Red Hat not doing things. They are just hosting the
project. Like sourceforge or savnnah would do. We need people to
actually work on the pages (and complain loudly on the mailing list) to
make the project seem less dead. (And thanks again for yelling and
screaming, we have been a bit neglecting the appearance of the project.)

> if this is a mailinglist; please cc answers!

CCed. But please join the list!

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-04-15 22:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 13:05 Thomas Zander
2004-04-03 13:16 ` Andrew Haley
2004-04-03 13:41   ` Thomas Zander
2004-04-03 15:42     ` Andrew Haley
2004-04-03 16:06       ` Thomas Zander
2004-04-15 22:22       ` Mark Wielaard
2004-04-16  9:31         ` Andrew Haley
2004-04-16 11:29           ` Mark Wielaard
2004-04-16 12:01             ` Some issues.. (batch_run and runner script documentation) Mark Wielaard
2004-04-16 12:04             ` Some issues Andrew Haley
2004-04-22 21:41               ` Mark Wielaard
2004-04-15 22:14 ` Mark Wielaard [this message]
2004-05-07 11:54 ` John Leuner
2004-05-07 13:25   ` Thomas
2004-04-23  9:12 Jeroen Frijters
2004-04-25 11:10 ` Mark Wielaard
2004-04-29 11:41   ` Andrew Haley
2004-04-29 13:16     ` Thomas
2004-04-29 15:29       ` Andrew Haley
2004-05-01  9:49         ` Thomas Zander
2004-05-02 12:27           ` Andrew Haley

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=1082067248.1986.45.camel@elsschot.wildebeest.org \
    --to=mark@klomp.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=tromey@redhat.com \
    --cc=zander@javalobby.org \
    /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).