Pylons Project Assimilation Team Minutes 2019-02-25

stevepiercy · February 28, 2019, 12:56am

Meeting Minutes - Monday, February 25, 19:00 UTC

1. Roll Call

Érico Andrei
Steve Piercy
Paul Roeland
Bert JW Regeer
Nejc Zupan

2. Minutes from 2019-01-28 approved.

3. Document all GitHub repos under Pylons organization

Steve has completed the first pass of collecting all licenses, owners, maintainers, and destination of repositories under the Pylons Project. The next step is for Pylons Projects contributors to review this document and provide any updates by Sunday, March 10. We especially need to verify the Destination column: Core, Community, or Tomb? The public can now view and comment on the document, and all other people previously granted edit access retain that permission.

Pylons repositories, PyPI projects, and licensing:

Document all GitHub repos under Pylons organization #42:

4. Revise statutes and regulatory docs

a. 501(c)(3) status

Paul has made inquiries, but more are needed from senior attorneys. There are mixed legal opinions. Paul will continue to collect opinions and make a recommendation by our next meeting on Monday, March 25.

b. Contributor Agreement

Paul posted the CA at:

github.com

plone/pylons-project-assimilation/blob/master/PLONE FOUNDATION CONTRIBUTOR ASSIGNMENT AGREEMENT.md

# PLONE FOUNDATION

## CONTRIBUTOR ASSIGNMENT AGREEMENT

For good and valuable consideration,
receipt of which I acknowledge,
I, _____________________________________ (Name),
hereby transfer to The Plone Foundation ("Foundation") my entire right, title, and interest (including all rights under copyright) in the program _____________________________________ (“Program”),
including original code, accompanying documentation and supporting files,
changes and enhancements to the Program code and accompanying files,
and all future modifications of the Program code and accompanying files,
subject to the conditions below.
The original code, files, changes and enhancements, and modifications are herein called the "Work".

For the purposes of this contract,
a work "based on the Work" means any work that in whole or in part incorporates or is derived from all or part of the Work.
The Foundation promises that the Work and any work "based on the Work" distributed by the Foundation or its assignees will be distributed under the GNU General Public License v2 or any later version,
or any other license determined to be a free software license by the Free Software Foundation (“FSF”) or approved as an open source license by the Open Source Initiative (“OSI”).
However, the Foundation may also distribute the Work and any work “based on the Work” under other terms as well.

This file has been truncated. show original

Everyone needs to do a first round of comments on the content of the CA by Sunday, March 17. We will review comments at the next meeting, and proceed from there. Steve will notify all current recipients of the monthly meeting agenda, as well as Steve McMahon and the Plone Foundation Board to provide feedback by the deadline.

After the meeting, Steve realized that GitHub does not really support comments unless it's during a code review in which changes are proposed, and only on changes. To submit comments, people must submit a pull request with proposed changes. That would mean opening several pull requests, instead of looking in one place. That's awkward.

Instead Steve suggests moving it to Google Drive for collecting comments and having a discussion, then incorporating any comments and changes as pull requests on GitHub.

Google Drive version for public comment:

Paul posted the instructions for the CA at:

github.com

plone/pylons-project-assimilation/blob/master/INSTRUCTIONS FOR PLONE FOUNDATION CONTRIBUTOR ASSIGNMENT AGREEMENT.md

# INSTRUCTIONS FOR PLONE FOUNDATION CONTRIBUTOR ASSIGNMENT AGREEMENT

When you write or make changes to software programs, you often automatically obtain a copyright in what you wrote.
The way to assign to the Plone Foundation the copyright in software that you wrote or changes that you made to Plone Foundation software is to send us a signed Assignment Agreement.
This makes the Plone Foundation the legal copyright holder so that we can register the copyright in the software that you wrote or changes that you made.
It is assumed that you wrote the software or changes yourself;
if other people wrote or changed parts, we will likely need Assignment Agreements from them as well.

* If you are employed to do programming (even at a university),
  or have made an agreement with your employer, school or anyone else saying it owns software you write,
  then you and we need a signed writing from them disclaiming any rights they may have to the software.
  The disclaimer should be signed by a vice president, general manager, or anyone else who is authorized to assign software owned by them.
  Here is a sample wording:

*ACME Corporation hereby disclaims all copyright interest in the code written by Jane Doe for the program "[insert name of program]" (“Program”), including original Program code and documentation and support files, changes and enhancements to the Program and files, and any future modifications of the Program and files.
We do not consider the code as work made for hire for us.
ACME Corporation affirms that it has no other intellectual property interest that would undermine this release, or the use of the Program, and will do nothing to undermine it in the future.*

*signature of John Smith, 30 March 20__*

This file has been truncated. show original

The process will not change. A copy must be printed and signed in ink, then scanned or photographed, and delivered. We lack the infrastructure to properly implement electronic signatures that satisfy European Union requirements, so they are not an option.

Google Drive version for public comment:

5. Discuss whether to change software license to MIT

This needs to wait until we have revised the Plone Contributor Agreement.

6. New business.

a. Plone Foundation Bylaws

Membership should include Pylons and Zope contributors.

b. Artistic Trademarks or Artwork Copyright

Steve will Contact Blaise LaFlamme to obtain an assignment of copyright to CC-BY-SA v4.0 for all the artwork that both he and Felix contributed to Pyramid and the Pylons Project.

c. GSoC

Nejc will pursue becoming a Google Summer of Code project and mentor under the Python Software Foundation. The project's goal is to publish a real world "todo" application, where a variety of front ends and back ends use the same API specification. Pyramid would be the backend for a contribution to the real world repository.

7. Next Meeting, Monday, March 25, 19:00 UTC

Fourth Monday of the month.
11:00 AM Pacific / 19:00 UTC

Join Zoom Meeting

One tap mobile
+16468769923,,292711041# US (New York)
+16699006833,,292711041# US (San Jose)

Dial by your location
+1 646 876 9923 US (New York)
+1 669 900 6833 US (San Jose)
Meeting ID: 292 711 041
Find your local number: Zoom International Dial-in Numbers - Zoom

Here is the GitHub repo and project to track our progress.

tkimnguyen · November 9, 2019, 10:01am

Ah bummer... was fooled by the spam reply into thinking this was revived