Hi Everyone, We are currently in the process of setting up and moving to a public Jira instance to manage many of our development issues. The first part of this move involves setting up a request for comments (RFC) process which will be implemented using a Jira project. You can find out more about the RFC process in the first RFC: https://sel4kernel.atlassian.net/browse/RFC-1 You are encouraged to leave feedback on the issue, but doing so requires that you are logged in with an Atlassian Cloud account. The introduction of a public issue tracker will allow us to better engage with our community, accept more contribution from outside the seL4 development team, and better communicate the ways in which we are changing and improving the seL4 ecosystem. In the long term, we hope to use this to track all of the major issues currently under development across the ecosystem, accept issues submitted by the public, and open issues up for members of the greater community to work on. The issue tracker will initially be used as the basis of the RFC process, which will allow for the community to get involved with larger changes to the ecosystem. Many of the details of the process can only be clearly resolved as it becomes used more regularly as part of ongoing development, so much of how it works is still to be determined. We are hoping to finalise this process at the beginning of the new year before we use it to present a number of other changes we have been planning so we can get your feedback before their design and implementation is finalised. This new issue tracker and RFC process are just part of greater ongoing changes on which we are working to grow the community and to increase its involvement. We wish you all a happy holiday season and look forward to the start of a new year with seL4. Cheers, Curtis
This is great news! I'm hoping it's the leading edge for visibility into
other parts of the project – CI, bugs, etc.
Had you considered using a GitHub repository, as Rust does? It might help
with some of the drawbacks noted, particularly tracking changes and reviews.
On Tue, Dec 18, 2018 at 4:35 PM
The introduction of a public issue tracker will allow us to better engage with our community, accept more contribution from outside the seL4 development team, and better communicate the ways in which we are changing and improving the seL4 ecosystem.
Had you considered using a GitHub repository, as Rust does? It might help with some of the drawbacks noted, particularly tracking changes and reviews.
That had been considered, but in an effort to consolidate the process of both proposal and implementation into one location we decided to not use a git repository. If we find that the proposed system is insufficient we may revise this in the future.
participants (2)
-
Curtis.Millar@data61.csiro.au
-
Jeff Waugh