On Monday, May 15, 2017 at 8:00:18 AM UTC+8, Tres Seaver wrote:

> The discussions which project members had with the SFC did not bear fruit 
> in the past, which isn't to say they couldn't be restarted:  only that 
> *I* (and Paul and Chris) won't be driving them. One sticking point was 
> that there are literally scores of repositories under the `Pylons` and 
> `repoze` organizations on Github, all published under the same license 
> and using the same contribution regime.  That meant that the "adopt a 
> repository" model already pioneered by SFC for other projects did not 
> work. 
>

I see. There are too many separate subprojects with different maintainers, 
so
SFC would not be able to deal with them directly.
 

> Forks incur serious engineering costs over time, compared to 
> collaboration:  in my view, forking is a 
> clear lose for both parties, 
>
I agree with this
 
Is it possible to remove/change the copyright notice on the trypyramid.com 
website ?
Something that would pass the right message that it's a community-driven 
website dedicated to free oss
Also in my opinion requirement on contributing docs / PR material should be 
relaxed, because that is the 
biggest area where Pyramid lacks people and could use all help it gets to 
improve the current situation,
where even technically inferior (imho) Flask gets more 
contributions/add-ons/PR


Thanks
Andrey

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/4ad24004-404f-45bb-9aa8-7cb1ba33d5b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to