Thank you!
> On May 27, 2023, at 2:47 AM, Benjamin Marwell wrote:
>
> Since we all agreed here, I will now open the GitHub issues and discussions
> in the next few days. If you're faster than me, feel welcome to do it
> earlier. 😉
>
> - Ben
>
>
>
>
> On Thu, 27 Apr 2023, 14:39 Benjamin Marw
Since we all agreed here, I will now open the GitHub issues and discussions
in the next few days. If you're faster than me, feel welcome to do it
earlier. 😉
- Ben
On Thu, 27 Apr 2023, 14:39 Benjamin Marwell, wrote:
> +1 for starting fresh.
> Since github is easier to get to, we will soon hav
+1 for starting fresh.
Since github is easier to get to, we will soon have enough issues to work
on. ;-)
Am Mi., 26. Apr. 2023 um 17:31 Uhr schrieb Colm O hEigeartaigh <
cohei...@apache.org>:
> +1, especially since new users having to manually be approved to signup to
> JIRA.
>
> Colm.
>
> On We
+1, especially since new users having to manually be approved to signup to JIRA.
Colm.
On Wed, Apr 26, 2023 at 3:38 PM Brian Demers wrote:
>
> That's a great point!
> Nothing is stopping us from cutting over to GH now and then figuring out
> the JIRA migration in the future (or not). 🤔
>
>
> On
That's a great point!
Nothing is stopping us from cutting over to GH now and then figuring out
the JIRA migration in the future (or not). 🤔
On Wed, Apr 26, 2023 at 6:23 AM Francois Papon
wrote:
> Hi Brian,
>
> Thanks for sharing that!
>
> I think we could start by making JIRA read-only start fr
Hi Brian,
Thanks for sharing that!
I think we could start by making JIRA read-only start fresh in GH, it
would be the less effort way for us.
regards,
François
I don't think we need something as complex as this, but some linked threads
make good points about only needing to search one loca
I've been doing some digging as to _how_ we would automate the migration.
The Arrow project went through a similar process:
https://github.com/apache/arrow/issues/14542
I assume these are the scripts;
https://github.com/rok/arrow-migration/tree/main
I don't think we need something as complex as t
+1 for me, no objections.
Regards
JB
On Fri, Mar 31, 2023 at 3:40 PM Brian Demers wrote:
>
> We received a suggestion from the last board report to consider switching
> from JIRA to GitHub issues.
>
> The ASF JIRA instance no longer allows users to self-sign-up (though it
> DOES allow us to invi
make sense, +1 from my side :)
regards,
François
On 31/03/2023 15:40, Brian Demers wrote:
We received a suggestion from the last board report to consider switching
from JIRA to GitHub issues.
The ASF JIRA instance no longer allows users to self-sign-up (though it
DOES allow us to invite other
Big +1
On Sat, 1 Apr 2023, 01:31 , wrote:
> BIG +1 for me.
> Even easier, just have old issues in JIRA and new ones in GH.
> Also maybe GH discussions as well?
>
> > On Mar 31, 2023, at 8:40 AM, Brian Demers wrote:
> >
> > We received a suggestion from the last board report to consider switc
BIG +1 for me.
Even easier, just have old issues in JIRA and new ones in GH.
Also maybe GH discussions as well?
> On Mar 31, 2023, at 8:40 AM, Brian Demers wrote:
>
> We received a suggestion from the last board report to consider switching
> from JIRA to GitHub issues.
>
> The ASF JIRA instanc
We received a suggestion from the last board report to consider switching
from JIRA to GitHub issues.
The ASF JIRA instance no longer allows users to self-sign-up (though it
DOES allow us to invite others). This is largely due to spam.
Most developers have a GitHub account (and that is where most
12 matches
Mail list logo
