Pylons Project Assimilation team meeting minutes from 2019-02-25

[Steve Piercy]

Minutes from the Pylons Project Assimilation team meeting from 2019-02-25 have been posted.

https://community.plone.org/t/pylons-project-assimilation-team-minutes-2019-02-25/8131

--steve

------------------------
Steve Piercy, Eugene, OR

[Jonathan Vanasco]

can you share anything on this migration/etc?

there have only been two posts about this as minutes, but no other announcements that I could find.

[andrew.sawyers]

I’m of the same opinion; I brought this up in the IRC channel earlier - I thought I’d missed something.

Andrew

On Feb 28, 2019, at 2:49 PM, Jonathan Vanasco <jona...@findmeon.com> wrote:

can you share anything on this migration/etc?

there have only been two posts about this as minutes, but no other announcements that I could find.

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/84db2a78-7f8e-44fb-bfb7-1dab40009d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steve Piercy]

Howdy,

I assume you've all read the minutes, so I won't repeat them,
except to emphasize specific points.

The assimilation of the Pylons Project under the Plone
Foundation has the primary purpose to establish legal and
financial vehicles for the Pylons Project. Our identity and
organization shall remain intact.

Currently any funds received must go through an individual who
would incur the tax liability.

For most of the projects under the Pylons Project, we have a
one-half assignment of copyright between contributors and
Agendaless Consulting.

At this time, we are assessing current licenses and whether to
change any from the BSD-derived Repoze Public License[1] to MIT,
and if so what that process would be. Along with that would be
copyright and intellectual property.

We are also assessing which repositories under the GitHub
organization Pylons should be retained as Core (supported by the
Pylons Core team members), Community (supported by the
community), or Tomb (archived and available, but no longer supported)[2].

You can participate by providing feedback or taking on tasks in
our issue tracker. For the latter, we use the GitHub issue
tracker[3] and project board[4] under the Plone Foundation, both
of which require a signed Plone Contributor Agreement to participate.[5]

If you have specific questions, please ask. We aim for
transparency, except as needed for sensitive information or security.

[1] https://pylonsproject.org/license.html
[2] https://docs.google.com/spreadsheets/d/15ptVFLY8oWcYmxn7kNtXBLpqSPLJ2Z2L-AI8it394Cs/edit#gid=0
[3] https://github.com/plone/pylons-project-assimilation/issues
[4] https://github.com/orgs/plone/projects/4
[5] https://plone.org/foundation/contributors-agreement

--steve


On 2/28/19 at 2:50 PM, and...@sawdog.com (andrew.sawyers) pronounced:

>I’m of the same opinion; I brought this up in the IRC channel
>earlier - I thought I’d missed something.
>
>Andrew
>
>>On Feb 28, 2019, at 2:49 PM, Jonathan Vanasco <jona...@findmeon.com> wrote:
>>
>>can you share anything on this migration/etc?
>>
>>there have only been two posts about this as minutes, but no other announcements that I
>could find.
>>
>>--
>>You received this message because you are subscribed to the Google Groups
>"pylons-discuss" group.
>>To unsubscribe from this group and stop receiving emails from it, send an email to

>pylons-discus...@googlegroups.com <mailto:pylons-discus...@googlegroups.com>.

>>To post to this group, send email to pylons-...@googlegroups.com

><mailto:pylons-...@googlegroups.com>.

>>To view this discussion on the web visit
>https://groups.google.com/d/msgid/pylons-discuss/84db2a78-7f8e-44fb-bfb7-1dab40009d9f%

>40googlegroups.com <https://groups.google.com/d/msgid/pylons-discuss/84db2a78-7f8e-44fb-bfb7-1dab40009d9f%
>40googlegroups.com?utm_medium=email&utm_source=footer>.

>>For more options, visit https://groups.google.com/d/optout

><https://groups.google.com/d/optout>.

[Bert JW Regeer]

tl;dr: Nothing will change for users of the Pylons Projects, for development there will be minor changes required in the near future.

To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/r480Ps-10126i-BFB1106F675B4FB18B305F4A46F95CFB%40Steves-iMac.local.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Vanasco]

Thanks for the heads up. This all makes perfect sense. It was just weird seeing "minutes" posted with no previous announcements by this.  i thought I missed something and couldn't figure out how!

[Steve Piercy]

Apologies for the lack of formal announcement here and
elsewhere. Such is the nature of a disparate group of project
leaders instead of a formal organization. ;)

FWIW, there was a formal announcement at PloneConf 2018 in Tokyo.

https://twitter.com/sneridagh/status/1060797959648886784

It's been under discussion for over two years amongst various
project leaders and members of the Plone Foundation Board. We
share common origins and many developers. The process will take
many months to complete.

--steve


On 3/1/19 at 8:58 AM, jona...@findmeon.com (Jonathan Vanasco) pronounced: