The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Meet Mer
m (spelling fix) |
(→Installation) |
||
| (8 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | = MeetMer - community dashboard = | |
| − | MeetMer is simple dashboard-ish application written with Ruby on Rails. The primary purpose of MeetMer dashboard is to help #Mer project contributors and other stakeholders monitor their performance and activities. | + | MeetMer is simple dashboard-ish application written with Ruby on Rails. The primary purpose of MeetMer dashboard is to help #Mer project contributors and other stakeholders monitor their performance and activities. Initial call for action can be found [http://blog.ossoil.com/2012/07/24/meetmer-community-dashboard-for-mer/ from here] |
| + | |||
| + | = Development = | ||
| + | Application structure will be modular. Each feature such as listing bugs or listing meetings is always a gem. Initial discussion about features is in Mer Bugzilla: [https://bugs.merproject.org/show_bug.cgi?id=429 Bug 429 - Mer Dashboard] | ||
| + | |||
| + | == Deployment == | ||
| + | Currently deployment goes through David Greaves, who manually pulls sources from github. | ||
| + | |||
| + | == Source codes == | ||
| + | Sources are managed in Github. | ||
| + | * [https://github.com/kyyberi/Meet-Mer https://github.com/kyyberi/Meet-Mer] | ||
| + | |||
| + | == Issue tracking == | ||
| + | Current issue tracking is in Github. | ||
| + | |||
| + | == Translations == | ||
| + | We will most likely use Transifex. | ||
| + | * [https://www.transifex.com/projects/p/meetmer/ MeetMer in Transifex] | ||
| + | |||
| + | = Installation = | ||
| + | * Described in separate [[/Installation| Installation page]] | ||
Latest revision as of 14:32, 28 July 2012
Contents |
[edit] MeetMer - community dashboard
MeetMer is simple dashboard-ish application written with Ruby on Rails. The primary purpose of MeetMer dashboard is to help #Mer project contributors and other stakeholders monitor their performance and activities. Initial call for action can be found from here
[edit] Development
Application structure will be modular. Each feature such as listing bugs or listing meetings is always a gem. Initial discussion about features is in Mer Bugzilla: Bug 429 - Mer Dashboard
[edit] Deployment
Currently deployment goes through David Greaves, who manually pulls sources from github.
[edit] Source codes
Sources are managed in Github.
[edit] Issue tracking
Current issue tracking is in Github.
[edit] Translations
We will most likely use Transifex.
[edit] Installation
- Described in separate Installation page
