Bugzilla for OSS opened

[hannu]

I have opened a bug tracking system (Bugzilla) for OSS at http://bugzilla.opensound.com . In the beginning the Bugzilla system will be used in parallel with this user forum and the old tehc support request form
on our web site. However sometimes in the future Bugzilla will replace
the other methods.

The OSS developer community web page (http://developer.opensound.com/opensource_oss/) has been updated to contain some instructions for developers who like to do contributions to OSS. There is also a contributor agreement that contributors need to sign and send to 4Front Technologies.

I'm also working on a source repository (Mercurial) for OSS 4.1. However it will probably take few weeks before it's up and running. We will finally start accepting contributions after we get some experience with Mercurial.

[Saoshyant]

These are really great news. Thanks for finally getting things in motion, Hannu.

[majeru]

Hello,
It seems that both the bugzilla and the mercurial web interface aren't currently working. Do you have hosting problems?

[seawright]

Bugzilla seems ok but mercurial is a different matter. The server appears to be ok but there is a dns problem.
As a temporary solution add:
"82.118.207.57 mercurial.opensound.com"
to your /etc/hosts file.

[SeaJey]

Please, add links to bugzilla and wiki to the left frame of front page http://opensound.com

[seawright]

Perhaps the front page of: http://developer.opensound.com/ should also be updated:

We are currently evaluating various bug tracking systems and an one for OSS will be opened in the future.

Oh and spell checked as well, "tehcnical".

[majeru]

I created an opengrok indexer at http://grok.utcluj.ro , which contains OSS4's sources, and a few other projects that i'm interested about. It's quite useful if one wants to quickly browse the sources when searching for symbol declarations, just like with cscope, but a lot neater.
I hope this isn't against OSS' copyright, or else I'll remove it.

Best regards,
Cristi

[dev]

I created an opengrok indexer at http://grok.utcluj.ro , which contains OSS4's sources, and a few other projects that i'm interested about. It's quite useful if one wants to quickly browse the sources when searching for symbol declarations, just like with cscope, but a lot neater.
I hope this isn't against OSS' copyright, or else I'll remove it.

Best regards,
Cristi

Hi,


Thanks for doing this. There is no problem with the OSS copyright.



regards
Dev

[nuc]

What happened to the Bugtracker

[igorzwx]

What happened to the Bugtracker

The so-called "open bug tracker" seems to be a symbolic attribute of "open development paradigm" http://linuxhaters.blogspot.de/2008/08/ ... m-all.html
The "open development model" invariably fails to work wonders. That is why the number of Linux users is below 0.5%. This means that the number of Linux users is comparable with the number of the deaf.

The very fact that Linux desktop users constitute a marginal minority causes a security problem: they can be easily identified and tracked by Three Letter Agencies http://www.urbandictionary.com/define.p ... r+Agencies
See: Side-Channel Privacy Leakage https://www.grc.com/sn/sn-264.htm
CryptoSystem Backdoors https://www.grc.com/sn/sn-268.htm

There is, of course, a conspiracy theory that explains the failure of "open development ideology" http://www.linuxuser.co.uk/news/a-linux ... acy-theory
Such conspiracy theories are a common symptom of Cargo cults http://www.youtube.com/watch?v=qmlYe2KS0-Y

The alternative is a "closed development model". Example: Slackware Linux.

Slackware is a free and open source Linux-based operating system. It was one of the earliest operating systems to be built on top of the Linux kernel and is the oldest currently being maintained.[4] Slackware was created by Patrick Volkerding of Slackware Linux, Inc. in 1993.

Non-open development
Slackware follows a non-open development paradigm, in the sense that there is no formal bug tracking facility (like, for example, bugzilla) and no official procedure to become a code contributor or developer. As a consequence the project does not maintain a public code repository. Bug reports and contributions, while being essential to the project, are managed in an informal way. All the final decisions about what is going to be included in a Slackware release strictly remain with Slackware's Benevolent Dictator For Life, Patrick Volkerding.
http://en.wikipedia.org/wiki/Slackware