> > 1. Activity on this list is very low (unless I'm missing > something). You report activity happening on a non-apache > list and github issues. Do we want to migrate from those > to Apache, or set up a gateway, or do you have in mind some > other approach? >
Historically, traffic on the pagespeed-dev@ group we migrated to this list has been low. We can probably improve by avoiding shortcuts and having discussions outside of this list. Or at least by posting a summary of such discussions here. As for migrating mod-pagespeed-discuss and ngx-pagespeed-discuss: I'd be happy to to see those migrate to a new mailing list, possibly merging both lists into a single users@ list for all open-source server implementations (apache, nginx, ats). The github issue system is used a lot as a discussion list by users -- lots of questions get posted over there next to actual bug reports. Migration of this issue system is in progress by transferring the repositories in question to the ASF. Does that suffice? 2. You've ticked "working towards a first release". It would > be good to see some thoughts on release policies and roadmap. > For example, does the project envisage all-at-once releases, > or a flexible policy whereby different components will be > released independently as and when it's appropriate? > As far as I know making sure the project and its dependencies are complying with ASF policies is the one thing blocking us from performing releases.. work is in progress to get that sorted and ensure all looks good. The current release process for the project is described here: https://github.com/pagespeed/mod_pagespeed/wiki/Release-Process Basically this envisions all-at-once releases.. this has been working well so far.. Do you have any thoughts on the way we do this right now? (one remark from my side: it would be nice if we could release/update online documentation independently, the need for this has come up a few times when users contribute or suggest doc enhancements after a discussion) Otto
