unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: guile-devel@gnu.org, guile-user@gnu.org
Subject: Collecting suggestions of Guildhall
Date: Sat, 12 Jan 2013 23:21:21 +0800	[thread overview]
Message-ID: <1358004081.23443.110.camel@Renee-desktop.suse> (raw)

Hi folks!
We'd like to start up guildhall.gnu.org, which is a guilers community
MAYBE based on savannah to let you guys share/fetch Guile packages. Just
like rubygems.org does. ;-)

Since savannah provides many VCS-systems: CVS/subversion/GNU
Arch/Mercurial/Bazaar, guilers may choose their favorite to maintain
their works, and submit the package to guildhall repository. 

IMO, a guildhall package must pass these two steps:
1. Package verify policy (PVP)
The rules to verify if package is valid/invalid.
And the package info specification. Include version-convention &
name-convention.
It can be checked automatically with a certain tools.

2. Package evaluate policy (PEP)
The rules to evaluate a submitted package, we need to classify them.
Current categories are:  quality/freedom/maintainability/experimental
This step has to be checked by human.

Though PEP & PVP seems alike, but they are different. If a package can't
pass PVP, it can't be classified according to PEP. PEP is used to
evaluate the quality of the package, but PVP is about the health of a
package. A valid package must be healthy, then it has the qualification
to be evaluated.

** Package security policy (PSP)
The rules to check if a package security/vulnerability, or even
malicious. 
This seems a hardcore one. I've no idea about it, but it's significant
though.

Now I'm inviting all folks to share your suggestions about the rules.
You may borrow some opinions from other communities anyway. 

But not limit to the rules, any related suggestions are welcome and
appreciated. ;-)

Thanks!





             reply	other threads:[~2013-01-12 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 15:21 Nala Ginrut [this message]
2013-01-22 11:30 ` Collecting suggestions of Guildhall Andy Wingo
2013-01-22 15:24   ` Nala Ginrut
2013-01-22 15:55     ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1358004081.23443.110.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.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).