The way to look at it is, I'm trying to carry on the work done by Peter deHaan with flexexamples.com. AFAIK, the Apache Flex site does not have a blog format specific to coding tutorials, which this "micro tutorial" format requires. Since they will be more or less single file coding tutorials, no repository will be necessary. Longer more complex examples and tutorials would be listed on my personal tech blog (which I'm going to completely revamp in the new year).
And besides, you guys have more than enough on your plate just updating the framework itself. My participatory inclinations lie more towards publishing and blogging, so I am happy to take full responsibility for apacheflexexamples.com (which is why I purchased the domain). Look at it as a fan-based tutorial site rather than an official publication. Some improvements from Peter's site will be made, such as indicating the version of the framework used, and I'll be checking back every once and a while to make sure old examples work with newer releases. If you guys wanted to include some of the future examples on the site into the Apache Flex documentation itself, similar to how Adobe used to put links to Flex examples in the ASdocs, that would be great. But I think it's important to have a separate, indexable, searchable, blog-style listing of micro tutorials for Apache Flex. If at some later date the Apache Flex team were to designate a subcommittee exclusively for tutorials and related publications, I might consider donating the site's governance to the group, but for now I think it best it remain as a "fan site". I guess what I was asking is what approvals do I need to get from Apache to use the Apache name, and it has been answered here: https://www.apache.org/foundation/marks/#domains https://www.apache.org/foundation/marks/faq/ I was thinking, as a courtesy, that I would launch a private "beta" of the site to elicit feedback from the flex team, and then the site would be launched only once everyone is comfortable that it does sufficient justice to the work being done at Apache Flex. Any further suggestions by the Apache Flex team would be welcome. Thanks, _______________________________________________________________________ Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca Author, Professional Flex 3 :: http://tinyurl.com/proflex3book Justin Mclean wrote: > Hi, > > Not to discourage you from anything, but it's suggest that that sort of > content went on the Apache Flex site or wiki. That way there's no trademark > issues, the code is correctly licensed, it can use use Apache infrastructure > and anyone can contribute to it. Unless you think there a good reason to not > do so? > > Thanks, > Justin
