You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by Rammohan Alampally <ra...@microsharp.net> on 2013/03/11 04:55:09 UTC

Unsubscribe mail request

Hello,

Please do let me know how do I unsubscribe from this group as I am NOT 
using this product.
I have sent a mail to the following mail account to unsubscribe my account.

openmeetings-user+unsubscribe@googlegroups.com

But, mail account is NOT exist and hence the mail was bounced.

Please do educate me. Thanking you!

Regards,
*Rammohan Alampally *
Co-Founder | Microsharp Technologies,
www.microsharp.net | rammohan@microsharp.net | +91 8105671238
World's cheapest Domain & Hosting packages - www.MicroSharp.co

*IMPORTANT: *The contents of this email and any attachments are 
confidential. They are intended for the named recipient(s) only. If you 
have received this email by mistake, please notify the sender 
immediately and DON'T disclose the contents to anyone or make copies 
thereof.
Please Print this Email Only if you really in need of a hard copy. Save 
Paper Save Trees & Be More Eco-Friendly...
On 11/03/2013 4:49 AM, seba.wagner@gmail.com wrote:
> Eldad/Jaime Are there JIRA tickets for the issues?
>
> Thanks,
> Sebastian
>
>
> 2013/3/11 Eldad Yamin <el...@gmail.com>
>
>> Unless you fix the video bug (cannot remove played videos from screen) I'd
>> say -1.
>>
>> On Sun, Mar 10, 2013 at 10:04 PM, Alexei Fedotov
>> <al...@gmail.com>wrote:
>>
>>> Hello Jaime,
>>>
>>> -1 votes should contain some justification
>>> 11.03.2013 0:02 пользователь "Jaime Balbino" <ja...@gmail.com>
>>> написал:
>>>
>>>> I review my vote: -1
>>>>
>>>>
>>>> 2013/3/10 seba.wagner@gmail.com <se...@gmail.com>
>>>>
>>>>> I appreciate all efforts going into that release but I think it needs
>>>> some
>>>>> more testing.
>>>>> Therefore my vote is currently negative.
>>>>>
>>>>> Mainly because recording on OSX did not work
>>>>> I will have to verify that on another box where windows is installed.
>>>>> Testing machine OSX 10.8.2, java 1.6.0_43
>>>>> Database: Default derby build in database
>>>>> Issues:
>>>>>   - Server needed 50% of the CPU as soon as I started to record in the
>>>>> screensharing client (the java process of the server took 50% the
>>>>> screensharing process took another 20-30 %).
>>>>> After starting the recording, hitting the stop button just resulted
>> in
>>>>> nothing.
>>>>>
>>>>> I am also a bit concerned about the Flash Players CPU usage. In
>>> previous
>>>>> versions I think the usage of the CPU was significant lower when you
>>> did
>>>> a
>>>>> share your cam+mic.
>>>>> But I first need to verify that using the old release to have some
>>>> concrete
>>>>> numbers.
>>>>>
>>>>> The Clustering feature is also not ready to be officially released.
>> The
>>>>> release notes say nothing about the missing components.
>>>>> For example: Whiteboard not stored in database, chat not stored in
>>>> database
>>>>> (which both has minor effects when not done however this would be
>>>> essential
>>>>> to know for anybody doing tests with it).
>>>>> The overall chat is not stored in the database and also not synced
>>>> between
>>>>> cluster nodes, so that the initial node of the cluster should be the
>>> same
>>>>> for anybody connecting to openmeetings (also this has only minor
>>> effects
>>>>> but nowhere documented).
>>>>> Server user/pass is nowhere in use but still to be in the database.
>>>>> After all there is only a single 3th party verification of the
>> cluster.
>>>>> The feature is of beta quality.
>>>>>
>>>>> Sebastian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2013/3/8 Maxim Solodovnik <so...@gmail.com>
>>>>>
>>>>>> That's a pity :(
>>>>>> I was sure all blocking issues are resolved. (There was mail thread
>>>> with
>>>>>> "release" bug list)
>>>>>>
>>>>>> @George can you create issues in JIRA?
>>>>>>
>>>>>> @Sebastian currently I'm modifying Release guide "on the fly" I'll
>>>> update
>>>>>> it with all my steps, so it will be up-to-date
>>>>>>
>>>>>>
>>>>>> On Fri, Mar 8, 2013 at 9:10 AM, George Kirkham <
>>> gkirkham@co2crc.com.au
>>>>>>> wrote:
>>>>>>> -1
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I personally believe we should delay the release of RC1 while we
>>>> attend
>>>>>> to
>>>>>>> minor design/GUI and bug issues.
>>>>>>>
>>>>>>> During this time that Apache OpenMeetings 2.1.0 RC1 is going
>>> through
>>>>>>> testing and bug fixes, development [of new features] could
>> continue
>>>>> with
>>>>>>> Apache OpenMeetings 2.2.
>>>>>>>
>>>>>>> My reasoning is that people I show OpenMeetings to are impressed
>>> with
>>>>> its
>>>>>>> capabilities but are really turned off by the obvious issues with
>>> the
>>>>>>> system, for example text that flows over or under other test or
>>>> fields
>>>>> in
>>>>>>> the windows/dialog boxes.
>>>>>>>
>>>>>>> Now that we are with Apache, I would really appreciate it if
>>>>> OpenMeetings
>>>>>>> did not have these little but annoying issues/bugs and that we
>> put
>>>>>> forward
>>>>>>> a much more professional and polished product. An easy to use,
>>>>>> consistent,
>>>>>>> and stable application.  New features can be added along the way
>>> with
>>>>>>> version 2.2, but we really should get to a position where what we
>>>> have
>>>>>> for
>>>>>>> 2.1.0 RC1 is well designed and maintained.
>>>>>>>
>>>>>>> When people complain about the look and feel (and they are
>> correct
>>> to
>>>>>>> complain), it really upsets me, and my users do complain, not
>>> loudly,
>>>>> but
>>>>>>> it is obvious that they do not appreciate these minor issues that
>>>>> detract
>>>>>>> from an otherwise great application, I would request that we
>> attend
>>>> to
>>>>>>> these issues before we release OpenMeetings version 2.1.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> George Kirkham
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
>>>>>>> Sent: Thursday, 7 March 2013 5:10 AM
>>>>>>> To: private@openmeetings.apache.org
>>>>>>> Subject: Fwd: [VOTE] Apache OpenMeetings 2.1.0 Release Candidate
>> 1
>>>>>>> ---------- Forwarded message ----------
>>>>>>> From: Maxim Solodovnik <so...@gmail.com>
>>>>>>> Date: Thu, Mar 7, 2013 at 1:09 AM
>>>>>>> Subject: [VOTE] Apache OpenMeetings 2.1.0 Release Candidate 1
>>>>>>> To: dev <de...@openmeetings.apache.org>
>>>>>>>
>>>>>>>
>>>>>>> Dear OpenMeetings Community,
>>>>>>>
>>>>>>> I would like to start a vote about releasing Apache OpenMeetings
>>>> 2.1.0
>>>>>> RC1
>>>>>>> Main changes are covered in the
>>>>>>> Readme:
>>>> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/README
>>>>>>> Full Changelog:
>>>>>>>
>> http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/CHANGELOG
>>>>>>> Release artefacts:
>>>>>>> https://dist.apache.org/repos/dist/dev/openmeetings/2.1/rc1/
>>>>>>>
>>>>>>> Tag:http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/
>>>>>>>
>>>>>>> PGP release keys (signed using C467526E):
>>>>>>> https://dist.apache.org/repos/dist/dev/openmeetings/2.1/rc1/KEYS
>>>>>>>
>>>>>>> Vote will be open for 72 hours.
>>>>>>>
>>>>>>> [ ] +1  approve
>>>>>>> [ ] +0  no opinion
>>>>>>> [ ] -1  disapprove (and reason why)
>>>>>>>
>>>>>>> My vote is +1.
>>>>>>>
>>>>>>>
>>>>>>> - --
>>>>>>> WBR
>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> - --
>>>>>>> WBR
>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> WBR
>>>>>> Maxim aka solomax
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sebastian Wagner
>>>>> https://twitter.com/#!/dead_lock
>>>>> http://www.webbase-design.de
>>>>> http://www.wagner-sebastian.com
>>>>> seba.wagner@gmail.com
>>>>>
>
>


Re: Unsubscribe mail request

Posted by Maxim Solodovnik <so...@gmail.com>.
http://openmeetings.apache.org/mail-lists.html


On Mon, Mar 11, 2013 at 10:55 AM, Rammohan Alampally <
rammohan@microsharp.net> wrote:

> Hello,
>
> Please do let me know how do I unsubscribe from this group as I am NOT
> using this product.
> I have sent a mail to the following mail account to unsubscribe my account.
>
> openmeetings-user+unsubscribe@**googlegroups.com<op...@googlegroups.com>
>
> But, mail account is NOT exist and hence the mail was bounced.
>
> Please do educate me. Thanking you!
>
> Regards,
> *Rammohan Alampally *
> Co-Founder | Microsharp Technologies,
> www.microsharp.net | rammohan@microsharp.net | +91 8105671238
> World's cheapest Domain & Hosting packages - www.MicroSharp.co
>
> *IMPORTANT: *The contents of this email and any attachments are
> confidential. They are intended for the named recipient(s) only. If you
> have received this email by mistake, please notify the sender immediately
> and DON'T disclose the contents to anyone or make copies thereof.
> Please Print this Email Only if you really in need of a hard copy. Save
> Paper Save Trees & Be More Eco-Friendly...
> On 11/03/2013 4:49 AM, seba.wagner@gmail.com wrote:
>
>> Eldad/Jaime Are there JIRA tickets for the issues?
>>
>> Thanks,
>> Sebastian
>>
>>
>> 2013/3/11 Eldad Yamin <el...@gmail.com>
>>
>>  Unless you fix the video bug (cannot remove played videos from screen)
>>> I'd
>>> say -1.
>>>
>>> On Sun, Mar 10, 2013 at 10:04 PM, Alexei Fedotov
>>> <al...@gmail.com>**wrote:
>>>
>>>  Hello Jaime,
>>>>
>>>> -1 votes should contain some justification
>>>> 11.03.2013 0:02 пользователь "Jaime Balbino" <ja...@gmail.com>
>>>> написал:
>>>>
>>>>  I review my vote: -1
>>>>>
>>>>>
>>>>> 2013/3/10 seba.wagner@gmail.com <se...@gmail.com>
>>>>>
>>>>>  I appreciate all efforts going into that release but I think it needs
>>>>>>
>>>>> some
>>>>>
>>>>>> more testing.
>>>>>> Therefore my vote is currently negative.
>>>>>>
>>>>>> Mainly because recording on OSX did not work
>>>>>> I will have to verify that on another box where windows is installed.
>>>>>> Testing machine OSX 10.8.2, java 1.6.0_43
>>>>>> Database: Default derby build in database
>>>>>> Issues:
>>>>>>   - Server needed 50% of the CPU as soon as I started to record in the
>>>>>> screensharing client (the java process of the server took 50% the
>>>>>> screensharing process took another 20-30 %).
>>>>>> After starting the recording, hitting the stop button just resulted
>>>>>>
>>>>> in
>>>
>>>> nothing.
>>>>>>
>>>>>> I am also a bit concerned about the Flash Players CPU usage. In
>>>>>>
>>>>> previous
>>>>
>>>>> versions I think the usage of the CPU was significant lower when you
>>>>>>
>>>>> did
>>>>
>>>>> a
>>>>>
>>>>>> share your cam+mic.
>>>>>> But I first need to verify that using the old release to have some
>>>>>>
>>>>> concrete
>>>>>
>>>>>> numbers.
>>>>>>
>>>>>> The Clustering feature is also not ready to be officially released.
>>>>>>
>>>>> The
>>>
>>>> release notes say nothing about the missing components.
>>>>>> For example: Whiteboard not stored in database, chat not stored in
>>>>>>
>>>>> database
>>>>>
>>>>>> (which both has minor effects when not done however this would be
>>>>>>
>>>>> essential
>>>>>
>>>>>> to know for anybody doing tests with it).
>>>>>> The overall chat is not stored in the database and also not synced
>>>>>>
>>>>> between
>>>>>
>>>>>> cluster nodes, so that the initial node of the cluster should be the
>>>>>>
>>>>> same
>>>>
>>>>> for anybody connecting to openmeetings (also this has only minor
>>>>>>
>>>>> effects
>>>>
>>>>> but nowhere documented).
>>>>>> Server user/pass is nowhere in use but still to be in the database.
>>>>>> After all there is only a single 3th party verification of the
>>>>>>
>>>>> cluster.
>>>
>>>> The feature is of beta quality.
>>>>>>
>>>>>> Sebastian
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2013/3/8 Maxim Solodovnik <so...@gmail.com>
>>>>>>
>>>>>>  That's a pity :(
>>>>>>> I was sure all blocking issues are resolved. (There was mail thread
>>>>>>>
>>>>>> with
>>>>>
>>>>>> "release" bug list)
>>>>>>>
>>>>>>> @George can you create issues in JIRA?
>>>>>>>
>>>>>>> @Sebastian currently I'm modifying Release guide "on the fly" I'll
>>>>>>>
>>>>>> update
>>>>>
>>>>>> it with all my steps, so it will be up-to-date
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Mar 8, 2013 at 9:10 AM, George Kirkham <
>>>>>>>
>>>>>> gkirkham@co2crc.com.au
>>>>
>>>>> wrote:
>>>>>>>> -1
>>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> I personally believe we should delay the release of RC1 while we
>>>>>>>>
>>>>>>> attend
>>>>>
>>>>>> to
>>>>>>>
>>>>>>>> minor design/GUI and bug issues.
>>>>>>>>
>>>>>>>> During this time that Apache OpenMeetings 2.1.0 RC1 is going
>>>>>>>>
>>>>>>> through
>>>>
>>>>> testing and bug fixes, development [of new features] could
>>>>>>>>
>>>>>>> continue
>>>
>>>> with
>>>>>>
>>>>>>> Apache OpenMeetings 2.2.
>>>>>>>>
>>>>>>>> My reasoning is that people I show OpenMeetings to are impressed
>>>>>>>>
>>>>>>> with
>>>>
>>>>> its
>>>>>>
>>>>>>> capabilities but are really turned off by the obvious issues with
>>>>>>>>
>>>>>>> the
>>>>
>>>>> system, for example text that flows over or under other test or
>>>>>>>>
>>>>>>> fields
>>>>>
>>>>>> in
>>>>>>
>>>>>>> the windows/dialog boxes.
>>>>>>>>
>>>>>>>> Now that we are with Apache, I would really appreciate it if
>>>>>>>>
>>>>>>> OpenMeetings
>>>>>>
>>>>>>> did not have these little but annoying issues/bugs and that we
>>>>>>>>
>>>>>>> put
>>>
>>>> forward
>>>>>>>
>>>>>>>> a much more professional and polished product. An easy to use,
>>>>>>>>
>>>>>>> consistent,
>>>>>>>
>>>>>>>> and stable application.  New features can be added along the way
>>>>>>>>
>>>>>>> with
>>>>
>>>>> version 2.2, but we really should get to a position where what we
>>>>>>>>
>>>>>>> have
>>>>>
>>>>>> for
>>>>>>>
>>>>>>>> 2.1.0 RC1 is well designed and maintained.
>>>>>>>>
>>>>>>>> When people complain about the look and feel (and they are
>>>>>>>>
>>>>>>> correct
>>>
>>>> to
>>>>
>>>>> complain), it really upsets me, and my users do complain, not
>>>>>>>>
>>>>>>> loudly,
>>>>
>>>>> but
>>>>>>
>>>>>>> it is obvious that they do not appreciate these minor issues that
>>>>>>>>
>>>>>>> detract
>>>>>>
>>>>>>> from an otherwise great application, I would request that we
>>>>>>>>
>>>>>>> attend
>>>
>>>> to
>>>>>
>>>>>> these issues before we release OpenMeetings version 2.1.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> George Kirkham
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Maxim Solodovnik [mailto:solomax666@gmail.com]
>>>>>>>> Sent: Thursday, 7 March 2013 5:10 AM
>>>>>>>> To: private@openmeetings.apache.**org<pr...@openmeetings.apache.org>
>>>>>>>> Subject: Fwd: [VOTE] Apache OpenMeetings 2.1.0 Release Candidate
>>>>>>>>
>>>>>>> 1
>>>
>>>> ---------- Forwarded message ----------
>>>>>>>> From: Maxim Solodovnik <so...@gmail.com>
>>>>>>>> Date: Thu, Mar 7, 2013 at 1:09 AM
>>>>>>>> Subject: [VOTE] Apache OpenMeetings 2.1.0 Release Candidate 1
>>>>>>>> To: dev <de...@openmeetings.apache.org>
>>>>>>>>
>>>>>>>>
>>>>>>>> Dear OpenMeetings Community,
>>>>>>>>
>>>>>>>> I would like to start a vote about releasing Apache OpenMeetings
>>>>>>>>
>>>>>>> 2.1.0
>>>>>
>>>>>> RC1
>>>>>>>
>>>>>>>> Main changes are covered in the
>>>>>>>> Readme:
>>>>>>>>
>>>>>>> http://svn.apache.org/repos/**asf/openmeetings/tags/2.1RC1/**README<http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/README>
>>>>>
>>>>>> Full Changelog:
>>>>>>>>
>>>>>>>>  http://svn.apache.org/repos/**asf/openmeetings/tags/2.1RC1/**
>>> CHANGELOG<http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/CHANGELOG>
>>>
>>>> Release artefacts:
>>>>>>>> https://dist.apache.org/repos/**dist/dev/openmeetings/2.1/rc1/<https://dist.apache.org/repos/dist/dev/openmeetings/2.1/rc1/>
>>>>>>>>
>>>>>>>> Tag:http://svn.apache.org/**repos/asf/openmeetings/tags/2.**1RC1/<http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/>
>>>>>>>>
>>>>>>>> PGP release keys (signed using C467526E):
>>>>>>>> https://dist.apache.org/repos/**dist/dev/openmeetings/2.1/rc1/**
>>>>>>>> KEYS<https://dist.apache.org/repos/dist/dev/openmeetings/2.1/rc1/KEYS>
>>>>>>>>
>>>>>>>> Vote will be open for 72 hours.
>>>>>>>>
>>>>>>>> [ ] +1  approve
>>>>>>>> [ ] +0  no opinion
>>>>>>>> [ ] -1  disapprove (and reason why)
>>>>>>>>
>>>>>>>> My vote is +1.
>>>>>>>>
>>>>>>>>
>>>>>>>> - --
>>>>>>>> WBR
>>>>>>>> Maxim aka solomax
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> - --
>>>>>>>> WBR
>>>>>>>> Maxim aka solomax
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> WBR
>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sebastian Wagner
>>>>>> https://twitter.com/#!/dead_**lock <https://twitter.com/#!/dead_lock>
>>>>>> http://www.webbase-design.de
>>>>>> http://www.wagner-sebastian.**com <http://www.wagner-sebastian.com>
>>>>>> seba.wagner@gmail.com
>>>>>>
>>>>>>
>>
>>
>


-- 
WBR
Maxim aka solomax