Hey,
Infra team started a survey:
> to understand the heart of the problems that our projects and podlings
face.
> (...)
> https://infra.apache.org/surveys/survey-1.html
I'm just reposting it here, if it just happens that you have something to
share with them.
Best,
Piotrek
pon., 14 lis 2022
Hi all,
The new workflow is documented at https://flink.apache.org/community.html
Thanks,
Martijn
On Mon, Nov 14, 2022 at 3:37 AM Leonard Xu wrote:
>
> > The mailing list has been created and I've opened a PR to update the
> docs
> > https://github.com/apache/flink-web/pull/583
>
> Thanks
> The mailing list has been created and I've opened a PR to update the docs
> https://github.com/apache/flink-web/pull/583
Thanks @Martijn for the nice work.
I am willing to review this document PR, because the PR also provides Chinese
part, which is great, I should be able to offer some
The mailing list has been created and I've opened a PR to update the docs
https://github.com/apache/flink-web/pull/583
Op zo 13 nov. 2022 om 09:40 schreef Martijn Visser
> Agreed. I've requested a new private mailing list [1]
>
> [1] https://issues.apache.org/jira/browse/INFRA-23898
>
> On
Agreed. I've requested a new private mailing list [1]
[1] https://issues.apache.org/jira/browse/INFRA-23898
On Sat, Nov 12, 2022 at 12:09 PM Márton Balassi
wrote:
> Hi Martjin,
>
> Given the situation let us set up the Jira signup mailing list following
> the Calcite model. This seems the most
Hi Martjin,
Given the situation let us set up the Jira signup mailing list following
the Calcite model. This seems the most sensible to me as of now.
On Fri, Nov 11, 2022 at 7:26 PM Martijn Visser
wrote:
> Hi everyone,
>
> Unfortunately ASF Infra has already implemented the change and new Jira
Hi everyone,
Unfortunately ASF Infra has already implemented the change and new Jira
users can't sign up.
I think there is consensus that we shouldn't move from Jira now. My
proposal would be to setup a separate mailing list to which users can send
their request for an account, which gets sent
Thanks all for the valuable feedback, opinions and suggestions.
# Option 1.
I know this is the first choice for pretty much everyone. Many people from
the Flink community (including myself) have shared their opinion with
Infra. However, based on the feedback so far, TBH I don't think things
would
Calcite just requested a separate mailing list for users to request a
JIRA account.
I think I'd try going a similar route. While I prefer the openness of
github issues, they are really limited, and while some things can be
replicated with labels (like fix versions / components), things like
Hi,
I'm afraid of the migration cost to only github issues and lack of many
features that we are currently using. That would be very disruptive and
annoying. For me github issues are far worse compared to using the Jira.
I would strongly prefer Option 1. over the others. Option 4 I would like
Hi,
We have to keep in mind that if a users asks for a new Jira account, that
person will need to provide its email address which is the Flink PMC
processing personal identifiable information. There needs to be a careful
process for that and to be honest, I don't think the ASF should do this
from
Hello,
I agree with Gyula. My preference is also option 1, and as a fallback
option 3. Handling new user account requests will be manageable, especially
via slack. We could setup a dedicated channel for people to ask for
Jira/wiki access.
Thanks,
Danny
On Wed, 26 Oct 2022, 12:16 Gyula Fóra,
Hi!
I would also personally prefer staying with JIRA given the feature set and
the past positive experience with it.
I think the structured nature of JIRA with flexible components, issue
types, epics, release handling etc have been a great benefit to the
project, it would be a shame to give some
Thank you for starting this discussion Xintong!
I would also prefer option 1.
The ASF Jira is probably one of the largest, public Jira instances on the
internet. Most other Jiras are internal within companies, so Atlassian is
probably not putting a lot of effort into automatically detecting and
Hi everyone,
while I see some benefits in moving to Github Issues completely, we need to
be aware that Github Issues lacks many features that Jira has. From the top
of my head:
* there are no issue types
* no priorities
* issues can only be assigned to one milestone
So, you need to work a lot
I agree that leaving everything as is would be the best option. I also tend
to lean towards option 4 as a fallback for the reasons already mentioned.
I'm still not a big fan of the Github issues. But that's probably only
because I'm used to the look-and-feel and the workflows of Jira. I see
I agree with you that option 1) would be the best for us. Let's keep hoping
for the best.
Option 4), as you said, comes with prices. At the moment, I don't have
thorough answers to your questions.
Just one quick response, I think there's a good chance that we can import
current Jira tickets into
Hi Xintong,
I'm also not in favour of option 2, I think that two systems will result in
an administrative burden and less-efficient workflow. I'm also not in
favour of option 3, I think that this will result in first time
users/contributors in not-filling their first bug report, user question or
Hi devs and users,
As many of you may have already noticed, Infra announced that they will
soon disable public Jira account signups [1]. That means, in order for
someone who is not yet a Jira user to open or comment on an issue, he/she
has to first reach out to a PMC member to create an account
19 matches
Mail list logo
