Re: [Savannah-hackers-public] Allowing git repos to automatically push to gnu.org/software/$PROJECT

> Date: Thu, 22 Jul 2021 16:25:08 -0600 > From: Karl Berry > Cc: savannah-hackers-public@gnu.org > > Also, I saw that there is a script to generate documentation for > each project. I think it runs on the Savannah side of things but > want to confirm. > > "Generate documentation"?

Re: [Savannah-hackers-public] Allowing git repos to automatically push to gnu.org/software/$PROJECT

> From: Daniel Katz > Date: Thu, 22 Jul 2021 17:24:18 -0400 > > For example, Emacs has its source repo, GNU ELPA, NonGNU ELPA, and Emacs > Org mode git repos on its project page. If the maintainers wanted it to > have a git repo for it's subpage instead of CVS, a maintainer should > create a

Re: [Savannah-hackers-public] Allowing git repos to automatically push to gnu.org/software/$PROJECT

Hi Daniel - sorry, but someone else from Savannah will need to work with you to move this forward. I just can't undertake the project. Project maintainers on savannah cannot create their own git repos. They have send email/submit a support request. (This is a constant thorn in everyone's

Re: [Savannah-hackers-public] Allowing git repos to automatically push to gnu.org/software/$PROJECT

Thank you for responding! Seeing the curl commands used makes the new.py script make a lot more sense now. I've been thinking about how the workflow for creating git repos for updating software subpages on gnu.org should be and how those repos can best be identified by wildebeest for syncing. If

Re: [Savannah-hackers-public] Allowing git repos to automatically push to gnu.org/software/$PROJECT

Yes. If someone wants to use CVS to update a project's webpage, they should not have to change their current workflow at all. Thanks for answering regardless; it's always great to get as much input as possible on these types of changes! On 7/21/21 7:28 AM, Eli Zaretskii wrote: >> Cc:

[Savannah-hackers-public] Volunteer to help with project evaluation

Hi there, Please find below a draft response to Task #16015 -- Dear user, Your project submission appears to be missing the GNU GPL license document. We require that you include a verbatim copy of the license in your project as plain text and to