Re: ARIA-118 plugin.yaml importing

Nothing has changed for non-committers; use the canonical GitHub fork->push patches->propose patch request method on the same two GitHub repos: https://github.com/apache/incubator-ariatosca-website and https://github.com/apache/incubator-ariatosca I’ll be on slack from now too if you need

[GitHub] djay87 opened a new pull request #212: ARIA-118 plugin.yaml importing

djay87 opened a new pull request #212: ARIA-118 plugin.yaml importing URL: https://github.com/apache/incubator-ariatosca/pull/212 This commit supports using the plugin.yaml present in a plugin wagon archive in a more simpler way as described below. imports: - file: -

[GitHub] asfgit commented on issue #212: ARIA-118 plugin.yaml importing

asfgit commented on issue #212: ARIA-118 plugin.yaml importing URL: https://github.com/apache/incubator-ariatosca/pull/212#issuecomment-348881562 Can one of the admins verify this patch? This is an automated message from the

ARIA-118 plugin.yaml importing

Hi, I need to contribute for this JIRA item. Previously I had made my contribution by forking from the apache-ariatosca project. Is the process changed now ? What is the process which I should follow now ? Regards, DJ

Re: Transition to Gitbox Complete

It's semantics, John. Recommending one mechanism but not the other means that the other mechanism is less recommended or, in other words, discouraged. This might be a mild discouragement, but it is so. The impact of this mild discouragement would be that our potential devs will likely be using

Re: Transition to Gitbox Complete

I just took "recommend" one way to discourage the other. FWIW I've used both methods with similar success; seems like personal preference. --Tom On Sun, Dec 3, 2017 at 5:23 PM, John D. Ament wrote: > On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau

Re: Transition to Gitbox Complete

Those instructions are working. I pushed a PR earlier as well as Maxim pushed a few. --Tom On Sun, Dec 3, 2017 at 5:21 PM, Suneel Marthi wrote: > If it helps, here's what was done on OpenNLP - one of the first projects > that transitioned to gitbox in July 2017 after

Re: Transition to Gitbox Complete

On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau wrote: > That still uses SSH, which then uses your pre-configured keys. Github docs > discourage this use for some reason. > Err no, github docs "recommend" using HTTPS, they don't discourage the use of SSH.

Re: Transition to Gitbox Complete

If it helps, here's what was done on OpenNLP - one of the first projects that transitioned to gitbox in July 2017 after gitbox was announced. http://opennlp.apache.org/using-git.html On Sun, Dec 3, 2017 at 10:11 AM, Thomas Nadeau wrote: > That still uses SSH, which

Re: Transition to Gitbox Complete

You *could* use those -- they are ssh with ssh keys. However, GitHub generally recommends using HTTPS. On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament wrote: > Any reason you wouldn't just use the github direct URLs? > > g...@github.com:apache/incubator-ariatosca.git >

Use of github tokens

Just to reflect this bit of important information for those pushing PRs: emblemparade [11:45 AM] also note: switching to two-factor authentication on github will involve some changes. if you want to use https URLs, you will need a personal access token. more info here:

[GitHub] tnadeauaria opened a new pull request #5: ARIA-415 Add git installation instructions to GettingStarted Guide

tnadeauaria opened a new pull request #5: ARIA-415 Add git installation instructions to GettingStarted Guide URL: https://github.com/apache/incubator-ariatosca-website/pull/5 Add git installation instructions to GettingStarted Guide, clean up some things making them consistent.

Making the usage of ARIA more generic

I've been working on making the usage of ARIA more generic, and opened up a few PRS: - https://github.com/apache/incubator-ariatosca/pull/209 - making the update of tasks triggered by events more generic. - https://github.com/apache/incubator-ariatosca/pull/211 - the current json

[GitHub] tnadeauaria closed pull request #4: ARIA-415: add git to source-based installation in Getting Started Guide

tnadeauaria closed pull request #4: ARIA-415: add git to source-based installation in Getting Started Guide URL: https://github.com/apache/incubator-ariatosca-website/pull/4 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below

[GitHub] tnadeauaria opened a new pull request #4: ARIA-415: add git to source-based installation in Getting Started Guide

tnadeauaria opened a new pull request #4: ARIA-415: add git to source-based installation in Getting Started Guide URL: https://github.com/apache/incubator-ariatosca-website/pull/4 Add git to source-based installation in Getting Started Guide. Updated main headers to reflect source or

Podling Report Reminder - December 2017

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 December 2017, 10:30 am PDT. The report for your podling will

[GitHub] mxmrlv opened a new pull request #211: ARIA-417 Encoding models to json is too strict

mxmrlv opened a new pull request #211: ARIA-417 Encoding models to json is too strict URL: https://github.com/apache/incubator-ariatosca/pull/211 This is an automated message from the Apache Git Service. To respond to the

[GitHub] asfgit commented on issue #211: ARIA-417 Encoding models to json is too strict

asfgit commented on issue #211: ARIA-417 Encoding models to json is too strict URL: https://github.com/apache/incubator-ariatosca/pull/211#issuecomment-348758528 Can one of the admins verify this patch? This is an automated

[GitHub] mxmrlv opened a new pull request #210: CFY-416 Providing handlers to logging_handlers only adds handles inst?

mxmrlv opened a new pull request #210: CFY-416 Providing handlers to logging_handlers only adds handles inst? URL: https://github.com/apache/incubator-ariatosca/pull/210 ?ead of replacing This is an automated message from

[GitHub] asfgit commented on issue #210: CFY-416 Providing handlers to logging_handlers only adds handles inst?

asfgit commented on issue #210: CFY-416 Providing handlers to logging_handlers only adds handles inst? URL: https://github.com/apache/incubator-ariatosca/pull/210#issuecomment-348758517 Can one of the admins verify this patch?

Transition to Gitbox Complete

The gitbox transition appears to have completed - thanks for setting this up Suneel. Committers please follow the instructions Suneel provided on Slack earlier to synch your apache account with github so permissions work/etc... --Tom >From slack:

Re: synchronize committers/devs/policies between code and web repos?

Sorry to reply to my own post, but I just wanted to update folks on this thread. We've transitioned the repos (https://github.com/apache/incubator-ariatosca and https://github.com/apache/incubator-ariatosca-website) with gitbox and as part of that it was clear that both repos are managed by the

Re: pip executable expected as part of plugin install.

DJ, If when you take a look at this, you find that it fails, please send detailed log/output so we can figure this out. I don’t see any of that from the thread below. Thx, —Tom On Sun, Dec 3, 2017 at 11:22 AM, Tal Liron wrote: > Hi DJ, > > A lot has changed since August.

Re: pip executable expected as part of plugin install.

Hi DJ, A lot has changed since August. :) I wonder if you can take a look at the current state of master and see if things have improved with wagon installs? On Fri, Dec 1, 2017 at 9:22 AM, D Jayachandran wrote: > Hi Ran, > > Sorry I had missed to answer this