(formerly Solutions Integration Community)
Regardless of how we are using Fedora, or what types of content we are putting into it, we all have a number of common technical challenges that we must all overcome. One of the greatest strengths of Fedora Commons is the fact that it has an active and innovative community of software architects, developers, archivists and librarians working to tackle those challenges in ways that range from pragmatic to visionary.
We've formed a Solutions Community around identifying, documenting, discussing, and solving these technical challenges that we must all face.
Read about the Solutions Integration Community if you would like to know more about the community, this section of the wiki, and how you can get involved.
Until then, let's get to work.
These are areas of technical difficulty that we are all facing together. For each of these topics, there are at least a handful of people who are actively working to reduce these challenges to non-issues. Are you one of those people? If you are, make sure we all know about your work, and make sure it's reflected here on the wiki.
These are areas of technical interest that the Fedora Community takes special interest in discussing
This list is intended for discussions between committers and testers of the Fedora Commons source code. Tech-heavy discussions of application integration problems seem to show up here too. There has been some discussion of creating a separate fedora-commons-tech list for those discussions.
We keep talking about setting this up, but it's not clear that people will use it. If you would like to make this happen, please stand up.
Many developers working with Fedora maintain blogs. They also actively refer to the blogs of other developers working in related fields.
Not Fedora, but still worth watching
Visit the recommended reading, which contains some recommended posts from many of these blogs (this is only updated periodically).