pouët.net

Hi there every one!

I've some developed sourcecode (that didn't follow up to any production) that could be usefull for intro makers... and I want show it to community.

I dont have any personal web page (any ideias to a free page host?)
but also in this aspect I think in something more like sourceforge where diferent people can contribute to development and improve it or take it to his productions.

I expect that for example.. I could post in the pouet as a demotool .. but it links somehow to a colaborative opensource project that could be updated by someone not just me.... and not just the "zip file"

uhmm hints?

thanks,
KS

Google Code: http://code.google.com

So, follow up to the production and then release the sources to that and link to the them at pouet.

two very good suggestions so far :)

uhm but.. it doesnt have to be an "production"
I want release it as a framework...
Usually people zip it and post in pouet.

I think sourceforge could be a solution but its not very scene related, i.e. I dont think they have a section just for demoscene related code...

maybe the "solution" is to create a project in sourceforge then link it as production in pouet.. so people go to project page..

Or actually create something using your framework to give people some context. I don't think a bunch of source code is really appropriate for lniking to pouet.

do a demo with it first to prove its worth - that's how it's been in the scene for a while now. (ever wondered WHY crinkler / v2 / werkkzeug / etc. suddenly became interesting?)

None of those are source code...

sigh. not that it's relevant, but frontend / kkapture / gnu rocket then.

someone uses gnu rocket in demos?

andromeda, excess, keyboarders, ...?

(I'd LOOOVE to see that)

your source code will not be interesting before you have used it in a demo. so make that demo.

I think I was confused about the name, I was thinking about a code generator building library

Hey, I know.. I'm lazy!
(true mean for the excuse of say that I dont have time for.. )
Almost of us have no time (== are lazy) :P

I dont have any demogroup, but, .. why need to release a prove production? what about make for example an opensource demo/intro development? that is, instead of make first the prod. and then release the source... make first the source devopmente release then release productions with that...

(some non sense talk here! ... I ear some voices saying: less talk, make prods!)
:)

knos: Also Portal Process and a few other groups, Kusma probably has a better overview of who is using gnu rocket for their demos.

kammutierspule: If I'm correct in understanding that what you are suggesting is not releasing finished, compiled demos, but just release the source and datafiles, then I fail to see the point. There is a distinct possibility that this isn't what you're saying though.

Well it kind of is... Would Crinkler/V2/Werkkzeug be uninteresting if they were released before any demos utilized them? I think the best advice is googlecode+don't add it as a prod on pouet. Saying "do a demo with it or we're not interested" is not really constructive.

Sorry, my "it kind of is" was in relation to adding it to the pouet database.

I remember something about a sourceforge project for demoscene (like a collection of effect code)...

I think the point to make is: There is no demoscenish Sourceforge, because code sharing is not a big enough part of demoscene culture to need one. Arguably it *should* be, but that's a whole other debate. The demoscene websites that do exist are only interested in finished releases (which, in the case of a demotool, probably means that its usefulness needs to be proven with a prod). As a result, something like Sourceforge / Google Code / Github is your best bet right now.

Can't you create own categories or tags in SourceForge / Google Code / Github etc?

Github doesn't seem to have any categorisation at all, which is quite strange for a Web 2.0 poster child... (one valid criticism I've heard of Github is that even though it's great for collaborating on code, it doesn't do much to actually build a community.) Sourceforge just seems to have the category tree where you can suggest a topic to their admins. Never used Google Code.

I think the first step is to actually create an open source culture in the scene before worrying about how to organise it though :-)

Perhaps this is of interest / inspiration.

Point, allthough there is plenty of source/code examples to go around, they just need to be organized properly, as mentioned. This sounds like a perfect thing for Scene.org v2, if that plan ever gains enough traction to get moving properly.

bring in the preacher jokes!