Page History

...

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 pointed out that there is a page for this information on the wiki, the Development Proposals page, though it was later pointed out that the wiki page doesn't really provide a good way to track project status. Bram Luyten suggested the possibility to automatically track an "outside" project status by linking to other issue trackers and wikis, perhaps via RSS feeds.

...

• Invite new repositories (through their managers after they signup for a listing on dspace.org)
• invite duraspace sponsors
• find ways to approach the non-english speaking community.
  • Translated wiki pages? Confluence plugin

Currently, DCAT meetings are one hour phone conferences (where you can also use Skype to dial in). The developers present in the room shared benefits of using IRC for text based chat meetings (could be in parallel with phone conversation):

• Automated transcript of everything being typed
• Subject overlaps, easy to pick up on something someone else has said before in parallel to another topic going on. This takes some time getting used to
• It tends to be short & very focused. Barrier is higher to keep typing as opposed to keep talking on the phone.

The developers commented that if DCAT will create new issues in JIRA, it would be best if:

• it's thoroughly verified if the bug or feature request isn't already logged in another JIRA ticket. If variants or related problems are logged, use the functionality to link JIRA tickets together.
• the issue category is carefully selected: New feature, improvement or bugfix is carefully considered.

Commenting on existing issues is no problem at all and should be encouraged at all times.

Sarah Shreeves open discussion

...