pouët.net

I believe he is waiting for things to cool down so he can put the source code on github so contributors will work on it.

So after all this, who is going to? Please raise your hands, step forward and form an orderly line underneath this post

"And all, I really hope we can still savage this. " I think we already did? Just a joke ;)

Kusma: *sigh* it wasn't the only part I cared about. It was just the only part I wanted to comment on, since you asked a hypothetical question I felt needed an answer - especially since Gargaj had already answered it earlier in the thread. The fact that collaboration is not a binary thing was my point indeed - as in: Gargaj DID collaborate, he just didn't collaborate publicly.

I honestly don't know why we're even debating this.

gloom: Fair enough. I interpreted your critical tone as rejecting the argument, which IMO would only work in context of the other arguments. I tried to phrase that last paragraph a rhetorical "IF you don't want all the babies to survive" kind of question, but perhaps I went a bit overboard.

The entire situation is unfortunate. I hope that peace is made and development continues.

that is so meta my mind = blown

where are those open source zealots now that the source and gargaj are out?

this is love <3

http://www.youtube.com/watch?v=fnrCdsicThk

i love this thread and want in too!
lets open up not just the source, but the whole database also, so there's no one single person in charge and everyone can fork it! then there'll be pouets.v.4 and demopoos all over the place fighting, and evolution comes in and decides that the shittiest one is the fittest and we all win and hug in front of a sunset.

considering the pouet logo, i cant help but hear http://www.youtube.com/watch?v=QITTy35CV_A

@w23: Isn't that more or less how we ended up with pouet?

Guys,

I did not specifically kicked Gargaj out of the project, I changed the credentials to the live website and the live database, as I was seeing people get heat up on the forum and no idea of who had access to it.
Password is in clear text in the source code and this code has been shared, maybe with security in mind, I just can't be sure it had been.
I have nothing against Gargaj and I appreciate whoever donates his time for pouet, we just disagree on something here and that's not why I changed the credentials.
Anyway 1.0 has not been updated for months, so it wont change a lot, and at least everything is still up and running.

Now here are my evil plans:
- Put the 1.0 source code on github
- Fix bugs and annoyances
- Welcome pull requests (propositions) and merge the ones that make sense, if any
- Work on a REST API
- Gargaj and anybody else are as welcome as before

Nothing revolutionnary here, I don't see any breaking change happening soon, data included.

At the same time:
- Gargaj and his collaborators can take their time working on 2.0 the way he intended to do it, openly or not
- If any change happens to the data on 1.0, he'll be able to track the changes on github, again if it happens, it will surely be minor stuff
- Once he feels is code his ready, he can open a pull request on github
- We review/test his code together and merge it
- We all contribute to Gargaj's 2.0, with his opinion obviously weigthing more than anyone else's, as he built it
- When Gargaj or any other contributor wants to quit, nothing will change and other people will still work on the site

If Gargaj does not intend to give away his code, it can't happen, and we'll just stick to 1.0.

Yes it's top down management from hell.

++

analogue: it seems to me you commited a coup d'etat. .. . .. Granted it secures pouet's developement on the long term (even when you are gone again) but why could you not agree with Gargaj on a date in the future and started open sourcing Pouet when v2.0 is finished ?

Also in 2008 i asked you: How do you see the future of Pouet.net on the short and long term?

And you said:
It really depends on the scene. I don't really know where the scene is going, it was easier before. As soon as the sceners take a strong direction toward some new way of enjoying our machines, Pouet will follow it. But for now, I see no evolution in the scene, hence there is no need for a major Pouet revision.

So why is there need for a major Pouet revision (open source) now? :)

Because as soon as pouet switches to a closed 2.0 code base, it will be way more difficult to open it, if ever possible, as Gargaj will be the owner.

I call bullshit.

Why? For this simple reason: what on earth did you think would happen? The people who started discussing "heatedly" were among the same people who have had access to the DB and SSH for years. Because they were the people who _took care of the site_. So the only reasonable explanation for changing the credentials was to keep people out because you we're afraid you would lose your own access. Which -- makes no sense -- because as a Pouet admin you could have gotten those credentials replaced by a Scene.org admin.

Again: I call bullshit for the explanation you're giving.

he already released it. maybe you should concentrate on listening instead of shouting, for a change.

gloom: Like you said I can get the credentials back from a scene.org admin, I just don't want to take the risk to spend 2h rolling back backups.

T-101: he's too busy making up yet another strawman

Gargaj: Thanks a lot for the source-drop. What license is this under? I.e can I modify it and release the result? If so, can I grant such a license to third parties?

I'm pretty sure it's under the "I don't care anymore, do whatever you want" license. ;)

kusma: Honestly? Didn't think or care about that, it's nothing extraordinary i guess... why, would you use it?

Analogue: You really think that people will buy that your decision to close everyone but you out was because of Security, when it happened to take place right after you got pissed off at Gargaj? The timing of that move is just way too close to your outburst for that to have any merit.

I get that you come back and try to save it though.. I have the tendency to try to save my ass as well if I realize I made a bad move while angry..

Be that as it may, you're still not making a good case for people to want to work together with you on projects, you seem like a pretty loose cannon at the moment (although calmer today).. Also, if 20 people advice you to do one thing and 2 people advice you to do another thing, why go with the 2?

Crazy. I agree with dubmood and rasmus (although i think cleaning up the database is a simple step once the API is done. Its simply all about using the API itself to pull the data out and insert it into another database. it's also a very decent test of the api-functionality).

What is funny is that the people argueing against analogue is really using analogues original concerns against him. While they stubbornly trust a guy who has been working on a site for FIVE years without deploying it to the community.

And viewing its source we can clearly see this is not a code base that is maintainable for a longer period of time. Inlined html/code with raw sql queries everything being hardcoded just as it is today. Analogues point is just validated since all he wanted is opensourcing the current codebase and move on to a lean api where people can do just what rasmus suggested.

"shove it where the sun don't shine"-license