Before you pay someone to do it, we need to define what "it" is.
"It" might generally look something like this:
1) Pull from the newest stable upstream code
2) Get it to compile
3) Run the regression tests
4) Make alpha and beta
builds, gather reports of bugs, fix bugs, re-run tests
5) Release
So for Pd-extended, one would pull from the newest stable Vanilla source.
To complete #2 and #4, one need build environments for all of Pd-extended's target platforms. Probably the easiest way to achieve that is to partner with two other developers-- for example, if
one uses Ubuntu, find an OSX person and a Windows person who can build Pd on their respective OSes. (There are guides on puredata.info about how to do this for each platform.)
Pd-extended doesn't have any tests AFAICT, so skip that step.
Kickstarter won't really help you here. It's possible that it would give some incentive for doing a single release, but how can it sustain that work for the next release, or the one after that?
-Jonathan
On Sunday, September 21, 2014 5:22 PM, me.grimm <megrimm@gmail.com> wrote:
>> it involves time
... or money.
maybe we revisit the kickstarter (or something else) idea brought forth by jonathon a few years ago and just pay someone to do it. to me it seems like 1) none of us really have any money (im just assuming here
we are all poor artists) and more importantly 2) none of us really have any time and those that do might not have the skills.
OR maybe we
have another PDCon (remember that?) to get amped up and pump something out....
m
On Sun, Sep 21, 2014 at 1:44 PM, Dan Wilcox
<danomatika@gmail.com> wrote:
I talked to Hans about this a bit. In essence, it involves bringing in the new pd vanilla source and making sure the Pd-extended additions/modifications aren't lost. With the updates/cleanups to the tcl/tk sources a few years ago (great work Hans et al!), it
should be alot easier than the previous extended releases. But still, *easy* or not, it involves
time.
Subject: Re: [PD] [Bulk] Re: [Bulk] Re: Updated pd-extended
Date: September 20, 2014 at 5:02:59 PM EDT
I wish I knew something about coding to help out with its development :P I do care a lot about it though and wish I could help in some other way.
I do see a few problems with extended, but they're basically related to some of the externals and libraries that sometimes do not work as they should, have bad and messy help files and are sometimes redundanct. If welcome, I could help sharing my thoughts and two cents about that, but I realize those are not actual bug fixes regarding the code, so it's not a priority on its to do list and issues for being updated to another release.
Anyway,
while were at it, what kind of work exactly do you mean someone would have to do? I suppose there is a great list of bug fixes just to keep it basically what it is. Given the context, I'm not assuming any big to do list for some new features agenda. But besidesthe bug fixes, how hard is it for someone to just update to the latest vanilla core?
Well, since Pd is an open source project that relies on community effort, and this is the list of its main developers and users, I guess this is the place to talk about a collaboration and see if we can get Pd-extended's development
to continue.
I'd to help in any way I can.
Cheers
--------
Dan Wilcox
@danomatika
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
--
____________________
m.e.grimm | m.f.a | ed.m.
megrimm@gmail.com_________________________________
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list