We can work up to a GitHub repo for this, if enough people make significant contributions -- along the lines of Sokwe's recent efforts, for example. But a new thread seems like the place to start.Andrew wrote:I quite like Apple Bottom's idea of providing an optional pattern collection in Golly's download page. This would be a zip file called something like More-Patterns-v1.zip. The version number would be incremented every time the collection is changed. (Or call it More-Patterns-Sep-2017.zip if you prefer a date rather than a version number.)
The zip file would expand to a *single* folder containing various subfolders (jslife, hensel, etc) and a ReadMe.html file with pointers, recommendations, credits, etc.
So who maintains the [extended] pattern collection and where should it be hosted? I'd rather not have it as part of Golly's repository, so probably best to create a new project on sourceforge or github where Dave and Matthias can haggle over what to include.
As a starting point, let's assume that this extended pattern collection will end up in a More-Patterns folder at the same level as the Patterns folder -- via some more or less convenient download method (I have some sneaky ideas about that). Maybe there will be several "extended sub-collections", but in that case they'll all end up in folders inside the More-Patterns folder.
There are quite a few extensive pattern collections and toolkits and so forth out there, that most Golly users probably never see because they don't know what to try downloading. Maybe this could be a good way to increase visibility for some of these collections.
Thoughts, ideas, objections? Put them all here, please -- and not in the Golly 3.0 or Golly Suggestions threads!