pspp-dev
[Top][All Lists]
Advanced

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

Re: new ideas for how to contribute to PSPP


From: Charles Stangor
Subject: Re: new ideas for how to contribute to PSPP
Date: Sun, 1 Aug 2010 18:20:53 -0400

As a new user of PSPP I was interested in contributing. I have a lot of experience in vb.net, but none in C++ or in the kind of joint project that PSPP involves. I couldn't really figure out how the code all fit together. For instance, if I wanted to write some GUI where would I begin? How exactly are the .q files turned into the .c files and then compiled on the fly? What is a .texi file? What is a .mk file? etc. etc. Probably a half hour on the phone with a developer would get me to where I need to be, but without that or some documentation that I couldn't find, I couldn't really make any progress -- well probably I could, but the time involved getting started seemed enormous.

Thanks


--------------------------------------------------
From: "Ben Pfaff" <address@hidden>
Sent: Sunday, August 01, 2010 2:39 PM
To: "John Darrington" <address@hidden>
Cc: <address@hidden>
Subject: Re: new ideas for how to contribute to PSPP

Good idea.  Added.

John Darrington <address@hidden> writes:

l10n would be worth mentioning here too.

On Sun, Aug 01, 2010 at 11:07:56AM -0700, Ben Pfaff wrote:
     Harry Thijssen has written up some new ideas on different ways
     that people could help out with PSPP development.  I've added
     these at the top of the existing "Contribute" page on the PSPP
     webpage:
             http://www.gnu.org/software/pspp/contribute.html

--
"Because computer source code is an expressive means for the exchange
of information and ideas about computer programming, we hold that it
is protected by the First Amendment."
--Hon. Boyce F. Martin, Jr., for the 6th Circuit Court, Junger vs. Daley

_______________________________________________
pspp-dev mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/pspp-dev




reply via email to

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