Re: [pylons-discuss] Pylons Project Assimilation team meeting minutes from 2019-02-25

2019-02-28 Thread 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.

> On Feb 28, 2019, at 14:53, Steve Piercy  wrote:
> 
> 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  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-discuss+unsubscr...@googlegroups.com 
>>  
>> > >.
>>> To post to this group, send email to pylons-discuss@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  
>> >  
>> 
>> 40googlegroups.com 
>> ?utm_medium=email_source=footer>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> 
>> >.
>> 
> 
> 
> Steve Piercy, Eugene, OR
> 
> -- 
> 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-discuss+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to pylons-discuss@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

Re: [pylons-discuss] Re: Pylons Project Assimilation team meeting minutes from 2019-02-25

2019-02-28 Thread 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  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-discuss+unsubscr...@googlegroups.com 
.

To post to this group, send email to pylons-discuss@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, Eugene, OR

--
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-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@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.

Re: [pylons-discuss] Re: Pylons Project Assimilation team meeting minutes from 2019-02-25

2019-02-28 Thread 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  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-discuss+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to pylons-discuss@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 
> .

-- 
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-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/EA7085C8-C338-4163-BDD6-383D034C7A92%40sawdog.com.
For more options, visit https://groups.google.com/d/optout.

[pylons-discuss] Re: Pylons Project Assimilation team meeting minutes from 2019-02-25

2019-02-28 Thread 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.

-- 
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-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@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.