No, but I didn't ask. I can ask in IRC tonight and see what their opinion is on it.
-Nick On Mon, Jan 14, 2013 at 1:39 PM, Alex Harui <aha...@adobe.com> wrote: > Sorry, when I said SVN, I meant under a different folder than CMS currently > watches, like a sibling of asjs, falcon, etc. SVN knows how to serve those > files. Did Infra explicitly say we can't explode it on dist? That's > another server we have write access to. > > > On 1/14/13 10:02 AM, "Nicholas Kwiatkowski" <nicho...@spoon.as> wrote: > > > When I say "CMS", I am pretty much talking about our SVN as the > repository. > > The CMS (buildbot) copies content from the SVN to its directories. > While > > it is coping, it checks each file for matches to the path strings we give > > and if they match, it does magic to it. > > > > I guess we could put it on people, but I doubt that is kosher for > something > > that is for the project... > > > > -Nick > > > > On Mon, Jan 14, 2013 at 12:28 PM, Alex Harui <aha...@adobe.com> wrote: > > > >> What do you really mean by "on our website"? Couldn't we point to a > copy > >> on > >> people@a.o or even in our SVN? > >> > >> > >> On 1/14/13 5:08 AM, "Nicholas Kwiatkowski" <nicho...@spoon.as> wrote: > >> > >>> Unfortunately, the only way to get stuff to our website is through the > >> CMS. > >>> Infra hasn't given us any other options, and from a legal standpoint, > I > >>> would rather keep them on our domain. > >>> > >>> -Nick > >>> > >>> On Mon, Jan 14, 2013 at 7:59 AM, Michael Schmalle > >>> <apa...@teotigraphix.com>wrote: > >>> > >>>> I wasn't debating the fact that asdocs need to be public, I was > >>>> questioning if having them in the CMS is our only option. > >>>> > >>>> As you said, republishing them kills the build and that proves there > >> must > >>>> be some other option or hosting solution. > >>>> > >>>> Mike > >>>> > >>>> > >>>> Quoting Nicholas Kwiatkowski <nicho...@spoon.as>: > >>>> > >>>> Personally, I like having the ASDocs on the website (and therefore, > we > >>>>> have > >>>>> to have it in the SVN). Otherwise I have to download 8 copies for > my 8 > >>>>> different machines. I asked infra on IRC to see about the > possibility > >> to > >>>>> get a "help.flex.apache.org" that wasn't run through the CMS or > >> something > >>>>> to that effect, and they didn't like the idea.. > >>>>> > >>>>> By the way, when anybody updates the ASdocs, the CMS will take about > 2 > >>>>> hours to process it. It also causes the buildbot process to crash ;S > >>>>> > >>>>> -Nick > >>>>> > >>>>> On Mon, Jan 14, 2013 at 5:12 AM, Michael Schmalle > >>>>> <apa...@teotigraphix.com>**wrote: > >>>>> > >>>>> > >>>>>> Having the asdoc in the site folder, is this a good idea? > >>>>>> > >>>>>> The seems really wrong on a gut level to me but I don't have another > >>>>>> solution at the moment. I am sitting still waiting on a broadband > >>>>>> connection just to change my site info. This is also why I only > >>>>>> selectively > >>>>>> check out whiteboard folders so I don't get multiple copied branches > >> of > >>>>>> the > >>>>>> 10000's of framework files and tests. > >>>>>> > >>>>>> In reply to the Flash docs, IMHO me a re screwed and another reason > to > >>>>>> keep running from Adobe. :) Since I have been working on a new ASDOc > >>>>>> tool/program I can see using the SWCs API to create the entries and > >> links > >>>>>> in the docs but have links in them to the Adobe live docs. > >>>>>> > >>>>>> This way you would get the api right in fornt of you all the way up > to > >>>>>> Object but not the descriptions. > >>>>>> > >>>>>> Mike > >>>>>> > >>>>>> -- > >>>>>> Michael Schmalle - Teoti Graphix, LLC > >>>>>> http://www.teotigraphix.com > >>>>>> http://blog.teotigraphix.com > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> -- > >>>> Michael Schmalle - Teoti Graphix, LLC > >>>> http://www.teotigraphix.com > >>>> http://blog.teotigraphix.com > >>>> > >>>> > >> > >> -- > >> Alex Harui > >> Flex SDK Team > >> Adobe Systems, Inc. > >> http://blogs.adobe.com/aharui > >> > >> > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
