David S Taylor | 27 Mar 20:32 2015

Using id.apache.org

I’ve been away from working with Apache releases for a few years now. Seems I missed out (didn’t pay
attention) to some important credentials migration instructions. I’d like to be able to ssh to
people.apache.org <http://people.apache.org/>, and also get my LDAP account setup. Can anyone help me
with this? Do I need to create an Infra JIRA? I see that id.apache.org <http://id.apache.org/> is
self-provisioning, but its not really clear what I need to do there.

Can someone please help? I’d like to start on a release soon… (IM a committer
(taylor@...
<mailto:taylor@...>), and PMC member of Apache Portals)

Thanks,

--
David 
taylor@...

jan i | 27 Mar 11:28 2015
Picon

Help promote apacheCON NA 2015, and meet friends/colleagues while attending.

Hi fellow ASFer.

I am going to apacheCON NA Austin in just over 2 weeks. I hope, so are you.

We need your help to promote apacheCON NA and get more people to come.

More people attending apacheCON, means more visibility for Apache and your
project(s), but just as important, more tickets sold, means we can make the
event even better for all of us.

I have prepared (with help from Linux Foundation) a few examples of how you
help promote the event:

Feel free to use these as is, edit them, or write your own, but please help
us get the word out:

Twitter:

Learn more about #ApacheCon speaking sessions at Schedule
<http://goo.gl/BCzJWM> , and register to attend at Register
<http://goo.gl/3Q8GFE>

Join me in Austin for #ApacheCon, the place to learn about the projects
driving the future of open source!

Facebook/Google+:

I’ll be at ApacheCon, the place to learn about and collaborate on the
technologies and projects driving the future of open source, big data and
cloud computing, April 13-16 in Austin. Learn more about the schedule at
(Continue reading)

Noah Slater | 25 Mar 17:00 2015
Picon

Re: Code of Conduct - links to why they are needed etc

Yep, thanks for the reply. I'm not sure how to handle the governance side
of this. But I'm sure we can come to an agreement on this list soon.

On Wed, 25 Mar 2015 at 15:13 jan i <jani@...> wrote:

> On 25 March 2015 at 13:08, Noah Slater <nslater@...> wrote:
>
> > Jan,
> >
> > Late to the party here, sorry. But I wanna reply to your point that the
> CoC
> > is not meant to be enforceable.
> >
> > That is not the case, as I understand it. Indeed, an unenforceable or
> > not-regularly-enforced CoC is not worthless, it's actually *harmful* and
> > dangerous for marginalised people in our community. Because we are
> > communicating to them that we have certain standards, and then not taking
> > any action to make sure that those standards are met.
> >
>
> Maybe I should have spent more words. Of course there are CoC items that
> should and  can be enforced, but to me there
> are also some with quite some elastic built in. For example we have a CoC
> for email, do not use he/she and be polite. The first
> part is easy to enforce, but the second part ? what you see as polite might
> not be polite to me.
>
>
> >
> > A community is, in many ways, defined by whatever its leaders are
(Continue reading)

Dennis E. Hamilton | 23 Mar 17:17 2015
Picon

ACEU Presentation Template

Truly back at the same venue?  <http://events.linuxfoundation.org/events/apachecon-europe>.  The
hotel that gave rise to an Apache Project (incubating).  Great!

Wow, the logo with just "ApacheCon Europe" over the feather is great.  Much easier to customize that one just
once for Europe, and just once for North America.  It also appears that many of the slide used had more
simplicity of backgrounds.

That I can handle, with backgrounds and venue information separately customizable.

Remind me at OSCON if I haven't done it already.

 - Dennis

-----Original Message-----
From: Rich Bowen [mailto:rbowen@...] 
Sent: Monday, March 23, 2015 06:56
To: dev@...
Subject: Re: ACNA Presentation Template

On 03/22/2015 12:40 PM, Dennis E. Hamilton wrote:
[ ... ]
> In anticipation of the next AC-anywhere, I want to help turn this (and the previous two under Linux
Foundation) into a form that can be repurposed/reused/customized along with information on how to do it
and the resources/skills that are required.
>
> Removing the crunch requirement is great.

Well, we need one for AC Europe, too. so there's about 6 months to work 
on that one. :-)

(Continue reading)

r01942072 | 23 Mar 13:28 2015
Picon

Apache POI CTPageMar not found

I am using eclipse. I download Apache POI 3.12 Beta 1, add all jar files into java build path, but eclipse
tells me that CTPageMar not found. Part of my code is shown below.

XWPFDocument doc = new XWPFDocument();
CTDocument1 doc1 = doc.get Document();
CTBody body = doc1.getBody();
CTSectPr sect = body.getSectPr();
CTPageMar mar = sect.getPgMar();

Only the last line contains error because CTPageMar not found.
Kay Schenk | 22 Mar 22:04 2015
Picon

gtk requirements for builds?

GTK is enabled by default for our builds.

I don't see this listed as a build requirement for either Windows or
Mac, however. So, should this build flag be changed to non-enabled
generally and only enabled for Linux?

--

-- 
-------------------------------------------------------------------------
MzK

“What is the point of being alive if you don't
 at least  try to do something remarkable?”
       -- John Green, "An Abundance of Katherines"

Bertrand Delacretaz | 22 Mar 13:56 2015
Picon

Re: Veto! Veto?

Hi,

On Sat, Mar 21, 2015 at 2:04 AM, Pierre Smits <pierre.smits@...> wrote:
> ...The following document https://community.apache.org/newcommitter.html
> states:
>
> A positive result is achieved by Consensus Approval i.e. at least 3 +1
> votes and no vetoes....

There are no vetoes when electing committers, that document is wrong.

https://www.apache.org/foundation/voting.html is the canonical
document about Apache votes, it specifies vetoes only for code
commits.

-Bertrand

Alex Harui | 21 Mar 05:24 2015
Picon

Re: Veto! Veto?

Consensus Approval works great until you have someone who others rightly
or wrongly perceive as an obstructionist.  Then it just makes the whole
project the loser.

At least one project uses majority approval for new members, but a serious
attempt is made to make sure that the vote is unanimous anyway.  Those in
opposition deserve to be listened to, but if there are only one or two
against and lots more in favor, then majority approval avoids long threads
trying to persuade the one or two.  Sure discussing more to achieve
Consensus can be better, but you can also lose momentum of the committer
candidate and momentum of the rest of the community.

The -1 vote is an alluring drug.  It can be misused by individuals who,
consciously or not, cannot avoid the temptation to have control rather
than to collaborate.  But really make sure you listen.  History is full of
disasters caused by not listening to that one person.

-Alex

On 3/20/15, 6:04 PM, "Pierre Smits" <pierre.smits <at> gmail.com> wrote:

>Hi all,
>
>If I understand the various documents/pages available regarding voting
>correctly, voting a new member in can't be vetoed. Likewise is it with
>respect to voting for board members. If I have missed a page somewhere,
>please point me to it and I stand corrected.
>
>The following document https://community.apache.org/newcommitter.html

>states:
(Continue reading)

Shane Curcuru | 21 Mar 04:49 2015

Re: Veto! Veto?

On 3/20/15 9:04 PM, Pierre Smits wrote:
> Hi all,
> 
> If I understand the various documents/pages available regarding voting
> correctly, voting a new member in can't be vetoed. Likewise is it with
> respect to voting for board members. If I have missed a page somewhere,
> please point me to it and I stand corrected.

Board and new Member voting at the Foundation level are clearly
documented - note that these are specific procedures that are
*different* from best practices for PMC voting on new committers.

  https://wiki.apache.org/general/MemberVoting
  https://wiki.apache.org/general/BoardVoting

In particular since the Board voting process uses STV there are only
positive votes, no negative votes for candidates (obviously, you can
withhold voting from some candidates).

> 
> The following document https://community.apache.org/newcommitter.html
> states:

That also notes at the top:

"Each project has different approaches to managing new committers, this
page describes a common process found in many Apache projects"

It is important to have best practices for all projects, and for
projects to document their own specific ways to make decisions.  But the
(Continue reading)

Marvin Humphrey | 21 Mar 03:45 2015

Re: Veto! Veto?

On Fri, Mar 20, 2015 at 6:04 PM, Pierre Smits <pierre.smits@...> wrote:

> Wouldn't a simple majority (more +1 than -1 votes) yield the same result?

Majority rule votes degrade community.  Whenever you have a contended vote,
you produce losers who feel alienated[1].  In contrast, consensus decision
making forces the majority to take account of minority opinions.  The
negotiation process may frustrate everyone to some extent, but it's less
exclusionary.

Avoiding majority rule and preferring consensus is one of the fundamental
design decisions which have made Apache successful.  The same community might
well produce different solutions to the same problem depending on the rules
for resolving conflict.

In the case of a VOTE to invite a new PMC member, there's no way to negotiate
an alternative solution to take into account the concerns of the minority.
However, those in favor will have to account for those concerns and those
opposed will need to defend their stance.  The act of talking things through
should help to keep the community whole.

Marvin Humphrey

[1] Anime explanation of how majority-rule voting alienates the minority:
    http://www.crunchyroll.com/hunter-x-hunter/episode-10-trick-x-to-the-x-trick-585058?t=429
    (Warning: autoplay video and multiple ads before the content starts)

Pierre Smits | 21 Mar 02:04 2015
Picon

Veto! Veto?

Hi all,

If I understand the various documents/pages available regarding voting
correctly, voting a new member in can't be vetoed. Likewise is it with
respect to voting for board members. If I have missed a page somewhere,
please point me to it and I stand corrected.

The following document https://community.apache.org/newcommitter.html
states:

A positive result is achieved by Consensus Approval i.e. at least 3 +1
votes and no vetoes.

Any veto must be accompanied by reasoning and be prepared to defend it.
Other members can attempt to encourage them to change.

While this document talks about getting new committers in a project, it
also seem to be applicable when it comes to getting new PMC members and
even who chairs the PMC.

So how can it be that when it comes to projects, vetoes can be expressed
and block innovation or growth?
One of the reasons I heard when discussing this was that it establishes
control or manageability of the projects member list.

Wouldn't a simple majority (more +1 than -1 votes) yield the same result?
If someone would feel that non-acceptance of a new person would benefit the
project, wouldn’t it be more proper/righteous  that he should put in the
effort and get a majority of votes?

(Continue reading)


Gmane