Non English Mailing Lists
Hi, I would like to clarify if Non-English Mailing lists are allowed. Background: I missed in our Proposal the Mailing List: http://groups.google.com/group/openmeetings-en-espanol/about?hl=en_US We made now a Vote on our Developer List to add this mailing list and the Moderators from the GoogleGroups List have applied to become the Moderator of the new list. Everythings fine from my point of view. But I've heard that using Non-English List is not allowed on Apache Infrastructure. Is that true? It makes me wonder as the OpenOffice project has 100++ Mailing lists in a lot of different languages. So I guess there is no such restriction and we can proceed right? Thanks, Sebastian -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com
Re: Non English Mailing Lists
First of all, my apologies for not being a good mentor for your project. Too many demands on too little time. But I'm starting to resurface. More comments inline... On 14 December 2011 12:34, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Hi, I would like to clarify if Non-English Mailing lists are allowed. There are no hard and fast rules about this other than the main dev list much be in English. That is the list where most decisions about the future of the project can occur. We generally discourage non-english dev lists as they serve to split the community. However, a case could be made for supporting such. Non-english user lists are not so much of a problem if there are sufficient users demanding them. One needs to be cautious about creating them as, again, you are splitting the community. But for users it can sometimes help. But I've heard that using Non-English List is not allowed on Apache Infrastructure. Is that true? No, see above. Discouraged is the correct word. It makes me wonder as the OpenOffice project has 100++ Mailing lists in a lot of different languages. So I guess there is no such restriction and we can proceed right? OpenOffice.org has 100+ non-english lists, but Apache OpenOffice has, at this point in time, just one or two non-english user lists. They are being created as the user community comes forwards and demonstrates a need for them. In the case of your Spanish list, which appears to be a user list, I see it is quite active. Sop, personally, I don't see a problem as long as all discussions that relate to the development of OpenMeetings happen on the English language dev list. Ross Thanks, Sebastian -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com -- 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: Non English Mailing Lists
Hi, On Wed, Dec 14, 2011 at 1:34 PM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: ...I've heard that using Non-English List is not allowed on Apache Infrastructure. Is that true?... That's wrong (or new - where did you hear it?) - as long as a PMC accepts overseeing such a list I think it's perfectly ok. In the case of a podling, the PMC is the Incubator PMC, represented by your mentors, so I'd make sure the mentors agree with the list's creation, and document that with a vote on your dev list (which IIUC already happened). -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Can (Podling) Projects collect funds through certification programs?
In general, the ASF does not accept targeted donations, nor does it allow it's projects (or podlings) to perform their own independent fundraising activities. Our general fundraising policy is that any donations are to the ASF as a whole, and not to individual projects or podlings. Our projects/podlings are certainly welcome to link to and encourage users to visit our Donations or Sponsorship pages. http://www.apache.org/foundation/contributing.html http://www.apache.org/foundation/sponsorship.html As other IPMC members have noted separately, projects/podlings may have a separate page on their sites that lists various third parties who offer services, consulting, training, certification, or the like around their specific software product; that may include commercial third parties. Such listings should *not* be advertisements - they should be links with brief descriptions (or similar) that are useful to users or contributors to that particular project/podling's software or community. Does that all help? A useful page to read about how a PPMC might decide what links to put on pages like this is here: http://community.apache.org/projectIndependence.html Healthy Apache projects recognize that having an ecosystem of volunteers and commercial companies working on/with/around their software is helpful both for our users and for the Apache project itself. We are happy to let our user communities know about the work of these other volunteers and companies - as long as it's done in a factual way, and doesn't imply endorsement or approval of any specific companies over other ones. - Shane On 2011-12-13 5:23 AM, seba.wag...@gmail.com wrote: How does the ASF deal with requests from companies that would like to get a certificate as reseller of a software? Are (Podling) Projects allowed to organize a Certification program for distributors and collect funds for their project that way? Collecting funds that way is a common way of Open Source projects, also Apache has a sponsor page et cetera. However the companies listed there contribute to the Foundation in general. The question is if each project of the foundation additionally can have its own Gold, Silver, et cetera Sponsorship program. Or for example can collect funds from a list of partners similar to for example http://moodle.com/partners/list/ Thanks Sebastian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] DeltaSpike to join the Incubator
+1 binding Regards, Alan On Dec 4, 2011, at 2:11 PM, Gerhard Petracek wrote: Hello, Please vote on the acceptance of DeltaSpike into the Apache Incubator. The proposal is available at [1] and its content is also included below for your convenience. Please vote: [ ] +1 Accept DeltaSpike for incubation [ ] +0 Don't care [ ] -1 Don't accept DeltaSpike for incubation because... The vote is open for 72 hours. Thanks, Gerhard [1] http://wiki.apache.org/incubator/DeltaSpikeProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Non English Mailing Lists
On Wed, Dec 14, 2011 at 7:34 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Hi, I would like to clarify if Non-English Mailing lists are allowed. Background: I missed in our Proposal the Mailing List: http://groups.google.com/group/openmeetings-en-espanol/about?hl=en_US We made now a Vote on our Developer List to add this mailing list and the Moderators from the GoogleGroups List have applied to become the Moderator of the new list. Everythings fine from my point of view. But I've heard that using Non-English List is not allowed on Apache Infrastructure. Is that true? It makes me wonder as the OpenOffice project has 100++ Mailing lists in a lot of different languages. So I guess there is no such restriction and we can proceed right? Aside from the good advice Ross gave, I'd point out one technical issue we did run into with the OpenOffice podling. The issue was related to character encoding and mailing list archives. The issue is here: https://issues.apache.org/bugzilla/show_bug.cgi?id=52195 So depending on what language you are looking at, this may or may not be an issue for you. -Rob Thanks, Sebastian -- Sebastian Wagner http://www.openmeetings.de 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] accumulo-1.3.5-incubating RC10
Hey folks, Our 72 hour minimum window has passed, and unfortunately we have not gotten enough approving votes (though no unvotes). I believe we only need one more IPMC approval vote to wrap up our first release, so if one of you could take a bit of time to look through RC10 and approve it (or provide criticism) that would be stellar. Cheers John - Original Message - | From: Eric Newton eric.new...@gmail.com | To: general@incubator.apache.org, accumulo-...@incubator.apache.org | Sent: Thursday, December 8, 2011 11:22:01 AM | Subject: [VOTE] accumulo-1.3.5-incubating RC10 | If at first you don't succeed... hopefully this candidate passes all | the | hurdles. | | Please vote on releasing the following candidate as Apache Accumulo | (incubating) version 1.3.5. This will be the first incubator release | for | Accumulo. | | This release candidate fixes the license documentation issues found in | rc9: | * Added the BSD license to the LICENSE file for jline | * Added the missing entry in NOTICE for the bloom filter files | | I generated the tarballs by exporting | https://svn.apache.org/repos/asf/incubator/accumulo/tags/1.3.5rc10 | then running tar cvzf to create the src and running | ./src/assemble/build.sh to create the dist. | | Tarballs, checksums, signatures: | | http://people.apache.org/~ecn/ | | | MD5 sums: | | 17e0c980a55b7be3abe560a38422e037 | accumulo-1.3.5-incubating-rc10-dist.tar.gz | 9e5bbca4935d3b80869cbabb9a52608d | accumulo-1.3.5-incubating-rc10-src.tar.gz | | | SVN tag: | | https://svn.apache.org/repos/asf/incubator/accumulo/tags/1.3.5rc10 | | | Keys: | | http://www.apache.org/dist/incubator/accumulo/KEYS | | | Given the amount of time allowed for the previous 3 calls and nature | of the | latest changes, I would like this to be a 24 hour vote. | | Thanks, | | -Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1213736 - in /incubator/public/trunk: site-author/projects/openmeetings.xml site-publish/projects/openmeetings.html
On 13 December 2011 15:27, sebawag...@apache.org wrote:
Author: sebawagner
Date: Tue Dec 13 15:27:36 2011
New Revision: 1213736
URL: http://svn.apache.org/viewvc?rev=1213736view=rev
Log:
Update OpenMeetings committers account names
Modified:
incubator/public/trunk/site-author/projects/openmeetings.xml
incubator/public/trunk/site-publish/projects/openmeetings.html
Modified: incubator/public/trunk/site-author/projects/openmeetings.xml
URL:
http://svn.apache.org/viewvc/incubator/public/trunk/site-author/projects/openmeetings.xml?rev=1213736r1=1213735r2=1213736view=diff
==
--- incubator/public/trunk/site-author/projects/openmeetings.xml [utf-8]
(original)
+++ incubator/public/trunk/site-author/projects/openmeetings.xml [utf-8] Tue
Dec 13 15:27:36 2011
@@ -135,12 +135,12 @@
/tr
tr
td./td
- tdsolomax/td
+ tdsolomax666/td
Why was that entry changed?
AFAICT, there is no such login as solomax666, however there is a
solomax login which is also listed in the iclas file.
tdMaxim Solodovnik/td
/tr
tr
td./td
- td/td
+ tdsxander/td
tdSascha Xander/td
/tr
tr
@@ -150,7 +150,7 @@
/tr
tr
td./td
- td/td
+ tdeschwert/td
tdEugen Schwert/td
/tr
tr
Modified: incubator/public/trunk/site-publish/projects/openmeetings.html
URL:
http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/projects/openmeetings.html?rev=1213736r1=1213735r2=1213736view=diff
==
--- incubator/public/trunk/site-publish/projects/openmeetings.html [utf-8]
(original)
+++ incubator/public/trunk/site-publish/projects/openmeetings.html [utf-8]
Tue Dec 13 15:27:36 2011
@@ -1,534 +1,534 @@
-!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
- http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
-!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- License); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
---
-html xmlns=http://www.w3.org/1999/xhtml;
- head
- meta http-equiv=Content-Type content=text/html; charset=utf-8 /
- link rel=stylesheet href=../style/bootstrap-1-3-0-min.css
type=text/css /
- link rel=stylesheet href=../style/style.css type=text/css /
- titleOpenMeetings Incubation Status - Apache Incubator/title
-
- /head
- body
- div class=container
- div class=row
-div class=span12
- a href=http://www.apache.org/;img
src=http://www.apache.org/images/asf_logo_wide.gif; alt=The Apache Software
Foundation border=0//a
-/div
-div class=span4
-a href=http://incubator.apache.org/;img
src=../images/apache-incubator-logo.png alt=Apache Incubator
border=0//a
-/div
-/div
- div class=rowdiv class=span16hr noshade=noshade
size=1//div/div
-
- div class=row
- div class=span4
- form action=http://www.google.com/search; method=get
- input value=incubator.apache.org name=sitesearch type=hidden/
- input size=20 name=q id=query type=text value=search...
- onclick=if(this.value == 'search...') {this.value = ''}/
- input name=Search value=Go type=submit/
- /form
- div class=menuheadera
-href=../projects/index.htmlIncubator Projects/a/div
- menu compact=compact
- /menu
- div class=menuheadera
-href=http://www.apache.org/foundation/glossary.html#Podling;Podlings
(What's that?)/a/div
- menu compact=compact
- lia href=../incubation/Incubation_Policy.htmlHow?
(Policy)/a/li
- lia href=../incubation/Roles_and_Responsibilities.htmlWho?
(Roles)/a/li
- lia href=../incubation/Process_Description.htmlWhen?
(Process)/a/li
- /menu
- div class=menuheadera
-href=../guides/index.htmlEntry Guides/a/div
- menu compact=compact
- lia href=../guides/proposal.htmlProposal Guide/a/li
- /menu
- div class=menuheadera
-href=../guides/index.htmlPodling Guides/a/div
- menu compact=compact
- lia href=../guides/committer.htmlPodling Committers/a/li
-
Re: so the deadline for podling reports has passed, now what?
Some reports missing: HISE, Kato, Wave. Would all podling developers please see http://wiki.apache.org/incubator/ReportingSchedule and put an entry in your calendar. Some mentors missing: RAT. Moderators: I looked at some dev lists and saw that their marvin reminders were not moderated. (Cannot remember which, perhaps HISE.) Is there some way that we can be sure that all lists are actively moderated? A discussion was commenced about how to streamline the whole of Incubator SCM authorisation, while addressing the associated issues and ramifications. Unfortunately the thread dwindled before reaching a solution. http://mid.gmane.org/232b0baa-64eb-4a96-853a-97d2f4400...@gbiv.com Subject: incubator is a single group -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Bloodhound
The discussion has been minimal, and has ramped down. Time to move to a vote? (I had hoped to see some people volunteer...) Cheers, -g On Dec 2, 2011 10:53 AM, Hyrum K Wright hyrum.wri...@wandisco.com wrote: Hello Incubator! WANdisco would like to propose the inclusion of a new project, Apache Bloodhound, to the Incubator. The proposal has been posted to the wiki[1], and is also included below. We've privately discussed this project with a number of individuals, but would now like to get the discussion rolling here. Bloodhound is new effort, based on Trac[2], to provide issue tracking and collaboration tools for developers. We realize the proposal is a work-in-progress, and as such look forward to feedback and discussion. We hope to attract mentors and other interested parties through the incubation proposal process, and further diversify the community as we move through incubation. In particular, this project is an opportunity to build a new community around the codebase, and we look forward to doing so at the ASF. -Hyrum [1] http://wiki.apache.org/incubator/BloodhoundProposal [2] http://trac.edgewall.org/ = Bloodhound - Collaborative development tools based on Trac = == Abstract == Bloodhound will be a software development collaboration tool, including issue tracking, wiki and repository browsing. Essentially an improved distribution of the well-known Trac project, Bloodhound will include the common and useful plugins to enable a more complete distribution than a typical Trac installation. == Proposal == Bloodhound will be a software development collaboration tool, based on the existing Trac project, which will include a repository browser, wiki, and defect tracker. In addition to the standard Trac installation, Bloodhound will incorporate a number of popular modules into the core distribution, and include additional improvements developed (as [[http://trac-hacks.org/|plugins]]) outside the Trac project. == Background == The [[http://trac.edgewall.org/|Trac project]] is a BSD-licensed collaboration tool used to assist in software development. It has a wide user base, a pluggable infrastructure, and is generally considered stable. By it's own recognition, however, the development community surrounding Trac has largely dissipated, with little mailing list traffic, and very few commits to the source code repository (see [2]). Private efforts to engage the existing developers in implementing features have been negatively received. At the same time, other individuals and companies, such as [[http://www.wandisco.com|WANdisco]], have expressed interest in helping continue to develop Trac. These entities would prefer this effort to be at a vendor-neutral location, with the clear process for intellectual property management that comes from the Foundation. As such, the Apache Software Foundation feels like the best fit for this new project based on Trac. == Rationale == As discussed earlier, the current Trac development community is small and reluctant to accept outside contributions. Given the Foundation’s reputation for building and maintaining communities, we feel a new project, based on Trac but incubated under the Apache umbrella, would help re-build the developer community, jump started by developer time donated by WANdisco. Additionally, as a developer tool, Bloodhound is a good fit with other, similarly-focused developer tools at the ASF. Private discussions have shown there is some interest by third-parties to release internal improvements to Trac, and Bloodhound gives them an additional venue to do so. == Initial Goals == The initial goals for Bloodhound primarily revolve around migrating the existing code base and integrating external features to make the project easy to deploy. Additional ideas will of course follow, but the following goals are sufficiently difficult to be considered early milestones. Some of the initial goals include: * Migrate the existing BSD-licensed Trac code base to the ASF. * Attract developer and user interest in the new Bloodhound project. * Incorporate externally developed features into the core Bloodhound project. * Package the most popular plugins into the core project, so installations and administration of Bloodhound becomes dead simple. = Current Status = == Meritocracy == Although initially corporate-sponsored, any interested developers would be granted commit access. Even developers employed by the sponsoring companies would be required to demonstrate competency to gain commit privileges. Individuals with corporate affiliations would understandably be known within the community, but would not have bearing on the granting of commit privileges. == Community == One of the primary purposes of this proposal is to develop a strong developer community around the Trac code base. The current developers and supporting institution have moved on to
RE: October 2011 Incubator Board Report
Our next report is due in December, not October. Nu? So where is it? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Bloodhound
On Mon, Dec 12, 2011 at 2:41 AM, Greg Stein gst...@gmail.com wrote: On Dec 12, 2011 3:12 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Fri, Dec 2, 2011 at 4:53 PM, Hyrum K Wright hyrum.wri...@wandisco.com wrote: By it's own recognition, however, the development community surrounding Trac has largely dissipated, with little mailing list traffic, and very few commits to the source code repository (see [2]). Private efforts to engage the existing developers in implementing features have been negatively received. At the same time, other individuals and companies, such as [[http://www.wandisco.com|WANdisco]], have expressed interest in helping continue to develop Trac. These entities would prefer this effort to be at a vendor-neutral location, with the clear process for intellectual property management that comes from the Foundation. Do you have pointers to public discussions about this? Without a well-documented history of attempts and failure to engage with the existing developers this could easily be seen as a hostile fork. I've seen some offlist discussions with the principals behind Trac. This has not caught them unaware. One of those devs even created a wiki page at Edgewall for Bloodhound: http://trac.edgewall.org/wiki/BloodHound?action=diffversion=1 My impression of their view is ambivalence. Most notably, has the idea of bringing Trac itself to the ASF been presented to Edgewall? What was their response? Hyrum has seen more of the discussion and could answer better, but my read is that ambivalence again. They aren't going to put in an effort themselves to move Trac itself. I seem to recall a couple of the devs are interested in the move, and want to see how it goes. That pretty much captures it. The complete discussion on the trac-dev mailing list is here: http://groups.google.com/group/trac-dev/browse_thread/thread/14268355c6e1d494 -Hyrum - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: so the deadline for podling reports has passed, now what?
Some reports missing: HISE, Kato, Wave. If they are not posted by tomorrow AM, the report is going in without them. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
