From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Panicz Maciej Godek Newsgroups: gmane.lisp.guile.user Subject: Re: SLAYER announcement and help request for preparing a GNU package Date: Sun, 5 May 2013 08:59:18 +0200 Message-ID: References: <20130505051554.GA2558@intra> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8f3ba4577da41004dbf31f7a X-Trace: ger.gmane.org 1367737176 15720 80.91.229.3 (5 May 2013 06:59:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 5 May 2013 06:59:36 +0000 (UTC) Cc: "guile-user@gnu.org" To: John Darrington Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sun May 05 08:59:36 2013 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UYsuy-0002kd-Uu for guile-user@m.gmane.org; Sun, 05 May 2013 08:59:33 +0200 Original-Received: from localhost ([::1]:60371 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UYsuy-000713-Ls for guile-user@m.gmane.org; Sun, 05 May 2013 02:59:32 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:57493) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UYsun-00070s-NQ for guile-user@gnu.org; Sun, 05 May 2013 02:59:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UYsum-0004Jv-BH for guile-user@gnu.org; Sun, 05 May 2013 02:59:21 -0400 Original-Received: from mail-wg0-x230.google.com ([2a00:1450:400c:c00::230]:37003) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UYsul-0004Jn-H9 for guile-user@gnu.org; Sun, 05 May 2013 02:59:20 -0400 Original-Received: by mail-wg0-f48.google.com with SMTP id f11so2671695wgh.27 for ; Sat, 04 May 2013 23:59:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=KOIlofvsk0Lc4YJ2jUb99fHQFS3QZfcdQ2NkxyRzWuQ=; b=1FAhFQ55kx6Kbt46aO3wtdde9kFZMy8lWaNradW0Z/prJp3Lqb5pW0QOiOLcRziMTw gChjq0g4iK6mtWWuiAHv5wHQUBMj06cugx77GUkBLSBdimMLDr11L9gLprgSh14BMpFR SManQSE79Hrwb7Nre/2dtD37LQyqmb8k0wLaJfK+yQ5YnYBgOjMlirr+GahzTrLOtIZ+ Ei6XxUQQ/Eo/q8LeolmTUTM4GHU/bLePQTW3eBRj1Rg1xFfM9ilDYj3zUuuQYRYYYgv0 d+CJuKK1pwyQxrzOIBK7cRZcVywCIHiEOGgfUDTKBoz9SU0sy/G2Scye/ZZs0cQw1Rzp l65w== X-Received: by 10.180.108.176 with SMTP id hl16mr3969465wib.25.1367737158704; Sat, 04 May 2013 23:59:18 -0700 (PDT) Original-Received: by 10.194.51.197 with HTTP; Sat, 4 May 2013 23:59:18 -0700 (PDT) In-Reply-To: <20130505051554.GA2558@intra> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::230 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:10314 Archived-At: --e89a8f3ba4577da41004dbf31f7a Content-Type: text/plain; charset=ISO-8859-1 Hello! It sounds like an interesting project. > > The subject line of your post says it is a "GNU Package", but I don't see > slayer in > the official list. Perhaps you mean it is one that you want to submit to > GNU in the hope that they will adopt it as a package? Or did you mean > something > else? Obviously how to it should be laid out will depend on that a lot. > Well, I mostly meant a package that is compatibile with GNU system -- so that it would conform to the GNU standards. Whether is should be made an official GNU package is not that important to me, and I think it's still too early to decide > Like you say, lack of documentation is will be a big factor in getting > users. > How will people know how to use it, and perhaps more importantly WHY the > should > use it? > As for now, there are two demos which should help them get around, but I agree that in the longer run the documentation has to appear, especially as the system gets more complex, and as some parts of it become steady. If it comes to the second question, I think that the simplicity could convince some people to employ slayer to their multimedia projects -- because it requires no additional setup and works out of the box, so for instance it could be quite easily employed to implement the picture language from SICP Autotools can indeed be tricky - and a time consuming part of maintaining a > package - but they do make it a hell of a lot easier for the general public > to build, especially on wierd systems. > If it comes to weird systems, I also thought that having a build from mingw could also earn some popularity (if it is possible) Lack of features is a concern - but if you have a dedicated user base, even > a small > one, you will get requests for them. However, if you don't have decent > documentation, > and a reliable and portable build system, then you won't have any users > .... > I know. For now slayer is a byproduct of my other strivings, but I just thought that someone else could find it useful -- and the feedback could boost the development. Yet at this stage my main target is the community of hackers who could review the code and possibly find their own applications. I think that if someone sees the demos and wants to find out more, then it would make sense to run a documentation wiki or work on the info pages (or -- initially -- to answer the questions via e-mail). This is also why I need someone with more experience, to help me conceive the documentation process. I'm thinking of slayer as of environment rather than a program, and I think that it could evolve (among others) towards a development environment, so it would make sense if the documentation was available from there as well. Thanks! :) M. --e89a8f3ba4577da41004dbf31f7a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello!

It sounds like an int= eresting project.

The subject line of your post says it is a "GNU Package", but I d= on't see slayer in
the official list. =A0Perhaps you mean it is one that you want to submit to=
GNU in the hope that they will adopt it as a package? Or did you mean somet= hing
else? Obviously how to it should be laid out will depend on that a lot.
=

Well, I mostly meant a package that = is compatibile with GNU system -- so that it would conform to the GNU stand= ards. Whether is should be made an official GNU package is not that importa= nt to me, and I think it's still too early to decide
=A0
Like you say, lack of documentation is will be a big factor in getting user= s.
How will people know how to use it, and perhaps more importantly WHY the sh= ould
use it?

As for now, there are two= demos which should help them get around, but I agree that in the longer ru= n the documentation has to appear, especially as the system gets more compl= ex, and as some parts of it become steady.
If it comes to the second question, I think that the simplicity = could convince some people to employ slayer to their multimedia projects --= because it requires no additional setup and works out of the box, so for i= nstance it could be quite easily employed to implement the picture language= from SICP

Autotools can indeed be tricky - and a time consuming part of maintaining a=
package - but they do make it a hell of a lot easier for the general public=
to build, especially on wierd systems.

If it comes to weird systems, I also thought that having a build from= mingw could also earn some popularity (if it is possible)

Lack of features is a concern - but if you have a dedicated user base, even= a small
one, you will get requests for them. =A0However, if you don't have dece= nt documentation,
and a reliable and portable build system, then you won't have any users= ....

I know. For now slayer is a= byproduct of my other strivings, but I just thought that someone else coul= d find it useful -- and the feedback could boost the development. Yet at th= is stage my main target is the community of hackers who could review the co= de and possibly find their own applications. I think that if someone sees t= he demos and wants to find out more, then it would make sense to run a docu= mentation wiki or work on the info pages (or -- initially -- to answer the = questions via e-mail). This is also why I need someone with more experience= , to help me conceive the documentation process.

I'm thinking of slayer as of environmen= t rather than a program, and I think that it could evolve (among others) to= wards a development environment, so it would make sense if the documentatio= n was available from there as well.

Thanks! :)
M.

--e89a8f3ba4577da41004dbf31f7a--