Hi Guys -
Yes, it would seem that either a wiki or google docs could work...Ben,
the suggestion grew out the thread of giving vserver "hypervisor"
capabilities (implementing libvirt dev I think), and there were some
emails pertaining to what people would like to see (i.e.,
"requirements", "features").
Not sure how this would work, but possibly there'd be a moderator in
charge of "clarifying (nothing more than making sure suggestions were
pithy and clear)", and then people could vote on what mattered most...
Possibly leading to people chipping in to get things developed...?
E.g., we'd like to be able to manage vserver guests (create, delete,
monitor, move, change storage size, adjust RAM/CPU allocation...)
through something like ESXI or OpenStack (have some familiarity with the
former, none with the latter) and were thinking we could do so if
vserver had hypervisor capabilities....
On 11/09/13 15:09, Herbert Poetzl wrote:
> On Sat, Nov 09, 2013 at 11:29:52AM +0000, Ben Green wrote:
>
>> Quoting Ted Barnes<madogdevelopment@gmail.com>:
>>
>
>>> Does Vserver have a way from the community to put together a
>>> requirements list?
>>>
>
>> I'm not sure what you mean by this.
>>
> How about using a wiki page or maybe google spreadsheet?
>
> best,
> Herbert
>
>
>> Cheers,
>> Ben
>>
Received on Sat Nov 9 15:49:22 2013