Development progress

[schlumpf]

I can't say having the development be private is a bad thing at all, as it ensures the quality of the code itself

How does _no_ code review of third parties improve the quality? Noggit has gained a horrible code base by being handed wildly through a chain of non-public development.

[fearless_wind]

I see no reason to make it public now when it is under development.  But I see no reason not to do it after relase.

[schlumpf]

Maybe, checking for errors _before_ a release would be a reason? You seem not to be familiar with software development.

[fearless_wind]

Errors in code will lead to bugs in programm itself, so when we see no bugs during work of the application - there are no errors in code. 2-3 testers (who know what to test, not newbies in wow modmaking) is more than enough to check the most painful bugs. Also, opensource code before release can lead to different problems. For example, somebody downloaded the source, compiled and uploaded to any board with the link to Modcraft. So, the forum will be full of "pls help me noggit crashes every 5 mins". Also people will make bug-reports about errors that developers have already fixed long time ago. So, my opinion: we need to make Noggit open source, but only after the release of 1.3 or 1.4.

[schlumpf]

Errors in code will lead to bugs in programm itself, so when we see no bugs during work of the application - there are no errors in code.

AHAHAHAHAHAHAHAHAHAH.
No.

You can prove _presence_ of bugs, __not__ absence of bugs. Testing with a hundred people does not change shit. Bugs may still be present. Thus: More review, even static reading of code is more helpful.

For example, somebody downloaded the source, compiled and uploaded to any board with the link to Modcraft. So, the forum will be full of "pls help me noggit crashes every 5 mins".

There are hundreds of versions available on bitbucket. How often did you see that scenario happening? Correct, never.


I demand access to the repository or to have the commits be published to the already established repository.
In case of access, I will push them to the public one.

Just push it publically. There is _no_ harm. The only harm is development being private again, which I fought for for years.

And I hate my "baby" being dragged into a pile of shit with no insight, in private, after I spend actual weeks of real time with developing on it.

I will not accept that.

[tharo]

There is _no_ reason to be private.

Agree. Open source dont means "free for beeing fucked by everyone that want to contribute".

[Gamh]

Thinking of this and as we're debating on IRC, it's GPL. And, you know, the 4 freedoms etc.

I release some stuff under GPL and would HATE to know someone fork it privately. Before even speaking about the motivations behind making it private or public, just a reminder that you mustn't hide this source.

[fearless_wind]

@Schlumpf: Yes, there are really a lot of versions on bit bucket, but they are outdated and has less functions than newer ones. Existing testing version of Noggit can save water on adts (3.68 Beket), but (just example) can crash on MCLQ water. So, we get half-working tool that is unstable. Then imagine a guy who compiled testing version, than put it to other board (ac-web.org for example). This will cause some problems I previously said.
Actually, I agree with you about private development. Noggit must be opensource. So, I offer such a system: we have 2 repos - release and development. Development repo consists of all development version, commits, forks and so on and it has closed access only for dev guys or testers. Release repo consists of all released Noggit versions with source included. This way we can avoid a lot of problems and floods of desinformation on the board.

[schlumpf]

Your concerns never happened and most likely never will.

[fearless_wind]

Maybe, but don't you remember that some newbie asked a lot of questions about where is their 4 buttons they saw on videos and screenshots (Noggit3 odd buttons). The questions with buttons wasn't serious because we all know what is it, but when the questions will be about bugs that had already fixed, it will be bad. Anyway, I see no reason to make it opensource right now. Let's make a surprise for users with release.

[axel0099]

I understand what schlumpf meams.
There is no reason to make it privatr.
And as i know: schlumpf worked on noggit before, many ppl did.
And only a few do now which can be very frustrating for old developers.

[MR. Farrare]

cant wait guys hope the best for you

[fearless_wind]

Honestly, I thought for a long time that schlumpf don't want to make sources private before this thread was started.

[Steff]

Most all old developers work now again on it that are willing and still in the scene.
And again why its closed in the moment, we clean up. If this is done and there is a code base that is realy usefull to get open, it will.

And also again, there is a reason agains making something open souece. If you ask for help in the community for development my points are:

1. You have to give a good documentaions how to compile
2. A traker of jobs for the people.
3. You need to plan a roadmap to give people a hint what is most needed in the moment
4. You need to test the sended stuff (patches or forks) and give fast feedback. Nothing is more frustrating if you do some contributon to a codebase, send this in and noone repleys.

An I don´t see that there is someone in the moment with time for this.
Only releasing code on some open repository is not realy usefull to bring some benefit to a project. I don´t know how much frustrated post and direct privat messages I got in the last year form coders that even don´t get the QT version to compile.

If open source then the rigareht way.

[schlumpf]

Only releasing code on some open repository is not realy usefull to bring some benefit to a project.

It might not attract new contributors, but allows for code review and shows that there is some activity.

I don´t know how much frustrated post and direct privat messages I got in the last year form coders that even don´t get the QT version to compile.

You may want to have asked then. Also, given the correct external dependencies, it should compile fine.

If open source then the rigareht way.

Wieso glaubst du eigentlich, darüber entscheiden zu können? Wir hatten damals ganz klar ausgemacht, dass wir es öffentlich entwickeln. Wir haben einen twitter feed, der commits published, einen Bug tracker, ein forum, sogar irgendwo noch eine mailingliste. Um es öffentlich zu haben. Erinnerst du dich nicht an die Jahre in denen es privat war?
Wenn du der originale Author von Noggit wärest, würde ich dir diese Entscheidung zugestehen. So finde ich es eine Anmaßung und Frechheit gegenüber den anderen Entwicklern.

_Wir_ hatten uns entschlossen, es öffentlich zu machen. _Wir_. Unabhängig von der Codequalität.