> When users want Jira access, do they use an Apache account, or can it be any account?
Folks who have an Apache account (e.g. committers, PMC members, etc.) automatically have access to the ASF Jira instance. > Or are we just creating jira-specific accounts for these users? If you don't have an Apache account and you want to create a Jira, for example, then you must request a Jira account. This is an account specifically for the ASF Jira instance. Lots of websites employ OAuth so that you can, for example, use your Google account or Facebook account to access their services. That's not true of ASF Jira. You must have a specific ASF Jira account. > Do they have / need-to-have an ICLA signed and on-file? No. > It seems to me the real issue at heart here is avoiding spam, and using authenticated users as a means to that end. So, I'm trying to understand whether that's feasible with Apache Jira. As far as I know ASF Infra has _always_ required an account to create Jiras, etc. However, that requirement still hasn't been sufficient to prevent spam - even with a captcha for creating an account. Therefore, the PMC now has to approve Jira account requests. Justin On Wed, Apr 3, 2024 at 11:10 AM Arthur Naseef <a...@amlinv.com> wrote: > I read through Justin's document up to the section "Why Use GitHub > Issues?" and have questions. > > When users want Jira access, do they use an Apache account, or can it > be any account? Or are we just creating jira-specific accounts for > these users? Do they have / need-to-have an ICLA signed and on-file? > > It seems to me the real issue at heart here is avoiding spam, and > using authenticated users as a means to that end. So, I'm trying to > understand whether that's feasible with Apache Jira. > > Art > > P.S. Nice write-up Justin - thank you! > > On Wed, Apr 3, 2024 at 2:16 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > > Hi Justin > > > > Fantastic work and great summary ! > > > > I do a quick pass, I will do a more detailed read. > > > > Thanks ! > > Regards > > JB > > > > On Tue, Apr 2, 2024 at 9:52 PM Justin Bertram <jbert...@apache.org> > wrote: > > > > > > There's been a few threads about this general subject, but most have > > > concentrated on Classic in particular. I think it's worth discussing > > > migration of ActiveMQ as a whole and diving a bit deeper into the > details > > > of why a migration makes (or doesn't make) sense and what the > challenges > > > may be. > > > > > > To this end I've put together this document [1]. I hope it will be of > > > service to the community as we consider this option. > > > > > > > > > Justin > > > > > > [1] > > > > https://github.com/jbertram/activemq-website/wiki/Apache-ActiveMQ-GitHub-Issues-Migration-Review > >
