Re: Is PHP available to projects' web pages?
Hello, Ineiev. On Mon, Jul 31, 2023 at 08:52:10 +, Ineiev wrote: > On Sun, Jul 30, 2023 at 10:42:21AM +0000, Alan Mackenzie wrote: > > Yes, I can see my way to generating the .html files. PHP is used solely > > to include boilerplate files (like lists of links) into the main files. > Apache SSI commands like > must work [0]... I think I'm going to have a copy of each such include file physically in the main .html files. The cost of the disk space for such a small web site is trivial, and I've developed scripts (mainly in sed) to maintain them. > > I'm not looking forward to removing all but one of the duplicate > > copyright/license statements which will appear in these files because of > > this file inclusion. But I know how to do that. > ...however, copyright and license notices should be written > in the covered files directly; if they aren't, it's too easy > to end up with invalid notices [1]. My intention is to have exactly one C/L notice physically in each file. > [0] https://savannah.gnu.org/maintenance/HomePage/ > [1] https://www.gnu.org/licenses/gpl-howto.html#why-license-notices -- Alan Mackenzie (Nuremberg, Germany).
Re: Is PHP available to projects' web pages?
Hello, Svetlana. On Sun, Jul 30, 2023 at 06:50:54 +1000, Svetlana Tkachenko wrote: > I believe that php is unsupported at savannah. You may need to install > php on your own computer and generate static html output. Thanks! Yes, I can see my way to generating the .html files. PHP is used solely to include boilerplate files (like lists of links) into the main files. I'm not looking forward to removing all but one of the duplicate copyright/license statements which will appear in these files because of this file inclusion. But I know how to do that. > -- > Svetlana -- Alan Mackenzie (Nuremberg, Germany).
Is PHP available to projects' web pages?
Hello, Savannah. I think the title says it all. I'm currently working on transferring a project, CC Mode, from SourceForge to Savannah. The web pages on SF are PHP pages, mainly for PHP's include facility. Is there a working PHP server on Savannah, or do I have to rethink those PHP pages before moving the web page sources? Thanks! -- Alan Mackenzie (Nuremberg, Germany).
Re: Moving an existing project from SourceForge to Savannah.
Hello, Tim. On Fri, Jul 28, 2023 at 09:58:59 +, Tim Landscheidt wrote: > Alan Mackenzie wrote: > > […] > >> And from past experience there I know they don't make accessing the > >> files there easy. > > That doesn't sound very good. :-( I've asked their support for a copy > > of the mailing list in, say, mbox format. That was two days ago and I > > haven't had a reply from them, as yet. I do hope they reply, one way or > > the other. > > […] > https://sourceforge.net/p/forge/documentation/Mailing%20List%20Archives/ > suggests that the archives for cc-mode should be available > at https://lists.sourceforge.net/mbox/cc-mode for project > administrators authenticated by their username/password. > Does this not work? Thanks, I didn't know that. At the moment, I'm blocked from logging on to SourceForge, because I won't/can't assent to their new so-called "privacy statement". But SourceForge (more exactly, SlashDot) has been in touch, and they offered "we can export your raw .mbox mailing list archive ..." which I take to mean the entire cc-mode-help mailing list archive. That will be helpful. :-) > Tim -- Alan Mackenzie (Nuremberg, Germany).
Re: Moving an existing project from SourceForge to Savannah.
Hello, Bob!
On Wed, Jul 26, 2023 at 15:55:05 -0600, Bob Proulx wrote:
> Ineiev wrote:
> > Alan Mackenzie wrote:
> > > I would thus like to move the project from SourceForge to Savannah. May
> > > I take it this would be acceptable and welcomed?
> > Yes; it's nice to see software migrating to more user-respecting
> > forges,
> > https://www.gnu.org/software/repo-criteria-evaluation.html
> +1! It will be good to see you using Savannah. We are happy to help
> with the process.
Thanks!
> > > Looking at the Savannah site, there are a couple of things which confuse
> > > me. I couldn't find a definition of what is meant by "group". It seems
> > > to mean the name of a project (in my case, "CC Mode") and/or the Linux
> > > file-system group name under which project files will be stored
> > > ("cc-mode").
> > The "project" is a type of group; other group types hosted on Savannah
> > include GNU User Groups, www.gnu.org portions and www.gnu.org translation
> > teams.
> In deep detail there are project types defined in the SQL database and
> there are Unix groups defined in the database that are real Unix
> groups to the system for file access permissions. Therefore "group"
> in that case means both things. But you can think of it as the
> classic Unix group and that will be accurate. Files are stored on
> disk accessible by file group permission.
OK.
> > > I would also like to preserve the project's mailing list, if possible.
> +1! Preserving history is important.
I agree.
> > > I have a copy of posts going back to 2001 on my own machine, I don't
> > > know if it will be possible to extract a more complete copy from
> > > SourceForge. Do you see any problems, here? Currently, the main
> > > mailing address for this list is bug-cc-m...@gnu.org, and the gnu server
> > > forwards the mail to the SourceForge address. I foresee this address
> > > remaining the main address for the list, relocated back to Savannah.
> > I think you can use your old mailing list or migrate to lists.gnu.org.
> I presume without looking that the old mailing list was hosted on
> SourceForge.
Indeed, so. It is still there.
> And from past experience there I know they don't make accessing the
> files there easy.
That doesn't sound very good. :-( I've asked their support for a copy
of the mailing list in, say, mbox format. That was two days ago and I
haven't had a reply from them, as yet. I do hope they reply, one way or
the other.
> In which case it would be easier to use your archive of the mailing
> list. Off the top of my head I don't know the recipe to do the
> mailing list archive import but I generally know and would work it out
> when the time comes to do it.
Thanks!
> > > What about old releases? How much point is there, trying to preserve
> > > these? SourceForge still has releases going back around 20 years, to
> > > release 5.26. Current (three years old) is 5.35. They do not take up
> > > much space (around 700 kByte each). The older releases must be presumed
> > > lost.
> > You'll be able to upload them to Savannah download area.
> +1
OK. Things are progressing. Maybe we'll have the "new" project up and
running by this time next week.
> Bob
--
Alan Mackenzie (Nuremberg, Germany).
Moving an existing project from SourceForge to Savannah.
Hello, Savannah.
I maintain the project CC Mode, part of Emacs (and also XEmacs), which
is currently hosted at SourceForge.
SourceForge has recently introduced a so-called "privacy" statement, to
which I cannot assent. In consequence, they will not let me log onto
the web site. This has made my maintenance work, such as releasing a
release, difficult, if it is at all possible.
I would thus like to move the project from SourceForge to Savannah. May
I take it this would be acceptable and welcomed? I already have an
account, acmacm, on Savannah, and contribute fairly often to the Emacs
project.
Looking at the Savannah site, there are a couple of things which confuse
me. I couldn't find a definition of what is meant by "group". It seems
to mean the name of a project (in my case, "CC Mode") and/or the Linux
file-system group name under which project files will be stored
("cc-mode").
Also, there is on the page "register" an opportunity to give a *.tar.gz
URL or upload a file to Savannah. What is this tarball? Is it a
tarball of an existing repository, or just of the project's source
files?
I am assuming at the moment that I can quite easily upload the project's
(mercurial) repository onto Savannah.
I would also like to preserve the project's mailing list, if possible.
I have a copy of posts going back to 2001 on my own machine, I don't
know if it will be possible to extract a more complete copy from
SourceForge. Do you see any problems, here? Currently, the main
mailing address for this list is bug-cc-m...@gnu.org, and the gnu server
forwards the mail to the SourceForge address. I foresee this address
remaining the main address for the list, relocated back to Savannah.
What about old releases? How much point is there, trying to preserve
these? SourceForge still has releases going back around 20 years, to
release 5.26. Current (three years old) is 5.35. They do not take up
much space (around 700 kByte each). The older releases must be presumed
lost.
Any further tips you could give me about moving from SourceForge to
Savannah would be welcome.
Thanks for the anticipated help!
--
Alan Mackenzie (Nuremberg, Germany).
