Pierre Smits | 4 Jul 18:34 2015

Incubating, Graduating & Code of conduct <at> The ASF (spin-off of Better specifying....)

>> Having such an official ASF policy without the executing office policing
>> it, without podlings being required to accept and instill it in their
>> bylaws before graduation and allowing existing projects not to
>> it makes it nothing more than a hollow statement,
> Being part of IPMC, I thought it was part of the incubator to make sure
> exactly this happened.

Having done a cursory review of the incubator reports to the board for this
year (January till May/June 2015), I found that only the SAMOA podling
reported working on a project set of bylaws, which without knowing details
could encompass and/or incorporate the code of conduct.
None of the other podlings reported about that. Having looked also at the
board reports for January up to May 2015 I found that podlings graduating
to TLP were either tasked by the board to establish a set of bylaws or not.

This tells me that acceptance/incorporation of the code of conduct of the
ASF by the podlings is not a requirement.
It might also mean - given the code of conduct as it is today - that IPMC
members (as mentors) are either not fully aware that
acceptance/incorporation is part of incubation process, or that they
consider it optional.

What I also observed from the board reports (minutes) from Jan till May is
that while graduating podlings (as part of their establisment as a TLP)
where tasked by the board to create a set of bylaws, that up to now those
projects (Apache Whimsy, Apache Orc, Apache Parquet, Apache Aurora, Apache
Zest) don't reference anything about a set of bylaws.
(Continue reading)

sebb | 4 Jul 16:48 2015

Re: svn commit: r1689145 - in /comdev/projects.apache.org/site: doap/whimsy/whimsy.rdf json/projects/whimsy.json

On 4 July 2015 at 12:36,  <hboutemy@...> wrote:
> Author: hboutemy
> Date: Sat Jul  4 11:36:45 2015
> New Revision: 1689145
> URL: http://svn.apache.org/r1689145
> Log:
> added Whimsy files
> Added:
>     comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf
>     comdev/projects.apache.org/site/json/projects/whimsy.json
> Added: comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf
> URL: http://svn.apache.org/viewvc/comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf?rev=1689145&view=auto
> ==============================================================================
> --- comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf (added)
> +++ comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf Sat Jul  4 11:36:45 2015
>  <at>  <at>  -0,0 +1,40  <at>  <at> 
> +<?xml version="1.0"?>
> +<?xml-stylesheet type="text/xsl"?>
> +<rdf:RDF xml:lang="en"
> +         xmlns="http://usefulinc.com/ns/doap#"
> +         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> +         xmlns:asfext="http://projects.apache.org/ns/asfext#"
> +         xmlns:foaf="http://xmlns.com/foaf/0.1/">
> +<!--
> +    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.
(Continue reading)

Pierre Smits | 1 Jul 13:31 2015

ApacheCON CORE? ApacheCon!

Who, in his moment of brightness, dreamed up the notion that a perfectly
accepted household name (and thereby a de facto brand) as ApacheCon for the
main event of the ASF would benefit from adding an extension like CORE?

ApacheCon in itself doesn't eat into the impact of the joint event 'Apache
Big Data', as that name doesn't have Con attached to Apache in all
promotions done up to now... Or dilutes the branding impact of that event.

Is there a negative connotation with the name that it would benefit from
the CORE extension?

Best regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade

On Wed, Jul 1, 2015 at 2:20 PM, jan i <jani@...> wrote:

> We have now passed the deadline for submitting talks to ApacheCON CORE in
> Budapest.
> We have received 156 submissions, which now will be reviewed. Thanks a lot
> for the
> big interest.
(Continue reading)

jan i | 1 Jul 13:20 2015

ApacheCON CORE and Apache Big Data, Budapest 28 september - 2 October.

We have now passed the deadline for submitting talks to ApacheCON CORE in

We have received 156 submissions, which now will be reviewed. Thanks a lot
for the
big interest.

It is already now clear, that some talks have been submitted to both
events, and some
talks submitted to CORE; really fits better in big data. The ApacheCON team
will contact
the authors shortly, to clarify these cases.

Apache Big Data has July 10th as deadline for CFP. There are a lot of open
slots here.

Please do not hesitate to submit your proposal for Apache Big Data.

on behalf of the ApacheCON Team.
jan i.
Suresh Marru | 30 Jun 20:10 2015

Hosting Searchable Release Specific Documentation

Hi All,

Can I get some advice on how projects deal with hosting release specific documentation? In addition to the
CMS and Wiki, I am exploring alternatives which have a good search built-in. I preciously came across ASF
projects hosting documentation on read the docs [1] and floss manuals [2] (sorry I could not trace all the
links of projects using them, but [3] and [4] are examples). I read the thread on github pages [5], but it did
not have a conclusive end. 

I am looking for something immediate, any suggestions please? It will be great if there is a precedence so we
could just refer or even better plagiarize the scripts or approaches.


[1] - https://readthedocs.org/ <https://readthedocs.org/>
[2] - http://en.flossmanuals.net/ <http://en.flossmanuals.net/> 
[3] - https://readthedocs.org/projects/cloudstack-administration/ <https://readthedocs.org/projects/cloudstack-administration/>
[4] - https://readthedocs.org/projects/trafficserver/ <https://readthedocs.org/projects/trafficserver/>
[5] - http://markmail.org/thread/bmbi65q7zdiej6dj <http://markmail.org/thread/bmbi65q7zdiej6dj>

Bertrand Delacretaz | 30 Jun 13:01 2015

Better specifying the scope of our Code of Conduct


Someone mentioned to me that they find the first paragraph of
http://www.apache.org/foundation/policies/conduct.html overly broad,
and I tend to agree.

That paragraph says "this code of conduct governs how we behave in any
forum and whenever we will be judged by our actions" which implies
that it also applies outside of "ASF territory" - I don't think that's
appropriate. The next paragraph mentions "spaces managed by the Apache
Software Foundation" which I find much more appropriate, maybe
expanded with "and whenever we represent the ASF".

The reasoning is that we can only speak about our own territory.

As a simple example, putting your hand on someone's shoulder while
talking to them is totally welcome in some cultures while considered
"unwelcome sexual attention" (to reuse the words of that document) in
others. We might ask people to refrain from doing that in our
multi-cultural environment where we need to go down to some common
denominator of acceptable behavior, but we can't blame them for doing
that where it's culturally acceptable and even expected. The same goes
with profanity, where the acceptable level varies immensely between

So I think it's good to restrict our code of conduct to our own territory.

I suggest reworking the first few paragraphs as follows, to clarify that:

*** reworked code of conduct intro section ***
(Continue reading)

Niclas Hedhman | 30 Jun 11:47 2015

Mailing list subscriptions

The page https://www.apache.org/foundation/mailinglists.html is written
with "foundation level" subscription in mind.

Which I think means that every PMC needs to replicate the same information
about how to subscribe to a mailing list.

Would it make sense to expand the "Project Mailing Lists" section with
generic instructions on how to subscribe?? If so, where would I find the
sources, so I can submit a patch?


Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
sebb | 30 Jun 02:20 2015

Reporter.apache.org displaying incorrect data - who is responsible for the host?

Reporter.apache.org is showing misleading PMC membership data.

As this is used in board reports, it really ought to be fixed ASAP.

However the fixes I made to SVN have not been applied, and there is no
documentation I could find on how the host has been set up - nor how
the faulty data is generated.

Who is responsible for maintaining the host and updating the software on it?

Rich Bowen | 29 Jun 21:42 2015

Upcoming Apache Meetups

The following are the meetups I'm aware of in the coming week where
Apache enthusiasts are likely to be present. If you know
of others, please let me know, and/or add them to

If there's a meetup in your area, please consider attending. If you
attend, please consider taking a few photos, and possibly even writing
up a brief summary of what was covered.


* Mon Jun 29 in Buenos Aires, AR: Por qué cambiar de Hadoop a Spark? 
Teoria y ejemplos de nuestra experiencia - 

* Mon Jun 29 in Manchester, 18, GB: Scala, The Modular Language. - 

* Mon Jun 29 in Alpharetta, GA, US: Learn How to Add Search to .NET with 
Solr & SolrNet - 

* Tue Jun 30 in Chicago, IL, US: Overview of Apache Flink: Next-Gen Big 
Data Analytics Framework - 

* Tue Jun 30 in Cambridge, MA, US: June Presentation Night - 

* Tue Jun 30 in Chennai, IN: Best practices for building statistical 
(Continue reading)

Martijn Dashorst | 29 Jun 10:36 2015

New committer PMC faq linkage on site

When trying to find all the resources for adding a new committer and
PMC member, the community site is pretty awesome, but it is completely
undiscoverable from a search engine because it is hidden by the
foundation wide PMC faq that doesn't link to the community development

Can someone with site authority update the apache.org/dev pages and
link them to the community site?

This is awesome:


This awesome as well, but not as awesome as the page above:



jan i | 28 Jun 15:24 2015

48 hours left to get your free ticket to apacheCON Core, budapest.


CFP for apacheCON core will close in around 48 hours (1 July).

Submit a talk, if accepted, you will get a free ticket.

Looking forward to see you all in Budapest.

on behalf of the apacheCON team
jan i.

ps. mail me if you have questions or comments.