gunghogeoduck/osem-fcy
1
0
Fork 0
mirror of https://github.com/openSUSE/osem.git synced 2026-08-13 19:54:02 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

[ci skip] Improve on issues section and meeting day

Browse source
This commit is contained in:
Artem Chernikov 2014-08-03 11:37:55 +02:00
parent 73c15e9404
commit 9734ce9836
1 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -18,7 +18,7 @@ as fast as we can. There are some things which we embrace
# Sprints # Sprints
* once in a while (2 weeks, currently) we catch up on freenode#osem to review results of previous sprint and plan next one. * once in a while (2 weeks, currently) we catch up on freenode#osem to review results of previous sprint and plan next one.
* date of the meeting should be last working day before the end of current sprint (Milestone in Github terms) * date of the meeting is discussed and chosen beforehand with preference to friday (Milestone in Github terms)
* on meeting we discuss what is achieved and what is not * on meeting we discuss what is achieved and what is not
* we do planning of next sprint tasks. It is a commitment. We will do our best to deliver what we agreed on * we do planning of next sprint tasks. It is a commitment. We will do our best to deliver what we agreed on
* we use [waffle.io](https://waffle.io/opensuse/osem) to track current GH issues/pull requests * we use [waffle.io](https://waffle.io/opensuse/osem) to track current GH issues/pull requests
@ -29,9 +29,7 @@ as fast as we can. There are some things which we embrace
# Issues # Issues
* every issue should be as clear as it is possible to creator. Consice, but enough detailed please refer to our [CONTRIBUTING.md](CONTRIBUTING guide)
* it should at best propose probable solution
* no problem/feature should be repeated or clash with existing one
## Documentation ## Documentation
OSEM is extensively (some would say maniacally ;-) documented. You can generate a nice HTML documentation with ''rdoc'' OSEM is extensively (some would say maniacally ;-) documented. You can generate a nice HTML documentation with ''rdoc''