This is still possible to ask for access if you want. Just let us know your confluence ID and we will give you read access.
We have > 2200 contributors to the project and since we closed JIRA it has happened 2 times that people asked for access to an issue so far. So I think it's not at all "many people like you". And this is always a good opportunity to explain that looking at JIRA makes no sense any more. Those old JIRA issues in the absolute vast majority of cases contain no extra context because they were just empty placeholders (JIRA was basically very rarely used, compared to GitHub Issues and Discussions). And having the project opened, made people mistakenly think that JIRA issues are still "the" project issue tracking and - made them mislead. I very much prefer that people like you ask for access rather than continue silently looking at JIRA and - for example - expecting that some of the issues there will be treated somehow and responded to. We are - collectively as a community - focused on the future of the project, not about distant past (especially that pretty much all meaningful past is now in GitHub Issues and discussions - and above all in devlist and in the code/git history. But again, if you really want - we can give you - personally - read access, no problem with that, we've done that for those 2 cases. If anyone else needs the access - feel free to ask here. J, On Thu, Oct 27, 2022 at 9:27 AM 杜文昊 <ggbo...@gmail.com> wrote: > I am not a apache airflow member, but i am reading apache airflow source, > not just use it. > I want to look some history issue to understand some code design reason. > But I have not enough permissions to do it. > > I search this information in dev list. > https://lists.apache.org/thread/g4sc91y585ypc7tgphlhvxt3v8nqsg5d > https://issues.apache.org/jira/browse/INFRA-23386 > > In the history of git, jira issue id in the commit message. > If you can continue public these issues, it will be the most convenient way > to obtain information. > > If you want prevent search engines to stop indexing those and casual users > not see it. > Only disable read permissions for anonymous user is enough. > > Many people like me who wish into the source code implementation, although > we are not airflow members, > but really need to continue reading it. >
