On Fri, Jan 6, 2012 at 6:20 PM, Brent Arnold <br...@brentarnold.com> wrote: >>Bertrand: >>> So IIUC you think that >>> >>> a) The layout of http://incubator.apache.org/flex/ should be improved? > > I don't know how the process works exactly, but how long would the project > be at the incubator page? If it's any significant amount of time, then yes > it should be improved.
I don't know what you mean by "be at the incubator page" - the website is live at http://incubator.apache.org/flex/, and if you edit its content in svn or via cms.apache.org the results go live within seconds. You can also run the CMS on your own box to play with content changes, start at http://incubator.apache.org/flex/developer-faqs.html#how_do_i_edit_this_website for more info. > >>> b) To be appealing, a website needs to use Flash? > > If the website is promoting Flex, then yes, it has to use Flash in order to > showcase what Flex can do. A non-techie person won't understand what it is > unless they can see it in action.... ok > >>> a) is easy, the website is found under >>> http://svn.apache.org/repos/asf/incubator/flex/site/trunk/ and people >>> are welcome to submit patches. > > Of course it's easy for you and me, and many of the people on this list, but > we have to consider that it's more than developers using Flex. agreed, that would be using a wiki I think > >>> As for b), the Apache CMS used to build that website can obviously >>> serve swf files, is there more to it? > > I sure hope there's more to it. What I'm trying to say is that the main > marketing force behind Flex is now in our hands. Adobe did a tremendous > amount of work to get it to where it is today, and if we take over and don't > do anything to maintain it's appeal, then it's dead in the water.... What I mean is, at the technical level, do you need more than a website that's able to serve swf files to create the cool site that you're envisioning? On the content side, that's a ton of work, I agree with that - just trying to clarify the technical requirements. > >>> >>> As others have said, we can get a wiki by just asking for it, running >>> on either MoinMoin of Confluence. Something that's worked well in >>> other projects is to use the wiki as a scratchpad where people can >>> easily contribute all types of content, and have committers cureate >>> and move the best of that to the main project's website. > > I think that's a great idea. Obviously what I'm suggesting isn't an > overnight transformation, but a wiki will be a good place to start. I'm sure > I'm not the only one who is passionate about Flex, but it's certainly more > than the handful of people on this list. sure, so a community wiki running here is probably good. .... > Not only do we take on the technical aspects of Flex (source control, bug > tracking, new > builds, etc.), but we have a responsibility (in my mind) to maintain the > marketing and > "customer facing" aspect of Flex... I agree, hence my suggestion to have committers who care about those community and marketing aspects, along with committers who care about code. To get started with this, IMO, only requires getting a flex community wiki setup at Apache, and some volunteers (like you I assume) to start fleshing it out. -Bertrand
