[jira] [Commented] (COMDEV-531) Unable to submit report via reporter.a.org

2023-08-05 Thread Sebb (Jira)


[ 
https://issues.apache.org/jira/browse/COMDEV-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751343#comment-17751343
 ] 

Sebb commented on COMDEV-531:
-

This is probably related to WHIMSY-404, however the lack of info shown by 
Reporter makes it hard to know.

> Unable to submit report via reporter.a.org
> --
>
> Key: COMDEV-531
> URL: https://issues.apache.org/jira/browse/COMDEV-531
> Project: Community Development
>  Issue Type: Bug
>Reporter: Philipp Ottlinger
>Priority: Major
>
> When I tried to file the Creadur report I was able to properly edit the 
> report, but when hitting "Publish via Whimsy" all I get is:
> "Something went wrong, and we couldn't publish your report.
> Please check with the Whimsy tool to see if there is already a report posted!"
> Not sure what else to add ... thus so unspecific.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org



[jira] [Moved] (COMDEV-531) Unable to submit report via reporter.a.org

2023-08-05 Thread Sebb (Jira)


 [ 
https://issues.apache.org/jira/browse/COMDEV-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb moved WHIMSY-403 to COMDEV-531:


 Key: COMDEV-531  (was: WHIMSY-403)
Workflow: classic default workflow  (was: jira)
difficulty-level: Easy
 Project: Community Development  (was: Whimsy)

> Unable to submit report via reporter.a.org
> --
>
> Key: COMDEV-531
> URL: https://issues.apache.org/jira/browse/COMDEV-531
> Project: Community Development
>  Issue Type: Bug
>Reporter: Philipp Ottlinger
>Priority: Major
>
> When I tried to file the Creadur report I was able to properly edit the 
> report, but when hitting "Publish via Whimsy" all I get is:
> "Something went wrong, and we couldn't publish your report.
> Please check with the Whimsy tool to see if there is already a report posted!"
> Not sure what else to add ... thus so unspecific.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org



AW: [DRAFT] Email to all PMCs or Committers

2023-08-05 Thread Christofer Dutz
Hi all,

So, I think we should stay with Rich’s version of the email.
Now to the next question … which list should we post this to?
And what do you think should we define as a date when we’ll switch?
As far as I understood things, Infa merges PRs like mine on Thursdays.
How much time to we want to give people to adjust their .asf.yml?

Do 4 weeks make sense, or would a shorter time be better?
(I mean … we all know that it really doesn’t matter if you give people a week 
or a year … they’ll always be surprised)

The range I’m ok with would be 2 weeks up to 4 weeks but wouldn’t really think 
we should go beyond that.

What do you think?


Chris

Von: rbo...@rcbowen.com 
Datum: Freitag, 4. August 2023 um 15:39
An: dev@community.apache.org 
Betreff: Re: [DRAFT] Email to all PMCs or Committers
On Fri, 2023-08-04 at 15:26 +0200, Jarek Potiuk wrote:
> +1. Looks way better.

Updated draft, for the sake of having it in the archive:



Subject: Mailing list threading improvements
Dear {Committers/members of the Apache PMCs},

TL;DR: We’re updating how auto-generated email from Github will be
threaded on your mailing lists. If you want to keep the old defaults,
details are below.

We’re pleased to let you know that we’re tweaking the way that auto-
generated email from Github will appear on your mailing lists. This
will lead to more human-readable subject lines, and the ability of most
modern mail clients to correctly thread discussions originating on
Github.

Background: Many project mailing lists receive email auto-generated by
Github. The way that the subject lines are crafted leads to messages
from the same topic not being threaded together by most mail clients.
We’re fixing that.

The way that these messages are threaded is defined by a file -
.asf.yml - in your git repositories. We’re changing the way that it
will work by default if you don’t choose settings. If you’re happy for
us to make this change, don’t do anything - the change will happen on
{DATE}.

Details of the current default, as well as the proposed changes, are on
the following page, along with instructions on how to keep your current
settings, if you prefer:

https://community.apache.org/contributors/mailing-lists.html#configuring-the-subject-lines-of-the-emails-being-sent

Please copy dev@community.apache.org on any feedback.

Chris, on behalf of the Comdev PMC

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org