From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [DISCUSSION] Issues, ToDo and Roadmap
Date: Mon, 11 Feb 2019 13:50:37 +0100 [thread overview]
Message-ID: <5450adad-0eeb-f569-c147-fb1af4f382d3@siemens.com> (raw)
In-Reply-To: <e0a05b70-aa75-a7b1-f08a-e7ff46fe1e66@siemens.com>
On 11.02.19 11:19, [ext] Claudius Heine wrote:
> Hi,
>
> I would like to open a discussion about how we could improve the organization of
> Isar in regards to the projects short, mid and long term goals e.g. annoyances
> to be fixed, features to be implemented and bigger designs to work towards.
>
> We currently only have two public ways of communication, one of which is not
> maintained. Those are the mailing list and the github issue tracker.
>
> Mailing lists are great for open discussions and patches, but is a pretty fast
> moving medium and old discussions are no longer looked at and even get forgotten
> at some point so it might be sensible to put the results of discussions
> somewhere more persistent, search and with state tracking. Like a ticket system,
> issue tracker or wiki...
>
> The github issue tracker of Isar is in a very sorry state. Some of those open
> issues are no longer applicable or already fixed. Maybe we could reactivate that
> and have some more moderators to keep that up to date?
>
> Maybe have employ some bots to improve the short comings of the issue trackern
> and integrate the ML with it better?
>
> What do you think?
I would start with something simple: If we think the issue tracker is an
appropriate way to handle to-dos, let's clean it up first and use it. Then, if
we do not run into the same state as today after a while again, we can think
about improving its integration (if there is something that can be enabled with
reasonable effort).
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-11 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 10:19 Claudius Heine
2019-02-11 12:50 ` Jan Kiszka [this message]
2019-02-11 15:21 ` Maxim Yu. Osipov
2019-02-12 9:12 ` Claudius Heine
2019-02-12 11:17 ` Baurzhan Ismagulov
2019-02-12 12:05 ` Jan Kiszka
2019-02-12 12:18 ` Claudius Heine
2019-02-12 12:40 ` Henning Schild
2019-02-12 14:41 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5450adad-0eeb-f569-c147-fb1af4f382d3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox