Re: [DISCUSS] OpenServerless Proposal to the incubator

[Bertrand Delacretaz]

On Thu, May 30, 2024 at 4:58 PM Michele Sciabarra  wrote:
> ...To my understanding, since there are other "serverless something"
> trademarks, "Apache OpenServerless" should be acceptable, but here we need
> support from trademark lawyers to be sure. So I opened the issue...

+1, it's good to select a good name now!

-Bertrand

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

Re: [DISCUSS] OpenServerless Proposal to the incubator

[Bertrand Delacretaz]

Hi,

On Tue, May 28, 2024 at 8:43 AM Francois Papon
 wrote:
> ...We need to ask for a search about the project name...

That's a requirement for exiting incubation, not for entering it, as per [1] .

But it's good to have a name that doesn't need to change later, so
checking now doesn't hurt.

-Bertrand

[1] https://www.apache.org/foundation/marks/naming.html

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

Re: Is llvm exception allowed for incubator projects?

[Bertrand Delacretaz]

Hi Roman,

On Tue, Oct 24, 2023 at 8:55 AM Roman Shaposhnik  wrote:
> ...If you decide to distribute convenience binary artifact -- only then the 
> LLVM exception
> will apply and it will be OK...

Shouldn't that exception be mentioned at
https://www.apache.org/legal/resolved.html ?

I searched for "llvm" there but found nothing.

-Bertrand

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

Re: [VOTE] KIE proposal acceptance

[Bertrand Delacretaz]

Hi,

Jason Porter  wrote:
> The proposal is available at [1]...

I'm copying the proposal text here, we usually include it in vote
threads for archiving purposes.

-Bertrand

*** KIE proposal ***

Abstract

KIE (Knowledge is Everything) is a community of solutions and
supporting tooling for knowledge engineering and process automation,
focusing on events, rules, and workflows.

Proposal

KIE is a community dedicated to supporting knowledge engineering and
process automation, using standards from groups like OMG (BPMN, CMMN,
DMN), CNCF (Serverless Workflow, Cloud Events), and DMG (PMML, PFA).
KIE is comprised of leading open-source projects (like Drools and
jBPM), which provide modeling and code authoring tools in this space.
The work has a strong emphasis on being a first-class citizen for
Kubernetes but will continue to support embedded and other
environments such as edge computing. Drools and jBPM are well-known
projects in their areas of rules and workflow and they will be joined
by another project, building on a shared core with jBPM, for CNCF’s
Serverless Workflow - this project is going through a naming process
at the time of this application. Kogito is the foundation project for
workflow which jBPM and CNCF’s Serverless Workflow build on. Services
and frameworks are provided to enable those projects in a cloud-native
environment and tooling is made available through KIE Tools.

Background

Experience has shown that a holistic approach is a practical
requirement for any  knowledge engineering and process automation.
This requires a breadth of capabilities able to model and execute an
application’s data models, rules, workflows, and events. These
projects aim to provide a holistic approach with a strong emphasis on
congruency across them.

Rationale


Knowledge engineering and process automation have been and continue to
play a large part in today’s software lifecycle. To date, there have
been few truly open-source implementations of any of the
specifications (DMN, PMML, BPMN, CNCF Workflow, etc). The projects
within Red Hat implement these standards and fill that gap of having
an open-source implementation.

The projects within KIE also mesh well with other Apache projects such
as Apache Camel and Apache Airavata. Integrations could be done at the
IoT level with Apache PLC4X and others.

Developers need a solution that follows, implements, and collaborates
with these industry specifications. The Apache Software Foundation
would allow these projects to continue to grow in a vendor-neutral
environment and promote further collaboration with existing
integrations and future partners.

Initial Goals

First and foremost, we aim to enlarge the community. KIE has primarily
been an open-source community of Red Hat Developers and users outside
of Red Hat. Adding IBM to the list of developers helps, but we would
like to see more. We have ideas for the various sub-projects, such as
straight-through processing support in Kogito, better spec compliance
for the tooling, and more research into language bindings for non-Java
languages. We believe we can address some of these while an Apache
Incubator project.

Current Status


Code for the various projects with the KIE community is all hosted on
GitHub. This includes Kogito, Drools, jBPM, and KIE Tools. All of the
code is Apache 2 licensed. Red Hat has been the project’s custodian
since its inception and has maintained leadership in that area. Moving
forward into the Apache Incubator, we would need to establish the
habit of holding votes and meetings and the project updates per the
Apache Way.

We also currently maintain a YouTube channel dedicated to the
community and projects, a Twitter presence, and a LinkedIn page for
the KIE Community.

Meritocracy

Red Hat runs all of its open-source projects as meritocracies, the KIE
Community is no different. This aspect would not change any. Kogito
currently does not make a distinction between “committer” and “PMC
member” the same way Apache does. That aspect would need
implementation.

Community

The KIE Community has an active base of contributors within and
outside Red Hat. Community members currently use Zulip chat or mailing
lists hosted by Google Groups as communication tools. It has been that
way for many years. Before that, we were using IRC at Freenode for
many years. There are also mailing lists hosted on Google Groups that
are leveraged for those who prefer mailing list communication. Zulip
was started as a standard communication medium for KIE Community back
in 2020. IRC has been used since 2003.

Core Developers

Core developers would come from both Red Hat and IBM. They include
people who have been working on related projects and the creation of
the KIE Community since the beginning, and also people new to the
project.

Alignment

Projects within the KIE Community align with multiple efforts within
Apache, namely:

  *   Apache OpenWhisk
  *   Apache Airavata
  *   Apache Camel


We are currently actively 

Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.

[Bertrand Delacretaz]

Le ven. 14 oct. 2022 à 15:24, Christofer Dutz
 a écrit :
> ...Would we still have an option to intervene, if for example one PPMC bunch 
> adds people from the same company, for example?

That should be reviewed at graduation time.

A PPMC has no formal power, so cannot cause any harm to the Foundation
- but yes we need to be careful when graduation happens.

-Bertrand

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

Re: [RESULT][VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

Hi,

Bertrand Delacretaz  wrote:
> ...will report here when the dev@ list is ready.

The Baremaps dev list is now ready [1], use
dev-subscr...@baremaps.apache.org to subscribe.

-Bertrand

[1] https://lists.apache.org/list.html?d...@baremaps.apache.org

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

Re: [RESULT][VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

Le lun. 10 oct. 2022 à 11:30, Bertrand Delacretaz
 wrote:

> ..The vote passes with more than 3 binding +1s, a few non-binding +1s
> and no other votes...

I should have included a link to the vote thread:
https://lists.apache.org/thread/6qhbbdnvszpj2wwkcqb1xc05c81brw4r

-Bertrand

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

[RESULT][VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

Le jeu. 6 oct. 2022 à 14:52, Bertrand Delacretaz  wrote:

> ...The [DISCUSS] thread on Baremaps [1] has slowed down, with no
> objections AFAICS, so I'm calling a vote to accept Baremap into the
> Apache incubator...

The vote passes with more than 3 binding +1s, a few non-binding +1s
and no other votes.

Thanks to all who voted!

I'll ask for the podling to be set up and mailing lists to be created
as per https://incubator.apache.org/cookbook/#podling_infrastructure_setup
and will report here when the dev@ list is ready.

-Bertrand

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

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

Bertrand Delacretaz  wrote:
> ...I'm calling a vote to accept Baremap into the
> Apache incubator.
>...

+1, bring Baremap into the Incubator!

-Bertrand

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

[VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

 of Western Switzerland). We also started
receiving contributions from individuals and companies (e.g.,
Camptocamp).

Reliance on Salaried Developers

Baremaps started as a hobby project. The geocoder and IP to location
components are the results of experiments conceived during research
and educational projects. The HTTP component was part of an R
project at camptocamp.

Relationships with Other Apache Products

Apache Baremaps relies on other Apache projects to achieve its goals.
Apache SIS is used to import spatial data (e.g., Shapefile,
GeoPackage, GeoJSON) in PostGIS. Apache Lucene is used for indexing
text and spatial attributes. Apache Calcite may be considered as an
alternative to PostGIS in the future.

An Excessive Fascination with the Apache Brand

The geospatial community regularly encounters licensing problems. For
instance, Mapbox recently got closed source and forked into the
MapLibre project. The storage components of Apache SIS, which overlap
with other projects under LGPL in terms of functionality, take time to
develop. The most popular open source map schema for vector tiles is
currently released with a CC-BY license that discourages derivative
work. We are interested in joining the ASF because it sets a high bar
for including third-party libraries. In the long term, this will
benefit our contributors, our users, and, more generally, the
geospatial community.

Documentation

The documentation of baremaps can be found at: https://www.baremaps.com/

Initial Source

The source code of baremaps can be found at:
https://github.com/baremaps/baremaps

The base map can be found at: https://github.com/baremaps/baremaps/tree/main/map

External Dependencies

To our knowledge, none of the dependencies currently used in our main
branch are a matter of concern (BSD, MIT, Apache).

Cryptography

There is no cryptography required in Apache Baremaps at present time.

Required Resources

Mailing lists

d...@baremaps.incubator.apache.org
u...@baremaps.incubator.apache.org
comm...@baremaps.incubator.apache.org
priv...@baremaps.incubator.apache.org

Git Repositories

We would like to transfer our current github repository to the apache
organization.

Source: https://github.com/baremaps/baremaps

Target: https://github.com/apache/baremaps

Issue Tracking

We currently use GitHub to manage the issues and would also appreciate
using a GitHub project.

https://github.com/orgs/apache/projects

Initial Committers

Names of initial committers with affiliation and current ASF status:

Bertil Chapuis (Heig-vd), Apache Committer, id: bchapuis
Andrea Borghi (Camptocamp)
James Smith (Heig-vd)
Antoine Drabble (Heig-vd)
Leonard Besseau (Hobbyist)
Josh Fischer, Apache Committer, id: joshfischer

Sponsors

Champion

Bertrand Delacretaz

Mentors

Martin Desruisseaux
George Percivall
Julian Hyde
Calvin Kirs

Sponsoring Entity

The Apache Incubator

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

Re: Proposal

[Bertrand Delacretaz]

Hi,

Le ven. 20 mai 2022 à 00:33, m sacks  a écrit :
>
> And if i want to publish it without building community just publish to
> github if i understand correctly?...

You can do that, and if you have plans to join the ASF later it's
useful to take a look at [1] and ideally shape your emerging community
along these lines.

And also look at [2] as mentioned earlier, which is more specifically
about the ASF Incubator.

-Bertrand

[1] https://community.apache.org/apache-way/apache-project-maturity-model.html
[2] https://incubator.apache.org/cookbook/

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

Re: [DISCUSS] Graduate Apache Hop (Incubating) as a TLP

[Bertrand Delacretaz]

Hi,

On Mon, Nov 29, 2021 at 5:56 PM Julian Hyde  wrote:
> ...Let’s just assume that it’s OK to include people with non-Apache email 
> addresses in the graduation resolution...

I don't think that's the case, in previous similar cases Board members
asked for the resolutions to be modified to avoid including non-apache
email addresses [1].

it's very easy for the PMC to fix that as soon as it's created, by
voting in the "missing" member. To me that's the safe option here.

-Bertrand

[1] https://lists.apache.org/thread/v7b1l27zf1xbkm45y8ryzs6pc0dwcl9g
(accessible to PMC chairs and ASF Members)

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

[jira] [Commented] (INCUBATOR-269) Podlings Guides menu is too long and does not scroll

[Bertrand Delacretaz (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395151#comment-17395151
 ] 

Bertrand Delacretaz commented on INCUBATOR-269:
---

I think an index page is simple to create and it also allows for creating 
categories, commenting the suggested reading sequence etc.

> Podlings Guides menu is too long and does not scroll
> 
>
> Key: INCUBATOR-269
> URL: https://issues.apache.org/jira/browse/INCUBATOR-269
> Project: Incubator
>  Issue Type: Task
>  Components: UX
>Reporter: Dave Fisher
>Priority: Major
>
> There are 20 menus and many dividers on the podling guides menu.
> I suggest a different approach is needed.
> Options:
>  # Create guides/index.ad and have an outline of the guides on that page.
>  # Have a submenu structure.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: [WEBSITE] More Fully Move to Git

[Bertrand Delacretaz]

On Fri, Aug 6, 2021 at 7:45 PM Dave Fisher  wrote:
> ...The branches are renamed:
>
> - status/projects
> - status/ip-clearance
> - status/clutch ...

Great, thank you! Such prefixes will definitely help.

-Bertrand

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

Re: [WEBSITE] More Fully Move to Git

[Bertrand Delacretaz]

On Fri, Aug 6, 2021 at 2:43 PM Greg Stein  wrote:
>
> Branches for a purpose are appropriate...

Absolutely agreed!

But (to me) on GitHub the role of each branch can be hard to figure
out, so I think that needs to be explicitly documented.

Using conventions for branch names might help, like website/clutch as
opposed to experiment/bertrands-crazy-stuff

-Bertrand

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

Re: [WEBSITE] More Fully Move to Git

[Bertrand Delacretaz]

Hi Dave,

On Thu, Aug 5, 2021 at 6:39 PM Dave Fisher  wrote:
> ...In Pelican we will have two branches for each directory...

Just a quick comment on this: I often get crazy with repositories
which use multiple branches "for production use" as they are often not
discoverable.

If you go this route (which might be perfectly valid) please make sure
to add a big info block to the main or master branch README so people
see what's going on!

-Bertrand

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

Re: [WEBSITE] More Fully Move to Git

[Bertrand Delacretaz]

Hi Dave,

On Wed, Aug 4, 2021 at 9:32 PM Dave Fisher  wrote:
> ...I plan to complete the move of many of the files that are maintained by 
> projects
> into an ASF-Pelican workflow like I recently completed for www.apache.org...

https://github.com/apache/incubator is currently built using JBake, do
you mean to render parts of it with Pelican?

That might be confusing, but if it makes your job easier and the
website build docs are clear, why not - just wondering what your plan
is.

-Bertrand

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

Re: Unable to access Incubator's web page

[Bertrand Delacretaz]

On Wed, Jul 21, 2021 at 3:35 PM Dave Fisher  wrote:
> ...What we need is to add a check to the script to stop before committing to 
> the asf-site branch...

Makes sense, https://github.com/apache/incubator/pull/96

-Bertrand

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

Re: Unable to access Incubator's web page

[Bertrand Delacretaz]

Hi,

On Mon, Jul 19, 2021 at 1:17 PM Daniel Gruno  wrote:
> ...There's currently an issue with the web site Jenkins job, in that it
> relies on a jbake that isn't available any longer...

For Sing we use the jbake-maven-plugin [1] which IIUC does not require
more than Maven on the build node.

Shall we change the incubator website to use a similar setup? Or is
infra planning to make JBake available on build nodes anyway?

-Bertrand

[1] 
https://github.com/apache/sling-site/blob/0d3c5f5431f512ef4dfdaaefa7d6853bb39bc125/pom.xml#L43

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

[jira] [Commented] (INCUBATOR-266) Update the website redirect page of weex

[Bertrand Delacretaz (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358618#comment-17358618
 ] 

Bertrand Delacretaz commented on INCUBATOR-266:
---

In the meantime I found the new README at 
[https://github.com/apache/incubator/blob/master/assets/retired/README.md] 
which clarifies this, thank you.

> Update the website redirect page of weex
> 
>
> Key: INCUBATOR-266
> URL: https://issues.apache.org/jira/browse/INCUBATOR-266
> Project: Incubator
>  Issue Type: Task
>Reporter: Willem Jiang
>Priority: Major
>
> We can create an empty index.html for the retired project to redirect the 
> page to incubator project status page. 
> Here are the more information about in the mailing list.
> https://lists.apache.org/thread.html/r361999f665b90434c285161925935f3da759c6f95d6959763860f4f2%40%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-266) Update the website redirect page of weex

[Bertrand Delacretaz (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358600#comment-17358600
 ] 

Bertrand Delacretaz commented on INCUBATOR-266:
---

Thank you for this, to make sure I understand, could someone clarify this 
statement from the above dev list thread:

bq. The web server that hosts all the podling websites checks for a directory 
matching the host name, and redirects to the podling status file if it is 
present.

Do I understand correctly that the goal is to redirect http://weex.apache.org 
to https://incubator.apache.org/projects/weex.html ?

(which is what is happening now - I just want to make sure we document this 
clearly as those nice "minor bits of magic" are often hard to follow when we 
look at this again in the future)

RTFM links welcome of course.

> Update the website redirect page of weex
> 
>
> Key: INCUBATOR-266
> URL: https://issues.apache.org/jira/browse/INCUBATOR-266
> Project: Incubator
>  Issue Type: Task
>Reporter: Willem Jiang
>Priority: Major
>
> We can create an empty index.html for the retired project to redirect the 
> page to incubator project status page. 
> Here are the more information about in the mailing list.
> https://lists.apache.org/thread.html/r361999f665b90434c285161925935f3da759c6f95d6959763860f4f2%40%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: JPMS Projects?

[Bertrand Delacretaz]

Hi,

On Thu, Mar 18, 2021 at 6:22 AM Daniel Widdis  wrote:
> ...Regarding "Apache" = "Quality", I'd be careful.  Apache asserts [1] a 
> maxim of "Community over code"

FWIW, the Maturity Model at [1] emphasizes being honest about the
quality of a project's modules (QU10).

As mentioned there, "various levels of quality and maturity for
various modules are natural and acceptable as long as they are clearly
communicated". It is quite common for projects to have different
levels of modules like core, contrib, experimental etc. and I think
what's important is to expose those expected quality levels.

-Bertrand

[1] https://community.apache.org/apache-way/apache-project-maturity-model.html

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

Re: JPMS Projects?

[Bertrand Delacretaz]

Hi,

On Thu, Mar 18, 2021 at 6:08 AM leerho  wrote:
> ...I am seriously looking at *redesigning* our JDK8 Library using Java Modules
> leveraging JDK16+/Panama/FMA and completely replacing the need for Unsafe,
> etc.  (Not just adapting our JDK8 code to run on JDK9+ and accessing Java
> internals using JVM args.)..

FWIW, http://felix.apache.org/ which implements an OSGi framework has
had to make some changes to coexist with JPMS, maybe that can help for
your case, though their use case is quite specific as OSGi implements
its own module system.

Useful links:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20text%20~%20jpms
https://blog.osgi.org/2016/08/osgi-with-java-modules-all-way-down.html
https://blog.osgi.org/2019/09/osgi-connect-revisited.html

-Bertrand

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

Re: [LAZY CONSENSUS] Suitable Name Search Documentation

[Bertrand Delacretaz]

On Mon, Nov 30, 2020 at 11:38 PM Dave Fisher  wrote:
> ...I suggest that we eliminate everything that is on the Incubator page
> that is a “duplicate" and point to the source of record...

+1 and we should do that every time we see such duplicates.

-Bertrand

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

Re: Where to get feedback on a project before formulating a proposal

[Bertrand Delacretaz]

Hi Daniel,

On Tue, Nov 24, 2020 at 5:15 AM Daniel Widdis  wrote:
> ...none of the documents states exactly how I am supposed to recruit a 
> champion
> and mentors or where I should find them

This list is a good place for that, and the starting point is indeed
finding a champion.

You might briefly describe your project here, with relevant links, and
use "looking for a champion for project X" as your subject line.

Or, if you know anyone who's an ASF Member or Incubation Mentor,
contact them directly and ask if they'd be willing to be your
champion.

HTH - I have added this info to
http://incubator.apache.org/cookbook/#finding_a_champion_and_mentors ,
should be live soon.

-Bertrand

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

Re: Apache Training (incubating) granted all Apache committers commit rights

[Bertrand Delacretaz]

Hi,

On Sun, Sep 27, 2020 at 12:59 PM Christofer Dutz
 wrote:
> ...We're opening up commit access to all Apache committers...

Great! It would be nice to mention this at http://training.apache.org/
, in the "Getting involved" section maybe?

-Bertrand

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

Re: [DISCUSS] New builds server and who should access

[Bertrand Delacretaz]

On Tue, Jul 28, 2020 at 8:31 PM Nathan Hartman  wrote:
...
> At the very least, allow PPMC members access to the folder for their project? 
> ...

+1, like we do with other infrastructure bits, I think each podling
should get their own build folder (if they need it), with access
granted to all PPMC members.

As for a general "incubator" folder, it's probably only needed for the
https://github.com/apache/incubator website builds?
In which case giving access to Incubator PMC members only makes sense IMO.

-Bertrand

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

Re: Issue with releases / feedback from ASF board

[Bertrand Delacretaz]

Hi,

On Thu, Jun 4, 2020 at 8:44 AM Leonard Lausen  wrote:
> ...Does adding the following notice pior to any mentioning of a third-party
> binary release work for clearly informing users?...

I haven't followed all the details but IIUC what you are doing is
linking to third-party packages that can help people get started with
MXNet but are not provided by the ASF.

If that's correct, I would phrase your disclaimer a bit differently.

>
> > WARNING: The following binary release is not provided by the Apache
> > Software Foundation and third-party members of the MXNet community.
> > They may contain closed-source components with restrictive licenses.
> > You may want to download the official Apache MXNet (incubating) source
> > release instead and build from source instead

WARNING: the following links are provided for your convenience but
they point to packages that are *not* provided nor endorsed by the
Apache Software Foundation.
As such, they might contain software components with more restrictive
licenses than the Apache License and you'll need to decide whether
they are appropriate for your usage. Like all Apache Releases, the
official Apache MXNet (incubating) releases consist of source code
only and are found at .

-Bertrand

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

Re: Running clutch?

[Bertrand Delacretaz]

On Thu, Apr 30, 2020 at 2:58 PM John D. Ament  wrote:
> ...Yeah, I found those via [1].  I'm assuming since running clutch locally
> isn't mentioned it isn't needed (it errored out on my system and I was
> trying to decide if I needed to fix it).  Thanks!

That's correct, and one can also start the Jenkins builds manually
given sufficient access rights.

-Bertrand

> [1]: http://incubator.apache.org/guides/website.html#building

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

Re: Running clutch?

[Bertrand Delacretaz]

Hi,

On Thu, Apr 30, 2020 at 2:37 PM John D. Ament  wrote:
> ...After making a change to podlings.xml or projects/$podling.xml do I need to
> rerun clutch or is everything handled within jenkins now?..

As per https://github.com/apache/incubator the Clutch build runs once
a day, 
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/

Dave Fisher refactored those builds a few months ago to have the main
website build run quickly, that's
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20GIT%20Site%20-%20part%202/

-Bertrand

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

Re: [VOTE] Project proposal - Apache AgensGraph Extension

[Bertrand Delacretaz]

On Wed, Apr 15, 2020 at 5:12 PM Jim Jagielski  wrote:
>
> We would like to propose AgensGraph Extension as an Apache incubator project.
> As such, I am calling a VOTE...

+1 with the understanding that the name will be changed before
creating infrastructure.

-Bertrand

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

Re: [DISCUSS] Project proposal - Apache AgensGraph

[Bertrand Delacretaz]

On Wed, Apr 15, 2020 at 2:30 AM David Nalley  wrote:
> On Tue, Apr 14, 2020 at 5:55 PM Justin Mclean  
> wrote:
> > ...I’d suggest that if this is a know issue, that a different name be 
> > selected before entering incubation, as name changes cost Infra time and 
> > effort.
> I'd wholeheartedly agree with Justin.
> Changing after entering incubation merely generates needless makework
> for Infra in renaming mailing lists, websites, setting up redirects,..

+1, renaming before incubation makes things much easier.

I think it's fine for the incoming podling to use a
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH ticket for
that name change, to avoid having to do that again later.

-Bertrand

-Bertrand

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

Re: [DISCUSS] Project proposal - Apache AgensGraph

[Bertrand Delacretaz]

Hi,

On Thu, Apr 9, 2020 at 3:10 AM 张铎(Duo Zhang)  wrote:
> ...And an interesting observation is that,  the AgensGraph project changed the
> license to AGPL in the past and then after several month changed back to AL
> 2.0...

FWIW, I don't think these changes make a difference in terms of
entering incubation.

-Bertrand

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

Re: [DISCUSS] Project proposal - Apache AgensGraph

[Bertrand Delacretaz]

On Wed, Apr 8, 2020 at 3:32 PM Jim Jagielski  wrote:
> The proposal can be found here:
> o 
> https://cwiki.apache.org/confluence/display/INCUBATOR/AgensGraphExtension ...

+1, interesting project IMO and proposal looks good to me!

-Bertrand

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

Re: "Fork Me" on GitHub (was Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP)

[Bertrand Delacretaz]

On Fri, Mar 27, 2020 at 10:27 AM Harbs  wrote:
> ...The compromise which seemed acceptable to most in that thread seems to be 
> to remove “GitHub” from the link...

On Fri, Mar 27, 2020 at 3:46 PM John D. Ament  wrote:
> ...The problem is that "fork" means two different things, and that some
> members seem to be interpreting fork in the sense of a project level fork...

Considering this and the Board discussion mentioned in this thread I
think changing the language would work, and also using a nofollow
attribute on the link to GitHub.

I suggest:
a) Changing the language of such banners to "Pull Requests Welcome"
(because "forking" can be misunderstood and due to our fierce
corporate independence principle)
b) Asking our projects to add a "rel=nofollow" attribute on the link to GitHub
c) Asking our projects to make sure the README of their repositories
points to their .apache.org URL

I think this information belongs to
https://www.apache.org/foundation/marks/pmcs as that's where projects
find the ASF requirements for their websites - this one is not
strictly about branding but it's good to have all this info in one
place.

If we agree on this I suggest that we propose a patch for that page to
trademarks@

-Bertrand

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

Re: [MENTORS] https://www.apache.org/dist/ has been deprecated

[Bertrand Delacretaz]

Hi,

On Wed, Mar 4, 2020 at 10:15 AM Justin Mclean  wrote:
> The new URL to use is https://downloads.apache.org. ...

FWIW, https://blogs.apache.org/infra/entry/more-secure-and-robust-downloads
has more info.

-Bertrand

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

[jira] [Commented] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing

[Bertrand Delacretaz (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041748#comment-17041748
 ] 

Bertrand Delacretaz commented on INCUBATOR-250:
---

Thank you! It would be good to improve error reporting but for now the build 
works indeed.

> Website build (part 1 - Clutch phase) failing
> -
>
> Key: INCUBATOR-250
> URL: https://issues.apache.org/jira/browse/INCUBATOR-250
> Project: Incubator
>  Issue Type: Bug
>    Reporter: Bertrand Delacretaz
>Assignee: Dave Fisher
>Priority: Major
>
> Recent builds are failing at 
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
>  so things like IP clearance forms are not updated on the website.
> I tried running {{sh build_local_clutch.sh}} from 
> https://github.com/apache/incubator on my laptop and this gives the following 
> error:
> {code}
> 
> STATUS: podlings: 44
> Build Clutch Status Pages
> STATUS: pages: 44
> ABORT: clutch2.sh error
> {code}
> I don't know this code so can't tell what's happening from those messages.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing

[Bertrand Delacretaz (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041095#comment-17041095
 ] 

Bertrand Delacretaz commented on INCUBATOR-250:
---

The content of https://github.com/apache/incubator hasn't changed in the last 
28 days so I suppose it's a change in svn that's causing problems,  
https://svn.apache.org/repos/asf/incubator/public/trunk

> Website build (part 1 - Clutch phase) failing
> -
>
> Key: INCUBATOR-250
> URL: https://issues.apache.org/jira/browse/INCUBATOR-250
> Project: Incubator
>  Issue Type: Bug
>    Reporter: Bertrand Delacretaz
>Priority: Major
>
> Recent builds are failing at 
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
>  so things like IP clearance forms are not updated on the website.
> I tried running {{sh build_local_clutch.sh}} from 
> https://github.com/apache/incubator on my laptop and this gives the following 
> error:
> {code}
> 
> STATUS: podlings: 44
> Build Clutch Status Pages
> STATUS: pages: 44
> ABORT: clutch2.sh error
> {code}
> I don't know this code so can't tell what's happening from those messages.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing

[Bertrand Delacretaz (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz updated INCUBATOR-250:
--
Description: 
Recent builds are failing at 
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
 so things like IP clearance forms are not updated on the website.

I tried running {{sh build_local_clutch.sh}} from 
https://github.com/apache/incubator on my laptop and this gives the following 
error:

{code}

STATUS: podlings: 44
Build Clutch Status Pages
STATUS: pages: 44
ABORT: clutch2.sh error
{code}

I don't know this code so can't tell what's happening from those messages.

  was:
Recent builds are failing at 
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
 so things like IP clearance forms are not updated on the website.

I tried running {{sh build_local_clutch.sh}} from 
https://github.com/apache/incubator on my laptop and this gives the following 
error:

{code}

STATUS: podlings: 44
Build Clutch Status Pages
STATUS: pages: 44
ABORT: clutch2.sh error
{code}

I don't know this code so can't tell what's happening from those messages.

Interestingly, it looks like the last build that worked (#377) ran on the 
current HEAD revision (d301ce36) so I really don't know what changed.


> Website build (part 1 - Clutch phase) failing
> -
>
> Key: INCUBATOR-250
> URL: https://issues.apache.org/jira/browse/INCUBATOR-250
> Project: Incubator
>  Issue Type: Bug
>    Reporter: Bertrand Delacretaz
>Priority: Major
>
> Recent builds are failing at 
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
>  so things like IP clearance forms are not updated on the website.
> I tried running {{sh build_local_clutch.sh}} from 
> https://github.com/apache/incubator on my laptop and this gives the following 
> error:
> {code}
> 
> STATUS: podlings: 44
> Build Clutch Status Pages
> STATUS: pages: 44
> ABORT: clutch2.sh error
> {code}
> I don't know this code so can't tell what's happening from those messages.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing

[Bertrand Delacretaz (Jira)]

Bertrand Delacretaz created INCUBATOR-250:
-

 Summary: Website build (part 1 - Clutch phase) failing
 Key: INCUBATOR-250
 URL: https://issues.apache.org/jira/browse/INCUBATOR-250
 Project: Incubator
  Issue Type: Bug
Reporter: Bertrand Delacretaz


Recent builds are failing at 
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
 so things like IP clearance forms are not updated on the website.

I tried running {{sh build_local_clutch.sh}} from 
https://github.com/apache/incubator on my laptop and this gives the following 
error:

{code}

STATUS: podlings: 44
Build Clutch Status Pages
STATUS: pages: 44
ABORT: clutch2.sh error
{code}

I don't know this code so can't tell what's happening from those messages.

Interestingly, it looks like the last build that worked (#377) ran on the 
current HEAD revision (d301ce36) so I really don't know what changed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: [IP Clearance] OpenWhisk - wskdebug

[Bertrand Delacretaz]

Hi,

On Thu, Feb 20, 2020 at 4:07 PM David P Grove  wrote:
>... The IP Clearance form can be found at
> https://incubator.apache.org/ip-clearance/openwhisk-wskdebug.html

It looks like the website build is having issues (I'll report on that
separately), the source XML file has the up-to-date info, at

https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml

-Bertrand

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

Re: Hooray! DataSketches website is now completely moved!

[Bertrand Delacretaz]

Hi,

On Fri, Jan 24, 2020 at 10:42 PM leerho  wrote:
> .-.Many thanks to Joonsuk Bae and Drew Foulks of the Infra team, our website
>  is now completely moved and being
> dynamically updated!...

Great, and the website looks nice and informative!

I think it would be useful to add information to the
incubator-datasketches-website README about how the website is built
and where to look for build issues if they happen. And also ideally
how to preview one's changes before pushing them.

Then, if someone has suggestions about your website you can just send
them that URL and all the info is there, like at
https://github.com/apache/sling-site for example.

Also, I'm not sure if the pom.xml in that repository is useful but
that's a detail ;-)

-Bertrand

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

Re: eliminating MD5 and SHA1 signatures

[Bertrand Delacretaz]

On Fri, Jan 17, 2020 at 9:51 PM leerho  wrote:
> ...either the Maven deploy plugin or the repository always adds
> MD5 and SHA1 signatures as well...

FWIW, we'd like to stop using MD5 but I don't think we're there yet,
the following URLs have more info:

http://www.apache.org/dev/release-distribution
https://issues.apache.org/jira/browse/INFRA-14923
https://issues.sonatype.org/browse/NEXUS-21802

-Bertrand

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

Re: Incubator PMC members not subscribed to private list

[Bertrand Delacretaz]

Hi Justin,

On Thu, Jan 23, 2020 at 4:01 AM Justin Mclean  wrote:
> Here the subjected text of the email to be sent out, feedback welcome:..

Looks good to me with two suggestions for clarity:

> ...The IPMC is considering removing all IPMC members that have not signed up 
> to the private list...

We are considering removing from the PMC all IPMC members who have not
signed up to the private list...

> ...you may want to consider:
> a) getting involved again
> b) retiring by sending a mail...

I'd say "leaving the IPMC" instead of "retiring".

-Bertrand

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

Re: Incubator PMC members not subscribed to private list

[Bertrand Delacretaz]

Hi,

On Thu, Jan 16, 2020 at 6:25 AM Justin Mclean  wrote:
> ...Do we want to consider the drastic step of removing all IPMC from the PMC 
> who are not signed
> up to the private mailing list? They could re-instated themselves by 
> subscribing to the private list...

That would work for me, after sending them a warning that this is
going to happen.

We probably have many inactive PMC members - Whimsy lists 298 of them
and 46 podlings so I suppose we don't have more than 100 PMC members
actually active.

-Bertrand

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

Re: [VOTE] Accept YuniKorn into Apache Incubator

[Bertrand Delacretaz]

Hi,

On Fri, Jan 10, 2020 at 6:47 PM Vinod Kumar Vavilapalli
 wrote:
> I'd like to call a vote on accepting YuniKorn into the Apache Incubator...

+1

I'm copying the proposal text below, we usually do that to get
complete mail archives.

-Bertrand


YuniKorn proposal

Abstract

YuniKorn is a standalone resource scheduler responsible for scheduling
batch jobs and long-running services on large scale distributed
systems running in on-premises environments as well as different
public clouds.
Proposal

YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to
achieve fine-grained resource sharing for various workloads
efficiently on a large scale, multi-tenant and cloud-native
environments. YuniKorn brings a unified, cross-platform scheduling
experience for mixed workloads, with support for but not limited to,
Apache™ Hadoop® YARN and Kubernetes. YuniKorn is a made-up word
(credit to Vinod Kumar Vavilapalli) - it’s made up of Y for Apache™
Hadoop® YARN, K for K8s, Uni for Unified, and its pronunciation is the
same as “Unicorn”

Currently, YuniKorn is an open-source project with Apache 2.0 license.
The source code is hosted as a git-repo under github.com/cloudera
domain. We would like to share it with the ASF and expand the
community to a wider range of users and contributors.
Background

Enterprise users run their workloads on different platforms such as
Apache™ Hadoop® YARN and Kubernetes. They need to work with different
resource schedulers in order to plan their workloads to run on these
platforms efficiently. The scheduler implementations are fragmented,
and not optimized to balance existing use-cases like batch workloads
along with new needs such as cloud-native architecture, autoscaling,
etc. We need a single resource planning/management framework to manage
resources on different platforms using the same semantics, in order to
address all the important resource management requirements.
Rationale

There is no solution that exists now to address the needs of having a
unified resource scheduling experiences across platforms. That makes
it difficult to manage workloads running on different environments,
from on-premise to Cloud. YuniKorn aims to satisfy these needs.
YuniKorn is designed around the following principles:

1) Support different environments

As the compute platforms are evolving quickly, there are more and more
challenges appears in on-prem, cloud or hybrid environments. YuniKorn
aims to bring unified scheduling experiences across multiple
environments with enhanced scheduling capabilities.

2) Support extensive type of workloads

To improve the efficiency of the computing platform, a key idea is to
run different types of applications, like long-running services and
batch jobs, on shared resources. YuniKorn is an effort to address all
the scheduling features needed for such mixed workload environments.

3) Benefit both big-data and cloud-native communities

A resource scheduler needs to be capable of supporting mixed
workloads, both batch and long-running services. This is the key to
improving cluster utilization, and to reduce the complexity of
dev-ops. By creating a common scheduler that is decoupled from the
container platforms underneath, it can benefit both Apache™ Hadoop®
YARN and the Kubernetes communities.
Initial Goals

Initial goals are:

Move the existing codebase, documentation to Apache hosted repo
Setup mailing lists, web-site, CI/CD pipeline under Apache infrastructure
Setup JIRA for issue tracking
Incremental development and releases according to Apache guidelines
Expand the community and bring more diversified contributors/users
to the community

Current Status
Meritocracy

Many of the initial developers of YuniKorn are already Apache
committers and PMC members from other Apache projects, such as Apache
Hadoop and Apache Submarine. Many of us have worked in the Apache
Hadoop community for years and know the Apache way well. We believe
strongly in meritocracy in electing committers and PMC members. We
believe that contributions can come in forms other than just code: for
example, one of our initial proposed committers has contributed solely
in the area of project documentation. We will encourage contributions
and participation of all types, and ensure that contributors are
appropriately recognized.
Community

YuniKorn is a relatively new open source project, Cloudera is the
original development sponsor for YuniKorn. From the beginning of the
project itself, we had clearly aimed to have this as an open source
project, so we started to build the community from the very early
stages. We received a lot of feedback and valuable suggestions from
other community members while the project was hosted as an open source
project on github. This feedback has greatly influenced some of our
designs. For e.g, developers from Alibaba had been involved in the
very early stage of development, lots of effort related to
performance/throughput enhancement were contributed 

[jira] [Commented] (INCUBATOR-248) Incubation Overview page not found (404 error)

[Bertrand Delacretaz (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000851#comment-17000851
 ] 

Bertrand Delacretaz commented on INCUBATOR-248:
---

That part of the website is still maintained in svn, I have committed a fix to 
http://svn.apache.org/repos/asf/incubator/public/trunk/ that links to 
http://incubator.apache.org/cookbook/ instead of this dead link. The changes 
should be live within about an hour, probably less.

> Incubation Overview page not found (404 error)
> --
>
> Key: INCUBATOR-248
> URL: https://issues.apache.org/jira/browse/INCUBATOR-248
> Project: Incubator
>  Issue Type: Bug
>Reporter: Xiangdong Huang
>Priority: Major
>
> The "incubation overview" page [1] on 
> incubator.apache.org/projects/PROJECT_NAME.html returns 404 error.
>  
> "Incubator Overview" locates on the left side bar of a project's incubator 
> status page.
>  
> I checked the error exists (maybe) on all incubator projects, e.g., IoTDB [2] 
> and ShardingSphere[3].
>  
> Does someone know how to fix it?
>  
> [1] http://incubator.apache.org/policy/process.html
> [2] [http://incubator.apache.org/projects/iotdb.html] 
> [3] [http://incubator.apache.org/projects/shardingsphere.html]
> [4] https://issues.apache.org/jira/browse/INFRA-19597



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Bertrand Delacretaz]

On Sat, Dec 7, 2019 at 10:55 PM Gian Merlino  wrote:
> ...Please take a minute to vote on whether or not Apache Druid should graduate
> to a Top Level Project..

+1 (binding)

-Bertrand

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

Re: [DISCUSS] NuttX Proposal

[Bertrand Delacretaz]

Hi,

On Tue, Dec 3, 2019 at 7:45 PM Gregory Nutt  wrote:
> ...I have a request to add Abdelatif GUETTOUCHE
>  as an initial committer as well..

The proposal shouldn't be modified once the vote starts, but note that
it's easy to add committers once the podling is established. Being an
initial committer or not doesn't make a real difference.

And that's a good exercise in terms of learning how Apache works ;-)

-Bertrand

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

Re: [VOTE] Accept NuttX into the Apache Incubator

[Bertrand Delacretaz]

On Wed, Dec 4, 2019 at 6:30 AM 俊平堵  wrote:
> ...I would like to call a VOTE to accept NuttX into the
> Apache Incubator...

Enthusiastic +1 (binding)

-Bertrand

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

Re: [DISCUSS] NuttX Proposal

[Bertrand Delacretaz]

On Tue, Dec 3, 2019 at 12:39 AM Greg Stein  wrote:
>
> I say just move to a vote and stop the second-guessing. GNutt seems
> on-board. Let them get their stuff done...

Yes!

Many thanks to Greg Nutt for your comments, to me this project looks
ready to enter incubation, with some adjustments required during the
journey towards graduation.

That's what incubation is for.

-Bertrand

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

Re: Incubator cookbook: Podling Releases update

[Bertrand Delacretaz]

Hi,

On Fri, Nov 22, 2019 at 9:47 PM Craig Russell  wrote:
> ...I believe that the current cookbook recommendations need an update. [1] ...

Thank you Craig and others for these suggestions, I have incorporated
them as follows:

-Added a new "Two-phase vote on Podling Releases" to keep the cookbook "modular"
-Reworked the text as per the suggestions in this thread
-Made a few minor related changes in other sections for consistency.

I think I have included all suggestions, sometimes with a slightly
different wording.

Please review, my changes are already live at
http://incubator.apache.org/cookbook/ but it's easy to change if we
need to tweak or revert, https://github.com/apache/incubator has
instructions.

Diff at https://github.com/apache/incubator/commit/5bf9c25

-Bertrand

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

Re: [DISCUSS] NuttX Proposal

[Bertrand Delacretaz]

On Sun, Dec 1, 2019 at 3:20 PM 张铎(Duo Zhang)  wrote:
>
> ...IMO, the name 'NuttX' is a kudos to Gregory Nutt, who has been
> developing and maintaining the project for 15 years...

I'm fine with having such a name for historical reasons and I agree
that it's nice to recognize the hard work of the project's creator.

> ...No matter what is the name, he will be the center of the project

Having someone be THE center of an Apache project is not ok, our
projects are governed by their PMCs.

But as I just said in my reply to Ted about the bus factor, IMO that's
something that can be sorted out during incubation, especially if the
project's current "benevolent dictator" expressly mentions a desire to
step down from that role.

-Bertrand

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

Re: [DISCUSS] NuttX Proposal

[Bertrand Delacretaz]

On Sun, Dec 1, 2019 at 6:16 PM Ted Dunning  wrote:
> ...As a thought experiment, if Greg could go on a disconnected vacation right
> now without messing up the move to Apache, I would have no worries...

IMHO having a low bus factor is a concern for *exiting* incubation.

I don't see it as a problem for entering the Incubator, as long as
there's a plan to improve things.

-Bertrand

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

Re: [DISCUSS] NuttX Proposal

[Bertrand Delacretaz]

On Wed, Nov 27, 2019 at 2:56 AM Justin Mclean  wrote:
> ...It might be OK with just a software grant from you if are the
> copyright owner. Any other IPMC member have an opinion?...

I think when Groovy joined Apache a few of its community members
signed the software grant "on behalf of the Groovy community" or
something like that.

We have the details in our archives, and I think that might be an option here.

-Bertrand

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

Re: Incubator cookbook: Podling Releases update

[Bertrand Delacretaz]

Hi,

On Fri, Nov 22, 2019 at 9:47 PM Craig Russell  wrote:
> ...2. Votes on the dev list should automatically carry over to the general 
> list...

I disagree with making this automatic.

It's fine for whoever starts the IPMC vote to indicate that dev list
votes carry over, including a link to those vote's archived email.

I'm also fine with recommending that people do that.

But "automatic" puts the burden on IPMC members to go find those votes
(if people forget to include a link) and is not obvious from the IPMC
email archives, if it's not mentioned explicitly.

So I'd say "votes from the podling dev list should be carried over to
the Incubator PMC vote, by explicitly mentioned them and including a
link to the corresponding vote tally (from lists.apache.org) in the
Incubator PMC vote message".

...or something like that.

I also think the proposed text does not match the current concise
style of the cookbook but (as Blaise Pascal would say ;-) I don't have
time to make it shorter right now. I've put that on my list but don't
wait for me if someone wants to publish it.

-Bertrand

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

Re: [VOTE] Accept StreamPipes into the Apache Incubator

[Bertrand Delacretaz]

On Thu, Nov 7, 2019 at 8:00 PM Dominik Riemer  wrote:
>   [X ] +1, bring StreamPipes into the Incubator..

With 5 mentors for 5 initial committers you should be well taken care of ;-)

-Bertrand

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

Re: [DISCUSS] Host Dynamic Content on Apache Sever?

[Bertrand Delacretaz]

Hi,

On Tue, Nov 5, 2019 at 4:33 AM 申远  wrote:
>... Is there a way to migrate such dynamic content to https://weex.apache.org 
>?..

A project can get virtual machines, not sure what the current flavor
of that is but https://www.apache.org/dev/services#virtual-servers
mentions FreeBSD jails and Ubuntu VMs. See
https://www.apache.org/dev/infra-contact for how to ask for that.

In the specific case of [1] I think some rebranding would allow it to
remain separate form Apache Weex, mainly saying it's an editor "for
Apache Weex" and adding the usual disclaimers and a link to
https://weex.apache.org/ - https://www.apache.org/foundation/marks/
has more details.

> [1] http://editor.weex.io/

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

Re: Omid and Tephra

[Bertrand Delacretaz]

Hi,

On Wed, Oct 30, 2019 at 3:55 PM Josh Elser  wrote:
> ...My current expectation is that we'd just rename the existing Git
> repositories and change the LDAP group which are used to determine write
> access...

>From the Incubator's point of view, I think an additional step is to
confirm and document if any Software Grants were needed for these
projects code and if yes if they've been filed as needed.

This can be just a jira or other ticket documenting the move and
including this info.

-Bertrand

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

Re: [VOTE] Accept TubeMQ into the Apache Incubator

[Bertrand Delacretaz]

On Wed, Oct 30, 2019 at 2:48 AM David Nalley  wrote:
> ...I would like to call a VOTE to accept TubeMQ into the
> Apache Incubator

+1, binding

-Bertrand

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

Re: Donation of subproject for PLC4X

[Bertrand Delacretaz]

On Mon, Oct 7, 2019 at 10:52 AM Lars Francke  wrote:
> ...while a name search is not necessary I'm sure you're aware that there's
> already an Apache Crunch project which _might_ confuse people...

Good point, thanks!

While a formal podling name search is not needed, it's of course a
good idea to choose a somewhat unique name. My favorite metric for
that is if Google doesn't find the suggested name...

-Bertrand

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

Re: Podling proposal pages

[Bertrand Delacretaz]

Hi,

On Mon, Oct 7, 2019 at 3:59 AM Justin Mclean  wrote:
> I'm thinking of removing this page (and links to it)  as it’s incomplete and 
> what is says
> could give the wrong impression. [3] ..

+1 to removing, I think https://incubator.apache.org/cookbook/ has
sufficient info about entry into the Incubator.

-Bertrand

> 3. https://incubator.apache.org/guides/entry.html

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

Re: Donation of subproject for PLC4X

[Bertrand Delacretaz]

Hi,

On Wed, Oct 2, 2019 at 1:59 PM Julian Feinauer
 wrote:
> my company decided to donate our project CRUNCH [1] that has been developed 
> internally to the ASF

> ...We need to find a name and go through namesearch, or?...

No, that's only for Apache PMCs which need to have a suitable name.

IOW if your module is called "Apache PLC4X Foo" you don't need to do a
name search on "Foo".

> And also we need to do IP Clearance, or?

Yes, see https://incubator.apache.org/ip-clearance/

-Bertrand

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

Re: Incubator policy wording

[Bertrand Delacretaz]

Hi Justin,

On Thu, Jul 25, 2019 at 5:26 AM Justin Mclean  wrote:
> I reorganised the policy pages and that can be seen here. [1]

Thanks!

> ..The next task which I think would be useful to to simply that language on 
> that page...

I have slightly reworked the beginning and added a link to the
cookbook - basically telling people that this policy page might not be
what they are really looking for.

It would still be good to improve the page, but it's probably rarely
needed except as a reference that we can point to when explaining
things.

-Bertrand

> 1. https://incubator.apache.org/policy/incubation.html

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

Re: Feedback on board report / incubator release proposal

[Bertrand Delacretaz]

On Wed, Jul 24, 2019 at 10:30 AM Justin Mclean  wrote:
> ...No issue from me if you want to change the proposal to use this wording...

Ok, I have updated the "proposal" section as above, with a minor
tweak, "acceptable for such non-compliant incubating releases"

-Bertrand

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

Re: Cookbook and duplication of content on incubator site

[Bertrand Delacretaz]

Hi Justin,

Thank you for addressing this, I was planning to work on this
duplication of content but didn't get to it yet.

On Wed, Jul 24, 2019 at 8:44 AM Justin Mclean  wrote:
> With the cookbook added [1] I suggest that we remove this page:
> https://incubator.apache.org/policy/process.html

+1

> And move this page:
> https://incubator.apache.org/policy/roles_and_responsibilities.html
> To:
> https://incubator.apache.org/guides/roles_and_responsibilities.html

+1

> And heavily cut down this page:
> https://incubator.apache.org/policy/incubation.html
> to remove anything that not actually IPMC policy.

+1 as you suggest.

> ...And that leaves:
> - Podling Constraints and sub headings

Note that the branding constraints are already pointed to by
http://incubator.apache.org/cookbook/#publicity_and_announcements

>
> We should add the section under "Podling Website Requirements” from:
> https://incubator.apache.org/guides/sites.html
> to this policy page with a few adjustments, like the need a disclaimer on the 
> podling web site.

+1

> What do other IPMC members think?..

+1 and thank you!

-Bertrand

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

Re: Feedback on board report / incubator release proposal

[Bertrand Delacretaz]

Hi Justin,

On Wed, Jul 24, 2019 at 3:38 AM Justin Mclean  wrote:
> ...Here's a slightly updated version of that original proposal. [1]..

Thank you for this, great summary!

I have added a "summary" intro paragraph, fixed a few typos,
simplified one phrase and suggest the following text to replace the
"proposal", replacing the term "serious issues" which a documented
list of acceptable issues.

> Proposal
> That the IPMC can allow non-compliant releases to be and distributed without 
> IPMC VP or
> legal VP approval, based on a documented list of issues which are acceptable 
> for such
> incubating releases. Such releases will include an alternative work in 
> progress
> DISCLAIMER-WIP to make users aware of the issues . When this occurs, podlings
> document the issues as blocking graduation and carry on incubating. They will 
> not
> be allowed to graduate until all such release issues have been fixed.

-Bertrand

> 1. 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Proposal

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

Re: [VOTE][LAZY] the Incubator as a service provider for podlings (was: overzealous bureaucracy...)

[Bertrand Delacretaz]

On Thu, Jul 18, 2019 at 10:12 AM Bertrand Delacretaz
 wrote:
> ...I'm planning to merge #12 in the next few days unless someone from the
> Incubator PMC objects...

I have merged that now, thanks for the comments and contributions
there, the content is now live at http://incubator.apache.org/

-Bertrand

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

Re: Board@ subscriptions

[Bertrand Delacretaz]

Hi Tom,

On Sun, Jul 21, 2019 at 6:38 PM Tom Barber  wrote:
> ...Quick protocol question as the board isn’t fit for purpose and I’m fed up
> of it clogging up my inbox

Requiring subject line tags like [chairs] on board@ might help
tremendously in keeping the traffic manageable by PMC chairs, if the
convention is that it's the only messages that they have to read.

If you feel this might help you it might be good to start a [POLL]
thread on board@ so that other PMC chairs can express their interest.

-Bertrand

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

[VOTE][LAZY] the Incubator as a service provider for podlings (was: overzealous bureaucracy...)

[Bertrand Delacretaz]

Hi,

As discussed in the "overzealous bureaucracy" thread, I suggest
changing the text on the http://incubator.apache.org/ homepage to
present the Incubator as a service provider for podlings.

I think the current description can be understood as the Incubator
being a"stern gatekeeper to the ASF" and that's not good.

Defining the Incubator a service provider will give us a documented
basis to adapt our tone and processes if we (or podlings) notice that
we're being a stern gatekeeper again, as has happened in the past.

If people agree with the general idea we can discuss the details of
the new text at https://github.com/apache/incubator/pull/12 if needed.

I suggest using this thread more to discuss (and hopefully approve ;-)
the general idea of this change.

I'm planning to merge #12 in the next few days unless someone from the
Incubator PMC objects.

-Bertrand

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

Re: New disclaimer text

[Bertrand Delacretaz]

Hi,

On Wed, Jul 17, 2019 at 8:06 AM Justin Mclean  wrote:
> - Keep the existing one called as it is...

And have it mention the possible additional disclaimers, as DISCLAIMER-* maybe.

>... Name the new one something like DISCLAIMER-PERMISSIVE, DISCLAIMER-ISSUES,
> DISCLAIMER-INITIAL, or DISCLAIMER-PROGRESS...

I suggest DISCLAIMER-WIP as in Work In Progress.

-Bertrand

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

Re: [RESULT] [VOTE] Recommend 'Apache OpenWhisk graduation to Top Level Project' resolution to the board

[Bertrand Delacretaz]

On Thu, Jul 11, 2019 at 10:05 PM Dave Grove  wrote:
> ...This vote passed with with 6 +1 votes and no 0 or -1 votes...

Ouch, and I missed voting! Here's my belated enthusiastic +1 ;-)

-Bertrand

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

Re: New Project?

[Bertrand Delacretaz]

Hi,

On Tue, Jul 2, 2019 at 9:28 PM Alejandro Caceres
 wrote:
> ...I've been looking at a lot of resources to how
> best to submit this to Apache...

Note that http://incubator.apache.org/cookbook/ might have useful
information as well.

-Bertrand

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

Re: New disclaimer text

[Bertrand Delacretaz]

Hi,

On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean  wrote:
> ...I put up suggested text changes for an incubator disclaimer here [1]...

Basically just adding this, right?

> Some of the project releases may not follow ASF policy or have
> incomplete or unknown licensing conditions

It works for me but I'd say "incubating project" to be clearer.

> ...It also been suggested than any known issues be listed in the disclaimer...

I don't think that works as modifying the disclaimer to list issues
will change the digests of the archive that's being voted on - and
those shouldn't change IMO.

As Paul suggests in a different thread I'd go for easy to find tickets
to describe those changes. The disclaimer might point to
http://incubator.apache.org/release-issues which in turn points to
those tickets, keyed by release name and version number. Or something
like that - a permalink that points to the details.

-Bertrand

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

Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

[Bertrand Delacretaz]

Hi,

On Thu, Jun 20, 2019 at 9:38 AM Lars Francke  wrote:
> ...Projects wishing to join the ASF as a TLP would then at some point need to
> abide by the rules (some of which probably also don't make sense but that's
> a different discussion) but until then Mentors could just provide hints...

Note that this was one of the reasons for creating the Maturity Model
[1], as described in its "overview" section.

Projects that may want to move to the ASF later can start by following
those principles, or at least the ones that apply outside of the ASF,
making their move easier if the time comes.

But I'm not sure if the ASF itself needs to be involved in that.
Individuals who want to help such projects can do that independently.

-Bertrand

[1] https://community.apache.org/apache-way/apache-project-maturity-model.html

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

Re: Incubation Pain Points

[Bertrand Delacretaz]

Hi,

On Wed, Jun 19, 2019 at 6:58 PM Dave Fisher  wrote:
> ...I wonder if we agree on the Core issue?...

To me the core issue, as I said in the "overzealous bureaucracy"
thread is that the Incubator is perceived as a stern gatekeeper of the
ASF, due to the way we act in general.

To fix this I suggested there [1] starting by reformulating the
Incubator's goals in a friendlier and service-oriented way.

Once we agree on that, there's many things that we can do, but having
a strong agreement on such basic principles is the start IMO.

-Bertrand

[1] 
https://lists.apache.org/thread.html/bee993d70cc29ab412031275571351253ccf59d6dee09e7b9818d779@%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: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

[Bertrand Delacretaz]

On Wed, Jun 19, 2019 at 7:14 PM Ted Dunning  wrote:
> ...This vote is *confirming* that
> nobody has objections (of any form) to Zipkin leaving and control of the
> git repos being transferred...

I agree and this means that in this case a [LAZY] vote would have been
sufficient.

-Bertrand

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

Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

[Bertrand Delacretaz]

Hi,

On Wed, Jun 19, 2019 at 8:13 AM Greg Stein  wrote:
> ...Let's talk about the overzealous bureaucracy of the IPMC...

IMO something that can help fix that is declaring that the IPMC's goal
is to *provide services to podlings so they can become top-level ASF
Projects".

Currently, many things in the Incubator make it appear more like a
*stern gatekeeper for entry to the ASF" - like this overzealous
bureaucracy that you mention and that is often perceptible.

The difference is subtle but it can influence the IPMC's culture.

I think the place where this declaration can be made is the first few
paragraphs at http://incubator.apache.org/ - currently IMHO they do
express the "stern gatekeeper" spirit, and changing that would be a
good starting point.

How about this to replace those first few paragraphs, up to the
"getting started.." heading.

 The Incubator provides services to projects which want to enter the ASF.
 It helps those incoming projects (called "podlings") adopt the Apache style
 of governance and operation and guides them to the ASF services available
 to our projects, so they can become top-level ASF projets ("TLPs").

The Incubator delegates 2-3 mentors for each podling, as "on the
ground" agents
to act as liaisons with the various ASF teams: Incubator PMC,
Infrastructure team,
etc. and facilitate the podling's growth and operations.

   Our cookbook (link:http://incubator.apache.org/cookbook/)helps
potential podlings
   decide whether the ASF might be a good fit for them and guides them
through the
   steps required to become an Apache Software Foundation podling.

We don't need to discuss the details of this text now but I thought
providing a concrete example of what I'm thinking about might help
convince people.

Let's Make The Incubator Great Again!
#sorry #couldnresist #ducksandrun

-Bertrand

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

Re: Incubation Pain Points

[Bertrand Delacretaz]

On Tue, Jun 18, 2019 at 1:44 PM Justin Mclean  wrote:
> >...at the Incubator level I think there's
> > way to many unclear or badly documented rules.
>
> Nope, sorry that’s at the ASF level

I agree, the mess is on both sides ;-)

-Bertrand

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

Re: Incubation Pain Points

[Bertrand Delacretaz]

On Tue, Jun 18, 2019 at 1:18 PM Jim Jagielski  wrote:
> ...prepping the existing community regarding what "moving to the ASF means" 
> is the job of the Champion, no?...

I agree but it has to be based on written docs, not oral tradition as
that does not scale.

http://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
does address this at least partly, IMO.

-Bertrand

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

Re: Incubation Pain Points

[Bertrand Delacretaz]

Hi,

On Thu, Jun 13, 2019 at 9:10 PM Dave Fisher  wrote:
> ...Here are some thoughts I have to improving Incubation

FWIW, to give additional context for ASF Members, there was also a
discussion about this started by Incubator PMC members, on the board@
list: http://s.apache.org/zipkin_mentors_feb18

(as mentioned, accessible to ASF Members and PMC Chairs only, but I
think most IPMC members are ASF Members)

-Bertrand

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

Re: Incubation Pain Points

[Bertrand Delacretaz]

Hi,

On Mon, Jun 17, 2019 at 10:24 AM Christofer Dutz
 wrote:
> ...We have to make them understand that the ASF is more than a GIT repo, CI 
> Server and Mailing lists.
> That the ASF has great things to provide (Legal Shield, Marketing, Infra, 
> ...) but that this only works
> If you play along with some rules we have. Also should we explain WHY these 
> rules are there...

In principle I would agree, but at the Incubator level I think there's
way to many unclear or badly documented rules.

Could we adopt the Maturity Model [1] as the only thing to which
podlings must conform to to graduate? Do we need more than that?

Focusing on such a clearly defined set of rules and removing anything
from http://incubator.apache.org/ that's not essential in that view
might make our podlings life much easier.

-Bertrand

[1] https://community.apache.org/apache-way/apache-project-maturity-model.html
[2] http://www.apache.org/legal/release-policy.html

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

Re: [VOTE] Zipkin leave incubator, return back to OpenZipkin

[Bertrand Delacretaz]

> On Mon, Jun 17, 2019 at 8:22 PM Sheng Wu  wrote:

> > This is a call for official vote of Zipkin leave from incubator, and
> > return back to OpenZipkin.

+1

-Bertrand

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

Re: [IMPORTANT] Board proposal on podling releases

[Bertrand Delacretaz]

On Thu, Jun 13, 2019 at 12:09 PM Bertrand Delacretaz wrote:
> ...IOW, base those exceptions on a strictly managed list of acceptable 
> issues...

And add the URL of that list to the DISCLAIMER, so users know what to expect.

-Bertrand

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

Re: [IMPORTANT] Board proposal on podling releases

[Bertrand Delacretaz]

Hi,

On Thu, Jun 13, 2019 at 11:53 AM Justin Mclean  wrote:
> > I think that serious = release blocker;
>...People / podlings have requested that release blockers be allowed in 
>podling releases...

Ok, "release blocker" says much more to me than "serious issues" to
which I objected as being too vague.

I think this can only work backed by a list of issues (each with a
unique ID) which are acceptable for podlings, even though they would
not be for a TLP.

Then, if new issues are discovered that we think fall into that
category, add them to the list subject to Incubator PMC approval.

IOW, base those exceptions on a strictly managed list of acceptable issues.

-Bertrand

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

Re: [VOTE] Release Apache Training - Navigating the ASF Incubator Process 1.0 (incubating)

[Bertrand Delacretaz]

On Sun, Jun 9, 2019 at 5:10 AM Justin Mclean  wrote:
> ...We have 2 IPMC votes, and only require one more +1 IPMC vote

+1 for the release of

SHA512(apache-training-navigating-ASF-incubation-1.0-incubating.tar.gz)=
b67d311cb553f5aec784187f65e85e173da276fea13d9a810e8e340ff11af77afb79e1a8accc74b66c72ae2ce8b40853c4e72b6025f880a968a93ea78e6eecc7

As a sidenote I'm surprised that that content doesn't seem to be
published at http://training.apache.org/ - but that's not a question
for the Incubator PMC.

-Bertrand

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

Re: [VOTE] Apache OpenWhisk graduation to Top Level Project

[Bertrand Delacretaz]

Hi,

On Fri, Jun 7, 2019 at 6:36 PM Rodric Rabbah  wrote:
> ...I don't have a diversity profile per employer. I can try to gather that. Do
> you have a suggestion for the easiest way to do this? Maybe infra has some
> tools?...

Note that the ASF doesn't require people to disclose their company or
other affiliations.

If they want to do so it's fine but it's not ok to hunt for that
information without their consent.

In this case, I suppose you know many of our committers so you might
just give rough numbers if you have enough information, otherwise ask
people - iff they agree - to indicate their affiliation.

-Bertrand

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

Re: [IMPORTANT] Board proposal on podling releases

[Bertrand Delacretaz]

Hi Kevin,

On Fri, Jun 7, 2019 at 5:29 PM Kevin A. McGrail  wrote:
>... I would urge you to see the lengthy thread on the matter...

I won't - if the proposal implies disclaimers, tickets etc. those
conditions should be included in the proposal, such that a single URL
provides all the required information without having to read long
threads.

Once again, if I was on the Board I would reject such a proposal
without a clear list of conditions, precautions etc...but I'm not
anymore, so if people think it will pass like that I'm fine.

-Bertrand

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

Re: [VOTE] Release Apache OpenWhisk API Gateway (v0.10.0-incubating, rc2)

[Bertrand Delacretaz]

On Mon, Jun 3, 2019 at 7:44 PM David P Grove  wrote:
> ...We now ask IPMC members to review this release candidate and vote
> accordingly...

+1, verified as follows:

./rcverify.sh openwhisk-apigateway 'OpenWhisk API Gateway' 0.10.0-incubating rc2
rcverify.sh (script SHA1: 6871 208F 37F8 2352 BA60  E66E 8953 94E8 2832 AA69)
working in the following directory:
/var/folders/dv/tyxwrt5j7m5_z3v85tfp43qrgn/T/tmp.XyMn2Gip
fetching tarball and signatures from
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.10.0-incubating-rc2
fetching openwhisk-apigateway-0.10.0-incubating-sources.tar.gz
fetching openwhisk-apigateway-0.10.0-incubating-sources.tar.gz.asc
fetching openwhisk-apigateway-0.10.0-incubating-sources.tar.gz.sha512
fetching release keys
importing keys
gpg: key 2C4CF320: "Vincent Hou (Release manager of OpenWhisk)
" not changed
gpg: key 147F886E: "Dave Grove " not changed
gpg: key 27C86D51: "Rodric Rabbah " not changed
gpg: Total number processed: 3
gpg:  unchanged: 3
unpacking tar ball
cloning scancode
Cloning into 'incubator-openwhisk-utilities'...
remote: Enumerating objects: 57, done.
remote: Counting objects: 100% (57/57), done.
remote: Compressing objects: 100% (42/42), done.
remote: Total 57 (delta 19), reused 37 (delta 12), pack-reused 0
Unpacking objects: 100% (57/57), done.
computing sha512 for openwhisk-apigateway-0.10.0-incubating-sources.tar.gz
SHA512: openwhisk-apigateway-0.10.0-incubating-sources.tar.gz:
F3A852F8 95982ED3 5735336F D1A85FF6 AE4575AA BAF251A7 0B77AA40 EE4D0727 09C40A99
 6F1BD0ED CDA91B9B 59C9C3AF 19E7AC52 BF05A869 61C113D9 D42BB691
validating sha512... passed
verifying asc... passed (signed-by: Dave Grove )
verifying disclaimer... passed
verifing notice... passed
verifying license... passed
verifying sources have proper headers... passed
scanning for executable files... passed
scanning for non-text files... passed
scanning for archives... passed
scanning for packages... passed

-Bertrand

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

Re: [VOTE]: Release Apache OpenWhisk Runtime Node.js v1.14.0 (incubating)

[Bertrand Delacretaz]

On Thu, Jun 6, 2019 at 11:37 AM James Thomas  wrote:
> ...This is a call for vote to release Apache OpenWhisk Runtime Node.js
> v1.14.0 (incubating) ...

+1, verified as follows:

./rcverify.sh openwhisk-runtime-nodejs 'OpenWhisk Runtime Node.js'
1.14.0-incubating rc2
rcverify.sh (script SHA1: 6871 208F 37F8 2352 BA60  E66E 8953 94E8 2832 AA69)
working in the following directory:
/var/folders/dv/tyxwrt5j7m5_z3v85tfp43qrgn/T/tmp.Hs53M8FF
fetching tarball and signatures from
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.14.0-incubating-rc2
fetching openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz
fetching openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz.asc
fetching openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz.sha512
fetching release keys
importing keys
gpg: key 2C4CF320: "Vincent Hou (Release manager of OpenWhisk)
" not changed
gpg: key 147F886E: "Dave Grove " not changed
gpg: key 27C86D51: "Rodric Rabbah " not changed
gpg: Total number processed: 3
gpg:  unchanged: 3
unpacking tar ball
cloning scancode
Cloning into 'incubator-openwhisk-utilities'...
remote: Enumerating objects: 57, done.
remote: Counting objects: 100% (57/57), done.
remote: Compressing objects: 100% (42/42), done.
remote: Total 57 (delta 19), reused 37 (delta 12), pack-reused 0
Unpacking objects: 100% (57/57), done.
computing sha512 for openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz
SHA512: openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz:
EA61BE97 5E7CCA26 E18D95B5 24B5414A 1C3998C7 C00B5C8A 39F8E3F0 04F4A20B 7045173D
 0F588F43 CA911AE1 EEE0B31F 9C297417 4370BF67 3A95B83F 31335048
validating sha512... passed
verifying asc... passed (signed-by: Vincent Hou (Release manager of
OpenWhisk) )
verifying disclaimer... passed
verifing notice... passed
verifying license... passed
verifying sources have proper headers... passed
scanning for executable files... passed
scanning for non-text files... passed
scanning for archives... passed
scanning for packages... passed

-Bertrand

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

Re: [IMPORTANT] Board proposal on podling releases

[Bertrand Delacretaz]

On Fri, Jun 7, 2019 at 5:22 PM Justin Mclean  wrote:
> ...I assume from your response that you disagree with the proposal or want it 
> modified? If so how?...

I don't think it's reasonable to allow releases with "serious" issues.
But let's see what the Board thinks.

-Bertrand

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

Re: [IMPORTANT] Board proposal on podling releases

[Bertrand Delacretaz]

Hi,

On Fri, Jun 7, 2019 at 8:46 AM Justin Mclean  wrote:
> ...The proposal can be found in the draft board report. [1]...

If I was on the Board I don't think I would accept making releases
"with serious issues in them" as mentioned there.

Maybe I missed the discussion - what I would find acceptable is making
releases with minor issues, which are documented as such.

For example requiring an
http://issues.apache.org/jira/browse/INCUBATOR ticket for such
releases and pointing to a search of the "problematic-release" label
there from the DISCLAIMER so that people can find out what's wrong
with a specific release, if anything.

But IMHO that can only work for minor issues, not "serious" ones. And
it's probably good to keep a list of such acceptable minor issues if
the proposal passes, for clarity.

-Bertrand

> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019

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

Re: Podling reports due Wednesday

[Bertrand Delacretaz]

Hi,

On Sun, Jun 2, 2019 at 2:04 AM Justin Mclean  wrote:
> ...Mentors don’t forget your podlings reports are due on Wednesday

I was going to ask "where" and found
https://cwiki.apache.org/confluence/display/INCUBATOR/May2019 which
IIUC is the right place.

I suppose the table of links at
https://cwiki.apache.org/confluence/display/INCUBATOR is obsolete?

-Bertrand

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

Re: Generating + formatting the Board report from the website?

[Bertrand Delacretaz]

On Wed, May 22, 2019 at 4:27 PM Justin Mclean  wrote:
> ...I'm not sure the board will be viewing the results of the markdown but 
> just the raw text???...

I think you need plaintext for the Board report but my idea was to get
that by copying and pasting the output of the Markdown conversion:

-Select and copy the report from
https://cwiki.apache.org/confluence/display/INCUBATOR/June2019 to your
clipboard
-Paste that into a text file
-Run fold -s -w76 | cat -s on that

Including the Markdown conversion in the pipeline cleans up quite a
number of things already, even if the end result is plain text.

-Bertrand

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

Re: Generating + formatting the Board report from the website?

[Bertrand Delacretaz]

Hi,

On Wed, May 22, 2019 at 3:19 PM Justin Mclean  wrote:
> ...Reflow so that they are human readable is a little hard to write down. :-) 
> Mostly it because of the wide
> variation of formatting podlings submit their reports ...

Doesn't the new Markdown format help with that? I experimented a bit
at 
https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#testing-the-formatting
and the problems in my input are immediately visible in the preview or
after you save - so people will hopefully pay more attention now that
they see the (first stage) conversion.

Most of my sloppy formatting is already fixed by the Markdown
conversion (assuming you copy the result from the
https://cwiki.apache.org/confluence/display/INCUBATOR/June2019 output)
and the remaining problems are obvious.

And for a second stage "fold -s -w76 | cat -s" (or the equivalent in
Whimsy) might be sufficient ?

-Bertrand

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

Re: Generating + formatting the Board report from the website?

[Bertrand Delacretaz]

Hi,

On Wed, May 22, 2019 at 11:46 AM Justin Mclean  wrote:
> ...It’s still unclear to me how Whimsy will render this, guess we find out 
> when we submit it?..

I think the core of the Board agenda is the text file in svn, that's
what needs to be clean AFAIK.

-Bertrand

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

Re: Generating + formatting the Board report from the website?

[Bertrand Delacretaz]

On Wed, May 22, 2019 at 10:18 AM Justin Mclean  wrote:
> ...So INFRA kindly installed a markdown macro for confluence so you can now 
> see
> the incubator report with some formatting when you edit it. [1]..

Cool! I have removed my formatting experiment,
https://github.com/apache/incubator/commit/71701e0ee

Do you then mean to run "fold -w 76 cat -s" on the formatted Markdown
to prepare it for the Board report? That seems to work fine as the
basic formatting is now clean.

-Bertrand

> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/June2019

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

Re: Generating + formatting the Board report from the website?

[Bertrand Delacretaz]

Hi Justin,

I've put your test content in and added cat -s, the formatted result
is at http://incubator.apache.org/report.html

It doesn't look too bad to me - my point would be that if people can
see the final formatted result at that URL they can fix their reports
themselves (like for the example you give below) and you don't have to
do that.

Whereas using the wiki IIUC people don't see the final result and if
anyone runs an automatic reformat things might break.

Or we can improve the script or maybe even move to Markdown for the
input to have more control, if you think this would help.

-Bertrand

On Mon, May 20, 2019 at 12:56 PM Justin Mclean  wrote:
> ...Also this:
>   On master, 253 files have changed and there have been 14,050 additions
> and
>   3,027 deletions.
> This:
>   On master, 253 files have changed and there have been 14,050 additions
>   and 3,027 deletions.

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

Generating + formatting the Board report from the website?

[Bertrand Delacretaz]

Hi,

It seems like there was some trouble and manual work to generate the
Board report since switching to https://cwiki.apache.org/incubator

As an experiment that should make this easier, I have created a small
pipeline that starts from a text file in Git [1], uses a script to
sanitize that file [2] and publishes the result at [3], an HTML page
that includes the report in a  block.

Thanks to Dave's great work in making publishing fast, it only takes
about a minute from changing [1] to seeing the results at [3].

The idea is that people would edit the former and use the latter to
verify that the formatting and sanitizing didn't break their report.
And no more formatting work for the PMC chair, the report should be
automatically good to go - and if not the preprocessing script can be
tweaked to achieve that.

WDYT?

If we don't like this or find a better solution it's a single commit
to revert, [4]

-Bertrand

[1] https://github.com/apache/incubator/blob/master/report.txt
[2] https://github.com/apache/incubator/blob/master/preprocess_content.sh
[3] http://incubator.apache.org/report.html
[4] https://github.com/apache/incubator/commit/33ecf33

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

Re: board report duplication

[Bertrand Delacretaz]

On Sun, Apr 14, 2019 at 4:59 AM Greg Stein  wrote:
> ...Within Infra at least, we use the philosophy of "Whimsy is great, but we
> must be able to perform our work without it."...

big +1 to that, many things have been fixed quickly by being able to
just do things directly on the agenda text file.

-Bertrand

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