User:Amc1/Azureus involvement
From AzureusWiki
Contents |
[edit]
About Azureus development
Just to save myself clarifying my position again and again...
I'm a volunteer developer - my first involvement with the Azureus project was in Jan 2006 to improve the XML/HTTP plugin. I became a proper contributor to the project in May 2006 - first piece of functionality I added was the move-on-removal behaviour. Since then, I've been adding various functionality and making bugfixes for the client.
I've also spent a lot of time opening up more and more of the Azureus code such that plugins have more access to it, and I've written numerous different plugins too.
[edit]
Vuze
[edit]
Regarding the whole Vuze thing...
- I still use the classic interface and focus my interface developments on that interface rather than the Vuze interfaces (though in some cases the Vuze interfaces can use the changes I make).
- I don't get paid by Vuze Inc in any way (nor am I looking for that).
- I am not always happy with all decisions that are made regarding Azureus - I have even quit from the project before over some issues. But I do stand up to try and make sure that users can, and will always be able to get The Azureus Experience they used to have from version 2, and largely, that's still in place.
[edit]
Why I defend Vuze...
- Because there is still a lot of belief that the move to Vuze means that the old azureus experience is no longer there, which isn't true. We made sure that the old interface is still there for the large number of users who are used to it and don't want to change (I'm one of them).
- Because the same people who spent years contributing and developing the Azureus program that people enjoyed using, now have an opportunity to continue work on it and make a living from it. And even if you don't want to use the Vuze side of things, you can still make use of some the improvements made in newer versions.
[edit]
Why I don't fork the project...
- It'd be a lot of work. ;)
- But that aside - it's because we've still got the old Azureus interface available. If that was taken out, or Vuze features were forced into the old interface without any way to prevent them, then I probably will end forking a project. But despite what you might think - the people in Vuze do know that there will be users who don't want (and may never want) to use the Vuze features, which is why we don't intend to remove it. Ever.
[edit]
Why I don't use the Vuze interface...
- I prefer the classic one, simple as that.
- I don't go around promoting the features in the Vuze UI - I actually spend more time in trying to convince people that they can have the old interface back (with very little effort required).
I also wrote this Wiki article about Vuze - including dealing with a lot of the arguments thrown at it.
