Hello,

May I introduce myself or better why I want have developer status on some subdirectories and some questions....

Since some years i was involved in some projects on the iem, where some tools have been written and some libraries programmed. Some project finished, some parts are use in other projects and develoipped further. We want some of the features stay alive and better accessible for the community. I made some patches to them and we put everything under LGPL and want to do some releases to stabilize. Also new developers helping are welcomed. Which should I contribute on sourceforge pure-data site,

XMLRPC Library: Makes pd a xmlrpc server

I think on written by thomas grill for the iaem project, which is very usefull in pd interconnection and I think better than netsend and -receive in cooperation with webservers or so.

Missing: xmlrpc client objects (to be added in next 2 month)

virtual concert hall - Complete Ambisonic Rendering lib with binaural patches

a toolkit to build virtual rooms inclusive room simulation (reverb, etc) to move sound sources in 3D-Space. missing key

iARS - PD as browser plugin and GEM functionality

The browser plugin for mozilla on windows, linux (missing mac support) (Any helpers are welcomed)

So the questions:

- is it possibble to be admin for some of the libfolder ?

- is LGPL ok for this stuff ?

- is it possible to make releases (being release manager) for some libs ?

- where to put them

I think the external should be under externals iem, except for iemlib thomas musil does and some hannes stuff for historical reasons.

For iARS or so... should we invent a projects folder on sourceforge ?

mfg winfried ritsch

...

alright.

since i am now cvs-admin, i'd like to add a new developer to the pure-data.sf project: mr "ritsch"

any objections ?

and should we discuss such decisions here ? i don't think that there can be much harm in adding new developers to the greater honour of this project.... (esp. if such person is well known to the community)

yes, we should discuss this here. I think it is not too much overhead and it keeps people informed about what is going on in the CVS.

Guenter

...

mfg.a.sdr IOhannes

---

PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev

---

PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev

This is great news! It'll be good to have all of the IEM stuff automatically included in the builds.

On Mar 8, 2005, at 11:33 AM, Frank Barknecht wrote:

Hallo, Winfried Ritsch hat gesagt: // Winfried Ritsch wrote:

...

So the questions:

• is it possibble to be admin for some of the libfolder ?

I don't think, being an admin only for some folders is possible, but I would very welcome you to be a "real admin". For the iem subsolder(s) we could just restrict write access a bit, if that is needed.

...

• is LGPL ok for this stuff ?

Yes, LGPL is among the Sourceforge-compatible licenses.

...

• is it possible to make releases (being release manager) for some

libs ?

Okay, this is part of a bigger question, namely how to do releases for the SF projects in the repository in general, as they have quite different release cycles. Anyway, making various file releases out of subdirectories technically is not a real problem.

I think the plan is to move towards autobuilding the whole thing every night, that's what I have been working towards. Then people can make other builds whenever they want.

.hc

________________________________________________________________________ ____

¡El pueblo unido jamás será vencido!

Hello,

I don't think, being an admin only for some folders is possible, but I would very welcome you to be a "real admin". For the iem subsolder(s) we could just restrict write access a bit, if that is needed.

ok I see, since hannes is mostly near he can do the few admin requests, we are also discussing here, so its not really needed if have write access to the iem part... (dont wanna mess up the system not reading sourcforge docs before ;-)))

Okay, this is part of a bigger question, namely how to do releases for the SF projects in the repository in general, as they have quite different release cycles. Anyway, making various file releases out of subdirectories technically is not a real problem.

Here the general question, maybe I missed sometime,

I want a file-release of a version (tag) off some library I was submitting. I want to upload some compiled archives, for this version. How should we handle this here ?

Should I discuss this here or just write some admin to do this ?

Or shouldnt we release external libs in extra packages ?

I think sourceforge says "release often, release early".

mfg winfried