Thanks a lot for your replies.
Could you please provide me the location of the source code of the site.?
Then I could look into it.
BR
On Thu, Oct 27, 2016 at 9:52 PM, Davor Bonaci wrote:
> The best place to learn how to get started is the Contribution Guide [1].
> The list
The best place to learn how to get started is the Contribution Guide [1].
The list of pending JIRA issues related to the website is also available
[2].
I think BEAM-752 would be the best to get your feet wet. Other good
candidates are 516, 268, 776. If someone knows a good (non-fragile)
solution
Great !! Thanks.
You can take a look on BEAM-500 and 501 and also the PR I did last week.
I plan to submit new PRs during the week end. So please let me know how we can
sync.
Thanks
Regards
JB
On Oct 27, 2016, 14:04, at 14:04, Minudika Malshan
wrote:
>Hi all,
>
>I
Hi all,
I would like to join for the development of the new site.
Is there any issue tracking method for this? (Are there any jirra issues)
Thank you!
On Thu, Oct 27, 2016 at 4:01 PM, Jean-Baptiste Onofré
wrote:
> Hi
>
> You can propose a PR on this Jira.
>
> We will be
Hi
You can propose a PR on this Jira.
We will be more than happy to review it.
Thanks
Regards
JB
On Oct 27, 2016, 11:26, at 11:26, Abdullah Bashir
wrote:
>Thank you very much for taking time to respond Davor :)
>
>Regarding BEAM-752, i can work on that, i have
Thank you very much for taking time to respond Davor :)
Regarding BEAM-752, i can work on that, i have already built some Dataflow
Piplines on Google Cloud in Python language.
Again Can you tell me where to start for BEAM-752. I am new to ASF
contribution, so onboarding steps are kind of a black
Hi Davor,
I am done with my local setup to start contributing, I have forked and
merged pull request *(**pull/51)* into my local repo. Then I read the
google docs, their are two tasks mentioned in it, as [Beam-500] and
[Beam-501].
I found out that [Beam-500] is closed in JIRA and [Beam-501] is
Hi James,
just to let you know that I did good progress on the website mockup.
I should be able to propose a PR very soon.
Thanks for your patience ;)
Regards
JB
On 06/06/2016 05:29 PM, James Malone wrote:
Hello everyone!
The current design of the Apache Beam website[1] is based on the a
Awesome! If you need or want any help on other styling (like docs and such)
let me know - I am happy to help!
James
On Wed, Oct 5, 2016 at 11:33 PM, Jean-Baptiste Onofré
wrote:
> Hi
>
> For the website I already proposed a new design and css:
>
Hi
For the website I already proposed a new design and css:
http://maven.nanthrax.net/beam/
I plan to provide a PR very soon.
I'm late on that.
Regards
JB
On Oct 5, 2016, 20:21, at 20:21, James Malone
wrote:
>Hi all!
>
>I want to revive this thread if I
On Wed, Oct 5, 2016 at 3:51 PM, Kenneth Knowles
wrote:
> Just because the thread got bumped... I kind of miss the old bucket of
> technical docs. They aren't user-facing, but I used it quite a lot. Perhaps
> instead of deleting it, move from "Learn" to "Contribute" or
Just because the thread got bumped... I kind of miss the old bucket of
technical docs. They aren't user-facing, but I used it quite a lot. Perhaps
instead of deleting it, move from "Learn" to "Contribute" or bury it
somewhere near the bottom of the contributors' guide?
On Wed, Oct 5, 2016 at
Good thoughts.
There'll be a section on IO that comes over as part of the programming
guide being ported from the Cloud Dataflow docs. Hopefully that has the
technical info needed. Once we see how that's structured (Devin is still
playing around with a single page or multiple), then we can decide
Hi Frances,
great doc !
Maybe in the "Learn" section, we can also add IOs (like SDKs, and
runners), like we do in Camel (http://camel.apache.org/components.html)
For the SDKs, I would also add DSLs in the same section.
WDYT ?
Regards
JB
On 06/17/2016 12:21 AM, Frances Perry wrote:
Good
Hi James,
very good idea !
Couple of month ago, I completely revamped the Karaf website:
http://karaf.apache.org/
It could be a good skeleton in term of sections/pages.
IMHO, for Beam, at least for the home page, we should have:
1. a clear message about what Beam is from an user perspective:
Hello everyone!
The current design of the Apache Beam website[1] is based on the a basic
Bootstrap/Jekyll theme. While this made getting an initial site out quickly
pretty easy, the site itself is a little bland (in my opinion :). I propose
we create a new design (layout templates, color schemes,
16 matches
Mail list logo