Re: Proposed table of contents for Royale help documentation

Personally, I would be very cautious about WP themes or copying look-and-feel of other sites. I would like our doc to be license-able under ALv2 and not run into IP and licensing issues. -Alex On 1/23/18, 3:11 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"

Re: Royale Static ASDoc

Without doubt "routing", so getting a library that make royale search friendly is the most important task there. That's one of the things that people will need. My way of thinking is always order by order of priority. So routing is one of the key things all tech need to have in order to be

Re: Proposed table of contents for Royale help documentation

Hi, I tried to read through this thread, but many mails to catch all whats happening at the moment, and just want to say a couple of things: 1.- Regarding TOC, I think it's ok (in a quick review, I should work a bit on docs too to see how this works). But as anything, I assume that it's a

Re: [RESULT][VOTE] Release Apache Royale 0.9.0 RC2

I created a royale-swf account and was able to publish the royale-swf package. I did not try to publish a 'royale' package which is the js-only package. I will adjust the package names for the next release. -Alex On 1/23/18, 1:39 PM, "Alex Harui" wrote: >I've been

[GitHub] cottage14 closed pull request #1: Added an entry to the doc ToC

cottage14 closed pull request #1: Added an entry to the doc ToC URL: https://github.com/apache/royale-docs/pull/1 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request

[GitHub] cottage14 closed pull request #2: Provided writing guidelines

cottage14 closed pull request #2: Provided writing guidelines URL: https://github.com/apache/royale-docs/pull/2 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request

[GitHub] cottage14 closed pull request #3: Merging new, added file into develop branch

cottage14 closed pull request #3: Merging new, added file into develop branch URL: https://github.com/apache/royale-docs/pull/3 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign

Re: [royale-asjs] branch develop updated: Fix npm module name

If there is already a "royale" page in npm, then I don't think we can publish this release on npm. Isn't the module name baked into package.json? Or is there a way to set it when publishing? -Alex On 1/23/18, 12:47 PM, "bigosma...@apache.org" wrote: >This is an

Re: [RESULT][VOTE] Release Apache Royale 0.9.0 RC2

I've been trying to get the releasecandidate.xml script to do that, but it keeps failing. First I had to upgrade to npm 5.6.0. The error I am getting now is: User not found : royale-swf The internet is implying that we need to create accounts like royale-swf on npmjs.org. Does that

Re: Proposed table of contents for Royale help documentation

I have set up 2FA and presume I have to wait a while until GitHub notices. In the mean time I may create another page or two offline... On Tue, Jan 23, 2018 at 4:41 PM, Andrew Wetmore wrote: > I have requested my authentication code, but it seems to be slow >

Re: Proposed table of contents for Royale help documentation

I have requested my authentication code, but it seems to be slow arriving...Will wait. On Tue, Jan 23, 2018 at 4:28 PM, Alex Harui wrote: > Hi Andrew, > > Infra did more checking and says that you haven't enabled 2FA on GH which > is why you are being denied. The links

Re: Proposed table of contents for Royale help documentation

Hi Andrew, Infra did more checking and says that you haven't enabled 2FA on GH which is why you are being denied. The links below may help you do that. https://help.github.com/articles/securing-your-account-with-two-factor-auth entication-2fa/

Re: Proposed table of contents for Royale help documentation

Not a tremendously helpful note, in that if I follow the link about permissions it takes me to vague observations and no actionable information. On Tue, Jan 23, 2018 at 4:14 PM, Andrew Wetmore wrote: > When I follow that process and get to the merge point, GitHub tells me

Re: Proposed table of contents for Royale help documentation

When I follow that process and get to the merge point, GitHub tells me I do not have write permissions to the 'develop' branch. On Tue, Jan 23, 2018 at 4:12 PM, OmPrakash Muppirala wrote: > A good workflow would be as follows: > > * Create your personal branch off of the

Re: Proposed table of contents for Royale help documentation

A good workflow would be as follows: * Create your personal branch off of the `develop` branch * Make all your commits directly to your personal branch * When you are ready to share your work to the world, create a Pull Request from your branch to `develop` * This will let others look at and

Re: Proposed table of contents for Royale help documentation

Hi Andrew, I've never used the GH UI before. If there is a way to merge your pull requests via the UI, then you should commit them that way once we figure out why you are having permissions issues. Otherwise, it is time to use Git and clone the repo and figure out how to pull/commit/push. I

Re: Proposed table of contents for Royale help documentation

Ah, wait: I was only creating and editing that file in my personal branch. I still don't see how to do creates and edits without making and having someone else process branches. On Tue, Jan 23, 2018 at 3:50 PM, Andrew Wetmore wrote: > I now seem to be able to create and

[GitHub] cottage14 opened a new pull request #3: Merging new, added file into develop branch

cottage14 opened a new pull request #3: Merging new, added file into develop branch URL: https://github.com/apache/royale-docs/pull/3 Test of merging. This is an automated message from the Apache Git Service. To respond to

Re: Proposed table of contents for Royale help documentation

I now seem to be able to create and commit a new file, and to edit an existing file and commit the edited file directly! Excellent. What do I do with the lurking pull requests? -- Andrew Wetmore http://cottage14.blogspot.com/

Build failed in Jenkins: royale-asjs #210

See -- [...truncated 932.07 KB...] [java] [java] Jan 23, 2018 7:41:21 PM com.google.javascript.jscomp.LoggerErrorManager println [java] WARNING:

Re: Proposed table of contents for Royale help documentation

On Tue, Jan 23, 2018 at 11:35 AM, Alex Harui wrote: > Can you use Git to clone a repo and try a test commit? That might help > determine if the problem is that your committer rights are still not right > or just the rights to use the GH UI (which does allow me to use

Re: Proposed table of contents for Royale help documentation

Can you use Git to clone a repo and try a test commit? That might help determine if the problem is that your committer rights are still not right or just the rights to use the GH UI (which does allow me to use the edit button). -Alex On 1/23/18, 11:22 AM, "Andrew Wetmore"

Re: Proposed table of contents for Royale help documentation

On Tue, Jan 23, 2018 at 11:22 AM, Andrew Wetmore wrote: > I have logged out of GitHub and logged back in on the browser. GitHub > congratulates me for having joined Apache, and shows me the repositories I > am involved in, including royale-docs. I don't see any reference to

Re: Proposed table of contents for Royale help documentation

I have logged out of GitHub and logged back in on the browser. GitHub congratulates me for having joined Apache, and shows me the repositories I am involved in, including royale-docs. I don't see any reference to my permissions or how to change them. On Tue, Jan 23, 2018 at 3:13 PM, Andrew

Build failed in Jenkins: royale-asjs_jsonly #184

See -- [...truncated 522.25 KB...] [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 4 warnings set.oem.jar.uptodate: oem.jar:

Re: Proposed table of contents for Royale help documentation

I got this message from GitHub after I went through the steps you provided: You’ve been added to the Apache Committers team for the The Apache Software Foundation organization. Apache Committers has 1754 members and gives *pull* access to 1 apache repository. View Apache Committers:

Royale Static ASDoc

Hi, As you probably know, currently the only ASDoc (our API Reference) is itself a Royale app running on the CI server. It is sort of ugly, so I plan to spend a little bit of time making it look better. Volunteers to help or provide feedback are welcome. Because it is an app, I think it will

Re: Proposed table of contents for Royale help documentation

GitHub tells me I don't have write permissions to the repository when I am editing a file, and I don't know what step to take to obtain those permissions. On Tue, Jan 23, 2018 at 2:05 PM, Alex Harui wrote: > Hi Andrew, > > You shouldn't have to open Pull Requests any

Re: Proposed table of contents for Royale help documentation

Hi Andrew, You shouldn't have to open Pull Requests any more. You should be able to directly commit/push to the source and edit the wiki. Let us know if you are having problems getting that to work. -Alex On 1/23/18, 10:00 AM, "Andrew Wetmore" wrote: >Thanks! I will be

Re: Proposed table of contents for Royale help documentation

Thanks! I will be using that shortly. On Tue, Jan 23, 2018 at 1:02 PM, Nemi wrote: > Andrew, you can create a folder on github.com same way as you create file, > just type like "newFolder/newFile". When you have typed "/" github will > recognize it as a folder. > > > > -- >

Re: Proposed table of contents for Royale help documentation

Andrew, you can create a folder on github.com same way as you create file, just type like "newFolder/newFile". When you have typed "/" github will recognize it as a folder. -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [RESULT][VOTE] Release Apache Royale 0.9.0 RC2

Sorry for missing this vote. I’ve been struggling to get above water ever since I got home… Harbs > On Jan 23, 2018, at 6:58 AM, Alex Harui wrote: > > Vote passes with 3 +1 votes. > > Thanks to Piotr and Yishay for voting. > > -Alex > > On 1/22/18, 10:07 AM,