Re: home.apache.org

[Mark Thomas]

On 13/09/2017 18:05, Peter Ent wrote:
> I get permission denied (public key). I remember having to set up
> something for the old people site (I think) and have been trying to hunt
> down the instructions.

You should be able to set up your key through id.apache.org

You then need to allow enough time (I think it is about an hour) for the
public key to sync to the servers you have access to. Then you should be
able to sftp to home.a.o.

Mark


> 
> ‹peter
> 
> On 9/13/17, 12:49 PM, "Alex Harui"  wrote:
> 
>> Should just be:
>>  sftp home.apache.org
>>
>> Hope you remember your passphrase.
>>
>> -Alex
>>
>> On 9/13/17, 9:16 AM, "Peter Ent"  wrote:
>>
>>> Hi,
>>>
>>> Does anyone have the instructions on how to set up access to your
>>> home.apache.org space? I've looked on the apache.org site and all I can
>>> find are instructions about the old people.apache.org. I guess I haven't
>>> accessed my home.apache.org since I set up my newer computer.
>>>
>>> I'm going to update my ASDocs info to point to our FlexJS ASDocs app page
>>> since Google is pointing to my old ASDoc and it needs to be more current.
>>>
>>> Thanks.
>>> Peter
>>
> 

Re: home.apache.org

[Mark Thomas]

On 13/09/17 19:27, Peter Ent wrote:
> Thanks, Mark.
> 
> I think I've done all the right stuff. As I started to do it, I began to
> remember doing it once before for SSH. I've been waiting awhile and still
> get permission denied, so I'll just keep waiting. I'm pretty sure I sent
> my key to a public key server. I'll go out for coffee and I hope it works
> when I get back.

That sounds like you might be mixing up OpenPGP release keys and SSH
keys. Anyway...

I've checked your LDAP record and you do have a public SSH key
configured. If it doesn't work when you try again let me know the time
(UTC) and IP address (send it privately if you have privacy concerns)
and I'll check the logs.

Mark


> 
> —peter
> 
> On 9/13/17, 1:22 PM, "Mark Thomas"  wrote:
> 
>> On 13/09/2017 18:05, Peter Ent wrote:
>>> I get permission denied (public key). I remember having to set up
>>> something for the old people site (I think) and have been trying to hunt
>>> down the instructions.
>>
>> You should be able to set up your key through id.apache.org
>>
>> You then need to allow enough time (I think it is about an hour) for the
>> public key to sync to the servers you have access to. Then you should be
>> able to sftp to home.a.o.
>>
>> Mark
>>
>>
>>>
>>> ‹peter
>>>
>>> On 9/13/17, 12:49 PM, "Alex Harui"  wrote:
>>>
>>>> Should just be:
>>>>  sftp home.apache.org
>>>>
>>>> Hope you remember your passphrase.
>>>>
>>>> -Alex
>>>>
>>>> On 9/13/17, 9:16 AM, "Peter Ent"  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Does anyone have the instructions on how to set up access to your
>>>>> home.apache.org space? I've looked on the apache.org site and all I
>>>>> can
>>>>> find are instructions about the old people.apache.org. I guess I
>>>>> haven't
>>>>> accessed my home.apache.org since I set up my newer computer.
>>>>>
>>>>> I'm going to update my ASDocs info to point to our FlexJS ASDocs app
>>>>> page
>>>>> since Google is pointing to my old ASDoc and it needs to be more
>>>>> current.
>>>>>
>>>>> Thanks.
>>>>> Peter
>>>>
>>>
>>
> 

Re: home.apache.org

[Mark Thomas]

On 13/09/17 21:00, Peter Ent wrote:
> My LDAP entry at id.apache.org has a OpenPGP Public Key Primary
> Fingerprint set. I assume when I do sftp p...@home.apache.org it looks up
> 'pent' and sees the OpenPGP fingerprint, goes out to some key server and
> fetches whatever it needs.
> 
> And after all this time I still get Permission denied. Maybe that's not a
> real PGP key. I looked up PGP for the Mac and found GPG Keychain which it
> says makes OpenPGP keys. Just very confused.

OK. You are mixing up key types.

The OpenPGP is typically used for signing releases and encrypting
e-mail. It isn't used for SSH.

Separately, you should also see in id.apache.org one or more "SSH Key
(authorized keys)" line.

This is the SSH public key that corresponds to your SSH private key that
you would typically store in ~/.ssh/id_rsa
(you can be more descriptive with the filename if you want to be)

If you only have one SSH key is should 'just work'. If you have more
than one you'll need to do some additional configuration via
~/.ssh/config

Did you remember to copy across your SSH private key from you old
computer to your newer one? If not, you can either copy it now or create
a new one and replace the public SSH key stored at id.a.o

HTH,

Mark


> 
> —peter
> 
> On 9/13/17, 3:15 PM, "Mark Thomas"  wrote:
> 
>> On 13/09/17 19:27, Peter Ent wrote:
>>> Thanks, Mark.
>>>
>>> I think I've done all the right stuff. As I started to do it, I began to
>>> remember doing it once before for SSH. I've been waiting awhile and
>>> still
>>> get permission denied, so I'll just keep waiting. I'm pretty sure I sent
>>> my key to a public key server. I'll go out for coffee and I hope it
>>> works
>>> when I get back.
>>
>> That sounds like you might be mixing up OpenPGP release keys and SSH
>> keys. Anyway...
>>
>> I've checked your LDAP record and you do have a public SSH key
>> configured. If it doesn't work when you try again let me know the time
>> (UTC) and IP address (send it privately if you have privacy concerns)
>> and I'll check the logs.
>>
>> Mark
>>
>>
>>>
>>> —peter
>>>
>>> On 9/13/17, 1:22 PM, "Mark Thomas"  wrote:
>>>
>>>> On 13/09/2017 18:05, Peter Ent wrote:
>>>>> I get permission denied (public key). I remember having to set up
>>>>> something for the old people site (I think) and have been trying to
>>>>> hunt
>>>>> down the instructions.
>>>>
>>>> You should be able to set up your key through id.apache.org
>>>>
>>>> You then need to allow enough time (I think it is about an hour) for
>>>> the
>>>> public key to sync to the servers you have access to. Then you should
>>>> be
>>>> able to sftp to home.a.o.
>>>>
>>>> Mark
>>>>
>>>>
>>>>>
>>>>> ‹peter
>>>>>
>>>>> On 9/13/17, 12:49 PM, "Alex Harui"  wrote:
>>>>>
>>>>>> Should just be:
>>>>>>  sftp home.apache.org
>>>>>>
>>>>>> Hope you remember your passphrase.
>>>>>>
>>>>>> -Alex
>>>>>>
>>>>>> On 9/13/17, 9:16 AM, "Peter Ent"  wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Does anyone have the instructions on how to set up access to your
>>>>>>> home.apache.org space? I've looked on the apache.org site and all I
>>>>>>> can
>>>>>>> find are instructions about the old people.apache.org. I guess I
>>>>>>> haven't
>>>>>>> accessed my home.apache.org since I set up my newer computer.
>>>>>>>
>>>>>>> I'm going to update my ASDocs info to point to our FlexJS ASDocs app
>>>>>>> page
>>>>>>> since Google is pointing to my old ASDoc and it needs to be more
>>>>>>> current.
>>>>>>>
>>>>>>> Thanks.
>>>>>>> Peter
>>>>>>
>>>>>
>>>>
>>>
>>
> 

Re: [DISCUSS] Building the brand for Royale

[Mark Thomas]

On 20/09/17 19:08, Alex Harui wrote:
> AIUI, we are going to build at least three sites:
> 
> 1) Royale.apache.org is a requirement.  And I think we have to use ASF CMS
> and whatever markup language it requires unless we generate html and js
> elsewhere and copy it in, which would be the case for any FlexJS/Royale
> apps.

No need to use the CMS.

Any system the project wants that results in a bunch of static files in
the right place in svn or git is fine.

Mark

> 
> 2) https://github.com/apache/royale.  Folks are going to land here quite
> often.  My understanding is that GH Pages can affect what folks land on.
> It doesn't have to be the standard page with the README.MD and a folder of
> files.  But I could be wrong about that.  Many GH projects mention a
> website on the standard landing page.  I don't know if we can make that
> something other than royale.apache.org.  We'll find out if we get to use
> GitBox.  If we can't I don't think we get to use GH Pages or control the
> landing page.
> 
> 3) Facebook/Royale.
> 
> The development of these 3 sites must be done the Apache Way and I suspect
> that there will be plenty of discussion on it.  I don't want to put stones
> in the road in front of Carlos.  I think he should go and build what he
> wants to build, host it on his hardware and show it to us.  Then we can
> ask for the minimum tweaks required to get approval as royale.xx.  If we
> can't agree on how to do that, Carlos can always publish it as
> royale.codeoscopic.com.  Domains of that pattern are supposedly easier to
> approve.
> 
> Also, we don't need to decide on royale.xx vs royale.yy if we can afford
> to get both.
> 
> Does that sound reasonable?
> 
> -Alex
> 
> On 9/20/17, 10:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
> 
>> Hi Alex,
>>
>> I was not thinking in promote Codeoscopic, but if I can put a link in some
>> place, it would be ok.
>> In the end Codeoscopic is a product company and its customers are
>> insurance
>> companies, so there's no much interest for me in that regard or at least I
>> can see a logic relation since we don't sell "flex services" anymore.
>>
>> 2017-09-20 19:49 GMT+02:00 Alex Harui :
>>
>>> True, that's a lot of rules.  Part of that is because we owe our hosts
>>> (the ASF) some "props".
>>>
>>> But that may be why it is easier for us to approve Carlos to do what we
>>> wants outside the project.  It will free him most of these rules.  AIUI,
>>> the only rules would then be:
>>> 1) make sure Apache is mentioned often enough
>>> 2) make sure there are enough links back to royale.apache.org
>>> 3) make sure he doesn't promote his company more than the project. (I
>>> think he is allowed to say the site is hosted by his company and some
>>> promotional info).
>>>
>>> Thoughts?
>>> -Alex
>>>
>>> On 9/20/17, 10:36 AM, "Erik de Bruin"  wrote:
>>>
> I think if we grab a domain and donate it to the ASF, that it can't
>>> be
> hosted on non-ASF hardware.  That would need to be verified.
> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> third-party domain under Carlos's control.  I think that's allowed.
>>> The
> policy [1] says that "in general" it is NOT allowed, but "in general"
> implies it isn't a hard and fast rule.
>
> IMO, things under the PMC's control have certain obligations.  It
>>> has to
> be sustainable by "anyone".  How many folks know how to edit
>>> WordPress
> themes?  I don't.  I always choose one of their default themes.  It
> might
> have to be hosted or host-able by Apache Infra, and I don't know if
>>> they
> are ok with WordPress.
>

 That is an awful lot of rules that seem to work against the creativity
>>> of
 the project...

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I.
 https://na01.safelinks.protection.outlook.com/?url=
>>>
>>> https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data
>>> =02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b34438794aed2c1
>>> 78decee1%7C0%7C0%7C636415267698995147&sdata=NQ%2BjrPGhT7zQtWVbo0nStXLzQit
>>> 19Ny3Y1JOczHt3hs%3D&reserved=0&data=
 02%7C01%7C%7Ceb4bfa47a0da41fe511b08d5004e3980%
>>> 7Cfa7b1b5a7b34438794aed2c178
 decee1%7C0%7C0%7C636415258339861760&sdata=K%
>>> 2FKg9eeTxMwS%2BsxE7xGAXU6KlhtQ
 sQNLKnv3gG81OKs%3D&reserved=0
>>>
>>>
>>
>>
>> -- 
>>
>> > scopic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636415267698995147&sdata=LBwi00UXVvi%2F7U
>> gwYDmrS2QKANVigbic9dJpsaQ31Xw%3D&reserved=0>
>>
>> Carlos Rovira
>>
>> Director General
>>
>> M: +34 607 22 60 05
>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>> copic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b3
>