public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Jackson <iggy@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GLEP #15 - a gentoo script repository.
Date: Wed, 15 Oct 2003 11:59:36 -0500	[thread overview]
Message-ID: <200310151159.37217.iggy@gentoo.org> (raw)
In-Reply-To: <20031015155730.GY1650@mail.lieber.org>

On Wednesday 15 October 2003 10:57 am, Kurt Lieber wrote:
> I missed the original thread on this GLEP, so apologies for the delay in
> responding.
> 
> For those who missed the original discussion as well, please see this
> thread:
> 
> http://article.gmane.org/gmane.linux.gentoo.devel/12750
> 
> So, let me start by saying that I support the idea behind this GLEP, though
> I would like to see some modifications made and some questions answered
> before approving it.
> 
> Some comments in no particular order:
> 
> * I dislike the idea of making this a plain page.  For it to be effective,
>   I think it needs to have some searching and filtering capabilities
>   straight away.

Okay, I didn't know what type of infrastructure commitment we could expect so 
I was shooting for the most simple thing. Something that work on the existing 
webnodes.

> 
>   One thing I'm not willing to do is simply throw a page up there and let
>   people start contributing scripts.  This will *quickly* become
>   unmanageable and unusable.  If we're going to do this, we need to design
>   it correctly from the start.

Understandable, I'll get something worked up and put it on my site for 
perusal. As per discussion on irc, I'll stick with python/php and mysql

>   
> * Rather than including this in another project page, such as tools or
>   base, I'd rather see this as a standalone application, personally.  Say,
>   scripts.gentoo.org.  This is largely a personal preference and I'm open
>   to discussing it, however.  I just feel that this doesn't fit neatly into
>   the mandate of tools and/or base and it would see more use as a
>   standalone app similar to the (now dead, but soon to be reborn)
>   stats.gentoo.org.  Other projects could link to specific sections from
>   their pages as they wished.
> 
> * "A scripts@gentoo.org email alias would be setup and forwarded to the
>   team that will accept and publish these scripts to the website."
> 
>   Who is this team?  This needs to be in place and functioning before this
>   GLEP can be approved.

Well, so far I have about 4 people who are interested in working on this, and 
I'm sure more will raise their hands.

> 
> * In addition to being divided by task, this app also needs to be able to
>   filter by language (python, shell, perl, etc.)  See the first bullet
>   point.

okay, will do

> 
> * There need to be standards and guidelines on what is required to have a
>   script be included in the repository.  Chief among these standards must
>   be documentation about how the script works, what it does, any special
>   requirements, etc.

agreed, I was going to require a usage blurb and long description for 
everything, and show that just below each script

> 
> * I would really, really like to see some sort of interactive application
>   where users could make comments on various scripts.  For a perfect
>   example of what I'm referring to, see PHP's documentaion:
> 
>   http://www.php.net/manual/en/function.date.php
> 
>   Specifically, the user contributed notes at the bottom.  IMO, I think
>   this is the perfect interface for a scripts.gentoo.org type application.

that sounds like a good plan, I'll look and see if I can find the code for it, 
and see if there is anything I can steal, I mean borrow.

> 
> * Who all is going to build this?  The folks behind the scripts@gentoo.org
>   alias?  Someone else?  

I haven't found a web programmer yet, so I'll probably do the rough draft

> 
> So, basically, I think the idea is great and am willing to support it from
> an infrastructure perspective.  If there are people willing to devote the
> elbow grease necessary to put this together, then great.  

Excellent! I'll let you know when I've got something for you to look at.

--Iggy

> 
> --kurt
> 

-- 
Home -- http://www.brianandsara.net
Gentoo -- http://gentoo.brianandsara.net

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-10-15 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 15:57 [gentoo-dev] GLEP #15 - a gentoo script repository Kurt Lieber
2003-10-15 16:59 ` Brian Jackson [this message]
2003-10-15 17:48   ` Kevin Lacquement
2003-10-15 18:37 ` Lisa Seelye
  -- strict thread matches above, loose matches on Subject: below --
2003-10-04 21:24 [gentoo-dev] glep " James Harlow
2003-10-04 21:39 ` Rob Cakebread
2003-10-05 10:06 ` Sven Vermeulen

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

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

  git send-email \
    --in-reply-to=200310151159.37217.iggy@gentoo.org \
    --to=iggy@gentoo.org \
    --cc=gentoo-dev@gentoo.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