OW2 Software Engineering Platform Requirements


This page lists several requirements to be ideally fulfilled by the future version of the OW2 Software Engineering Platform, covering in particular the following services and they way they interact together: wiki, VCS, issue tracking, notifications, statistics, continuous integration, source code analysis, license check, originality check, testing, cloud deployment, etc.

Release management service

  • Ability to publish project news directly on the project's dashboard (see also MO-54 private issue)
  • Ability to view the detailed release notes directly from the project's dashboard without the need to navigate to the project's site itself

Notification service

  • Ability to provide notifications of new releases, like what is offering for GitHub hosted projects: https://sibbell.com/ 
  • Ability to notify specific people or groups of specific engineering events or service maintenance events

Voting service

  • Ability to vote for a feature, a new process, a project, etc.

See also:

Crowdsourcing service

  • Ability to crowdsource some tasks for a project such as mobile testing, security testing (see also the POSS 2015 presentation on this topic)

Delegated administration of services

  • Ability for project leaders to administer the services used by their project with a limited scope (only partial administration, limited to the configuration of the service of their project)

https://en.wikipedia.org/wiki/Software_configuration_management