Website Revamp Update - Week 1 (and how to get involved)

2020-10-20 Thread Griselda Cuevas
Hi folks, please find here [1] the updates for week 1 of the website revamp
work. This document will contain notes for every sprint, which will last
one week.

If you want to get involved in this effort here are some resources:

   - The Polidea/Utilo team will be sharing mocks and designs as they are
   available to get feedback from the community, so share your thoughts and
   suggestions!
   - @Agnieszka Sell  will create a public link
   for the weekly review meeting so anyone interesting in joining can come.
   - I created a slack channel [2] if you want to chat about this project
   with the working group

Thanks all,
G

[1]
https://docs.google.com/document/d/1CqssBpRt1EjpV0nCBaS9WGaGHt_4stKXbwMz9gYfmwc/edit
[2] https://join.slack.com/share/zt-i7u8s7vr-g8IYBC8IS3bcUmsCHmYa5Q


Re: Requesting Jira contributor access for Website revamp project team

2020-10-20 Thread Griselda Cuevas
Thank you Alexey

On Fri, 16 Oct 2020 at 09:40, Alexey Romanenko 
wrote:

> Hi Gris,
>
> It’s done.
>
> Regards,
> Alexey
>
> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
> >
> > Hi folks, could someone in the PMC provide "Contributor" roles to the
> following folks who will be working on the website revamp?
> >
> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
> >
>
>


Re: Requesting Jira contributor access for Website revamp project team

2020-10-20 Thread Griselda Cuevas
+1 to Kyle's suggestion.

@Agnieszka Sell  - I went ahead and created
BEAM-11079 . I added the
Public PRD and created the label website-revamp-2020, let's use that to
track work on this project.

Could you add an overview of the timeline as a comment to BEAM-11079
?

On Tue, 20 Oct 2020 at 08:44, Kyle Weaver  wrote:

> > Can I ask you to provide me additional ones that will allow me to create
> a new project (Beam website revamp)?
>
> Usually we put all our issues under the BEAM project. Then we organize
> issues by setting their components and labels. I recommend using the
> existing "website" component along with a new label for the website revamp.
> You might already have permissions to create new labels; if not, please let
> us know.
>
> On Mon, Oct 19, 2020 at 11:36 PM Agnieszka Sell <
> agnieszka.s...@polidea.com> wrote:
>
>> Hi folks,
>>
>> Thank you for the Jira permissions for my team! Can I ask you to provide
>> me additional ones that will allow me to create a new project (Beam website
>> revamp)? Now I can create new boards but only for existing projects. My
>> username is Agnieszka Sell.
>>
>> Kind regards,
>>
>> Agnieszka
>>
>> On Fri, Oct 16, 2020 at 6:40 PM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> Hi Gris,
>>>
>>> It’s done.
>>>
>>> Regards,
>>> Alexey
>>>
>>> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
>>> >
>>> > Hi folks, could someone in the PMC provide "Contributor" roles to the
>>> following folks who will be working on the website revamp?
>>> >
>>> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
>>> >
>>>
>>>
>>
>> --
>>
>> Agnieszka Sell
>> Polidea  | Project Manager
>>
>> M: *+48 504 901 334* <+48504901334>
>> E: agnieszka.s...@polidea.com
>> [image: Polidea] 
>>
>> Check out our projects! 
>> [image: Github]  [image: Facebook]
>>  [image: Twitter]
>>  [image: Linkedin]
>>  [image: Instagram]
>> 
>>
>> Unique Tech
>> Check out our projects! 
>>
>


Re: [Proposal] Website Revamp project

2020-10-20 Thread Griselda Cuevas
Thanks Robert.

I have talked to the team who will be working on the redesign, and we are
going to take on the following tasks to make the work more manageable:

1) Work will be managed in Jira by myself and Agnieszka
2) Agnieszka will be sharing weekly updates in the dev@ list, these update
will have calls for feedback so the community can chime in
3) We'll host weekly calls that anyone in the community can join

We hope that #1 and #2 can provide visibility in what to expect on the
review side.


On Mon, 19 Oct 2020 at 10:01, Robert Bradshaw  wrote:

> Welcome. Looking forward to the website improvements.
>
> I would like to call out that it'd be a good idea to have a plan for how
> this can be developed/reviewed incrementally. We were able to get the last
> major website change in, but huge monolithic PRs that change the world are
> difficult to review and integrate, so it'd be good to have a plan upfront
> (learning from or experience last time).
>
> On Fri, Oct 16, 2020 at 1:24 PM Alexey Romanenko 
> wrote:
>
>> Welcome to Beam!
>>
>> Regards,
>> Alexey
>>
>> On 15 Oct 2020, at 16:06, Nam Bui  wrote:
>>
>> Hi everyone,
>>
>> I'm Nam. I used to work on Apache Beam website migration. From now on, I
>> will be responsible for website development. Thus, I will implement new
>> designs and some of the functionalities on our website. Great to be working
>> with you!
>>
>> Best regards,
>> Nam
>>
>>
>>
>> On Thu, Oct 15, 2020 at 8:42 PM Kasia Zając 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am Kasia and I will be responsible for the UX side of things in the
>>> project. I will be preparing the wireframes and also asking you for
>>> feedback later in the process. Happy to join the community at least for a
>>> short amount of time :)
>>>
>>> Have a good day,
>>> Kasia Zając
>>> Product Owner
>>> +48 664 115 440 <+48664115440>
>>> ka...@utilodesign.com
>>> [image: utilo] 
>>>
>>> www.utilodesign.com
>>> [image: Behance]  [image:
>>> dribbble]  [image: Instagram]
>>>  [image: Linkedin]
>>> 
>>>
>>>
>>> On Thu, Oct 15, 2020 at 2:12 PM Agnieszka Sell <
>>> agnieszka.s...@polidea.com> wrote:
>>>
 Hi Everyone,

 I'm Agnieszka Sell, Project Manager in the Beam website revamp project.

 I'm looking forward to getting your feedback on design and development
 progress we'll be sharing with you in upcoming weeks.

 Best,

 Agnieszka

 On Wed, Oct 14, 2020 at 7:06 PM Gris Cuevas  wrote:

> Hi Everyone,
>
> We're ready to start work on the revamp of the website, we'll use the
> PRD shared in this thread previously.
>
> Polidea will be the team working on this revamp and we'll be bringing
> designs and proposals to the community for review as the project
> progresses.
>
> Thank you!
> Gris
>
> On 2020/09/09 18:14:18, Gris Cuevas  wrote:
> > Hi Beam community,
> >
> > In a previous thread [1] I mentioned that I was going to work on
> product requirements document (PRD) for a project to address some of the
> requests and ideas collected by Aizhamal, Rose and David in previous
> efforts.
> >
> > The PRD is ready [2], and I'd like to get your feedback before
> moving forward into implementation. Please add you comments by Sunday
> Septermber 13, 2020.
> >
> > We're looking to start work on this project in around 2 weeks.
> >
> > Thank you!
> > Gris
> >
> > [1]
> https://lists.apache.org/thread.html/r1a4cea1e8b53bef73c49f75df13956024d8d78bc81b36e54ef71f8a9%40%3Cdev.beam.apache.org%3E
> >
> > [2] https://s.apache.org/beam-site-revamp
> >
>


 --
 Agnieszka Sell
 Polidea  | Project Manager
 M: *+48 504 901 334* <+48504901334>
 E: agnieszka.s...@polidea.com
 [image: Polidea] 

 Check out our projects! 
 [image: Github]  [image: Facebook]
  [image: Twitter]
  [image: Linkedin]
  [image: Instagram]
 

 Unique Tech
 Check out our projects! 

>>>
>>


Re: [VOTE] Release 2.25.0, release candidate #2

2020-10-20 Thread Ahmet Altay
+1 - I verified python quickstarts.

On Tue, Oct 20, 2020 at 11:36 AM Robin Qiu  wrote:

> Hi everyone,
> Please review and vote on the release candidate #2 for the version 2.25.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org [2],
> which is signed with the key with fingerprint
> AD70476B9D1AF3EFEC2208165952E71AACAF911D [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.25.0-RC2" [5],
> * website pull request listing the release [6], publishing the API
> reference manual [7], and the blog post [8].
> * Java artifacts were built with Maven 3.5.3 and OpenJDK 1.8.0
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> * Validation sheet with a tab for 2.25.0 release to help with validation
> [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Robin
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12347147
> [2] https://dist.apache.org/repos/dist/dev/beam/2.25.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1142
> [5] https://github.com/apache/beam/tree/v2.25.0-RC2
> [6] https://github.com/apache/beam/pull/13130
> [7] https://github.com/apache/beam-site/pull/608
> [8] https://github.com/apache/beam/pull/13131
> [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1494345946
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>


[VOTE] Release 2.25.0, release candidate #2

2020-10-20 Thread Robin Qiu
Hi everyone,
Please review and vote on the release candidate #2 for the version 2.25.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org [2],
which is signed with the key with fingerprint
AD70476B9D1AF3EFEC2208165952E71AACAF911D [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.25.0-RC2" [5],
* website pull request listing the release [6], publishing the API
reference manual [7], and the blog post [8].
* Java artifacts were built with Maven 3.5.3 and OpenJDK 1.8.0
* Python artifacts are deployed along with the source release to the
dist.apache.org [2].
* Validation sheet with a tab for 2.25.0 release to help with validation
[9].
* Docker images published to Docker Hub [10].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Robin

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12347147
[2] https://dist.apache.org/repos/dist/dev/beam/2.25.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1142
[5] https://github.com/apache/beam/tree/v2.25.0-RC2
[6] https://github.com/apache/beam/pull/13130
[7] https://github.com/apache/beam-site/pull/608
[8] https://github.com/apache/beam/pull/13131
[9]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1494345946
[10] https://hub.docker.com/search?q=apache%2Fbeam=image


Re: Requesting Jira contributor access for Website revamp project team

2020-10-20 Thread Kyle Weaver
> Can I ask you to provide me additional ones that will allow me to create
a new project (Beam website revamp)?

Usually we put all our issues under the BEAM project. Then we organize
issues by setting their components and labels. I recommend using the
existing "website" component along with a new label for the website revamp.
You might already have permissions to create new labels; if not, please let
us know.

On Mon, Oct 19, 2020 at 11:36 PM Agnieszka Sell 
wrote:

> Hi folks,
>
> Thank you for the Jira permissions for my team! Can I ask you to provide
> me additional ones that will allow me to create a new project (Beam website
> revamp)? Now I can create new boards but only for existing projects. My
> username is Agnieszka Sell.
>
> Kind regards,
>
> Agnieszka
>
> On Fri, Oct 16, 2020 at 6:40 PM Alexey Romanenko 
> wrote:
>
>> Hi Gris,
>>
>> It’s done.
>>
>> Regards,
>> Alexey
>>
>> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
>> >
>> > Hi folks, could someone in the PMC provide "Contributor" roles to the
>> following folks who will be working on the website revamp?
>> >
>> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
>> >
>>
>>
>
> --
>
> Agnieszka Sell
> Polidea  | Project Manager
>
> M: *+48 504 901 334* <+48504901334>
> E: agnieszka.s...@polidea.com
> [image: Polidea] 
>
> Check out our projects! 
> [image: Github]  [image: Facebook]
>  [image: Twitter]
>  [image: Linkedin]
>  [image: Instagram]
> 
>
> Unique Tech
> Check out our projects! 
>


Release schedule for PubsubIO with message ordering enabled subscription

2020-10-20 Thread JITHIN SUKUMAR
Hi Apache Beam Maintainers,

I am using Cloud Dataflow for reading messages from a Pub/Sub subscription
(PubsubIO) and writing the messages to a text file (in Google Cloud
Storage). I have enabled Message Ordering for the subscription (
https://cloud.google.com/pubsub/docs/ordering).However, the pipeline fails
with the error message:

Workflow failed. Causes: pubsub subscription
projects/{project_name}/subscriptions/{subscription_name} has message
ordering enabled, which is not supported.

I am using JAVA SDK of apache beam version 2.24.0.Can anybody let me know
when (or in which version) will message ordering enabled subscriptions be
supported by Dataflow?

Thanks!
Regards,
Jithin


Re: Requesting Jira contributor access for Website revamp project team

2020-10-20 Thread Agnieszka Sell
Hi folks,

Thank you for the Jira permissions for my team! Can I ask you to provide me
additional ones that will allow me to create a new project (Beam website
revamp)? Now I can create new boards but only for existing projects. My
username is Agnieszka Sell.

Kind regards,

Agnieszka

On Fri, Oct 16, 2020 at 6:40 PM Alexey Romanenko 
wrote:

> Hi Gris,
>
> It’s done.
>
> Regards,
> Alexey
>
> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
> >
> > Hi folks, could someone in the PMC provide "Contributor" roles to the
> following folks who will be working on the website revamp?
> >
> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
> >
>
>

-- 

Agnieszka Sell
Polidea  | Project Manager

M: *+48 504 901 334* <+48504901334>
E: agnieszka.s...@polidea.com
[image: Polidea] 

Check out our projects! 
[image: Github]  [image: Facebook]
 [image: Twitter]
 [image: Linkedin]
 [image: Instagram]


Unique Tech
Check out our projects!