Re: Commit messages from GPL project on ASF list
https://groups.google.com/forum/?fromgroups#!forum/apache-openmeetings-extras Group mail address would be: apache-openmeetings-ext...@googlegroups.com ... yeah but you got it already :) Sebastian 2013/3/22 Maxim Solodovnik > great :) > can you create one? > And we will use it's email in all "extra projects" > > > On Fri, Mar 22, 2013 at 1:17 PM, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > > > just create a Google Group for example? > > Anybody interested in those emails can subscribe to it. > > > > Sebastian > > > > > > 2013/3/22 Maxim Solodovnik > > > > > Maybe anybody knows how to create group email alias for free? > > > something like: dev-om-apache-ext...@whatever.com? > > > > > > > > > On Fri, Mar 22, 2013 at 10:36 AM, Maxim Solodovnik < > solomax...@gmail.com > > > >wrote: > > > > > > > I have updated all apache-extras projects (replace dev@ with my > email > > or > > > > Sebastian's email) > > > > except for (no adminitration rights) > > > > > > https://code.google.com/a/apache-extras.org/p/openmeetings-atutor-plugin > > > > https://code.google.com/p/red5phone/ > > > > > > > > @Sebastian can you update these two? > > > > > > > > > > > > On Fri, Mar 22, 2013 at 4:13 AM, seba.wag...@gmail.com < > > > > seba.wag...@gmail.com> wrote: > > > > > > > >> The OpenMeetings PMC agrees on disabling those notifications. > > > >> Anybody interested in those emails can subscribe to it on its own. > > > >> > > > >> Sebastian > > > >> Am 22.03.2013 05:34 schrieb "Luciano Resende" >: > > > >> > > > >> > On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com > > > >> > wrote: > > > >> > > There is a flag in the mail notification to turn of diff's in > > those > > > >> > emails. > > > >> > > So theoretically those emails don't have to include not even > code > > > >> > fragments > > > >> > > of GPL licensed code. > > > >> > > So those emails could become what they initially should have > been: > > > >> Some > > > >> > > simple notification of activity. > > > >> > > > > > >> > > We are actually also not interested in what exactly has changed > or > > > >> > archiving > > > >> > > external activities. > > > >> > > If anybody is interested in those projects he can catch up with > > > those > > > >> > > involved there. > > > >> > > > > > >> > > All we are interested is a "heads up" there is something going > on > > as > > > >> we > > > >> > > provide integration APIs that 3th parties are using. > > > >> > > > > > >> > > There are also a number of more 3th party projects that send > those > > > >> pings. > > > >> > > Basically all projects hosted at apache-extras.org are > configured > > > to > > > >> > send a > > > >> > > ping to our list when there was a SVN commit. > > > >> > > > > > >> > > > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > > >> > > > > > >> > > It is argueable if an Apache developer list is the right place > to > > > have > > > >> > such > > > >> > > a "news aggregator" for activities around OpenMeetings. > > > >> > > There might be easy ways to resolve such a conflict. Possibly > for > > > >> > example a > > > >> > > Google Group Mailing list. "openmeetings-apache-extras" or > > something > > > >> like > > > >> > > that. It does in fact not make a difference, just another > mailing > > > >> list to > > > >> > > monitor :) > > > >> > > It is just a bit an imaginary line that we draw here from my > point > > > of > > > >> > view. > > > >> > > > > > >> > > Sebastian > > > >> > > > > > >> > > > > > >> > > 2013/3/21 Jim Jagielski > > > >> > >> > > > >> > >> IMO, it's inappropriate content for a dev@ list, which is > > > >> > >> a place to *discuss* development, not an "archive" for > > > >> > >> external development, legal issues notwithstanding. > > > >> > >> > > > >> > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru < > a...@shanecurcuru.org > > > > > > >> > wrote: > > > >> > >> > > > >> > >> > I would be uncomfortable as well. If project members want to > > > follow > > > >> > >> > external projects that's great, but duplicating all of an > > > external > > > >> > project's > > > >> > >> > messages onto the public dev@ list is... not a best > practice, > > to > > > >> say > > > >> > the > > > >> > >> > least. > > > >> > >> > > > > >> > >> > Personally, I'd have to presume (for the average user) that > > > >> everything > > > >> > >> > coming from that other GPL licensed project is GPL. Thus, > this > > > >> seems > > > >> > to > > > >> > >> > violate the principle of least surprise and the fact that GPL > > is > > > >> > Category X, > > > >> > >> > which means that end users should be able to use Apache > > projects > > > >> and > > > >> > >> > products without having to worry that GPL code is included - > > > either > > > >> > in the > > > >> > >> > download, or in other places on our websites or mailing > lists. > > > >> > >> > > > > >> > >> > - Shane > > > >> > >> > > > > >> > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > > > >> > >> >> It's c
Re: Commit messages from GPL project on ASF list
great :) can you create one? And we will use it's email in all "extra projects" On Fri, Mar 22, 2013 at 1:17 PM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > just create a Google Group for example? > Anybody interested in those emails can subscribe to it. > > Sebastian > > > 2013/3/22 Maxim Solodovnik > > > Maybe anybody knows how to create group email alias for free? > > something like: dev-om-apache-ext...@whatever.com? > > > > > > On Fri, Mar 22, 2013 at 10:36 AM, Maxim Solodovnik > >wrote: > > > > > I have updated all apache-extras projects (replace dev@ with my email > or > > > Sebastian's email) > > > except for (no adminitration rights) > > > > https://code.google.com/a/apache-extras.org/p/openmeetings-atutor-plugin > > > https://code.google.com/p/red5phone/ > > > > > > @Sebastian can you update these two? > > > > > > > > > On Fri, Mar 22, 2013 at 4:13 AM, seba.wag...@gmail.com < > > > seba.wag...@gmail.com> wrote: > > > > > >> The OpenMeetings PMC agrees on disabling those notifications. > > >> Anybody interested in those emails can subscribe to it on its own. > > >> > > >> Sebastian > > >> Am 22.03.2013 05:34 schrieb "Luciano Resende" : > > >> > > >> > On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com > > >> > wrote: > > >> > > There is a flag in the mail notification to turn of diff's in > those > > >> > emails. > > >> > > So theoretically those emails don't have to include not even code > > >> > fragments > > >> > > of GPL licensed code. > > >> > > So those emails could become what they initially should have been: > > >> Some > > >> > > simple notification of activity. > > >> > > > > >> > > We are actually also not interested in what exactly has changed or > > >> > archiving > > >> > > external activities. > > >> > > If anybody is interested in those projects he can catch up with > > those > > >> > > involved there. > > >> > > > > >> > > All we are interested is a "heads up" there is something going on > as > > >> we > > >> > > provide integration APIs that 3th parties are using. > > >> > > > > >> > > There are also a number of more 3th party projects that send those > > >> pings. > > >> > > Basically all projects hosted at apache-extras.org are configured > > to > > >> > send a > > >> > > ping to our list when there was a SVN commit. > > >> > > > > >> > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > >> > > > > >> > > It is argueable if an Apache developer list is the right place to > > have > > >> > such > > >> > > a "news aggregator" for activities around OpenMeetings. > > >> > > There might be easy ways to resolve such a conflict. Possibly for > > >> > example a > > >> > > Google Group Mailing list. "openmeetings-apache-extras" or > something > > >> like > > >> > > that. It does in fact not make a difference, just another mailing > > >> list to > > >> > > monitor :) > > >> > > It is just a bit an imaginary line that we draw here from my point > > of > > >> > view. > > >> > > > > >> > > Sebastian > > >> > > > > >> > > > > >> > > 2013/3/21 Jim Jagielski > > >> > >> > > >> > >> IMO, it's inappropriate content for a dev@ list, which is > > >> > >> a place to *discuss* development, not an "archive" for > > >> > >> external development, legal issues notwithstanding. > > >> > >> > > >> > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > > > >> > wrote: > > >> > >> > > >> > >> > I would be uncomfortable as well. If project members want to > > follow > > >> > >> > external projects that's great, but duplicating all of an > > external > > >> > project's > > >> > >> > messages onto the public dev@ list is... not a best practice, > to > > >> say > > >> > the > > >> > >> > least. > > >> > >> > > > >> > >> > Personally, I'd have to presume (for the average user) that > > >> everything > > >> > >> > coming from that other GPL licensed project is GPL. Thus, this > > >> seems > > >> > to > > >> > >> > violate the principle of least surprise and the fact that GPL > is > > >> > Category X, > > >> > >> > which means that end users should be able to use Apache > projects > > >> and > > >> > >> > products without having to worry that GPL code is included - > > either > > >> > in the > > >> > >> > download, or in other places on our websites or mailing lists. > > >> > >> > > > >> > >> > - Shane > > >> > >> > > > >> > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > > >> > >> >> It's come to my attention that the openmeetings project has > > >> recently > > >> > >> >> subscribed their dev list to the commit messages of a Google > > Code > > >> > >> >> hosted > > >> > >> >> project under the GPL. I asked why and was told " those > updates > > >> are > > >> > >> >> interesting for our integration API." There is some overlap in > > >> > >> >> committers but the project communities do seem to be distinct > > >> other > > >> > >> >> than > > >> > >> >> this cross-posting of commits. > > >> > >> >> > > >> > >> >> I'm quite uncomfortable about this as it means that G
Re: Commit messages from GPL project on ASF list
just create a Google Group for example? Anybody interested in those emails can subscribe to it. Sebastian 2013/3/22 Maxim Solodovnik > Maybe anybody knows how to create group email alias for free? > something like: dev-om-apache-ext...@whatever.com? > > > On Fri, Mar 22, 2013 at 10:36 AM, Maxim Solodovnik >wrote: > > > I have updated all apache-extras projects (replace dev@ with my email or > > Sebastian's email) > > except for (no adminitration rights) > > https://code.google.com/a/apache-extras.org/p/openmeetings-atutor-plugin > > https://code.google.com/p/red5phone/ > > > > @Sebastian can you update these two? > > > > > > On Fri, Mar 22, 2013 at 4:13 AM, seba.wag...@gmail.com < > > seba.wag...@gmail.com> wrote: > > > >> The OpenMeetings PMC agrees on disabling those notifications. > >> Anybody interested in those emails can subscribe to it on its own. > >> > >> Sebastian > >> Am 22.03.2013 05:34 schrieb "Luciano Resende" : > >> > >> > On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com > >> > wrote: > >> > > There is a flag in the mail notification to turn of diff's in those > >> > emails. > >> > > So theoretically those emails don't have to include not even code > >> > fragments > >> > > of GPL licensed code. > >> > > So those emails could become what they initially should have been: > >> Some > >> > > simple notification of activity. > >> > > > >> > > We are actually also not interested in what exactly has changed or > >> > archiving > >> > > external activities. > >> > > If anybody is interested in those projects he can catch up with > those > >> > > involved there. > >> > > > >> > > All we are interested is a "heads up" there is something going on as > >> we > >> > > provide integration APIs that 3th parties are using. > >> > > > >> > > There are also a number of more 3th party projects that send those > >> pings. > >> > > Basically all projects hosted at apache-extras.org are configured > to > >> > send a > >> > > ping to our list when there was a SVN commit. > >> > > > >> > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > >> > > > >> > > It is argueable if an Apache developer list is the right place to > have > >> > such > >> > > a "news aggregator" for activities around OpenMeetings. > >> > > There might be easy ways to resolve such a conflict. Possibly for > >> > example a > >> > > Google Group Mailing list. "openmeetings-apache-extras" or something > >> like > >> > > that. It does in fact not make a difference, just another mailing > >> list to > >> > > monitor :) > >> > > It is just a bit an imaginary line that we draw here from my point > of > >> > view. > >> > > > >> > > Sebastian > >> > > > >> > > > >> > > 2013/3/21 Jim Jagielski > >> > >> > >> > >> IMO, it's inappropriate content for a dev@ list, which is > >> > >> a place to *discuss* development, not an "archive" for > >> > >> external development, legal issues notwithstanding. > >> > >> > >> > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > >> > wrote: > >> > >> > >> > >> > I would be uncomfortable as well. If project members want to > follow > >> > >> > external projects that's great, but duplicating all of an > external > >> > project's > >> > >> > messages onto the public dev@ list is... not a best practice, to > >> say > >> > the > >> > >> > least. > >> > >> > > >> > >> > Personally, I'd have to presume (for the average user) that > >> everything > >> > >> > coming from that other GPL licensed project is GPL. Thus, this > >> seems > >> > to > >> > >> > violate the principle of least surprise and the fact that GPL is > >> > Category X, > >> > >> > which means that end users should be able to use Apache projects > >> and > >> > >> > products without having to worry that GPL code is included - > either > >> > in the > >> > >> > download, or in other places on our websites or mailing lists. > >> > >> > > >> > >> > - Shane > >> > >> > > >> > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > >> > >> >> It's come to my attention that the openmeetings project has > >> recently > >> > >> >> subscribed their dev list to the commit messages of a Google > Code > >> > >> >> hosted > >> > >> >> project under the GPL. I asked why and was told " those updates > >> are > >> > >> >> interesting for our integration API." There is some overlap in > >> > >> >> committers but the project communities do seem to be distinct > >> other > >> > >> >> than > >> > >> >> this cross-posting of commits. > >> > >> >> > >> > >> >> I'm quite uncomfortable about this as it means that GPL code is > >> > passing > >> > >> >> through our lists (and being archived) without any clear > >> indication > >> > of > >> > >> >> its legal status. What I'm not sure about is whether my > >> discomfort is > >> > >> >> because of an irrational fear of someone inadvertently using GPL > >> code > >> > >> >> without knowing it or whether that is, in fact, a rational fear. > >> > >> >> > >> > >> >> Advice please? > >> > >> >> > >> > >> >> Ross > >>
Re: upcoming RC3
this should be awesome! looking forward to test RC3. Harsha Siriwardena [harshadura.net] On Fri, Mar 22, 2013 at 9:15 AM, Maxim Solodovnik wrote: > Hello All, > > I'm going to pack RC3 tonight, please let me know if anybody have any > concern regarding this > > -- > WBR > Maxim aka solomax >
upcoming RC3
Hello All, I'm going to pack RC3 tonight, please let me know if anybody have any concern regarding this -- WBR Maxim aka solomax
Re: Commit messages from GPL project on ASF list
Maybe anybody knows how to create group email alias for free? something like: dev-om-apache-ext...@whatever.com? On Fri, Mar 22, 2013 at 10:36 AM, Maxim Solodovnik wrote: > I have updated all apache-extras projects (replace dev@ with my email or > Sebastian's email) > except for (no adminitration rights) > https://code.google.com/a/apache-extras.org/p/openmeetings-atutor-plugin > https://code.google.com/p/red5phone/ > > @Sebastian can you update these two? > > > On Fri, Mar 22, 2013 at 4:13 AM, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > >> The OpenMeetings PMC agrees on disabling those notifications. >> Anybody interested in those emails can subscribe to it on its own. >> >> Sebastian >> Am 22.03.2013 05:34 schrieb "Luciano Resende" : >> >> > On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com >> > wrote: >> > > There is a flag in the mail notification to turn of diff's in those >> > emails. >> > > So theoretically those emails don't have to include not even code >> > fragments >> > > of GPL licensed code. >> > > So those emails could become what they initially should have been: >> Some >> > > simple notification of activity. >> > > >> > > We are actually also not interested in what exactly has changed or >> > archiving >> > > external activities. >> > > If anybody is interested in those projects he can catch up with those >> > > involved there. >> > > >> > > All we are interested is a "heads up" there is something going on as >> we >> > > provide integration APIs that 3th parties are using. >> > > >> > > There are also a number of more 3th party projects that send those >> pings. >> > > Basically all projects hosted at apache-extras.org are configured to >> > send a >> > > ping to our list when there was a SVN commit. >> > > >> http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings >> > > >> > > It is argueable if an Apache developer list is the right place to have >> > such >> > > a "news aggregator" for activities around OpenMeetings. >> > > There might be easy ways to resolve such a conflict. Possibly for >> > example a >> > > Google Group Mailing list. "openmeetings-apache-extras" or something >> like >> > > that. It does in fact not make a difference, just another mailing >> list to >> > > monitor :) >> > > It is just a bit an imaginary line that we draw here from my point of >> > view. >> > > >> > > Sebastian >> > > >> > > >> > > 2013/3/21 Jim Jagielski >> > >> >> > >> IMO, it's inappropriate content for a dev@ list, which is >> > >> a place to *discuss* development, not an "archive" for >> > >> external development, legal issues notwithstanding. >> > >> >> > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru >> > wrote: >> > >> >> > >> > I would be uncomfortable as well. If project members want to follow >> > >> > external projects that's great, but duplicating all of an external >> > project's >> > >> > messages onto the public dev@ list is... not a best practice, to >> say >> > the >> > >> > least. >> > >> > >> > >> > Personally, I'd have to presume (for the average user) that >> everything >> > >> > coming from that other GPL licensed project is GPL. Thus, this >> seems >> > to >> > >> > violate the principle of least surprise and the fact that GPL is >> > Category X, >> > >> > which means that end users should be able to use Apache projects >> and >> > >> > products without having to worry that GPL code is included - either >> > in the >> > >> > download, or in other places on our websites or mailing lists. >> > >> > >> > >> > - Shane >> > >> > >> > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: >> > >> >> It's come to my attention that the openmeetings project has >> recently >> > >> >> subscribed their dev list to the commit messages of a Google Code >> > >> >> hosted >> > >> >> project under the GPL. I asked why and was told " those updates >> are >> > >> >> interesting for our integration API." There is some overlap in >> > >> >> committers but the project communities do seem to be distinct >> other >> > >> >> than >> > >> >> this cross-posting of commits. >> > >> >> >> > >> >> I'm quite uncomfortable about this as it means that GPL code is >> > passing >> > >> >> through our lists (and being archived) without any clear >> indication >> > of >> > >> >> its legal status. What I'm not sure about is whether my >> discomfort is >> > >> >> because of an irrational fear of someone inadvertently using GPL >> code >> > >> >> without knowing it or whether that is, in fact, a rational fear. >> > >> >> >> > >> >> Advice please? >> > >> >> >> > >> >> Ross >> > >> >> >> > >> >> >> > >> >> -- >> > >> >> Ross Gardler (@rgardler) >> > >> >> Programme Leader (Open Development) >> > >> >> OpenDirective http://opendirective.com >> > >> >> >> > >> > >> > >> > We have had a similar discussion in the ComDev related to Apache >> > Extras [1], and the consensus at that time was that external projects, >> > particular the ones that are not compatible with AL2, should be >> >
Re: Commit messages from GPL project on ASF list
I have updated all apache-extras projects (replace dev@ with my email or Sebastian's email) except for (no adminitration rights) https://code.google.com/a/apache-extras.org/p/openmeetings-atutor-plugin https://code.google.com/p/red5phone/ @Sebastian can you update these two? On Fri, Mar 22, 2013 at 4:13 AM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > The OpenMeetings PMC agrees on disabling those notifications. > Anybody interested in those emails can subscribe to it on its own. > > Sebastian > Am 22.03.2013 05:34 schrieb "Luciano Resende" : > > > On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com > > wrote: > > > There is a flag in the mail notification to turn of diff's in those > > emails. > > > So theoretically those emails don't have to include not even code > > fragments > > > of GPL licensed code. > > > So those emails could become what they initially should have been: Some > > > simple notification of activity. > > > > > > We are actually also not interested in what exactly has changed or > > archiving > > > external activities. > > > If anybody is interested in those projects he can catch up with those > > > involved there. > > > > > > All we are interested is a "heads up" there is something going on as we > > > provide integration APIs that 3th parties are using. > > > > > > There are also a number of more 3th party projects that send those > pings. > > > Basically all projects hosted at apache-extras.org are configured to > > send a > > > ping to our list when there was a SVN commit. > > > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > > > > > It is argueable if an Apache developer list is the right place to have > > such > > > a "news aggregator" for activities around OpenMeetings. > > > There might be easy ways to resolve such a conflict. Possibly for > > example a > > > Google Group Mailing list. "openmeetings-apache-extras" or something > like > > > that. It does in fact not make a difference, just another mailing list > to > > > monitor :) > > > It is just a bit an imaginary line that we draw here from my point of > > view. > > > > > > Sebastian > > > > > > > > > 2013/3/21 Jim Jagielski > > >> > > >> IMO, it's inappropriate content for a dev@ list, which is > > >> a place to *discuss* development, not an "archive" for > > >> external development, legal issues notwithstanding. > > >> > > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > > wrote: > > >> > > >> > I would be uncomfortable as well. If project members want to follow > > >> > external projects that's great, but duplicating all of an external > > project's > > >> > messages onto the public dev@ list is... not a best practice, to > say > > the > > >> > least. > > >> > > > >> > Personally, I'd have to presume (for the average user) that > everything > > >> > coming from that other GPL licensed project is GPL. Thus, this > seems > > to > > >> > violate the principle of least surprise and the fact that GPL is > > Category X, > > >> > which means that end users should be able to use Apache projects and > > >> > products without having to worry that GPL code is included - either > > in the > > >> > download, or in other places on our websites or mailing lists. > > >> > > > >> > - Shane > > >> > > > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > > >> >> It's come to my attention that the openmeetings project has > recently > > >> >> subscribed their dev list to the commit messages of a Google Code > > >> >> hosted > > >> >> project under the GPL. I asked why and was told " those updates are > > >> >> interesting for our integration API." There is some overlap in > > >> >> committers but the project communities do seem to be distinct other > > >> >> than > > >> >> this cross-posting of commits. > > >> >> > > >> >> I'm quite uncomfortable about this as it means that GPL code is > > passing > > >> >> through our lists (and being archived) without any clear indication > > of > > >> >> its legal status. What I'm not sure about is whether my discomfort > is > > >> >> because of an irrational fear of someone inadvertently using GPL > code > > >> >> without knowing it or whether that is, in fact, a rational fear. > > >> >> > > >> >> Advice please? > > >> >> > > >> >> Ross > > >> >> > > >> >> > > >> >> -- > > >> >> Ross Gardler (@rgardler) > > >> >> Programme Leader (Open Development) > > >> >> OpenDirective http://opendirective.com > > >> >> > > >> > > > > > We have had a similar discussion in the ComDev related to Apache > > Extras [1], and the consensus at that time was that external projects, > > particular the ones that are not compatible with AL2, should be > > managed separately, which means that we should not encourage PMCs to > > have their official mailing lists receiving e-mails from other > > non-Apache GPL projects. If individuals are interested on what's going > > on with external projects, they should subscribe to these projects > > mailing list as an individual. > > > > > >
Re: GSOC: Recurrence events support in OpenMeetings calendar
On Thu, Mar 21, 2013 at 10:44 PM, Irina Arkhipets wrote: > Dishara, > > Yes, moreover - this library is already used in OpenMeetings. > > Wonderful.. In fact I have created an eclipse project and was able to build the trunk.I will look in to this ical4j API and get an understanding of how this can be incorporated to this project implementation. And thank you for pointing out the ical4j. > Regards, > Irina. > > On Thu, Mar 21, 2013 at 10:49 PM, Dishara Wijewardana < > ddwijeward...@gmail.com> wrote: > > > On Thu, Mar 21, 2013 at 11:23 AM, Irina Arkhipets < > > irina.arkhip...@gmail.com > > > wrote: > > > > > Hi Dishara, > > > > > > FYI: you can try ical4j library for your project as it already > implements > > > required recurrence models for java. > > > > > > > Hi Irina, > > This seems pretty good indeed. I also saw quite a few positive feedbacks > > for them. Before digging in to this, can we ship this as a dependency > under > > Apache License 2 ? > > Please refer [1]. > > > > [1] - http://build.mnode.org/projects/ical4j/license.html > > > > > > > > https://sourceforge.net/projects/ical4j/ > > > > > > Best regards, > > > Irina. > > > > > > On Wed, Mar 20, 2013 at 12:41 AM, Dishara Wijewardana < > > > ddwijeward...@gmail.com> wrote: > > > > > > > Hi all, > > > > This is regarding the JIRA [1] created for one of the GSoC 2013 > project > > > > ideas. And I am moving the discussion regarding $subject at [1] to > open > > > > meeting dev list. > > > > > > > > Just a small brief of my self to the mailing list: I am Dishara > > > Wijewardana > > > > who is interested in contributing to Apache projects and I have > > > > successfully completed my last year GSoC (2012) in Apache Velocity > > > project > > > > and there I implemented a complete JSR 223 API support for velocity. > > And > > > > willing to take part in GSoC this year with Apache OpenMeetings. > > > > > > > > Hi Irina, > > > > It seems that what you basically mentioned on [1] are the fundamental > > > facts > > > > from iCalendar Specification which is related to recurrence events > > > > implementation. But I will start looking in to the spec [2] to get a > > > better > > > > understanding and meanwhile will checkout the code and build it first > > of > > > > all, and hopefully find a way in to the Open Meetings code base ;-). > > Will > > > > post If I encounter any issues. > > > > > > > > [1] - https://issues.apache.org/jira/browse/OPENMEETINGS-549 > > > > [2] - http://www.ietf.org/rfc/rfc2445.txt > > > > > > > > -- > > > > Thanks > > > > /Dishara > > > > > > > > > > > > > > > -- > > Thanks > > /Dishara > > > -- Thanks /Dishara
Re: Commit messages from GPL project on ASF list
The OpenMeetings PMC agrees on disabling those notifications. Anybody interested in those emails can subscribe to it on its own. Sebastian Am 22.03.2013 05:34 schrieb "Luciano Resende" : > On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com > wrote: > > There is a flag in the mail notification to turn of diff's in those > emails. > > So theoretically those emails don't have to include not even code > fragments > > of GPL licensed code. > > So those emails could become what they initially should have been: Some > > simple notification of activity. > > > > We are actually also not interested in what exactly has changed or > archiving > > external activities. > > If anybody is interested in those projects he can catch up with those > > involved there. > > > > All we are interested is a "heads up" there is something going on as we > > provide integration APIs that 3th parties are using. > > > > There are also a number of more 3th party projects that send those pings. > > Basically all projects hosted at apache-extras.org are configured to > send a > > ping to our list when there was a SVN commit. > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > > > It is argueable if an Apache developer list is the right place to have > such > > a "news aggregator" for activities around OpenMeetings. > > There might be easy ways to resolve such a conflict. Possibly for > example a > > Google Group Mailing list. "openmeetings-apache-extras" or something like > > that. It does in fact not make a difference, just another mailing list to > > monitor :) > > It is just a bit an imaginary line that we draw here from my point of > view. > > > > Sebastian > > > > > > 2013/3/21 Jim Jagielski > >> > >> IMO, it's inappropriate content for a dev@ list, which is > >> a place to *discuss* development, not an "archive" for > >> external development, legal issues notwithstanding. > >> > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > wrote: > >> > >> > I would be uncomfortable as well. If project members want to follow > >> > external projects that's great, but duplicating all of an external > project's > >> > messages onto the public dev@ list is... not a best practice, to say > the > >> > least. > >> > > >> > Personally, I'd have to presume (for the average user) that everything > >> > coming from that other GPL licensed project is GPL. Thus, this seems > to > >> > violate the principle of least surprise and the fact that GPL is > Category X, > >> > which means that end users should be able to use Apache projects and > >> > products without having to worry that GPL code is included - either > in the > >> > download, or in other places on our websites or mailing lists. > >> > > >> > - Shane > >> > > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > >> >> It's come to my attention that the openmeetings project has recently > >> >> subscribed their dev list to the commit messages of a Google Code > >> >> hosted > >> >> project under the GPL. I asked why and was told " those updates are > >> >> interesting for our integration API." There is some overlap in > >> >> committers but the project communities do seem to be distinct other > >> >> than > >> >> this cross-posting of commits. > >> >> > >> >> I'm quite uncomfortable about this as it means that GPL code is > passing > >> >> through our lists (and being archived) without any clear indication > of > >> >> its legal status. What I'm not sure about is whether my discomfort is > >> >> because of an irrational fear of someone inadvertently using GPL code > >> >> without knowing it or whether that is, in fact, a rational fear. > >> >> > >> >> Advice please? > >> >> > >> >> Ross > >> >> > >> >> > >> >> -- > >> >> Ross Gardler (@rgardler) > >> >> Programme Leader (Open Development) > >> >> OpenDirective http://opendirective.com > >> >> > >> > > > We have had a similar discussion in the ComDev related to Apache > Extras [1], and the consensus at that time was that external projects, > particular the ones that are not compatible with AL2, should be > managed separately, which means that we should not encourage PMCs to > have their official mailing lists receiving e-mails from other > non-Apache GPL projects. If individuals are interested on what's going > on with external projects, they should subscribe to these projects > mailing list as an individual. > > > > http://mail-archives.apache.org/mod_mbox/community-dev/201209.mbox/%3CCALvzYd-h4Q%3DcTEgGqCNEEninhVose8uiGt2gTK22n9cMr_kVyg%40mail.gmail.com%3E > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > > - > To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org > For additional commands, e-mail: legal-discuss-h...@apache.org > >
Re: Commit messages from GPL project on ASF list
Ok, so our concens is to disable those notifications. Anybody interested in those emails can subscribe to it on its own. Sebastian Am 21.03.2013 23:45 schrieb "Maxim Solodovnik" : > OK, thanks > Haven't read this :( > > > On Thu, Mar 21, 2013 at 5:41 PM, Alexei Fedotov >wrote: > > > I read Jim's concern below Sebastian's letter: > > > > > > 2013/3/21 Jim Jagielski > > > > > IMO, it's inappropriate content for a dev@ list, > > > a place to *discuss* development, not an "archive" for > > > external development, legal issues notwithstanding. > > -- > > With best regards / с наилучшими пожеланиями, > > Alexei Fedotov / Алексей Федотов, > > http://dataved.ru/ > > +7 916 562 8095 > > > > > > On Thu, Mar 21, 2013 at 2:22 PM, Maxim Solodovnik > > wrote: > > > @Alexei I'm afraid you are talking to wider list > > > Could you please clarify what "As for Jim's concern"? > > > > > > > > > On Thu, Mar 21, 2013 at 5:10 PM, Alexei Fedotov < > > alexei.fedo...@gmail.com>wrote: > > > > > >> As for Jim's concern, I think commits can be redirected to > commits@list. > > >> -- > > >> With best regards / с наилучшими пожеланиями, > > >> Alexei Fedotov / Алексей Федотов, > > >> http://dataved.ru/ > > >> +7 916 562 8095 > > >> > > >> > > >> On Thu, Mar 21, 2013 at 2:00 PM, seba.wag...@gmail.com > > >> wrote: > > >> > There is a flag in the mail notification to turn of diff's in those > > >> emails. > > >> > So theoretically those emails don't have to include not even code > > >> fragments > > >> > of GPL licensed code. > > >> > So those emails could become what they initially should have been: > > Some > > >> > simple notification of activity. > > >> > > > >> > We are actually also not interested in what exactly has changed or > > >> > archiving external activities. > > >> > If anybody is interested in those projects he can catch up with > those > > >> > involved there. > > >> > > > >> > All we are interested is a "heads up" there is something going on as > > we > > >> > provide integration APIs that 3th parties are using. > > >> > > > >> > There are also a number of more 3th party projects that send those > > pings. > > >> > Basically all projects hosted at apache-extras.org are configured > to > > >> send a > > >> > ping to our list when there was a SVN commit. > > >> > > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > >> > > > >> > It is argueable if an Apache developer list is the right place to > have > > >> such > > >> > a "news aggregator" for activities around OpenMeetings. > > >> > There might be easy ways to resolve such a conflict. Possibly for > > >> example a > > >> > Google Group Mailing list. "openmeetings-apache-extras" or something > > like > > >> > that. It does in fact not make a difference, just another mailing > > list to > > >> > monitor :) > > >> > It is just a bit an imaginary line that we draw here from my point > of > > >> view. > > >> > > > >> > Sebastian > > >> > > > >> > > > >> > 2013/3/21 Jim Jagielski > > >> > > > >> >> IMO, it's inappropriate content for a dev@ list, which is > > >> >> a place to *discuss* development, not an "archive" for > > >> >> external development, legal issues notwithstanding. > > >> >> > > >> >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > > >> wrote: > > >> >> > > >> >> > I would be uncomfortable as well. If project members want to > follow > > >> >> external projects that's great, but duplicating all of an external > > >> >> project's messages onto the public dev@ list is... not a best > > practice, > > >> >> to say the least. > > >> >> > > > >> >> > Personally, I'd have to presume (for the average user) that > > everything > > >> >> coming from that other GPL licensed project is GPL. Thus, this > > seems to > > >> >> violate the principle of least surprise and the fact that GPL is > > >> Category > > >> >> X, which means that end users should be able to use Apache projects > > and > > >> >> products without having to worry that GPL code is included - either > > in > > >> the > > >> >> download, or in other places on our websites or mailing lists. > > >> >> > > > >> >> > - Shane > > >> >> > > > >> >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > > >> >> >> It's come to my attention that the openmeetings project has > > recently > > >> >> >> subscribed their dev list to the commit messages of a Google > Code > > >> hosted > > >> >> >> project under the GPL. I asked why and was told " those updates > > are > > >> >> >> interesting for our integration API." There is some overlap in > > >> >> >> committers but the project communities do seem to be distinct > > other > > >> than > > >> >> >> this cross-posting of commits. > > >> >> >> > > >> >> >> I'm quite uncomfortable about this as it means that GPL code is > > >> passing > > >> >> >> through our lists (and being archived) without any clear > > indication > > >> of > > >> >> >> its legal status. What I'm not sure about is whether my > > discomfort is > > >> >> >> because of an i
Re: Commit messages from GPL project on ASF list
On Thu, Mar 21, 2013 at 3:00 AM, seba.wag...@gmail.com wrote: > There is a flag in the mail notification to turn of diff's in those emails. > So theoretically those emails don't have to include not even code fragments > of GPL licensed code. > So those emails could become what they initially should have been: Some > simple notification of activity. > > We are actually also not interested in what exactly has changed or archiving > external activities. > If anybody is interested in those projects he can catch up with those > involved there. > > All we are interested is a "heads up" there is something going on as we > provide integration APIs that 3th parties are using. > > There are also a number of more 3th party projects that send those pings. > Basically all projects hosted at apache-extras.org are configured to send a > ping to our list when there was a SVN commit. > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > It is argueable if an Apache developer list is the right place to have such > a "news aggregator" for activities around OpenMeetings. > There might be easy ways to resolve such a conflict. Possibly for example a > Google Group Mailing list. "openmeetings-apache-extras" or something like > that. It does in fact not make a difference, just another mailing list to > monitor :) > It is just a bit an imaginary line that we draw here from my point of view. > > Sebastian > > > 2013/3/21 Jim Jagielski >> >> IMO, it's inappropriate content for a dev@ list, which is >> a place to *discuss* development, not an "archive" for >> external development, legal issues notwithstanding. >> >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru wrote: >> >> > I would be uncomfortable as well. If project members want to follow >> > external projects that's great, but duplicating all of an external >> > project's >> > messages onto the public dev@ list is... not a best practice, to say the >> > least. >> > >> > Personally, I'd have to presume (for the average user) that everything >> > coming from that other GPL licensed project is GPL. Thus, this seems to >> > violate the principle of least surprise and the fact that GPL is Category >> > X, >> > which means that end users should be able to use Apache projects and >> > products without having to worry that GPL code is included - either in the >> > download, or in other places on our websites or mailing lists. >> > >> > - Shane >> > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: >> >> It's come to my attention that the openmeetings project has recently >> >> subscribed their dev list to the commit messages of a Google Code >> >> hosted >> >> project under the GPL. I asked why and was told " those updates are >> >> interesting for our integration API." There is some overlap in >> >> committers but the project communities do seem to be distinct other >> >> than >> >> this cross-posting of commits. >> >> >> >> I'm quite uncomfortable about this as it means that GPL code is passing >> >> through our lists (and being archived) without any clear indication of >> >> its legal status. What I'm not sure about is whether my discomfort is >> >> because of an irrational fear of someone inadvertently using GPL code >> >> without knowing it or whether that is, in fact, a rational fear. >> >> >> >> Advice please? >> >> >> >> Ross >> >> >> >> >> >> -- >> >> Ross Gardler (@rgardler) >> >> Programme Leader (Open Development) >> >> OpenDirective http://opendirective.com >> >> >> > We have had a similar discussion in the ComDev related to Apache Extras [1], and the consensus at that time was that external projects, particular the ones that are not compatible with AL2, should be managed separately, which means that we should not encourage PMCs to have their official mailing lists receiving e-mails from other non-Apache GPL projects. If individuals are interested on what's going on with external projects, they should subscribe to these projects mailing list as an individual. http://mail-archives.apache.org/mod_mbox/community-dev/201209.mbox/%3CCALvzYd-h4Q%3DcTEgGqCNEEninhVose8uiGt2gTK22n9cMr_kVyg%40mail.gmail.com%3E -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: GSOC: Recurrence events support in OpenMeetings calendar
Dishara, Yes, moreover - this library is already used in OpenMeetings. Regards, Irina. On Thu, Mar 21, 2013 at 10:49 PM, Dishara Wijewardana < ddwijeward...@gmail.com> wrote: > On Thu, Mar 21, 2013 at 11:23 AM, Irina Arkhipets < > irina.arkhip...@gmail.com > > wrote: > > > Hi Dishara, > > > > FYI: you can try ical4j library for your project as it already implements > > required recurrence models for java. > > > > Hi Irina, > This seems pretty good indeed. I also saw quite a few positive feedbacks > for them. Before digging in to this, can we ship this as a dependency under > Apache License 2 ? > Please refer [1]. > > [1] - http://build.mnode.org/projects/ical4j/license.html > > > > > https://sourceforge.net/projects/ical4j/ > > > > Best regards, > > Irina. > > > > On Wed, Mar 20, 2013 at 12:41 AM, Dishara Wijewardana < > > ddwijeward...@gmail.com> wrote: > > > > > Hi all, > > > This is regarding the JIRA [1] created for one of the GSoC 2013 project > > > ideas. And I am moving the discussion regarding $subject at [1] to open > > > meeting dev list. > > > > > > Just a small brief of my self to the mailing list: I am Dishara > > Wijewardana > > > who is interested in contributing to Apache projects and I have > > > successfully completed my last year GSoC (2012) in Apache Velocity > > project > > > and there I implemented a complete JSR 223 API support for velocity. > And > > > willing to take part in GSoC this year with Apache OpenMeetings. > > > > > > Hi Irina, > > > It seems that what you basically mentioned on [1] are the fundamental > > facts > > > from iCalendar Specification which is related to recurrence events > > > implementation. But I will start looking in to the spec [2] to get a > > better > > > understanding and meanwhile will checkout the code and build it first > of > > > all, and hopefully find a way in to the Open Meetings code base ;-). > Will > > > post If I encounter any issues. > > > > > > [1] - https://issues.apache.org/jira/browse/OPENMEETINGS-549 > > > [2] - http://www.ietf.org/rfc/rfc2445.txt > > > > > > -- > > > Thanks > > > /Dishara > > > > > > > > > -- > Thanks > /Dishara >
Re: GSOC: Recurrence events support in OpenMeetings calendar
On Thu, Mar 21, 2013 at 11:23 AM, Irina Arkhipets wrote: > Hi Dishara, > > FYI: you can try ical4j library for your project as it already implements > required recurrence models for java. > Hi Irina, This seems pretty good indeed. I also saw quite a few positive feedbacks for them. Before digging in to this, can we ship this as a dependency under Apache License 2 ? Please refer [1]. [1] - http://build.mnode.org/projects/ical4j/license.html > > https://sourceforge.net/projects/ical4j/ > > Best regards, > Irina. > > On Wed, Mar 20, 2013 at 12:41 AM, Dishara Wijewardana < > ddwijeward...@gmail.com> wrote: > > > Hi all, > > This is regarding the JIRA [1] created for one of the GSoC 2013 project > > ideas. And I am moving the discussion regarding $subject at [1] to open > > meeting dev list. > > > > Just a small brief of my self to the mailing list: I am Dishara > Wijewardana > > who is interested in contributing to Apache projects and I have > > successfully completed my last year GSoC (2012) in Apache Velocity > project > > and there I implemented a complete JSR 223 API support for velocity. And > > willing to take part in GSoC this year with Apache OpenMeetings. > > > > Hi Irina, > > It seems that what you basically mentioned on [1] are the fundamental > facts > > from iCalendar Specification which is related to recurrence events > > implementation. But I will start looking in to the spec [2] to get a > better > > understanding and meanwhile will checkout the code and build it first of > > all, and hopefully find a way in to the Open Meetings code base ;-). Will > > post If I encounter any issues. > > > > [1] - https://issues.apache.org/jira/browse/OPENMEETINGS-549 > > [2] - http://www.ietf.org/rfc/rfc2445.txt > > > > -- > > Thanks > > /Dishara > > > -- Thanks /Dishara
Re: Commit messages from GPL project on ASF list
OK, thanks Haven't read this :( On Thu, Mar 21, 2013 at 5:41 PM, Alexei Fedotov wrote: > I read Jim's concern below Sebastian's letter: > > > 2013/3/21 Jim Jagielski > > > IMO, it's inappropriate content for a dev@ list, > > a place to *discuss* development, not an "archive" for > > external development, legal issues notwithstanding. > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Thu, Mar 21, 2013 at 2:22 PM, Maxim Solodovnik > wrote: > > @Alexei I'm afraid you are talking to wider list > > Could you please clarify what "As for Jim's concern"? > > > > > > On Thu, Mar 21, 2013 at 5:10 PM, Alexei Fedotov < > alexei.fedo...@gmail.com>wrote: > > > >> As for Jim's concern, I think commits can be redirected to commits@list. > >> -- > >> With best regards / с наилучшими пожеланиями, > >> Alexei Fedotov / Алексей Федотов, > >> http://dataved.ru/ > >> +7 916 562 8095 > >> > >> > >> On Thu, Mar 21, 2013 at 2:00 PM, seba.wag...@gmail.com > >> wrote: > >> > There is a flag in the mail notification to turn of diff's in those > >> emails. > >> > So theoretically those emails don't have to include not even code > >> fragments > >> > of GPL licensed code. > >> > So those emails could become what they initially should have been: > Some > >> > simple notification of activity. > >> > > >> > We are actually also not interested in what exactly has changed or > >> > archiving external activities. > >> > If anybody is interested in those projects he can catch up with those > >> > involved there. > >> > > >> > All we are interested is a "heads up" there is something going on as > we > >> > provide integration APIs that 3th parties are using. > >> > > >> > There are also a number of more 3th party projects that send those > pings. > >> > Basically all projects hosted at apache-extras.org are configured to > >> send a > >> > ping to our list when there was a SVN commit. > >> > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > >> > > >> > It is argueable if an Apache developer list is the right place to have > >> such > >> > a "news aggregator" for activities around OpenMeetings. > >> > There might be easy ways to resolve such a conflict. Possibly for > >> example a > >> > Google Group Mailing list. "openmeetings-apache-extras" or something > like > >> > that. It does in fact not make a difference, just another mailing > list to > >> > monitor :) > >> > It is just a bit an imaginary line that we draw here from my point of > >> view. > >> > > >> > Sebastian > >> > > >> > > >> > 2013/3/21 Jim Jagielski > >> > > >> >> IMO, it's inappropriate content for a dev@ list, which is > >> >> a place to *discuss* development, not an "archive" for > >> >> external development, legal issues notwithstanding. > >> >> > >> >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > >> wrote: > >> >> > >> >> > I would be uncomfortable as well. If project members want to follow > >> >> external projects that's great, but duplicating all of an external > >> >> project's messages onto the public dev@ list is... not a best > practice, > >> >> to say the least. > >> >> > > >> >> > Personally, I'd have to presume (for the average user) that > everything > >> >> coming from that other GPL licensed project is GPL. Thus, this > seems to > >> >> violate the principle of least surprise and the fact that GPL is > >> Category > >> >> X, which means that end users should be able to use Apache projects > and > >> >> products without having to worry that GPL code is included - either > in > >> the > >> >> download, or in other places on our websites or mailing lists. > >> >> > > >> >> > - Shane > >> >> > > >> >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > >> >> >> It's come to my attention that the openmeetings project has > recently > >> >> >> subscribed their dev list to the commit messages of a Google Code > >> hosted > >> >> >> project under the GPL. I asked why and was told " those updates > are > >> >> >> interesting for our integration API." There is some overlap in > >> >> >> committers but the project communities do seem to be distinct > other > >> than > >> >> >> this cross-posting of commits. > >> >> >> > >> >> >> I'm quite uncomfortable about this as it means that GPL code is > >> passing > >> >> >> through our lists (and being archived) without any clear > indication > >> of > >> >> >> its legal status. What I'm not sure about is whether my > discomfort is > >> >> >> because of an irrational fear of someone inadvertently using GPL > code > >> >> >> without knowing it or whether that is, in fact, a rational fear. > >> >> >> > >> >> >> Advice please? > >> >> >> > >> >> >> Ross > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> Ross Gardler (@rgardler) > >> >> >> Programme Leader (Open Development) > >> >> >> OpenDirective http://opendirective.com > >> >> >> > >> >> > > >> >> > > >> >> > > -
Re: Commit messages from GPL project on ASF list
I read Jim's concern below Sebastian's letter: 2013/3/21 Jim Jagielski > IMO, it's inappropriate content for a dev@ list, > a place to *discuss* development, not an "archive" for > external development, legal issues notwithstanding. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Mar 21, 2013 at 2:22 PM, Maxim Solodovnik wrote: > @Alexei I'm afraid you are talking to wider list > Could you please clarify what "As for Jim's concern"? > > > On Thu, Mar 21, 2013 at 5:10 PM, Alexei Fedotov > wrote: > >> As for Jim's concern, I think commits can be redirected to commits@ list. >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> On Thu, Mar 21, 2013 at 2:00 PM, seba.wag...@gmail.com >> wrote: >> > There is a flag in the mail notification to turn of diff's in those >> emails. >> > So theoretically those emails don't have to include not even code >> fragments >> > of GPL licensed code. >> > So those emails could become what they initially should have been: Some >> > simple notification of activity. >> > >> > We are actually also not interested in what exactly has changed or >> > archiving external activities. >> > If anybody is interested in those projects he can catch up with those >> > involved there. >> > >> > All we are interested is a "heads up" there is something going on as we >> > provide integration APIs that 3th parties are using. >> > >> > There are also a number of more 3th party projects that send those pings. >> > Basically all projects hosted at apache-extras.org are configured to >> send a >> > ping to our list when there was a SVN commit. >> > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings >> > >> > It is argueable if an Apache developer list is the right place to have >> such >> > a "news aggregator" for activities around OpenMeetings. >> > There might be easy ways to resolve such a conflict. Possibly for >> example a >> > Google Group Mailing list. "openmeetings-apache-extras" or something like >> > that. It does in fact not make a difference, just another mailing list to >> > monitor :) >> > It is just a bit an imaginary line that we draw here from my point of >> view. >> > >> > Sebastian >> > >> > >> > 2013/3/21 Jim Jagielski >> > >> >> IMO, it's inappropriate content for a dev@ list, which is >> >> a place to *discuss* development, not an "archive" for >> >> external development, legal issues notwithstanding. >> >> >> >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru >> wrote: >> >> >> >> > I would be uncomfortable as well. If project members want to follow >> >> external projects that's great, but duplicating all of an external >> >> project's messages onto the public dev@ list is... not a best practice, >> >> to say the least. >> >> > >> >> > Personally, I'd have to presume (for the average user) that everything >> >> coming from that other GPL licensed project is GPL. Thus, this seems to >> >> violate the principle of least surprise and the fact that GPL is >> Category >> >> X, which means that end users should be able to use Apache projects and >> >> products without having to worry that GPL code is included - either in >> the >> >> download, or in other places on our websites or mailing lists. >> >> > >> >> > - Shane >> >> > >> >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: >> >> >> It's come to my attention that the openmeetings project has recently >> >> >> subscribed their dev list to the commit messages of a Google Code >> hosted >> >> >> project under the GPL. I asked why and was told " those updates are >> >> >> interesting for our integration API." There is some overlap in >> >> >> committers but the project communities do seem to be distinct other >> than >> >> >> this cross-posting of commits. >> >> >> >> >> >> I'm quite uncomfortable about this as it means that GPL code is >> passing >> >> >> through our lists (and being archived) without any clear indication >> of >> >> >> its legal status. What I'm not sure about is whether my discomfort is >> >> >> because of an irrational fear of someone inadvertently using GPL code >> >> >> without knowing it or whether that is, in fact, a rational fear. >> >> >> >> >> >> Advice please? >> >> >> >> >> >> Ross >> >> >> >> >> >> >> >> >> -- >> >> >> Ross Gardler (@rgardler) >> >> >> Programme Leader (Open Development) >> >> >> OpenDirective http://opendirective.com >> >> >> >> >> > >> >> > >> >> > - >> >> > To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org >> >> > For additional commands, e-mail: legal-discuss-h...@apache.org >> >> > >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org >> >> For additional commands, e-mail: legal-discuss-h...@apache.org >> >> >
Re: Commit messages from GPL project on ASF list
@Alexei I'm afraid you are talking to wider list Could you please clarify what "As for Jim's concern"? On Thu, Mar 21, 2013 at 5:10 PM, Alexei Fedotov wrote: > As for Jim's concern, I think commits can be redirected to commits@ list. > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Thu, Mar 21, 2013 at 2:00 PM, seba.wag...@gmail.com > wrote: > > There is a flag in the mail notification to turn of diff's in those > emails. > > So theoretically those emails don't have to include not even code > fragments > > of GPL licensed code. > > So those emails could become what they initially should have been: Some > > simple notification of activity. > > > > We are actually also not interested in what exactly has changed or > > archiving external activities. > > If anybody is interested in those projects he can catch up with those > > involved there. > > > > All we are interested is a "heads up" there is something going on as we > > provide integration APIs that 3th parties are using. > > > > There are also a number of more 3th party projects that send those pings. > > Basically all projects hosted at apache-extras.org are configured to > send a > > ping to our list when there was a SVN commit. > > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > > > It is argueable if an Apache developer list is the right place to have > such > > a "news aggregator" for activities around OpenMeetings. > > There might be easy ways to resolve such a conflict. Possibly for > example a > > Google Group Mailing list. "openmeetings-apache-extras" or something like > > that. It does in fact not make a difference, just another mailing list to > > monitor :) > > It is just a bit an imaginary line that we draw here from my point of > view. > > > > Sebastian > > > > > > 2013/3/21 Jim Jagielski > > > >> IMO, it's inappropriate content for a dev@ list, which is > >> a place to *discuss* development, not an "archive" for > >> external development, legal issues notwithstanding. > >> > >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru > wrote: > >> > >> > I would be uncomfortable as well. If project members want to follow > >> external projects that's great, but duplicating all of an external > >> project's messages onto the public dev@ list is... not a best practice, > >> to say the least. > >> > > >> > Personally, I'd have to presume (for the average user) that everything > >> coming from that other GPL licensed project is GPL. Thus, this seems to > >> violate the principle of least surprise and the fact that GPL is > Category > >> X, which means that end users should be able to use Apache projects and > >> products without having to worry that GPL code is included - either in > the > >> download, or in other places on our websites or mailing lists. > >> > > >> > - Shane > >> > > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: > >> >> It's come to my attention that the openmeetings project has recently > >> >> subscribed their dev list to the commit messages of a Google Code > hosted > >> >> project under the GPL. I asked why and was told " those updates are > >> >> interesting for our integration API." There is some overlap in > >> >> committers but the project communities do seem to be distinct other > than > >> >> this cross-posting of commits. > >> >> > >> >> I'm quite uncomfortable about this as it means that GPL code is > passing > >> >> through our lists (and being archived) without any clear indication > of > >> >> its legal status. What I'm not sure about is whether my discomfort is > >> >> because of an irrational fear of someone inadvertently using GPL code > >> >> without knowing it or whether that is, in fact, a rational fear. > >> >> > >> >> Advice please? > >> >> > >> >> Ross > >> >> > >> >> > >> >> -- > >> >> Ross Gardler (@rgardler) > >> >> Programme Leader (Open Development) > >> >> OpenDirective http://opendirective.com > >> >> > >> > > >> > > >> > - > >> > To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org > >> > For additional commands, e-mail: legal-discuss-h...@apache.org > >> > > >> > >> > >> - > >> To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org > >> For additional commands, e-mail: legal-discuss-h...@apache.org > >> > >> > > > > > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > seba.wag...@gmail.com > -- WBR Maxim aka solomax
Re: Commit messages from GPL project on ASF list
As for Jim's concern, I think commits can be redirected to commits@ list. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Mar 21, 2013 at 2:00 PM, seba.wag...@gmail.com wrote: > There is a flag in the mail notification to turn of diff's in those emails. > So theoretically those emails don't have to include not even code fragments > of GPL licensed code. > So those emails could become what they initially should have been: Some > simple notification of activity. > > We are actually also not interested in what exactly has changed or > archiving external activities. > If anybody is interested in those projects he can catch up with those > involved there. > > All we are interested is a "heads up" there is something going on as we > provide integration APIs that 3th parties are using. > > There are also a number of more 3th party projects that send those pings. > Basically all projects hosted at apache-extras.org are configured to send a > ping to our list when there was a SVN commit. > http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings > > It is argueable if an Apache developer list is the right place to have such > a "news aggregator" for activities around OpenMeetings. > There might be easy ways to resolve such a conflict. Possibly for example a > Google Group Mailing list. "openmeetings-apache-extras" or something like > that. It does in fact not make a difference, just another mailing list to > monitor :) > It is just a bit an imaginary line that we draw here from my point of view. > > Sebastian > > > 2013/3/21 Jim Jagielski > >> IMO, it's inappropriate content for a dev@ list, which is >> a place to *discuss* development, not an "archive" for >> external development, legal issues notwithstanding. >> >> On Mar 20, 2013, at 7:16 AM, Shane Curcuru wrote: >> >> > I would be uncomfortable as well. If project members want to follow >> external projects that's great, but duplicating all of an external >> project's messages onto the public dev@ list is... not a best practice, >> to say the least. >> > >> > Personally, I'd have to presume (for the average user) that everything >> coming from that other GPL licensed project is GPL. Thus, this seems to >> violate the principle of least surprise and the fact that GPL is Category >> X, which means that end users should be able to use Apache projects and >> products without having to worry that GPL code is included - either in the >> download, or in other places on our websites or mailing lists. >> > >> > - Shane >> > >> > On 3/19/2013 6:51 PM, Ross Gardler wrote: >> >> It's come to my attention that the openmeetings project has recently >> >> subscribed their dev list to the commit messages of a Google Code hosted >> >> project under the GPL. I asked why and was told " those updates are >> >> interesting for our integration API." There is some overlap in >> >> committers but the project communities do seem to be distinct other than >> >> this cross-posting of commits. >> >> >> >> I'm quite uncomfortable about this as it means that GPL code is passing >> >> through our lists (and being archived) without any clear indication of >> >> its legal status. What I'm not sure about is whether my discomfort is >> >> because of an irrational fear of someone inadvertently using GPL code >> >> without knowing it or whether that is, in fact, a rational fear. >> >> >> >> Advice please? >> >> >> >> Ross >> >> >> >> >> >> -- >> >> Ross Gardler (@rgardler) >> >> Programme Leader (Open Development) >> >> OpenDirective http://opendirective.com >> >> >> > >> > >> > - >> > To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org >> > For additional commands, e-mail: legal-discuss-h...@apache.org >> > >> >> >> - >> To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org >> For additional commands, e-mail: legal-discuss-h...@apache.org >> >> > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wag...@gmail.com
Re: Commit messages from GPL project on ASF list
There is a flag in the mail notification to turn of diff's in those emails. So theoretically those emails don't have to include not even code fragments of GPL licensed code. So those emails could become what they initially should have been: Some simple notification of activity. We are actually also not interested in what exactly has changed or archiving external activities. If anybody is interested in those projects he can catch up with those involved there. All we are interested is a "heads up" there is something going on as we provide integration APIs that 3th parties are using. There are also a number of more 3th party projects that send those pings. Basically all projects hosted at apache-extras.org are configured to send a ping to our list when there was a SVN commit. http://code.google.com/a/apache-extras.org/hosting/search?q=openmeetings It is argueable if an Apache developer list is the right place to have such a "news aggregator" for activities around OpenMeetings. There might be easy ways to resolve such a conflict. Possibly for example a Google Group Mailing list. "openmeetings-apache-extras" or something like that. It does in fact not make a difference, just another mailing list to monitor :) It is just a bit an imaginary line that we draw here from my point of view. Sebastian 2013/3/21 Jim Jagielski > IMO, it's inappropriate content for a dev@ list, which is > a place to *discuss* development, not an "archive" for > external development, legal issues notwithstanding. > > On Mar 20, 2013, at 7:16 AM, Shane Curcuru wrote: > > > I would be uncomfortable as well. If project members want to follow > external projects that's great, but duplicating all of an external > project's messages onto the public dev@ list is... not a best practice, > to say the least. > > > > Personally, I'd have to presume (for the average user) that everything > coming from that other GPL licensed project is GPL. Thus, this seems to > violate the principle of least surprise and the fact that GPL is Category > X, which means that end users should be able to use Apache projects and > products without having to worry that GPL code is included - either in the > download, or in other places on our websites or mailing lists. > > > > - Shane > > > > On 3/19/2013 6:51 PM, Ross Gardler wrote: > >> It's come to my attention that the openmeetings project has recently > >> subscribed their dev list to the commit messages of a Google Code hosted > >> project under the GPL. I asked why and was told " those updates are > >> interesting for our integration API." There is some overlap in > >> committers but the project communities do seem to be distinct other than > >> this cross-posting of commits. > >> > >> I'm quite uncomfortable about this as it means that GPL code is passing > >> through our lists (and being archived) without any clear indication of > >> its legal status. What I'm not sure about is whether my discomfort is > >> because of an irrational fear of someone inadvertently using GPL code > >> without knowing it or whether that is, in fact, a rational fear. > >> > >> Advice please? > >> > >> Ross > >> > >> > >> -- > >> Ross Gardler (@rgardler) > >> Programme Leader (Open Development) > >> OpenDirective http://opendirective.com > >> > > > > > > - > > To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org > > For additional commands, e-mail: legal-discuss-h...@apache.org > > > > > - > To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org > For additional commands, e-mail: legal-discuss-h...@apache.org > > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com
Re: configure room
Hi Vital, No, there is no such a possibility for now. Regards, Irina. On Thu, Mar 21, 2013 at 2:26 PM, Vital Kutsyv wrote: > Hi, everyone! > Is it possible to make so that the lecturer in the room saw a video of all > the students, and the students only the video of the lecturer? > > > -- > Vitaly Kutsyv >
configure room
Hi, everyone! Is it possible to make so that the lecturer in the room saw a video of all the students, and the students only the video of the lecturer? -- Vitaly Kutsyv
