Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org)

[Jean-Baptiste Onofré]

Hi,

it's on the way for the four repositories. I should be done today.

Regards
JB

On 12/01/2019 21:11, Nick Couchman wrote:
> On Fri, Jan 11, 2019 at 1:44 AM Mike Jumper  wrote:
> 
>> On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré >
>>> Hi,
>>>
>>> No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
>>>
>>> Do you want me to create a Jira for INFRA ?
>>>
>>
>> Sure! Thanks, JB.
>>
>> - Mike
>>
> 
> Thanks for doing this, JB.  Any word on the timeline for it (maybe it's
> already done)?
> 
> -Nick
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

[GitHub] guacamole-client pull request #356: GUACAMOLE-699: Add helper script for ver...

[mike-jumper]

GitHub user mike-jumper opened a pull request:

https://github.com/apache/guacamole-client/pull/356

GUACAMOLE-699: Add helper script for verifying translations.

This change adds a utility script, `guacamole/util/check-translation.py`, 
which performs automated comparisons between the JSON files that define 
Guacamole's translated strings.

By default, strings which are present in English but absent in the 
translation will be listed (these will need to be added), as well as strings 
which are present in the translation but not in English (these are likely 
incorrect and should be removed). These checks can be disabled with command 
line options, if desired.

An additional duplicate string check can be enabled to test whether strings 
were incorrectly copied verbatim from English without being translated at all. 
This check includes some obvious exclusions (empty strings, simple numbers, 
protocol names, "Apache Guacamole"), but will likely produce false positives. 
It is disabled by default unless requested on the command line.

Usage
-

```
usage: check-translation.py [-h] [--no-missing] [--no-unused] 
[--check-copied]
[ORIGINAL] TRANSLATED

Compares two JSON translation files, as used by the Apache Guacamole web
application, listing the strings which appear to be missing or incorrect.

positional arguments:
  ORIGINALThe JSON file which should be used as the basis for
  comparison. This should be JSON which can be expected to
  contain every string used by the web application and no
  others. Typically, this will be the primary, original
  language of the web application. In the case of Apache
  Guacamole, this should be English. If omitted, the file
  "en.json" within the same directory as TRANSLATED will be
  used by default.
  TRANSLATED  The JSON file which should be compared against ORIGINAL.
  This should be the JSON which has been translated from
  ORIGINAL, and thus should contain the same set of strings 
if
  the translation is complete.

optional arguments:
  -h, --help  show this help message and exit
  --no-missingDisables checking for strings which are present in 
ORIGINAL
  but are missing from TRANSLATED. Assuming ORIGINAL
  represents the set of strings actually used by the web
  application, these strings are those which are missing and
  need to be defined for the translation to be complete. By
  default, the comparison will check for missing 
translations.
  --no-unused Disables checking for strings which are present in
  TRANSLATED but not in ORIGINAL. Assuming ORIGINAL 
represents
  the set of strings actually used by the web application,
  these strings are those which are defined by the 
translation
  but unused. By default, the comparison will check for 
unused
  translations.
  --check-copied  Enables checking for strings defined in TRANSLATED which 
are
  identical to the corresponding strings in ORIGINAL. Such
  strings may have been incorrectly copied verbatim from the
  original without being translated at all. It is also
  possible that both languages simply use the same text for
  that string, and the string is correct. As this test can
  produce false positives, it is disabled by default.
```

Example output
-

```
[mjumper@dev-mjumper guacamole]$ ./util/check-translation.py --check-copied 
src/main/webapp/translations/de.json 
Original language: en (English)
Translation language: de (Deutsch)

The following strings are missing from the translation and should be added:

APP.ACTION_DOWNLOAD
APP.ACTION_MANAGE_USER_GROUPS
APP.ACTION_SHARE
APP.ERROR_PAGE_UNAVAILABLE
APP.TEXT_ANONYMOUS_USER
CLIENT.ACTION_SHARE
CLIENT.ERROR_CLIENT_207
CLIENT.ERROR_CLIENT_208
CLIENT.ERROR_CLIENT_209
CLIENT.ERROR_CLIENT_20A
CLIENT.ERROR_CLIENT_20B
CLIENT.ERROR_TUNNEL_207
CLIENT.ERROR_TUNNEL_208
CLIENT.HELP_SHARE_LINK
CLIENT.INFO_CONNECTION_SHARED
CLIENT.TEXT_CLIENT_STATUS_UNSTABLE
LIST.TEXT_ANONYMOUS_USER
MANAGE_CONNECTION.TABLE_HEADER_HISTORY_REMOTEHOST
MANAGE_CONNECTION_GROUP.ACTION_CLONE
MANAGE_SHARING_PROFILE.DIALOG_HEADER_CONFIRM_DELETE
MANAGE_SHARING_PROFILE.FIELD_HEADER_PRIMARY_CONNECTION
 

Chat with #guacamole on Slack

[Nick Couchman]

Hey, everyone,
A while back I set up the Guacamole discussion room on HipChat.  HipChat is
going away and ASF has chosen to migrate to Slack, so I've begun the
process of getting the Guacamole channel configured in Slack.  You'll find
the #guacamole channel on https://the-asf.slack.com.  If you have an @
apache.org e-mail address you can register and sign-in with that.  If you
don't you can still join using this invite link:

https://join.slack.com/t/the-asf/shared_invite/enQtNDQ3OTEwNzE1MDg5LWY2NjkwMTEzMGI2ZTI1NzUzMDk0MzJmMWM1NWVmODg0MzBjNjAxYzUwMjIwNDI3MjlhZWRjNmNhOTM5NmIxNDk

Please note that this Slack channel/interface is not designed to replace
the mailing lists.  Particularly where topics need full community
discussion and decision and should be recorded for posterity, for example
items related to direction of development of the project, the dev@ mailing
list is still the place for those.

-Nick

Chat with #guacamole on Slack

[Nick Couchman]

Hey, everyone,
A while back I set up the Guacamole discussion room on HipChat.  HipChat is
going away and ASF has chosen to migrate to Slack, so I've begun the
process of getting the Guacamole channel configured in Slack.  You'll find
the #guacamole channel on https://the-asf.slack.com.  If you have an @
apache.org e-mail address you can register and sign-in with that.  If you
don't you can still join using this invite link:

https://join.slack.com/t/the-asf/shared_invite/enQtNDQ3OTEwNzE1MDg5LWY2NjkwMTEzMGI2ZTI1NzUzMDk0MzJmMWM1NWVmODg0MzBjNjAxYzUwMjIwNDI3MjlhZWRjNmNhOTM5NmIxNDk

Please note that this Slack channel/interface is not designed to replace
the mailing lists.  Particularly where topics need full community
discussion and decision and should be recorded for posterity, for example
items related to direction of development of the project, the dev@ mailing
list is still the place for those.

-Nick

[GitHub] guacamole-client pull request #351: GUACAMOLE-683: Add OpenID support in Doc...

[krisss85]

Github user krisss85 commented on a diff in the pull request:

https://github.com/apache/guacamole-client/pull/351#discussion_r247323482
  
--- Diff: guacamole-docker/bin/start.sh ---
@@ -404,6 +404,42 @@ END
 ln -s /opt/guacamole/radius/guacamole-auth-*.jar "$GUACAMOLE_EXT"
 }
 
+## Adds properties to guacamole.properties which select the OPENID
+## authentication provider, and configure it to connect to the specified 
OPENID
+## provider.
+##
+associate_openid() {
+
+# Verify required parameters are present
+if [ -z "$OPENID_AUTHORIZATION_ENDPOINT" ] || \
+   [ -z "$OPENID_JWKS_ENDPOINT" ]  || \
+   [ -z "$OPENID_ISSUER" ] || \
+   [ -z "$OPENID_CLIENT_ID" ]  || \  
+   [ -z "$OPENID_REDIRECT_URI" ]
+then
+cat <

Re: Guacamole extensión MongoDB

[Daniel Quirant Rico]

Hello,

I have advanced a lot in the development of the common authentication
extension for jdbc and mongo. At this moment I have a stable enough version
to share it with you and together find all possible faults that remain to
be resolved.
I am aware that there are several errors in the application, but I have a
deployment booted with MySQL and MongoDB. The two deployments are
accessible and you can navigate well through the different options, I ask
for your help to find the errors that may arise when making the different
possible cases in the application since I do not know the whole functional
part.
If you agree I prepare the pull request with my development, this includes
two new libraries, the implementation of the guacamole database with
morphia using mongodb and the shared library with all the common code
between morphia and jdbc for authentication. In addition to the adaptation
of the existing libraries of jdbc to use the new common dependency.

The name of the classes that I have used may not be suitable, since to
guide me I chose to name all the classes and interfaces, which had to be
reimplemented in the specific parts of jdbc and morphia, as an abstract in
the final part of the name . This will be refactored at the end of the
development with a more coherent nomenclature.

I hope that the development is at the level you are looking for.

I feel if the language used is not adequate, I do not speak the language
correctly.

A greeting.

El mar., 8 ene. 2019 a las 17:32, Daniel Quirant Rico (<
daniel.quirant.r...@gmail.com>) escribió:

> Hello,
>
> Thanks for your interest.
> I have finished the integration and I am solving small errors. During the 
> next week I will try to upload the code, depending on the time I have free to 
> finish reviewing the code, and you can help prove it.
>
> PS: I've noticed that in a previous email I mentioned that I was working on 
> version 0.9.4, I meant 0.9.14.
>
> Greetings.
>
>
> El dom., 6 ene. 2019 15:26, fou fe  escribió:
>
>> Hi
>> I m interesting to test your extension.
>> If you need help i m here.
>>
>> Fouad
>>
>> Télécharger Outlook pour Android 
>>
>> --
>> *From:* Daniel Quirant Rico 
>> *Sent:* Thursday, January 3, 2019 2:16:17 AM
>> *To:* dev@guacamole.apache.org
>> *Subject:* Re: Guacamole extensión MongoDB
>>
>> Hello,
>>
>> I still work hard on the common base extension, a week ago I finished the
>> development but there were many changes since I initially fork.
>> I have updated my fork and am adapting the whole new part of the user
>> groups to be able to run all the databases. By mistake when updating my
>> fork I created a pull request, I feel the confusion.
>> The adaptation completed for version 0.9.4 looks very good, I will
>> continue
>> working hard until I complete version 1.0.0.
>> If you wish, I can upload version 0.9.4 so you can take a look.
>>
>> Greetings and happy new year.
>>
>> El lun., 17 dic. 2018 a las 21:31, Daniel Quirant Rico (<
>> daniel.quirant.r...@gmail.com>) escribió:
>>
>> > I'm going to review the code a bit more to clean it, for now I have the
>> > morphia part running, I'll check that everything works in the sql part
>> and
>> > I'll do a pull request so you can check it.
>> >
>> > El vie., 14 dic. 2018 a las 12:55, Nick Couchman ()
>> > escribió:
>> >
>> >> >
>> >> > I think I have explained it more or less well, it is possible that my
>> >> > expression in the language is not the most appropriate since I do not
>> >> speak
>> >> > English well.
>> >> >
>> >> > I hope you respond with ideas and proposals, as well as your opinion
>> on
>> >> > what I am trying to solve.
>> >> > If you need to see the code, I can share it without problem, even if
>> it
>> >> is
>> >> > not completely finished.
>> >> >
>> >>
>> >> I think you did a great job of explaining it, but I do better seeing
>> >> actual
>> >> code, so if you wouldn't mind sharing examples of what you have, that
>> >> would
>> >> probably be best, at least for me.
>> >>
>> >> -Nick
>> >>
>> >
>>
>