Some proxmox VE developement considerations

[nextime]

Well, i found proxmox VE to be a good product, young maybe, with many improvements that can be done, but good as idea and vision, and look very promising.

Now, we notice in the forum than the next version of proxmox will have some exciting new features than i'm sure many of the pve users are waiting with impatience.

What i want to ask here is the following:

Considering than many good projects, even if businness driven like pve, get a good improvements and benefit by the collaborations and patches from the community, can't be considered by proxmox staff to open source the "developement" of PVE to the community?

A public SVN/CVS/Mercurial/GIT/something with latest code that anyone can download and use even if in developement stage, a bugtracker and the ability for developers to send patches for upstream with the benefit of the proxmox staff to revise, accept or decline, and maybe include those patch in upstream can be a good thing for both the community ( developers that can both try latest upstream developement version and help the developement cycle with patches and ideas ) and the proxmox staff ( more hands on the code with a centralized control can help to develop more things in less time ).

Can't be an option to be considered?

Sorry if someone has already asked same question in the past, i've not noticed it nor in forum or in everyelse place, i want to specify that isn't a complain to proxmox, but want just to open a collaborative and productive rapport between users, community and proxmox itself hoping that even those type of discussion are welcome by proxmox.

Also, sorry if this isn't exactly the right forum to say those things, but there isn't any other appropriape place i can find here.

 

[tom]

Well, i found proxmox VE to be a good product, young maybe, with many improvements that can be done, but good as idea and vision, and look very promising.

Now, we notice in the forum than the next version of proxmox will have some exciting new features than i'm sure many of the pve users are waiting with impatience.

What i want to ask here is the following:

Considering than many good projects, even if businness driven like pve, get a good improvements and benefit by the collaborations and patches from the community, can't be considered by proxmox staff to open source the "developement" of PVE to the community?

A public SVN/CVS/Mercurial/GIT/something with latest code that anyone can download and use even if in developement stage, a bugtracker and the ability for developers to send patches for upstream with the benefit of the proxmox staff to revise, accept or decline, and maybe include those patch in upstream can be a good thing for both the community ( developers that can both try latest upstream developement version and help the developement cycle with patches and ideas ) and the proxmox staff ( more hands on the code with a centralized control can help to develop more things in less time ).

Can't be an option to be considered?

Sorry if someone has already asked same question in the past, i've not noticed it nor in forum or in everyelse place, i want to specify that isn't a complain to proxmox, but want just to open a collaborative and productive rapport between users, community and proxmox itself hoping that even those type of discussion are welcome by proxmox.

Also, sorry if this isn't exactly the right forum to say those things, but there isn't any other appropriape place i can find here.

Thanks for your comments, here a short status:

Due to some major changes form 1.x to 2.x we decided NOT to open SVN and the bug tracker for public as this does not speed up the release cycle in the current situation. Due to the big success of the project we need to focus on the core dev to get the shortest time to release.

All source code of the current Proxmox VE version can be found here.

But already some externals dev´s get access, the systems are online but needs still registration - feel free to contact martin at proxmox.com, define what area you are interested in working and hopefully you can add something and you can also discuss how to get access to the not released code.

We already accept patches and feature requests posted in this forum. We plan to increase the community access as soon as the next major changes are released (later this year) - in the meantime we are committed to supporting all forum members in the best way and work to release as fast as possible - and if you take a look on the number of postings you will see our staff is doing a good job so far.

 

[nextime]

Thanks Tom, this is maybe the better answer i can hope for my questions, and i can understand and agree with your choice to concentrate on the core and other things before to open a public svn and so on.

Now i will try to get confident with the code (it isn't so complex nor so many lines considering what it do, but personally i'm not too perl oriented so i need to put my mind in the right direction to read it, usually i code in C or python... ) and maybe i will try to contribute in some way.

For the moment, thanks to all proxmox for your amazing piece of code!