Am Donnerstag, 23. Februar 2017, 11:12:36 CET schrieb Lars Vogdt:
As I had some topics in mind for our next meeting,
that I don't want
to forget, I started to think about where to save them...
Other teams have some information about their meetings in the wiki -
so I started to setup
...but during that, I felt that it might be also a good idea to use
our admin tool also to collect the topics and provide a schedule - so
I ended up with:
I'd recommend not to include the description in the query output - it
might look like a good idea now, but on the long term (and with more
meetings), it will just add superfluous stuff to the list page. And to
make things even worse, the meeting topics in the checklist are _not_
included in the description, which makes it basically useless.
A general problem in redmine is that it remembers query settings too
good ;-) which means: if you are viewing that custom query and then
click on the "Tickets" menu item, it will still give you the events list
instead of all tickets. (This isn't specific to the events list, it
applies to all queries.)
Maybe we just need a boring stored query "open tasks" (similar to "Tasks
by category", but without grouping by category) which can act as "reset
to default query parameters".
which is a custom query containing only issues
reported in the Redmine
Category "Event". My idea is to use this Category maybe also for
Conferences and other stuff later.
?query_id=36 should provide you with an overview of upcoming events.
One problem might be that I did not find a way to include the time in
the calendar, so I used the summary for it. But I hope this is a not
so problematic issue for now.
I don't see that as a problem, and would even put the date in the
summary (which would make it more visible in mails sent out by
progress.o.o). So for the next meeting, I'd use the summary
2017-03-05 18:00 UTC openSUSE Heroes meeting
(ISO date is better sortable than month names ;-)
Instead of putting the topics in the description, I
hope it's a good
idea using a checklist instead (as everybody can easily add a
checklist entry that will then be added in the top) - but we can also
What do you think?
Would that work also for you - and help to organize our meeting?
This looks like a good way to organize the meeting.
We can also attach the IRC log after the meeting to have everything in
Some high-level complaints - the checklist has two small disadvantages:
- we can't sort the checklist (or I didn't find out yet ;-)
- when adding an item, the diff is unreadable ("item added: $foo" would
be more useful)
plugin we use? If so, updating to the latest version should fix these
Still, using the checklist is much better than adding topics in the
IMHO it's also better than organizing meetings on en.o.o.
Having meeting topics and logs there doesn't make too much sense - on
the long run, they'll mostly be "old stuff" nobody cares about. I know
we have the "Archive:" namespace for that, so it would be ok - but
having a ticket per meeting looks like the better solution to me.
Ich bin nicht stolz auf das unnoetige Icon "Arbeitsplatz" auf
dem Desktop. Irgendwann sieht man nur noch per "uname -a", ob
das richtige System laeuft... [Thomas Moritz in suse-linux]
To unsubscribe, e-mail: heroes+unsubscribe(a)opensuse.org
To contact the owner, e-mail: heroes+owner(a)opensuse.org