Coordination meeting notes

Overview

This page contains meeting notes for the bi-weekly coordination meetings held by the HPX Project Management Committee (PMC).

Meeting notes

2020-05-14

Agenda

• public API, namespaces, headers
• exporting symbols on windows

2020-04-16

Agenda

• docs PRs

2020-04-02

Agenda

• GSoC
• pragma once
• local runtime

2020-03-19

Agenda

• Public calendar (does stellar have a google account?)
• Modularization of distributed runtime (components, actions, agas, etc.)
• future refactoring PR (future_then_result? future_then_executor_result?)
• CMake targets PR, all ok in Phylanx?
• buildbot update?

2020-03-05

Agenda

• Decide on PMC members. Hartmut, Thomas, Mikael already agreed. John most likely agrees. Adrian or Augustin as fifth member.

Notes

2020-02-20

Agenda

• Governance: merge open PRs and announce governance document
• Create a dedicated web-home for the HPX project (extend http://stellar-group.org/libraries/hpx/ ?)
  • Contact information for PMC (contact@stellar-group.org ?), list PMC members
  • meeting notes of PMC/coordination meetings
  • voting results
  • sponsors
  • other documents (planning, guidelines, etc.)
• PRs:
  • Plugins are not really plugins?
  • RP init: API decisions
  • hpxMP
  • module naming schemes

Notes

• Governance: no more comments on governance document. Decided to merge remaining PRs and make document public (see next point about website)
• HPX website would be focal point for project
  • Content as described in agenda above
  • Hartmut will set up a wordpress site on hpx.stellar-group.org
• Must decide on first PMC
  • Mikael sends email to discuss first members of PMC
  • Odd number of people, no problems with ties
    • Prefer this, 3 or 5 people, avoid CSCS majority
  • Even number, PMC Chair special position
    • Avoid this option
  • First decision for PMC is to select a chair
• On voting/feature proposals/decisions:
  • Keep doing what we're doing with pull requests
  • Silence is agreement, speak up in disagreement
  • If situation requires it use voting procedures, but default is to discuss things as we have done so far
• Hartmut creates hpx-pmc@stellar-group.org mailing list for PMC
• Plugins not plugins?
  • IO counters true plugin (does not affect application code, shared library can be removed without consequences to applications)
  • Consider enabling parcel coalescing for everything and making it part of main library (not 100% plugin because requires changes in user code to use it)
  • Consider removing compression plugins
    • Moving out of main library guarantees that they will be forgotten and unmaintained, but should set expectations on maintenance of them (i.e. noone has tried them for a long time)
    • PMC could vote on this
  • hpxMP another candidate for removal or moving out of HPX build
    • Currently built with HPX for convenience (no need to link to separate library)
    • Performance results not as good as hoped, potentially abandon project
• Set clear expectations on maintained/experimental features of HPX library