| <?xml version="1.0" encoding="utf-8"?> |
| <feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Infrastructure Website</title><link href="https://infra.apache.org/" rel="alternate"></link><link href="https://infra.apache.org/feeds/all-en.atom.xml" rel="self"></link><id>https://infra.apache.org/</id><updated>2024-04-25T00:00:00+00:00</updated><entry><title>Inside Infra April 2024</title><link href="https://infra.apache.org/blog/inside-infra-april-2024.html" rel="alternate"></link><published>2024-04-25T00:00:00+00:00</published><updated>2024-04-25T00:00:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2024-04-25:/blog/inside-infra-april-2024.html</id><summary type="html"><p>Welcome to <em>Inside Infra</em> for April, 2024.</p> |
| <h2>Infra Reporting Dashboard</h2> |
| <p>The dashboard, at <a href="https://infra-reports.apache.org/" target="_blank">infra-reports.apache.org</a>, provides a collection of reports on the overall health and activity of the infrastructure at the ASF. These reports can be helpful in understanding the status of all the ASF 'under the hood' resources …</p></summary><content type="html"><p>Welcome to <em>Inside Infra</em> for April, 2024.</p> |
| <h2>Infra Reporting Dashboard</h2> |
| <p>The dashboard, at <a href="https://infra-reports.apache.org/" target="_blank">infra-reports.apache.org</a>, provides a collection of reports on the overall health and activity of the infrastructure at the ASF. These reports can be helpful in understanding the status of all the ASF 'under the hood' resources, and in assessing the resource cost of some activities, like build processes.</p> |
| <p>Some of the reports are open to the public, while others are restricted to those who genuinely need them; see the documentation at <a href="https://infra.apache.org/infra-reports.html" target="_blank">infra.apache.org/infra-reports.html</a>.</p> |
| <h2>MFA at the ASF</h2> |
| <p>Infra is working on policies to cover use of multi-factor authorization (MFA) at The ASF, and tooling to support and enable those policies. The goal is to provide the best-possible security for user accounts at the lowest reasonable level of disruption to work processes.</p> |
| <p>The draft of the main MFA policy, with a link to the policy on restoring MFA when someone has lost a key element of it, is available at <a href="https://infra.apache.org/mfa.html" target="_blank">infra.apache.org/mfa.html</a>. </p> |
| <p>As we refine the policy and bring the tools to support it online, we will update the policy page. We will make a general announcement when we are close to bringing MFA live for The ASF and its projects.</p> |
| <h2>Roundtable</h2> |
| <p>There was no April roundtable.</p> |
| <p>The May Roundtable will be on Wednesday, May 8, 2024, 1700 UTC. The topic of the day will be "How PMCs can use the STeVe voting tool", with a live demonstration. There will probably also be time for unstructured discussion about other issues and concerns related to infrastructure. </p> |
| <p>Info about the roundtables is at <a href="https://infra.apache.org/roundtable.html" target="_blank">infra.apache.org/roundtable.html</a>.</p> |
| <h2>Access to the Confluence Wiki</h2> |
| <p>To deal with the creation of spammy accounts and risks to ASF and project information on the wiki, we have limited account-creation: committers and ASF members can automatically log in to the ASF Confluence Wiki without creating an account. At the moment people who do not have an ASF LDAP account <strong>cannot</strong> create an account in the wiki.</p> |
| <hr/> |
| |
| <p>The next issue of <em>Inside Infra</em> will appear near the end of May, 2024.</p></content><category term="blog"></category></entry><entry><title>Inside Infra March 2024</title><link href="https://infra.apache.org/blog/inside-infra-march-2024.html" rel="alternate"></link><published>2024-03-23T00:00:00+00:00</published><updated>2024-03-23T00:00:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2024-03-23:/blog/inside-infra-march-2024.html</id><summary type="html"><p>Welcome to <strong>Inside Infra</strong> for March, 2024.</p> |
| <h3>Policy change on use of GitHub Actions</h3> |
| <p>Due to misconfigurations in their builds, some projects have been using unsupportable numbers of GitHub Actions. As part of fixing this situation, Infra has added a 'resource use' section to the policy on GitHub Actions. This …</p></summary><content type="html"><p>Welcome to <strong>Inside Infra</strong> for March, 2024.</p> |
| <h3>Policy change on use of GitHub Actions</h3> |
| <p>Due to misconfigurations in their builds, some projects have been using unsupportable numbers of GitHub Actions. As part of fixing this situation, Infra has added a 'resource use' section to the policy on GitHub Actions. This section of the policy will come into effect on <strong>April 20, 2024</strong>:</p> |
| <ul> |
| <li>All workflows MUST have a job concurrency level less than or equal to 20. This means a workflow cannot have more than 20 jobs running at the same time across all matrices.</li> |
| <li>All workflows SHOULD have a job concurrency level less than or equal to 15. Just because 20 is the max, doesn't mean you should strive for 20.</li> |
| <li>The average number of minutes a project uses per calendar week MUST NOT exceed the equivalent of 25 full-time runners (250,000 minutes, or 4,200 hours).</li> |
| <li>The average number of minutes a project uses in any consecutive five-day period MUST NOT exceed the equivalent of 30 full-time runners (216,000 minutes, or 3,600 hours).</li> |
| <li>Projects whose builds consistently cross the maximum use limits will lose their access to GitHub Actions until they fix their build configurations.</li> |
| </ul> |
| <p>The full policy is at <a href="https://infra.apache.org/github-actions-policy.html" target="_blank">https://infra.apache.org/github-actions-policy.html</a>.</p> |
| <h3>Roundtable summary</h3> |
| <p>In the Roundtable of March 3, 2024, Clay Johnson of Gradle outlined the testing features that come with Develocity, focussing on their use with Gradle and Maven. For instance:</p> |
| <ul> |
| <li>The build scan gives insights into what goes on in a build, and can help a project quickly focus on tests that are failing or flaky, and address related code issues.</li> |
| <li>Predictive test selection can speed up certain types of builds by skipping the tests that are not relevant to the build.</li> |
| </ul> |
| <p>A fuller summary of this discussion, and conversation about GitHub Runners and other topics, is at <a href="https://cwiki.apache.org/confluence/display/INFRA/Infra+Roundtable+2024-03-06%2C+17%3A00+UTC" target="_blank">https://cwiki.apache.org/confluence/display/INFRA/Infra+Roundtable+2024-03-06%2C+17%3A00+UTC</a>, and is available to ASF Members and Committers.</p> |
| <p><strong>Note</strong>: There will be <strong>no April 2024 Roundtable</strong>. The series will resume in May.</p> |
| <h3>The end of Apache Paste Bucket?</h3> |
| <p>In 2013 Infra rolled out Apache Paste Bucket (<code>http://paste.apache.org/</code>). In a blog entry at the time, we described it as an "ASF-driven site for posting snippets, scripts, logging output, configurations and much more and sharing them with the world."</p> |
| <p>The tool has seen some use over the past decade, but has had very little traffic in the last couple of years. To keep Apache Paste Bucket available, the code would require a significant upgrade. Unless we hear that the tool is important to some part of the ASF community, we plan to shut down Apache Paste in the near future.</p> |
| <hr/> |
| <p>The next newsletter will appear toward the end of April, 2024.</p></content><category term="blog"></category></entry><entry><title>Inside Infra February 2024</title><link href="https://infra.apache.org/blog/inside-infra-february-2024.html" rel="alternate"></link><published>2024-02-20T00:00:00+00:00</published><updated>2024-02-20T00:00:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2024-02-20:/blog/inside-infra-february-2024.html</id><summary type="html"><p><em>Hello, all!</em></p> |
| <h2>Newsletter name</h2> |
| <p>Our very unscientific poll showed that "Inside Infra" has the most support as a name for this newsletter, so that is what we shall be. </p> |
| <p><strong>Note</strong>: in 2020 the main ASF blog published a series of interviews with Infra team members also called "Inside Infra". Links …</p></summary><content type="html"><p><em>Hello, all!</em></p> |
| <h2>Newsletter name</h2> |
| <p>Our very unscientific poll showed that "Inside Infra" has the most support as a name for this newsletter, so that is what we shall be. </p> |
| <p><strong>Note</strong>: in 2020 the main ASF blog published a series of interviews with Infra team members also called "Inside Infra". Links to the interviews are available at <a href="https://cwiki.apache.org/confluence/display/INFRA/The+Infrastructure+team" target="_blank">The Infrastructure team</a>.</p> |
| <h2>2023 year-end survey</h2> |
| <p>We held our second annual year-end survey and got a lot of participation. Overall satisfaction with Infra's work seems high, but there were also a series of very useful suggestions and ideas. This newsletter, in fact, is a response to one of the suggestions.</p> |
| <p>The survey summary is on our <a href="https://infra.apache.org/blog/2023%20Infra%20Survey%20Results.html" target="_blank">blog</a>.</p> |
| <h2>Roundtable summary</h2> |
| <p>The February Roundtable focused on Keycloak and related security issues but, as is often the case, conversation also moved usefully into several other areas and concerns, including:</p> |
| <ul> |
| <li>There is concern that it is difficult to find a link to Infra's website, or even know that it exists, from the main ASF website.</li> |
| <li>A suggestion to develop project-level security groups for GitHub Issues, based on roles.</li> |
| <li>There should be a CalDev service that would support an events calendar for each project that wants one.</li> |
| <li>There was discussion of trying to find a forum solution that could in time replace the requirement for email-based conversation threads for project decisions.</li> |
| <li>The summary of the conversation is on the Infra Confluence wiki.</li> |
| </ul> |
| <p>The next Infra Roundtable will be <strong>March 6, 2024 1700 UTC</strong>. The main topic, before the suggestions start to fly, will be <strong>improving automated testing</strong>.</p> |
| <p>Of note: Develocity is hoping to roll out predictive test / flaky test analysis, to help projects improve their test suites so they generate more reliable results.</p> |
| <p>Information on how the roundtables work, and how to join in, is at <a href="https://infra.apache.org/roundtable.html" target="_blank">infra.apache.org/roundtable.html</a>.</p> |
| <h2>.asf.yaml info available</h2> |
| <p>.asf.yaml is an important tool in managing project websites and other services. It is a branch-specific configuration file that a project may create and put in the root of a Git repository to control features such as</p> |
| <ul> |
| <li>notification schemes</li> |
| <li>website staging</li> |
| <li>GitHub settings</li> |
| <li>Pelican builds</li> |
| </ul> |
| <p>The documentation for .asf.yaml was on the Infra Cwiki, but is now is in its repository's README file: <a href="https://github.com/apache/infrastructure-asfyaml/blob/main/README.md" target="_blank">github.com/apache/infrastructure-asfyaml/blob/main/README.md</a>.</p> |
| <h2>Self-serve and wiki accounts</h2> |
| <p>An addition to the Apache self-serve tool will let a user request a Cwiki account. The request goes for approval to the project the user specifies. The project can also grant the user write access, should that be desired.</p> |
| <p>This feature is not yet available, but is coming soon.</p> |
| <h2>Delivery issues with Gmail</h2> |
| <p>If you are subscribed to an ASF mailing list with a Gmail account, you may experience missing list mail. This is due to changes Google made that cause rejection of ASF mailing list mail to Gmail addresses. Infra is currently investigating this issue.</p> |
| <p>If you or your project experience this, Infra has a workaround which we can apply to your mailing list, but some messages may |
| still be rejected.</p> |
| <h2>Excellent questions</h2> |
| <p>Some of the best stuff Infra does has evolved from project members' questions and suggestions. If you have an infrastructure-related question, feel free to ask it on the <code>users@infra.apache.org</code> email list. We may share your question, and our answer to it, in a coming newslette</p> |
| <p><em>That's it until next month!</em></p></content><category term="blog"></category></entry><entry><title>2023 Infra Survey Results</title><link href="https://infra.apache.org/blog/2023-infra-survey-results.html" rel="alternate"></link><published>2024-02-13T00:00:00+00:00</published><updated>2024-02-13T00:00:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2024-02-13:/blog/2023-infra-survey-results.html</id><summary type="html"><p>More than 50 people posted responses to our 2023 'year in review' survey. Here is a summary of the responses to questions and the comments added in each section.</p> |
| <p>We're grateful to those who took the time to fill out the survey. Without feedback like this, the Infra team can …</p></summary><content type="html"><p>More than 50 people posted responses to our 2023 'year in review' survey. Here is a summary of the responses to questions and the comments added in each section.</p> |
| <p>We're grateful to those who took the time to fill out the survey. Without feedback like this, the Infra team can feel a bit like it is flailing around in the dark.</p> |
| <h2>Summary of responses</h2> |
| <h3>Infra Roundtables</h3> |
| <p>82% of survey respondents have attended an Infra Roundtable</p> |
| <p>Some reasons for not having attended include:</p> |
| <ul> |
| <li>Time constraints (most frequent response)</li> |
| <li>Was not aware it existed</li> |
| <li>Do not need it / no pressing issues</li> |
| <li>Timezone issues (the roundtables frequently happen at a time which is more convenient to people in Europe and North American than in Asia)</li> |
| </ul> |
| <p>88.9% say the roundtables ‘provide value’.</p> |
| <p>Topics respondents would like roundtables to address:</p> |
| <ul> |
| <li>Things Infra is working on that might be useful to PMCs</li> |
| <li>Vulnerability scanning</li> |
| <li>Automation of<ul> |
| <li>voting</li> |
| <li>policy compliance verification</li> |
| <li>releases</li> |
| </ul> |
| </li> |
| <li>Ways to make it easier for contributors to projects to contribute to Infra coding tasks</li> |
| <li>Periodic hackathons Infra hackathons open to all contributors</li> |
| <li>Series of FAQs / tutorials on common tasks at the ASF</li> |
| </ul> |
| <h3>Communication</h3> |
| <p>81% agreed that Infra is getting better at open communication.</p> |
| <p>Further communications improvement suggestions included:</p> |
| <ul> |
| <li>Periodic newsletter (implemented!)</li> |
| <li>Email announcements of important matters to all members</li> |
| <li>Better connection of each Infra service with its documentation</li> |
| <li>News box on the landing page at <code>infra.a.o</code> needs to be updated more frequently</li> |
| <li>Questions to <code>users@infra.a.o</code> seem to go unanswered</li> |
| <li>Be more consistent in showing latest and earlier versions of info on the wiki pages</li> |
| <li>Public archive containing summaries of all main points in all roundtables</li> |
| <li>Periodic publication of the basic stuff, such as 'Where is self-serve?'</li> |
| </ul> |
| <h3>Technical services</h3> |
| <p>95% feel Infra offers adequate technical services for their project.</p> |
| <p>Service improvement suggestions:</p> |
| <ul> |
| <li>Proactively improve the security posture of all ASF projects</li> |
| <li>Automating releases (this is coming!) and dependency upgrades for CVE mitigation</li> |
| <li>Free BSD runners and CI builder on GitHub</li> |
| <li>More docs and examples for VM setup via puppet</li> |
| <li>Password management solution</li> |
| <li>More powerful GitHub Action runners for all platforms</li> |
| <li>Video call service</li> |
| </ul> |
| <p>We asked which existing services need improvement. These areas got the most votes:</p> |
| <ul> |
| <li>CI/CD (Jenkins, BuildBot, GitHub Actions – 62%</li> |
| <li>Issue Tracking (Jira, GitHubIssues, Bugzilla) – 31%</li> |
| <li>Documentation / Wiki pages – 31%</li> |
| <li>Source control (GitHub/GitBox, SVN) – 19%</li> |
| <li>Messaging (Slack, mailing lists) – 19% </li> |
| </ul> |
| <p>Comments:</p> |
| <ul> |
| <li>Archived blog content is greatly bit rotted with no way to fix; no good modern blogging options</li> |
| <li>ASF project websites vary widely in visual appeal and functionality. How to make it easier to quickly set up ‘modern looking’ websites?</li> |
| <li>Issue tracking – automated scripts to migrate existing issues from Jira to GitHub Issues.</li> |
| <li>Fix tool sprawl – self-serve, whimsy, reporter, cveprocess...</li> |
| <li>Jenkins seems outdated. Would prefer something like Concourse.</li> |
| <li>Research an official Stack Overflow integration as an alternative to users’ lists?</li> |
| <li>In CI/CD, we don’t really have any CD. Where can we deploy test apps?</li> |
| <li>Docker Images.</li> |
| <li>More control over Docker Hub repos.</li> |
| <li>Builds are sometimes flaky because of disk-full error, broken hardware, missing build tools...</li> |
| <li>Builds are very slow for projects with a large number of modules and different workflows for different test suites. Such projects need more dedicated resources.</li> |
| <li>It’s easy for projects to configure build pipelines that don’t work well.</li> |
| <li>I shouldn’t have to create a filter to understand the context of an email from the ASF.</li> |
| <li>Struggling to find good documentation on Buildbot hosts, in particular for setting up a Windows build.</li> |
| <li>In a multilanguage project, Kotlin is not counted.</li> |
| <li>Mailing list noise from GitHub/GitBox. Drop messages from some bots.</li> |
| <li>Need a simple build caching solution for Jenkins so we can cache Maven repositories between builds</li> |
| <li>Need a good template for the static part of project websites. (Working on it!)</li> |
| <li>There is no documentation on cleanup after a build and main + subpath deployment of a website, nor an example to start with.</li> |
| <li>Long build queues on ASF Jenkins; problems with GHA builds</li> |
| <li>Jenkins builds should be containerized and isolated from one another, so one build does not bring down a node for everybody else. Need guaranteed minimum performance for performance-sensitive build tests.</li> |
| <li>Improve the messaging of Jira to the mailing lists.</li> |
| </ul> |
| <h3>New Year’s resolutions for projects:</h3> |
| <ul> |
| <li>Hope to make more frequent releases (multiple mentions).</li> |
| <li>Get it fully, reproducibly built with OID integration to release it via Trusted Publishing to PyPI.</li> |
| <li>Reduce ‘onboarding barriers’ and bridging projects for more synergy.</li> |
| <li>Add documentation tutorials.</li> |
| <li>Attracting more people to work on the documentation.</li> |
| </ul> |
| <h3>New Year’s hopes to get from Infra, the ASF, from your project</h3> |
| <ul> |
| <li>Easy to use and secure package and releasing platform (Working on it!)</li> |
| <li>More reliability</li> |
| <li>An arrangement with medium or substack</li> |
| <li>FreeBSD/BSD</li> |
| <li>More stability for Ubuntu Jenkins nodes</li> |
| <li>automated voting tool (Working on it!)</li> |
| <li>CI stabiity</li> |
| <li>More powerful GitHub Runners for all platforms</li> |
| </ul> |
| <h3>Feedback for the Infra team:</h3> |
| <p>Most of the comments were positive, with thanks for our efforts and good wishes for the new year.</p> |
| <p>And there was one “Well, there is that one guy...” (working on it!)</p></content><category term="blog"></category></entry><entry><title>The Infra Newsletter January 2024</title><link href="https://infra.apache.org/blog/the-infra-newsletter-january-2024.html" rel="alternate"></link><published>2024-01-20T00:00:00+00:00</published><updated>2024-01-20T00:00:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2024-01-20:/blog/the-infra-newsletter-january-2024.html</id><summary type="html"><p>Hi, all!</p> |
| <p>Someone who responded to our annual survey (see below) suggested that we start a newsletter to share developments and other news. The suggester thought we should send it to the <code>dev@</code> list of every PMC and PPMC, but we are going to start with a more limited distribution …</p></summary><content type="html"><p>Hi, all!</p> |
| <p>Someone who responded to our annual survey (see below) suggested that we start a newsletter to share developments and other news. The suggester thought we should send it to the <code>dev@</code> list of every PMC and PPMC, but we are going to start with a more limited distribution and see if the benefit to readers outweighs the additional email traffic. If you would like to get each issue in your email inbox, make sure you are subscribed to <code>users@infra.apache.org</code>.</p> |
| <p>The complete text of each month's newsletter appears here on the Infra blog.</p> |
| <p>Expect to see a new installment of the newsletter toward the end of each month. If you have suggestions, please share them in an email to <code>users@infra.apache.org</code>.</p> |
| <h2>The Infra year-end survey</h2> |
| <p>As we start 2024, we're using a survey to review infrastructure developments and plans for the ASF. We will compile responses into an anonymized report to share with the whole ASF community and to provide the Infrastructure team with insights that may help us improve our work in the new year. </p> |
| <p>If you have not had a chance to fill out the survey yet, <a href="https://forms.gle/rQwYykCuP3Z1ij5Z9" target="_blank">it is here</a>. It will be active until <strong>February 2, 2024</strong>.</p> |
| <h2>The Infra Roundtable</h2> |
| <p>Last year the Infrastructure team started holding monthly <strong>Roundtable</strong> meetings, in response to requests for a way to discuss infrastructure issues and initiatives. In 2023, we held ten such meetings, usually on the first Wednesday of each month. One meeting was face-to-face, as a part of Community Over Code North America.</p> |
| <p>Although an Infra member generally makes a brief presentation on some topic, this is not the sort of gathering where we talk and talk and you meekly listen. We enjoy hearing insights from all across the ASF universe, and some very good ideas have emerged from Roundtable meetings and become part of Infra's work plan.</p> |
| <p>The roundtables last an hour and take place in a huddle in the Infra channel in the Apache space on Slack. Instructions on how to join the roundtables are at <a href="https://infra.apache.org/roundtable.html" target="_blank">infra.apache.org/roundtable.html</a>.</p> |
| <p>Links to summaries of all meetings are at <a href="https://cwiki.apache.org/confluence/display/INFRA/Infra+Roundtable" target="_blank">cwiki.apache.org/confluence/display/INFRA/Infra+Roundtable</a>.</p> |
| <p>The next Roundtable will be <strong>Wednesday, February 7, 2024 1700 UTC</strong>, and we will focus on <a href="https://www.keycloak.org" target="_blank">Keycloak</a> and two factor authentication.</p> |
| <h2>Infra and conferences in 2024</h2> |
| <p>While Infra will be taking part in both <strong>Community over Code</strong> (CoC) <strong>Europe</strong> and <strong>CoC North America</strong> in 2024, we will not be able to send team members to <strong>CoC Asia</strong>. It would be great if anyone attending could pass on to us, by email or through our Slack channel, insights or issues discussed at the conference that are relevant to Infra.</p> |
| <h2>What's in a name?</h2> |
| <p>What should we call this thing? "The Infra Newsletter" is straightforward, but maybe not all that catchy. "Infractions", while being a cute mashup of "Infra" and "actions", may not be clear to readers for whom English is not their best language.</p> |
| <p>Use <a href="https://forms.gle/TCEDGdE9VHM45CGJA" target="_blank">this link</a> to vote for a name you prefer for the Infra newsletter: The poll is on Google Drive, but you do not have to log in to use it. The poll will stay open until <strong>February 5, 2024</strong>.</p></content><category term="blog"></category></entry><entry><title>Add your wisdom to Infra</title><link href="https://infra.apache.org/blog/add-your-wisdom-to-infra.html" rel="alternate"></link><published>2023-11-17T01:55:55+00:00</published><updated>2023-11-17T01:55:55+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2023-11-17:/blog/add-your-wisdom-to-infra.html</id><summary type="html"><p>Committers, contributors, and ASF Members have a wealth of information about every aspect of software and community development. When we share our knowledge, its reach multiplies and our effectiveness increases.</p> |
| <p>For the infrastructure that supports all our efforts at the ASF, here are some ways to share what you know …</p></summary><content type="html"><p>Committers, contributors, and ASF Members have a wealth of information about every aspect of software and community development. When we share our knowledge, its reach multiplies and our effectiveness increases.</p> |
| <p>For the infrastructure that supports all our efforts at the ASF, here are some ways to share what you know with the folks with the greatest need to hear it:</p> |
| <p><strong>Share your smarts</strong></p> |
| <p>If you join the <code>users@infra.apache.org</code> email list, you can help answer the many questions we receive related to our infrastructure: Where can I find X? How do I achieve Y? I am trying to do Z but getting this mystery error message.</p> |
| <p>The issues range in complexity. Any committer or ASF Member is well-positioned to answer all but the most gnarly ones.</p> |
| <p><strong>Join the Roundtables</strong></p> |
| <p>Infra holds regular roundtable discussions on important topics in the World of Infrastructure. These are not lectures, where an Infra member holds forth and everybody is supposed to sit in respectful silence. Rather, the Infra team is hoping to gain insights and guidance from members of the ASF community that will improve how the team works or a tool it is developing.</p> |
| <p>The roundtables usually take place on the <strong>first Wednesday of each month</strong>, on the <code>#roundtable</code> channel in the <code>the-ASF</code> workspace on Slack. They are available to anyone who can access the ASF workspace on Slack: basically, committers and Members. |
| - Here are <a href="https://infra.apache.org/roundtable.html" target="_blank">details about the Roundtables</a>, including information on joining the <code>#roundtable</code> channel. |
| - We don't record the sessions, but we do take <a href="https://cwiki.apache.org/confluence/display/INFRA/Infra+Roundtable" target="_blank">copious notes</a>.</p> |
| <p><strong>Build better builds</strong></p> |
| <p>A group meets regularly (usually the second Thursday of the month) in the <code>#builds</code> channel in the <code>the-ASF</code> workspace on Slack to explore issues related to builds of ASF projects' products. You are welcome whether you have a puzzle you need help solving, or some insights that may help others.</p> |
| <p><strong>Re-vision distribution</strong></p> |
| <p>Infra is starting to develop the <strong>Artifacts Distribution Platform</strong> (ADP). The idea is to consolidate <code>dist.apache.org</code>, <code>downloads.apache.org</code>, <code>rsync.apache.org</code> and <code>archive.apache.org</code> into one service that will free up resources and:</p> |
| <ul> |
| <li>simplify backups of release artifacts</li> |
| <li>remove the need to "police" projects about their release pages by no longer requiring them to manually archive older releases</li> |
| <li>ensure that all new releases follow our release policies by only allowing policy-compliant artifacts to be released</li> |
| <li>make it easier for product users to verify that what they are about to download is a certified ASF artifact</li> |
| </ul> |
| <p>We are assembling lists of necessary features, 'good to have' features, and ambitious pipe dreams, and value input from all across the The ASF's communities.</p> |
| <ul> |
| <li>Join the <code>artifacts@infra.apache.org</code> mailing list.</li> |
| <li>Ask to be invited to the <code>artifact-platform-dev</code> channel in the <code>the-ASF</code> workspace on Slack.</li> |
| <li>Review the <a href="https://cwiki.apache.org/confluence/display/INFRA/Artifacts+Distribution+Platform" target="_blank">current collection of ideas and issues</a> related to the ADP. Add your thoughts/concerns/insights in the editable pages linked to from that main page. (Note: we have already blue-skied a very complex application. If you suggest another component, we may invite you to help develop it.)</li> |
| </ul></content><category term="blog"></category></entry><entry><title>Infra blogs has a new home</title><link href="https://infra.apache.org/blog/infra-blogs-has-a-new-home.html" rel="alternate"></link><published>2022-10-24T12:54:00+00:00</published><updated>2022-10-24T12:54:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2022-10-24:/blog/infra-blogs-has-a-new-home.html</id><content type="html"><p>Just moved posts over from blogs.apache.org/infra. New posts all go through the infrastructure-website repo and it should be as easy as posting some markdown.</p></content><category term="blog"></category></entry><entry><title>index</title><link href="https://infra.apache.org/blog/index.html" rel="alternate"></link><published>2020-02-02T00:00:00+00:00</published><updated>2020-02-02T00:00:00+00:00</updated><author><name></name></author><id>tag:infra.apache.org,2020-02-02:/blog/index.html</id><content type="html"></content><category term="blog"></category></entry></feed> |
