Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

OK, please remove it from the release/0.9.0 branch.

Thanks,
-Alex

On 1/16/18, 10:06 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>On Jan 16, 2018 8:47 PM, "Alex Harui"  wrote:
>
>
>
>On 1/16/18, 1:13 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
> wrote:
>>
>>+1 to exclude the MDL examples from this release.  Let's find a good way
>>to
>>fix the IP issues in our next release.
>
>Speaking of removing examples...  What's up with AngularExample?  It
>doesn't build in Maven and there is no Ant build script for it.  Should we
>make it work or skip around it or remove it?
>
>
>I think that was just an experiment.  We can in fact delete it from the
>codebase.
>
>I will get to it unless anyone else gets to it before me.
>
>Thanks,
>Om
>
>
>-Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[OmPrakash Muppirala]

On Jan 16, 2018 8:47 PM, "Alex Harui"  wrote:



On 1/16/18, 1:13 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:
>
>+1 to exclude the MDL examples from this release.  Let's find a good way
>to
>fix the IP issues in our next release.

Speaking of removing examples...  What's up with AngularExample?  It
doesn't build in Maven and there is no Ant build script for it.  Should we
make it work or skip around it or remove it?


I think that was just an experiment.  We can in fact delete it from the
codebase.

I will get to it unless anyone else gets to it before me.

Thanks,
Om


-Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Dave Fisher]

Hi Justin,

We have it now and are doing the correct thing in a natural way. An Apache 
Member who was on my first PMC has explained the situation well. He calls it 
“cups and saucers” when we discovered a single GPL file had been in a few 
releases we removed it. It is best effort and sometimes things spill.

Shine the light forward.

Regards,
Dave

Sent from my iPhone

> On Jan 16, 2018, at 9:16 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Royale is not going to operate like Flex.  We want to be more responsive
>> to our users.  So instead of conducting detailed searches for IP issues at
>> release time, they should be done at commit time or at other times.
> 
> The issue has been brought up before so is a known issue. (See that 
> discussion thread). Given that discussion I would of assumed that committers 
> wouldn't check in plain text CC-BY-SA licensed content. But I guess people 
> forget about it, I had even forgotten about that thread. If you where 
> watching the commits it would be very easy to miss the file(s) in question as 
> they also incorrectly had an ASF headers on them. But any PMC member or 
> committer could of noticed this, the fact that no one did until now probably 
> indicates how difficult it was to find. Perhaps it would be better to deal 
> with licensing issues when they are raised or soon after - especially when a 
> 3rd party doesn’t respond in a timely way?
> 
> BTW the legal JIRA about CC-SA content is here [1] not sure if you managed to 
> find that when looking at the issue.
> 
> Thanks,
> Justin
> 
> 1. https://issues.apache.org/jira/browse/LEGAL-167

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Justin Mclean]

Hi,

> Can you provide a link to that discussion?

Sure here [1] As discussed in that thread I asked them to clarity what license 
the files are under [2] (way back in October 2016) and got no response. Other 
people since then have asked the same question (including Om yesterday) and not 
got any clear answers.

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/aa0646f937c65d66404f2a398733f7354225b5eb64e299a9d65e5139@%3Cdev.flex.apache.org%3E
2. https://github.com/google/material-design-lite/issues/4850

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

On 1/16/18, 1:13 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:
>
>+1 to exclude the MDL examples from this release.  Let's find a good way
>to
>fix the IP issues in our next release.

Speaking of removing examples...  What's up with AngularExample?  It
doesn't build in Maven and there is no Ant build script for it.  Should we
make it work or skip around it or remove it?

-Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

On 1/16/18, 3:32 PM, "Justin Mclean"  wrote:

>
>Yes is is unfortunate that the PMC failed to notice this issue. The issue
>had actually been brought up before the MDL code was checked in to a repo
>and there was some discussion about the issues but it wasn’t fully
>resolved. It’s unfortunate, that we forgot about that discussion, and
>that it slipped between the cracks.

Can you provide a link to that discussion?
>
>If the last call process had been followed it probably would of come up
>then rather than with the first release candidate but I’m not sure that
>would of saved any time.

Royale is not going to operate like Flex.  We want to be more responsive
to our users.  So instead of conducting detailed searches for IP issues at
release time, they should be done at commit time or at other times.

-Alex

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Justin Mclean]

Hi,

>  After Justin pointed out that there is CSS under CC-BY-4.0 in 
> MDLBlogExample, I took a closer look
> and realized that really, I think these two examples are just ports of
> Google's examples and thus should remain under Google's copyright

Yep I agree with that.

> There is also a thread open on legal-discuss to verify that CSS is
> considered to be "media" and not "source code".  If it is "source code"
> then we have to treat the example as Category X and remove the CSS and
> text from the repos and releases.

Hopefully some-one on legal discuss with reply and it will be resolved quickly. 

> It is, as always, unfortunate that these issues are not discovered when these 
> files are first committed to
> the repo as has been recommended by more than one experienced Apache
> member instead of during the release process.

Yes is is unfortunate that the PMC failed to notice this issue. The issue had 
actually been brought up before the MDL code was checked in to a repo and there 
was some discussion about the issues but it wasn’t fully resolved. It’s 
unfortunate, that we forgot about that discussion, and that it slipped between 
the cracks.

If the last call process had been followed it probably would of come up then 
rather than with the first release candidate but I’m not sure that would of 
saved any time.

Thanks,
Justin

Re: [Royale] ICollectionView

[Peter Ent]

Now that I've checked in TreeGrid and my changes to DataGrid (not much) I
can look into this with you.

I created an interface, IDataGridColumn so that TreeGrid and DataGrid can
share a lot of the same code, although the two are separate at the moment.
I want TreeGrid to be able to use most of the same beads DataGrid does or
will have available to it in the future. The styling should be the same,
too.

‹peter

On 1/12/18, 6:35 PM, "piotrz"  wrote:

>Peter,
>
>I see one more issue. In DataGridColumnList we have following line:
>"typeNames = "DataGridColumnList";". After compilation each div which
>represents DataGridColumnList have class="List".
>
>yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Flist_each_datagridcolum
>nlist.png=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536
>ef%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=j
>avj1cU%2BeNSJvY%2FwHzRtOQDDCGJKSNEUP2QCWWWZpug%3D=0>
>
>This gives us some borders because default List style has css which is
>doing
>for us border etc. [1]
>
>yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Fborder_grid.png=02
>%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636513969542441416=D%2BVI5eYn%2FTXqG1
>DDvfS5GSfGctc0JptwQZ%2BHNG1hT3s%3D=0>
>
>However if I add to the column some style as we are doing it in
>DataGridExample for as second grid, we are ending up with something weird:
>
>yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Fno_border_grid.png
>=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%7Cfa7b1b5a7
>b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=nxtvREgcMz6kgZ0
>wwZV5bmUbkhvAuckEnUETYmFpgrs%3D=0>
>
>There is no border, cause DataGridColumnList style doesn't have it [2].
>
>I think we should:
>1) Set className = "DataGridColumnList" - here [3]
>2) Add those border to class "DataGridColumnList" in css
>
>What do you think ?
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>n27aYN=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=rOBo
>byCAc2i92Vmlu0eniYIkCaEtWRA%2BTox08IMOFhQ%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>N4S9PK=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=dQ0p
>WvYbK4Yn0RNJOKhZkKLbJzF4T54%2BSikI7bes1%2Bw%3D=0
>[3] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>8mF2Lr=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=mPbe
>gCAynPs5olJlaFDMFew5Bfb5mkP6lYIplrrqMd0%3D=0
>
>Thanks,
>Piotr
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F=02%7C01%7Cpent%40adobe.com%7Ca
>95e03b494894e2bf8ba08d55a1536ef%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0
>%7C636513969542441416=aLSGgQj1G%2F24n9AS97pDZgY59%2FycIbacHt0xUtKnCz
>c%3D=0

[Royale] TreeGrid

[Peter Ent]

Hi,

I've committed/pushed code that makes TreeGrid work. You can look at 
TreeExample to see how to use it. Basically, TreeGrid is just like DataGrid 
except it works with HierarchicalData. You define which column you want to hold 
the tree using a  description. For the other columns use 
. You can make any column be the Tree. You can even have 
multiple columns be trees, although I'm not sure if that makes any sense.

There is still some more work and styling to be done.

Regards,
Peter Ent
Adobe Systems/Apache Royale project

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[OmPrakash Muppirala]

On Tue, Jan 16, 2018 at 1:10 PM, Alex Harui 
wrote:

> Thanks Olaf!  Good to know that we don't have that restriction anymore.
>
> I'd like to get Piotr and Carlos's opinions about removing the MDL
> examples since they worked so hard on it.  I'm finishing up changing the
> file headers to reflect that these two examples are under Google's
> copyright and license.
>

+1 to exclude the MDL examples from this release.  Let's find a good way to
fix the IP issues in our next release.

Thanks,
Om


>
> -Alex
>
> On 1/16/18, 12:47 PM, "Olaf Krueger"  wrote:
>
> >Alex, it works [1]
> >
> >Regarding the MDL examples:
> >If there still IP and license issues left I would like to suggest to
> >remove
> >the affected examples from RC2 until we've resolved those problems. (I am
> >not sure if you already did it).
> >
> >Regarding the [y]/[n] questions during the approval:
> >During my tests, I've always entered [y] like a monkey with the focus on
> >testing the script.
> >What does this question about 'unexpected binaries' [2] mean and how
> >should
> >I check it?
> >
> >However, I am looking forward to the RC2 and, hopefully, a smooth release
> >process :-)
> >Thanks for your patient!
> >
> >Olaf
> >
> >
> >[1]
> >BUILD SUCCESSFUL
> >Total time: 34 minutes 42 seconds
> >
> >[2]
> >Check that there are no unexpected binaries.  Is it ok? (y, [n])
> >
> >
> >
> >
> >--
> >Sent from:
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-roy
> >ale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com
> %7
> >C066714a0a4d14f01d85808d55d22621f%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7
> >C0%7C636517324616345561=RtRvGTu1N2FPJSB7Y3np6Q%
> 2Fn%2BIZzYHCg5%2F%2Bi
> >b%2BUnN%2Bc%3D=0
>
>

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

Ah yes, that's a bug that has already been fixed for RC2.  It doesn't
happen when you first run a build in the source folder but now you are
running a build for the second time.  Try deleting the
apache-royale-0.9.0-src/royale-asjs/lib and
apache-royale-0.9.0-src/royale-asjs/js/lib folders and try again.

HTH,
-Alex

On 1/16/18, 11:32 AM, "Olaf Krueger"  wrote:

>Hi Alex,
>I've stumbled over the next issue [1].
>It seems to me that externc is not available?
>Any ideas?
>
>Thanks,
>Olaf
>
>[1]
>download:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs
>Expanding:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs
>\js\lib\google\closure-compiler\compiler.jar
>into C:\local\apache-royale\release-p
> 
>rocess\apache-royale-0.9.0-src\royale-typedefs\js\target\temp\externs
>Expanding:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-type
>defs\js\target\temp\externs\externs.zip
>into C:\local\apache-royale\release-proces
>  
>s\apache-royale-0.9.0-src\royale-typedefs\js\target\downloads
>Getting:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstorage.g
>oogleapis.com%2Fgoogle-code-archive-downloads%2Fv2%2Fcode.google.com%2Fclo
>sureidl%2Fsvg.js=02%7C01%7Caharui%40adobe.com%7Cb05e03660541413e1c060
>8d55d17e80f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63651727962185938
>3=GO4%2F8%2FcWVvk2MhohqRZL6FElZK5Bjq1r0TmZuzm7ETc%3D=0
>To:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-type
>defs\js\target\downloads\svg.js
>
>double-check-file:
>${env.ROYALE_DOWNLOAD_CACHE}
>Need file: ${still_no_file}
>
>get-from-cache-if-needed:
>
>fail-if-not-found:
>
>preprocess:
>
>externc:
>Fehler: Hauptklasse org.apache.royale.compiler.clients.EXTERNC konnte
>nicht
>gefunden oder geladen werden
>(Error: Main class org.apache.royale.compiler.clients.EXTERNC could not
>found or loaded)
>
>BUILD FAILED
>C:\local\apache-royale\release-process\ApproveRoyale.xml:721: The
>following
>error occurred while executing this line:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs
>\build.xml:1752:
>The following error occurred while executing this line:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs
>\build.xml:1824:
>The following error occurred while executing this line:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-type
>defs\build.xml:52:
>The following error occurred while executing this line:
>C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-type
>defs\js\build.xml:159:
>Java returned: 1
>
>Total time: 3 minutes 55 seconds
>
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7
>Cb05e03660541413e1c0608d55d17e80f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636517279621859383=lU5xfEz2pYOxJFga5IuIg9EApYaXK%2FuSG%2FLWj0zS
>SXM%3D=0

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Olaf Krueger]

Hi Alex,
I've stumbled over the next issue [1].
It seems to me that externc is not available?
Any ideas?

Thanks,
Olaf

[1]
download:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs
Expanding:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs\js\lib\google\closure-compiler\compiler.jar
into C:\local\apache-royale\release-p  
rocess\apache-royale-0.9.0-src\royale-typedefs\js\target\temp\externs
Expanding:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-typedefs\js\target\temp\externs\externs.zip
into C:\local\apache-royale\release-proces  

s\apache-royale-0.9.0-src\royale-typedefs\js\target\downloads
Getting:
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/closureidl/svg.js
To:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-typedefs\js\target\downloads\svg.js

double-check-file:
${env.ROYALE_DOWNLOAD_CACHE}
Need file: ${still_no_file}

get-from-cache-if-needed:

fail-if-not-found:

preprocess:

externc:
Fehler: Hauptklasse org.apache.royale.compiler.clients.EXTERNC konnte nicht
gefunden oder geladen werden
(Error: Main class org.apache.royale.compiler.clients.EXTERNC could not
found or loaded)

BUILD FAILED
C:\local\apache-royale\release-process\ApproveRoyale.xml:721: The following
error occurred while executing this line:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs\build.xml:1752:
The following error occurred while executing this line:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-asjs\build.xml:1824:
The following error occurred while executing this line:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-typedefs\build.xml:52:
The following error occurred while executing this line:
C:\local\apache-royale\release-process\apache-royale-0.9.0-src\royale-typedefs\js\build.xml:159:
Java returned: 1

Total time: 3 minutes 55 seconds




--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Alex Harui]

Olaf is correct.  He can just try hand-patching the files that have been
downloaded and expanded in the folder where he is running
ApproveRoyale.xml.  There should be an apache-royals-0.9.0-src folder with
a royale-asjs/examples/royale/DataBindingExample_Flat subfolder.  Running
the "build" target in Ant should help us find out if the build will finish
without the Flash/AIR environment variables.

I'm waiting on the Olaf's results before cutting an RC2.  I'd like the
examples to build without Flash/AIR.  Also, I'm making changes to
MDLBlogExample and I think MDLExample as well.  After Justin pointed out
that there is CSS under CC-BY-4.0 in MDLBlogExample, I took a closer look
and realized that really, I think these two examples are just ports of
Google's examples and thus should remain under Google's copyright, and
that we should clearly mark the boundaries of the CC-BY-4.0 CSS.  Some of
the text used in the example is also CC-BY-4.0.

There is also a thread open on legal-discuss to verify that CSS is
considered to be "media" and not "source code".  If it is "source code"
then we have to treat the example as Category X and remove the CSS and
text from the repos and releases.  It is, as always, unfortunate that
these issues are not discovered when these files are first committed to
the repo as has been recommended by more than one experienced Apache
member instead of during the release process.

Hopefully we'll see RC2 soon.

-Alex

On 1/16/18, 2:12 AM, "Olaf Krueger"  wrote:

>Piotr,
>I guess this time I understand what to do...hopefully ;-):
>
>Alex made a change at one of the examples at the release/0.9.0 branch.
>Because the distribution server does not contain this change I can't
>continue testing.
>
>So, in order to continue testing I have to adopt Alex change to my local
>copy (which originally was downloaded from the distribution server by
>using
>the approval script) and after making chances I just have to run/test just
>the build.
>
>Thanks,
>Olaf
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7
>C19fd212b71614b56ae6f08d55ccaec08%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636516948969228487=FoNZH5kWbppMWhLkLAXBHofzysIHXgFiqIAD4y4L0Zw%
>3D=0

Re: Github Documentation (Re: Apache Royale website is live!!)

[Alex Harui]

We decided a while back to use GH Pages instead of a wiki for our
user-facing documentation.  Royale is part of the Apache organization on
GH, so there might be more restrictions on what we can and can't do.

AIUI, it is all HTML and CSS in the end.  I'm not opposed to switching to
using Jekyll and MarkDown as long as we can add regular HTML files, as
well as other CSS and JS files which might be generated by Royale to the
GH Pages web site.

Thanks,
-Alex

On 1/16/18, 5:34 AM, "Olaf Krueger"  wrote:

>Hi Carlos,
>
>>I think we should have control over this in order to modify to our needs
>and not having to bother
>>anyone for something so easy
>
>Agree!
>
>
>>I need to know now, how I can tweak the theme to our needs
>This should do the trick [1]
>
>Thanks for working on this!!
>
>Olaf
>
>[1]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.gith
>ub.com%2Farticles%2Fcustomizing-css-and-html-in-your-jekyll-theme%2F=
>02%7C01%7Caharui%40adobe.com%7C309fdf7eef9c4f84f64c08d55ce5f44c%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636517065116363687=kNtFlcYO2ukNYL
>d654tQmV0J0GCaS5reROk7Zozlcb8%3D=0
>
>
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7
>C309fdf7eef9c4f84f64c08d55ce5f44c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636517065116363687=1Mm16vSGSNHaSU7khN0IsT1Hm%2FGpKyGVDmkoa3meTw
>8%3D=0

Re: [Royale] ICollectionView

[Peter Ent]

Sorry for the delay; yesterday was a company holiday here in the States. I
was catching up on other things. I figured this would come up; we need to
have a plan for style names that is consistent. What we have now isn't
working right all the time. I was trying to give the columns additional
class names as "first", "middle", and "last" so that borders could be
added more precisely. That seems not be working either. I think its my
application and not anything to do with the underlying Royale framework.
I'll look into this today.

Thanks for all your help!
‹peter

On 1/12/18, 6:35 PM, "piotrz"  wrote:

>Peter,
>
>I see one more issue. In DataGridColumnList we have following line:
>"typeNames = "DataGridColumnList";". After compilation each div which
>represents DataGridColumnList have class="List".
>
>yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Flist_each_datagridcolum
>nlist.png=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536
>ef%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=j
>avj1cU%2BeNSJvY%2FwHzRtOQDDCGJKSNEUP2QCWWWZpug%3D=0>
>
>This gives us some borders because default List style has css which is
>doing
>for us border etc. [1]
>
>yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Fborder_grid.png=02
>%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636513969542441416=D%2BVI5eYn%2FTXqG1
>DDvfS5GSfGctc0JptwQZ%2BHNG1hT3s%3D=0>
>
>However if I add to the column some style as we are doing it in
>DataGridExample for as second grid, we are ending up with something weird:
>
>yale-development.20373.n8.nabble.com%2Ffile%2Ft1%2Fno_border_grid.png
>=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%7Cfa7b1b5a7
>b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=nxtvREgcMz6kgZ0
>wwZV5bmUbkhvAuckEnUETYmFpgrs%3D=0>
>
>There is no border, cause DataGridColumnList style doesn't have it [2].
>
>I think we should:
>1) Set className = "DataGridColumnList" - here [3]
>2) Add those border to class "DataGridColumnList" in css
>
>What do you think ?
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>n27aYN=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=rOBo
>byCAc2i92Vmlu0eniYIkCaEtWRA%2BTox08IMOFhQ%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>N4S9PK=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=dQ0p
>WvYbK4Yn0RNJOKhZkKLbJzF4T54%2BSikI7bes1%2Bw%3D=0
>[3] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>8mF2Lr=02%7C01%7Cpent%40adobe.com%7Ca95e03b494894e2bf8ba08d55a1536ef%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636513969542441416=mPbe
>gCAynPs5olJlaFDMFew5Bfb5mkP6lYIplrrqMd0%3D=0
>
>Thanks,
>Piotr
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F=02%7C01%7Cpent%40adobe.com%7Ca
>95e03b494894e2bf8ba08d55a1536ef%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0
>%7C636513969542441416=aLSGgQj1G%2F24n9AS97pDZgY59%2FycIbacHt0xUtKnCz
>c%3D=0

Re: Github Documentation (Re: Apache Royale website is live!!)

[Olaf Krueger]

Hi Carlos,

>I think we should have control over this in order to modify to our needs
and not having to bother
>anyone for something so easy

Agree!


>I need to know now, how I can tweak the theme to our needs
This should do the trick [1]

Thanks for working on this!!

Olaf

[1]
https://help.github.com/articles/customizing-css-and-html-in-your-jekyll-theme/





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Github Documentation (Re: Apache Royale website is live!!)

[Carlos Rovira]

Cayman is a Github official theme. So I suppose is totally right to use it
as an starting point.
But in the end: We don't want to use Cayman!, we want to create a theme
that has our branding (fonts, colors and some image backgrounds)

2018-01-16 13:23 GMT+01:00 Piotr Zarzycki :

> Carlos,
>
> What's with the license of Cayman. Maybe we should choose some theme
> compatible with Apache ? Only one from the list seems to be, but I'm not an
> expert [1]
>
> [1] https://github.com/pages-themes/primer
>
> Thanks, Piotr
>
>
> 2018-01-16 13:14 GMT+01:00 Carlos Rovira :
>
> > Just created the ticket here:
> >
> > https://issues.apache.org/jira/browse/INFRA-15845
> >
> > 2018-01-16 13:03 GMT+01:00 Carlos Rovira :
> >
> > > Hi,
> > >
> > > yes, I think the best way is to use markdown, GitHub pages and some
> > > template (e.j: Cayman) as an starting point to change styles to match
> or
> > > Royale website styles
> > > As we all doesn't have experience, I'll try to investigate and talk
> with
> > > infra to see if they need to make some tweak.
> > >
> > > I want to put all the things inlace so Andrew can work on docs more
> > easily
> > >
> > > Thanks all fro your thoughts! :)
> > >
> > > 2018-01-16 11:13 GMT+01:00 Piotr Zarzycki :
> > >
> > >> There is possibility that we may have to ask infra to switch something
> > >> etc.
> > >> I don't think we need Wiki on the docs repository. It should be
> possible
> > >> make pull requests to that repository by anyone.
> > >>
> > >> We just need to correct all the things which you have on your repo,
> than
> > >> make transformation to the GitHub pages.
> > >>
> > >> Later we can proceed straight in our repo. It is less pleasent write
> > mark
> > >> down only without preview. - If there is some tool which allows have
> > >> preview without Wiki, we can even transform current state of your
> > >> repository to GitHub pages.
> > >>
> > >>
> > >> 2018-01-16 11:03 GMT+01:00 Olaf Krueger :
> > >>
> > >> > >Do you know the way how to do this ?
> > >> >
> > >> > My understanding is that Jekyll supports MarkDown out of the box.
> > >> > If that's the case, each Wiki article could easily be reused with
> > GitHub
> > >> > pages.
> > >> > As I started with my FlexJS docs Wiki the goal was to start easily
> > using
> > >> > the
> > >> > Wiki and porting it later to GitHub pages.
> > >> >
> > >> > BTW: From my opionion, we definately should use Markdown in order to
> > >> write
> > >> > the documentation cause it simplifies things a lot.
> > >> >
> > >> >
> > >> > >If someone can help with that it would be great.
> > >> >
> > >> > If I would entirely know how it works I would share my knowledge and
> > >> would
> > >> > help of course ;-)
> > >> > I'll try to I find some time to investigate a bit more...
> > >> >
> > >> > Thanks,
> > >> > Olaf
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> *
> > >>
> > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>



-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Github Documentation (Re: Apache Royale website is live!!)

[Carlos Rovira]

Hi,

I created my own test repo, and is very easy.

https://github.com/carlosrovira/royale-pages-test/blob/master/README.md
https://carlosrovira.github.io/royale-pages-test/

So we need for infra to config the Github repo. I think we should have
control over this in order to modify to our needs and not having to bother
anyone for something so easy

In the other hand, I applied the theme with the theme chooser, I need to
know now, how I can tweak the theme to our needs


2018-01-16 13:14 GMT+01:00 Carlos Rovira :

> Just created the ticket here:
>
> https://issues.apache.org/jira/browse/INFRA-15845
>
> 2018-01-16 13:03 GMT+01:00 Carlos Rovira :
>
>> Hi,
>>
>> yes, I think the best way is to use markdown, GitHub pages and some
>> template (e.j: Cayman) as an starting point to change styles to match or
>> Royale website styles
>> As we all doesn't have experience, I'll try to investigate and talk with
>> infra to see if they need to make some tweak.
>>
>> I want to put all the things inlace so Andrew can work on docs more
>> easily
>>
>> Thanks all fro your thoughts! :)
>>
>> 2018-01-16 11:13 GMT+01:00 Piotr Zarzycki :
>>
>>> There is possibility that we may have to ask infra to switch something
>>> etc.
>>> I don't think we need Wiki on the docs repository. It should be possible
>>> make pull requests to that repository by anyone.
>>>
>>> We just need to correct all the things which you have on your repo, than
>>> make transformation to the GitHub pages.
>>>
>>> Later we can proceed straight in our repo. It is less pleasent write mark
>>> down only without preview. - If there is some tool which allows have
>>> preview without Wiki, we can even transform current state of your
>>> repository to GitHub pages.
>>>
>>>
>>> 2018-01-16 11:03 GMT+01:00 Olaf Krueger :
>>>
>>> > >Do you know the way how to do this ?
>>> >
>>> > My understanding is that Jekyll supports MarkDown out of the box.
>>> > If that's the case, each Wiki article could easily be reused with
>>> GitHub
>>> > pages.
>>> > As I started with my FlexJS docs Wiki the goal was to start easily
>>> using
>>> > the
>>> > Wiki and porting it later to GitHub pages.
>>> >
>>> > BTW: From my opionion, we definately should use Markdown in order to
>>> write
>>> > the documentation cause it simplifies things a lot.
>>> >
>>> >
>>> > >If someone can help with that it would be great.
>>> >
>>> > If I would entirely know how it works I would share my knowledge and
>>> would
>>> > help of course ;-)
>>> > I'll try to I find some time to investigate a bit more...
>>> >
>>> > Thanks,
>>> > Olaf
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
>>> >
>>>
>>>
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>>>
>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Github Documentation (Re: Apache Royale website is live!!)

[Piotr Zarzycki]

Carlos,

What's with the license of Cayman. Maybe we should choose some theme
compatible with Apache ? Only one from the list seems to be, but I'm not an
expert [1]

[1] https://github.com/pages-themes/primer

Thanks, Piotr


2018-01-16 13:14 GMT+01:00 Carlos Rovira :

> Just created the ticket here:
>
> https://issues.apache.org/jira/browse/INFRA-15845
>
> 2018-01-16 13:03 GMT+01:00 Carlos Rovira :
>
> > Hi,
> >
> > yes, I think the best way is to use markdown, GitHub pages and some
> > template (e.j: Cayman) as an starting point to change styles to match or
> > Royale website styles
> > As we all doesn't have experience, I'll try to investigate and talk with
> > infra to see if they need to make some tweak.
> >
> > I want to put all the things inlace so Andrew can work on docs more
> easily
> >
> > Thanks all fro your thoughts! :)
> >
> > 2018-01-16 11:13 GMT+01:00 Piotr Zarzycki :
> >
> >> There is possibility that we may have to ask infra to switch something
> >> etc.
> >> I don't think we need Wiki on the docs repository. It should be possible
> >> make pull requests to that repository by anyone.
> >>
> >> We just need to correct all the things which you have on your repo, than
> >> make transformation to the GitHub pages.
> >>
> >> Later we can proceed straight in our repo. It is less pleasent write
> mark
> >> down only without preview. - If there is some tool which allows have
> >> preview without Wiki, we can even transform current state of your
> >> repository to GitHub pages.
> >>
> >>
> >> 2018-01-16 11:03 GMT+01:00 Olaf Krueger :
> >>
> >> > >Do you know the way how to do this ?
> >> >
> >> > My understanding is that Jekyll supports MarkDown out of the box.
> >> > If that's the case, each Wiki article could easily be reused with
> GitHub
> >> > pages.
> >> > As I started with my FlexJS docs Wiki the goal was to start easily
> using
> >> > the
> >> > Wiki and porting it later to GitHub pages.
> >> >
> >> > BTW: From my opionion, we definately should use Markdown in order to
> >> write
> >> > the documentation cause it simplifies things a lot.
> >> >
> >> >
> >> > >If someone can help with that it would be great.
> >> >
> >> > If I would entirely know how it works I would share my knowledge and
> >> would
> >> > help of course ;-)
> >> > I'll try to I find some time to investigate a bit more...
> >> >
> >> > Thanks,
> >> > Olaf
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> *
> >>
> >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Github Documentation (Re: Apache Royale website is live!!)

[Carlos Rovira]

Just created the ticket here:

https://issues.apache.org/jira/browse/INFRA-15845

2018-01-16 13:03 GMT+01:00 Carlos Rovira :

> Hi,
>
> yes, I think the best way is to use markdown, GitHub pages and some
> template (e.j: Cayman) as an starting point to change styles to match or
> Royale website styles
> As we all doesn't have experience, I'll try to investigate and talk with
> infra to see if they need to make some tweak.
>
> I want to put all the things inlace so Andrew can work on docs more easily
>
> Thanks all fro your thoughts! :)
>
> 2018-01-16 11:13 GMT+01:00 Piotr Zarzycki :
>
>> There is possibility that we may have to ask infra to switch something
>> etc.
>> I don't think we need Wiki on the docs repository. It should be possible
>> make pull requests to that repository by anyone.
>>
>> We just need to correct all the things which you have on your repo, than
>> make transformation to the GitHub pages.
>>
>> Later we can proceed straight in our repo. It is less pleasent write mark
>> down only without preview. - If there is some tool which allows have
>> preview without Wiki, we can even transform current state of your
>> repository to GitHub pages.
>>
>>
>> 2018-01-16 11:03 GMT+01:00 Olaf Krueger :
>>
>> > >Do you know the way how to do this ?
>> >
>> > My understanding is that Jekyll supports MarkDown out of the box.
>> > If that's the case, each Wiki article could easily be reused with GitHub
>> > pages.
>> > As I started with my FlexJS docs Wiki the goal was to start easily using
>> > the
>> > Wiki and porting it later to GitHub pages.
>> >
>> > BTW: From my opionion, we definately should use Markdown in order to
>> write
>> > the documentation cause it simplifies things a lot.
>> >
>> >
>> > >If someone can help with that it would be great.
>> >
>> > If I would entirely know how it works I would share my knowledge and
>> would
>> > help of course ;-)
>> > I'll try to I find some time to investigate a bit more...
>> >
>> > Thanks,
>> > Olaf
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
>> >
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Github Documentation (Re: Apache Royale website is live!!)

[Carlos Rovira]

Hi,

yes, I think the best way is to use markdown, GitHub pages and some
template (e.j: Cayman) as an starting point to change styles to match or
Royale website styles
As we all doesn't have experience, I'll try to investigate and talk with
infra to see if they need to make some tweak.

I want to put all the things inlace so Andrew can work on docs more easily

Thanks all fro your thoughts! :)

2018-01-16 11:13 GMT+01:00 Piotr Zarzycki :

> There is possibility that we may have to ask infra to switch something etc.
> I don't think we need Wiki on the docs repository. It should be possible
> make pull requests to that repository by anyone.
>
> We just need to correct all the things which you have on your repo, than
> make transformation to the GitHub pages.
>
> Later we can proceed straight in our repo. It is less pleasent write mark
> down only without preview. - If there is some tool which allows have
> preview without Wiki, we can even transform current state of your
> repository to GitHub pages.
>
>
> 2018-01-16 11:03 GMT+01:00 Olaf Krueger :
>
> > >Do you know the way how to do this ?
> >
> > My understanding is that Jekyll supports MarkDown out of the box.
> > If that's the case, each Wiki article could easily be reused with GitHub
> > pages.
> > As I started with my FlexJS docs Wiki the goal was to start easily using
> > the
> > Wiki and porting it later to GitHub pages.
> >
> > BTW: From my opionion, we definately should use Markdown in order to
> write
> > the documentation cause it simplifies things a lot.
> >
> >
> > >If someone can help with that it would be great.
> >
> > If I would entirely know how it works I would share my knowledge and
> would
> > help of course ;-)
> > I'll try to I find some time to investigate a bit more...
> >
> > Thanks,
> > Olaf
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>



-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Github Documentation (Re: Apache Royale website is live!!)

[Olaf Krueger]

Hi Piotr,

>I don't think we need Wiki on the docs repository. 
I agree that we should start directly with GH pages.


>We just need to correct all the things which you have on your repo
It is not so much content at the end.
I guess we have to rewrite it anyway, so don't care about it ;-) 

>It is less pleasent write mark down only without preview. - If there is
some tool...
https://github.com/planetjekyll/awesome-jekyll-editors

Thanks,
Olaf






--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1

[Olaf Krueger]

Piotr,
I guess this time I understand what to do...hopefully ;-):

Alex made a change at one of the examples at the release/0.9.0 branch.
Because the distribution server does not contain this change I can't
continue testing.

So, in order to continue testing I have to adopt Alex change to my local
copy (which originally was downloaded from the distribution server by using
the approval script) and after making chances I just have to run/test just
the build.

Thanks,
Olaf



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Github Documentation (Re: Apache Royale website is live!!)

[Piotr Zarzycki]

There is possibility that we may have to ask infra to switch something etc.
I don't think we need Wiki on the docs repository. It should be possible
make pull requests to that repository by anyone.

We just need to correct all the things which you have on your repo, than
make transformation to the GitHub pages.

Later we can proceed straight in our repo. It is less pleasent write mark
down only without preview. - If there is some tool which allows have
preview without Wiki, we can even transform current state of your
repository to GitHub pages.


2018-01-16 11:03 GMT+01:00 Olaf Krueger :

> >Do you know the way how to do this ?
>
> My understanding is that Jekyll supports MarkDown out of the box.
> If that's the case, each Wiki article could easily be reused with GitHub
> pages.
> As I started with my FlexJS docs Wiki the goal was to start easily using
> the
> Wiki and porting it later to GitHub pages.
>
> BTW: From my opionion, we definately should use Markdown in order to write
> the documentation cause it simplifies things a lot.
>
>
> >If someone can help with that it would be great.
>
> If I would entirely know how it works I would share my knowledge and would
> help of course ;-)
> I'll try to I find some time to investigate a bit more...
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Github Documentation (Re: Apache Royale website is live!!)

[Piotr Zarzycki]

Olaf,

Ad. 1) I personally don't want wiki for documentation. That is only the
proposition to use wiki on your repository in order to simplify things and
investigate whether we can transform it to the GitHub pages. Do you know
the way how to do this ?

Ad. 2) I think Carlos need help with run even simple Hello World using
Jekyll on our royale-docs. If someone can help with that it would be great.

Thanks, Piotr


2018-01-16 10:46 GMT+01:00 Olaf Krueger :

> Hi,
>
> >How do we create navigation that shows up on each page of the
> >documentation
>
> To be clear:
> There are two common ways of creating a documentation by using GitHub:
>
> 1) Using the GitHub Wiki
> 2) Using GitHub pages
>
> 1)
> Here the navigation is provided by using the Wikis' sidebar.
> You have to put some Marddown into the _Sidebar in order to build the
> navigation structure.
> All articles has to be written in MarkDown.
> I noticed that our Royale-docs repo does not provide a Wiki.
> If we would like to use it we have to enable it at first. Does anybody know
> how to enable the Wiki?
> The main drawback of the Wiki is, that (as far as I know) we can't use pull
> request. There are revisons for particular articles, but it feels that a
> lot
> of things are done behind the scene.
> Moreover I guess we can't customize the look and feel.
>
> 2)
> This is they way Carlos would like to go.
> With GitHub pages you can use e.g. Jekyll, which is a static site
> generator.
> This produces a more sophisticated look and feel.
> We have to grab a Jekyll template and customize it and make it all work.
> When all is in place we could start with creating content.
> The entire code/content could be managed in the same way as any other code
> repository.
>
> I guess we would like to go with GitHub pages?
>
> Hope this helps,
> Olaf
>
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Github Documentation (Re: Apache Royale website is live!!)

[Olaf Krueger]

Hi,

>How do we create navigation that shows up on each page of the 
>documentation

To be clear:
There are two common ways of creating a documentation by using GitHub:

1) Using the GitHub Wiki
2) Using GitHub pages

1)
Here the navigation is provided by using the Wikis' sidebar.
You have to put some Marddown into the _Sidebar in order to build the
navigation structure.
All articles has to be written in MarkDown.
I noticed that our Royale-docs repo does not provide a Wiki.
If we would like to use it we have to enable it at first. Does anybody know
how to enable the Wiki?
The main drawback of the Wiki is, that (as far as I know) we can't use pull
request. There are revisons for particular articles, but it feels that a lot
of things are done behind the scene.
Moreover I guess we can't customize the look and feel.

2) 
This is they way Carlos would like to go.
With GitHub pages you can use e.g. Jekyll, which is a static site generator.
This produces a more sophisticated look and feel.
We have to grab a Jekyll template and customize it and make it all work.
When all is in place we could start with creating content.
The entire code/content could be managed in the same way as any other code
repository.

I guess we would like to go with GitHub pages?

Hope this helps,
Olaf






--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Github Documentation (Re: Apache Royale website is live!!)

[Olaf Krueger]

Hi Carlos,

>But there's no such file, so my main question is, is royale-docs a Github
>pages repo so I can customize it with a Github Pages Theme?

>From my understanding, any GitHub repo is able to process/provide GitHub
pages.

>Add the following to your site's _config.yml: 

IIRIC, GitHub pages uses Jekyll as default static site generator.
This _config.yml is a Jekyll file [1].

I guess we have to setup our repo at first in order to use one of those
(Jekyll?) templates [2][3][4].

Of yourse, I could be wrong.

I would help with this, but after I took some time in order to test the
release approval stuff I'd like to continue with the TryItNow app at first
;-)

Thanks,
Olaf



[1] https://jekyllrb.com/docs/configuration/
[2] https://help.github.com/categories/customizing-github-pages/
[3]
https://help.github.com/articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser/
[4]
https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/






--
Sent from: http://apache-royale-development.20373.n8.nabble.com/