Re: [IMO] There are no Incubator issues
A month.. aha. :-) 08.11.2013 3:35 пользователь "Martijn Dashorst" написал: > In my opinion it is always a failure of a podling when they can't get > a release out of the door, or are unable to vote in new committers. > > "The future is not something we enter. The future is something we > create." --Leonard I. Sweet > > As a podling is waiting for its release to be approved, I sure hope > they aren't holding their breath. If they have missing mentors, then > prod the mentors. If the mentors don't react, prod general@ (in a > polite way). If that doesn't help prod private@ or send a message to > VP incubator. > > Is it frustrating that a first release can take a month to get to your > users? Yup. But consider that if it takes a month, your release and > your release process had many issues. Your next release should go much > faster (you did automate the release building, did you?). Is it > frustrating that nobody wants to look at your release? Yup. But ask > politely: you are asking volunteers their time–time they can spend > with their children, spouses, parents, friends or with their existing > projects. Time they will never get back. So spend that time wisely! > > Outside the incubator you will find that it is still hard to get a > release vetted. People get swamped in work. They move houses. Life > happens. The incubator won't the last time you will struggle to get > the required +3 binding votes. Outside the incubator you also need to > make it happen, so show that you are able to do so! > > If/when a drive by review unveils some things that are wrong with a > release (even minutia) go fix them, automate them and respin the > release. Do the work and get the release up to standards. You got the > attention, someone put the time in to review your release, the onus is > on you to fix it. Do it quickly and you'll have a review that much > faster. Even better if you can prove that you fixed the discovered > issues (show a rat report, a diff of the archive structure, etc). > > Subscribe to the general@ list and read the things that are uncovered > for failed releases. Fix that too in your release. This way you learn > from other folks' mistakes. > > Fill in your board reports on time. Prod your mentors to sign off the > reports. Do the trademark search. Fix the licensing. Expand your > community. > > Self governance doesn't just mean the ability to answer messages on > users@ or to have civil discourse on dev@, or the ability to commit > code without having too many merge conflicts. It also means taking > responsibility for your project. You are responsible for getting a > release out of the door: it is your project! You are responsible for > ensuring the status page is completely checked off: it is your > project! You are responsible for completing a trademark search: it is > your project! You are responsible for filing a board report on time: > it is your project! > > And yes I speak from my own experience. With Wicket we were living in > a slum for half a year. But finally we got our own act together to get > a release out the door, to vote in new committers, to fix our status > page, to fix our licensing issues etc. That is hard work and you have > to spend the time and energy to complete those tasks. But when you > have everything in order, you can graduate with confidence. > > The short guide to graduation: do the work, see it through, persevere > and graduate. > > Martijn > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Graduate Apache Marmotta as TLP
+1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/ [2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings On Mon, Nov 4, 2013 at 1:16 PM, Fabian Christ wrote: > +1 > > Best, > - Fabian (Marmotta mentor) > > 2013/11/4 Jakob Frank : >> Hi all, >> >> the Marmotta podling, whose goal is to provide an Open Platform for >> Linked Data, entered incubation in December 2012. Since then, the >> codebase has stabilized and two releases were published following ASF >> policies and guidelines. >> The community has grown, two new committers have joined the development >> team and more people joined the mailing lists. >> >> The last incubator report lists Marmotta as "Ready to graduate" [1], the >> Marmotta community has decided to take this step [2] and agreed on a >> Graduation Resolution Draft [3] which is also attached below. >> >> The resolution draft was posted to general@incubator.a.o for discussion >> [4] and raised no concerns, now please cast your votes: >> >> [ ] +1 Graduate the Marmotta podling from Incubator >> [ ] +0 Indifferent to graduation status of the Marmotta podling >> [ ] -1 Reject graduation of the Marmotta podling from Incubator because... >> >> The vote will be open for at least 72 hours starting now. >> >> >> Best, >> Jakob >> on behalf of the Marmotta community >> >> [1] <http://s.apache.org/marmotta-graduation-vote> >> [2] <http://s.apache.org/marmotta-graduation-result> >> [3] <http://s.apache.org/marmotta-graduation-resolution> >> [4] <http://s.apache.org/dYt> >> >> Apache Marmotta Graduation Resolution >> = >> >> X. Establish the Apache Marmotta Project >> >>WHEREAS, the Board of Directors deems it to be in the best >>interests of the Foundation and consistent with the >>Foundation's purpose to establish a Project Management >>Committee charged with the creation and maintenance of >>open-source software, for distribution at no charge to >>the public, related to an open platform for Linked Data. >> >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>Committee (PMC), to be known as the "Apache Marmotta Project", >>be and hereby is established pursuant to Bylaws of the >>Foundation; and be it further >> >>RESOLVED, that the Apache Marmotta Project be and hereby is >>responsible for the creation and maintenance of software >>related to an open platform for Linked Data; >>and be it further >> >>RESOLVED, that the office of "Vice President, Apache Marmotta" be >>and hereby is created, the person holding such office to >>serve at the direction of the Board of Directors as the chair >>of the Apache Marmotta Project, and to have primary responsibility >>for management of the projects within the scope of >>responsibility of the Apache Marmotta Project; and be it further >> >>RESOLVED, that the persons listed immediately below be and >>hereby are appointed to serve as the initial members of the >>Apache Marmotta Project: >> >> * Peter Ansell >> * Fabian Christ >> * Sergio Fernández >> * Jakob Frank >> * Dietmar Glachs >> * Thomas Kurz >> * Nandana Mihindukulasooriya >> * Raffaele Palmieri >> * Sebastian Schaffert >> * Rupert Westenthaler >> >>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank >>be appointed to the office of Vice President, Apache Marmotta, to >>serve in accordance with and subject to the direction of the >>Board of Directors and the Bylaws of the Foundation until >>death, resignation, retirement, removal or disqualification, >>or until a successor is appointed; and be it further >> >>RESOLVED, that the Apache Marmotta Project be and hereby >>is tasked with the migration and rationalization of the Apache >>Incub
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
I like the idea. Btw, I'm currently trying github gists as a database backend. 16.09.2013 21:06 пользователь "Luciano Resende" написал: > On Mon, Sep 16, 2013 at 6:39 AM, Jim Jagielski wrote: > > > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > > stack for web & mobile applications based on RESTful APIs, as an Apache > > Incubator podling. > > > > Here is a link to the proposal: > >https://wiki.apache.org/incubator/UsergridProposal > > > > It is also pasted below: > > > > = Usergrid Proposal = > > > > == Abstract == > > > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > > applications, based on RESTful APIs. > > > > > > == Proposal == > > > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > > composed > > of an integrated distributed NoSQL database, application layer and client > > tier with SDKs for developers looking to rapidly build web and/or mobile > > applications. It provides elementary services (user registration & > > management, data storage, file storage, queues) and retrieval features > > (full > > text search, geolocation search, joins) to power common app features. > > > > It is a multi-tenant system designed for deployment to public cloud > > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > > traditional server infrastructures so that anyone can run their own > private > > BaaS deployment. > > > > For architects and back-end teams, it aims to provide a distributed, > easily > > extendable, operationally predictable and highly scalable solution. For > > front-end developers, it aims to simplify the development process by > > enabling them to rapidly build and operate mobile and web applications > > without requiring backend expertise. > > > > > > == Background == > > > > Developing web or mobile applications obviously necessitates writing and > > maintaining more than just front-end code. Even simple applications can > > implicitly rely on server code being run to store users, perform database > > queries, serve images and video files, etc. Developing and maintaining > such > > backend services requires skills not always available or expected of app > > development teams. Beyond that, the proliferation of apps inside of > > companies leads to the creation of many different, ad-hoc, unequally > > maintained backend solutions created by employees and contractors alike > and > > hosted on a wide variety of environments. This is causing poor resource > > usage, operational issues, as well as security, privacy & compliance > > concerns. > > > > In response to this problem, companies have long tried to standardize > their > > server-side stack or unify them behind an ESB or API strategy. > > Backends-as-a-Service follow a similar approach but their unique > > characteristic is strongly tying 1) a persistence tier (typically a > > database), 2) a server-side application tier delivering a set of common > > services and 3) a set of client-side application interface mechanisms. > For > > example, a BaaS could package 1) MongoDB with 2) a node.js application > that > > offers access through 3) WebSockets. In the case of Usergrid, the > trifecta > > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > > > The Backend-as-a-Service approach has steadily gained popularity in the > > last > > few years with cloud providers such Parse.com, Stackmob.com and > Kinvey.com, > > each operating tens of thousands of apps for tens of thousands of > > developers. The trend has already reached large organizations as well, > with > > global companies such as Korea Telecom internally building a > privately-run > > BaaS platform. But so far, there have been limited options for developers > > that want a non-proprietary, open option for hosting and providing these > > services themselves, or for enterprise and government users who want to > > provide these capabilities from their own data centers, especially on a > > very > > large scale. > > > > > > == Rationale == > > > > The issue this proposal deals with is implicit in the name. > > Backend-as-a-Service platforms are usually offered solely as proprietary > > cloud services. They are typically closed sourced, hosted on public > clouds, > > and require subscription payment. Usergrid opens the playing field, by > > making a fully-featured BaaS platform freely available to all. This > > includes > > developers that previously could not afford them, such as mobile > > enthusiasts, small boutiques, and cost-sensitive startups. This also > > includes large companies that benefit from a reference implementation > they > > can deploy in trust, or extend to their needs without losing time writing > > less-vetted, less-performant boilerplate functionality. > > > > Usergrid has been open source since 2011 and has grown as an independent > > project, garnering 11 primary committers, 35 total contributors, 260+ > > participants on its mailing list, with 3,700+ commits, 20
Re: [ANNOUNCE] Apache jclouds 1.6.1-incubating released
Congratulations! 20.06.2013 7:33 пользователь "Andrew Bayer" написал: > The Apache jclouds (incubating) team is pleased to announce the release of > jclouds 1.6.1-incubating. > > This is the first Apache release of jclouds. Apache jclouds is a cloud > agnostic library that enables developers to access a variety of supported > cloud providers using one API. > > The source archives for the release are available here: > http://www.apache.org/dyn/closer.cgi/incubator/jclouds > > The Maven artifacts for the release are available in Maven Central, under > the new org.apache.jclouds groupId. > > The full change log is available here: > https://issues.apache.org/jira/browse/JCLOUDS/fixforversion/12324412 > > We welcome your help and feedback. For more information on how to > report problems, and to get involved, visit the project website at > http://jclouds.incubator.apache.org/ > > The Apache jclouds Team >
Re: [PROPOSAL] Creation of the Incubator Ombudsman
Hello, Why one would need an additional alias? Existing questions are sent to general@ or dev@community or (please add here), and one in the superhero role should timely answer them or facilitate an answer. [Complex question] tag in the subject line should be sufficient, or just no answer to some mail for 72 hours. If titles are important, we can simply assign nice titles to guys who answer to 10 of these complex issues. Maybe some discussion on facilitation means can be useful to avoid calling the guy impolite. I have one particular problem to deal with. New projects which come outside of Apache, cannot find Apache champion. The request is too wide to reach someones ear. One possibe way to address it is to assign an eco-champion to the new project who performs the project evaluation. The champion comes from the Apache project of the same area. Sometimes we may end up with community merges by going this way. 19.06.2013 3:03 пользователь "Ross Gardler" написал: > On 18 June 2013 23:53, Joe Schaefer wrote: > > Why so much reluctance to just honor the request such as it is > > instead of looking for different ways of modifying it to taste? > > ISSUE 03 at work I think - perhaps it is my fault for thinking aloud > about how the role might also help solve a different problem from the > one it was originally designed to solve. Maybe I set the wrong tone > for discussion. Lets forget that. > > Please just go ahead and do it the way you are suggesting. There is no > harm. The worst that can happen is someone sends an email to the alias > and there is no response. The next worst is that nobody ever uses it. > In either case we will eventually reverse this step. > > And please also go ahead with your "bill of rights" - I'll comment in > that thread in a moment. > > Ross > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [PROPOSAL] Mandatory podling exit interviews
I believe a set of automatically generated monthly metrics including a number of commits, total number of letters to the project mail list and number of mentor letters to the list will give a good picture which projects experience which problems. 15.06.2013 19:48 пользователь "Alan Cabrera" написал: > > Problem: we seem to have unclear and conflicting ideas as to what the > areas of improvement are for the Incubator. > > Cause: we have no concrete, anonymized, information on what the podlings' > experiences were during incubation. > > Solution: require all podlings to submit anonymous exit interviews as part > of the graduation requirements. These exit interviews will be suitably > scrubbed and organized by the Incubator Ombudsman; see next proposal. > > > Regards, > Alan > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [PROPOSAL] Creation of the Incubator Ombudsman
Let me add that a TLP sometimes get confused when it faces a problem. :-) Why these problem solving superheroes should limit themselves to the incubator? 15.06.2013 19:53 пользователь "Alan Cabrera" написал: > > Problem: podlings are confused on where to go when there's a problem. > > Cause: we seem to collect/handle/organize problems in an ad hoc manner > and sometimes mentors are the problem. > > Solution: we create an elected Incubator Ombudsman. > > > Regards, > Alan > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
I'm just happy to have PaaS as a part of Apache. Thanks to all who are doing this. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jun 13, 2013 at 2:21 PM, Ross Gardler wrote: > On 13 June 2013 10:56, Noah Slater wrote: >> Ross, thanks for bringing this up! I'm happy to be a part of this >> experiment. >> >> On 13 June 2013 09:13, Ross Gardler wrote: >> >>> "Better" yes - "required" before we can vote - no. My reasoning is >>> that WSO2 have already agreed they will use a different name if VP >>> Branding requires it. In fact they won't have any choice since the >>> proposal clearly indicates the Stratos trademark will be assigned to >>> the ASF. >>> >> >> While owning the "Stratos" trademark would certainly put us in a position >> of being able to ask WSO2 to stop using StratosLive. But there's no >> guarantee that we would be successful. > > That's true, but there is no change in that risk even if we give WSO2 > an answer before the vote. What is more important (in my non-legal > opinion) is a publicly archived statement from the WSO2 CEO stating > they have no intention of abusing the Stratos mark that will be > donated to the ASF. We already have that. > > It's only about the required order, not about the end game. > > Note, it is normal practice for pre-existing marks to be formally > donated to the ASF during incubation, usually just before graduation. > The former owner does not (usually) want to assign a mark that may > become useless if the project does not graduate. Such graduation is > not wholly under the control of the trademark owner. > >> 1. You need to be mindful of third-parties using your trademark in a >> compound name. > > This is already encoded in the ASF trademarks policies - WSO2 have > agreed to conform to those policies. > >> 2. You need to apply branding rules consistently. > > WSO2 have agreed to do so. > > Sanjiva - perhaps you can edit the proposal to this effect in order to > help allay any fears. That is to include the statement you made > earlier: > > "if StratosLive is too close to home we can certainly change it. Bit > painful but not impossible." > > I don't want to hold up the vote for entry into the incubator on this > issue. At the same time I don't want VP Branding to be in a position > of having to come to a quick decision. We will have plenty of time > during incubation to resolve everything to our satisfaction. > Ultimately VP Branding will be able to object to graduation if the > issue has not been adequately addressed during incubation. > >> We allowed Couchbase (and >> others) to share our brand because they were seen as "friendly" to the >> community. > > This is the root of why CouchDB has a problem today. I believe you a > projecting that problem and its cause onto a different issue here. > This is not about allowing WSO2 an exception to the existing policy. > It is about giving WSO2, the Stratos project community (which includes > you) and VP Branding time to work on a satisfactory solution *during* > incubation rather than prior to a vote. In my opinion WSO2 have > demonstrated they are willing to play by the rules. > > Ross > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Error collecting infrastructure for Openmeetings
Sebastian, I believe as for now, the decision is *not to include* the code into release. I opposed this initially, yet it seems I have to step down here. There were no strong support for this from anyone other then me. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 12, 2013 at 3:16 AM, seba.wag...@gmail.com wrote: > *AFAIK, > many Apache projects do use Google Analytics already.* > => The next question will be: Which projects do you Google Analytics? > > I doubt that any Apache product includes a UA code in its release packages. > > Sebastian > > > 2013/6/10 Alexei Fedotov > >> [added general@ for vivid discussion] >> >> Hello Sebastian, >> >> I'm glad that the statement that this infrastructure is needed is not >> questioned. >> >> We technically can use either CGI script, or existing Confluence API. >> The intention for using Google Analytics is minimum effort. AFAIK, >> many Apache projects do use Google Analytics already. >> >> The goal for the request is to avoid inventing a project-wide policy >> where foundation-wide policy is needed. >> >> With best regards, Alexei >> >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> On Mon, Jun 10, 2013 at 7:03 AM, seba.wag...@gmail.com >> wrote: >> > Hi Alexei, >> > >> > what about a simple CGI script that takes the input and send an email to >> the >> > mailing list? >> > I think some more simple approach would do the same and does not have >> such a >> > deep impact on the whole infrastructure. Some legal and privacy aspects >> are >> > still tbc. >> > >> > However no matter what we do it is unlikely that including the actual UA >> > code or any kind of real pwd / hash in a release is a good idea. It is >> quite >> > easy to manipulate that. >> > >> > Also the question rises if the OpenMeetings server is in a public >> network at >> > all. Just sending request blindly without knowing if they ever reach >> their >> > destination is kind of odd. >> > >> > It should be some subscribe mechanism where an OpenMeetings admin can >> > activate the error collecting. The activation could then subscribe and >> load >> > a hash that will auth that server for error collecting. >> > >> > If you put that activation in the installer with appropriate >> explenations I >> > think it has better chances to find a wider positive reaction in devs and >> > users. >> > >> > Maybe it would be enough to give some kind of more general feedback from >> > @legal and @infra and we can then in the OpenMeetings PMC create a more >> > detailed spec of that component. >> > >> > @legal: Do you have general constraints regarding error collecting ? >> > >> > @infra: What kind of advices can you give us? I guess some CGI scripts >> are >> > not that big deal. Is there any process who would review and activate / >> make >> > them executable? >> > >> > Thanks, >> > Sebastian >> > >> > Am 06.06.2013 19:38 schrieb "Alexei Fedotov" : >> > >> >> [added Shane for reputation issues] >> >> >> >> Hello, Infra and Legal folks, >> >> >> >> We ask you for advice on the automated error collection >> >> infrastructure. Any helpful ideas are appreciated. >> >> >> >> 1. Our users are tainted with iphones and other reliable and fancy >> >> staff. They start wanting openmeetings to work reliably. This makes us >> >> think of a global error collecting infrastructure to plan important >> >> bug fixes. Here is an example by Firefox [1]. >> >> >> >> We believe collecting user errors is generally ok if proper >> >> preparations are made. Is it generally possible to implement error >> >> collecting infrastructure as a part of Apache project? If not, we can >> >> try to do it as a commercial company, yet Firefox example shows a >> >> non-commercial org can be behind that error collection. >> >> >> >> 2. Could we use Google Analytics to store collected errors? The >> >> general Apache practice is to use Apache infrastructure. Google >> >> Analytics allows us storing 50 mln. events for free. The com
Re: Error collecting infrastructure for Openmeetings
Answering a personal request on general@ usage: 1) we discovered from our internal discussions that the topic is sensitive and want to be transparent with our intentions to collect user data; 2) we want to know more about Apache ways of addressing the problem; 3) we have not got any answer from legal@ and infra@ in this thread, thus I believe this may be more a cultural issue than a legal or technical issue; the incubator is a culture-spreading entity; 4) finally addressing general@ may be my mistake. I still will be grateful if anyone shares their experience on best practices on how to collect user errors to improve product quality. 10.06.2013 12:05 пользователь "Alexei Fedotov" написал: > [added general@ for vivid discussion] > > Hello Sebastian, > > I'm glad that the statement that this infrastructure is needed is not > questioned. > > We technically can use either CGI script, or existing Confluence API. > The intention for using Google Analytics is minimum effort. AFAIK, > many Apache projects do use Google Analytics already. > > The goal for the request is to avoid inventing a project-wide policy > where foundation-wide policy is needed. > > With best regards, Alexei > > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Mon, Jun 10, 2013 at 7:03 AM, seba.wag...@gmail.com > wrote: > > Hi Alexei, > > > > what about a simple CGI script that takes the input and send an email to > the > > mailing list? > > I think some more simple approach would do the same and does not have > such a > > deep impact on the whole infrastructure. Some legal and privacy aspects > are > > still tbc. > > > > However no matter what we do it is unlikely that including the actual UA > > code or any kind of real pwd / hash in a release is a good idea. It is > quite > > easy to manipulate that. > > > > Also the question rises if the OpenMeetings server is in a public > network at > > all. Just sending request blindly without knowing if they ever reach > their > > destination is kind of odd. > > > > It should be some subscribe mechanism where an OpenMeetings admin can > > activate the error collecting. The activation could then subscribe and > load > > a hash that will auth that server for error collecting. > > > > If you put that activation in the installer with appropriate > explenations I > > think it has better chances to find a wider positive reaction in devs and > > users. > > > > Maybe it would be enough to give some kind of more general feedback from > > @legal and @infra and we can then in the OpenMeetings PMC create a more > > detailed spec of that component. > > > > @legal: Do you have general constraints regarding error collecting ? > > > > @infra: What kind of advices can you give us? I guess some CGI scripts > are > > not that big deal. Is there any process who would review and activate / > make > > them executable? > > > > Thanks, > > Sebastian > > > > Am 06.06.2013 19:38 schrieb "Alexei Fedotov" : > > > >> [added Shane for reputation issues] > >> > >> Hello, Infra and Legal folks, > >> > >> We ask you for advice on the automated error collection > >> infrastructure. Any helpful ideas are appreciated. > >> > >> 1. Our users are tainted with iphones and other reliable and fancy > >> staff. They start wanting openmeetings to work reliably. This makes us > >> think of a global error collecting infrastructure to plan important > >> bug fixes. Here is an example by Firefox [1]. > >> > >> We believe collecting user errors is generally ok if proper > >> preparations are made. Is it generally possible to implement error > >> collecting infrastructure as a part of Apache project? If not, we can > >> try to do it as a commercial company, yet Firefox example shows a > >> non-commercial org can be behind that error collection. > >> > >> 2. Could we use Google Analytics to store collected errors? The > >> general Apache practice is to use Apache infrastructure. Google > >> Analytics allows us storing 50 mln. events for free. The comparable > >> thing won't be free for Apache for sure. > >> > >> Once can use JIRA, or Confluence via API, this will be a heavy load. > >> Are you ok with using third party for storing error & environment > >> messages and associated risks? > >> > >> The code we are talking about is below: > >
Re: Error collecting infrastructure for Openmeetings
[added general@ for vivid discussion]
Hello Sebastian,
I'm glad that the statement that this infrastructure is needed is not
questioned.
We technically can use either CGI script, or existing Confluence API.
The intention for using Google Analytics is minimum effort. AFAIK,
many Apache projects do use Google Analytics already.
The goal for the request is to avoid inventing a project-wide policy
where foundation-wide policy is needed.
With best regards, Alexei
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095
On Mon, Jun 10, 2013 at 7:03 AM, seba.wag...@gmail.com
wrote:
> Hi Alexei,
>
> what about a simple CGI script that takes the input and send an email to the
> mailing list?
> I think some more simple approach would do the same and does not have such a
> deep impact on the whole infrastructure. Some legal and privacy aspects are
> still tbc.
>
> However no matter what we do it is unlikely that including the actual UA
> code or any kind of real pwd / hash in a release is a good idea. It is quite
> easy to manipulate that.
>
> Also the question rises if the OpenMeetings server is in a public network at
> all. Just sending request blindly without knowing if they ever reach their
> destination is kind of odd.
>
> It should be some subscribe mechanism where an OpenMeetings admin can
> activate the error collecting. The activation could then subscribe and load
> a hash that will auth that server for error collecting.
>
> If you put that activation in the installer with appropriate explenations I
> think it has better chances to find a wider positive reaction in devs and
> users.
>
> Maybe it would be enough to give some kind of more general feedback from
> @legal and @infra and we can then in the OpenMeetings PMC create a more
> detailed spec of that component.
>
> @legal: Do you have general constraints regarding error collecting ?
>
> @infra: What kind of advices can you give us? I guess some CGI scripts are
> not that big deal. Is there any process who would review and activate / make
> them executable?
>
> Thanks,
> Sebastian
>
> Am 06.06.2013 19:38 schrieb "Alexei Fedotov" :
>
>> [added Shane for reputation issues]
>>
>> Hello, Infra and Legal folks,
>>
>> We ask you for advice on the automated error collection
>> infrastructure. Any helpful ideas are appreciated.
>>
>> 1. Our users are tainted with iphones and other reliable and fancy
>> staff. They start wanting openmeetings to work reliably. This makes us
>> think of a global error collecting infrastructure to plan important
>> bug fixes. Here is an example by Firefox [1].
>>
>> We believe collecting user errors is generally ok if proper
>> preparations are made. Is it generally possible to implement error
>> collecting infrastructure as a part of Apache project? If not, we can
>> try to do it as a commercial company, yet Firefox example shows a
>> non-commercial org can be behind that error collection.
>>
>> 2. Could we use Google Analytics to store collected errors? The
>> general Apache practice is to use Apache infrastructure. Google
>> Analytics allows us storing 50 mln. events for free. The comparable
>> thing won't be free for Apache for sure.
>>
>> Once can use JIRA, or Confluence via API, this will be a heavy load.
>> Are you ok with using third party for storing error & environment
>> messages and associated risks?
>>
>> The code we are talking about is below:
>>try {
>>_gaq = _gaq || [];
>>_gaq.push(['_setAccount', 'UA-13024987-1']); // PMC id
>>_gaq.push(['_trackPageview']);
>>_gaq.push(['_trackEvent', 'Openmeetings client error',
>> message, '', 0, true]);
>>} catch (exception) {
>>alert(exception);
>>}
>>
>> 3. Is it ok for PMC to share Google Analytics id? Should we use some
>> Apache Id instead?
>>
>> 4. Which preparations should be done to start this error collection
>> service in the next release?
>>
>> 4.1. Is it ok just to semi-silently mention in release notes, that
>> errors are automatically sent to the (Google) server right now?
>> 4.2. Or should we explicitly notify each new user that the errors are
>> now to be collected?
>> 4.3. If 4.2. holds, can we ask once per user at the beginning of his
>> session and remember if he agreed sharing error reports? Or should we
>> allow a user to review each error report each time the error is sent
>> (I
Re: Looking for a Champion
I usually point to the script & jenkins config SCM for that task.
06.06.2013 10:54 пользователь "Andy Van Den Heuvel" <
andy.vandenheu...@gmail.com> написал:
> Jenkins is used to build software projects. It's a continuous integration
> server.
> Tashlin will be more generic, used to build any set of tasks. Also business
> processes are possible.
>
> Example: Let's say I want a job to do a HTTP GET call every 5 minutes and
> show the results.
> In Jenkins, I'll probably create a free-style project, but it asks me for a
> SCM which makes no sense for this scenario.
> I think a lot of people today hack around the fact that Jenkins is a
> continuous integration server, because it is easy to use and to setup
> scheduling tasks.
>
> If we make a generic platform we can create a one stop shop for all
> schedeling tasks.
>
>
>
> On Thu, Jun 6, 2013 at 8:17 AM, Alexei Fedotov >wrote:
>
> > There is no requirement to be different to join, I just wonder
> > 06.06.2013 9:36 пользователь "Andy Van Den Heuvel" <
> > andy.vandenheu...@gmail.com> написал:
> >
> > > My apologies for causing confusion. Hopefully this will clear things
> up:
> > >
> > > Abstract
> > > Tashlin is a lightweight application for composing and executing batch
> > jobs
> > > via a web user interface.
> > >
> > > Brief Description
> > > Tashlin allows you to create and run batch jobs in a standalone
> > application
> > > for use cases where you want to automate a set of tasks. It will
> provide
> > a
> > > simple workflow
> > > which allows users to set up automation up in minutes with provided
> > plugins
> > > for common functionality. This differs from tools like Jenkins in that
> it
> > > can be used in a
> > > more generic way. Continuous integration is just one of the
> possibities.
> > > (E.g. integration with SCM or build automation is not a requirement).
> > > Other use cases are Monitoring, Backups, General Process Automation...
> > >
> > > The basic idea runs around these concepts:
> > > Recipe: Users will compose recipes. This is a template that will be
> > > executed by a Job
> > > Flow: A recipe contains 2 flows: a buildflow (= will stop when an
> > exception
> > > is thrown) and a feedbackflow (will run, even when exceptions are
> thrown
> > to
> > > notify interested parties)
> > > Step: A flow will execute a set of steps. Step logic will be provided
> > > through the use of plugins. Step configuration can be configured.
> > > Job: A job will be executed on a specific trigger. (on-demand,
> > > cron-based...) and can contain parameters.
> > > Parameter: A parameter is a value that can be used in a recipe so that
> > > recipes can be reused
> > >
> > > Because it has come up on this thread, I'll give continuous integration
> > as
> > > an example.
> > > Let's say I want to setup continuous integration for my maven project.
> > > I create a recipe with 2 build steps ('CheckOut From Subversion',
> 'Build
> > > With Maven') and 1 feedback step ('Email results').
> > > I create a job using this recipe and providing a parameter 'Goals' with
> > > value 'clean install'
> > > The 'Build With Maven' step will have ${GOALS} as a placeholder, the
> > value
> > > will be provided when executing the recipe (via EL).
> > > Now I can create a 2nd job providing a parameter 'Goals' with value
> > 'clean
> > > test -Dtest=*IntegrationTests' etc.
> > >
> > > Keep in mind that this is just a very basic example. The goal of the
> > > project is to bridge the gap for people who simply want to automate
> stuff
> > > and see the results of it.
> > > I think that a lot of people could benefit from this.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Wed, Jun 5, 2013 at 4:36 PM, Mohammad Nour El-Din <
> > > nour.moham...@gmail.com> wrote:
> > >
> > > > @Ate Yes I noticed but not enough information here in the thread to
> > make
> > > > anyone think to help or not and I would suggest for Andy just to
> > prepare
> > > an
> > > > abstract and brief description and share it here to see if someone is
> > > > interested rather than keep coming and going with q
Re: Looking for a Champion
There is no requirement to be different to join, I just wonder
06.06.2013 9:36 пользователь "Andy Van Den Heuvel" <
andy.vandenheu...@gmail.com> написал:
> My apologies for causing confusion. Hopefully this will clear things up:
>
> Abstract
> Tashlin is a lightweight application for composing and executing batch jobs
> via a web user interface.
>
> Brief Description
> Tashlin allows you to create and run batch jobs in a standalone application
> for use cases where you want to automate a set of tasks. It will provide a
> simple workflow
> which allows users to set up automation up in minutes with provided plugins
> for common functionality. This differs from tools like Jenkins in that it
> can be used in a
> more generic way. Continuous integration is just one of the possibities.
> (E.g. integration with SCM or build automation is not a requirement).
> Other use cases are Monitoring, Backups, General Process Automation...
>
> The basic idea runs around these concepts:
> Recipe: Users will compose recipes. This is a template that will be
> executed by a Job
> Flow: A recipe contains 2 flows: a buildflow (= will stop when an exception
> is thrown) and a feedbackflow (will run, even when exceptions are thrown to
> notify interested parties)
> Step: A flow will execute a set of steps. Step logic will be provided
> through the use of plugins. Step configuration can be configured.
> Job: A job will be executed on a specific trigger. (on-demand,
> cron-based...) and can contain parameters.
> Parameter: A parameter is a value that can be used in a recipe so that
> recipes can be reused
>
> Because it has come up on this thread, I'll give continuous integration as
> an example.
> Let's say I want to setup continuous integration for my maven project.
> I create a recipe with 2 build steps ('CheckOut From Subversion', 'Build
> With Maven') and 1 feedback step ('Email results').
> I create a job using this recipe and providing a parameter 'Goals' with
> value 'clean install'
> The 'Build With Maven' step will have ${GOALS} as a placeholder, the value
> will be provided when executing the recipe (via EL).
> Now I can create a 2nd job providing a parameter 'Goals' with value 'clean
> test -Dtest=*IntegrationTests' etc.
>
> Keep in mind that this is just a very basic example. The goal of the
> project is to bridge the gap for people who simply want to automate stuff
> and see the results of it.
> I think that a lot of people could benefit from this.
>
>
>
>
>
>
>
>
>
> On Wed, Jun 5, 2013 at 4:36 PM, Mohammad Nour El-Din <
> nour.moham...@gmail.com> wrote:
>
> > @Ate Yes I noticed but not enough information here in the thread to make
> > anyone think to help or not and I would suggest for Andy just to prepare
> an
> > abstract and brief description and share it here to see if someone is
> > interested rather than keep coming and going with question just to know
> > what the project is about rather than discussing whom will help and how
> >
> > @Andy: Would you please paste (or link) here an abstract and a brief
> > description what the project is about ? I would say have a look at [1]
> make
> > a similar one fill it in with as much as you can share that here to see
> if
> > someone is interested to be a Champion and take it from there
> >
> > [1] https://wiki.apache.org/incubator/StratosProposal
> >
> >
> > On Wed, Jun 5, 2013 at 4:29 PM, Ate Douma wrote:
> >
> > > On 06/05/2013 04:12 PM, Mohammad Nour El-Din wrote:
> > >
> > >> +1 @Marcel
> > >>
> > >> Any links for the draft proposal so people can assess if they can help
> > or
> > >> not ?
> > >>
> > >
> > > He is asking for help (Champion) to create such a draft :)
> > >
> > >
> > >
> > >>
> > >> On Wed, Jun 5, 2013 at 4:07 PM, Marcel Offermans <
> > >> marcel.offerm...@luminis.nl> wrote:
> > >>
> > >> I would never search for a generic job scheduling application in the
> > >>> Wicket project. I still don't know exactly what this new project is
> > >>> about,
> > >>> but the fact that it happens to use Wicket in itself is not enough to
> > >>> make
> > >>> it a Wicket subproject if you ask me.
> > >>>
> > >>> Greetings, Marcel
> > >>>
> > >>> On Jun 5, 2013, at 16:01 PM, Alexei Fedotov <
> alexei.fedo...@gmail.com>
> > >>>
Re: Looking for a Champion
So what makes it different from jenkins?
06.06.2013 9:36 пользователь "Andy Van Den Heuvel" <
andy.vandenheu...@gmail.com> написал:
> My apologies for causing confusion. Hopefully this will clear things up:
>
> Abstract
> Tashlin is a lightweight application for composing and executing batch jobs
> via a web user interface.
>
> Brief Description
> Tashlin allows you to create and run batch jobs in a standalone application
> for use cases where you want to automate a set of tasks. It will provide a
> simple workflow
> which allows users to set up automation up in minutes with provided plugins
> for common functionality. This differs from tools like Jenkins in that it
> can be used in a
> more generic way. Continuous integration is just one of the possibities.
> (E.g. integration with SCM or build automation is not a requirement).
> Other use cases are Monitoring, Backups, General Process Automation...
>
> The basic idea runs around these concepts:
> Recipe: Users will compose recipes. This is a template that will be
> executed by a Job
> Flow: A recipe contains 2 flows: a buildflow (= will stop when an exception
> is thrown) and a feedbackflow (will run, even when exceptions are thrown to
> notify interested parties)
> Step: A flow will execute a set of steps. Step logic will be provided
> through the use of plugins. Step configuration can be configured.
> Job: A job will be executed on a specific trigger. (on-demand,
> cron-based...) and can contain parameters.
> Parameter: A parameter is a value that can be used in a recipe so that
> recipes can be reused
>
> Because it has come up on this thread, I'll give continuous integration as
> an example.
> Let's say I want to setup continuous integration for my maven project.
> I create a recipe with 2 build steps ('CheckOut From Subversion', 'Build
> With Maven') and 1 feedback step ('Email results').
> I create a job using this recipe and providing a parameter 'Goals' with
> value 'clean install'
> The 'Build With Maven' step will have ${GOALS} as a placeholder, the value
> will be provided when executing the recipe (via EL).
> Now I can create a 2nd job providing a parameter 'Goals' with value 'clean
> test -Dtest=*IntegrationTests' etc.
>
> Keep in mind that this is just a very basic example. The goal of the
> project is to bridge the gap for people who simply want to automate stuff
> and see the results of it.
> I think that a lot of people could benefit from this.
>
>
>
>
>
>
>
>
>
> On Wed, Jun 5, 2013 at 4:36 PM, Mohammad Nour El-Din <
> nour.moham...@gmail.com> wrote:
>
> > @Ate Yes I noticed but not enough information here in the thread to make
> > anyone think to help or not and I would suggest for Andy just to prepare
> an
> > abstract and brief description and share it here to see if someone is
> > interested rather than keep coming and going with question just to know
> > what the project is about rather than discussing whom will help and how
> >
> > @Andy: Would you please paste (or link) here an abstract and a brief
> > description what the project is about ? I would say have a look at [1]
> make
> > a similar one fill it in with as much as you can share that here to see
> if
> > someone is interested to be a Champion and take it from there
> >
> > [1] https://wiki.apache.org/incubator/StratosProposal
> >
> >
> > On Wed, Jun 5, 2013 at 4:29 PM, Ate Douma wrote:
> >
> > > On 06/05/2013 04:12 PM, Mohammad Nour El-Din wrote:
> > >
> > >> +1 @Marcel
> > >>
> > >> Any links for the draft proposal so people can assess if they can help
> > or
> > >> not ?
> > >>
> > >
> > > He is asking for help (Champion) to create such a draft :)
> > >
> > >
> > >
> > >>
> > >> On Wed, Jun 5, 2013 at 4:07 PM, Marcel Offermans <
> > >> marcel.offerm...@luminis.nl> wrote:
> > >>
> > >> I would never search for a generic job scheduling application in the
> > >>> Wicket project. I still don't know exactly what this new project is
> > >>> about,
> > >>> but the fact that it happens to use Wicket in itself is not enough to
> > >>> make
> > >>> it a Wicket subproject if you ask me.
> > >>>
> > >>> Greetings, Marcel
> > >>>
> > >>> On Jun 5, 2013, at 16:01 PM, Alexei Fedotov <
> alexei.fedo...@gmail.com>
> > >>> wrote:
&g
Re: Looking for a Champion
Could it be a part of Apache Wicket? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 5, 2013 at 5:33 PM, Andy Van Den Heuvel wrote: > Hey Alexei, > > Yes, it does. > > On Wed, Jun 5, 2013 at 3:20 PM, Alexei Fedotov > wrote: > >> Andy, >> It uses Apache Wicket, doesn't it? >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> On Wed, Jun 5, 2013 at 4:42 PM, Andy Van Den Heuvel >> wrote: >> > Jenkins is a continuous integration server, it provides integration with >> > SCM, Build Automation, Testing... >> > This proposal is for a multi-purpose tool, providing support for >> > Monitoring, Backup's,Process Automation, (also Continuous Integration >> > though) >> > The architecture is very different. >> > >> > The idea behind this has come up of using Hudson/Jenkins for several >> years. >> > >> > >> > On Wed, Jun 5, 2013 at 2:25 PM, Simon Lucy wrote: >> > >> >> Andy Van Den Heuvel wrote: >> >> >> >> I'm looking for a Champion to help me setup a proposal. >> >>> The project is a pluggable all-round job scheduling application. >> >>> >> >> >> >> >> >> Not to be a killjoy but how is it different to Hudson/Jenkins? >> >> >> >> >> >> S >> >> >> >> >> >>> Can somebody help me? >> >>> >> >>> Thanks for your consideration. >> >>> >> >>> >> >> >> >> >> >> >> --**--**- >> >> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org< >> general-unsubscr...@incubator.apache.org> >> >> For additional commands, e-mail: general-help@incubator.apache.**org< >> general-h...@incubator.apache.org> >> >> >> >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Looking for a Champion
Andy, It uses Apache Wicket, doesn't it? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 5, 2013 at 4:42 PM, Andy Van Den Heuvel wrote: > Jenkins is a continuous integration server, it provides integration with > SCM, Build Automation, Testing... > This proposal is for a multi-purpose tool, providing support for > Monitoring, Backup's,Process Automation, (also Continuous Integration > though) > The architecture is very different. > > The idea behind this has come up of using Hudson/Jenkins for several years. > > > On Wed, Jun 5, 2013 at 2:25 PM, Simon Lucy wrote: > >> Andy Van Den Heuvel wrote: >> >> I'm looking for a Champion to help me setup a proposal. >>> The project is a pluggable all-round job scheduling application. >>> >> >> >> Not to be a killjoy but how is it different to Hudson/Jenkins? >> >> >> S >> >> >>> Can somebody help me? >>> >>> Thanks for your consideration. >>> >>> >> >> >> --**--**- >> To unsubscribe, e-mail: >> general-unsubscribe@incubator.**apache.org >> For additional commands, e-mail: >> general-help@incubator.apache.**org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: AIFTTT, message connector
Sorry for telling, the proposal does not match proposal standards, and contains invalid information in competitors section. 24.05.2013 1:57 пользователь "james pruett" написал: > Hi all, > > I am looking for a Champion. > > https://wiki.apache.org/incubator/jamespruett > > I know all-you-all are busy, > so please know that I appreciate your time! > > > -Jim Pruett >
Re: If I were king of the forest
If I'm a king of a dream forest... I think how to improve attractiveness of free software to contributors. It is no longer a cool trend. How about find some resources (maybe internal ones) to make people strengthen the community by creative reasons? Business reasons are short living (compared to creative reasons) and unpedictable. There is a long and unproductive discussion on how to make foss more attractive to business, improving it won't not hurt either. Maybe attracting some educational resources / collaborating with them would help. This 100% success GSoC rate makes us turning some students away from Apache, and they should have some place to stay and learn and grow. More new blood will create more productive and successful and caring mentors. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, May 8, 2013 at 10:44 PM, Chip Childers wrote: > On Wed, May 08, 2013 at 11:40:59AM -0700, Alan Cabrera wrote: > > > > On May 8, 2013, at 11:36 AM, Alan Cabrera wrote: > > > > > > > > On May 8, 2013, at 11:20 AM, Chip Childers > wrote: > > > > > >> On Wed, May 08, 2013 at 11:00:14AM -0700, Alan Cabrera wrote: > > >>> > > >>> On May 8, 2013, at 10:22 AM, Eric Johnson wrote: > > >>>> One last suggested refinement: > > >>>> > > >>>> At least two mentors, but perhaps not allow more than three, where > the third is generally a backup for the others in a transition period, such > as one of the mentors looking to shed their responsibilities. One point > that has come out of the discussion has been a lack of clear > responsibility. Adding more mentors dilutes that responsibility. Two allows > one as backup for the other. > > >>> > > >>> Yes, this was what I was thinking as well. Two active mentors, > maybe one or two inactive ones but since they officially declared > themselves inactive the active mentor know not to assume anything of them. > > >> > > >> I may be incorrect in my understanding of the official ASF policy here > > >> [1], but WRT a release, doesn't it require at least 3 +1 votes of the > > >> appropriate PMC (in the case of podlings, the IPMC)? If the mentors > > >> were limited to 2 within the podlings, then would that leave all > podling > > >> in a position of having to get a third +1 from the IPMC? > > > > > > We're the IPMC, we can change the rules if we need to. > > > > Oh, I see this is an ASF rule. Maybe we should have three active > mentors? > > That was exactly my point, yes. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Identifying and removing inactive mentors
At Openmeetings we spent some time looking for mentors, and every mentor really helped at some point. Upayavira's letter reminds me to say thanks to @Andrus, @Egor and @Ross. 24.03.2013 21:21 пользователь "Upayavira" написал: > I have mentored at least two podlings where I am the only active mentor. > One had six mentors on the list, but I was the only one actually paying > any attention. We're not talking about occasional absenteeism, we're > talking not having participated since the beginning of the podling. One > podling I note two of the mentors don't even appear to be subscribed to > the dev list. > > I didn't sign up to being the *only* mentor. I'm not convinced that > having only me as a mentor is best for the project. Fortunately, there's > another ASF member who watches and chimes in, which I really appreciate. > > So sure, let's not force out people who are having a bad month or > something, but surely we should only be listing as mentors those that > are actually paying some attention to the podling? > > Upayavira > > On Sat, Mar 23, 2013, at 11:59 PM, Ross Gardler wrote: > > I'd suggest a different approach, the motivation for this suggestion is > > that I don't believe having inactive mentors is a problem if there is an > > active one available. Everyone gets busy occasionally, should we really > > be > > kicking them off a podling when they have already expressed interest? At > > next months report they might be the one who is active. They may have > > been > > active in the two months between reports. Etc. > > > > In my opinion there is only a problem if nobody is looking or if the > > podling community feels they are not getting the support they need. > > > > I therefore suggest reaching out to the podling rather than passing > > judgement on the mentors. > > > > Ross > > > > > > > > On 23 March 2013 10:23, Christian Grobmeier wrote: > > > > > Hello, > > > > > > I know at least one podling where 75% of the mentors is awol. We don't > > > have an oversight on the "awol"-state, just the shepherds do know for > > > the projects they shepherd. > > > > > > We have status reports, which should be signed by all mentors. I > > > believe reading, verifying and signing a podling report is not so much > > > work and it is the least a mentor should do. > > > > > > My proposal: > > > > > > We should contact all Mentors who have not signed a report 2 times in > > > a row if they are still committed to their role. If we get no response > > > within a week, we should remove them as a mentor from podlings.xml (or > > > give them an inactive flag). With this information clutch can report > > > projects which do not have sufficient mentors. > > > > > > Thoughts? > > > > > > Christian > > > > > > -- > > > http://www.grobmeier.de > > > https://www.timeandbill.de > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > -- > > Ross Gardler (@rgardler) > > Programme Leader (Open Development) > > OpenDirective http://opendirective.com > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator
+1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Feb 5, 2013 at 9:59 PM, Ted Dunning wrote: > +1 (binding) > > On Tue, Feb 5, 2013 at 8:24 AM, Andrew Hart wrote: > > > +1 (binding) > > > > -Andrew > > > > > > > > On 2/5/13 8:18 AM, Mattmann, Chris A (388J) wrote: > > > >> Hi Folks, > >> > >> OK, now that discussion has settled down, I'd like to call a VOTE for > >> acceptance of Apache Open Climate Workbench into the Incubator. > >> I'll leave the VOTE open the rest of the week and close it out next > >> Monday, February 11th early am PT. > >> > >> [ ] +1 Accept Apache Open Climate Workbench into the Incubator > >> [ ] +0 Don't care. > >> [ ] -1 Don't accept Apache Open Climate Workbench into the Incubator > >> because... > >> > >> Full proposal is pasted at the bottom of this email. Only VOTEs from > >> Incubator PMC members are binding, but all are welcome to express their > >> thoughts. > >> > >> Thank you! > >> > >> Cheers, > >> Chris > >> > >> P.S. Here's my +1 (binding) > >> > >> - > >> = Apache Open Climate Workbench, tool for scalable comparison of remote > >> sensing observations to climate model outputs, regionally and globally. > = > >> === Abstract === > >> The Apache Open Climate Workbench proposal desires to contribute an > >> existing community of software related to the analysis and evaluation of > >> climate models, and related to the use of remote sensing data in that > >> process. > >> > >> Specifically, we will bring a fundamental software toolkit for analysis > >> and evaluation of climate model output against remote sensing data. The > >> toolkit is called the [[http://rcmes.jpl.nasa.gov|**Regional Climate > >> Model > >> Evaluation System (RCMES)]]. RCMES provides two fundamental components > for > >> the easy, intuitive comparison of climate model output against remote > >> sensing data. The first component called RCMED (for "Regional Climate > >> Model Evaluation Database") is a scalable cloud database that decimates > >> remote sensing data and renalysis data related to climate using Apache > >> OODT extractors, Apache Tika, etc. These transformations make > >> traditionally heterogeneous upstream remote sensing data and climate > model > >> output homogeneous and unify them into a data point model of the form > >> (lat, lng, time, value, height) on a per parameter basis. Latitude (lat) > >> and Longitude (lng) are in WGS84 format, but can be reformatted on the > >> fly. time is in ISO 8601 format, a string sortable format independent of > >> underlying store. value carries with it units, related to interpretation > >> and height allows for different values for different atmospheric > vertical > >> levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop > >> and Apache Hive, along with hooks to PostGIS and MySQL (traditional > >> relational databases). The second component of the system, RCMET (for > >> "Regional Climate Model Evaluation Toolkit") provides facilities for > >> connecting to RCMED, dynamically obtaining remote sensing data for a > >> space/time region of interest, grabbing associated model output (that > the > >> user brings, or from the Earth System Grid Federation) of the same form, > >> and then regridding the remote sensing data to be on the model output > >> grid, or the model output to be on the remote sensing data grid. The > >> regridded data spatially is then temporally regridded using techniques > >> including seasonal cycle compositing (e.g., all summer months, all > >> Januaries, etc.), or by daily, monthly, etc. The uniform model output > and > >> remote sensing data are then analyzed using pluggable metrics, e.g., > >> Probability Distribution Functions (PDFs), Root Mean Squared Error > (RMSE), > >> Bias, and other (possibly user-defined) techniques, computing an > analyzed > >> comparison or evaluation. This evaluation is then visualized by plugging > >> in to the NCAR NCL library for producing static plots (histograms, time > >> series, etc.) > >> > >> We also have performed a great deal of work in packaging RCMES to make > the > >> system easy to deploy. We have working Virtual Machi
Re: Icons for the toolbar
[added general@ list] It seems we need to provide required attribution in some form, e.g. in the LICENSE file On Fri, Dec 28, 2012 at 4:03 PM, Artyom Horuzhenko wrote: > Hello everybody! > Is the license for this http://www.fatcow.com/free-icons set of icons > compatible with Openmeetings? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenMeetings suitable name search never closed?
Hello Shane, We discussed name change at the beginning of incubation and decided to keep Opemeetings. [and yes, this is a bit of a duplicate letter] -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Dec 19, 2012 at 10:21 PM, Shane Curcuru wrote: > (Note the two mailing lists have different archive policies) > > Did the IPMC and the Apache OpenMeetings podling ever finish their name > search, or bring it to trademarks@? I just ask since they're up for > potential graduation today. > > I see the JIRA, but not any messages to trademarks@ asking for final OK - > or, even anyone else's comments (although I expect some comments may be on > their private list). > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-7 > > 30 second read of their JIRA shows it's a fine name for them, but I want to > make sure we *ensure* this step is finished for all podlings before > graduation. > > - Shane > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Marmotta into the incubator
+1 On Thu, Nov 29, 2012 at 6:35 PM, Dave Fisher wrote: > +1 binding > > Sent from my iPhone > > On Nov 29, 2012, at 6:28 AM, Andy Seaborne wrote: > >> Hi there, >> >> Following the discussion thread, here is the formal vote on the Marmotta >> proposal: >> >> Please cast your votes on whether to accept the Apache Marmotta proposal: >> >> [ ] +1 Accept Marmotta into the Apache Incubator >> [ ] +0 Indifferent to the acceptance of Marmotta >> [ ] -1 Do not accept the Marmotta proposal because ... >> >> The vote will be open until at least 23:59 Sunday 2nd December UTC >> (which is three full days from midnight tonight) >> >>Andy >> >> http://wiki.apache.org/incubator/MarmottaProposal >> >> --- >> >> == Abstract >> >> Marmotta is a Linked Data platform for industry-strength installations. >> >> == Proposal >> >> The goal of Apache Marmotta is to provide an open implementation of a Linked >> Data Platform that can be used, extended, and deployed easily by >> organizations who want to publish Linked Data or build custom applications >> on Linked Data. >> >> The phrase "Linked Data" is used here idiosyncratically to refer to a data >> integration paradigm across the Web. The term was coined by Tim Berners-Lee >> in 2006, and it is based on four very simple principles which basically >> describe recommended best practices for exposing, sharing, and connecting >> pieces of data, information, and knowledge on the Semantic Web using URIs >> and the RDF technology stack. Therefore Linked Data is about using the Web >> to connect related data that wasn't previously linked, or using the Web to >> lower the barriers to linking data currently linked using other methods. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to grow podling communities
Let me note, that one can use Apache software (Openmeetings Incubating) to run video conferences simply by using the following URL http://demo.dataved.ru/public/?firstname=Ross&lastname=Gardler -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Nov 28, 2012 at 1:03 AM, Ross Gardler wrote: > Forgot a couple for the list... > > Lucy is running a book club - they meet on Google Hangouts and discuss how an > appropriate book chapter might apply to their project. This was recently > reported in their board report and early feedback is very positive. > > OpenOffice are building a "course" for new community members. The goal is to > guide people through the learning process around contribution with regular > check-ins with the community lists where the community works hard to > congratulate and welcome. > > Ross > > > >> -Original Message- >> From: Luciano Resende [mailto:luckbr1...@gmail.com] >> Sent: 27 November 2012 17:40 >> To: general@incubator.apache.org >> Subject: Re: How to grow podling communities >> >> On Mon, Nov 26, 2012 at 3:50 PM, Ross Gardler >> wrote: >> >> > Growing community is about "getting the message out there". There has >> > to be someone in the project who wants to do that. Some techniques are: >> > >> > - press >> > - community events >> > - mentoring (that is mentoring of potential new committers) >> > - fast turnaround on patch reviews >> > - regular releases >> > - decent website >> > - tutorials >> > - screencasts >> > - public discussion (even with self while no community exists) >> > >> > Developing code for one's own use is all well can good but it does not >> > build community and trying to build community doesn't, in the short >> > term, write code. It's a catch-22. >> > >> > Personally I have no problem with a podling having low activity. A >> > single developer doing their thing in the incubator is not going to hurt >> anyone. >> > What I'm concerned about is a podling that is not doing any of the >> > above community development activities or, even worse, is ignoring >> > potential contributors. >> > >> > I don't think it is the responsibility of ComDev to do this, although >> > one could argue ComDev should be documenting these techniques in ways >> > useful to mentors. I don't think it is the job of mentors (or the >> > IPMC) to do this either. It is entirely the PPMC responsibility. In my >> > opinion. >> > >> > >> This is exactly things that I want to bring up to the podling attentions, a >> list of >> things that they could do to try to build/increase the community. >> Once we collect a list of them, we can document it and use it as suggestions >> for struggling podlings. >> >> My main goal is to avoid mentors coming to a podling and telling them its >> time to retire, but pointing them to resources that can help them get out of >> the retirement situation. >> >> The IPMC and ComDev should always be here to help, documenting the >> things that have worked in the past, and facilitating access to resources >> that >> can help the podlings. >> >> -- >> Luciano Resende >> http://people.apache.org/~lresende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Chukwa from incubation
Let me rephrase the question. Could the actual reason behind Chukwa retirement be related to the fact, that there exist Flume and Kafka which gives users same opportunites to manage distributed systems? I better understand this before trying to spread the word about joinging Chukwa community. If this is the case, could it be that there are ways to mergre projects somehow, e.g. provide Chukwa API on the top of Flume or Kafka? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 27, 2012 at 6:23 PM, Alexei Fedotov wrote: > Hello guys, > I want to understand Chukwa community building strategy better. Are > there any insights why companies which use Hadoop (in Moscow those > include Deutche Bank, Yandex, Rambler and Microsoft) do not crowd > around or stay in line to get a chance to use Chukwa? > > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Tue, Nov 27, 2012 at 3:55 PM, ant elder wrote: >> On Tue, Nov 27, 2012 at 11:48 AM, Benson Margulies >> wrote: >> >>> One interesting point about consensus decision-making process is the >>> need to define the starting point. The process assumes that there is a >>> clear 'status quo', and that a consensus is required to change it. >>> This may not always be the appropriate way to think about retiring a >>> podling, but it's clearly the way we're thinking about this one. >>> >>> Does anyone else feel that this could have benefitted from a [DISCUSS] >>> before the [VOTE]. >>> >>> At the bottom line, if there are new mentors to be fully responsible, >>> I think it's reasonable to continue; however, I don't want to have >>> exactly the same conversation in N months. Would the new mentors like >>> to propose a time limit, and is the group willing to subscribe to the >>> notion that, if after that time, the new mentors have the same report >>> as the old mentors, we're at the end? >>> >>> >> Could we maybe include a time limit next month with the credible plan to >> give new mentors a little time to get up to speed with the project? >> >>...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Chukwa from incubation
Hello guys, I want to understand Chukwa community building strategy better. Are there any insights why companies which use Hadoop (in Moscow those include Deutche Bank, Yandex, Rambler and Microsoft) do not crowd around or stay in line to get a chance to use Chukwa? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 27, 2012 at 3:55 PM, ant elder wrote: > On Tue, Nov 27, 2012 at 11:48 AM, Benson Margulies > wrote: > >> One interesting point about consensus decision-making process is the >> need to define the starting point. The process assumes that there is a >> clear 'status quo', and that a consensus is required to change it. >> This may not always be the appropriate way to think about retiring a >> podling, but it's clearly the way we're thinking about this one. >> >> Does anyone else feel that this could have benefitted from a [DISCUSS] >> before the [VOTE]. >> >> At the bottom line, if there are new mentors to be fully responsible, >> I think it's reasonable to continue; however, I don't want to have >> exactly the same conversation in N months. Would the new mentors like >> to propose a time limit, and is the group willing to subscribe to the >> notion that, if after that time, the new mentors have the same report >> as the old mentors, we're at the end? >> >> > Could we maybe include a time limit next month with the credible plan to > give new mentors a little time to get up to speed with the project? > >...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What constitute a successful project?
I wonder which steps were taken by mentors, community and pmc to foster a community. I want to learn something from this case. Thanks. 26.11.2012 18:55 пользователь "Alan Cabrera" написал: > > On Nov 25, 2012, at 7:33 PM, Eric Yang wrote: > > > Hi IPMC, > > > > For the past two years, Chukwa has been labelled as non-active project by > > mentors, and has been put on votes for retiring this project by mentor > and > > IPMC. > > In this year's stats, Chukwa has more activities in comparison to Apache > > Wink in both mailing list traffic and resolved jiras. Yet Chukwa has > been > > voted to discontinue by mentors, but Wink is voted to graduate by the > same > > mentor. Here are the number of mails showed up in dev list between Apache > > Chukwa and Apache Wink: > > Since I am the mentor that started the retirement vote on the podling I > will explain my perspective. > > What it comes down to is actual diverse activity. For me, the > overwhelming bulk of the work for Chukwa was being done by one person. > While looking at the raw numbers the two projects seem similar, if you > scrub the threads where we discuss whether or not to retire Chukwa and also > look at who's doing the actual work, it seems to me that the two projects > are not exactly the same. > > > Regards, > Alan > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Sub-projects - when are they acceptable? (was Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany)
This is good point of view. I think one may also take a user cases and product distribution perspectives into account. For example, when both projects naturally come in one binary release, this may be feasible to have them joined. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 20, 2012 at 3:28 PM, Ross Gardler wrote: > On 20 November 2012 11:18, Benson Margulies wrote: > > On Tue, Nov 20, 2012 at 3:01 AM, Bertrand Delacretaz > > wrote: > >> On Tue, Nov 20, 2012 at 6:41 AM, Luciano Resende > wrote: > >>> ...Nuvem has a great synergy with Apache Tuscany, and after > >>> discussion between the two projects, we are seeking IPMC approval to > allow > >>> graduation of Apache Nuvem as a sub-project under Apache Tuscany > >> > >> Can you clarify what this means? Do all members of the Nuvem PPMC > >> become Tuscany PMC members? > > > > Bertrand, this is a great opportunity to clarify the board's attitude > > toward 'subprojects'. Ever since the campaign to dismantle umbrellas, > > I've been confused about what structures the board would find > > reasonable. > > I don't speak for the board, but my opinion is that if a sub-project > is OK as long as it is actively managed by the same PMC as the parent > project. > > Where I start to get worried is when a sub-project takes on a life of > its own and significant portions of the parent PMC are not interested > in the sub-project and thus fail to provide appropriate oversight. The > more sub-projects there are in a project the more likely this is to > happen. > > I'm interested to hear if this is also the opinion of others and thus > I've changed the subject. In terms of Nuvem I'm interested in the > answer to Bertrands question. > > Ross > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release JSPWiki version 2.9.0-incubating
Hello Juan, According to your answers, I suggest the following (IMHO, not binding anyway) 1) remove licenses for files which are not included into the source release (this actually means the source release license file should be different from the binary release one); 2) remove the second copy for any LICENSE (the one under doc/); 3) for the binary release, make the artifact list complete, so it would contain the reference to Mozilla licensed file and other missed entities. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Nov 15, 2012 at 4:11 AM, Juan Pablo Santos Rodríguez wrote: > Hi Alexei, > > activation-1.1.jar et al are downloaded as part of the build. They're not > included in the source because that's contrary to the Apache principles. > That was noted in our July report (and tracked at [#1]). > > Regarding the LICENSE / doc/LICENSE.* files: initially, we kept each > license in a separate file (doc/LICENSE.*), while ./LICENSE contained only > the AL. This raised some concerns, noted on our 3rd RC vote [#2], which led > to ./LICENSE file also having verbatim copies of all used licenses. As for > the Mozilla license, it's in the ./LICENSE file (line 1090 onwards), we use > custom-rhino in some of the tests, which uses that license. > > > cheers, > juan pablo > > p.d.: your vote being..? O:-D > > [#1]: > https://issues.apache.org/jira/browse/JSPWIKI-738<https://issues.apache.org/jira/browse/JSPWIKI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419501#comment-13419501> > [#2]: > http://mail-archives.apache.org/mod_mbox/incubator-general/201210.mbox/%3c80852492-ac42-4f8d-82ca-760eefccd...@oracle.com%3E > > On Wed, Nov 14, 2012 at 4:36 PM, Alexei Fedotov > wrote: > >> Great work! >> >> I've got the following questions concerning the ./LICENSE file for the >> source release: >> >> There is a list of jar files in the ./LICENSE file of the following form: >> activation-1.1.jar doc/LICENSE.cddl >> >> What is the point of including licenses for files which are absent in >> the source release? >> Why license texts appear twice (both in the ./LICENSE file and ./doc/ >> folder)? That provides more place for possible errors. >> I believe the list is good to exist in the ./LICENSE file for the >> binary release. Why it does not mention all licenses from the source >> release ./LICENSE file, e.g. Mozilla license? >> >> How to understand "Copyright (c) " in MIT >> license. The template style cannot appear in final version of the >> LICENSE. Also, IMHO, copyright attribution does not belong to the >> license (unless you use a copyrighted license). >> >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> On Wed, Nov 14, 2012 at 5:03 AM, Florian Holeczek >> wrote: >> > Hi all, >> > >> > I'd like to start a vote on an incubator release for Apache JSPWiki, >> version >> > 2.9.0-incubating. >> > >> > Apache JSPWiki (incubating) is a leading open source WikiWiki engine, >> > feature-rich and built around standard J2EE components (Java, servlets, >> > JSP). >> > >> > >> > A vote was held on the developer mailing list [1] and passed with 9 "+1"s >> > [2], two of them from our mentors. >> > >> > >> > This release candidate fixes the following issues: >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732&version=12319521 >> > >> > The tag to be voted upon: >> > >> https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating >> > >> > Source and binary files: >> > http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ >> > >> > Checksums: >> > >> > JSPWiki-2.9.0-incubating-src.zip >> > MD5:287e75857b03b41dca769211591c6144 >> > SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 >> > SHA512: >> > >> 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a >> > >> > JSPWiki-2.9.0-incubating-bin.zip >> > MD5:7e774dc46c112ca895aad60fb607dc60 >> > SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 >> > SHA512: >> > >> 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd132
Re: [VOTE] Release JSPWiki version 2.9.0-incubating
Great work! I've got the following questions concerning the ./LICENSE file for the source release: There is a list of jar files in the ./LICENSE file of the following form: activation-1.1.jar doc/LICENSE.cddl What is the point of including licenses for files which are absent in the source release? Why license texts appear twice (both in the ./LICENSE file and ./doc/ folder)? That provides more place for possible errors. I believe the list is good to exist in the ./LICENSE file for the binary release. Why it does not mention all licenses from the source release ./LICENSE file, e.g. Mozilla license? How to understand "Copyright (c) " in MIT license. The template style cannot appear in final version of the LICENSE. Also, IMHO, copyright attribution does not belong to the license (unless you use a copyrighted license). -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Nov 14, 2012 at 5:03 AM, Florian Holeczek wrote: > Hi all, > > I'd like to start a vote on an incubator release for Apache JSPWiki, version > 2.9.0-incubating. > > Apache JSPWiki (incubating) is a leading open source WikiWiki engine, > feature-rich and built around standard J2EE components (Java, servlets, > JSP). > > > A vote was held on the developer mailing list [1] and passed with 9 "+1"s > [2], two of them from our mentors. > > > This release candidate fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732&version=12319521 > > The tag to be voted upon: > https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating > > Source and binary files: > http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ > > Checksums: > > JSPWiki-2.9.0-incubating-src.zip > MD5:287e75857b03b41dca769211591c6144 > SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 > SHA512: > 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a > > JSPWiki-2.9.0-incubating-bin.zip > MD5:7e774dc46c112ca895aad60fb607dc60 > SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 > SHA512: > 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4 > > JSPWiki's KEYS file containing PGP keys we use to sign the release: > http://www.apache.org/dist/incubator/jspwiki/KEYS > > For convenience, this directory includes a binary distribution and a RAT > report on the cited tag. > You can manually generate the RAT report from a clean source by running the > "rat-report" Ant target. > > > Please vote: > > [ ] +1 approve, release Apache JSPWiki 2.9.0-incubating > [ ] +0 no opinion > [ ] -1 disapprove (and giving a reason) > > > The vote will be open for at least 72 hours. > > Best regards > Florian Holeczek > > [1] http://markmail.org/message/gksvnjnru2nhhenf > [2] http://markmail.org/message/mht24dwvpmm7xgft > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
Great, thanks. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Mon, Nov 5, 2012 at 6:28 PM, Om wrote: > Yes, we have addressed that issue. We reinstated the original license text > for the headers in MD5Stream.as and IntUtil.as > > Thanks, > Om > On Nov 5, 2012 2:35 AM, "Alexei Fedotov" wrote: > >> Hello Om, >> >> Alex wrote, >> > After more digging, I think the issue is that IntUtil.as shouldn't have >> an Apache header. It comes from external projects under Modified BSD. >> >> Do you plan to fix this? >> >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> On Sat, Nov 3, 2012 at 1:50 AM, Om wrote: >> > For the record, these are issues we are fixing in the next RC: >> > >> > 1. incorrect headers in MD5Stream.as and IntUtil.as >> > 2. incorrect path to MD5Stream.as and IntUtil.as in the LICENSE file >> > 3. incorrect license for the open_sans fonts in the LICENSE file >> > 4. incorrect path to the open_sans fonts in the LICENSE file >> > 5. in the distro the NOTICE, LICENSE and DISCLAIMER files are at root >> but in >> > svn they are under the installer directory - we pulled them up to root >> when >> > we packaged everything. >> > >> > Please let us know if anything else needs to be addressed. >> > >> > Thanks, >> > Om >> > >> > On Fri, Nov 2, 2012 at 2:43 PM, Om wrote: >> > >> >> In light of all the issues uncovered, I am closing this vote thread. We >> >> are working on fixing the issues and will be back with a new vote >> thread. >> >> >> >> Thanks, >> >> Om >> >> >> >> >> >> On Fri, Nov 2, 2012 at 4:09 AM, Bertrand Delacretaz < >> >> bdelacre...@apache.org> wrote: >> >> >> >>> On Fri, Nov 2, 2012 at 11:55 AM, sebb wrote: >> >>> > ...If I were the RM, I would add the missing EOLs at EOF and create >> >>> another RC >> >>> >> >>> I see your point about the distributed files not being *binary >> >>> identical* to the svn tag, but I personally consider source files to >> >>> be identical if diff -b (i.e. ignore changes in the amount of >> >>> whitespace) says they are. >> >>> >> >>> So, in this case, I definitely don't see this as a blocker, just >> >>> something to fix for a future release. >> >>> >> >>> -Bertrand >> >>> >> >>> - >> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> >>> For additional commands, e-mail: general-h...@incubator.apache.org >> >>> >> >>> >> >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
Hello Om, Alex wrote, > After more digging, I think the issue is that IntUtil.as shouldn't have an > Apache header. It comes from external projects under Modified BSD. Do you plan to fix this? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sat, Nov 3, 2012 at 1:50 AM, Om wrote: > For the record, these are issues we are fixing in the next RC: > > 1. incorrect headers in MD5Stream.as and IntUtil.as > 2. incorrect path to MD5Stream.as and IntUtil.as in the LICENSE file > 3. incorrect license for the open_sans fonts in the LICENSE file > 4. incorrect path to the open_sans fonts in the LICENSE file > 5. in the distro the NOTICE, LICENSE and DISCLAIMER files are at root but in > svn they are under the installer directory - we pulled them up to root when > we packaged everything. > > Please let us know if anything else needs to be addressed. > > Thanks, > Om > > On Fri, Nov 2, 2012 at 2:43 PM, Om wrote: > >> In light of all the issues uncovered, I am closing this vote thread. We >> are working on fixing the issues and will be back with a new vote thread. >> >> Thanks, >> Om >> >> >> On Fri, Nov 2, 2012 at 4:09 AM, Bertrand Delacretaz < >> bdelacre...@apache.org> wrote: >> >>> On Fri, Nov 2, 2012 at 11:55 AM, sebb wrote: >>> > ...If I were the RM, I would add the missing EOLs at EOF and create >>> another RC >>> >>> I see your point about the distributed files not being *binary >>> identical* to the svn tag, but I personally consider source files to >>> be identical if diff -b (i.e. ignore changes in the amount of >>> whitespace) says they are. >>> >>> So, in this case, I definitely don't see this as a blocker, just >>> something to fix for a future release. >>> >>> -Bertrand >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
Thank you, Alex On Fri, Nov 2, 2012 at 3:59 AM, Alex Harui wrote: > > > > On 11/1/12 4:08 PM, "Alexei Fedotov" wrote: > >> Thanks for explaining, I finally got Carol's point on installer. >> >> I still cannot fully understand the licensing. I have checked that >> installer/src/com/adobe/utils/IntUtil.as (which is mentioned in LICENSE >> file as Adobe licensed) contains Apache license header. > After more digging, I think the issue is that IntUtil.as shouldn't have an > Apache header. It comes from external projects under Modified BSD. Then I > think it would make sense to have the Adobe/BSD license in the LICENSE file? > >> >> Why do you need any additional attributions for Apache licensed file? > After more digging, I think this is here because these are binary files > that, while under Apache license, are not sourced from a.o, so technically, > third-party. It isn't clear from here [5] that if it is under Apache it > doesn't have to be called out in the LICENSE file. >> >> BTW, file paths are incorrect in the LICENSE file. > Agreed. But not critical? > > [5] http://www.apache.org/legal/resolved.html#required-third-party-notices > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
Thanks for explaining, I finally got Carol's point on installer. I still cannot fully understand the licensing. I have checked that installer/src/com/adobe/utils/IntUtil.as (which is mentioned in LICENSE file as Adobe licensed) contains Apache license header. Why do you need any additional attributions for Apache licensed file? BTW, file paths are incorrect in the LICENSE file. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Nov 2, 2012 at 2:47 AM, Alex Harui wrote: > > > > On 11/1/12 3:04 PM, "Alexei Fedotov" wrote: > >> First, I'm not a lawyer. More experienced guys will tell us more. >> >> In our project (Openmeetings) we keep the files which are not Apache >> licensed in different places, e.g. at googlecode, and collect them >> during the build process via wget. We do not include them into a >> source release. >> > OK, thanks. We include our in the LICENSE file per this document [1] > Where it says: > > "All the licenses on all the files to be included within a package should be > included in the LICENSE document. This LICENSE (courtesy of Apache HTTPD) is > a good example. The Apache License is at the top of the LICENSE document. > After that, the license for each non-Apache licensed component is included, > along with a clear explanation of which files that license applies to." > > We'll see if others have to say, but I think we are conforming. > > [1] > http://incubator.apache.org/guides/releasemanagement.html#best-practice-lice > nse > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
First, I'm not a lawyer. More experienced guys will tell us more. In our project (Openmeetings) we keep the files which are not Apache licensed in different places, e.g. at googlecode, and collect them during the build process via wget. We do not include them into a source release. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Nov 2, 2012 at 1:58 AM, Alex Harui wrote: > > > > On 11/1/12 2:50 PM, "Alexei Fedotov" wrote: > >> I mention ./LICENSE file from the source release and naturally assume >> this is the source release license. >> Then I assume Apache source release should be generally Apache >> licensed. This is not necessarily true for a binary release which can >> contain compatibly licensed components. >> > Hi Alexei, > > I think there may in fact be a problem with the LICENSE file and the > Open_Sans font. > > However, I I am confused about what steps we are supposed to execute to > address your second concern. I'm not sure what you mean by "adding > BSD-like...". > > There are two files in the source release that have a BSD license using the > Modified BSD template and substituting Adobe as the organization. Why isn't > what we did the correct way to handle this? >>>>> 2. Something like BSD license. >>>>> >>>>> The first item I cannot understand completely, the second one can be >>>>> resolved by adding BSD-like licensed files during build. >>>>> >>>>> So the question is why do you use non-standard LICENSE for the source >>>>> release? > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
I mention ./LICENSE file from the source release and naturally assume this is the source release license. Then I assume Apache source release should be generally Apache licensed. This is not necessarily true for a binary release which can contain compatibly licensed components. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Nov 2, 2012 at 1:43 AM, Carol Frampton wrote: > > > On 11/1/12 3 :59PM, "Carol Frampton" wrote: > >> >> >>On 11/1/12 7 :36AM, "Alexei Fedotov" wrote: >> >>>Hello OmPrakash, >>> >>>I have notices that the LICENSE file has few additions two Apache >>>License: >>> >>>1. The second entry for Apache license. >>>2. Something like BSD license. >>> >>>The first item I cannot understand completely, the second one can be >>>resolved by adding BSD-like licensed files during build. >>> >>>So the question is why do you use non-standard LICENSE for the source >>>release? >> >>This is the LICENSE file for Apache Flex which was reviewed by our mentors >>prior to the release of Apache Flex 4.8.0-incubating. If I am not >>mistaken, this is the format that Apache and Adobe agreed to when Adobe >>donated the code to Apache. > > Ignore my comment. I was looking at the LICENSE file for the SDK rather > than the installer. > > Carol > >> >>Carol >> >>> >>>-- >>>With best regards / с наилучшими пожеланиями, >>>Alexei Fedotov / Алексей Федотов, >>>http://dataved.ru/ >>>+7 916 562 8095 >>> >>> >>>On Thu, Nov 1, 2012 at 3:16 PM, sebb wrote: >>>> On 30 October 2012 20:16, Om wrote: >>>>> Hi all, >>>>> >>>>> After our first release as Apache Flex, we are following it up with >>>>>the Apache >>>>> Flex SDK Installer (Incubating) AIR application. >>>>> >>>>> The Apache Flex SDK Installer AIR application provides an easy, >>>>> single-click installation of the Apache Flex SDK and all its >>>>>dependencies. >>>>> This will make it suitable for working with IDEs such as Adobe >>>>>Flash >>>>> Builder, FDT, IntelliJ IDEA, FlashDevelop, etc. >>>>> >>>>> The application downloads the following dependencies: >>>>> >>>>>- The AIR sdk (Windows vs. Mac) based on the current platform >>>>>- Adobe Flash Player playerglobal.swc >>>>>- SwfObject >>>>>- Open Source Media Framework (OSMF) >>>>>- Adobe Text Layout Format (TLF) >>>>> >>>>> Optionally, the application will download these files as well: >>>>> >>>>>- Adobe BlazeDS >>>>>- Adobe embedded font support >>>>> >>>>> >>>>> This release was voted upon on the flex-...@incubator.apache.org list. >>>>> The >>>>> vote passed with 11 binding and 5 non-binding votes. Here is the >>>>>voting >>>>> thread: >>>>> http://markmail.org/thread/nbrflol6mkpu65ry >>>>> >>>>> The source distributions for Windows and Mac are available here: >>>>> http://people.apache.org/~bigosmallm/installapacheflex_RC9/ >>>>> >>>>> The binary distributions as a convenience for the respective >>>>>platforms, >>>>> available here: >>>>> http://people.apache.org/~bigosmallm/installapacheflex_RC9/binaries/ >>>>> >>>>> The PGP keys of the two release managers - OmPrakash Muppirala (Source >>>>>kit >>>>> + Windows binaries) and Erik de Bruin (Mac binaries) are available >>>>>here: >>>>> http://www.apache.org/dist/incubator/flex/KEYS >>>>> >>>>> Here is the tag for the release: >>>>> >>>>>https://svn.apache.org/repos/asf/incubator/flex/utilities/tags/apache-f >>>>>l >>>>>ex-sdk-installer-1.0.8-RC9 >>>> >>>> There are 3 directories under that tag; I would expect to find the >>>> NOTICE, LICENSE and DISCLAIMER files at the top level rather than >>>> under just one of them. >>>> >>>> The files do end up at the top level in the source archive, which is >>>>good. >>>> >>>> Also, the installe
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
Carol, There are usually two licenses - for a source release and for binary distribution. Was the agreement you mentioned about source release license? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Nov 1, 2012 at 11:59 PM, Carol Frampton wrote: > > > On 11/1/12 7 :36AM, "Alexei Fedotov" wrote: > >>Hello OmPrakash, >> >>I have notices that the LICENSE file has few additions two Apache License: >> >>1. The second entry for Apache license. >>2. Something like BSD license. >> >>The first item I cannot understand completely, the second one can be >>resolved by adding BSD-like licensed files during build. >> >>So the question is why do you use non-standard LICENSE for the source >>release? > > This is the LICENSE file for Apache Flex which was reviewed by our mentors > prior to the release of Apache Flex 4.8.0-incubating. If I am not > mistaken, this is the format that Apache and Adobe agreed to when Adobe > donated the code to Apache. > > Carol > >> >>-- >>With best regards / с наилучшими пожеланиями, >>Alexei Fedotov / Алексей Федотов, >>http://dataved.ru/ >>+7 916 562 8095 >> >> >>On Thu, Nov 1, 2012 at 3:16 PM, sebb wrote: >>> On 30 October 2012 20:16, Om wrote: >>>> Hi all, >>>> >>>> After our first release as Apache Flex, we are following it up with >>>>the Apache >>>> Flex SDK Installer (Incubating) AIR application. >>>> >>>> The Apache Flex SDK Installer AIR application provides an easy, >>>> single-click installation of the Apache Flex SDK and all its >>>>dependencies. >>>> This will make it suitable for working with IDEs such as Adobe Flash >>>> Builder, FDT, IntelliJ IDEA, FlashDevelop, etc. >>>> >>>> The application downloads the following dependencies: >>>> >>>>- The AIR sdk (Windows vs. Mac) based on the current platform >>>>- Adobe Flash Player playerglobal.swc >>>>- SwfObject >>>>- Open Source Media Framework (OSMF) >>>>- Adobe Text Layout Format (TLF) >>>> >>>> Optionally, the application will download these files as well: >>>> >>>>- Adobe BlazeDS >>>>- Adobe embedded font support >>>> >>>> >>>> This release was voted upon on the flex-...@incubator.apache.org list. >>>> The >>>> vote passed with 11 binding and 5 non-binding votes. Here is the >>>>voting >>>> thread: >>>> http://markmail.org/thread/nbrflol6mkpu65ry >>>> >>>> The source distributions for Windows and Mac are available here: >>>> http://people.apache.org/~bigosmallm/installapacheflex_RC9/ >>>> >>>> The binary distributions as a convenience for the respective platforms, >>>> available here: >>>> http://people.apache.org/~bigosmallm/installapacheflex_RC9/binaries/ >>>> >>>> The PGP keys of the two release managers - OmPrakash Muppirala (Source >>>>kit >>>> + Windows binaries) and Erik de Bruin (Mac binaries) are available >>>>here: >>>> http://www.apache.org/dist/incubator/flex/KEYS >>>> >>>> Here is the tag for the release: >>>> >>>>https://svn.apache.org/repos/asf/incubator/flex/utilities/tags/apache-fl >>>>ex-sdk-installer-1.0.8-RC9 >>> >>> There are 3 directories under that tag; I would expect to find the >>> NOTICE, LICENSE and DISCLAIMER files at the top level rather than >>> under just one of them. >>> >>> The files do end up at the top level in the source archive, which is >>>good. >>> >>> Also, the installerBadge directory tree does not appear to be included >>> in the source archive - is that intentional? >>> If so, why is it in the tag? >>> >>> The key C1708693 does not appear to be available from the normal >>> public PGP key servers. >>> >>> Some of the source files don't have an EOL at EOF (e.g. >>> ApacheFlexToolsStyle.css) in the SVN tag whereas they do have an EOL >>> in the source archive. >>> This is a packaging error, which can be sorted by ensuring that source >>> files always have an EOL at EOF, or by changing the packaging >>> instructions to not add the missing EOLs. >>> >>>> >>>> >>>> P
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
I have also found the following line of code: > ./installer/src/InstallApacheFlex.mxml: var > licenseWindow:AdobeLicense = new AdobeLicense(); Shouldn't you use new ApacheLicense() here? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Nov 1, 2012 at 3:36 PM, Alexei Fedotov wrote: > Hello OmPrakash, > > I have notices that the LICENSE file has few additions two Apache License: > > 1. The second entry for Apache license. > 2. Something like BSD license. > > The first item I cannot understand completely, the second one can be > resolved by adding BSD-like licensed files during build. > > So the question is why do you use non-standard LICENSE for the source release? > > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Thu, Nov 1, 2012 at 3:16 PM, sebb wrote: >> On 30 October 2012 20:16, Om wrote: >>> Hi all, >>> >>> After our first release as Apache Flex, we are following it up with the >>> Apache >>> Flex SDK Installer (Incubating) AIR application. >>> >>> The Apache Flex SDK Installer AIR application provides an easy, >>> single-click installation of the Apache Flex SDK and all its dependencies. >>> This will make it suitable for working with IDEs such as Adobe Flash >>> Builder, FDT, IntelliJ IDEA, FlashDevelop, etc. >>> >>> The application downloads the following dependencies: >>> >>>- The AIR sdk (Windows vs. Mac) based on the current platform >>>- Adobe Flash Player playerglobal.swc >>>- SwfObject >>>- Open Source Media Framework (OSMF) >>>- Adobe Text Layout Format (TLF) >>> >>> Optionally, the application will download these files as well: >>> >>>- Adobe BlazeDS >>>- Adobe embedded font support >>> >>> >>> This release was voted upon on the flex-...@incubator.apache.org list. The >>> vote passed with 11 binding and 5 non-binding votes. Here is the voting >>> thread: >>> http://markmail.org/thread/nbrflol6mkpu65ry >>> >>> The source distributions for Windows and Mac are available here: >>> http://people.apache.org/~bigosmallm/installapacheflex_RC9/ >>> >>> The binary distributions as a convenience for the respective platforms, >>> available here: >>> http://people.apache.org/~bigosmallm/installapacheflex_RC9/binaries/ >>> >>> The PGP keys of the two release managers - OmPrakash Muppirala (Source kit >>> + Windows binaries) and Erik de Bruin (Mac binaries) are available here: >>> http://www.apache.org/dist/incubator/flex/KEYS >>> >>> Here is the tag for the release: >>> https://svn.apache.org/repos/asf/incubator/flex/utilities/tags/apache-flex-sdk-installer-1.0.8-RC9 >> >> There are 3 directories under that tag; I would expect to find the >> NOTICE, LICENSE and DISCLAIMER files at the top level rather than >> under just one of them. >> >> The files do end up at the top level in the source archive, which is good. >> >> Also, the installerBadge directory tree does not appear to be included >> in the source archive - is that intentional? >> If so, why is it in the tag? >> >> The key C1708693 does not appear to be available from the normal >> public PGP key servers. >> >> Some of the source files don't have an EOL at EOF (e.g. >> ApacheFlexToolsStyle.css) in the SVN tag whereas they do have an EOL >> in the source archive. >> This is a packaging error, which can be sorted by ensuring that source >> files always have an EOL at EOF, or by changing the packaging >> instructions to not add the missing EOLs. >> >>> >>> >>> Please vote: >>> >>> [ ] +1 approve >>> [ ] +0 no opinion >>> [ ] -1 disapprove (and reason why) >>> >>> The vote will be open for at least 72 hours. >>> >>> Regards, >>> OmPrakash Muppirala >>> Apache Flex PPMC Member >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Flex SDK Installer 1.0.8-incubating
Hello OmPrakash, I have notices that the LICENSE file has few additions two Apache License: 1. The second entry for Apache license. 2. Something like BSD license. The first item I cannot understand completely, the second one can be resolved by adding BSD-like licensed files during build. So the question is why do you use non-standard LICENSE for the source release? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Nov 1, 2012 at 3:16 PM, sebb wrote: > On 30 October 2012 20:16, Om wrote: >> Hi all, >> >> After our first release as Apache Flex, we are following it up with the >> Apache >> Flex SDK Installer (Incubating) AIR application. >> >> The Apache Flex SDK Installer AIR application provides an easy, >> single-click installation of the Apache Flex SDK and all its dependencies. >> This will make it suitable for working with IDEs such as Adobe Flash >> Builder, FDT, IntelliJ IDEA, FlashDevelop, etc. >> >> The application downloads the following dependencies: >> >>- The AIR sdk (Windows vs. Mac) based on the current platform >>- Adobe Flash Player playerglobal.swc >>- SwfObject >>- Open Source Media Framework (OSMF) >>- Adobe Text Layout Format (TLF) >> >> Optionally, the application will download these files as well: >> >>- Adobe BlazeDS >>- Adobe embedded font support >> >> >> This release was voted upon on the flex-...@incubator.apache.org list. The >> vote passed with 11 binding and 5 non-binding votes. Here is the voting >> thread: >> http://markmail.org/thread/nbrflol6mkpu65ry >> >> The source distributions for Windows and Mac are available here: >> http://people.apache.org/~bigosmallm/installapacheflex_RC9/ >> >> The binary distributions as a convenience for the respective platforms, >> available here: >> http://people.apache.org/~bigosmallm/installapacheflex_RC9/binaries/ >> >> The PGP keys of the two release managers - OmPrakash Muppirala (Source kit >> + Windows binaries) and Erik de Bruin (Mac binaries) are available here: >> http://www.apache.org/dist/incubator/flex/KEYS >> >> Here is the tag for the release: >> https://svn.apache.org/repos/asf/incubator/flex/utilities/tags/apache-flex-sdk-installer-1.0.8-RC9 > > There are 3 directories under that tag; I would expect to find the > NOTICE, LICENSE and DISCLAIMER files at the top level rather than > under just one of them. > > The files do end up at the top level in the source archive, which is good. > > Also, the installerBadge directory tree does not appear to be included > in the source archive - is that intentional? > If so, why is it in the tag? > > The key C1708693 does not appear to be available from the normal > public PGP key servers. > > Some of the source files don't have an EOL at EOF (e.g. > ApacheFlexToolsStyle.css) in the SVN tag whereas they do have an EOL > in the source archive. > This is a packaging error, which can be sorted by ensuring that source > files always have an EOL at EOF, or by changing the packaging > instructions to not add the missing EOLs. > >> >> >> Please vote: >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> The vote will be open for at least 72 hours. >> >> Regards, >> OmPrakash Muppirala >> Apache Flex PPMC Member > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Welcome Roman Shaposhnik to the Apache Incubator PMC
Congratulations, Roman! On Mon, Oct 22, 2012 at 9:19 AM, Roman Shaposhnik wrote: > On Fri, Oct 19, 2012 at 10:47 AM, Mattmann, Chris A (388J) > wrote: >> Hey Folks, >> >> The Apache Incubator PMC has VOTEd to add Roman Shaposhnik to our ranks. >> >> Welcome, Roman! Feel free to say a bit about yourself. > > Thanks Chris! > > I'm extremely excited and honored to join the ranks of > the IPMC. I will do my best to measure up to the high > standard that the project has been known for. > > As for myself, I'm a software engineer who's been lucky > enough to be involved in open source projects for > pretty much all of my career. I grew up with UNIX > (later Plan9) and for 11 years I was a happy > hacker at Sun microsystems working on quite a few > different projects (C++ compilers, development tools, > DTrace tools, cloud storage -- you name it!). > > Nowadays, I like my software extreme -- it either has > to be huge and intimidating (like Hadoop) or small > and beautiful (like Lua). And if you believe this divide > can be bridged then we'd love to see you in Apache > Bigtop ;-) > > I'm originally from St.Petersburg, Russia but these days > you can find me on the other side of the globe in > Silicon Valley (I'm currently employed by Cloudera Inc) > mulling about at various Meetups and Board game events. > > Thanks, > Roman. > > P.S. And the most crucial bit of info: I use vim, 4 space > tabs and mutt. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: ${podling}.incubator.apache.org
I like it -
that will simplify migrations
12.10.2012 11:31 пользователь "Daniel Shahaf"
написал:
> Do people mind if web sites (and maybe mailing lists) of new podlings
> live at domains of the form "${podling}.incubator.apache.org"?
>
> This is in relation to infra work on streamlining TLP migrations. (Case
> in point: CMS TLP migrations.) This thread is about the
> externally-visible names, not about implementation details.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
Re: [VOTE] Recommend to the Board to establish the Apache OpenOffice Project
+1 On Thu, Oct 11, 2012 at 2:53 PM, Mark Struberg wrote: > +1 > > LieGrue, > strub > > > > > - Original Message - >> From: Ross Gardler >> To: general@incubator.apache.org >> Cc: >> Sent: Thursday, October 11, 2012 9:14 AM >> Subject: Re: [VOTE] Recommend to the Board to establish the Apache >> OpenOffice Project >> >> +1 (mentor) >> >> Sent from my tablet >> On Oct 10, 2012 9:00 PM, "Andrea Pescetti" >> wrote: >> >>> Seeing no objections to my last message, and keeping into account that >>> this list had been regularly informed about the steps Apache OpenOffice was >>> taking towards graduation, I'm hereby asking the IPMC to recommend the >>> following resolution to the Board. Aim of the resolution is to establish >>> the Apache OpenOffice Project as a Top Level Project. >>> >>> Please cast your vote: >>> >>> [ ] +1, recommend the resolution to the Board >>> [ ] +0, abstain/don't care >>> [ ] -1, do not recommend the resolution to the Board, because... >>> >>> This vote will be open for 72 hours from now; only votes from the >>> Incubator PMC are binding. >>> >>> Resolution text: >>>--- >>> WHEREAS, the Board of Directors deems it to be in the best interests of >>> the Foundation and consistent with the Foundation's purpose to >> establish a >>> Project Management Committee charged with the creation and maintenance of >>> open-source software related to the OpenOffice personal productivity >>> applications, for distribution at no charge to the public. >>> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), >>> to be known as the "Apache OpenOffice Project", be and hereby is >>> established pursuant to Bylaws of the Foundation; and be it further >>> >>> RESOLVED, that the Apache OpenOffice Project be and hereby is responsible >>> for the creation and maintenance of software related to the OpenOffice >>> personal productivity applications; and be it further >>> >>> RESOLVED, that the office of "Vice President, OpenOffice" be and >> hereby is >>> created, the person holding such office to serve at the direction of the >>> Board of Directors as the chair of the Apache OpenOffice Project, and to >>> have primary responsibility for management of the projects within the scope >>> of responsibility of the Apache OpenOffice Project; and be it further >>> >>> RESOLVED, that the persons listed immediately below be and hereby are >>> appointed to serve as the initial members of the Apache OpenOffice Project: >>> >>> * Andre Fischer (af) >>> * Andrea Pescetti (pescetti) >>> * Andrew Rist (arist) >>> * Ariel Constenla-Haile (arielch) >>> * Armin Le Grand (alg) >>> * Dave Fisher (wave) >>> * Donald Harbison (dpharbison) >>> * Drew Jensen (atjensen) >>> * Ian Lynch (ingotian) >>> * Jürgen Schmidt (jsc) >>> * Kay Schenk (kschenk) >>> * Kazunari Hirano (khirano) >>> * Louis Suarez-Potts (louis) >>> * Marcus Lange (marcus) >>> * Oliver-Rainer Wittmann (orw) >>> * Pedro Giffuni (pfg) >>> * Peter Junge (pj) >>> * Raphael Bircher (rbircher) >>> * Regina Henschel (regina) >>> * RGB.ES (rgb-es) >>> * Roberto Galoppini (galoppini) >>> * Yang Shih-Ching (imacat) >>> * Yong Lin Ma (mayongl) >>> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrea Pescetti be appointed >>> to the office of Vice President, OpenOffice, to serve in accordance with >>> and subject to the direction of the Board of Directors and the Bylaws of >>> the Foundation until death, resignation, retirement, removal or >>> disqualification, or until a successor is appointed; and be it further >>> >>> RESOLVED, that the initial Apache OpenOffice Project be and hereby is >>> tasked with the creation of a set of bylaws intended to encourage open >>> development and increased participation in the OpenOffice Project; and be >>> it further >>> >>> RESOLVED, that the Apache OpenOffice Project be and hereby is tasked with >>> the migration and rationalization of the Apache OpenOffice.org podling; and >>> be it further >>> >>> RESOLVED, that all responsibilities pertaining to the Apache Incubator >>> OpenOffice.org podling encumbered upon the Apache Incubator Project are >>> hereafter discharged. >>>--- >>> Best regards, >>>Andrea Pescetti - Apache OpenOffice PPMC. >>> >>> --**--**- >>> To unsubscribe, e-mail: >> general-unsubscribe@incubator.**apache.org >>> For additional commands, e-mail: >> general-help@incubator.apache.**org >>> >>> >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additiona
Re: [VOTE] Apache OpenMeetings Drupal Plugin 1.0 Incubating Release Candidate 1
+1 On Thu, Oct 11, 2012 at 1:40 PM, seba.wag...@gmail.com wrote: > We've moved the project to apache-extras.org > > http://code.google.com/a/apache-extras.org/p/drupal-plugin-openmeetings/ > > Sebastian > > 2012/9/13 Jukka Zitting > >> Hi, >> >> On Thu, Sep 13, 2012 at 10:08 AM, seba.wag...@gmail.com >> wrote: >> > I don't want to create a "claim" here. If the request raises too many >> > concerns we will simply move it to apache-extras.org. Although it >> > would be better if we could maintain those plugins within the ASF and >> > contributors have the chance to become full members of our project. >> > Also I don't understand in what sense implementing an API >> > automatically requires all code to apply a certain License. >> >> I agree with that argument against the viral nature of GPL, but in >> general the ASF has tended to honor the wishes of upstream copyright >> owners also beyond the requirements of copyright law. >> >> > Somehow those issues just prevent progress. Maybe we should wait until >> > the Incubator/Board meeting at the 19th takes place? >> >> The ASF legal team is best positioned to resolve this issue. LEGAL-147 >> [1] is the place to look at. >> >> [1] https://issues.apache.org/jira/browse/LEGAL-147 >> >> BR, >> >> Jukka Zitting >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: New challenges (Was: NOMINATIONS for Incubator PMC Chair)
+1 (non-binding) for Benson for being a nice and practical guy On Fri, Oct 5, 2012 at 5:06 PM, Davanum Srinivas wrote: > > On Fri, Oct 5, 2012 at 9:04 AM, Matt Hogstrom wrote: > > > I prefer simple. I'd rather see nominations and votes done via-email > with > > IPMC votes noted as (binding). > > > > My +1 for nominating Benson. > > > > On Oct 2, 2012, at 10:07 AM, sebb wrote: > > > > > Indeed, but that might be better done if/when Steve is enhanced to > > > support private (as opposed to secret) votes, as hopefully that would > > > not require the same overhead. > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > -- > Davanum Srinivas :: http://davanum.wordpress.com >
Re: Openmeetings - A Shepherd's View
The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. 14.09.2012 16:46 пользователь "Jim Jagielski" написал: > > On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din > wrote: > > > > > But can we add ASL headers to files which are defined and considered > > to be, even structure wise (please correct me if I am wrong), under > > the license of Eclipse ? > > > > If they are build artifacts (like stuff created by autoconf > for example), then there's no need to add AL headers (AL, not ASL). > AL headers are for actual work products (like source code, etc)... > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Openmeetings - A Shepherd's View
Hello Mohammad, thank you for the review. Eclipse can be considered as an alternative build system, so these files are like build.xml files. Why not to keep them in release? 14.09.2012 3:46 пользователь "Mohammad Nour El-Din" написал: > Hi > >I checked: > - Mailing lists and from it the community looks active to a good > extent both on the users and developers lists > - Last report (June 2012) they were in the 'No Release' group of > podlings but they managed to get a release out > - Their progress is not that fast but it is stable and steady > > One minor note: > - In [1] I noticed files related to Eclipse like .classpath and > .project, I am not sure that these files should be in a release tag. > Comments about that ? > > [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/ > > > -- > Thanks > - Mohammad Nour > > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Apache OpenMeetings Drupal Plugin 1.0 Incubating Release Candidate 1
What if we double license the code under public domain? Those who install the plug-in for Drupal, just use public code to create their own GPL licensed distribution at that moment. 15.08.2012 1:10 пользователь "Christian Grobmeier" написал: > Hi, > > I can understand having 10 projects on apache-extras is not really > great - but legals are more important than comfort. > > I am afraid I cannot answer the legal question. But my understanding > seems to be similar to what Sam Ruby thinks: > > http://markmail.org/message/srggkothptvoemxg#query:+page:1+mid:33hztgfyfxdb3jef+state:results > > I would feel better if we would get a green light from legal here. I > know this is an another hurdle for you but if we have one time > clarification we never need to it that again. We should also look at > the licenses of the other plugins. > > Cheers > Christian > > > > On Tue, Aug 14, 2012 at 9:52 PM, seba.wag...@gmail.com > wrote: > > Hi Christian, > > > > we have been discussing a similar issue some time ago about the Moodle > Plugin: > > http://markmail.org/thread/jf2r4ljxgdc7cfqe > > > > There is also a discussion on legal-discuss list on similar topic: > > http://markmail.org/message/srggkothptvoemxg > > > > As you can see from the list of plugins that we already maintain: > > https://builds.apache.org/view/M-R/view/OpenMeetings/ > > This is a quite important question. > > > > Although Apache Extra might be a good place for it legally having 10 > > subproject will be a tough task to handle. > > > > Sebastian > > > > 2012/8/14 Christian Grobmeier : > >> Hello guys, > >> > >> just was reviewing this release and it looks good so far. I have > >> reviewed the content, did not check the sigs at the moment. > >> > >> One question raised to my mind: Drupal is GPL licensed. You wrote a > >> plugin for Drupal. Isn't it the case it needs to be licensed like > >> Drupal then? Probably I am paranoid here, but I would love to get a > >> clear answer at this. Becuase if that is the case the plug cannot be > >> released from the ASF and must go to for example apache-extras.org > >> > >> Cheers > >> Christian > >> > >> On Tue, Aug 14, 2012 at 3:53 PM, seba.wag...@gmail.com > >> wrote: > >>> Dear Incubator Members, > >>> > >>> I would like to start a vote about releasing Apache OpenMeetings Drupal > >>> Plugin 1.0 Incubating Release Candidate 1 > >>> > >>> There was already a positive vote on the developer mailing list: > >>> > >>> +1 IPMC: yegor > >>> +1 PPMC: solomax, albus, german, aaf(mentor), sebawagner > >>> Wider community: Irina > >>> > >>> Vote Thread: > >>> http://markmail.org/message/qufzi46cpl242sqx > >>> > >>> Changes are in the Changelog: > >>> > https://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/drupal/1.0RC1/CHANGELOG > >>> > >>> Release artefacts: > >>> http://people.apache.org/~sebawagner/drupal-plugin-1.0-incubating/ > >>> > >>> Tag: > >>> > https://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/drupal/1.0RC1 > >>> > >>> PGP release keys (signed using 93A30395): > >>> http://www.apache.org/dist/incubator/openmeetings/KEYS > >>> > >>> [ ] +1 approve > >>> [ ] +0 no opinion > >>> [ ] -1 disapprove (and reason why) > >>> > >>> Thanks! > >>> Sebastian > >> > >> > >> > >> -- > >> http://www.grobmeier.de > >> https://www.timeandbill.de > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > > > > > > > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > seba.wag...@gmail.com > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1
Matthew, thank you! -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Aug 10, 2012 at 3:47 PM, Franklin, Matthew B. wrote: > If no one else beats me to it, I will review this before the end of the > weekend. > > -Matt > >>-Original Message- >>From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] >>Sent: Friday, August 10, 2012 7:28 AM >>To: general@incubator.apache.org >>Cc: openmeetings-...@incubator.apache.org >>Subject: Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating >>Release Candidate 1 >> >>Thanks Alexei! >> >>Still 1 IPMC vote missing >> >>Thanks >>Sebastian >> >>2012/8/10 Alexei Fedotov >> >>> +1 >>> >>> >>> -- >>> With best regards / с наилучшими пожеланиями, >>> Alexei Fedotov / Алексей Федотов, >>> http://dataved.ru/ >>> +7 916 562 8095 >>> >>> >>> On Fri, Aug 10, 2012 at 11:32 AM, seba.wag...@gmail.com >>> wrote: >>> > Yegor & Jukka thanks for review and voting! >>> > >>> > We still need one IPMC vote to approve that release. >>> > >>> > Those are just integration plugins for the ELearning Platform Moodle. >>> > roughly 20 files zipped to packages, ~40KByte each, zero dependencies, >>> > 2 minutes to check :) >>> > >>> > Release artefacts: >>> > http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/ >>> > >>> > Thanks! >>> > Sebastian >>> > >>> > 2012/8/9 Yegor Kozlov >>> > >>> >> +1 >>> >> >>> >> Yegor >>> >> >>> >> On Mon, Aug 6, 2012 at 4:44 PM, seba.wag...@gmail.com >>> >> wrote: >>> >> > Dear Incubator Members, >>> >> > >>> >> > I would like to start a vote about releasing Apache OpenMeetings >>> Moodle >>> >> > Plugin 1.4 Incubating Release Candidate 1 >>> >> > >>> >> > There was already a positive vote on the developer mailing list: >>> >> > +1 PPMC: >>> >> > solomax, albus, eschwert, german, aaf(mentor), sebawagner >>> >> > >>> >> > Vote Thread: >>> >> > http://markmail.org/thread/db4bhkroe6yun5bi >>> >> > >>> >> > Changes are in the Changelog: >>> >> > >>> >> >>> >>http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo >>dle/1.4RC1/CHANGELOG >>> >> > >>> >> > Release artefacts: >>> >> > http://people.apache.org/~sebawagner/moodle-plugin-1.4- >>incubating/ >>> >> > >>> >> > Tag: >>> >> > >>> >> >>> >>http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo >>dle/1.4RC1/ >>> >> > >>> >> > PGP release keys (signed using 93A30395): >>> >> > http://www.apache.org/dist/incubator/openmeetings/KEYS >>> >> > >>> >> > Vote will be open for 72 hours. >>> >> > >>> >> > [ ] +1 approve >>> >> > [ ] +0 no opinion >>> >> > [ ] -1 disapprove (and reason why) >>> >> > >>> >> > >>> >> > Thanks! >>> >> > Sebastian >>> >> > -- >>> >> > Sebastian Wagner >>> >> > https://twitter.com/#!/dead_lock >>> >> > http://www.webbase-design.de >>> >> > http://www.wagner-sebastian.com >>> >> > seba.wag...@gmail.com >>> >> >>> > >>> > >>> > >>> > -- >>> > Sebastian Wagner >>> > https://twitter.com/#!/dead_lock >>> > http://www.webbase-design.de >>> > http://www.wagner-sebastian.com >>> > seba.wag...@gmail.com >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> >> >>-- >>Sebastian Wagner >>https://twitter.com/#!/dead_lock >>http://www.webbase-design.de >>http://www.wagner-sebastian.com >>seba.wag...@gmail.com > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1
+1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Aug 10, 2012 at 11:32 AM, seba.wag...@gmail.com wrote: > Yegor & Jukka thanks for review and voting! > > We still need one IPMC vote to approve that release. > > Those are just integration plugins for the ELearning Platform Moodle. > roughly 20 files zipped to packages, ~40KByte each, zero dependencies, > 2 minutes to check :) > > Release artefacts: > http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/ > > Thanks! > Sebastian > > 2012/8/9 Yegor Kozlov > >> +1 >> >> Yegor >> >> On Mon, Aug 6, 2012 at 4:44 PM, seba.wag...@gmail.com >> wrote: >> > Dear Incubator Members, >> > >> > I would like to start a vote about releasing Apache OpenMeetings Moodle >> > Plugin 1.4 Incubating Release Candidate 1 >> > >> > There was already a positive vote on the developer mailing list: >> > +1 PPMC: >> > solomax, albus, eschwert, german, aaf(mentor), sebawagner >> > >> > Vote Thread: >> > http://markmail.org/thread/db4bhkroe6yun5bi >> > >> > Changes are in the Changelog: >> > >> http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moodle/1.4RC1/CHANGELOG >> > >> > Release artefacts: >> > http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/ >> > >> > Tag: >> > >> http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moodle/1.4RC1/ >> > >> > PGP release keys (signed using 93A30395): >> > http://www.apache.org/dist/incubator/openmeetings/KEYS >> > >> > Vote will be open for 72 hours. >> > >> > [ ] +1 approve >> > [ ] +0 no opinion >> > [ ] -1 disapprove (and reason why) >> > >> > >> > Thanks! >> > Sebastian >> > -- >> > Sebastian Wagner >> > https://twitter.com/#!/dead_lock >> > http://www.webbase-design.de >> > http://www.wagner-sebastian.com >> > seba.wag...@gmail.com >> > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating)
Hello, Let me add one more point on adding dependencies to source releases. In addition to license, the dependence contain copyright statements, e.g. "# Copyright (C) 2005 Christopher Lenz ". As mentioned here http://www.apache.org/legal/src-headers.html > If the source file is submitted with a copyright notice included in it, the > copyright owner (or owner's agent) must either: > remove such notices, or > move them to the NOTICE file associated with each applicable project release, > or > provide written permission for the ASF to make such removal or relocation of > the notices. This issue cannot be fixed by merging licenses into LICENSE file. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Aug 8, 2012 at 11:26 AM, ant elder wrote: > On Wed, Aug 8, 2012 at 1:13 AM, Greg Stein wrote: >> On Tue, Aug 7, 2012 at 5:54 PM, ant elder wrote: >>> On Tue, Aug 7, 2012 at 9:51 PM, Greg Stein wrote: >>>... >>>> You can look at the archives back in 2006 when it was incubating. In >>>> particular, there is one sent to private@incubator that I would refer >>>> you to: >>>> http://s.apache.org/c04 [only usable by ASF Members] >>>> >>> >>> Didn't that get subsequently revised by Cliff et al into "Incubating >>> projects must not distribute an official product release that includes >>> works covered by an excluded license" - >>> http://www.apache.org/legal/3party.html#transition-incubator >> >> Dunno. That link is for a draft document, and has been replaced by a >> final/resolved form (see link at top of page). >> >> Regardless... Jukka posted recently, and I'd look to his note for >> "current policy". I think his statement puts Incubator policy a little >> more relaxed than ASF, but likely not as relaxed as I would have >> posited (in regards to dependencies). >> > > The good thing about release votes is that they can't be vetoed so > regardless of what policies may or may not be documented whether or > not a release vote passes is just down to getting enough people to > vote +1. Votes on general@ often stall and require a respin when > someone claims something is wrong which puts off others from voting. > Something as basic as a dependent license missing from the LICENSE > file would be one of those things that in the past would have always > demanded a respin, so the change, and it is a change, to allow wiggle > room is what i hope people will remember from this. > >...ant > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Syncope 1.0.0-incubating
+1 (non-binding) -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Mon, Aug 6, 2012 at 7:50 PM, Francesco Chicchiriccò wrote: > On 06/08/2012 16:36, Alexei Fedotov wrote: >> Hello Francesco, >> >> Here are few things I have found via manual inspection: >> >> 1. Jquery bundle contains several following strings: "Dual licensed >> under the MIT or GPL Version 2 licenses." >> *) source release LICENSE file does not contain MIT license; >> *) and the file itself does not look like APL licensed; >> *) and it is a part of the source release. >> >> Something should be fixed here, i.e. the files replaced with wget in >> the build script. >> >> 2. ./legal_ext/LICENSE does not have a license for jquery. Does war >> contain jquery? > > Hi Alexei, > I've taken a look at other ASF projects including JQuery (or similar > dual-licensed JS frameworks) and I've opened > https://issues.apache.org/jira/browse/SYNCOPE-181 > We'll fix this ASAP. > >> Don't think these issues are stoppers. > > Cool :-) > What's your vote on the release, then? > > Thanks for your review. > Regards. > >> On Mon, Aug 6, 2012 at 6:07 PM, Mark Struberg wrote: >>> Hi Francesco, I can check in the evening. >>> >>> LieGrue, >>> strub >>> >>> >>> >>> - Original Message - >>>> From: Francesco Chicchiriccò >>>> To: general@incubator.apache.org >>>> Cc: >>>> Sent: Monday, August 6, 2012 2:49 PM >>>> Subject: Re: [VOTE] Apache Syncope 1.0.0-incubating >>>> >>>> Hi IPMC members, >>>> we are missing a single vote on this release: anyone interested to check? >>>> >>>> TIA. >>>> Regards. >>>> >>>> On 03/08/2012 09:58, Francesco Chicchiriccò wrote: >>>>> I've created a 1.0.0-incubating release, with the following artifacts >>>> up >>>>> for a vote: >>>>> >>>>> SVN source tag (r1367421): >>>>> >>>> https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-incubating/ >>>>> List of changes: >>>>> >>>> https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-incubating/CHANGES >>>>> Maven staging repo: >>>>> https://repository.apache.org/content/repositories/orgapachesyncope-100/ >>>>> >>>>> Source release (checksums and signatures are available at the same >>>>> location): >>>>> >>>> https://repository.apache.org/content/repositories/orgapachesyncope-100/org/apache/syncope/syncope-root/1.0.0-incubating/syncope-root-1.0.0-incubating-source-release.zip >>>>> Staging site: >>>>> http://incubator.apache.org/syncope/1.0.0-incubating/ >>>>> >>>>> PGP release keys (signed using 273DF287): >>>>> http://www.apache.org/dist/incubator/syncope/KEYS >>>>> >>>>> >>>>> This has been voted through on the syncope-...@incubator.apache.org >>>>> mailing list [1], >>>>> and now requires a vote on general@incubator.apache.org >>>>> >>>>> Votes already cast (on syncope-dev): >>>>> >>>>> +1 (binding) >>>>> * Francesco Chicchiriccò >>>>> * Massimiliano Perrone >>>>> * Marco Di Sabatino Di Diodoro >>>>> * Emmanuel Lécharny (IPMC member) >>>>> * Simone Tripodi >>>>> * Colm O hEigeartaigh (IPMC member) >>>>> >>>>> +1 (non binding) >>>>> * Denis Signoretto >>>>> >>>>> >>>>> Vote will be open for 72 hours. >>>>> >>>>> [ ] +1 approve >>>>> [ ] +0 no opinion >>>>> [ ] -1 disapprove (and reason why) >>>>> >>>>> Best regards. >>>>> >>>>> [1] >>>>> >>>> http://syncope-dev.1063484.n5.nabble.com/VOTE-Apache-Syncope-1-0-0-incubating-tp5710173p5710292.html > > -- > Francesco Chicchiriccò > > ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member > http://people.apache.org/~ilgrosso/ > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Syncope 1.0.0-incubating
Hello Francesco, Here are few things I have found via manual inspection: 1. Jquery bundle contains several following strings: "Dual licensed under the MIT or GPL Version 2 licenses." *) source release LICENSE file does not contain MIT license; *) and the file itself does not look like APL licensed; *) and it is a part of the source release. Something should be fixed here, i.e. the files replaced with wget in the build script. 2. ./legal_ext/LICENSE does not have a license for jquery. Does war contain jquery? Don't think these issues are stoppers. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Mon, Aug 6, 2012 at 6:07 PM, Mark Struberg wrote: > Hi Francesco, I can check in the evening. > > LieGrue, > strub > > > > - Original Message - >> From: Francesco Chicchiriccò >> To: general@incubator.apache.org >> Cc: >> Sent: Monday, August 6, 2012 2:49 PM >> Subject: Re: [VOTE] Apache Syncope 1.0.0-incubating >> >> Hi IPMC members, >> we are missing a single vote on this release: anyone interested to check? >> >> TIA. >> Regards. >> >> On 03/08/2012 09:58, Francesco Chicchiriccò wrote: >>> I've created a 1.0.0-incubating release, with the following artifacts >> up >>> for a vote: >>> >>> SVN source tag (r1367421): >>> >> https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-incubating/ >>> >>> List of changes: >>> >> https://svn.apache.org/repos/asf/incubator/syncope/tags/syncope-1.0.0-incubating/CHANGES >>> >>> Maven staging repo: >>> https://repository.apache.org/content/repositories/orgapachesyncope-100/ >>> >>> Source release (checksums and signatures are available at the same >>> location): >>> >> https://repository.apache.org/content/repositories/orgapachesyncope-100/org/apache/syncope/syncope-root/1.0.0-incubating/syncope-root-1.0.0-incubating-source-release.zip >>> >>> Staging site: >>> http://incubator.apache.org/syncope/1.0.0-incubating/ >>> >>> PGP release keys (signed using 273DF287): >>> http://www.apache.org/dist/incubator/syncope/KEYS >>> >>> >>> This has been voted through on the syncope-...@incubator.apache.org >>> mailing list [1], >>> and now requires a vote on general@incubator.apache.org >>> >>> Votes already cast (on syncope-dev): >>> >>> +1 (binding) >>> * Francesco Chicchiriccò >>> * Massimiliano Perrone >>> * Marco Di Sabatino Di Diodoro >>> * Emmanuel Lécharny (IPMC member) >>> * Simone Tripodi >>> * Colm O hEigeartaigh (IPMC member) >>> >>> +1 (non binding) >>> * Denis Signoretto >>> >>> >>> Vote will be open for 72 hours. >>> >>> [ ] +1 approve >>> [ ] +0 no opinion >>> [ ] -1 disapprove (and reason why) >>> >>> Best regards. >>> >>> [1] >>> >> http://syncope-dev.1063484.n5.nabble.com/VOTE-Apache-Syncope-1-0-0-incubating-tp5710173p5710292.html >> >> -- >> Francesco Chicchiriccò >> >> ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member >> http://people.apache.org/~ilgrosso/ >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of DirectMemory as a TLP
+1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Aug 1, 2012 at 10:08 AM, Tommaso Teofili wrote: > +1 > > Tommaso > > 2012/8/1 Tim Williams > >> The DirectMemory community is ready to graduate and become a full TLP. >> We began incubation in October 2011 and have demonstrated our ability >> to function according to the Apache Way. We've successfully made a >> release. We have begun to grow the community. We didn't hold a >> separate formal vote - it's not a requirement - but the sense of the >> community is that we're ready to go[1]. >> >> Please VOTE to submit the below resolution to the board for consideration: >> >> [ ] +1 DirectMemory graduates to TLP >> [ ] -1 DirectMemory isn't ready, because... >> >> Vote will remain open for 72hrs... >> >> Thanks, >> --tim >> >> [1] - http://markmail.org/thread/3j4q7xehzn72dhk4 >> >> >> >> X. Resolution to establish the Apache DirectMemory Project >> >> WHEREAS, the Board of Directors deems it to be in the best >>interests of the Foundation and consistent with the Foundation's >>purpose to establish a Project Management Committee charged with >>the creation and maintenance of open-source software related a >>second level, off-heap, cache able to store large amounts of >> data without filling >>up the Java heap and thus avoiding long garbage collection cycles. >> >>NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>Committee (PMC), to be known as the "The Apache DirectMemory >> Project", >>be and hereby is established pursuant to Bylaws of the >>Foundation; and be it further >> >>RESOLVED, that The Apache DirectMemory Project be and hereby is >>responsible for the creation and maintenance of a software >>project related to a second level off-heap cache; and be it further >> >>RESOLVED, that the office of "Vice President, DirectMemory" be and >>hereby is created, the person holding such office to serve at the >>direction of the Board of Directors as the chair of The Apache >>DirectMemory Project, and to have primary responsibility for >>management of the projects within the scope of responsibility of >>The Apache DirectMemory Project; and be it further >> >>RESOLVED, that the persons listed immediately below be and >>hereby are appointed to serve as the initial members of The >>Apache DirectMemory Project: >> >> * Ioannic Canellos (iocanel) >> * Maurizio Cucchiara (mcucchiara) >> * Christian Grobmeier (grobmeier) >> * Olivier Lamy (olamy) >> * Raffaele P. Guidi (raffaeleguidi) >> * Simone Gianni (simoneg) >> * Simone Tripodi (simonetripodi) >> * Tommaso Teofill (tommaso) >> * Benoit Perroud (bperroud) >> >>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Raffaele P. >>Guidi be and hereby is appointed to the office of Vice >>President, DirectMemory, to serve in accordance with and subject to >>the direction of the Board of Directors and the Bylaws of the >>Foundation until death, resignation, retirement, removal or >>disqualification, or until a successor is appointed; and be it >>further >> >>RESOLVED, that the initial Apache DirectMemory Project be and hereby >>is tasked with the migration and rationalization of the Apache >>Incubator DirectMemory podling; and be it further >> >>RESOLVED, that all responsibility pertaining to the Apache >>Incubator DirectMemory podling encumbered upon the Apache Incubator >>PMC are hereafter discharged. >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.2.0-incubating (RC1)
Hello Richard, folks, Thanks for creating a wonderful project. Could it be that the reference tag at 0.2.0-incubating/src/site/apt/download.apt incorrectly references 0.1.0 release? That's not a showstopper in any case. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Jul 31, 2012 at 9:11 PM, Richard Frovarp wrote: > Thank you very much. Still need one more. > > > On 07/31/2012 02:42 AM, ant elder wrote: >> >> Looks good to me >> >> +1 >> >> ...ant >> >> On Mon, Jul 30, 2012 at 11:43 PM, Richard Frovarp >> wrote: >>> >>> On 07/23/2012 10:44 AM, Richard Frovarp wrote: >>>> >>>> >>>> On 07/09/2012 11:19 AM, Richard Frovarp wrote: >>>>> >>>>> >>>>> A 0.2.0-incubating release candidate has been created. This will be the >>>>> second release of Apache Droids incubating. >>>>> >>>>> We have 3 +1 votes, with 1 +1 IPMC vote (rfrovarp). We are in need of 2 >>>>> more IPMC votes. >>>>> >>>>> Vote thread: >>>>> >>>>> >>>>> http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201206.mbox/%3C4FDAA788.4000400%40apache.org%3E >>>>> >>>>> >>>>> >>>>> Release Notes: >>>>> http://people.apache.org/~rfrovarp/droids/0.2.0-rc1/release-notes.html >>>>> >>>>> The following artifacts are up for a vote: >>>>> >>>>> SVN source tag (r1350453): >>>>> >>>>> https://svn.apache.org/repos/asf/incubator/droids/tags/0.2.0-incubating/ >>>>> >>>>> Maven staging repo: >>>>> https://repository.apache.org/content/repositories/orgapachedroids-238/ >>>>> >>>>> Source release: >>>>> http://people.apache.org/~rfrovarp/droids/0.2.0-rc1/ >>>>> >>>>> PGP release keys (signed using 26B716B3): >>>>> https://svn.apache.org/repos/asf/incubator/droids/KEYS >>>>> >>>>> >>>>> [ ] +1 approve >>>>> [ ] +0 no opinion >>>>> [ ] -1 disapprove (and reason why) >>>> >>>> >>>> >>>> I still need 2 more +1's from the IPMC. I would certainly appreciate any >>>> help. >>> >>> >>> >>> Still in need of 2 more +1's from the IPMC to get the release out. Any >>> help >>> at all is appreciated. >>> >>> Thanks, >>> Richard >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Airavata 0.4-Incubating RC1
Suresh, I am not a lawyer, and cannot yet decide if any of issues is serious enough. Let mentors decide. I'm glad to see that you have cleaned the trunk. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Jul 31, 2012 at 5:59 PM, Suresh Marru wrote: > Hi Alexei, > > Thank you for taking time to review the release. Please see comments below: > > On Jul 29, 2012, at 4:15 PM, Alexei Fedotov wrote: > >> Hello Suresh, >> hope the following questions could make the release better. >> >> 1. Why root NOTICE and LICENSE files are nearly empty, while the files at >> modules/distribution/src/main/resources contain all required info on >> licenses? Why not to move files to the root? > > The root NOTICE & LICENSE are for source code and the ones in > modules/distribution/src/main/resources are for binary release. Since the > source code does not have any third party codes, you will see it have only > APL V2 where as the binary ones include all L&D of all the bundled jars. > >> 2. I have noticed import com.sun.tools.doclets.internal.toolkit.MethodWriter >> at >> modules/ws-messenger/samples/messagebroker/wse-multiple-producers-consumers/src/org/apache/airavata/wsmg/samples/wse/Consumer.java >> >> MethodWriter license seems to be GPL, see below. If the link below is >> correct, we get linking to GPL code. >> http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/com/sun/tools/doclets/internal/toolkit/MethodWriter.java?av=h >> >> It seems the class is not used anyway. Why not to remove it? > > Thanks for this catch, too bad to have this unused import linger through in a > stale sample code. Since it was an unused import and it was not linked to any > code, is it a blocker for the release?, I removed it in the trunk though > (r1367537). >> >> 3. I wonder if the parts of work >> (modules/xbaya-gui/src/main/java/org/apache/airavata/xbaya/ui/graph/system/DifferedInputNodeGUI.java) >> containing APL along with Indiana University Extreme! Lab Software >> License can be just licensed under Apache License in the release (for >> usage simplicity). The initial authors seem to be the same as Apache >> committers. > > Yes your assertion is right, during incubation the IP was donated from > Indiana University to Apache and headers were properly replaced. Tracking > back on the file you pointed out (and couple of others) were added to the > trunk from donation area and added the APL header but a legacy snipped was > left out at the bottom of the files, I removed them now. The RAT check passes > on all the code since all java have APL headers and probably ignored these > stale snippets at the bottom. > > Appreciate your attention to detail. Do you think we should call a new RC or > 2 and 3 are non-blockers for the release? > > Thanks, > Suresh > > >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> On Sun, Jul 29, 2012 at 6:37 PM, Suresh Marru wrote: >>> Apache Airavata (Incubating) is pleased to call for a vote on the following >>> Apache Airavata 0.4-incubating release candidate artifacts: >>> >>> We are requesting a lazy consensus vote, as we have already received 3 >>> binding IPMC +1 votes during the release voting on airavata-dev: >>> >>> Community VOTE & RESULT Thread: http://markmail.org/thread/4nbaxvi5byjpvhgq >>> >>> Detailed change log/release notes: >>> https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.4-incubating/RELEASE_NOTES >>> >>> All Release Artifacts: >>> http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/ >>> >>> PGP release keys (signed using 617DDBAD): >>> https://svn.apache.org/repos/asf/incubator/airavata/KEYS >>> >>> Specific URL's: >>> >>> SVN source tag (1364995): >>> https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.4-incubating/ >>> >>> Source release: >>> http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/airavata-0.4-incubating-source-release.zip >>> >>> Binary Artifacts: >>> http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/apache-airavata-0.4-incubating-bin.tar.gz >>> http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/apache-airavata-0.4-incubating-bin.zip >>> >>> Maven staging repo: >>> https://repository.apache
Re: Resigning as openmeetings mentor
Hello Ross, Let me personally thank you for the effort you spent mentoring our project. I got a great experience from issues you've raised. The initial perception is that Apache process can be easily learned by reading apache.org. More understanding comes from listening to the voice of many other projects around, and this level of understanding is hard to obtain. Correct application of Apache traditions require the knowledge of the story behind the knowledge. Apache continues to grow, and stay a great place to develop software products. This cannot be done without strong culture. Thanks to your efforts, I learned a lot about it. With gratitude, Alexei On Fri, Jul 27, 2012 at 4:57 PM, Ross Gardler wrote: > Recent mails have made it obvious that I no longer have the time or > inclination to mentor OpenMeetings. I therefore step down as a mentor. > > This project is in pretty good shape. It just made a release. The > community is functional. What it really needs is someone to close off > incubation for them and let them manage their own affairs. There are > still two active mentors there so I don't imagine I'll be missed. > > Ross > > -- > Ross Gardler (@rgardler) > Programme Leader (Open Development) > OpenDirective http://opendirective.com > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Blur into the Apache Incubator
+1 (non-binding) 20.07.2012 20:43 пользователь "Aaron McCurry" написал: > I would like to call a vote for accepting Blur for incubation in the > Apache Incubator. The full proposal is available below. > > Please cast your vote: > > [ ] +1, bring Blur into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Blur into Incubator, because... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thank you for your consideration! > > Aaron > > http://wiki.apache.org/incubator/BlurProposal > > = Blur Proposal = > > == Abstract == > Blur is a search platform capable of searching massive amounts of data > in a cloud computing environment. Blur leverages several existing > Apache projects, including Apache Lucene, Apache Hadoop, Apache > !ZooKeeper and Apache Thrift. Both bulk and near real time (NRT) > updates are possible with Blur. Bulk updates are accomplished using > Hadoop Map/Reduce and NRT are performed through direct Thrift calls. > > == Proposal == > Blur is an open source search platform capable of querying massive > amounts of data at incredible speeds. Rather than using the flat, > document-like data model used by most search solutions, Blur allows > you to build rich data models and search them in a semi-relational > manner similar to joins while querying a relational database. Using > Blur, you can get precise search results against terabytes of data at > Google-like speeds. Blur leverages multiple open source projects > including Hadoop, Lucene, Thrift and !ZooKeeper to create an > environment where structured data can be transformed into an index > that runs on a Hadoop cluster. Blur uses the power of Map/Reduce for > bulk indexing into Blur. Server failures are handled automatically by > using !ZooKeeper for cluster state and HDFS for index storage. > > == Background == > Blur was created by Aaron !McCurry in 2010. Blur was developed to > solve the challenges in dealing with searching huge quantities of data > that the traditional RDBMS solutions could not cope with while still > providing JOIN-like capabilities to query the data. Several other > open source projects have implemented aspects of this design including > elasticsearch, Katta and Apache Solr. > > == Rationale == > There is a need for a distributed search capability within the Hadoop > ecosystem. Currently, there are no other search solutions that > natively leverage HDFS and the failover features of Hadoop in the same > manner as the Blur project. The communities we expect to be most > interested in such a project are government, health care, and other > industries where scalability is a concern. We have made much progress > in developing this project over the past 2 years and believe both the > project and the interested communities would benefit from this work > being openly available and having open development. In future > versions of Blur the API will more closely follow the API’s provided > in Lucene so that systems that already use Lucene can more easily > scale with Blur. Blur can be viewed as a query execution engine that > Lucene based solutions can utilize when scale becomes an issue. > > == Initial Goals == > The initial goals of the project are: > * To migrate the Blur codebase, issue tracking and wiki from > github.com and integrate the project with the ASF infrastructure. > * Add new committers to the project and grow the community in "The Apache > Way". > > == Current Status == > > === Meritocracy === > Blur was initially developed by Aaron !McCurry in June 2010. Since > then Blur has continued to evolve with the support of a small > development team at Near Infinity. As a part of the Apache Software > Foundation, the Apache Blur team intends to strongly encourage the > community to help with and contribute to the project. Apache Blur > will actively seek potential committers and help them become familiar > with the codebase. > > === Community === > A small community has developed around Blur and several project teams > are currently using Blur for their big data search capability. The > source code is currently available on GitHub and there is a dedicated > website (blur.io) that provides an overview of the project. Blur has > been shared with several members of the Apache community and has been > presented at the Bay Area HUG (see > http://www.meetup.com/hadoop/events/20109471/). > > === Core Developers === > The current developers are employed by Near Infinity Corporation, but > we anticipate interest developing among other companies. > > === Alignment === > Blur is built on top of a number of Apache projects; Hadoop, Lucene, > !ZooKeeper, and Thrift. It builds with Maven. During the course of > Blur development, a couple of patches have been committed back to the > Lucene project, including LUCENE-2205 and LUCENE-2215. Due to the > strong relationship with the before mentioned Apache projects, the > incubator is a good match for Blur. > > ==
Re: [VOTE] Apache Airavata 0.4-Incubating RC1
Hello Suresh, hope the following questions could make the release better. 1. Why root NOTICE and LICENSE files are nearly empty, while the files at modules/distribution/src/main/resources contain all required info on licenses? Why not to move files to the root? 2. I have noticed import com.sun.tools.doclets.internal.toolkit.MethodWriter at modules/ws-messenger/samples/messagebroker/wse-multiple-producers-consumers/src/org/apache/airavata/wsmg/samples/wse/Consumer.java MethodWriter license seems to be GPL, see below. If the link below is correct, we get linking to GPL code. http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/com/sun/tools/doclets/internal/toolkit/MethodWriter.java?av=h It seems the class is not used anyway. Why not to remove it? 3. I wonder if the parts of work (modules/xbaya-gui/src/main/java/org/apache/airavata/xbaya/ui/graph/system/DifferedInputNodeGUI.java) containing APL along with Indiana University Extreme! Lab Software License can be just licensed under Apache License in the release (for usage simplicity). The initial authors seem to be the same as Apache committers. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sun, Jul 29, 2012 at 6:37 PM, Suresh Marru wrote: > Apache Airavata (Incubating) is pleased to call for a vote on the following > Apache Airavata 0.4-incubating release candidate artifacts: > > We are requesting a lazy consensus vote, as we have already received 3 > binding IPMC +1 votes during the release voting on airavata-dev: > > Community VOTE & RESULT Thread: http://markmail.org/thread/4nbaxvi5byjpvhgq > > Detailed change log/release notes: > https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.4-incubating/RELEASE_NOTES > > All Release Artifacts: > http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/ > > PGP release keys (signed using 617DDBAD): > https://svn.apache.org/repos/asf/incubator/airavata/KEYS > > Specific URL's: > > SVN source tag (1364995): > https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.4-incubating/ > > Source release: > http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/airavata-0.4-incubating-source-release.zip > > Binary Artifacts: > http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/apache-airavata-0.4-incubating-bin.tar.gz > http://people.apache.org/builds/incubator/airavata/0.4-incubating/RC1/apache-airavata-0.4-incubating-bin.zip > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapacheairavata-072/ > > Please verify the artifacts and vote. The vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve Openmeetings (Incubating) release
Dave, tanks for the tip. I highly respect all Apache members (regardless of actual "member" status") and their (your, our) time. I thank all the thread participants who find their time to help the release despite being busy and those who wrote a private reply as well. As for the patience, the Openmeetings proposal to general@ is dated Oct 27, 2009. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jul 26, 2012 at 3:37 AM, Dave Fisher wrote: > HI Alexei, > > It seems that you have sent various requests in advance of this one through > channels other than general@. This is not appreciated by busy people who do > read general@. > > Please have patience, the Incubator release process can take some time. IPMC > members are busy volunteers many of whom are mentoring other podlings. > > See: http://www.apache.org/dev/contrib-email-tips.html item #5 > > Thanks for your consideration and good luck with OpenMeetings, I'm told it's > really cool. > > Regards, > Dave > > On Jul 25, 2012, at 2:20 AM, Alexei Fedotov wrote: > >> Senaka, folks, release has not been deployed to the official page yet - we >> need an approve first. >> >> Here are few links to release artifacts: >> >> Main changes are covered in the Readme: >> http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC4/README >> >> Full Changelog: >> http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC4/CHANGELOG >> >> Release bundles: http://people.apache.org/~sebawagner/2.0RC4/ >> >> Tag: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC4/ >> >> PGP release keys (signed using 93A30395): >> http://www.apache.org/dist/incubator/openmeetings/KEYS >> >> Senaka, thanks for asking for clarification! >> 23.07.2012 17:03 пользователь "Alexei Fedotov" >> написал: >> >>> The Openmeetings community voted on and has approved a proposal to release >>> Openmeetings 2.0. Pursuant to the Releases section of the Incubation >>> Policy and with the endorsement of two of our mentors we would now >>> like to request the permission of the Incubator PMC to publish the >>> release on the Download page. >>> >>> Please vote by 26 July 10 AM GMT >>> >>> Thanks, >>> Alexei >>> >>> Proposal: >>> http://markmail.org/message/aahmijcb5dsjlxiv >>> >>> Vote result: >>> http://markmail.org/message/azenwwlcfhnxmysf >>> >>> Download page: >>> http://www.apache.org/dist/incubator/openmeetings >>> >>> Releases section of the Incubation Policy: >>> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases >>> >>> Demos & Kittens >>> http://markmail.org/message/oqj3eko732rx2cgy >>> >>> >>> >>> On Mon, Jul 23, 2012 at 11:50 AM, Alexei Fedotov >>> wrote: >>>> >>>> Jukka, thanks for explaining. >>>> >>>> Ross, Andrus, >>>> would you please consider voting for the Openmeetings release? We are >>> stuck with insufficient number of votes. Thanks! >>>> >>>> Incubator folks, >>>> Don't allow another little cute kitten and fluffy puppy die by missing >>> Apache Openmeetings (Incubating) release: >>>> http://demo.openmeetings.de/openmeetings/ >>>> http://demo.dataved.ru/openmeetings/ >>>> >>>> You are mostly welcome to support our release here >>>> http://markmail.org/message/azenwwlcfhnxmysf >>>> >>>> >>>> -- >>>> With best regards / с наилучшими пожеланиями, >>>> Alexei Fedotov / Алексей Федотов, >>>> http://dataved.ru/ >>>> +7 916 562 8095 >>>> >>>> >>>> >>>> On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting >>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov >>>>> wrote: >>>>>> The release vote have successfully passed and forwarded to general@ >>>>>> list [1]. What should be our next step? Have we got Incubator PMC >>>>>> approval? Can we proceed with wider distribution? >>>>> >>>>> See >>> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases >>>>> for the Incubator policy on releases. You're almost done, just an >>>>> extra approval vote on general@ is still needed (and since you already >>>>> have two mentor +1s, you only need one more IPMC member to vote for >>>>> the release). >>>>> >>>>> BR, >>>>> >>>>> Jukka Zitting >>>>> >>>>> - >>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>> >>>> >>> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve Openmeetings (Incubating) release
Senaka, folks, release has not been deployed to the official page yet - we need an approve first. Here are few links to release artifacts: Main changes are covered in the Readme: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC4/README Full Changelog: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC4/CHANGELOG Release bundles: http://people.apache.org/~sebawagner/2.0RC4/ Tag: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC4/ PGP release keys (signed using 93A30395): http://www.apache.org/dist/incubator/openmeetings/KEYS Senaka, thanks for asking for clarification! 23.07.2012 17:03 пользователь "Alexei Fedotov" написал: > The Openmeetings community voted on and has approved a proposal to release > Openmeetings 2.0. Pursuant to the Releases section of the Incubation > Policy and with the endorsement of two of our mentors we would now > like to request the permission of the Incubator PMC to publish the > release on the Download page. > > Please vote by 26 July 10 AM GMT > > Thanks, > Alexei > > Proposal: > http://markmail.org/message/aahmijcb5dsjlxiv > > Vote result: > http://markmail.org/message/azenwwlcfhnxmysf > > Download page: > http://www.apache.org/dist/incubator/openmeetings > > Releases section of the Incubation Policy: > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > > Demos & Kittens > http://markmail.org/message/oqj3eko732rx2cgy > > > > On Mon, Jul 23, 2012 at 11:50 AM, Alexei Fedotov > wrote: > > > > Jukka, thanks for explaining. > > > > Ross, Andrus, > > would you please consider voting for the Openmeetings release? We are > stuck with insufficient number of votes. Thanks! > > > > Incubator folks, > > Don't allow another little cute kitten and fluffy puppy die by missing > Apache Openmeetings (Incubating) release: > > http://demo.openmeetings.de/openmeetings/ > > http://demo.dataved.ru/openmeetings/ > > > > You are mostly welcome to support our release here > > http://markmail.org/message/azenwwlcfhnxmysf > > > > > > -- > > With best regards / с наилучшими пожеланиями, > > Alexei Fedotov / Алексей Федотов, > > http://dataved.ru/ > > +7 916 562 8095 > > > > > > > > On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting > wrote: > >> > >> Hi, > >> > >> On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov > >> wrote: > >> > The release vote have successfully passed and forwarded to general@ > >> > list [1]. What should be our next step? Have we got Incubator PMC > >> > approval? Can we proceed with wider distribution? > >> > >> See > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > >> for the Incubator policy on releases. You're almost done, just an > >> extra approval vote on general@ is still needed (and since you already > >> have two mentor +1s, you only need one more IPMC member to vote for > >> the release). > >> > >> BR, > >> > >> Jukka Zitting > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > > >
Re: Your vote is casting Was: Openmeetings release approval by Incubator PMC Was: Incubation state transitions and stuck projects (Was: February report review)
Andrus, thanks! We also have a shepherd. Matt, aren't you, by chance, IPMC? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Mon, Jul 23, 2012 at 5:33 PM, Andrus Adamchik wrote: > Hi Alexei, > > I am listed as a mentor in error at > http://incubator.apache.org/projects/openmeetings.html . I was the champion > on the proposal. But even though I like the project, I knew I wouldn't be > able to lead you through incubator and give all needed attention due to other > commitments. So I indicated back then that I am stepping down after incubator > entry. So I guess we should take my name from the mentor list. > > Having said that, I'll be happy to lend a hand on this occasion and I am > still an IPMC member. Just give me some time to evaluate the release. > > One more note - you actually need 2 more votes. Only Egor's (yegor) vote is > binding. You are listed as a mentor, but you don't appear to be an IPMC > member. This means we'll need help from Ross and/or Jim. And maybe we can > enroll new mentors. Anyone? > > Andrus > > > On Jul 23, 2012, at 7:50 AM, Alexei Fedotov wrote: >> Jukka, thanks for explaining. >> >> Ross, Andrus, >> would you please consider voting for the Openmeetings release? We are stuck >> with insufficient number of votes. Thanks! >> >> Incubator folks, >> Don't allow another little cute kitten and fluffy puppy die by missing >> Apache Openmeetings (Incubating) release: >> http://demo.openmeetings.de/openmeetings/ >> http://demo.dataved.ru/openmeetings/ >> >> You are mostly welcome to support our release here >> http://markmail.org/message/azenwwlcfhnxmysf >> >> >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://dataved.ru/ >> +7 916 562 8095 >> >> >> >> On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting >> wrote: >> >>> Hi, >>> >>> On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov >>> wrote: >>>> The release vote have successfully passed and forwarded to general@ >>>> list [1]. What should be our next step? Have we got Incubator PMC >>>> approval? Can we proceed with wider distribution? >>> >>> See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases >>> for the Incubator policy on releases. You're almost done, just an >>> extra approval vote on general@ is still needed (and since you already >>> have two mentor +1s, you only need one more IPMC member to vote for >>> the release). >>> >>> BR, >>> >>> Jukka Zitting > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Approve Openmeetings (Incubating) release
The Openmeetings community voted on and has approved a proposal to release Openmeetings 2.0. Pursuant to the Releases section of the Incubation Policy and with the endorsement of two of our mentors we would now like to request the permission of the Incubator PMC to publish the release on the Download page. Please vote by 26 July 10 AM GMT Thanks, Alexei Proposal: http://markmail.org/message/aahmijcb5dsjlxiv Vote result: http://markmail.org/message/azenwwlcfhnxmysf Download page: http://www.apache.org/dist/incubator/openmeetings Releases section of the Incubation Policy: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Demos & Kittens http://markmail.org/message/oqj3eko732rx2cgy On Mon, Jul 23, 2012 at 11:50 AM, Alexei Fedotov wrote: > > Jukka, thanks for explaining. > > Ross, Andrus, > would you please consider voting for the Openmeetings release? We are stuck > with insufficient number of votes. Thanks! > > Incubator folks, > Don't allow another little cute kitten and fluffy puppy die by missing Apache > Openmeetings (Incubating) release: > http://demo.openmeetings.de/openmeetings/ > http://demo.dataved.ru/openmeetings/ > > You are mostly welcome to support our release here > http://markmail.org/message/azenwwlcfhnxmysf > > > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > > On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting > wrote: >> >> Hi, >> >> On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov >> wrote: >> > The release vote have successfully passed and forwarded to general@ >> > list [1]. What should be our next step? Have we got Incubator PMC >> > approval? Can we proceed with wider distribution? >> >> See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases >> for the Incubator policy on releases. You're almost done, just an >> extra approval vote on general@ is still needed (and since you already >> have two mentor +1s, you only need one more IPMC member to vote for >> the release). >> >> BR, >> >> Jukka Zitting >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Your vote is casting Was: Openmeetings release approval by Incubator PMC Was: Incubation state transitions and stuck projects (Was: February report review)
Jukka, thanks for explaining. Ross, Andrus, would you please consider voting for the Openmeetings release? We are stuck with insufficient number of votes. Thanks! Incubator folks, Don't allow another little cute kitten and fluffy puppy die by missing Apache Openmeetings (Incubating) release: http://demo.openmeetings.de/openmeetings/ http://demo.dataved.ru/openmeetings/ You are mostly welcome to support our release here http://markmail.org/message/azenwwlcfhnxmysf -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting wrote: > Hi, > > On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov > wrote: > > The release vote have successfully passed and forwarded to general@ > > list [1]. What should be our next step? Have we got Incubator PMC > > approval? Can we proceed with wider distribution? > > See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > for the Incubator policy on releases. You're almost done, just an > extra approval vote on general@ is still needed (and since you already > have two mentor +1s, you only need one more IPMC member to vote for > the release). > > BR, > > Jukka Zitting > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Openmeetings release approval by Incubator PMC Was: Incubation state transitions and stuck projects (Was: February report review)
[cc-ed to dev@ and changed the subject] Hello Jukka, You wrote: > IP clearance -> No release:Openmeetings The release vote have successfully passed and forwarded to general@ list [1]. What should be our next step? Have we got Incubator PMC approval? Can we proceed with wider distribution? [1] http://markmail.org/message/azenwwlcfhnxmysf -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sun, Jul 15, 2012 at 7:15 AM, Jukka Zitting wrote: > Hi, > > On Thu, Feb 9, 2012 at 4:59 PM, Jukka Zitting wrote: >> My suggestion is to ask the podlings now in category 2 to report again >> in May on their progress on the identified blockers. If there's been >> no measurable progress by then, we'll dig deeper to see what we can >> do. Podlings reporting in other months can be picked up for a similar >> oversight cycle over the coming months. By July we should then have a >> pretty accurate record of progress throughout the entire Incubator, >> including a clear list of podlings that are stuck and need help. > > Following up on this, here's a quick graph I put together when > preparing for this month's board report: http://twitpic.com/a7o368 > > The graph shows how podlings have moved from one (subjective) > categorization to another (or to graduation/retirement) between their > two scheduled reports in the February-July time frame (I'm only > counting projects that were already past their first three months at > the Incubator). The edge width is proportional to the number of > podlings that made that particular "state change". The Graphviz source > of the graph is included at the end of this message. > > The overall picture looks pretty good. We have strong movement towards > graduation, and so far no regressions from the "ready to graduate" > state back to low activity or diversity. > > Here's the list of projects that stayed at the same category from one > report to the next: > > IP clearance: Amber > No release:Any23, Bloodhound, Cordova, JSPWiki > Low activity: Ambari, AWF, EasyAnt, Kitty, Nuvem, PhotArk, Kato > Low diversity: Airavata, Bigtop, Chukwa, Tashi > Ready to graduate: Flume, Lucene.NET, NPanday > > The IP clearance issue in Amber seems to be finally resolved ( LEGAL-134). > > The release issues are being resolved, as Any23 has just passed a > release vote and I've seen good progress towards an Apache release in > both Cordova and JSPWiki. I don't know the release status in > Bloodhound. > > The low activity projects remain a problem though there are a few > projects who've managed to escape that trap. For the rest we need to > find solutions. Kato was already retired, and AWF and Kitty getting > there. EasyAnt might go the subproject route, and PhotArk has been > showing increased activity lately. I don't know what's going on in > Ambari or Nuvem. > > The low diversity "state" is a bit vague catchall category for > projects that don't yet feel ready to graduate. I'm not too concerned > if some projects take a bit longer there as long as they don't regress > to low activity. Once a project has hit the "low diversity" category, > chances are quite high that it'll end up graduating. > > The podlings that were "ready to graduate" for more than three months > are a bit mixed story. Flume already graduated and Lucene.NET is just > about to, but NPanday looks to be in trouble as activity there seems > to have plummeted since May for some reason. > > BR, > > Jukka Zitting > > > > /* > IP clearance -> IP clearance: Amber > IP clearance -> No release:Openmeetings > No release-> No release:Any23, Bloodhound, Cordova, JSPWiki > No release-> Low diversity: Mesos > No release-> Ready to graduate: Clerezza, DirectMemory, > OpenOffice, Stanbol > Low activity -> Low activity: Ambari, AWF, EasyAnt, Kitty, > Nuvem, PhotArk, Kato > Low activity -> Retire:Kalumet, Zeta Components > Low activity -> No release:Celix, VXQuery > Low activity -> Low diversity: SIS > Low activity -> Ready to graduate: Wink > Low diversity -> Low activity: Droids, ODF Toolkit > Low diversity -> Low diversity: Airavata, Bigtop, Chukwa, Tashi > Low diversity -> No release:S4, Wave > Low diversity -> Ready to graduate: Etch, HCatalog, Isis, Kafka, > Oozie, VCL, Wookie > Low diversity -> Graduate:
Re: Incubation state transitions and stuck projects (Was: February report review)
Hello Jukka, You wrote: > IP clearance -> No release:Openmeetings The release vote have successfully passed and forwarded to general@ list [1]. What should be our next step? Have we got Incubator PMC approval? Can we proceed with wider distribution? [1] http://markmail.org/message/azenwwlcfhnxmysf -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sun, Jul 15, 2012 at 7:15 AM, Jukka Zitting wrote: > Hi, > > On Thu, Feb 9, 2012 at 4:59 PM, Jukka Zitting wrote: >> My suggestion is to ask the podlings now in category 2 to report again >> in May on their progress on the identified blockers. If there's been >> no measurable progress by then, we'll dig deeper to see what we can >> do. Podlings reporting in other months can be picked up for a similar >> oversight cycle over the coming months. By July we should then have a >> pretty accurate record of progress throughout the entire Incubator, >> including a clear list of podlings that are stuck and need help. > > Following up on this, here's a quick graph I put together when > preparing for this month's board report: http://twitpic.com/a7o368 > > The graph shows how podlings have moved from one (subjective) > categorization to another (or to graduation/retirement) between their > two scheduled reports in the February-July time frame (I'm only > counting projects that were already past their first three months at > the Incubator). The edge width is proportional to the number of > podlings that made that particular "state change". The Graphviz source > of the graph is included at the end of this message. > > The overall picture looks pretty good. We have strong movement towards > graduation, and so far no regressions from the "ready to graduate" > state back to low activity or diversity. > > Here's the list of projects that stayed at the same category from one > report to the next: > > IP clearance: Amber > No release:Any23, Bloodhound, Cordova, JSPWiki > Low activity: Ambari, AWF, EasyAnt, Kitty, Nuvem, PhotArk, Kato > Low diversity: Airavata, Bigtop, Chukwa, Tashi > Ready to graduate: Flume, Lucene.NET, NPanday > > The IP clearance issue in Amber seems to be finally resolved ( LEGAL-134). > > The release issues are being resolved, as Any23 has just passed a > release vote and I've seen good progress towards an Apache release in > both Cordova and JSPWiki. I don't know the release status in > Bloodhound. > > The low activity projects remain a problem though there are a few > projects who've managed to escape that trap. For the rest we need to > find solutions. Kato was already retired, and AWF and Kitty getting > there. EasyAnt might go the subproject route, and PhotArk has been > showing increased activity lately. I don't know what's going on in > Ambari or Nuvem. > > The low diversity "state" is a bit vague catchall category for > projects that don't yet feel ready to graduate. I'm not too concerned > if some projects take a bit longer there as long as they don't regress > to low activity. Once a project has hit the "low diversity" category, > chances are quite high that it'll end up graduating. > > The podlings that were "ready to graduate" for more than three months > are a bit mixed story. Flume already graduated and Lucene.NET is just > about to, but NPanday looks to be in trouble as activity there seems > to have plummeted since May for some reason. > > BR, > > Jukka Zitting > > > > /* > IP clearance -> IP clearance: Amber > IP clearance -> No release:Openmeetings > No release-> No release:Any23, Bloodhound, Cordova, JSPWiki > No release-> Low diversity: Mesos > No release-> Ready to graduate: Clerezza, DirectMemory, > OpenOffice, Stanbol > Low activity -> Low activity: Ambari, AWF, EasyAnt, Kitty, > Nuvem, PhotArk, Kato > Low activity -> Retire:Kalumet, Zeta Components > Low activity -> No release:Celix, VXQuery > Low activity -> Low diversity: SIS > Low activity -> Ready to graduate: Wink > Low diversity -> Low activity: Droids, ODF Toolkit > Low diversity -> Low diversity: Airavata, Bigtop, Chukwa, Tashi > Low diversity -> No release:S4, Wave > Low diversity -> Ready to graduate: Etch, HCatalog, Isis, Kafka, > Oozie, VCL, Wookie > Low diversity -> Graduate: Hama, MRUnit > Ready to graduate -&
Re: [VOTE] Accept Openmeetings to Apache Incubator
+1 (non-binding) -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 8, 2011 at 8:08 PM, Kalle Korhonen wrote: > +1 (non-binding) > > On Mon, Nov 7, 2011 at 10:53 PM, Andrus Adamchik > wrote: >> Opemeetings proposal has been discussed a few times here before. The group >> of developers behind it worked hard (and succeeded) to address all potential >> obstacles to the Incubator acceptance and to the following incubation. They >> even went an extra mile and collected all ICLAs in adbvance. >> >> So now I am starting the vote to accept Openmeetings to Apache Incubator. >> >> The proposal is also available at: >> http://wiki.apache.org/incubator/OpenmeetingsProposal >> >> Please cast your votes: >> >> [ ] +1 Accept Openmeetings for incubation >> [ ] +0 Don't care >> [ ] -1 Reject for the following reason: >> >> The vote is open for 72 hours. >> >> Andrus >> >> --- >> Andrus Adamchik >> Apache Cayenne ORM: http://cayenne.apache.org/ >> Twitter: http://twitter.com/andrus_a >> >> >> >> --- >> >> == OpenMeetings Project Proposal == >> >> == Abstract == >> Openmeetings is a web conferencing solution. >> >> == Proposal == >> Openmeetings provides video conferencing, instant messaging, white board, >> collaborative document editing and other groupware tools using API functions >> of the Red5 Streaming Server for Remoting and Streaming. >> >> == Background == >> Openmeetings was developed since 2007 by Sebastian Wagner and willing >> developers. The project ships a release approximately once per quarter. It >> was developed using LGPL license, and developers are currently thinking of >> re-licensing it under Apache License 2.0. >> >> The project started as module by Sebastian Wagner for an ELearning platform >> (Dokeos) and was then split into a separated project. That is the reason why >> there is a strong relation to educational institutions that are using >> OpenMeetings and there are integrations for platforms like Moodle, ATutor, >> Sakai, STudIP or ILias available >> (http://code.google.com/p/openmeetings/wiki/MoodlePlugins). The relation to >> educational institutions also subsequently lead to some projects funded by >> the EU where OpenMeetings was involved, for example by the Swedish/Finnish >> Centre of Open-Source !OpenKarken (Case-Study about the EU project at >> OSOR.eu: http://www.osor.eu/studies/finland-and-sweden-collaborate-using-oss >> ) >> >> The integration and internationalization of the project was a primary focus >> right from the start of the project. Since Version 0.5 there is a >> Language-Editor (http://code.google.com/p/openmeetings/wiki/LanguageEditor) >> to edit labels, export and import them as XML and you can use those XML >> files for future installations (or contribute it to the community). There >> are currently around 30 languages available. Since version 0.5.1 there is >> also a SOAP API to integrate !OpenMeetings. We constantly improve this >> SOAP/REST API (http://code.google.com/p/openmeetings/wiki/SoapMethods) with >> new functionality with a strong focus on security and usability. The >> auth-mechnism is quite similar to OAuth, you create some token and then >> assign rights to the token. (Documentation for Single Sign On: >> http://code.google.com/p/openmeetings/wiki/DirectLoginSoapGeneralFlow) >> >> The project name "!OpenMeetings" and logos are inspired by Ludovic Gasc who >> has been the project manager at Dokeos at the time Sebastian split >> !OpenMeetings as separated project. >> >> Red5 Server provides an "Edge-Orion-Clustering" >> (http://trac.red5.org/wiki/Documentation/Tutorials/EdgeOriginClusteringConfiguration). >> We hope to extend this clustering solution with support for rtmpt and >> rtmps and integrate that into our application as native clustering option. >> >> == Rationale == >> Last year most major vendors started commercial web conferencing solutions. >> This is an important part of software ecosystem, and there is an urge to >> consolidate open source development efforts in this direction. >> >> According to several studies demand for synchronous Communication, in >> opposite to asynchronous Communication like wiki's or email, will raise the >> upcoming years. For example Gartner promises that 2011 the market will grow >> 20% according to their "Ma
Re: Last Bluesky report
Hello Chris, guys, I wonder if any of former BlueSky mentors can help us with Openmeetings incubation [1]. Openmeetings was born as e-learning platform, most of our users come from educational institutions. Also if BlueSky code contribution has appropriate paperwork around, I can look into it to check if some stable and useful project libraries can be added into the Openmeetings codebase. [1] http://wiki.apache.org/incubator/OpenmeetingsProposal -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Aug 3, 2011 at 7:54 AM, Henri Yandell wrote: > On Mon, Aug 1, 2011 at 9:34 PM, Henri Yandell wrote: >> Complete action items: >> >> * Moved to retired table on Incubator project page. >> * JIRA now read-only. >> * SVN now read-only. To be deleted. > > SVN now deleted. > >> * Project page indicates retirement. >> * Dropped from Incubator website RHS nav. >> * Removed from reporting schedule. >> >> To do: >> >> * Make wiki read-only. > > Nothing to do here. > >> * Close mailing lists. > > Bertrand has an issue open for this > (https://issues.apache.org/jira/browse/INFRA-3785). > >> * Keep website or remove? > > Website removed. I checked in the two txt documents that were on the > site but not in svn. > > Hen > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Daniel, Thank you for an excellent report! -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jul 28, 2011 at 10:20 PM, dsh wrote: > Hi, > > please find my feedback below: > > OS X Lion: > > * tested with: > ** Firefox 5.0.1 and Adobe Flash Player 10.3 > ** Safari 5.1 and Adobe Flash Player 10.3 > * Observations: > ** Openmeetings did not work with Firefox/Safari if using a webcam/mic > cause on the adobe flash player settings dialog it was not possible to > click allow nor deny > ** In Safari clicking the share/record screen button N times did open > the screen sharing app N times (maybe you want to check whether an > instance of the app is already running) > ** I understand if sharing screens everybody has control over your > screen. you may consider adding a view only mode too. > ** you might check while signing up whether popup blockers are active. > if yes you could prompt the user to disable popup blockers first > before signing in. > ** pressing the share/record screen button opens a new, blank window > just to download the JNLP app. maybe you want to change that to not > open a separate window that needs to be closed after starting the JNLP > app > ** It looks like after stopping screen sharing the shared screen still > remains on each participants screen. Maybe it would make sense to > provide a message to each participant that the host stopped sharing > its screen. > > OS X Snow Leopard: > > * tested with: > ** Firefox 5.0.1 and Adobe Flash Player 10.3 > ** Safari 5.1 and Adobe Flash Player 10.3 > * Observations: > ** Openmeetings did not work with Firefox cause the initial screen did > not load after signing up > ** In Safari clicking the share/record screen button N times did open > the screen sharing app N times (maybe you want to check whether an > instance of the app is already running) > ** I understand if sharing screens everybody has control over your > screen. you may consider adding a view only mode too. > ** you might check while signing up whether popup blockers are active. > if yes you could prompt the user to disable popup blockers first > before signing in. > ** pressing the share/record screen button opens a new, blank window > just to download the JNLP app. maybe you want to change that to not > open a separate window that needs to be closed after starting the JNLP > app > ** It looks like after stopping screen sharing the shared screen still > remains on each participants screen. Maybe it would make sense to > provide a message to each participant that the host stopped sharing > its screen. > > Windows 7 Ultimate: > > * tested with: > ** Firefox 4.0.1 and Adobe Flash Player 10.3 > ** Firefox 5.0.1 and Adobe Flash Player 10.3 > ** Safari 5.1 and Adobe Flash Player 10.3 > * Observations: > ** In Firefox clicking the share/record screen button N times did open > the screen sharing app N times (maybe you want to check whether an > instance of the app is already running) > ** I understand if sharing screens everybody has control over your > screen. you may consider adding a view only mode too. > ** you might check while signing up whether popup blockers are active. > if yes you could prompt the user to disable popup blockers first > before signing in. > ** In Safari signing up did open a new window instead of opening a new > tab which is different to Firefox"s behaviour (maybe this can be > changed in the Safari prefs) > ** pressing the share/record screen button opens a new, blank window > just to download the JNLP app. maybe you want to change that to not > open a separate window that needs to be closed after starting the JNLP > app > ** It looks like after stopping screen sharing the shared screen still > remains on each participants screen. Maybe it would make sense to > provide a message to each participant that the host stopped sharing > its screen. > > Fedora Core 15 Gnome Edition: > > * tested with: > ** Firefox 4.0.1 and Adobe Flash Player 11 > * Observations: > * I had to download the JNLP file and execute it using javaws on the > command line. Did expect it would be run more seamlessly cause the > IcedTea-Web plug-in is installed > ** In Firefox clicking the share/record screen button N times did open > the screen sharing app N times (maybe you want to check whether an > instance of the app is already running) > ** I understand if sharing screens everybody has control over your > screen. you may consider adding a view only mode too. > ** you might check while signing up whether popup blockers are active. > if yes you could prompt the user to disable popup blockers first > before signing in. > *
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Mohammad, Any impressions to share? Have you occasionally faced any bugs? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 2011/7/25 Mohammad Nour El-Din : > +1 for the proposal > > I tried it out. It looks very promising :). > > 2011/7/25 seba.wag...@gmail.com : >> Hi, >> >> thanks for your feedback! >> @Scott: I think so too. Synchrious communication could become an >> standard feature of Social Networking Platforms. Lets see if there is >> an API in Rave for integration. >> >> Sebastian >> >> 2011/7/23 Maurizio Cucchiara : >>> Good idea!!! I had the opportunity to try OM, nice tool! >>> >>> Maurizio Cucchiara >>> >>> Il giorno 23/lug/2011 17.57, "Scott Wilson" >>> ha scritto: >>>> Fantastic proposal. It would be even more fantastic to link it up with >>> Rave and Wookie! >>>> >>>> +1 (non-binding) >>>> >>>> S >>>> >>>> On 23 Jul 2011, at 16:25, Jim Jagielski wrote: >>>> >>>>> V. cool. Big +1 >>>>> >>>>> Let me know how I can help. >>>>> >>>>> On Jul 21, 2011, at 9:40 AM, seba.wag...@gmail.com wrote: >>>>> >>>>>> We would like to propose Openmeetings project to join the incubator. >>>>>> >>>>>> Full Proposal: >>>>>> http://wiki.apache.org/incubator/OpenmeetingsProposal >>>>>> >>>>>> Quick summary: >>>>>> OpenMeetings is Web Conferencing application that fits into >>>>>> educational or business sector. You can make conference sessions in >>>>>> different room-types with up to 100 peoples in a Room. It contains all >>>>>> main features of Web Conferencing: Audio/Video, Whiteboard, Screen >>>>>> Sharing, Chat and Moderation System. It is translated into more then >>>>>> 30 languages and its a basic goal of OpenMeetings to be easy to embed >>>>>> into existing environments. It already uses many of Apache >>>>>> Technologies like Tomcat, Mina, Velocity, Commons, ... >>>>>> >>>>>> As you can see below the last time we did the proposal we had >>>>>> Hibernate in our software stack, we did refactor the hole project and >>>>>> use openJPA now. >>>>>> So that one should be no more blocker to it. >>>>>> Red5 is used like a Servlet container and licensed under the LGPL, >>>>>> Red5 can be obtained for example from the Debian Repository: >>>>>> http://packages.debian.org/wheezy/red5-server >>>>>> >>>>>> You may find all existing documents and further material on the >>>>>> GoogleCode pages: http://code.google.com/p/openmeetings/ >>>>>> >>>>>> We appreciate any feedback and comments on the proposal. >>>>>> >>>>>> Sebastian Wagner >>>>>> >>>>>> 2009/11/9 Ross Gardler : >>>>>>> Just as a point of interest, I just completed a test meeting using >>>>>>> OpenMeetings across three sites using the demo server. >>>>>>> >>>>>>> I was suitably impressed by the project. It has a few annoying >>>>>>> limitations, but as an online meeting tool it is very good. to the >>>>>>> extent that I will almost certainly be installing a copy on our own >>>>>>> servers. I would be very happy to see it coming into the incubator and >>>>>>> would be willing to be a mentor, assuming the legal issues are not >>>>>>> blockers. >>>>>>> >>>>>>> Ross >>>>>>> >>>>>>> 2009/11/3 Alexei Fedotov : >>>>>>>> Noel, >>>>>>>> Regarding Theora codec, I have checked the page [1]. Currently, there >>>>>>>> are no products which successfully use the codec for video >>>>>>>> communication. Video-phone encodes and decodes the stream in >>>>>>>> real-time, adopts the quality with regard to network conditions (e.g. >>>>>>>> lost packet rate) and tries to minimize subjective effects of network >>>>>>>> errors - the list of requirements is broader than for media players >>>>&
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
+1 Jim, folks, as for help, we are looking for Apache member who may become a project champion. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 2011/7/23 Jim Jagielski : > V. cool. Big +1 > > Let me know how I can help. > > On Jul 21, 2011, at 9:40 AM, seba.wag...@gmail.com wrote: > >> We would like to propose Openmeetings project to join the incubator. >> >> Full Proposal: >> http://wiki.apache.org/incubator/OpenmeetingsProposal >> >> Quick summary: >> OpenMeetings is Web Conferencing application that fits into >> educational or business sector. You can make conference sessions in >> different room-types with up to 100 peoples in a Room. It contains all >> main features of Web Conferencing: Audio/Video, Whiteboard, Screen >> Sharing, Chat and Moderation System. It is translated into more then >> 30 languages and its a basic goal of OpenMeetings to be easy to embed >> into existing environments. It already uses many of Apache >> Technologies like Tomcat, Mina, Velocity, Commons, ... >> >> As you can see below the last time we did the proposal we had >> Hibernate in our software stack, we did refactor the hole project and >> use openJPA now. >> So that one should be no more blocker to it. >> Red5 is used like a Servlet container and licensed under the LGPL, >> Red5 can be obtained for example from the Debian Repository: >> http://packages.debian.org/wheezy/red5-server >> >> You may find all existing documents and further material on the >> GoogleCode pages: http://code.google.com/p/openmeetings/ >> >> We appreciate any feedback and comments on the proposal. >> >> Sebastian Wagner >> >> 2009/11/9 Ross Gardler : >>> Just as a point of interest, I just completed a test meeting using >>> OpenMeetings across three sites using the demo server. >>> >>> I was suitably impressed by the project. It has a few annoying >>> limitations, but as an online meeting tool it is very good. to the >>> extent that I will almost certainly be installing a copy on our own >>> servers. I would be very happy to see it coming into the incubator and >>> would be willing to be a mentor, assuming the legal issues are not >>> blockers. >>> >>> Ross >>> >>> 2009/11/3 Alexei Fedotov : >>>> Noel, >>>> Regarding Theora codec, I have checked the page [1]. Currently, there >>>> are no products which successfully use the codec for video >>>> communication. Video-phone encodes and decodes the stream in >>>> real-time, adopts the quality with regard to network conditions (e.g. >>>> lost packet rate) and tries to minimize subjective effects of network >>>> errors - the list of requirements is broader than for media players >>>> Theora is mostly used. The work [2] says suggests using hardware >>>> implementations for Theora codec because, otherwise "a computational >>>> performance too high to be implemented in the camera by the universal >>>> processor". >>>> >>>> So at least it requires some time and testing before I can say that >>>> Theora-based solution is feasible. Another ecosystem change, like >>>> embedding video-codecs in browsers, may resolve our need in a >>>> different way. >>>> >>>> [1] http://www.vorbis.com/software/ >>>> [2] http://www3.elphel.com/linuxtag/talks_2005/paper-11081 >>>> >>>> 2009/11/3 Noel J. Bergman : >>>>> Alexei Fedotov wrote: >>>>> >>>>>> I see two long-term possibilities for synergy. >>>>>> 1. BlueSky can integrate browser pannel in their client to handle a >>>>>> whiteboard. In this case the code for whiteboard can be re-used in >>>>>> both projects. >>>>> >>>>>> 2. They promise to get rid from mplayer and ffmpeg dependencies. If >>>>>> they get a working streaming video-client under APL, this would help >>>>>> us to remove the most imporant dependency from Flash. >>>>> >>>>> They are proposing to move to Theora/Vorbis, which is under a suitable >>>>> license: http://www.vorbis.com/faq/#slic. Would that be suitable for your >>>>> needs? >>>>> >>>>>> we [also] get more people on Apache who share the same task. >>>>> >>>>> Agreed. >>>>> &
Re: [DISCUSSION] Accept OpenOffice.org for incubation
Anyone is allowed to vote. If you vote against, please, explain why. Most of votes do not count anyway, negative votes are usually addressed. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Jun 10, 2011 at 8:45 PM, Simon Phipps wrote: > For us outsiders, can you explain who is allowed to vote and in what way, > please? > > S. > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenOffice.org for incubation
+1 (non-binding) -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Jun 10, 2011 at 8:20 PM, William A. Rowe Jr. wrote: > On 6/10/2011 11:02 AM, Sam Ruby wrote: >> >> Please cast your votes: >> >> [ ] +1 Accept OpenOffice.org for incubation > > +1 [binding] > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org Apache Incubator Proposal
Rob, thanks for your question. OpenOffice integration is a minor issue compared to Hibernate and some other packages which require code changes. Openmeetings uses OpenOffice service via socket. Having the common license helps, for example, putting both into one distribution package. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jun 2, 2011 at 6:45 AM, wrote: > Alexei Fedotov wrote on 06/01/2011 01:38:43 PM: > >> >> OpenOffice is used in our product [1] we want to submit to the >> incubator. We promised to show that we can gradually clean up LGPL >> from the code and were working on that [2]. We'd have one less >> head-ache with OO under Apache License (even if we don't statically >> linking it, GPL does not define linking). >> >> If some guys would consider merging back changes from Lotus Symphony >> and some other guys wouldn't be abandoning OO in this nice, polite and >> gentle way, I'd really like the change. >> > . > . > . >>[1] http://wiki.apache.org/incubator/OpenmeetingsProposal > > Hi Alexei, I'm not familiar with OpenMeetings. Can you say a little more > about how it uses OpenOffice? In particular, does it reuse the OpenOffice > binaries as-is? Does it extend OpenOffice via scripts or plugins? Or > does it require making core source code modifications and rebuilding? Or > something else? > > I'm just trying to better understand the nature of the dependency, so we > can better coordinate on this. > Regards, > > -Rob > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org Apache Incubator Proposal
OpenOffice is used in our product [1] we want to submit to the incubator. We promised to show that we can gradually clean up LGPL from the code and were working on that [2]. We'd have one less head-ache with OO under Apache License (even if we don't statically linking it, GPL does not define linking). If some guys would consider merging back changes from Lotus Symphony and some other guys wouldn't be abandoning OO in this nice, polite and gentle way, I'd really like the change. Thanks for an opportunity to answer to a president. :-) [1] http://wiki.apache.org/incubator/OpenmeetingsProposal [2] http://www.mail-archive.com/general@incubator.apache.org/msg23299.html -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Jun 1, 2011 at 7:41 PM, Luke Kowalski wrote: > > The following project is being sent in as an incubator candidate. > > regards > luke > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Vote]: Libcloud to become a TLP
+1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, May 18, 2011 at 12:31 PM, Mohammad Nour El-Din wrote: > Also mine ;) > > On Mon, May 16, 2011 at 8:28 AM, Mattmann, Chris A (388J) > wrote: >> Hi Tomaz, >> >> My vote is (binding) as well. >> >> Cheers, >> Chris >> >> On May 15, 2011, at 10:42 PM, Tomaz Muraus wrote: >> >>> OK, sorry for the confusion, but apparently I need to open a separate voting >>> thread so here it is. >>> >>> Here is also a list of people who have already voted +1 in the proposal >>> thread which can be found at >>> http://mail-archives.apache.org/mod_mbox/incubator-general/201105.mbox/%3cbanlktikhycoedn3r9o41ohmgj1hs41d...@mail.gmail.com%3E >>> : >>> >>> - Paul Querna >>> - Chris Mattmann >>> - Joe Schaefer (binding) >>> - Davanum Srinivas (binding) >>> - Mohammad Nour El-Din >>> - Alan D. Cabrera >>> - Tommaso Teofili (binding) >>> - Mark Struberg (binding) >>> - Luciano Resende (binding) >>> >>> >>> >>> Hello all, >>> >>> Apache Libcloud developers and community thinks we are ready to graduate and >>> become a top level project. >>> >>> Libcloud (http://incubator.apache.org/libcloud/) has entered the incubator >>> in late 2009 and so far we have had multiple releases. >>> >>> The last version (0.4.2) was released in January. We are currently working >>> towards 0.5.0 which is planned to be released in the upcoming week. This >>> release is considered as a big one since it will include multiple new >>> features (storage & load balancer API), new provider drivers and a lot of >>> improvements. >>> >>> We have also built a healthy and a diverse community around our project. So >>> far we have received (and continue to receive) multiple contributions from >>> them. >>> >>> Community voting has passed with ten (10) +1's, zero (0) 0's and zero (0) >>> -1's. Thread with the results can be found at >>> http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser >>> >>> Our status file can be found at >>> http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/libcloud.xmland >>> the resolution is included bellow. >>> >>> < >>> http://mail-archives.apache.org/mod_mbox/incubator-libcloud/201105.mbox/browser >>>> >>> Thanks, >>> Tomaz >>> >>> Establish the Apache Libcloud Project >>> >>> WHEREAS, the Board of Directors deems it to be in the best >>> interests of the Foundation and consistent with the >>> Foundation's purpose to establish a Project Management >>> Committee charged with the creation and maintenance of >>> open-source software related to abstracting differences >>> between cloud providers for distribution at no charge to >>> the public. >>> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>> Committee (PMC), to be known as the "Apache Libcloud Project", >>> be and hereby is established pursuant to Bylaws of the >>> Foundation; and be it further >>> >>> RESOLVED, that the Apache Libcloud Project be and hereby is >>> responsible for the creation and maintenance of software >>> related to software providing a standard interface to the >>> cloud provider APIs; and be it further >>> >>> RESOLVED, that the office of "Vice President, Apache Libcloud" be >>> and hereby is created, the person holding such office to >>> serve at the direction of the Board of Directors as the chair >>> of the Apache Libcloud Project, and to have primary responsibility >>> for management of the projects within the scope of >>> responsibility of the Apache Libcloud Project; and be it further >>> >>> RESOLVED, that the persons listed immediately below be and >>> hereby are appointed to serve as the initial members of the >>> Apache Libcloud Project: >>> >>> * Eric Woods (wood...@apache.org) >>> * Jed Smith (j...@apache.org) >>> * Jeremiah Orem(or...@apache.org) >>> * Jerry Chen (je...@apache.org) >>> * Roman Bogorodskiy (rbogorods...@apache.org) >>> * Tom Davis (t...@apache.org) >>> * Tomaz Muraus (to...@apache.org) >>> * Paul Quer
Re: [RESULTS][VOTE] Wave accepted into the ASF incubator
Missed the actual vote... Congratulations to fellow wavers! -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 2010/12/4 Dan Peterson > Hi everyone, > > I'm pleased to report that the vote to accept Wave into the ASF incubator > was overwhelmingly positive. > > By my tally, there have been 88 votes over the past 3+ days, including 18 > IPMC binding votes, 8 votes by members of the ASF, and no -1 votes. Of > those > 88 votes, due to a slight process confusion (and an issue of reply-to > settings), 22 votes were only registered on the existing wave-protocol > Google Group. > > The 18 binding votes: > Andrus Adamchik, Ant Elder, Bernd Fondermann, Bertrand Delacretaz, Chris A. > Mattmann, Christian Grobmeier, Davanum Srinivas, Dave Johnson, Doug > Cutting, Emmanuel Lecharny, Jim Jagielski, Kevan Miller, Luciano Resende, > Mark > Struberg, Michael McCandless, Ralph Goers, Tim Williams, and Upayavira > > The 8 non-IMPC members who are ASF members: > Ate Douma, Brett Porter, Leif Hedstrom, Marcel Offermans, Niklas > Gustavsson, Richard Hall, Santiago Gala, and Vincent Siveton > > The 68 non-binding votes: > a2c, Adirondack, Alain Levesque, Albonobo, Alex North, Andreas Kuckartz, > Andrian Kurniady, Anthony Watkins, Bart Thate, benediktus dwi hari > prasetyo, > Bertine van Hövell, Charles Goddard, Chris Harvey, Christopher Brind, Dan > Peterson, Dave Woollard, David Wang, David Westbrook, Davide Carnovale, > Edward J. Yoon, Eelco Hillenius, florent andré, Florian Rohrweck, Francis > De > Brabandere, Gamer-Z, Help Earth Foundation,Honza Rameš, Ian Boston, Ian > Roughley,Isabel Drost, Jack Park, James R. Purser, Jeff Forsyth, Jeremy > ngl, > John Edstrom, JR Smith, Kevin Lau, Lahiru Gunathilake, Manfred Herrmann, > Mark Kovacevich, Matias Molinas, Matt Richards, Matthew Cua1, Michael > MacFadden, MiCHiLU/Takanao Endoh, Mohammad Nour, Nathanael Abbotts, Noriyo, > Paul Lindner, Petru, Riu6, Sander W G van der Waal, Scott Wilson, > shigech...@gmail.com, Sophia Parafina, Soren Lassen, STenyaK, Tad Glines, > ThomasWrobel, Tish Shute, Vitality, and Yasushi Ando > > The primary voting thread (there were a few side threads that sprawled that > aren't linked here): > http://apache.markmail.org/message/v2c4cnewpczdxzny > [ The following Google Group archives the other 22 unofficial, non-binding > votes: > > http://groups.google.com/group/wave-protocol/browse_thread/thread/4fc26d16cde74380 > ] > > The proposal that was approved: > http://wiki.apache.org/incubator/WaveProposal > > Looking forward to growing Wave in the Apache way, > -Dan >
Re: [PROPOSAL] Accept Wave for incubation
+1 (non-binding) -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Nov 24, 2010 at 5:25 PM, Paul Lindner wrote: > A hearty +1 from the designated champion to getting Wave into the > Incubator. I've been especially impressed with the way the community > has rallied behind the open source implementation and know that it > will do well at Apache. > > > On Tue, Nov 23, 2010 at 12:16 PM, Dan Peterson wrote: >> Hello all, >> >> We'd like to propose Wave for entry into the ASF incubator. >> >> The draft proposal is available at: >> http://wiki.apache.org/incubator/WaveProposal >> (for your convenience, a snapshot is also copied below) >> >> A wave is a hosted, live, concurrent data structure for rich communication. >> It can be used like email, chat, or a document. Wave in a Box (WIAB) is the >> name of the main product at the moment, which is a server that hosts and >> federates waves, supports extensive APIs, and provides a rich web client. >> This project also includes an implementation of the Wave Federation >> protocol, to enable federated collaboration systems (such as multiple >> interoperable Wave In a Box instances). >> >> As a result of the recent Wave Summit, beyond growing a few new committers, >> we've put together the following proposal for migrating the community into >> the ASF incubator. More details on the summit & Wave in a Box progress in >> this blogpost: >> http://googlewavedev.blogspot.com/2010/11/this-weeks-wave-protocol-summit-updates.html >> >> We are looking forward to your feedback and suggestions. >> >> By the way, if you're looking to learn more about the technology related to >> wave, you can see the videos and presentations from the recent Wave Summit >> in: https://wave.google.com/wave/waveref/googlewave.com/w+rwFyiw47A >> >> Kind regards, >> -Dan, on behalf of the Wave Community >> >> P.S. For those on the wave-protocol Google Group (that aren't yet on >> general@incubator.apache.org), please participate in this discussion >> by sending a message to general-subscribe at incubator dot apache dot org >> >> >> Apache Wave Proposal (Apache Incubator) >> >> = Abstract = >> >> Apache Wave is the project where wave technology is developed at Apache. >> Wave in a Box (WIAB) is the name of the main product at the moment, which is >> a server that hosts and federates waves, supports extensive APIs, and >> provides a rich web client. This project also includes an implementation of >> the Wave Federation protocol, to enable federated collaboration systems >> (such as multiple interoperable Wave In a Box instances). >> >> = Proposal = >> >> A wave is a hosted, live, concurrent data structure for rich communication. >> It can be used like email, chat, or a document. >> >> WIAB is a server that hosts waves. The best analogy for this is a mail >> server with a web client. WIAB is comprised of a few high-level components: >> the client and the server. They have the following major functionality >> (though this is not an exhaustive list): >> >> * Client >> *A dynamic web client for users to create, edit, and search waves. Users >> can access this client by directly visiting the server in a browser. >> * Gadgets provide the ability to insert, view, and modify the UI -- >> exposing the Wave Gadgets API ( >> http://code.google.com/apis/wave/extensions/gadgets/guide.html) >> * A console client that can create and edit waves via a command-line-like >> interface. >> * Server >> * Hosts and stores waves. WIAB comes with a default storage mechanism. The >> administrators of the server may configure it to use alternative storage >> mechanisms. >> * Indexing, allowing for searching the waves a user has access to. >> * Basic authentication, configurable to delegate to other systems. >> * Federation, allowing separate Wave in a Box servers to communicate with >> each other using the Wave Federation Protocol ( >> http://www.waveprotocol.org/federation). >> * Robots, using the Wave Robots API, ( >> http://code.google.com/apis/wave/extensions/robots/) may interact with waves >> on a WIAB instance. >> >> = Background = >> >> Wave expresses a new metaphor for communication: hosted conversations. This >> was created by Lars and Jens Rasmussen after observation of people's use of >> many separate forms of communication to get something done, e.g, email, >> chat, docs, b
Re: [PROPOSAL] Gora to enter Incubator
This is how a person like me perceives the project. ORM... Mmm... The acronym resembles CRM. Aha, this is CRM for stores which sell these colum things! :-) P.S. I've got the point. Later. On Tue, Sep 14, 2010 at 11:33 AM, Tommaso Teofili wrote: > +1 (not binding) > Tommaso > > 2010/9/13 Mohammad Nour El-Din > >> +1 (Not binding) >> >> On Mon, Sep 13, 2010 at 4:46 PM, Mattmann, Chris A (388J) >> wrote: >> > My +1 to this proposal, but we certainly need at least one more mentor, >> please, if you’re interested sign up. >> > >> > Thanks! >> > >> > Cheers, >> > Chris >> > >> > >> > >> > On 9/13/10 6:10 AM, "Enis Soztutar" wrote: >> > >> > Hi all, >> > >> > We would like to announce the Proposal for Gora, an ORM for Colum Stores, >> > for the Apache Incubation. We believe that Gora can find a nice home at >> > Apache. >> > >> > Wiki of the proposal can be found at >> > http://wiki.apache.org/incubator/GoraProposal >> > >> > The proposal is as below. >> > >> > >> > = Gora Proposal for Apache Incubation = >> > >> > == Abstract == >> > Gora is an ORM framework for column stores such as Apache HBase and >> Apache >> > Cassandra with a specific focus on Hadoop. >> > >> > == Proposal == >> > Although there are various excellent ORM frameworks for relational >> > databases, data modeling in NoSQL data stores differ profoundly from >> their >> > relational cousins. Moreover, data-model agnostic frameworks such as JDO >> are >> > not sufficient for use cases, where one needs to use the full power of >> the >> > data models in column stores. Gora fills this gap by giving the user an >> > easy-to-use ORM framework with data store specific mappings and built in >> > Apache Hadoop support. >> > >> > The overall goal for Gora is to become the standard data representation >> and >> > persistence framework for big data. The roadmap of Gora can be grouped as >> > follows. >> > >> > * Data Persistence : Persisting objects to Column stores such as HBase, >> > Cassandra, Hypertable; key-value stores such as Voldermort, Redis, etc; >> SQL >> > databases, such as MySQL, HSQLDB, flat files in local file system of >> Hadoop >> > HDFS. >> > * Data Access : An easy to use Java-friendly common API for accessing >> the >> > data regardless of its location. >> > * Indexing : Persisting objects to Lucene and Solr indexes, >> > accessing/querying the data with Gora API. >> > * Analysis : Accesing the data and making analysis through adapters for >> > Apache Pig, Apache Hive and Cascading >> > * MapReduce support : Out-of-the-box and extensive MapReduce (Apache >> > Hadoop) support for data in the data store. >> > >> > == Background == >> > ORM stands for Object Relation Mapping. It is a technology which abstacts >> > the persistency layer >> > (mostly Relational Databases) so that plain domain level objects can be >> > used, without the cumbersome effort to save/load the data to and from the >> > database. Gora differs from current solutions in that: >> > * Gora is specially focussed at NoSQL data stores, but also has limited >> > support for SQL databases >> > * The main use case for Gora is to access/analyze big data using Hadoop. >> > * Gora uses Avro for bean definition, not byte code enhancement or >> > annotations >> > * Object-to-data store mappings are backend specific, so that full data >> > model can be utilized. >> > * Gora is simple since it ignores complex SQL mappings >> > * Gora will support persistence, indexing and anaysis of data, using >> Pig, >> > Lucene, Hive, etc >> > >> > == Rationale == >> > ORM frameworks are nothing new. But with the explosion of data generated >> in >> > Terabytes and even Petabytes, NoSQL data stores are gaining >> ever-increasing >> > popularity. Coupled with limited support to already-proven Apache Hadoop >> > support in current ORM frameworks, there was a need for a new project. >> > >> > Gora is currently hosted at Github. However, Gora has ties to ASF in many >> > ways. As detailed in the proposal section, Gora will be a high level >> client >> > for many Apache projects and subprojects including Hadoop(common, hdfs, >> and >> > mapreduce), HBase, Cassandra, Avro, Lucene, Solr, Pig, and Hive. Gora >> > already uses Hadoop, HBase, Cassandra and Avro. Moreover, Gora started >> its >> > life inside Apache Nutch project, and now Nutch trunk uses Gora as a >> > library. Even more, the initial set of committers are all ASF members. >> > Therefore, we think that Apache will be an excellent home for Gora. >> > >> > == Initial Goals == >> > Initial goals for Gora can be summarized as: >> > * Iron out the remaining issues with HBase, Cassandra and SQL support. >> > * Make the first release before the end of the year. >> > * Improve documentation >> > * Support for Cascading >> > >> > == Current Status == >> > === Meritocracy === >> > Current commit rights belong to the initial list of committers four of >> who >> > are also ASF members. All the developers have extensive experienc
Hibernate migration strategy Was: [PROPOSAL][VOTE] OpenMeetings
Hello, As for migrating from Hibernate, I see several alternatives for persistence. Enterprise Java experts, please, could you comment on this? 1. stackoverflow.com suggested using Spring as a persistence technology. My friend said that it requires coding, but you get manageable, clear and transparent application. We already use Spring as a dependency. 2. Using JPA from Java 6 JPA allows using less libraries and being more compatible with Google App Engine. The latter may help general users to host the web application. 3. Does OpenJPA suggested by Niclas offer any benefits compared to JPA? Synergy is good, but there may be other benefits I cannot see. Sorry for my ignorance. Thanks. P.S. Ross, it would be really nice to get you as a mentor. On Wed, Nov 18, 2009 at 6:56 PM, Ross Gardler wrote: > 2009/11/18 Sebastian Wagner : > > we would like to propose Openmeetings project to join the incubator. > > > > Full Proposal: > > http://wiki.apache.org/incubator/OpenmeetingsProposal > > Calling a vote is premature. Therefore my vote is -1. > > Your proposal does not yet have a confirmed champion and you don't > have sufficient mentors yet. > > I'm still toying with the idea of mentoring, but I'm still unclear > with respect to the legal situation. I've not seen a clear consensus > that it will ever be possible to produce a cleanly licensed > application that does not require the use of LGPL/GPL code. > > Ross > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Noel, Regarding Theora codec, I have checked the page [1]. Currently, there are no products which successfully use the codec for video communication. Video-phone encodes and decodes the stream in real-time, adopts the quality with regard to network conditions (e.g. lost packet rate) and tries to minimize subjective effects of network errors - the list of requirements is broader than for media players Theora is mostly used. The work [2] says suggests using hardware implementations for Theora codec because, otherwise "a computational performance too high to be implemented in the camera by the universal processor". So at least it requires some time and testing before I can say that Theora-based solution is feasible. Another ecosystem change, like embedding video-codecs in browsers, may resolve our need in a different way. [1] http://www.vorbis.com/software/ [2] http://www3.elphel.com/linuxtag/talks_2005/paper-11081 2009/11/3 Noel J. Bergman : > Alexei Fedotov wrote: > >> I see two long-term possibilities for synergy. >> 1. BlueSky can integrate browser pannel in their client to handle a >> whiteboard. In this case the code for whiteboard can be re-used in >> both projects. > >> 2. They promise to get rid from mplayer and ffmpeg dependencies. If >> they get a working streaming video-client under APL, this would help >> us to remove the most imporant dependency from Flash. > > They are proposing to move to Theora/Vorbis, which is under a suitable > license: http://www.vorbis.com/faq/#slic. Would that be suitable for your > needs? > >> we [also] get more people on Apache who share the same task. > > Agreed. > > --- Noel > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Niclas, thanks for an answer about LGPL! Noel, Thanks for a link to BlueSky! Openmeetings is used into Moodle and Dokeos e-learning systems - communication always helps education. The main difference with BlueSky is that BlueSky has a standalone client, and not the browser-based one. I see two long-term possibilities for synergy. 1. BlueSky can integrate browser pannel in their client to handle a whiteboard. In this case the code for whiteboard can be re-used in both projects. 2. They promise to get rid from mplayer and ffmpeg dependencies. If they get a working streaming video-client under APL, this would help us to remove the most imporant dependency from Flash. As for quick benefits, we get more people on Apache who share the same task. For example, usability really matters in end-user applications, and establishing usability standard for our applications would help us both. Thanks. On Fri, Oct 30, 2009 at 8:43 PM, Noel J. Bergman wrote: > > Sounds very interesting. In addition to the existing question related to > licening, can you also comment on the problem domain overlap with BlueSky? > It seems to me that there might be good synergies. > > --- Noel > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Hello Niclas, Thanks for a link [1]! It reads: > The LGPL is ineligible primarily due to the restrictions it places on larger > works Well, I believe if lawyers said that, they have enough attribution. Though I always thought that LGPL is GPL limited to the library scope. How does LGPL place restrictions on larger works? [1] http://www.apache.org/legal/resolved.html On Thu, Oct 29, 2009 at 5:54 AM, Niclas Hedhman wrote: > On Thu, Oct 29, 2009 at 4:10 AM, Sebastian Wagner > wrote: > >> Is a LGPL Library a general Issue? For running the application we also use >> hibernate. >> Spring, Apache Batik and Apache Mina are also used, but these are all >> already Apache Licenses projects. Hibernate is LGPL. Is this a conflict? > > For "hard dependencies" then LGPL is an issue. If you ship optional > features which relies on LGPL components, then that is generally Ok. > > Some questions on this are already answered; > http://www.apache.org/legal/resolved.html , but if in doubt contact > legal-disc...@apache.org for clarifications prior to shipping > non-Apache licensed material. > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Hello Martin, I may fail to understand Paul's question, indeed. Let me give my best try to answer to your questions. > Is it not true that OpenMeetings requires Red5 in order to function properly? True. The Openmeetings requires Red5 to function properly. > So that, if we cannot distribute Red5 as part of an ASF distro, because of > the license, we also cannot distribute a functional OpenMeetings product? Not true. Openmeetings can be distributed without Red5. > Or is there some alternative to Red5 that could be distributed instead? I believe it is possible to use Adobe Flash Media Server as a substitution for Red5, but we cannot distribute Adobe FMS that for sure. In your last question you assume that we cannot distribute Red5. I don't think this is a valid problem. 1. Anyone can distribute GPL-licensed binary, or LGPL-licensed library. The virus problems begin when you try to modify the source of the product. This always requires proper attributions in COPYRIGHT file, but anyway. 2. Apache may have more strict guidelines on distributions. Nothing prevents us to write a small Apache-licensed Red5 installer and distribute it instead. 3. The truth is that currently Openmeetings is not built on pure Apache stack. I cannot see a problem here. Most Apache products used Sun's java when there was no Harmony, and Sun's vm was not even FOSS. Since I'm not a layer, I can be mistaken here. Martin, please, let me know, if you find error in my conclusions. 2009/10/28 Martin Cooper : > 2009/10/28 Alexei Fedotov : >> Hello Paul, >> Thanks for a good question! >> >> Openmeetings is red5 application which is very close to ordinary web >> application. AFAIU, the last change by Sebastian makes them even >> closer by implementing ".war" deployment. The code of the projects >> does not overlap in any way, and projects are connected via dynamic >> linking. AFAIK, dynamic linking of separate modules is permitted by >> LGPL. >> >> Digging this deeper, most dynamic linking is with a web server (i.e. >> Tomcat or Jetty) embedded into Red5, which is Apache licensed. To the >> best of my knowledge openmeetings communicate with a media server >> mostly using sockets, so some distribution re-packs may eliminate even >> dynamic linking. > > I don't believe you've answered what Paul was really asking, though. > Is it not true that OpenMeetings requires Red5 in order to function > properly? So that, if we cannot distribute Red5 as part of an ASF > distro, because of the license, we also cannot distribute a functional > OpenMeetings product? Or is there some alternative to Red5 that could > be distributed instead? > > -- > Martin Cooper > > >> >> >> >> On Wed, Oct 28, 2009 at 1:01 AM, Paul Querna wrote: >>> On Tue, Oct 27, 2009 at 4:22 AM, Sebastian Wagner >>> wrote: >>>> hi, >>>> >>>> we would like to propose Openmeetings project to join the incubator. >>>> >>>> Full Proposal: >>>> http://wiki.apache.org/incubator/OpenmeetingsProposal >>>> >>>> Quick summary: >>>> OpenMeetings is Web Conferencing application that fits into educational or >>>> business sector. You can make conference sessions in different room-types >>>> with up to 100 peoples in a Room. It contains all main features of Web >>>> Conferencing: Audio/Video, Whiteboard, Screen Sharing, Chat and Moderation >>>> System. It is translated into more then 20 languages and its a basic goal >>>> of >>>> OpenMeetings to be easy to embed into existing environments. It already >>>> uses >>>> many of Apache Technologies like Tomcat, Mina, Velocity, Commons, ... >>>> >>>> You may find all existing documents and further material on the GoogleCode >>>> pages: http://code.google.com/p/openmeetings/ >>>> >>> >>> Sounds cool! >>> >>> I do have a question about how the project uses Red5 Media Server. >>> Red5 is licensed under the LGPL, how exactly does OpenMeetings use it? >>> >>> Thanks, >>> >>> Paul >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> >> >> >> -- >> With best regards / с наилучшими пожеланиями, >> Alexei Fedotov / Алексей Федотов, >> http://www.telecom-express.ru/ >> http://harmony.apache.org/ >> http://
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Hello Ian, Thanks for raising questions. As for OpenLaszlo, I cannot say much. Some Apache projects use Microsoft compiler, that's legal. I believe it is quite doable to build OpenLaszlo completely on Apache stack, but that project has their own authors. As for Red5, the situation is good and became better. Red5 is no more than a proxy which re-sends packets from one Adobe player to another. This is good because we do not dig into Adobe's rtmp packets, and especially into h.264 codec frames. This saves us from patent violations. This has some drawback: we cannot mix all video streams into one - we can just forward them as is. When we get free and patent-free open souce codecs, we can replace a traffic layer with a FOSS one. The better thing is that Adobe finally opened RTMP specification [1]. The specification license prohibits unintended use of rtmp for for violating digital protection (this somehow relates to new GPL v.3 features) and intercepting video, othewise it is ok. Disclaimer. IMHO. IANAL. [1] http://www.adobe.com/devnet/rtmp/pdf/rtmp_specification_1.0.pdf On Wed, Oct 28, 2009 at 2:38 PM, Ian Boston wrote: > Openmeetings looks very interesting. I notice Red5, and see Paul Querna > asked a question. I have 2 questions for my own education more than > anything, > > What's the status of OpenLazlo wrt Apache Projects? I see it has a long list > of dependencies with all sorts of licenses [1] but have no idea if there is > a runtime or distribution binding that matters ? > > I hate to bring this up , but I have to ask (sorry) > Also, are there any problems between Red5 and Adobe in terms of patents on > the Flash Media Server protocols. IIRC Adobe have some patents in this area > but I have no idea if they are relevant and enforceable or would want to > enforce them against an open source project? > > > Ian > > 1 http://www.openlaszlo.org/lps4.2/docs/developers/licenses.html > > > On 27 Oct 2009, at 11:22, Sebastian Wagner wrote: > >> hi, >> >> we would like to propose Openmeetings project to join the incubator. >> >> Full Proposal: >> http://wiki.apache.org/incubator/OpenmeetingsProposal >> >> Quick summary: >> OpenMeetings is Web Conferencing application that fits into educational or >> business sector. You can make conference sessions in different room-types >> with up to 100 peoples in a Room. It contains all main features of Web >> Conferencing: Audio/Video, Whiteboard, Screen Sharing, Chat and Moderation >> System. It is translated into more then 20 languages and its a basic goal >> of >> OpenMeetings to be easy to embed into existing environments. It already >> uses >> many of Apache Technologies like Tomcat, Mina, Velocity, Commons, ... >> >> You may find all existing documents and further material on the GoogleCode >> pages: http://code.google.com/p/openmeetings/ >> >> >> We appreciate any feedback and comments on the proposal. >> >> >> sebastian wagner >> -- >> Sebastian Wagner >> http://www.webbase-design.de >> http://openmeetings.googlecode.com >> http://www.laszlo-forum.de >> seba.wag...@gmail.com > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Hello Nick, There is a "Not a member" button [1] on the first page to get a free account. If you doesn't mind Russian field names during registration you can try [2] as a localization example. [1] http://www.openmeetings.de/ [2] http://www.telebridge.ru/ On Wed, Oct 28, 2009 at 1:38 AM, Nick Kew wrote: > > On 27 Oct 2009, at 11:22, Sebastian Wagner wrote: > >> hi, >> >> we would like to propose Openmeetings project to join the incubator. >> >> Full Proposal: >> http://wiki.apache.org/incubator/OpenmeetingsProposal > > Wow, two new proposals in a day! > > Would be good to get a feeling for what this is. Is www.openmeetings.de > a genuine free-for-all to sign up and play? And what would be a good > time of day to find life there? > > -- > Nick Kew > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
Hello Paul, Thanks for a good question! Openmeetings is red5 application which is very close to ordinary web application. AFAIU, the last change by Sebastian makes them even closer by implementing ".war" deployment. The code of the projects does not overlap in any way, and projects are connected via dynamic linking. AFAIK, dynamic linking of separate modules is permitted by LGPL. Digging this deeper, most dynamic linking is with a web server (i.e. Tomcat or Jetty) embedded into Red5, which is Apache licensed. To the best of my knowledge openmeetings communicate with a media server mostly using sockets, so some distribution re-packs may eliminate even dynamic linking. On Wed, Oct 28, 2009 at 1:01 AM, Paul Querna wrote: > On Tue, Oct 27, 2009 at 4:22 AM, Sebastian Wagner > wrote: >> hi, >> >> we would like to propose Openmeetings project to join the incubator. >> >> Full Proposal: >> http://wiki.apache.org/incubator/OpenmeetingsProposal >> >> Quick summary: >> OpenMeetings is Web Conferencing application that fits into educational or >> business sector. You can make conference sessions in different room-types >> with up to 100 peoples in a Room. It contains all main features of Web >> Conferencing: Audio/Video, Whiteboard, Screen Sharing, Chat and Moderation >> System. It is translated into more then 20 languages and its a basic goal of >> OpenMeetings to be easy to embed into existing environments. It already uses >> many of Apache Technologies like Tomcat, Mina, Velocity, Commons, ... >> >> You may find all existing documents and further material on the GoogleCode >> pages: http://code.google.com/p/openmeetings/ >> > > Sounds cool! > > I do have a question about how the project uses Red5 Media Server. > Red5 is licensed under the LGPL, how exactly does OpenMeetings use it? > > Thanks, > > Paul > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Vote] Release Apache Pivot 1.1
> Does Harmony have a plugin.jar? This one may be good enough to compile against. https://issues.apache.org/jira/browse/HARMONY-5824 On Tue, Apr 14, 2009 at 6:18 PM, Martijn Dashorst wrote: > On Mon, Apr 13, 2009 at 1:32 PM, Todd Volkert wrote: >>> wtk/lib/plugin.jar : I don' t see this mentioned in notice or license >> >> This file is included in the JRE, which we list as a system >> requirement. We only include it in the source distribution because >> it's not in the classpath by default when you compile, so we had to >> put it in a known place. > > I think we are not allowed to distribute this dependency. This would > make my +1 a -1 I think. Does Harmony have a plugin.jar? > > Martijn > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://people.apache.org/~aaf/ http://harmony.apache.org/ http://code.google.com/p/openmeetings/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: An anti-plagiarism tool for GSoC Was: [pulse] A lab or an incubator?
Robert, Thanks for a quick answer. I have read RAT's proposal, and I agree that it is a right place to go. Do I understand correctly that you and your project fellows are open to start this GSoC task? I'm open for any form of collaboration, e.g. co-mentorship. Wtih best regards, Alexei P.S. Technically, it is ok to create the anti-plagiarism tool using Java: Google provides Javi API. The next similarity is in heuristic nature of comparison. Could you please provide a pointer how RAT heuristics are kept in the code? On Tue, Mar 3, 2009 at 3:46 PM, Robert Burrell Donkin wrote: > On Tue, Mar 3, 2009 at 11:46 AM, Alexei Fedotov > wrote: >> Hello folks, >> >> I want to know your opinion concerning the following matter. Recently >> I asked if one knows a free anti-plagiarism for scanning my project >> before an incubation. There was no answer if one knew. >> >> I think of suggesting this task for GSoC. One may use Google code >> search for detecting suspicious comments and code constructs in new >> contributions. The code search allows using of regular expressions, >> which allows whitespace and variable name differences to be neglected >> during comparison. What do you think? > > this is - i think - nearly in scope for RAT > > opinions? > > - robert > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- С уважением, Алексей Федотов, http://people.apache.org/~aaf/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
An anti-plagiarism tool for GSoC Was: [pulse] A lab or an incubator?
Hello folks, I want to know your opinion concerning the following matter. Recently I asked if one knows a free anti-plagiarism for scanning my project before an incubation. There was no answer if one knew. I think of suggesting this task for GSoC. One may use Google code search for detecting suspicious comments and code constructs in new contributions. The code search allows using of regular expressions, which allows whitespace and variable name differences to be neglected during comparison. What do you think? Thank you! On Wed, Dec 24, 2008 at 10:33 AM, Alexei Fedotov wrote: > Hello, Bernd, > Thanks for a quick answer. > > Well, we do have a working code base, that's correct. I might perceive > things as too complex having concerns about a gap between working code > and the code which can be committed to the Apache subversion. Our code > might (and likely was) tainted by cut&pasted samples, open source > fragments and third party inclusions with unknown authors and > uncertain licensing models. If I would understand how to define > questionable code and would remove the code, then this would result in > the broken code base. There are minor issues like comments in Russian > as well. > > My approach to avoid the licensing mess is writing from scratch. I > plan moving an ongoing development to Apache and envision building new > modules as pluggable APL-licensed libraries which then can be reused > by the multiple-licensed project. Another goal is to import the code > under different licenses using a build system rather then mixing all > the code in the phone code base. Such build system have to be > developed from scratch as well. That is I plan to use the labs for. > > I'm CCing this letter to general.AT.incubator.apache.org hoping to > attract incubationers attention to the discussion and get your opinion > whether it worth to start incubation or lab for the Pulse project, see > the project description below. I have passed Apache Harmony incubation > led by Geir, and have to admit openly that we are currently less > prepared for it than Intel and IBM were. As the first step I have to > find a anti-plagiarism tool reliable enough to detect GPL > contamination and copied samples from code guru web sites. Could > anyone share any tool which is preferably free for Apache committers? > > As for JIRA usage, I mean the following problem. As I've already said, > I cannot see how to open the code for the whole project at once. Now > imagine, that bugs opened for opened components would use Apache JIRA, > bugs for closed components would use our internal Bugzilla, and some > bugs during resolution would travel between two these tracking > systems. I personally believe it would be nice to have all new bugs > stored in one place. I don't think that allowing people keeping all > bugs in JIRA would be an abuse for Apache because I don't expect heavy > bug traffic. We have 45 issues so far. > > As for the binary, I got the point on careful naming. We may re-use > Harmony "snapshot build" term to name it carefully. > Thanks! > > With best regards, Alexei > > On Tue, Dec 23, 2008 at 9:55 PM, Bernd Fondermann > wrote: >> Hi Alexei, >> >> Alexei Fedotov wrote: >>> >>> Hello folks, >>> >>> Recently I became involved in development of H.323-compatible software >>> videophone [1] based on MPL-licensed OpenH323. It is mostly the same >>> as Ekiga [2], though we hardly can join GPL-ed project due to complex >>> licensing >>> of the existing code. I have a strategic goal to expose our project >>> code under Apache license and >>> move related development to Apache. I believe that working on Apache would >>> help >>> us achieving legally clean code. As a nice side benefits goal I see >>> openness to the English-speaking world which believes that software can be >>> bought and not necessarily pirated, and providing an open alternative >>> to the closed-source solutions ranged from Skype to Tandberg and Polycom, >>> thus changing the world into being more competitive and >>> customer-friendly. I would like taking advantage of APR though staying >>> with PTLib seemed >>> to be more realistic. >> >> If you have an existing code base and don't start from scratch - and that's >> what I read from your mail - the Incubator seems more appropriate to me than >> Labs. >> >>> I believe it would be feasible providing several portable and >>> re-usable communication libraries with clean interfaces under APL as the >>> first >>> step. Well, this requires much more understanding from the
Re: [pulse] A lab or an incubator? Was: Lab request: Pulse
Thanks Bertrand, The point is clear. I will look into incubation possibilities for the whole project. Let me as if folks on the list think that the project [1] is interesting and may consider contributing in any way? Meanwhile if I have an ongoing new development I will ask for a lab with a clear technical scope, e.g. "creating an ant script for bundling openh323 with pwlib and opal" or "writing utilities for saving/loading avi files". All, Merry Christmas! [1] http://www.youtube.com/watch?v=avOVE2BbPHE On Wed, Dec 24, 2008 at 11:32 AM, Bertrand Delacretaz wrote: > Hi Alexei, > > Alexei Fedotov wrote: >>>>... I wonder what do you think about using Apache labs as a >>>> launching pad for the project. It is hard to guarantee now if it would >>>> be possible to expose enough code to build a self sufficient product > > I also think that a lab is not well suited to your project's scope and > goals - I'm just quoting the above excerpt where you talk about a > "product", and that's not what labs are meant for IMHO, they're meant > for experiments. You also seem to need an issue tracker of your own, > and binary releases - that's not labs. > > I would suggest going for the incubator, assuming you can form a small > community of interested people and mentors. If not, starting outside > Apache but with the Apache way of working, and coming back to incubate > a bit later, might be an option. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- С уважением, Алексей Федотов, ЗАО «Телеком Экспресс»
[pulse] A lab or an incubator? Was: Lab request: Pulse
Hello, Bernd, Thanks for a quick answer. Well, we do have a working code base, that's correct. I might perceive things as too complex having concerns about a gap between working code and the code which can be committed to the Apache subversion. Our code might (and likely was) tainted by cut&pasted samples, open source fragments and third party inclusions with unknown authors and uncertain licensing models. If I would understand how to define questionable code and would remove the code, then this would result in the broken code base. There are minor issues like comments in Russian as well. My approach to avoid the licensing mess is writing from scratch. I plan moving an ongoing development to Apache and envision building new modules as pluggable APL-licensed libraries which then can be reused by the multiple-licensed project. Another goal is to import the code under different licenses using a build system rather then mixing all the code in the phone code base. Such build system have to be developed from scratch as well. That is I plan to use the labs for. I'm CCing this letter to general.AT.incubator.apache.org hoping to attract incubationers attention to the discussion and get your opinion whether it worth to start incubation or lab for the Pulse project, see the project description below. I have passed Apache Harmony incubation led by Geir, and have to admit openly that we are currently less prepared for it than Intel and IBM were. As the first step I have to find a anti-plagiarism tool reliable enough to detect GPL contamination and copied samples from code guru web sites. Could anyone share any tool which is preferably free for Apache committers? As for JIRA usage, I mean the following problem. As I've already said, I cannot see how to open the code for the whole project at once. Now imagine, that bugs opened for opened components would use Apache JIRA, bugs for closed components would use our internal Bugzilla, and some bugs during resolution would travel between two these tracking systems. I personally believe it would be nice to have all new bugs stored in one place. I don't think that allowing people keeping all bugs in JIRA would be an abuse for Apache because I don't expect heavy bug traffic. We have 45 issues so far. As for the binary, I got the point on careful naming. We may re-use Harmony "snapshot build" term to name it carefully. Thanks! With best regards, Alexei On Tue, Dec 23, 2008 at 9:55 PM, Bernd Fondermann wrote: > Hi Alexei, > > Alexei Fedotov wrote: >> >> Hello folks, >> >> Recently I became involved in development of H.323-compatible software >> videophone [1] based on MPL-licensed OpenH323. It is mostly the same >> as Ekiga [2], though we hardly can join GPL-ed project due to complex >> licensing >> of the existing code. I have a strategic goal to expose our project >> code under Apache license and >> move related development to Apache. I believe that working on Apache would >> help >> us achieving legally clean code. As a nice side benefits goal I see >> openness to the English-speaking world which believes that software can be >> bought and not necessarily pirated, and providing an open alternative >> to the closed-source solutions ranged from Skype to Tandberg and Polycom, >> thus changing the world into being more competitive and >> customer-friendly. I would like taking advantage of APR though staying >> with PTLib seemed >> to be more realistic. > > If you have an existing code base and don't start from scratch - and that's > what I read from your mail - the Incubator seems more appropriate to me than > Labs. > >> I believe it would be feasible providing several portable and >> re-usable communication libraries with clean interfaces under APL as the >> first >> step. Well, this requires much more understanding from the fellow >> stakeholders including developers who are not familiar with an open >> source model. I plan to resolve patenting issues around codecs Ekiga is >> facing >> by providing enough modularity of the project design and keeping >> questionable modules out of the Apache source base. > > Ok, fine. > >> I wonder what do you think about using Apache labs as a >> launching pad for the project. It is hard to guarantee now if it would >> be possible to expose enough code to build a self sufficient product. > > See my first comment. If you indeed start a lab (or at the Incubator), you > don't need to say where your project will end up, finally. Just start and > see where it takes you. > >> Some parts of our product are contaminated while others are >> third party legacy of uncertain origin (e.g. may be contaminated as well). >> We may only hope to concent
