Quote from: Philogus on December 30, 2013, 06:34:16 AM

Quote from: arthurf on December 30, 2013, 06:12:36 AM

~~I also created a Ubuntu 64bits deb package: http://log.life.com.br/archive/ubuntu/coins/unobtanium/unobtanium-qt_latest_amd64.deb~~ ******DON'T DO THIS!!!!!!*******

I know that you are just trying to be proactive and help. Everything that you did is wonderful except for building the 64 bit Ubuntu package. We should not train people, especially new people, to download and install binary packages from unknown sources, especially when a crypto-currency wallet is concerned. Think about it this way: you are probably a trustworthy person, but imagine if a nefarious person took the UNO source code and put something malicious in it (let's say that it quietly sends the creator the private keys for the UNO wallet). He distributes it as a binary package, so people can't analyze the source code (In your case, I have no way of knowing for sure whether the package you are distributing comes from exactly the same source code as what you posted on Github). Do you see the dilemma? It is far better to let people analyze the source code for vulnerabilities, and then compile the program from known trusted sources. The most important step is a very public peer review where A LOT of people get to look at the source code.

In summary:

Don't fork someone else's project unless you made some significant improvements to it AND you are fully committed to do the massive amount if work that it will take to properly maintain the fork (e.g. if people report bugs, they will expect you to fix them).
When you share you improvements, just share a link to your improved source code, DON'T share a binary that you have compiled.
Give people ample time to study your source code, and to come up with noted problems, and recommended solutions.
Once you have acted upon the recommendations that you find valid, then share the final version of your code
When you are ready to share binaries, calculate a hash of the binaries and share that hash so that people can be sure that your binaries have not been changed.
Share you binaries with a small test group first. This is how you build community trust. The test group will compile the source code, hash the resulting binary, and compare the hash with the the hash then get from your version of the binary. If everything matched, and your program runs well, you will build trust.

Right now, you are asking people to download and install your binary when they have no idea who you are, what your intentions are, or what is actually in its source code. This is an EXTREMELY bad policy pattern to set for UNO.
[/list]

Ok, sorry, just to make it clear: I'm not clamming any special feature in the binary, this is from the official source, anyone who wants to take the risk can take it.

If I make any feature, I would post the code. I'm Pro-Open Source Software. I made AwesomeTTS(quite popular) and JSON-ADVPL and I love Richard Stallman's work.

On reddit I'm a mod of /r/postscarcity, /r/getdisciplined (68k followers) many other smaller subreddits and now /r/catcoins.

In the catcoin community I saw people making windows and mac binaries, so I ended up making for Ubuntu too.

I saw there was pending issues in the main project, so I thought about doing the fork. I didn't make any push today because I worked so much on many different things (mostly for catcoin subreddit, and today was my first time making a deb file for the catcoin wallet and unobtanium) and it's already 5:18 AM and I have a 14 hours flight tomorrow. :S

Sorry, I just wanted to help. Maybe I should had chatted on IRC before doing anything. But I'm learning from mistakes and I complete understand that you are also doing the best to protect and improve this community.

Thanks for taking the time to explain it carefully. I will read your post again and again after I rest and I will discuss with more people about projects, ideas, etc.