From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [DISCUSSION] Issues, ToDo and Roadmap
Date: Mon, 11 Feb 2019 11:19:54 +0100 [thread overview]
Message-ID: <e0a05b70-aa75-a7b1-f08a-e7ff46fe1e66@siemens.com> (raw)
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?
regards,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next reply other threads:[~2019-02-11 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 10:19 Claudius Heine [this message]
2019-02-11 12:50 ` Jan Kiszka
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=e0a05b70-aa75-a7b1-f08a-e7ff46fe1e66@siemens.com \
--to=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