On 10/19/16, 2:18 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Ok picking up this thread again ... > > >Well I think that allowing non-comitters to contribute to the page is a >pretty slim benefit. I couldn't say that we have used that even for a >single time in the past. And I think it would be good not to allow this >in general. At least I couldn't find a way to release only parts of the >site, so it's an all or nothing. And I also couldn't see any "this has >changed" so you would actually have to verify the entire page just to >make sure no one pushed anything bad. So I think it's a good thing that >non-comitters can't contribute to the site. This way we also don't have >to worry about signed ICLAs and so. "this has changed" would be on commits@. But yeah, I do not like having to push the entire site, and going through the web interface to do it. > >One thing I couldn't find in the codebase however was the footer of each >page containing the Twitter feed, the latest releases, the about flex >text and how to subscribe to mailinglists. I couldn't find this content >anywhere :-( I think that is in trunk/templates. I've been wondering why this move to Maven didn't involve just copying the templates and other files to Git. Did you try to implement a port to Bootstrap at the same time because you had to, or was it an option? > > >And I would like to state that I didn't expect this to be a race in which >the first one wins. If there are other initiatives to generating the site >in git, why not simply setup a separate branch and put that stuff in >there? I could change the buildbot job to push to "asf-site-maven" and >different solutions could co-exist. All that I want, is the ability to >produce the sites of sub-modules such as FlexJS (and it's part) >automatically. I don't think it is a race. We are just experimenting with various options. I saw an old mail where Harbs tried to get GitHub pages up. I don't know of any other current alternatives. It really is a matter of whether it is worth your time since nobody else seems to have time to help. I'm definitely not a fan of ASF CMS, I just am wondering if it truly needs replacing right now. Would it be higher impact to the project to work on Generics support instead? -Alex
