Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor revisions, just changed the tense from present to past tense for many of the notes, for clarity

...

Some cross discussion about best ways to foster big development projects/large architectural changes in community-supported open source projects. A discussion of a need for better communication between committers and the community, possibly an information exchange about active development projects. Valorie Hollister points pointed out that there is a page for this information on the wiki, though it is later pointed out that the wiki page doesn't really provide a good way to track project status. Bram Luyten suggests the possibility to automatically track an "outside" project status by linking to other issue trackers and wikis, perhaps via RSS feeds.

Valorie Hollister spoke about DCAT:- a description of what it is, who participates, etc. Valorie observes observed that the "most successful meetings have been when committers have been present," which leads to a discussion of ways to encourage this synergy in the future. The idea of a regular joint meeting of DCAT and the committers is was brought forward. Everyone in the room seem seemed to agree that making a specific agenda available prior to a joint meeting would be key to the success of the meeting. This discussion segued into the subsequent session hosted by Sarah Shreeves on 'hot topics'.

...

A number of "repostiory" ideas are were discussed next, an XMLUI "theme garden" has long been on the wish list, and now add to that a curation task and SWORD package garden/repository. From the discussion, it seems like GitHub can handle the actual code storage handily, it's just an issue of discoverability. The wiki may work OK for this task. Richard asks "who takes the lead?" on implementing this idea?

...