flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <dave2w...@comcast.net>
Subject Re: [DISCUSS] Building the brand for Royale
Date Wed, 20 Sep 2017 17:51:44 GMT
Hi -

Wordpress on apache infrastructure would require following every Wordpress release which can
be more frequently than monthly. The PMC would need to provide the manpower to do this. We
would also need to be careful about plugins which can also have security issues.

I say if we can eat our Royale then that would be best. If we go with Git it can be there
and then we can refer to it from the official ask site and/or merge the two under standard
ASF CMS.

Regards,
Dave

> On Sep 20, 2017, at 1:36 PM, OmPrakash Muppirala <bigosmallm@gmail.com> wrote:
> 
> I would stay away from WordPress just because of all the security issues
> and maintenance required.
> 
> Github pages should be a better place.
> 
> Thanks,
> Om
> 
> On Sep 20, 2017 10:26 AM, "Alex Harui" <aharui@adobe.com.invalid> wrote:
> 
>> Hmm.
>> 
>> 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.
>> 
>> Personally, I want to be able to stick FlexJS apps in our web presence.
>> Honestly, I'd actually like to see our entire web presence be built in
>> FlexJS.  It would truly be "eating our own dog food".  Yes, I know that
>> mostly static pages aren't a great match for FlexJS/Royale, but in the
>> end, shouldn't all of our web presence be dynamic?
>> 
>> My 2 cents,
>> -Alex
>> 
>> [1] http://www.apache.org/foundation/marks/domains.html
>> 
>> On 9/20/17, 10:02 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
>> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
>> wrote:
>> 
>>> Hi Alex,
>>> 
>>> that's my bet. To make a good website I proposed to make it in Wordpress
>>> since is what I have some expertise in that field (If I'm the person in
>>> charge to make it happen). All the team can as well have an account in the
>>> WP dash board to be able to post and share content in a easy way.
>>> 
>>> WP will gave as the landing and some pages that would be useful for
>>> convenience. But I think, as well, to link directly to the resources in
>>> the
>>> apache infrastructure in the main menu of the site just as we do now
>>> (code,
>>> GitHub, wiki, links to our mailing lists, releases, binaries, and so on)
>>> 
>>> For domain registration I'd prefer .io since is very popular today, but
>>> .as
>>> seems ok for me as well.
>>> I think Erik proposed to register the domain for us, so I think is ok for
>>> me that he makes the registration. Maybe we could do it as soon as the
>>> board approve the new TLP and name.
>>> 
>>> I can host the site in CO servers with the rest of our websites, to
>>> support
>>> as well this change and initiative. Again I'll be waiting for board
>>> approval to start working. I'm assuming here that you guys trust me to
>>> make
>>> this website and branding work, of course.
>>> 
>>> So maybe we could make a thread to select from Royale.io and Royale.as,
>>> and
>>> of course if price for .io is very high we could go with .as if it's more
>>> low.
>>> 
>>> 
>>> 
>>> 
>>> 2017-09-20 18:44 GMT+02:00 Alex Harui <aharui@adobe.com.invalid>:
>>> 
>>>> Hi Carlos,
>>>> 
>>>> We can go grab some royale.<xxx> domains.  Apache will have some rules
>>>> about what can go on them.  At the worst it will have to be a straight
>>>> redirect to royale.apache.org, but I think we might be able to have at
>>>> least a landing page.  I think the goal is that Apache wants strong
>>>> association with a project's web presence.  Even on a royale.foo landing
>>>> page, the first mention of Royale probably has to be "Apache Royale".
>>>> 
>>>> But also, I am hopeful we will be using GitBox and thus GitHub will be
>>>> our
>>>> hub of activity.  And I think we should use GitHub pages and build a
>>>> solid
>>>> web presence there, again within Apache's rules.
>>>> 
>>>> Royale.io is for sale.  We could ask what the price is.
>>>> Royale.as appears to be unregistered.
>>>> 
>>>> My 2 cents,
>>>> -Alex
>>>> 
>>>> On 9/20/17, 8:31 AM, "carlos.rovira@gmail.com on behalf of Carlos
>>>> Rovira"
>>>> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
>>>> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> as Alex and Dave said, we should wait for board approval.
>>>>> 
>>>>> @Harbs, I was using "xxx" to refer to "whatever domain extension out
>>>> there
>>>>> that would fit for us" ;)
>>>>> 
>>>>> @Dave, I understand that we should use the apache domain for the
>>>> service
>>>>> apache provide (i.e: store code, mailing list, releases...), but as
>>>> many
>>>>> other projects out there, I suppose we should as well have an external
>>>>> tools or domains that serve our purpose. In the same way we have  some
>>>>> external servers or tools actually.
>>>>> For example, we could have a cool name domain that points to a website
>>>> and
>>>>> there refer to the apache resources. If that option should go against
>>>>> apache rules, that would be strange for me, and would certainly be
>>>>> hopeless
>>>>> to work in and organization with such limitations.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> 
>>>>> 2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic <tomislav@svemir.net>:
>>>>> 
>>>>>> Guys, congrats for selecting the new project name.
>>>>>> Still not sure how Royale resonates with me, but like it much more
>>>> than
>>>>>> the 1st runner up.
>>>>>> Non English speakers would pretty often confuse beads with beds and
>>>> job
>>>>>> ads might sound strange.
>>>>>> Just imagine:
>>>>>> "Looking for an amazing Beads expert to join our team."
>>>>>> :)
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Tom
>>>>>> 
>>>>>> 
>>>>>> On 20.9.2017. 15:45, Dave Fisher wrote:
>>>>>> 
>>>>>>> As an Apache project the domain would be:
>>>>>>> 
>>>>>>> Royale.apache.org
>>>>>>> 
>>>>>>> I can write a long discussion about policy later but there are
>>>> reasons,
>>>>>>> requirements, approvals around use of other domains.
>>>>>>> 
>>>>>>> I know everyone is enthusiastic but let's get approved by the
board
>>>>>>> first.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> Dave
>>>>>>> 
>>>>>>> Sent from my iPhone
>>>>>>> 
>>>>>>> On Sep 20, 2017, at 6:33 AM, Erik de Bruin <erik@ixsoftware.nl>
>>>> wrote:
>>>>>>> 
>>>>>>> * Domain: We must find a good and simple domain for Royale. I
think
>>>> if
>>>>>>> we
>>>>>>>>> can find something short like "royale.XXX" would be great
over
>>>>>>>>> "apacheroyale.XXX".
>>>>>>>>> 
>>>>>>>>> .com, .org, .net, .io etc. all seem to be either in use
or
>>>> squatted
>>>>>>>> upon.
>>>>>>>> Am I forgetting memorable TLP extensions? I assume we don't
want
>>>>>>>> anything
>>>>>>>> like 'royale.foundation' or any fancy extensions like that,
right?
>>>>>>>> 
>>>>>>>> Are we considering extended names, like 'royaleframework'
as well?
>>>>>>>> 
>>>>>>>> I can register anything we decide and sponsor until a foundation
>>>> takes
>>>>>>>> over
>>>>>>>> and then transfer the domain.
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> 
>>>>>>>> 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%7C7a1bad633d124870d72508d5004968f3%
>> 7Cfa7b1b5a7b34438794aed2c1
>>>> 78decee1%7C0%7C0%7C636415237653639659&sdata=
>> J8Fnfl9NYUdUQgb2JolOElSQf3AmV
>>>> dxhNX8TeGpE1II%3D&reserved=0&da
>>>>>>>> ta=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
>>>> ad9e%7Cfa7b1b5a7b34438794ae
>>>>>>>> d2c178decee1%7C0%7C0%7C636415182976392829&sdata=
>>>> LDQFlmzgCBkY3NyhB%2BZ1W
>>>>>>>> bJnC6FcmPRRXhB7Ltggre8%3D&reserved=0
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 
>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>> http%3A%2F%2Fwww.codeo
>>>>> scopic.com&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
>>>> ad9e%7Cfa7b1b5a7b
>>>>> 34438794aed2c178decee1%7C0%7C0%7C636415182976392829&
>>>> sdata=snzdFt3cDT4GcWGa
>>>>> NJF3dFIfdKedU5jF%2FBM1XqrkQHY%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%7Cab05fef4543644f67e2c08d5003c
>>>> ad9e%7Cfa7b1b5a7b3
>>>>> 4438794aed2c178decee1%7C0%7C0%7C636415182976392829&
>>>> sdata=snzdFt3cDT4GcWGaN
>>>>> JF3dFIfdKedU5jF%2FBM1XqrkQHY%3D&reserved=0
>>>>> 
>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>>> http%3A%2F%2Fwww.avant2
>>>>> .es&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
>>>> ad9e%7Cfa7b1b5a7b3443879
>>>>> 4aed2c178decee1%7C0%7C0%7C636415182976392829&sdata=
>>>> 8SXVcRe3E%2FLVCSIODbbnL
>>>>> wsN3AIsG4djE9F0VhpX8H0%3D&reserved=0
>>>>> 
>>>>> 
>>>>> Conocenos en 1 minuto!
>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>> https%3A%2F%2Fyoutu.be
>>>>> %2FP2IEAYDG5HU&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
>>>> ad9e%7Cfa7b1b
>>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636415182976392829&
>>>> sdata=%2FWlOcenx8I
>>>>> qTu2PYyD%2FBiChaLHKstZC0eLlmb5gpmng%3D&reserved=0>
>>>>> 
>>>>> 
>>>>> Este mensaje se dirige exclusivamente a su destinatario y puede
>>>> contener
>>>>> información privilegiada o confidencial. Si ha recibido este mensaje
>>>> por
>>>>> error, le rogamos que nos lo comunique inmediatamente por esta misma
>>>> vía y
>>>>> proceda a su destrucción.
>>>>> 
>>>>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>>>>> comunicamos
>>>>> que sus datos forman parte de un fichero cuyo responsable es
>>>> CODEOSCOPIC
>>>>> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>>>>> servicio o información solicitados, teniendo usted derecho de acceso,
>>>>> rectificación, cancelación y oposición de sus datos dirigiéndose
a
>>>>> nuestras
>>>>> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>>>>> necesaria.
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> 
>>> <https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.codeo
>>> scopic.com&data=02%7C01%7C%7C7a1bad633d124870d72508d50049
>> 68f3%7Cfa7b1b5a7b
>>> 34438794aed2c178decee1%7C0%7C0%7C636415237653639659&
>> sdata=3TVBQ1FBx7N0zaeD
>>> gNrxg80zei0XQWTnUtNwJqD5xps%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%7C7a1bad633d124870d72508d50049
>> 68f3%7Cfa7b1b5a7b3
>>> 4438794aed2c178decee1%7C0%7C0%7C636415237653639659&
>> sdata=3TVBQ1FBx7N0zaeDg
>>> Nrxg80zei0XQWTnUtNwJqD5xps%3D&reserved=0
>>> 
>>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.avant2
>>> .es&data=02%7C01%7C%7C7a1bad633d124870d72508d50049
>> 68f3%7Cfa7b1b5a7b3443879
>>> 4aed2c178decee1%7C0%7C0%7C636415237653639659&sdata=
>> g8k6t3Kn7Hv1VhuuhhIK0xV
>>> QTvVgOh4WcNU0LiAL1S0%3D&reserved=0
>>> 
>>> 
>>> Conocenos en 1 minuto!
>>> <https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fyoutu.be
>>> %2FP2IEAYDG5HU&data=02%7C01%7C%7C7a1bad633d124870d72508d50049
>> 68f3%7Cfa7b1b
>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636415237653639659&
>> sdata=OZzBDygty6bK
>>> flTfL4%2Bfr6Bt5huzu%2BX6QxrJFc0hOEw%3D&reserved=0>
>>> 
>>> 
>>> Este mensaje se dirige exclusivamente a su destinatario y puede contener
>>> información privilegiada o confidencial. Si ha recibido este mensaje por
>>> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>>> proceda a su destrucción.
>>> 
>>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>>> comunicamos
>>> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>>> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>>> servicio o información solicitados, teniendo usted derecho de acceso,
>>> rectificación, cancelación y oposición de sus datos dirigiéndose a
>>> nuestras
>>> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>>> necesaria.
>> 
>> 


Mime
View raw message