bug#7035: Savannah Emacs page fixes

bug#7035: Savannah Emacs page fixes

[Glenn Morris]

Package: emacs
Severity: minor

Is someone with admin rights for the Emacs Savannah page able to fix
the following issues, or do I need to report them to Savannah?

http://savannah.gnu.org/projects/emacs/

"Source Code" link:

1) Remove "Use Git" and the following "Browse Sources Repository" link.
(dead repository)

2) Change "Use CVS" to something like "Use CVS (web pages only)".


http://savannah.gnu.org/mail/?group=emacs

1) Any reason not to add the help-emacs-windows and gnu-emacs-sources
lists?

2) The "to post a message" comment is inappropriate for the lists:
emacs-bug-tracker, emacs-diffs, and info-gnu-emacs.

bug#7035: Savannah Emacs page fixes

[Stefan Monnier]

> http://savannah.gnu.org/projects/emacs/
> "Source Code" link:
> 1) Remove "Use Git" and the following "Browse Sources Repository" link.
> (dead repository)

Could we find someone to maintain it up-to-date instead?

> 2) Change "Use CVS" to something like "Use CVS (web pages only)".

We could turn off CVS access, indeed, tho I'm not sure what are the
consequences in terms of the old CVS repository: would it still be
accessible via `cvs'?  Would it disappear completely?  Would we care?

> http://savannah.gnu.org/mail/?group=emacs

> 1) Any reason not to add the help-emacs-windows and gnu-emacs-sources
> lists?

This page is auto-generated.  So to add those lists, we'd have to
change them into standard lists managed by lists.gnu.org.  Since they're
also available as usenet groups, I'm not sure how easy such a switch
would be.

> 2) The "to post a message" comment is inappropriate for the lists:
> emacs-bug-tracker, emacs-diffs, and info-gnu-emacs.

Again, this is auto-generated, and I have no idea if a switch somewhere
in the mailing-list config controls this message and if so which one,


        Stefan

bug#7035: Savannah Emacs page fixes

[Andreas Schwab]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> http://savannah.gnu.org/projects/emacs/
>> "Source Code" link:
>> 1) Remove "Use Git" and the following "Browse Sources Repository" link.
>> (dead repository)
>
> Could we find someone to maintain it up-to-date instead?

Only Jim has write access to it.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

bug#7035: Savannah Emacs page fixes

[Stefan Monnier]

>>> http://savannah.gnu.org/projects/emacs/
>>> "Source Code" link:
>>> 1) Remove "Use Git" and the following "Browse Sources Repository" link.
>>> (dead repository)
>> Could we find someone to maintain it up-to-date instead?
> Only Jim has write access to it.

Sounds like a problem we need to fix, indeed.  Can someone take care
of that?


        Stefan

bug#7035: Savannah Emacs page fixes

[Glenn Morris]

Stefan Monnier wrote:

>> 1) Remove "Use Git" and the following "Browse Sources Repository" link.
>> (dead repository)
>
> Could we find someone to maintain it up-to-date instead?

Hooray, more git discussion. :(

>> 2) Change "Use CVS" to something like "Use CVS (web pages only)".
>
> We could turn off CVS access, 

I wasn't suggesting turning off CVS access, just stop the slightly
misleading advertisement of it in the "Source Code" menu. It's still
used for the Emacs web pages, so it is useful to have those
instructions there for that.

>> http://savannah.gnu.org/mail/?group=emacs
>
>> 1) Any reason not to add the help-emacs-windows and gnu-emacs-sources
>> lists?
>
> This page is auto-generated. So to add those lists, we'd have to
> change them into standard lists managed by lists.gnu.org.

But they are standard lists.gnu.org lists:

http://lists.gnu.org/mailman/listinfo/help-emacs-windows
http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources

AFAIK, there is no difference between these and eg bug-gnu-emacs.

>> 2) The "to post a message" comment is inappropriate for the lists:
>> emacs-bug-tracker, emacs-diffs, and info-gnu-emacs.
>
> Again, this is auto-generated,

Oh well, I thought it might be.

bug#7035: Savannah Emacs page fixes

[Stefan Monnier]

>>> 2) Change "Use CVS" to something like "Use CVS (web pages only)".
>> We could turn off CVS access, 
> I wasn't suggesting turning off CVS access, just stop the slightly
> misleading advertisement of it in the "Source Code" menu.  It's still
> used for the Emacs web pages, so it is useful to have those
> instructions there for that.

IIUC the message you don't like is auto-generated and controlled by
whether or not the CVS flag is set.  Note that this flag only controls
the non-web part, IIUC (the web part is always unconditionally enabled).

Actually... it seems that the CVS part is already de-activated, so it
seems the problem is on the savannah side where the auto-generated
message isn't quite right.

>>> http://savannah.gnu.org/mail/?group=emacs
>> 
>>> 1) Any reason not to add the help-emacs-windows and gnu-emacs-sources
>>> lists?
>> 
>> This page is auto-generated. So to add those lists, we'd have to
>> change them into standard lists managed by lists.gnu.org.

> But they are standard lists.gnu.org lists:

> http://lists.gnu.org/mailman/listinfo/help-emacs-windows
> http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources

> AFAIK, there is no difference between these and eg bug-gnu-emacs.

I guess savannah hasn't been made aware that these belong to the
`emacs' project.

>>> 2) The "to post a message" comment is inappropriate for the lists:
>>> emacs-bug-tracker, emacs-diffs, and info-gnu-emacs.
>> Again, this is auto-generated,
> Oh well, I thought it might be.

Actually, the problem is that mailing-list configuration has only
"public" and "private" settings which control how easily one can
subscribe, but it doesn't have any settings about who can send email to
that list.


        Stefan

bug#7035: Savannah Emacs page fixes

[Eli Zaretskii]

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Sat, 18 Sep 2010 10:14:31 +0200
> Cc: 7035@debbugs.gnu.org
> 
> >>> http://savannah.gnu.org/mail/?group=emacs
> >> 
> >>> 1) Any reason not to add the help-emacs-windows and gnu-emacs-sources
> >>> lists?
> >> 
> >> This page is auto-generated. So to add those lists, we'd have to
> >> change them into standard lists managed by lists.gnu.org.
> 
> > But they are standard lists.gnu.org lists:
> 
> > http://lists.gnu.org/mailman/listinfo/help-emacs-windows
> > http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
> 
> > AFAIK, there is no difference between these and eg bug-gnu-emacs.
> 
> I guess savannah hasn't been made aware that these belong to the
> `emacs' project.
> 
> >>> 2) The "to post a message" comment is inappropriate for the lists:
> >>> emacs-bug-tracker, emacs-diffs, and info-gnu-emacs.
> >> Again, this is auto-generated,
> > Oh well, I thought it might be.
> 
> Actually, the problem is that mailing-list configuration has only
> "public" and "private" settings which control how easily one can
> subscribe, but it doesn't have any settings about who can send email to
> that list.

So what's the conclusion regarding these lists?  Should I add them or
not?  If you want them added, just say so.

bug#7035: Savannah Emacs page fixes

[Stefan Monnier]

>> >>> http://savannah.gnu.org/mail/?group=emacs
>> >>> 1) Any reason not to add the help-emacs-windows and gnu-emacs-sources
>> >>> lists?
>> >> 
>> >> This page is auto-generated. So to add those lists, we'd have to
>> >> change them into standard lists managed by lists.gnu.org.
>> 
>> > But they are standard lists.gnu.org lists:
>> 
>> > http://lists.gnu.org/mailman/listinfo/help-emacs-windows
>> > http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
>> 
>> > AFAIK, there is no difference between these and eg bug-gnu-emacs.
>> 
>> I guess savannah hasn't been made aware that these belong to the
>> `emacs' project.
>> 
>> >>> 2) The "to post a message" comment is inappropriate for the lists:
>> >>> emacs-bug-tracker, emacs-diffs, and info-gnu-emacs.
>> >> Again, this is auto-generated,
>> > Oh well, I thought it might be.
>> 
>> Actually, the problem is that mailing-list configuration has only
>> "public" and "private" settings which control how easily one can
>> subscribe, but it doesn't have any settings about who can send email to
>> that list.

> So what's the conclusion regarding these lists?  Should I add them or
> not?  If you want them added, just say so.

I've filed a support request #107479 on savannah for those issues.
So if you can resolve them yourself, go ahead (and please mention what
you've fixed, in that support request).


        Stefan

bug#7035: Savannah Emacs page fixes

[Eli Zaretskii]

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: rgm@gnu.org, 7035@debbugs.gnu.org
> Date: Sat, 18 Sep 2010 16:55:21 +0200
> 
> > So what's the conclusion regarding these lists?  Should I add them or
> > not?  If you want them added, just say so.
> 
> I've filed a support request #107479 on savannah for those issues.
> So if you can resolve them yourself, go ahead (and please mention what
> you've fixed, in that support request).

It looks like they've changed the UI and it's no longer possible for
the project admins to add existing mailing lists to a project.  That
was definitely not so a couple of years ago, when I added emacs-bidi
to the project page.

Sorry.