Hi Alex, I think we provide all what they ask us to provide. We just only need the text for source code bundles to put in source code page, and we can add a link for source code and GitHub pages in download page. So we have in place all the things they ask. And we use our own presentation since we pursue and objective to compete with project like React or Angular. So I don't see any reason of weight to make us start wasting time making changes that, IMO will end having a worst site that the current one.
the focus in on source code? ok, we'll soon have more info on how to get source code. the focus is to get commiters? ok, we have in all pages a call to arms banner that ask people to join and link to mailing list. Moreover we have a safe button (top - right corner) with a icon of user+ that again as people to join us with a big button to join mailing list. 2018-01-30 18:10 GMT+01:00 Alex Harui <[email protected]>: > Hi Carlos, > > We are under the rulings of the Apache Brand committee. I've seen them > request changes to other project sites in order to conform to certain > branding standards for consistency. It appears that whatever is on > project.a.o needs to attract new committers and emphasize source code. > So, whatever is on royale.a.o is not fully our decision. If someone from > Branding notices something a couple of months from now and doesn't like > it, we'll have to change it. > > Apache Open Office has a user-facing domain and site. We weren't allowed > to have one because the Branding folks only wanted to allow pre-existing > domains, but IMO, they did not come up with a reason why allowing other > projects to have user-facing domains would harm the ASF. > > -Alex > > On 1/30/18, 9:02 AM, "[email protected] on behalf of Carlos Rovira" > <[email protected] on behalf of [email protected]> wrote: > > >Hi Alex, > > > >I have to say that I'd not like that direction at all. I think that after > >many efforts for our part, we are getting a good organization and we have > >the opportunity to compete with other technologies if we get some other > >things we really need. Instead, if we go down that route we'll be > >providing > >something that people coming could see it as something from the old > >school. > >We must honor what people coming to us expect from us while compiling with > >what Apache want for s to do. I think now we are proving both in a good > >mix > >that is our brand. > > > >IMHO, we need work in the Royale docs and we'll be with almost all the > >public pieces for our users set. Then as I always say we need a good > >working royale UI set. > > > >I think although we are an Apache project we have our own personality and > >while is great to copy others, we only need to copy things that really fit > >us. But I think body and old organization only because many apache project > >make in that way without thinking in what our project really demands will > >be not good for our project. > > > >But that's only my opinion > > > >Thanks > > > >Carlos > > > > > > > > > > > > > >2018-01-30 17:46 GMT+01:00 Alex Harui <[email protected]>: > > > >> We could appeal to have royalesdk.org allowed as our user-facing site. > >> IMO, VP Branding never gave us a really good reason why it would be bad > >> for Apache to allow it. Every Apache project site I looked at is geared > >> towards committers as well as users. I don't think we can avoid > >>appealing > >> to committers on royale.a.o. > >> > >> My 2 cents, > >> -Alex > >> > >> On 1/30/18, 8:40 AM, "[email protected] on behalf of Carlos > >>Rovira" > >> <[email protected] on behalf of [email protected]> wrote: > >> > >> >Hi Alex, > >> > > >> >We are providing all of this. We can discuss the best organization, I > >> >think > >> >is right to add a links in the Downloads page to Source Code and > >>Github so > >> >people interested could go directly to that point. I think that while > >>we > >> >are providing all what Apache require from us we as well are organizing > >> >and > >> >presenting in a more modern way and more near to what people expect and > >> >what others are doing. > >> > > >> >For two sites, I think we already have it and are ok with apache rules. > >> >Remember that royalesdk.org was not allowed by apache brand and legal. > >>So > >> >for me royale.a.o is the marketing site and Github (where code > >>resides) > >> >is > >> >the "code" site and something directly prepared for people that wants > >>the > >> >code. > >> > > >> >Just my 2 ctnms > >> > > >> >2018-01-30 17:16 GMT+01:00 Alex Harui <[email protected]>: > >> > > >> >> Hi Carlos, > >> >> > >> >> It may not be required by policy, but the first 5 Apache project > >> >>websites > >> >> I went to all had download links for the source package on their > >> >>download > >> >> page, and any "Source" page pointed to the project's repos. > >> >> > >> >> Apache's only official products are source code releases, not binary > >> >> artifacts. I think we have to list the source package on the > >>downloads > >> >> page. I did see that one project listed the binaries before the > >>source > >> >>so > >> >> maybe we can do that. We want to direct people to our repos as well, > >> >>but > >> >> they are not releases. > >> >> > >> >> I think we have the option of having our download link redirect to > >>the > >> >> GitHub releases page if that makes sense. > >> >> > >> >> And as Piotr pointed out, there are 3 repos bundled into each release > >> >> artifact so the "Source" page should reference all 3 repos and the > >> >> "Downloads" reference the package that contains all 3 repos. > >> >> > >> >> Again, this is why I keep thinking we need a separate > >> >> user-facing/marketing site and domain that is distinct from > >>royale.a.o > >> >> which is more tuned to attracting new committers. > >> >> > >> >> My 2 cents, > >> >> -Alex > >> >> > >> >> > >> >> On 1/30/18, 2:49 AM, "[email protected] on behalf of Carlos > >> >>Rovira" > >> >> <[email protected] on behalf of [email protected]> > wrote: > >> >> > >> >> >No, I'm talking about this page: > >> >> >https://na01.safelinks.protection.outlook.com/?url= > >> >> http%3A%2F%2Froyale.apa > >> >> >che.org%2Fsource-code%2F&data=02%7C01%7Caharui%40adobe.com > >> >> %7Cafe5673656ea4 > >> >> >92d967c08d567d00eff%7Cfa7b1b5a7b34438794aed2c178de > >> >> cee1%7C0%7C0%7C636529065 > >> >> >657298785&sdata=v3PxmC3CwRXMLbJgHZVj8HjpqyG% > >> >> 2BX%2Bno%2B7OrTixvYLs%3D&reser > >> >> >ved=0 > >> >> >(link is the footer since its priority is low) > >> >> > > >> >> >For all: I updated as well the Home in the pre-production with the > >>NPM > >> >> >info > >> >> >so you can check. I added the "NPM" link to footer menu as well, as > >>it > >> >>was > >> >> >some time ago before first website release. > >> >> > > >> >> >2018-01-30 11:34 GMT+01:00 Piotr Zarzycki > >><[email protected]>: > >> >> > > >> >> >> Carlos, > >> >> >> > >> >> >> Are you refering by source code - specific TAG in the repository > >>? If > >> >> >>you > >> >> >> wanted to point to the sources you need to point sources for the > >>all > >> >> >>three > >> >> >> repository. Point to the 0.9.0 released tag. > >> >> >> > >> >> >> But what is for on the Download page link to the sources ? Just to > >> >> >>address > >> >> >> other type of users ? If they want to come and help us we have > >>GitHub > >> >> >>link > >> >> >> on our page. > >> >> >> > >> >> >> Thanks, Piotr > >> >> >> > >> >> >> 2018-01-30 11:20 GMT+01:00 Carlos Rovira > >><[email protected]>: > >> >> >> > >> >> >> > Hi Alex, > >> >> >> > > >> >> >> > Thinking about this and I think is not right. We define > >>Downloads > >> >>page > >> >> >> with > >> >> >> > the following phrase: > >> >> >> > > >> >> >> > "Here you can find the binary distributions of Apache Royale SDK > >> >>for > >> >> >>you > >> >> >> to > >> >> >> > download." > >> >> >> > > >> >> >> > the source is in the "source code" page and in the Github link. > >> >> >> > > >> >> >> > I think that's the right way, since we provide the separated > >>spaces > >> >> >>to do > >> >> >> > that, and make it more clear for users coming > >> >> >> > (as I mentioned before, we should have two basic types of users, > >> >> >>people > >> >> >> > wanting to get the binaries to go fast without worry about more, > >> >>and > >> >> >> > people more advanced, first will go to downloads, and second > >>will > >> >>go > >> >> >>to > >> >> >> > source code page or directly to gihub link. > >> >> >> > > >> >> >> > But, We should change the source code page with the links to the > >> >> >>source > >> >> >> > code bundles. > >> >> >> > @Andrew can you provide a text and right links to source code > >>so I > >> >>can > >> >> >> make > >> >> >> > the same and put in Source code page? > >> >> >> > > >> >> >> > thanks > >> >> >> > > >> >> >> > > >> >> >> > 2018-01-30 7:23 GMT+01:00 Alex Harui <[email protected] > >: > >> >> >> > > >> >> >> > > IMO, we need to list the source package first. Apache is > >>about > >> >> >>source. > >> >> >> > > > >> >> >> > > This is why I still think about a marketing site and domain > >>that > >> >>is > >> >> >> more > >> >> >> > > like the other JS frameworks out there. > >> >> >> > > > >> >> >> > > > >> >> >> > > >> >> >> > -- > >> >> >> > Carlos Rovira > >> >> >> > > >> >> >>https://na01.safelinks.protection.outlook.com/?url= > >> >> http%3A%2F%2Fabout.me% > >> >> >>2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com% > >> >> 7Cafe5673656ea492d967c08 > >> >> >>d567d00eff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >> >> 7C63652906565729878 > >> >> >>5&sdata=GQobmSWy%2BnwN9rCu0Bu%2BGi77vSqDAikjTOkF11%2Byc%2FA% > >> >> 3D&reserved=0 > >> >> >> > > >> >> >> > >> >> >> > >> >> >> > >> >> >> -- > >> >> >> > >> >> >> Piotr Zarzycki > >> >> >> > >> >> >> Patreon: > >> >> >>*https://na01.safelinks.protection.outlook.com/?url= > >> >> https%3A%2F%2Fwww.pat > >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com > >> >> %7Cafe5673656ea > >> >> >>492d967c08d567d00eff%7Cfa7b1b5a7b34438794aed2c178de > >> >> cee1%7C0%7C0%7C6365290 > >> >> >>65657298785&sdata=hGxX4SM9Ob4E5FSSOWnKuR50L3aBmH > >> >> w7u76s4tl9GxQ%3D&reserved > >> >> >>=0 > >> >> >> > >> >> >><https://na01.safelinks.protection.outlook.com/?url= > >> >> https%3A%2F%2Fwww.pat > >> >> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com > >> >> %7Cafe5673656ea > >> >> >>492d967c08d567d00eff%7Cfa7b1b5a7b34438794aed2c178de > >> >> cee1%7C0%7C0%7C6365290 > >> >> >>65657298785&sdata=hGxX4SM9Ob4E5FSSOWnKuR50L3aBmH > >> >> w7u76s4tl9GxQ%3D&reserved > >> >> >>=0>* > >> >> >> > >> >> > > >> >> > > >> >> > > >> >> >-- > >> >> >Carlos Rovira > >> >> >https://na01.safelinks.protection.outlook.com/?url= > >> >> http%3A%2F%2Fabout.me%2 > >> >> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com% > >> >> 7Cafe5673656ea492d967c08d5 > >> >> >67d00eff%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >> >> 7C636529065657298785&s > >> >> > >>>data=GQobmSWy%2BnwN9rCu0Bu%2BGi77vSqDAikjTOkF11%2Byc%2FA%3D&reserved=0 > >> >> > >> >> > >> > > >> > > >> >-- > >> >Carlos Rovira > >> >https://na01.safelinks.protection.outlook.com/?url= > >> http%3A%2F%2Fabout.me%2 > >> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com% > >> 7C7806908e47a44d95088408d5 > >> >680037e6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >> 7C636529272504602759&s > >> >data=eaJ2e0K97gkmn0txGt2wrCsuEd6y%2FgzzmcdBWKb3a8g%3D&reserved=0 > >> > >> > > > > > >-- > >Carlos Rovira > >https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fabout.me%2 > >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com% > 7C26c3892e8cf148fb8f8508d5 > >68034f2d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > 7C636529285783612643&s > >data=bKDasniFGSRfUmdbkxBHK8UzVTuqJuzo0jxKFVsyz1g%3D&reserved=0 > > -- Carlos Rovira http://about.me/carlosrovira
