[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers-public] requirements page

From: Assaf Gordon
Subject: Re: [Savannah-hackers-public] requirements page
Date: Wed, 8 Mar 2017 16:25:15 +0000
User-agent: Mutt/1.5.23 (2014-03-12)


Thank you for continuing this discussion.

On Tue, Mar 07, 2017 at 09:30:18PM -0800, Ivan Zaigralin wrote:
(3) Nothing currently listed in the two pages cited above can be interpreted
as a clear statement of the standing policy.

Shortly after you raised the issue, the two pages have been updated
to include such wording (briefly in 'requirements.php' and longer in 'HowToGetYourProjectApprovedQuickly').

Please visit them and make suggestions if needed.

(4) In line with the ideas stated above, I'd like to suggest adding the
following paragraph to the bottom of the page

<h3>Other Requirements</h3>

<p>Savannah is a non-commercial, volunteer-powered project with
extremely limited computational resources (such as disk
space). Reviewers can exercise judgment, and are not required to
accept every project submission that meets the objective technical
requirements listed on this page.</p>

Optionally, the previous paragraph can be extended to provide more specific
guidelines, if the Savannah team deems this to be helpful for the potential

<p>A judgment call can be made with respect to how generally useful the
program is, how simplistic it is, whether it is a one-time experiment,

We've added something a bit more concise. The 'requirements.php' page
needs to be short and succinct. The 'HowToGetYourProjectApprovedQuickly'
is where we can elaborate more freely.

But again, if you have suggestions for improvements, please do send them.

Optionally, some references can be given to further elucidate the policy.

The best way to start is to clone the wiki, make improvements and send a
patch to this mailing list. This will make it easier to discuss concrete
changes. To get started, please see the "One-off contributions" in .

- assaf

reply via email to

[Prev in Thread] Current Thread [Next in Thread]