[Chaoss-members] Proposal for a FOSDEM devroom
Jesus M. Gonzalez-Barahona
jgb at bitergia.com
Wed Sep 13 20:21:45 UTC 2017
BTW, I will include your name as a backer of the proposal, maybe with
some others if I have their approval.
In your case, I will assume that you're ok if I use your name and
affiliation, as it is in the list of board members, except that you
tell me otherwise (sorry for the opt-out, but deadline is getting
closer, and I completely forgot asking you about this during our
On Tue, 2017-09-12 at 14:04 -0700, Jesus M. Gonzalez-Barahona wrote:
> Thanks for the comments!
> Find below a new version of the proposal (with the changes proposed
> Ray), which I will submit to FOSDEM, if nobody opposes.
> * Proposal for a FOSDEM devroom: FOSS Development Analytics*
> ** Main objectives **
> To reinforce the emerging community interest in FOSS (free, open
> software) development analytics.
> More specifically:
> - To discuss the current status of FOSS tools in this area
> - To share models about FOSS health and sustainability based on
> - To share experiences by FOSS projects already doing their own
> - To find ways of pooling development effort and other resources
> - To explore the requirements and functionality of future platforms
> ** Summary **
> Tools and platforms for analyzing and visualizing information from
> software repositories (source code management, bug reporting /
> ticketing, code review, mailing lists, etc.) are flourishing. Many of
> them are proprietary, which means that in many cases, FOSS (free,
> source software) projects are using proprietary tools to analyze
> There is also a lot of interest in models to evaluate the health,
> quality or sustainability of FOSS projects, based on factual data
> retrieved mainly from their repositories. But there are little
> opportunities of sharing these interests, and the experiences in
> building and applying these models, in venues where all stakeholders
> are represented: developers, academics, project managers, users, etc.
> We believe that the FOSS development model is especially well suited
> for being applied in both cases. In fact, many projects are already
> developing software and setting up platforms for analyzing their own
> repositories, some FOSS systems and tools do exist for retrieving,
> analyzing and visualizing information about FOSS development, and
> health and quality models for FOSS are being created and discussed
> using practices quite similar to those of FOSS development.
> If a certain critical mass is reached in this domain, it is
> to assume that usual mechanisms observed in FOSS development will
> enable continuous innovation and the quick improvement of the
> capabilities of these tools and models.
> The FOSS Development Analytics devroom intends to be an open venue to
> present these models, tools, and analysis that are already under
> development, and to discuss about collaboration, synergies, etc. The
> devroom will be organized to foster discussion and finding of
> synergies, but also development of new tools and models, improvement
> existing ones, and spread the knowledge about what is being done and
> can be done in this area. Given that the devroom will happen in the
> context of FOSDEM, it will be focused on the needs, interests and
> contributions of FOSS developers.
> ** Backers **
> This proposal is put together by the CHAOSS group, which includes
> contributors from well known FOSS Foundations, companies producing
> tools for software development analytics, and academics with
> in analysis of FOSS projects. To ensure that the needs of the wider
> FOSS development community are met, CHAOSS is working with other
> parties, and together put together this list of people backing the
> proposal, and with interest in contributing to the success of the
> devroom (alphabetic order, all of them representing themselves,
> affiliation is only informative):
> The responsibility for the organization and coordination will be led
> the CHAOSS group, in a way as inclusive and open as possible.
> * CHAOSS Group: http://chaoss.community
> ** Participants **
> Participation as speaker in the devroom will be subject to an open
> for contributions. This call will be communicated through mailing
> and social media channels related to the subject, in which the
> of the proposal participate.
> The backers of this proposal commit to prepare at least five
> presentations for the devroom, which will be submitted through the
> call. They will be subject to the same review and selection process
> than the other proposals.
> In addition, anyone could attend, provided there is space.
> between speakers and other attendants will be promoted as much as
> ** Organization **
> An organizing committee will be established to promote the devroom,
> open call, and the organization in general. It will be composed by
> backers, plus some other persons related to the subject of the
> It will be as much inclusive as possible, giving voice to FOSS
> and developers interested in the subject.
> The organizing committee will produce the call for contributions,
> will be based on this proposal. They will receive all proposals, and
> will openly discuss about how to better accommodate as many of them
> possible, while at the same time fostering discussion and reserving
> some slots for open interaction.
> The devroom will include some time for demos and live explanations of
> how to use FOSS applications for analyzing software development,and
> models of FOSS health, specifically focused to FOSS developers.
> All the materials used in the talks, demos and other activities will
> published under free culture licenses.
> Since this is the first year the devroom will be celebrated, we
> envision having a half-day (morning or afternoon) devroom, but a full
> day devroom will also be possible.
/me at Twitter: https://twitter.com/jgbarah
More information about the Chaoss-members