Retiring Podlings

2020-10-02 Thread Drew Foulks 
Hello People of the Attic!

I see that taverna has been listed as retired on the incubator website, and
I've confirmed with justin that the podling is supposed to be retired.

Generally speaking: what is infra supposed to do when a podling doesn't
have enough people to vote on retirement.

Should we wait for someone at the Incubator to file a ticket stating that
the podling is to be retired?

More specifically: should someone from the incubator file an infra ticket
to retire taverna? (There are project resources for taverna that haven't
been decommissioned.)

-- 
Cheers,

Drew Foulks
 ASF Infra

Re: taverna podling

2020-07-14 Thread Drew Foulks 
Justin,

Is someone from the PPMC available to file a podling retirement ticket with 
infra?

cheers,

On 2020/07/10 23:00:08, Justin Mclean  wrote: 
> Hi,
> 
> > What is the status of the taverna podling? The incubator website says it's
> > retired but the taverna website says it's still going.
> 
> They have retired see [1]. I'd say the web site just hasn’t been updated.
> 
> Thanks,
> Justin
> 
> 1. https://github.com/apache/incubator-taverna-engine
> -
> 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

taverna podling

2020-07-10 Thread Drew Foulks 
Hi Incubator folks,

What is the status of the taverna podling? The incubator website says it's
retired but the taverna website says it's still going.

cheers,

Drew Foulks, ASF Infra

Re: May 2019 report timeline

2019-04-20 Thread Drew Farris 
Perfect. Thanks Justin, thanks Dave.

On Sat, Apr 20, 2019 at 6:00 PM Justin Mclean 
wrote:

> HI,
>
> Drew you were assigned to Milagro  and Pinot, was a copy paste error when
> I was trying to reformat the page.
>
> Thanks,
> Justin
>

Re: May 2019 report timeline

2019-04-20 Thread Drew Farris 
Hi All,

I noticed that I fell off the shepherds list for May. Did something change
with the way shepherds are assigned after the report moved to Confluence?

Thanks,
Drew

On Thu, Apr 18, 2019 at 9:54 PM Justin Mclean 
wrote:

> Hi,
>
> Report timeline for May:
> Wed May 01  -Podling reports due by end of day
> Sun May 05 - Shepherd reviews due by end of day
> Sun May 05 - Summary due by end of day
> Tue May 07 - |Mentor signoff due by end of day
> Wed May 08 - Report submitted to Board
> Wed May 15 - Board meeting
>
> Podlings expect to report:
> DataSketches
> Doris
> ECharts
> Edgent
> Heron
> Milagro
> MXNet
> PageSpeed
> Pinot
> Ratis
> S2Graph
> SDAP
> Tamaya
> Toree
> Training
> Tuweni
> TVM
>
> Please note that the report location has changed  to the ASF confluence
> incubator space. [1]
>
> Thanks,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire Sirona

2017-06-30 Thread Drew Farris 
+1 to retire.

On Wed, Jun 28, 2017 at 12:32 AM Ralph Goers 
wrote:

> +1 to retire.
>
> Ralph
>
> > On Jun 26, 2017, at 9:50 AM, John D. Ament 
> wrote:
> >
> > All,
> >
> > This is a call to vote the Sirona podling.
> >
> > A vote was called for on the dev list for Sirona [1], of which one mentor
> > commented and that's all.
> >
> > Sirona at this point is behind 6 months on reports, has shown little
> > activity since joining the incubator.  Its not clear there are 3 PPMCs
> > available for a vote if need be.  Based on the prior discussions ([2] &
> > [3]) and these items, I'd like to call for a vote and unilateral decision
> > by the IPMC to retire Sirona.
> >
> > [ ] +1 to retire Sirona
> > [ ] -1 don't retire Sirona because...
> >
> > Here is my +1.
> >
> > John
> >
> > [1]:
> >
> https://lists.apache.org/thread.html/673daa1452150ed5ef0df4aa77f587dbac6e5a4a63670c6bf4809b17@%3Cdev.sirona.apache.org%3E
> > [2]:
> >
> https://lists.apache.org/thread.html/0a70d486680f0339bfcb4baae23c2540095fda90ca83eb414104a6fd@%3Cgeneral.incubator.apache.org%3E
> > [3]:
> >
> https://lists.apache.org/thread.html/438298290de9a3573b5e315b12e77191b27f8d91b50cf9f97e90cba8@%3Cgeneral.incubator.apache.org%3E
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Gossip version gossip-0.1.1-incubating (RC2)

2017-01-15 Thread Drew Farris 
Hello,

+1 (binding)

I checked:
- name includes incubating
- disclaimer exists
- notice looks good (echo Justin's comment re: 2106 vs 2017)
- commit 6720f35beb8 is present at git://git.apache.org/incubator-gossip.git
- binary distribution builds
- gpg signatures OK (echo Justin's comment re: signing address)
- checksums OK
- no binary files in release
- can compile from source

Thanks for the release,

Drew

On Thu, Jan 12, 2017 at 1:48 AM Justin Mclean <jus...@classsoftware.com>
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - name includes incubating
> - disclaimer exists
> - notice good (but year last year - please update in next release)
> - all source files have ASF header
> - no binary files in release
> - can compile from source
>
> Next time could you please:
> - Place the artefacts for voting on in [1] that way they can be released
> with an svn mv command.
> - Can you sign the artifact with an apache email address rather than
> edlinuxg...@gmail.com.
>
> README without a license header is fine IMO [1] but no harm in including
> one either.
>
> Thanks,
> Justin
>
> 1. https://dist.apache.org/repos/dist/dev/incubator/gossip/
> 2. https://www.apache.org/legal/src-headers.html#faq-exceptions
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

2017-01-07 Thread Drew Farris 
+1 (binding)

On Sat, Jan 7, 2017 at 12:56 AM Niclas Hedhman  wrote:

> +1 (binding)
>
> On Sat, Jan 7, 2017 at 6:29 AM, Owen O'Malley  wrote:
>
> > +1 (binding)
> >
> > On Wed, Jan 4, 2017 at 5:15 PM, Balaji Ganesan <
> balaji.ganesa...@gmail.com
> > >
> > wrote:
> >
> > > +1 Great to see the progress from the Ranger community.
> > >
> > > On Wed, Jan 4, 2017 at 4:54 PM, Suneel Marthi 
> > wrote:
> > >
> > > > +1 binding
> > > >
> > > > On Wed, Jan 4, 2017 at 5:48 PM, Ramesh Mani 
> > > wrote:
> > > >
> > > > > Dear Incubator members,
> > > > >
> > > > > Apache Ranger Project community has successfully released 0.6.2
> > version
> > > > > and with it there had been a lot of discussion within Apache Ranger
> > > > > community to consider graduation to TLP. Apache Ranger entered into
> > > > > incubation on 24th July 2014 and from this welcoming community had
> > > done a
> > > > > tremendous job in resolving various technical hurdles like
> > refactoring
> > > > the
> > > > > project core model to  be service based, adding more Apache Hadoop
> > > > > components like Apache YARN, Apache Storm, Apache Kafka, Apache
> Nifi,
> > > > > Apache Ranger KMS into Ranger Authorizing  model for security and
> > > making
> > > > it
> > > > > into a core product in the Apache Hadoop security space. PPMC has
> > > > exhibited
> > > > > a clear understanding of this growing apache community by
> electing  4
> > > > > individuals as committers  and  inculding 22 individuals as
> > > contributors
> > > > to
> > > > > the Apache Ranger project. PPMC also has done 8 successful releases
> > > under
> > > > > the guidance of mentors demonstrating their mastery over AFS’s IP
> > > > policies.
> > > > >
> > > > > An voting was conducted within Apache Ranger Community to graduate
> > > Apache
> > > > > Ranger Project to Top Level Project. Vote passed with 16 +1 votes ,
> > no
> > > 0
> > > > or
> > > > > –1 votes.
> > > > > http://mail-archives.apache.org/mod_mbox/incubator-ranger-
> > > > > dev/201612.mbox/%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
> > > > >
> > > > > Apache Ranger Project has shown a great perspective to become a
> true
> > > TLP.
> > > > > Following summary on the project reflects its accomplishment.
> > > > >
> > > > > Please vote on the Project resolution that is found in bottom to
> > > graduate
> > > > > Apache Ranger Project from Incubator to Top Level Project.
> > > > >
> > > > > [ ] +1 Graduate Apache Ranger from the Incubator.
> > > > > [ ] +0 No opinion
> > > > > [ ] -1 Don't graduate Apache Ranger from the Incubator ( please
> > provide
> > > > > the reason)
> > > > >
> > > > > This VOTE will be opened for next 72 hours.
> > > > >
> > > > > Thanks all Mentors and Apache Ranger Project members for their
> > support
> > > > and
> > > > > contributions.
> > > > >
> > > > > Here is my vote +1 (binding)
> > > > >
> > > > > Project Summary:
> > > > > =
> > > > >
> > > > > http://incubator.apache.org/projects/ranger.html
> > > > >
> > > > > Project website:
> > > > > =
> > > > >
> > > > > http://ranger.incubator.apache.org > incubator.apache.org/
> > > >
> > > > >
> > > > > Project Documentation:
> > > > > ===
> > > > >
> > > > > http://ranger.incubator.apache.org/index.html
> > > > > http://ranger.incubator.apache.org/quick_start_guide.html
> > > > > https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
> > > > >
> > > > > Project maturity Assessment:
> > > > > ===
> > > > >
> > > > > https://cwiki.apache.org/confluence/display/RANGER/
> > > > > Apache+Ranger+Project+Ma
> > > > > turity+Model
> > > > >
> > > > > Proposed PMC size: 17
> > > > >
> > > > > Total number of committers   : 14 members
> > > > > Total number of contributors : 22 members
> > > > >
> > > > > PMC affiliation (* indicated chair)
> > > > >
> > > > > * Hortonworks (9)
> > > > >Privacera (2)
> > > > >BlueTalon (1)
> > > > >Others(1)
> > > > >
> > > > > 1802 commits on develop
> > > > > 22 contributors across all branches
> > > > > Dev list averaged ~50 msgs/month in 2016
> > > > > User list averaged ~40 msgs/month in 2016
> > > > > 1208 issues created
> > > > > 997 issues resolved
> > > > >
> > > > > Committer’s affiliation:
> > > > > ===
> > > > > Active:
> > > > > Hortonworks
> > > > > Talend
> > > > > Freestone infotech
> > > > > BlueTalon
> > > > > eBay
> > > > > Others
> > > > >
> > > > >
> > > > > Apache Ranger Top Level Project Resolution:
> > > > > 
> > > > >
> > > > > Establish the Apache Ranger 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
> >

Re: Looking for a mentor for Gossip and Rya

2016-11-12 Thread Drew Farris 
Hi Sean,

Unless I missed a response, no one has stepped up to mentor Gossip. I'd be
happy to do so.

Drew

On Mon, Nov 7, 2016 at 7:03 PM Sean Busbey <bus...@apache.org> wrote:

> Hi Folks!
>
> Sadly, other commitments in my life require that I step down the amount of
> volunteer time I spend on the ASF. I had originally thought that I'd still
> have time for mentoring the two podlings I've been involved with (Gossip
> and Rya), but it doesn't look that way.
>
> As such, I'm hoping someone on general@ might be convinced to step up in
> either case. My need to step aside should not reflect on the podlings
> themselves; they're both doing just fine for where they are in terms of
> project maturity.
>
> If the particular technology aims matter:
>
> Apache Gossip (incubating) is creating a foundational library for
> distributed systems to use the gossip protocol to make peer-to-peer
> networks. It's written in Java.
>
> Apache RYA (incubating) is an RDF triple store built on top of sparse
> key-value stores (specifically Apache Accumulo is currently the robust
> exemplar implementation). It is also written (mostly) in Java.
>
> I'd say Rya is farther along the path to graduation, but neither podling
> is particularly demanding in terms of kinds-of or amounts-of attention
> required.
>
> Anyone interested in transitioning onto one or both?
>
> -busbey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Fluo Recipes 1.0.0-incubating (rc1)

2016-10-25 Thread Drew Farris 
+1 for this release (IPMC, Binding)

I checked the following:

- hashes good
- signatures good
- name contains incubating
- DISCLAIMER good
- LICENSE good
- NOTICE good
- No binaries in source release
- All source files have required Apache license headers
  - (77 java, 6 poms, 10 markdown, 4 properties)
- Builds successfully with 'mvn clean package'
  - artifacts built contain 'incubating'

Thanks for the release,

Drew

On Mon, Oct 24, 2016 at 12:34 PM Keith Turner <ke...@deenlo.com> wrote:

> Dear IPMC,
>
> Please vote for the following release candidate of Apache Fluo Recipes
> 1.0.0-incubating.
>
> PPMC vote thread:
>
> https://lists.apache.org/thread.html/d1e8ae5cef7c4ab1eac8192b742a3229b346335fec64afd080284dd4@%3Cdev.fluo.apache.org%3E
>
> Staged dist artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/fluo/fluo-recipes/1.0.0-incubating-rc1/
>
> Staged Maven repository:
> https://repository.apache.org/content/repositories/orgapachefluo-1016/
>
> Signing KEYS:
> https://www.apache.org/dist/incubator/fluo/KEYS
> (fingerprint for this release: CF72CA07C8BC86A1C862765F9AACFB56352ACF76)
>
> Git repo:
> https://git-wip-us.apache.org/repos/asf/incubator-fluo-recipes
> (branch: 1.0.0-incubating-rc1,
> commit: 682eff983f1fe6e60b75c36d3b2f782c6a93b155)
>
> This vote will end on Thu Oct 27 17:00:00 UTC 2016
> (Thu Oct 27 13:00:00 EDT 2016 / Thu Oct 27 10:00:00 PDT 2016)
>

Re: [VOTE] Apache Fluo 1.0.0-incubating (rc2)

2016-10-03 Thread Drew Farris 
+1 Binding

I checked:
- DISCLAIMER, LICENSE and NOTICE all look good
- no unexpected binaries in source
- hashes good + signature verified
- builds from source release + unit tests pass
- Source files have ASF headers (except autogenerated files*)
- convenience binary looks good.
- incubating in name.

* I noticed that the following Autogenerated files do not have ASF license
headers:
./modules/core/src/main/java/org/apache/fluo/core/thrift/OracleService.java
./modules/core/src/main/java/org/apache/fluo/core/thrift/Stamps.java
- I don't feel that this is a sufficient reason to fail the incubating
release, but generally think it should be resolved in the next release -
unless there is policy that states it is not strictly required.

On Mon, Oct 3, 2016 at 6:27 PM Christopher  wrote:

> Bump. Just want to remind IPMC this vote ends tonight at 11pm Eastern.
>
> On Fri, Sep 30, 2016 at 10:55 PM Christopher  wrote:
>
> > Dear IPMC,
> >
> > Please vote for the following release candidate of Apache Fluo
> > 1.0.0-incubating.
> >
> > PPMC vote thread:
> >
> >
> https://lists.apache.org/thread.html/8b6ec5f17e277ed2d01e8df61eb1f1f42266cd30b9e114cb431c1c17@%3Cdev.fluo.apache.org%3E
> >
> > Staged dist artifacts:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/fluo/fluo/1.0.0-incubating-rc2/
> >
> > Staged Maven repository:
> > https://repository.apache.org/content/repositories/orgapachefluo-1013/
> >
> > Signing KEYS:
> > https://www.apache.org/dist/incubator/fluo/KEYS
> > (fingerprint for this release: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Git repo:
> > https://git-wip-us.apache.org/repos/asf/incubator-fluo
> > (branch: 1.0.0-incubating-rc2,
> > commit: e1dbc608c67f31e804b59abd69d0bc530ca00f77)
> >
> > This vote will end on Tue Oct  4 03:00:00 UTC 2016
> > (Mon Oct  3 23:00:00 EDT 2016 / Mon Oct  3 20:00:00 PDT 2016)
> >
> >
>

Re: [VOTE] HTrace 4.2-incubating release

2016-10-02 Thread Drew Farris 
Mike,

If this release can only be built with Maven 3.0.4, would it make sense to
set up the enforcer plugin to fail the build if an attempt is made to build
with something other than that version? It could help others avoid some
gnashing of teeth and document the specific requirement.

Drew

On Sat, Oct 1, 2016, 6:31 PM Mike Drob <md...@apache.org> wrote:

> Justin,
>
> Yes, the compilation issue is MSHADE-148, also captured in HTRACE-236. [1]
>
> Although MSHADE-148 is resolved, you can see discussion towards the end of
> the JIRA that identifies it as still a problem for HTrace and others. For
> now, the workaround is to either build with Maven 3.0.4, which I will agree
> is inconvenient and needs to be better documented.
>
> I will file JIRA issues for your other suggestions shortly.
>
> Mike
>
> [1]: https://issues.apache.org/jira/browse/HTRACE-236
>
> On 2016-09-30 21:40 (-0500), Justin Mclean <jus...@classsoftware.com>
> wrote:
> > Hi,
> >
> > +0 binding as I had issues compiling (see below). Happy to change to +1
> if I can compile everything else is good.
> >
> > I checked:
> > - incubating in name
> > - signature and hashes good
> > - DISCLAIMER exists
> > - LICENSE is missing MIT licensed normalise.css bundled in several
> bootstrap files. e.g. [2]. Please fix for net release.
> > - NOTICE good
> > - All Apache files have ASF header
> > - No unexpended binary files
> > - Can’t compile
> >
> > You may want to remove the copyright line from this ASF header [1]
> >
> > The compile seem to get stuck in an infinite loop at this point:
> > [INFO] Replacing original artifact with shaded artifact.
> > [INFO] Replacing
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating.jar
> with
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating-shaded.jar
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > [INFO] Dependency-reduced POM written at:
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> > …
> >
> > Issue may be related to this bug? [3] However changing the pom to use
> shade 2.4.1 didn’t fix the issue.
> >
> > Thanks,
> > Justin
> >
> > 1. ./bin/gen_thrift.sh
> > 2. ./htrace-htraced/go/web/lib/bootstrap-3.3.1/css/bootstrap.css
> > 3. https://issues.apache.org/jira/browse/MSHADE-148
> >
> >
> > -
> > 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 Pirk into the Apache Incubator

2016-06-14 Thread Drew Farris 
+1 (binding)

On Tue, Jun 14, 2016 at 6:41 PM Josh Elser  wrote:

> +1 (binding)
> On Jun 14, 2016 4:10 PM, "Billie Rinaldi"  wrote:
>
> > Since discussion has died down and we have gotten a couple of additional
> > mentor volunteers, I would like to call a VOTE on accepting Pirk into the
> > Apache Incubator.
> >
> > Proposal: https://wiki.apache.org/incubator/PirkProposal
> >
> > [ ] +1 Accept Pirk into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Pirk into the Apache Incubator because…
> >
> > This vote will be open for at least 72 hours.
> >
> > Here is my +1 (binding).
> >
> > Billie
> > --
> >
> > Pirk Proposal
> >
> > Abstract
> >
> > Pirk is a framework for scalable Private Information Retrieval (PIR).
> >
> > Proposal
> >
> > Pirk is a software framework for scalable Private Information Retrieval
> and
> > is meant to provide a landing place for robust, scalable, and practical
> > implementations of PIR algorithms. The initial scalable PIR algorithms of
> > Pirk were developed at the National Security Agency.
> >
> > Background
> >
> > Private Information Retrieval (PIR) is an area of computer science and
> > mathematics that enables a user/entity to privately and securely obtain
> > information from a dataset, to which they have been granted access,
> without
> > revealing, to the dataset owner or to an observer, any information
> > regarding the questions asked or the results obtained. Employing
> > homomorphic encryption techniques, PIR enables datasets to remain
> resident
> > in their native locations while giving the ability to query the datasets
> > with sensitive terms.
> >
> > Rationale
> >
> > Although PIR has been in existence for over twenty years, it has largely
> > remained an academic discipline with very little robust or scalable
> > implementation. Pirk not only provides implementations of novel scalable
> > PIR algorithms, but it provides a framework into which robust, scalable,
> > and practical PIR may be developed.
> >
> > Pirk fits well within the Apache Software Foundation (ASF) family as it
> > depends on numerous ASF projects and integrates with several others such
> as
> > Hadoop and Spark. We also anticipate developing extensions/adaptors for
> > several other ASF projects such as Kafka, Storm, HBase, and Accumulo in
> the
> > near future.
> >
> > Initial Goals
> >
> > Ensure all dependencies are compliant with Apache License version 2.0
> > and that all code and documentation artifacts have the correct Apache
> > licensing markings and notice.
> > Establish a formal release process and schedule, allowing for
> > dependable release cycles in a manner consistent with the Apache
> > development process.
> > Establish a process which allows different release cycles for the
> core
> > framework, extensions/adaptors, and additional algorithms.
> > Grow the community to establish diversity of background and
> expertise.
> >
> > Current Status
> >
> > Meritocracy
> >
> > We will actively seek help and encourage promotion of influence in the
> > project through meritocracy. We will discuss the requirements in an open
> > forum. We will encourage and monitor community participation so that
> > privileges can be extended to those that contribute.
> >
> > Community
> >
> > Pirk currently has a community of developers within the U.S. government.
> In
> > open sourcing Pirk we plan to grow the community to a broader base of
> > industries and will work to align the interaction of our existing
> > community.
> >
> > Core Developers
> >
> > The initial core developers are employed by the US Government. We will
> work
> > to grow the community among a more diverse set of developers and
> > industries.
> >
> > Alignment
> >
> > Pirk was developed with an open source philosophy in mind and the Apache
> > way is consistent with the approach we have taken to date. Further, Pirk
> > depends on numerous ASF libraries and projects including Hadoop, Spark,
> > Commons, and Maven. We also anticipate extensions and dependencies with
> > several more ASF projects, including Accumulo, Avro, HBase, Storm, Kafka,
> > and others. This existing alignment with Apache and the desired community
> > makes the Apache Incubator a good fit for Pirk.
> >
> > Known Risks
> >
> > Orphaned Products
> >
> > Risk of orphaning is limited though it is important to grow the
> community.
> > The project user and developer base is growing and there is already
> > operational use of Pirk.
> >
> > Inexperience with Open Source
> >
> > The initial committers to Pirk have limited experience with true open
> > source software development. However, despite the project origins being
> > from closed source development we have modeled our behavior and community
> > development on The Apache Way to the greatest extent possible. We are
> > committed to the ideals of open source software and will eagerly seek out
> > mentors and sponsors who can help us

Re: [VOTE] Release Apache Myriad 0.2.0 (incubating)

2016-06-14 Thread Drew Farris 
+1 binding.

I checked the following:

- hashes
- gpg signature
- builds from source
- LICENSE file
- NOTICE file
- Source code headers
- no stray binaries
- release has incubating in version number

- Drew

On Fri, Jun 10, 2016 at 12:03 AM Darin Johnson <dbjohnson1...@gmail.com>
wrote:

> Hi,
>
> The Apache Myriad community has voted on and approved a proposal to release
> Apache Myriad 0.2.0-incubating.
>
> Vote call:
> http://mail-archives.apache.org/mod_mbox/incubator-myriad-dev/201605.mbox/%3CCAN73n9AJeyXgDdfWbURtbn%2BKPFNW9XpLfJHQDDgDFTbz6PjFRQ%40mail.gmail.com%3E
>
> Vote result:
> 3 binding +1 votes
> 3 non-binding +1 votes
> No -1 votes*
> http://mail-archives.apache.org/mod_mbox/incubator-myriad-dev/201606.mbox/%3CCAN73n9Cv%3D760HFAtZWxcMnVfpaPrUvf8%2BVQgAzOh_4LNs7Rbwg%40mail.gmail.com%3E
> <
> http://mail-archives.apache.org/mod_mbox/incubator-myriad-dev/201606.mbox/%3CCAN73n9Cv%3D760HFAtZWxcMnVfpaPrUvf8%2BVQgAzOh_4LNs7Rbwg%40mail.gmail.com%3E
> >*
>
>
> Release Notes:
> https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes
>
> The commit to be voted upon is tagged with "myriad-0.2.0-incubating-rc4"
> and is available
> here:
> https://git1-us-west.apache.org/repos/asf/incubator-myriad/?p=incubator-myriad.git;a=commit;h=63b58698e668729f9f5fb65d5ebc426bf6a8680e
>
> The artifacts to be voted upon are located below. Please note that this is
> a source release:
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.2.0-incubating-rc4/
>
> Release artifacts are signed with the following key:
>
> *https://home.apache.org/~darinj/gpg/2AAE9E3F.asc
> <https://home.apache.org/~darinj/gpg/2AAE9E3F.asc>*
>
>
> We request the permission of IPMC to publish the above release candidate as
> Apache Myriad 0.2.0-incubating. Please try out the package and vote.
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache Myriad 0.1.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Please add (binding) if your vote is binding.
>
> Thanks,
> Darin
> (On behalf of Apache Myriad PPMC)
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

2016-05-24 Thread Drew Farris 
+1 (binding)

On Tue, May 24, 2016, 5:27 PM Andrew Purtell  wrote:

> +1 (binding)
>
>
> On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno 
> wrote:
>
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related to this
> > project.
> >
> > Pony Mail relies on a set of CSS3 templates as well as some very
> stable
> > programming languages. We have no reason to believe these would
> >

Re: [VOTE] Accept PredictionIO into the Apache Incubator

2016-05-23 Thread Drew Farris 
+1 (binding)

On Mon, May 23, 2016, 6:23 PM Andrew Purtell  wrote:

> Since discussion on the matter of PredictionIO has died down, I would like
> to call a VOTE
> on accepting PredictionIO into the Apache Incubator.
>
> Proposal: https://wiki.apache.org/incubator/PredictionIO
>
> ​[ ] +1 Accept PredictionIO into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>
> This vote will be open for at least 72 hours.
>
> My vote is +1 (binding)
>
> --
>
> PredictionIO Proposal
>
> Abstract
>
> PredictionIO is an open source Machine Learning Server built on top of
> state-of-the-art open source stack, that enables developers to manage and
> deploy production-ready predictive services for various kinds of machine
> learning tasks.
>
> Proposal
>
> The PredictionIO platform consists of the following components:
>
>* PredictionIO framework - provides the machine learning stack for
>  building, evaluating and deploying engines with machine learning
>  algorithms. It uses Apache Spark for processing.
>
>* Event Server - the machine learning analytics layer for unifying
> events
>  from multiple platforms. It can use Apache HBase or any JDBC backends
>  as its data store.
>
> The PredictionIO community also maintains a Template Gallery, a place to
> publish and download (free or proprietary) engine templates for different
> types of machine learning applications, and is a complemental part of the
> project. At this point we exclude the Template Gallery from the proposal,
> as it has a separate set of contributors and we’re not familiar with an
> Apache approved mechanism to maintain such a gallery.
>
> Background
>
> PredictionIO was started with a mission to democratize and bring machine
> learning to the masses.
>
> Machine learning has traditionally been a luxury for big companies like
> Google, Facebook, and Netflix. There are ML libraries and tools lying
> around the internet but the effort of putting them all together as a
> production-ready infrastructure is a very resource-intensive task that is
> remotely reachable by individuals or small businesses.
>
> PredictionIO is a production-ready, full stack machine learning system that
> allows organizations of any scale to quickly deploy machine learning
> capabilities. It comes with official and community-contributed machine
> learning engine templates that are easy to customize.
>
> Rationale
>
> As usage and number of contributors to PredictionIO has grown bigger and
> more diverse, we have sought for an independent framework for the project
> to keep thriving. We believe the Apache foundation is a great fit. Joining
> Apache would ensure that tried and true processes and procedures are in
> place for the growing number of organizations interested in contributing
> to PredictionIO. PredictionIO is also a good fit for the Apache foundation.
> PredictionIO was built on top of several Apache projects (HBase, Spark,
> Hadoop). We are familiar with the Apache process and believe that the
> democratic and meritocratic nature of the foundation aligns with the
> project goals.
>
> Initial Goals
>
> The initial milestones will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines, as well as growing our developer and user communities.
>
> Current Status
>
> PredictionIO has undergone nine minor releases and many patches.
> PredictionIO is being used in production by Salesforce.com as well as many
> other organizations and apps. The PredictionIO codebase is currently
> hosted at GitHub, which will form the basis of the Apache git repository.
>
> Meritocracy
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We intend to invite additional developers
> to participate. We will encourage and monitor community participation so
> that privileges can be extended to those that contribute.
>
> Community
>
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around PredictionIO. That community includes
> many contributors from various other companies, and an active mailing list
> composed of hundreds of users.
>
> Core Developers
>
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many are employed at Salesforce.com, there are
> also engineers from ActionML, and independent developers.
>
> Alignment
>
> The ASF is the natural choice to host the PredictionIO project as its goal
> is democratizing Machine Learning by making it more easily accessible to
> every user/developer. PredictionIO is built on top of several top level
> Apache projects as outlined above.
>
> Known Risks
>
> Orphaned Products
>
> PredictionIO has a solid and growing community. It is deployed on
>

Re: [VOTE] Accept Fluo into the Apache Incubator

2016-05-13 Thread Drew Farris 
t; as well as open source projects outside ASF, and understand open source
> development.
>
> Homogeneous Developers
>
> The initial committers work for different employers. We hope add more
> developers from other employers and industries.
>
> Reliance on Salaried Developers
>
> While most of the initial committers are paid to work on Fluo, there have
> been many contributions from developers working independently.
>
> Relationships with Other Apache Products
>
> Fluo uses Accumulo, Hadoop (HDFS & YARN), Twill, ZooKeeper, Curator,
> Thrift, and various Commons libraries. During development, contributions
> have been made to some of these Apache projects to better support Fluo use
> cases.
>
> Apache Brand
>
> While we recognize the impact of the Apache brand, we feel that Fluo would
> fit well in Apache because of its relationship to other Apache projects and
> because we share the ASF values of meritocracy and community over code.
>
> Documentation
>
> Information about Fluo can be found on the project website at
> http://fluo.io/. This includes:
>
> General documentation - http://fluo.io/docs/
>
> API documentation - http://fluo.io/apidocs/
>
> Release notes - http://fluo.io/release-notes/
>
> Blog posts - http://fluo.io/blog/
>
> Initial Source
>
> The initial source code is publicly available as an open source project on
> GitHub at https://github.com/fluo-io/fluo
>
> Supplemental repositories also exist on GitHub at
> https://github.com/fluo-io
> and some of those will become part of the initial code base (perhaps in
> separate repositories).
>
> Source and Intellectual Property Submission Plan
>
> All of the Fluo’s source code is available under the Apache License,
> Version 2.
>
> The Fluo logo was designed and contributed to the Fluo project, for use by
> the project, and the contributors would like it to remain the logo of the
> project within the ASF, granting any necessary rights to the ASF, while
> continuing to use the logo on Fluo-related historical sites and project
> pages (such as Fluo’s current GitHub site).
>
> External Dependencies
>
> Fluo has made it a point from its beginning to use dependencies which are
> compatible with the expectations of an ASF project. The following are its
> current dependencies, grouped by license.
>
> Apache License, Version 2.0
>
> accumulo
> commons-{collections,configuration,io}
> curator
> dropwizard metrics
> easymock
> guava
> hadoop
> jcommander
> maven
> thrift
> twill
> zookeeper
>
> BSD License (2-Clause)
>
> HdrHistogram
>
> Eclipse Public License - v 1.0
>
> junit (not bundled)
> logback (binary bundling only)
>
> MIT License (Expat)
>
> slf4j
>
> Cryptography
>
> none
>
> Required Resources
>
> Mailing Lists
>
> private at fluo.incubator.apache.org
> dev at fluo.incubator.apache.org
> notifications at fluo.incubator.apache.org
>
> Git Repository
>
> https://git-wip-us.apache.org/repos/asf/incubator-fluo.git
>
> (The developers will use a git-based site for project documentation
> in the asf-site branch of the repo.)
>
> https://git-wip-us.apache.org/repos/asf/incubator-fluo-recipes.git
>
> Issue Tracking
>
> https://issues.apache.org/jira/browse/FLUO
>
> (Currently, the developers rely on GitHub issues. If possible,
> GitHub integration for issue tracking would be preferred. If this is
> possible, the Fluo developers could work with INFRA to transfer the
> existing GitHub repositories to the Apache GitHub organization to bring the
> existing GitHub issues.)
>
> Continuous Integration
>
> Travis CI on the GitHub mirror is fine (flag set to build only if
> .travis.yml file is present)
>
> Initial Committers
>
> Keith Turner (kturner at apache dot org)
> Mike Walch (mike.walch at ptech-llc dot com)
> Corey Nolet (cjnolet at apache dot org)
> Christopher Tubbs (ctubbsii at apache dot org)
> Josh Elser (elserj at apache dot org)
>
> Affiliations
>
> Keith Turner (Peterson Technologies, ASF Member, Accumulo PMC, Gora
> PMC)
> Mike Walch (Peterson Technologies)
> Corey Nolet (Tetra Concepts LLC, Accumulo PMC)
> Christopher Tubbs (U.S. Government, ASF Member, Accumulo PMC)
> Josh Elser (Hortonworks, ASF Member, Accumulo PMC, Calcite PMC, IPMC)
>
> Sponsors
>
> Champion
>
> Billie Rinaldi (billie at apache dot org) has volunteered to be our
> Champion
>
> Nominated Mentors
>
> Drew Farris (drew at apache dot org)
> Josh Elser (elserj at apache dot org)
> Billie Rinaldi (billie at apache dot org)
>
> Sponsoring Entity
>
> The Fluo team requests sponsorship from the Incubator PMC
>
> USENIX (2010), http://research.google.com/pubs/pub36726.html (1)
>

Re: Website for Tamaya - need help

2014-11-29 Thread Drew Farris 
John,

I just took a quick look at this. It appears the options are svnpubsub
or Apache CMS. For CMS, you have a choice of 'cms build type':
default-perl, maven, ant, or shell.

It sounds like you want Apache CMS, do you have any thoughts about the
'cms build type' option?

Drew

--
Drew Farris
drew.far...@gmail.com
d...@apache.org


On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament john.d.am...@gmail.com wrote:
 Benson,

 Thanks.  So I don't know what that page is expecting since I can't actually
 see it.

 If you require a temporary index.html, I can upload one.  In which case,
 the full URL would be
 https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html for
 the staging site to read from.

 I think we're expecting staging/production via Apache CMS (cms.apache.org).

 John

 On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies bimargul...@gmail.com
 wrote:

 On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament johndam...@apache.org
 wrote:
  https://infra.apache.org/officers/webreq

 I tried:

 Missing https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html

 -
 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: Website for Tamaya - need help

2014-11-29 Thread Drew Farris 
John,

Ok, request successfully submitted, from the output: Next steps: We
will create the web site and email private@tamaya once we have done
that. There is no need to file a JIRA.

It is not entirely clear to me how to publish a podling via CMS. I
wasn't able to find docs and permutations of cms.apache.org weren't
useful. It doesn't appear that there is
(podling).staging.incubator.apache.org, where the staging version of
the site can be viewed. This leads me to believe that publishing the
podling site is managed independently from the incubator site proper.

Drew
--
drew.far...@gmail.com
d...@apache.org

On Sat, Nov 29, 2014 at 9:58 AM, John D. Ament johndam...@apache.org wrote:
 One other thing (sorry!)

 I notice on the cms.apache.org landing page, none of the podlings are
 listed.  How do podlings publish?

 On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament johndam...@apache.org
 wrote:

 Drew,

 default-perl would make the most sense.  They're going to manage the
 asciidoc files within standard source, use a site plugin to publish the
 html to the SVN directory.  This should end up being very similar to
 batchee's [setup].

 Thanks!

 John

 [setup]:
 https://git-wip-us.apache.org/repos/asf/infrastructure-puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427

 On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris d...@apache.org wrote:

 John,

 I just took a quick look at this. It appears the options are svnpubsub
 or Apache CMS. For CMS, you have a choice of 'cms build type':
 default-perl, maven, ant, or shell.

 It sounds like you want Apache CMS, do you have any thoughts about the
 'cms build type' option?

 Drew

 --
 Drew Farris
 drew.far...@gmail.com
 d...@apache.org


 On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament john.d.am...@gmail.com
 wrote:
  Benson,
 
  Thanks.  So I don't know what that page is expecting since I can't
 actually
  see it.
 
  If you require a temporary index.html, I can upload one.  In which case,
  the full URL would be
  https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html
 for
  the staging site to read from.
 
  I think we're expecting staging/production via Apache CMS (
 cms.apache.org).
 
  John
 
  On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies 
 bimargul...@gmail.com
  wrote:
 
  On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament johndam...@apache.org
  wrote:
   https://infra.apache.org/officers/webreq
 
  I tried:
 
  Missing
 https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
 
  -
  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: Website for Tamaya - need help

2014-11-29 Thread Drew Farris 
On Sat, Nov 29, 2014 at 9:58 AM, John D. Ament johndam...@apache.org wrote:
 One other thing (sorry!)

 I notice on the cms.apache.org landing page, none of the podlings are
 listed.  How do podlings publish?

Actually, it looks like there are podlings listed in [export], and on
cms.apache.org proper (e.g: devicemap). I'm going to assume that will
be or can be modified once the site is set up properly.

[export] 
https://svn.apache.org/repos/infra/websites/cms/webgui/content/export.json

 On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament johndam...@apache.org
 wrote:

 Drew,

 default-perl would make the most sense.  They're going to manage the
 asciidoc files within standard source, use a site plugin to publish the
 html to the SVN directory.  This should end up being very similar to
 batchee's [setup].

 Thanks!

 John

 [setup]:
 https://git-wip-us.apache.org/repos/asf/infrastructure-puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427

 On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris d...@apache.org wrote:

 John,

 I just took a quick look at this. It appears the options are svnpubsub
 or Apache CMS. For CMS, you have a choice of 'cms build type':
 default-perl, maven, ant, or shell.

 It sounds like you want Apache CMS, do you have any thoughts about the
 'cms build type' option?

 Drew

 --
 Drew Farris
 drew.far...@gmail.com
 d...@apache.org


 On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament john.d.am...@gmail.com
 wrote:
  Benson,
 
  Thanks.  So I don't know what that page is expecting since I can't
 actually
  see it.
 
  If you require a temporary index.html, I can upload one.  In which case,
  the full URL would be
  https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html
 for
  the staging site to read from.
 
  I think we're expecting staging/production via Apache CMS (
 cms.apache.org).
 
  John
 
  On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies 
 bimargul...@gmail.com
  wrote:
 
  On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament johndam...@apache.org
  wrote:
   https://infra.apache.org/officers/webreq
 
  I tried:
 
  Missing
 https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
 
  -
  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

Incubator Shepherd

2014-11-25 Thread Drew Farris 
Hi All,

I'm interested in helping out as an incubator shepherd, is it just a matter
of adding myself to shepherds.json?

Drew

--
Drew Farris
drew.far...@gmail.com
d...@apache.org

Re: Incubator Shepherd

2014-11-25 Thread Drew Farris 
On Tue, Nov 25, 2014 at 8:49 PM, John D. Ament john.d.am...@gmail.com wrote:

 Yes, as long as you have write access to it.  If you don't, please let
 us know what your info is and someone will add you.


Looks like I had write access, so I added myself.

 If you're interested in getting started this month, feel free to take
 a podling from this [list] and change the name to yours.
 [list]: https://wiki.apache.org/incubator/December2014

It looks like the user DrewFarris needs some sort of karma to change
that page. I'm happy to wait until January, but equally happy to take
one of the assignments for folks that have two.

Drew

-- 
Drew Farris
drew.far...@gmail.com
d...@apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-25 Thread drew 
On Sat, 2012-08-25 at 06:45 -0700, Benson Margulies wrote:
 I submit that this sub-thread has reached the end of its useful lifetime.

Howdy,

After a re-read of this thread, along with similar on the AOO dev/priv
list and referenced ASF policy, or best practices, docs., I fully agree.

Honestly, after this review my thinking has changed somewhat and there
seems value still to be had in assuring that everyone is chasing the
same ends.   I'd like to address this in a context of project goals and
best way to attain them, as an ASF project, so will move the general
discussion back to AOO dev.

I think the group can come to a reasonable consensus from that approach
quickly. Then, _if_ (or which) specific changes to current ASF norms
truly are needed, to best attain those goals, can go through the proper
steps - which isn't this thread ;) 

Also - It may very well be that what needs addressing is already in the
pipeline, IMO.

Thanks,

//drew



 
 The IPMC's view of binaries is clear, and the IPMC believes that its
 views reflect the will of the board. 'Official' binaries, like
 binaries signed with a certificate with the Foundation's name on it,
 are not currently permissible. Roughly, the same questions of how the
 voting members of a PMC could meaningfully check a release before
 voting apply to both questions.
 
 If you want to engage with the board on this, by all means, there is
 board@. It's a complete waste of time to argue on this list and this
 thread about the Foundation's governance.
 
 In the mean time, AOO releases can continue to have 'convenience
 binaries', sans signatures.



 
 Since this is a community vote thread (!) and not an IPMC vote thread,
 I further submit that all of us IPMC members should get out of the way
 and leave it to the mentors to sort out the disconnect between
 Foundation policy and AOO needs/wants. To quote the mentors from a
 previous conversation, if people want to join in the process, they
 should become mentors and fully engage.
 
 Of course, a discussion thread started here to solicit the IPMC's
 opinion on graduation would be another matter entirely.
 
 -
 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 OpenOffice Community Graduation Vote

2012-08-20 Thread drew 
On Mon, 2012-08-20 at 13:32 -0700, Marvin Humphrey wrote:
 On Sun, Aug 19, 2012 at 8:53 AM, Rob Weir robw...@apache.org wrote:
  Per the IPMC's Guide to Successful Graduation [1] this is the
  optional, but recommended, community vote for us to express our
  willingness/readiness to govern ourselves.  If this vote passes then
  we continue by drafting a charter, submitting it for IPMC endorsement,
  and then to the ASF Board for final approval.   Details can be found
  in the Guide to Successful Graduation.
 
  Everyone in the community is encouraged to vote.  Votes from PPMC
  members and Mentors are binding.  This vote will run 72-hours.
 
 
  [ ] +1  Apache OpenOffice community is ready to graduate from the
  Apache Incubator.
  [ ] +0 Don't care.
  [ ] -1  Apache OpenOffice community is not ready to graduate from the
  Apache Incubator because...
 
 In my opinion, the issue of binary releases ought to be resolved before
 graduation.
 
 If the podling believes that ASF-endorsed binaries are a hard requirement,
 then it seems to me that the ASF is not yet ready for AOO and will not be
 until suitable infrastructure and legal institutions to support binary
 releases (sterile build machines, artifact signing, etc) have been created
 and a policy has been endorsed by the Board.
 
 One possibility discussed in the past was to have downstream commercial
 vendors release binaries a la Subversion's example, which would
 obviate the need for all the effort and risk associated with providing support
 for ASF-endorsed binaries.  For whatever reason, the AOO podling seems not to
 have gone this direction, though.
 
 Marvin Humphrey

Hi Marvin,

Well, for myself, I don't have a problem with the AOO project not having
official binary releases - in such a circumstance I would strongly
prefer no binary release at all. 

On the other hand if there is a binary release from the AOO project then
I believe it should be treated as a fully endorsed action.

One guys opinion.

Thanks

Drew Jensen
AOO PPMC member


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-20 Thread drew 
On Mon, 2012-08-20 at 17:01 -0700, Marvin Humphrey wrote:
 On Mon, Aug 20, 2012 at 3:03 PM, drew d...@baseanswers.com wrote:
  Well, for myself, I don't have a problem with the AOO project not having
  official binary releases - in such a circumstance I would strongly
  prefer no binary release at all.
 
 I wonder who might step into the breach to provide binaries for such a
 package...

Hi,

Well, for a start:

IBM stated it will release a free binary version at some point, after
shutting down the Symphony product.

CS2C, a Chinese firm working in cooperation with Ernest and Young IIRC,
releases a binary based on the source code - in fact I'm not even sure
AOO supplied binaries are available to most folks in China.

Multiracio releases a closed source version of the application for sale
in Europe and the US.

In the past quite a few Linux distributors included binary releases in
their offerings, they consume source not binaries.

The current BSD, OS/2 and Solaris ports will go out as source only from
AOO, but come to end users from a third party repository, unless I
totally missed what was happening there (and I might off ;)

There are currently two groups which offer binary versions packaged to
run off USB drives, as far as I understand it, they work from source and
don't require binaries.

Finally this is a well known brand now, it would be hard to believe that
if AOO did not release binaries the void would not be filled by others.

//drew

ps - sorry if this double posts... 

 
  On the other hand if there is a binary release from the AOO project then
  I believe it should be treated as a fully endorsed action.
 
 At the ASF, the source release is canonical.  I have never seen anyone assert
 that the source release is not offical and endorsed by the ASF.
 
 There has been disagreement about whether binaries should be official or not.
 To the best of my knowledge, every time the matter has come up, the debate has
 been resolved with a compromise: that while binary releases are not endorsed
 by the ASF, they may be provided in addition to the source release for the
 convenience of users.
 
 What is different with AOO is that the compromise does not seem to satisfy
 an element within the PPMC and thus the matter is being forced.
 
 It would be a lot of hard, time-consuming work for the ASF to build the
 institutions necessary to provide binary releases that approach the standards
 our source releases set.  (As illustrated by e.g. the challenges of setting up
 the code signing service.)  Not all of us are convinced that it is for the
 best, either.
 
 Marvin Humphrey
 
 -
 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 OpenOffice Community Graduation Vote

2012-08-20 Thread drew jensen 
On Mon, 2012-08-20 at 17:01 -0700, Marvin Humphrey wrote:
 On Mon, Aug 20, 2012 at 3:03 PM, drew d...@baseanswers.com wrote:
  Well, for myself, I don't have a problem with the AOO project not having
  official binary releases - in such a circumstance I would strongly
  prefer no binary release at all.
 
 I wonder who might step into the breach to provide binaries for such a
 package...

Hi,

Well, for a start:

IBM stated it will release a free binary version at some point, after
shutting down the Symphony product.

CS2C, a Chinese firm working in cooperation with Ernest and Young IIRC,
releases a binary based on the source code - in fact I'm not even sure
AOO supplied binaries are available to most folks in China.

Multiracio releases a closed source version of the application for sale
in Europe and the US.

In the past quite a few Linux distributors included binary releases in
their offerings, they consume source not binaries.

The current BSD, OS/2 and Solaris ports will go out as source only from
AOO, but come to end users from a third party repository, unless I
totally missed what was happening there (and I might off ;)

There are currently two groups which offer binary versions packaged to
run off USB drives, as far as I understand it, they work from source and
don't require binaries.

Finally this is a well known brand now, it would be hard to believe that
if AOO did not release binaries the void would not be filled by others.

//drew


 
  On the other hand if there is a binary release from the AOO project then
  I believe it should be treated as a fully endorsed action.
 
 At the ASF, the source release is canonical.  I have never seen anyone assert
 that the source release is not offical and endorsed by the ASF.
 
 There has been disagreement about whether binaries should be official or not.
 To the best of my knowledge, every time the matter has come up, the debate has
 been resolved with a compromise: that while binary releases are not endorsed
 by the ASF, they may be provided in addition to the source release for the
 convenience of users.
 
 What is different with AOO is that the compromise does not seem to satisfy
 an element within the PPMC and thus the matter is being forced.
 
 It would be a lot of hard, time-consuming work for the ASF to build the
 institutions necessary to provide binary releases that approach the standards
 our source releases set.  (As illustrated by e.g. the challenges of setting up
 the code signing service.)  Not all of us are convinced that it is for the
 best, either.
 
 Marvin Humphrey
 
 -
 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: References to Apache OpenOffice

2012-06-23 Thread drew 
On Sat, 2012-06-23 at 19:43 +0100, Nick Kew wrote:
 On 23 Jun 2012, at 19:37, Nick Kew wrote:
 
  Nor what appears on planet.apache.org, featuring the article that first 
  struck me
  as using the name in a way I wouldn't expect when I read it in my feed 
  reader:
  http://www.robweir.com/blog/2012/06/pache-openoffice-34-downloads.html
 
 Following that link in a browser I see there's also a nice but questionable 
 logo:
 http://www.robweir.com/blog/images/get-aoo-300x100-cf.png
 If PR are OK with that then fine, but I find it surprising.
 

hmm - I suppose you are correct, it shouldn't have the feather and
should have the incubator tab - right?

//drew



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: References to Apache OpenOffice

2012-06-23 Thread drew 
On Sat, 2012-06-23 at 15:42 -0400, Rob Weir wrote:
 On Sat, Jun 23, 2012 at 2:59 PM, drew d...@baseanswers.com wrote:
  On Sat, 2012-06-23 at 19:43 +0100, Nick Kew wrote:
  On 23 Jun 2012, at 19:37, Nick Kew wrote:
 
   Nor what appears on planet.apache.org, featuring the article that first 
   struck me
   as using the name in a way I wouldn't expect when I read it in my feed 
   reader:
   http://www.robweir.com/blog/2012/06/pache-openoffice-34-downloads.html
 
  Following that link in a browser I see there's also a nice but 
  questionable logo:
  http://www.robweir.com/blog/images/get-aoo-300x100-cf.png
  If PR are OK with that then fine, but I find it surprising.
 
 
 
 With reference to the Podling Branding Guide [1] , the requirement is
 that the product be called Apache OpenOffice.  That is the name.
 Nothing else.  But we're also required to mention that the project is
 under Incubation.  There is more than one way of doing that.  Also,
 These statements only need to be disclosed upon the first reference
 in a document.  IMHO, we've done that for the blog posts as hosted on
 ASF servers.  But it is not clear if or how we control other parties
 tweeting links.  But I assume if someone feels strongly about
 controlling things at that level they will propose a way.
 
 [1] http://incubator.apache.org/guides/branding.html
 
 
  hmm - I suppose you are correct, it shouldn't have the feather and
  should have the incubator tab - right?
 
 
 Actually, we did approve that logo as a PPMC as part of a download
 promotion program:
 
 http://incubator.apache.org/openofficeorg/get-it-here.html
 
 We ran that by VP Branding as well.  I could be wrong, but my
 impression was he approved as well.

So what, it is still wrong and I can fix it easy enough.


 
 The PPMC does not control the Apache.org home page.  If the ASF
 decides to aggregate posts from the committers planet, then maybe that
 should come with a disclaimer?  Or bring in just the project blogs,
 not the committer blogs?  I could be talking about anything on my
 blog: OpenOffice, beer. satantic rituals, bagpipes, perhaps all at
 once.   It probably should not automatically all be promoted to the
 ASF home page.
 
 As for the project blogs, maybe we should just enhance the aggregator
 logic on the ASF home page?  For example, Google+ gets does it well,
 pulling in the blog title along with the post title.  Se here:
 https://plus.google.com/u/0/114598373874764163668/posts/ZiRcwog5cDJ  .
 
 If you try to fix it in the content itself, then you end up with
 suboptimal results for Google+ and other places that do bring the blog
 title along, ending up with something like 5 Million Downloads of
 Apache OpenOffice (incubating) : Apache OpenOffice (incubating) which
 looks sloppy.
 
 -Rob
 
  //drew
 
 
 
  -
  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: References to Apache OpenOffice

2012-06-23 Thread drew 
On Sat, 2012-06-23 at 16:01 -0400, Rob Weir wrote:
 On Sat, Jun 23, 2012 at 3:55 PM, drew d...@baseanswers.com wrote:
  On Sat, 2012-06-23 at 15:42 -0400, Rob Weir wrote:
  On Sat, Jun 23, 2012 at 2:59 PM, drew d...@baseanswers.com wrote:
   On Sat, 2012-06-23 at 19:43 +0100, Nick Kew wrote:
   On 23 Jun 2012, at 19:37, Nick Kew wrote:
  
Nor what appears on planet.apache.org, featuring the article that 
first struck me
as using the name in a way I wouldn't expect when I read it in my 
feed reader:
http://www.robweir.com/blog/2012/06/pache-openoffice-34-downloads.html
  
   Following that link in a browser I see there's also a nice but 
   questionable logo:
   http://www.robweir.com/blog/images/get-aoo-300x100-cf.png
   If PR are OK with that then fine, but I find it surprising.
  
  
 
  With reference to the Podling Branding Guide [1] , the requirement is
  that the product be called Apache OpenOffice.  That is the name.
  Nothing else.  But we're also required to mention that the project is
  under Incubation.  There is more than one way of doing that.  Also,
  These statements only need to be disclosed upon the first reference
  in a document.  IMHO, we've done that for the blog posts as hosted on
  ASF servers.  But it is not clear if or how we control other parties
  tweeting links.  But I assume if someone feels strongly about
  controlling things at that level they will propose a way.
 
  [1] http://incubator.apache.org/guides/branding.html
 
 
   hmm - I suppose you are correct, it shouldn't have the feather and
   should have the incubator tab - right?
  
 
  Actually, we did approve that logo as a PPMC as part of a download
  promotion program:
 
  http://incubator.apache.org/openofficeorg/get-it-here.html
 
  We ran that by VP Branding as well.  I could be wrong, but my
  impression was he approved as well.
 
  So what, it is still wrong and I can fix it easy enough.
 
 
 There is more than one way to make it right, so it might be worth a
 quick discuss on ooo-dev.
 
 Or if you are in a JFDI mood, the live copy is here:
 
 https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/images/get-it-here/en.png


Ok - well, I still have the original SVG file on disk, so I'll work with
that - I'll put, as always, a link to the oo-dev ML with the draft
change. 

Off to fire up the editor, see you back at oo-dev.

TTFN,

//drew

 
 Regards,
 
 -Rob
 
 
 
  The PPMC does not control the Apache.org home page.  If the ASF
  decides to aggregate posts from the committers planet, then maybe that
  should come with a disclaimer?  Or bring in just the project blogs,
  not the committer blogs?  I could be talking about anything on my
  blog: OpenOffice, beer. satantic rituals, bagpipes, perhaps all at
  once.   It probably should not automatically all be promoted to the
  ASF home page.
 
  As for the project blogs, maybe we should just enhance the aggregator
  logic on the ASF home page?  For example, Google+ gets does it well,
  pulling in the blog title along with the post title.  Se here:
  https://plus.google.com/u/0/114598373874764163668/posts/ZiRcwog5cDJ  .
 
  If you try to fix it in the content itself, then you end up with
  suboptimal results for Google+ and other places that do bring the blog
  title along, ending up with something like 5 Million Downloads of
  Apache OpenOffice (incubating) : Apache OpenOffice (incubating) which
  looks sloppy.
 
  -Rob
 
   //drew
  
  
  
   -
   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
 
 



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE][RESULT] Accept ODF Toolkit for Incubation

2011-08-01 Thread drew 
On Mon, 2011-08-01 at 12:05 +0100, Nick Burch wrote:
 On Sun, 31 Jul 2011, Sam Ruby wrote:
  On Thu, Jul 28, 2011 at 3:53 PM, Sam Ruby ru...@intertwingly.net wrote:
  As the discussions on the ODF Toolkit threads seem to be winding down,
  I would like to initiate the vote to accept the ODF Toolkit as an
  Apache Incubator project.
 
  This vote will close 72 hours from now.
 
  Voting is now closed.  Quorum was achieved, and the vote passes.
 
 Great. I've gone ahead and added the podling status page:
  http://incubator.apache.org/projects/odftoolkit.html
 (may take an hour or two for the site publish to go live though)
 

Hi Nick,

 
 Next step is probably to get the lists setup, so we can use them to 
 discuss importing the code, website etc.
 
 Can I have a couple of volunteers to be moderators for the lists? 

Raising hand.

I'd be happy to help on that.

Best wishes,

//drew

snip


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

ODF Toolkit

2011-08-01 Thread drew 
Hi,

Wondering if it is still appropriate, acceptable, to add myself to the
list of initial Committers at:

http://wiki.apache.org/incubator/ODFToolkitProposal

Thanks much,

Drew Jensen


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: ODF Toolkit

2011-08-01 Thread drew 
On Mon, 2011-08-01 at 15:16 +0100, Nick Burch wrote:
 On Mon, 1 Aug 2011, drew wrote:
  Wondering if it is still appropriate, acceptable, to add myself to the
  list of initial Committers
 
 Alas not, 

Not a problem.

 now the proposal has been accepted, that initial list is final
 
 The good news is that as soon as the lists are set up, the podling would 
 be able to vote you in. If you've been involved in the project before, 
 that should be very quick, though for future new contributors it would 
 normally wait until after they've submitted patches that everyone is happy 
 with.
 
 If you were involved in the project before, I'd suggest you join the dev 
 list once it's created, and remind people that you're interested in 
 joining.

OK - thanks,

Drew


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept ODF Toolkit for Incubation

2011-07-30 Thread Drew Jensen 
On Thu, 2011-07-28 at 15:53 -0400, Sam Ruby wrote:
 *** Please change your Subject: line for any [DISCUSSION] of this [VOTE]
 
 As the discussions on the ODF Toolkit threads seem to be winding down,
 I would like to initiate the vote to accept the ODF Toolkit as an
 Apache Incubator project.
 
 At the end of this mail, I've put a copy of the current proposal.
 Here is a link to the document in the wiki:
 
 http://wiki.apache.org/incubator/ODFToolkitProposal?action=recallrev=7
 
 I encourage everybody to read the proposal thread before voting:
 
 http://old.nabble.com/-PROPOSAL--ODF-Toolkit-for-Incubation-td32102643.html
 
 Please cast your votes:
 
 [  ] +1 Accept ODF Toolkit for incubation
 [  ] +0 Indifferent to ODF Toolkit incubation
 [  ] -1 Reject ODF Toolkit for incubation
 
snip

+1

Thanks,

Drew Jensen


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: OpenOffice: were are we now?

2011-06-06 Thread drew 
On Mon, 2011-06-06 at 12:08 -0400, Greg Stein wrote:
 On Mon, Jun 6, 2011 at 11:46, Ian Lynch ianrly...@gmail.com wrote:
 ...
  And the natural extension is that if there is no home for the OOo code with
  Apache where will it end up? That scenario is not without risk either.
 
 As I've said elsewhere, I would lobby our Board for an unsupported
 tarball of the granted code, under the ALv2. Let others pick it up and
 do whatever they'd like with it.

Well, for whatever it is worth - +1

Thanks,

Drew Jensen


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: OpenOffice.org Summit Proposal - Budget Concerns

2011-06-06 Thread drew 
On Mon, 2011-06-06 at 21:35 +0100, Simon Phipps wrote:
 On Mon, Jun 6, 2011 at 9:25 PM, Alexandro Colorado j...@openoffice.orgwrote:
 
  On Mon, Jun 6, 2011 at 3:18 PM, Nóirín Plunkett noi...@apache.org wrote:
 
   Note that an expo-hall pass is free until (and including) today; it's
   $25 thereafter.
  
   This also opens up the evening events Mon-Fri, which, if you're going
   to find yourself in Portland that week, might be fun to attend :-)
  
   Noirin
  
 
  Drew Jensen probably have better knowlledge of the more community focus
  events across the US.
 
  Specially the Linuxfests. They usually have a more open source crowd (with
  open source budgets).
 
  I heard the Ohio Linuxfest is one of the most recognized ones.
 
 
 Do please add ebents (and yourselves) to:
 http://wiki.documentfoundation.org/OOoCommunitySummit

Hi Simon,

Thanks for starting that page - and to the others for starting this line
of discussion.

Quick note: I'll be staffing the TDF/LibreOffice table at SELF
(Southeast Linux Fest) in Spartanburg, South Carolina this coming
weekend. I expect that some of the Ohio Linux-fest (Sept. 9-11)
organizers will be in attendance, so i could touch base with them
directly.

As for Ohio, I am already planning on attending, Andrew Pitonyak (most
of the OO.o should recognize his name) has even offered to put myself
and Joyce up in his guest room. There are a few other OO.o folks in the
immediate area there, so I would guess if it as a case of coordinating a
hosting staff the bodies could be assembled.

otherwise, will update the wiki page.

Thanks

Drew Jensen





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: OpenOffice.org Summit Proposal - Budget Concerns

2011-06-06 Thread drew 
On Mon, 2011-06-06 at 16:59 -0400, Noel J. Bergman wrote:
 Drew,
 
  Quick note: I'll be staffing the TDF/LibreOffice table at SELF
  (Southeast Linux Fest) in Spartanburg, South Carolina this coming
  weekend.
 
 I can't make it for this weekend, but keep me in mind for future, local, 
 activities.

:-) Consider yourself drafted - details to be worked out later..

//drew


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: OpenOffice: were are we now?

2011-06-05 Thread drew 
On Sun, 2011-06-05 at 10:01 -0700, Joe Schaefer wrote:
 - Original Message 
 
snip

 
 Personally I have no idea how my daily workload will be affected by dealing
 with OOo's infra requirements.  If it just means dishing out dedicated 
 resources
 and setting up end-user services, that shouldn't present any issues.  OTOH
 staffing a forum with support service isn't something I'm equipped to deal 
 with.
 Either way, I don't intend to block incubation over it- collectively infra
 will learn to cope with the change.

Hello Joe,

Since this is my (almost) first email to this list:

Drew Jensen
- Started involvement with OO.o back around 2005. 
- Primary focus was end user support/QA on the Base module.
- I am a member of the Document Foundation, primarily focused on
marketing efforts in North America there, for the moment.

Alright - OO.o end user forum.

Currently the forum is hosted on a single blade in the Oracle offices,
Hamburg DE. It runs on VM on that machine (I can get details but it is
not particularly taxing from a systems resources POV). It's a pretty
straight forward phpBB set of sites w/some light custom mod work.

The daily functioning/management of the forums is handled by an
autonomous group, The Volunteers, at the forums. This goes all the way
from site admin (I was one of the initial group, currently that is Terry
Ellison [Individual] and Clayton Cornell [Oracle]) with root access (to
the VPS), right down to the individual board moderators. All decisions
are made by this group either via lazy consensus or when needed, a vote.

The Volunteer group is also represented I see on the wiki page by Dave
McKay, one of the global moderators. Terry will be the right POC for any
move but at the moment he is on an extended vacation with  his wife on
some Greek Island, the nerve. *smile* 

Different subjects 

- the wiki. MediaWiki, lots of work invested in that beast and this is a
larger resource hog. Clayton Cornell at Oracle is the POC here, if I can
help with this work also I certainly will and I'll touch base directly
with Clayton on that.

- Extension/template repository - Currently hosted at Oregon State Open
Source Labs. Drupal based, and it is having some real problems right
now. IMO, this needs some direct and _immediate_ love. I can't pull the
contact name for the Oracle admin on that site from my noggin at the
moment. (Matt ?) BTW, TDF is nearing roll out of it's extension site, so
this may ease some of the problems users are having with getting
dictionaries and such at the moment.

Anyway - more detail then is needed for this list I suppose. 

@Joe feel free to ping me direct if I can help with running down
details/information on anything.

Thanks much,

Drew Jensen




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: confirm subscribe to general@incubator.apache.org

2011-06-03 Thread drew 
On Wed, 2011-06-01 at 20:14 +, general-h...@incubator.apache.org
wrote:
 Hi! This is the ezmlm program. I'm managing the
 general@incubator.apache.org mailing list.
 
 I'm working for my owner, who can be reached
 at general-ow...@incubator.apache.org.
 
 To confirm that you would like
 
d...@baseanswers.com
 
 added to the general mailing list, please send
 a short reply to this address:
 

 general-sc.1306959277.cflfnlgkmpmiejlhlofb-drew=baseanswers@incubator.apache.org
 
 Usually, this happens when you just hit the reply button.
 If this does not work, simply copy the address and paste it into
 the To: field of a new message.
 
 or click here:
   
 mailto:general-sc.1306959277.cflfnlgkmpmiejlhlofb-drew=baseanswers@incubator.apache.org
 
 This confirmation serves two purposes. First, it verifies that I am able
 to get mail through to you. Second, it protects you in case someone
 forges a subscription request in your name.
 
 Some mail programs are broken and cannot handle long addresses. If you
 cannot reply to this request, instead send a message to
 general-requ...@incubator.apache.org and put the
 entire address listed above into the Subject: line.
 
 
 --- Administrative commands for the general list ---
 
 I can handle administrative requests automatically. Please
 do not send them to the list address! Instead, send
 your message to the correct command address:
 
 For help and a description of available commands, send a message to:
general-h...@incubator.apache.org
 
 To subscribe to the list, send a message to:
general-subscr...@incubator.apache.org
 
 To remove your address from the list, just send a message to
 the address in the ``List-Unsubscribe'' header of any list
 message. If you haven't changed addresses since subscribing,
 you can also send a message to:
general-unsubscr...@incubator.apache.org
 
 or for the digest to:
general-digest-unsubscr...@incubator.apache.org
 
 For addition or removal of addresses, I'll send a confirmation
 message to that address. When you receive it, simply reply to it
 to complete the transaction.
 
 If you need to get in touch with the human owner of this list,
 please send a message to:
 
 general-ow...@incubator.apache.org
 
 Please include a FORWARDED list message with ALL HEADERS intact
 to make it easier to help you.
 
 --- Enclosed is a copy of the request I received.
 
 Return-Path: d...@baseanswers.com
 Received: (qmail 76525 invoked by uid 99); 1 Jun 2011 20:14:37 -
 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
 by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2011 20:14:37 +
 X-ASF-Spam-Status: No, hits=-1.3 required=10.0
   tests=ASF_LIST_OPS,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL
 X-Spam-Check-By: apache.org
 Received-SPF: neutral (athena.apache.org: local policy)
 Received: from [205.178.146.51] (HELO omr1.networksolutionsemail.com) 
 (205.178.146.51)
 by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2011 20:14:28 +
 Received: from cm-omr5 (mail.networksolutionsemail.com [205.178.146.50])
   by omr1.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id 
 p51KE5kg004437
   for general-subscr...@incubator.apache.org; Wed, 1 Jun 2011 16:14:06 
 -0400
 Authentication-Results:  cm-omr5 smtp.user=d...@baseanswers.com; auth=pass 
 (LOGIN)
 X-Authenticated-UID: d...@baseanswers.com
 Received: from [174.140.78.93] ([174.140.78.93:59871] helo=[192.168.1.2])
   by cm-omr5 (envelope-from d...@baseanswers.com)
   (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA
   id 57/5A-04865-D8D96ED4; Wed, 01 Jun 2011 16:14:05 -0400
 Subject: subscribe
 From: drew d...@baseanswers.com
 To: general-subscr...@incubator.apache.org
 Content-Type: text/plain
 Date: Wed, 01 Jun 2011 16:14:06 -0400
 Message-ID: 1306959246.21630.0.camel@sybil-gnome
 Mime-Version: 1.0
 X-Mailer: Evolution 2.32.2 
 Content-Transfer-Encoding: 7bit
 
 
 
 



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Approve the M1 release of Apache Stonehenge (third try)

2009-06-01 Thread Drew Baird (Volt) 
I was unable to add a comment to this file.  The file does not allow comments 
and it is machine generated.


-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: Monday, June 01, 2009 11:15 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Approve the M1 release of Apache Stonehenge (third try)

+0.

There should probably be an AL header in the file:

stocktrader/dotnet/trader_client/Trade/Global.asax

but IMO this is not a blocker. Please fix for the next release.

==

The site index.html does not appear to have a link to the license;
there is a file called license.html but it does not seem to be linked
via the index page. Even it it were, the page just says:

No project license is defined for this project.

which is wrong.

There are some other orphaned pages, e.g. project-summary.html

These are not release-blockers, but they must be fixed before the site
is uploaded.

==

There are lots of missing SVN properties (eol-style and mime-type);
I'll e-mail a fixup script separately.

On 01/06/2009, Jim Jagielski j...@jagunet.com wrote:
 +1


  On Jun 1, 2009, at 2:43 AM, Selvaratnam Uthaiyashankar wrote:


  Hi,
 
  The Apache Stonehenge community has voted for the M1 release of Apache
  Stonehenge. We are now asking the approval from the Incubator PMC to
  publish the release.
 
  Stonehenge is a set of example applications for Service Oriented
  Architecture that spans languages and platforms and demonstrates best
  practise and interoperability.
 
  I have uploaded the Apache Stonehenge M1 release artifacts here:
  http://people.apache.org/~shankar/stonehenge/m1/take4/
 
  The key is here:
 
 http://people.apache.org/~shankar/stonehenge/m1/take4/KEYS
 
  RAT reports are here:
 
 http://people.apache.org/~shankar/stonehenge/m1/rat_report/take4/
 
  This release is tagged at:
 
 https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m1_incubator_take4/
 
  The release vote on the stonehenge-dev mailing list resulted in
  *nine* +1 votes and no 0 or -1 votes.
  +1 votes are from
  *Drew Baird
  *Chintana Wilamuna
  *Paul Fremantle
  *Ben Dewey
  *Kent Brown
  *Abu Obeida Bakhach
  *Nandana Mihindukulasooriya
  *Kamaljit Bath
  *Selvaratnam Uthaiyashankar
 
  This includes one IPMC vote from:
  *Paul Fremantle
 
  Vote Mail Thread is here:
 
 http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg01030.html
 
  Previous attempts on gene...@incubator list is here:
 
 http://www.mail-archive.com/general@incubator.apache.org/msg21414.html
 
 http://www.mail-archive.com/general@incubator.apache.org/msg21453.html
 
  More information about the project can be found here:
  [Incubation Status Page]
 http://incubator.apache.org/projects/stonehenge.html
  [Project Page] http://incubator.apache.org/stonehenge/
 
  Please vote to approve this release.
  [] +1 Publish
  [] +0
  [] -0
  [] -1 Don't publish
 
  Regards,
  Shankar
 
 
 -
  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] Approve the M1 release of Apache Stonehenge (third try)

2009-06-01 Thread Drew Baird (Volt) 
Correction: I can add a comment just not in the header. The first place to put 
an AL header is at the code block.

I can add it there.
Drew


-Original Message-
From: Drew Baird (Volt) [mailto:a-dre...@microsoft.com] 
Sent: Monday, June 01, 2009 12:09 PM
To: general@incubator.apache.org
Subject: RE: [VOTE] Approve the M1 release of Apache Stonehenge (third try)

I was unable to add a comment to this file.  The file does not allow comments 
and it is machine generated.


-Original Message-
From: sebb [mailto:seb...@gmail.com] 
Sent: Monday, June 01, 2009 11:15 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Approve the M1 release of Apache Stonehenge (third try)

+0.

There should probably be an AL header in the file:

stocktrader/dotnet/trader_client/Trade/Global.asax

but IMO this is not a blocker. Please fix for the next release.

==

The site index.html does not appear to have a link to the license;
there is a file called license.html but it does not seem to be linked
via the index page. Even it it were, the page just says:

No project license is defined for this project.

which is wrong.

There are some other orphaned pages, e.g. project-summary.html

These are not release-blockers, but they must be fixed before the site
is uploaded.

==

There are lots of missing SVN properties (eol-style and mime-type);
I'll e-mail a fixup script separately.

On 01/06/2009, Jim Jagielski j...@jagunet.com wrote:
 +1


  On Jun 1, 2009, at 2:43 AM, Selvaratnam Uthaiyashankar wrote:


  Hi,
 
  The Apache Stonehenge community has voted for the M1 release of Apache
  Stonehenge. We are now asking the approval from the Incubator PMC to
  publish the release.
 
  Stonehenge is a set of example applications for Service Oriented
  Architecture that spans languages and platforms and demonstrates best
  practise and interoperability.
 
  I have uploaded the Apache Stonehenge M1 release artifacts here:
  http://people.apache.org/~shankar/stonehenge/m1/take4/
 
  The key is here:
 
 http://people.apache.org/~shankar/stonehenge/m1/take4/KEYS
 
  RAT reports are here:
 
 http://people.apache.org/~shankar/stonehenge/m1/rat_report/take4/
 
  This release is tagged at:
 
 https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m1_incubator_take4/
 
  The release vote on the stonehenge-dev mailing list resulted in
  *nine* +1 votes and no 0 or -1 votes.
  +1 votes are from
  *Drew Baird
  *Chintana Wilamuna
  *Paul Fremantle
  *Ben Dewey
  *Kent Brown
  *Abu Obeida Bakhach
  *Nandana Mihindukulasooriya
  *Kamaljit Bath
  *Selvaratnam Uthaiyashankar
 
  This includes one IPMC vote from:
  *Paul Fremantle
 
  Vote Mail Thread is here:
 
 http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg01030.html
 
  Previous attempts on gene...@incubator list is here:
 
 http://www.mail-archive.com/general@incubator.apache.org/msg21414.html
 
 http://www.mail-archive.com/general@incubator.apache.org/msg21453.html
 
  More information about the project can be found here:
  [Incubation Status Page]
 http://incubator.apache.org/projects/stonehenge.html
  [Project Page] http://incubator.apache.org/stonehenge/
 
  Please vote to approve this release.
  [] +1 Publish
  [] +0
  [] -0
  [] -1 Don't publish
 
  Regards,
  Shankar
 
 
 -
  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



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Accept Stonehenge into the Incubator

2008-11-13 Thread Drew Baird (Volt) 
+1
Drew

From: Paul Fremantle [EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 9:41 AM
To: general@incubator.apache.org
Subject: [VOTE] Accept Stonehenge into the Incubator

The Stonehenge proposal has been around for discussion for a while,
and we now have a wide set of contributors and mentors, so I'd like to
call a vote. I know there are some other potential mentors and or
contributors still considering getting involved, but the normal Apache
process of course allows that at any time.

The proposal is here:
http://wiki.apache.org/incubator/StonehengeProposal

And also included at the end:

Please vote +1 to accept, or -1 with reasons to not accept as a podling.

Paul

StonehengeProposal
Project Stonehenge
Abstract

Stonehenge is a set of example applications for Service Oriented
Architecture that spans languages and platforms and demonstrates best
practise and interoperability.
Proposal

The aim of the Stonehenge project is to develop a set of sample
applications to demonstrate seamless interoperability across multiple
underlying platform technologies by using currently defined W3C and
OASIS standard protocols.

We are proposing this incubator project because we believe that a
project that includes a set of sample applications, with multiple
language and framework implementations will become a useful and
important part of the SOA landscape. It will:

*

  illustrate and develop best practice for interoperable
applications that communicate via distributed protocols,
*

  demonstrate interoperability between platforms,
*

  provide sample code upon which SOA developers can build,
*

  help identify interoperability issues and their solutions, and
*

  build confidence in cross-platform deployment of SOA technologies.

We believe that pursuit of these objectives at Apache has a number of
significant benefits:

   1.

  Attractiveness of Apache to the wide range of vendors and
customers willing to participate in the conception, development, and
implementation of new scenarios.
   2.

  A well-established, neutral forum and process for architectural
design and implementation.
   3.

  The flexibility of the Apache License to allow users to leverage
Stonehenge without onerous conditions.

Initially WSO2 will contribute an application called StockTrader,
which is currently implemented in various languages based on
Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and
Spring. This will form the first of several applications which will be
built in this incubator podling. In addition, we will invite
contributions of other stock trader applications, including the
Microsoft StockTrader sample found at [WWW]
http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also
invite contributions from any other organization who has similar
applications or technologies.

Interoperability between the WSO2 StockTrader 2.0 application and the
Microsoft StockTrader 2.0 has already been demonstrated and we expect
to demonstrate wider interoperability.

Going beyond StockTrader, we expect to develop additional applications
that demonstrate SOA principles in an open and collaborative manner
within the Stonehenge community.
Current Status

The development to date of the StockTrader application has
successfully shown the benefits of cross-platform interoperability and
have provided a useful example to developers on those platforms.
However, the StockTrader application as currently implemented has
limitations, including a limited repertoire of technologies (e.g.
focusing primarily on WS-Security), and a limited number of
implementation platforms (Axis2/Java, Axis2/C). We expect that this
podling would expand the scope of this effort to a wider set of
implementation platforms (including but not limited to Apache
technologies such as Apache CXF) as well as bring in a wider, more
diverse community of participants.
Meritocracy

One of the core aims of the Stonehenge proposal is to encourage
meritocracy and contribution. One core aim in coming to Apache is to
use the well-defined governance model that Apache has and to encourage
the developers of frameworks to get involved and contribute
implementations of the core components. A good proportion of the
project participants are experienced Apache contributors and totally
understand the Apache meritocracy approach. Everyone involved see that
as being crucial to the success of this project.
Core Developers

The core developers are all listed in the initial committers list
later in this proposal.
Alignment

The project already uses core libraries from the [WWW] Apache WS
project including [WWW] Apache Axis2/Java, [WWW] Rampart and [WWW]
Sandesha2. In addition, the PHP, Perl, and Python versions use the
[WWW] Apache Axis2/C libraries. We hope to develop versions that
utilize at least the [WWW] Apache CXF and [WWW] Apache Qpid projects
in the future. For build we intend to use [WWW