> Hello all,
>
> last few weeks we have been discussing RedMine upgrade while few of
> us raised question about using Github Issues. The key question is
> what you - community developers and users - think about RedMine and
> Github Issues.
>
> As a starting point for the discussion, let me summarize pros/cons
> from my point of view:
>
> RedMine Pros: - our own service - lots of fields to fill - owner -
> priority - category - target version - difficulty -
> bug/request/feature types - integrated with wiki, IRC/GIT - other
> features like files, roadmap, activity
>
> RedMine Cons: - our own service - interface is a bit funky - new
> users need to register - multiple projects structure can be
> confusing - does not support "take bug" (one need to scroll through
> the list) - new bug form maybe too complicated for new reporters -
> watchers checkbox forrest is annoying (should go away with the
> upgrade)
>
> Github Issues Pros: - hosted service - excellent integration with
> github/pull requests - familiar and fast interface - agile fields:
> - owner - target version (milestone) - labels feature (can be used
> for the missing fields) - possibility that user already have github
> account
>
> Github Issues Cons: - hosted service - missing fields: - priority -
> category - difficulty - no bug/request/feature types
You can use labels to mimic bug/request/feature types.
Same for priority and category.
···
On 07/15/2013 02:34 PM, Lukas Zapletal wrote:
Folks are evaluating Chilli Project which is a fork of Red Mine,
we could use that as well. I guess we can assume Chilli Project =
Red Mine for now.
So the question is - should we upgrade RedMine and stay on that or
should we evaluate Github Issues and try if that works for us?
I feel what we need from a bug/issue tracker exceeds what we can get
from github. That said, you did point out some cons with our existing
redmine instance that may be addressable using a newer version, or
developing some web forms on top of the redmine api…
I'll also add that many in the "Software Freedom" community have an
issue with Github. Although our primary workflow today is Github/fork
based, and I don't believe we are advertising it heavily, we still
accept git patches, so we do NOT exclude their contribution.
I would not want to preclude contribution from folks that are strongly
aligned with software freedom by mandating the use of github for
submitting issues/bugs.
Thanks,
-Brian
···
On Mon, Jul 15, 2013 at 8:34 AM, Lukas Zapletal wrote:
> Hello all,
>
> last few weeks we have been discussing RedMine upgrade while few of us
> raised question about using Github Issues. The key question is what you
> - community developers and users - think about RedMine and Github
> Issues.
>
> As a starting point for the discussion, let me summarize pros/cons from
> my point of view:
>
> RedMine Pros:
> - our own service
> - lots of fields to fill
> - owner
> - priority
> - category
> - target version
> - difficulty
> - bug/request/feature types
> - integrated with wiki, IRC/GIT
> - other features like files, roadmap, activity
>
> RedMine Cons:
> - our own service
> - interface is a bit funky
> - new users need to register
> - multiple projects structure can be confusing
> - does not support "take bug" (one need to scroll through the list)
> - new bug form maybe too complicated for new reporters
> - watchers checkbox forrest is annoying (should go away with the
> upgrade)
>
> Github Issues Pros:
> - hosted service
> - excellent integration with github/pull requests
> - familiar and fast interface
> - agile fields:
> - owner
> - target version (milestone)
> - labels feature (can be used for the missing fields)
> - possibility that user already have github account
>
> Github Issues Cons:
> - hosted service
> - missing fields:
> - priority
> - category
> - difficulty
> - no bug/request/feature types
>
> Folks are evaluating Chilli Project which is a fork of Red Mine, we
> could use that as well. I guess we can assume Chilli Project = Red Mine
> for now.
>
> So the question is - should we upgrade RedMine and stay on that or
> should we evaluate Github Issues and try if that works for us?
>
> Please send us your feedback.
>
> --
> Later,
>
> Lukas "lzap" Zapletal
> irc: lzap #theforeman
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/groups/opt_out.
Some of redmine cons can be fixed by either installing new plugins (there are
plenty of them) or by our custom changes. I used to modify redmine internals a
lot. Also we could write a plugin for github oauth login if you find it useful
(I didn't find existing one).
···
--
Marek
On Monday 15 of July 2013 14:34:46 Lukas Zapletal wrote:
Hello all,
last few weeks we have been discussing RedMine upgrade while few of us
raised question about using Github Issues. The key question is what you
community developers and users - think about RedMine and Github
Issues.
As a starting point for the discussion, let me summarize pros/cons from
my point of view:
RedMine Pros:
our own service
lots of fields to fill
owner
priority
category
target version
difficulty
bug/request/feature types
integrated with wiki, IRC/GIT
other features like files, roadmap, activity
RedMine Cons:
our own service
interface is a bit funky
new users need to register
multiple projects structure can be confusing
does not support “take bug” (one need to scroll through the list)
new bug form maybe too complicated for new reporters
watchers checkbox forrest is annoying (should go away with the
upgrade)
Github Issues Pros:
hosted service
excellent integration with github/pull requests
familiar and fast interface
agile fields:
owner
target version (milestone)
labels feature (can be used for the missing fields)
possibility that user already have github account
Github Issues Cons:
hosted service
missing fields:
priority
category
difficulty
no bug/request/feature types
Folks are evaluating Chilli Project which is a fork of Red Mine, we
could use that as well. I guess we can assume Chilli Project = Red Mine
for now.
So the question is - should we upgrade RedMine and stay on that or
should we evaluate Github Issues and try if that works for us?
imho we should also see how do we align the commit messages to old bugs…
the link between tickets and commits is pretty important imho.
does it mean everybody needs a github account instead of a redmine account?
Ohad
···
On Mon, Jul 15, 2013 at 3:40 PM, Jan Vansteenkiste wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 07/15/2013 02:34 PM, Lukas Zapletal wrote:
Hello all,
last few weeks we have been discussing RedMine upgrade while few of
us raised question about using Github Issues. The key question is
what you - community developers and users - think about RedMine and
Github Issues.
As a starting point for the discussion, let me summarize pros/cons
from my point of view:
RedMine Pros: - our own service - lots of fields to fill - owner -
priority - category - target version - difficulty -
bug/request/feature types - integrated with wiki, IRC/GIT - other
features like files, roadmap, activity
RedMine Cons: - our own service - interface is a bit funky - new
users need to register - multiple projects structure can be
confusing - does not support “take bug” (one need to scroll through
the list) - new bug form maybe too complicated for new reporters -
watchers checkbox forrest is annoying (should go away with the
upgrade)
Github Issues Pros: - hosted service - excellent integration with
github/pull requests - familiar and fast interface - agile fields:
owner - target version (milestone) - labels feature (can be used
for the missing fields) - possibility that user already have github
account
Github Issues Cons: - hosted service - missing fields: - priority -
category - difficulty - no bug/request/feature types
You can use labels to mimic bug/request/feature types.
Same for priority and category.
Folks are evaluating Chilli Project which is a fork of Red Mine,
we could use that as well. I guess we can assume Chilli Project =
Red Mine for now.
So the question is - should we upgrade RedMine and stay on that or
should we evaluate Github Issues and try if that works for us?
Please send us your feedback.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
This might be slightly off topic, but you might want to have a quick
glance at GitLab for some of those issues with GitHub.
I'm not sure how the issue tracker compares with the ones mentioned,
but it could be worth 5 minutes to have a look, since the familiar
"GitHub" interface is very similar (if not too similar…)
I would just love to have the redmine API. Would make my life a wee bit
easier
– bk
···
On 07/16/2013 03:02 AM, Marek Hulan wrote:
> Some of redmine cons can be fixed by either installing new plugins (there are
> plenty of them) or by our custom changes. I used to modify redmine internals a
> lot. Also we could write a plugin for github oauth login if you find it useful
> (I didn't find existing one).
>
> Some of redmine cons can be fixed by either installing new plugins (there
> are
> plenty of them) or by our custom changes. I used to modify redmine
> internals a
> lot. Also we could write a plugin for github oauth login if you find it
> useful
> (I didn't find existing one).
>
ooo… that would be lovely… It would be also interesting if there is a
way to add links from github to redmine?
Ohad
···
On Tue, Jul 16, 2013 at 10:02 AM, Marek Hulan wrote:
–
Marek
On Monday 15 of July 2013 14:34:46 Lukas Zapletal wrote:
Hello all,
last few weeks we have been discussing RedMine upgrade while few of us
raised question about using Github Issues. The key question is what you
community developers and users - think about RedMine and Github
Issues.
As a starting point for the discussion, let me summarize pros/cons from
my point of view:
RedMine Pros:
our own service
lots of fields to fill
owner
priority
category
target version
difficulty
bug/request/feature types
integrated with wiki, IRC/GIT
other features like files, roadmap, activity
RedMine Cons:
our own service
interface is a bit funky
new users need to register
multiple projects structure can be confusing
does not support “take bug” (one need to scroll through the list)
new bug form maybe too complicated for new reporters
watchers checkbox forrest is annoying (should go away with the
upgrade)
Github Issues Pros:
hosted service
excellent integration with github/pull requests
familiar and fast interface
agile fields:
owner
target version (milestone)
labels feature (can be used for the missing fields)
possibility that user already have github account
Github Issues Cons:
hosted service
missing fields:
priority
category
difficulty
no bug/request/feature types
Folks are evaluating Chilli Project which is a fork of Red Mine, we
could use that as well. I guess we can assume Chilli Project = Red Mine
for now.
So the question is - should we upgrade RedMine and stay on that or
should we evaluate Github Issues and try if that works for us?
The discussion seems to be coming down in favour of Redmine (which is also
my view) - I'll try to get the Redmine instance updated soon, and then we
can see what gaps we can fill in with new plugins.
> Hi
>
> This might be slightly off topic, but you might want to have a quick
> glance at GitLab for some of those issues with GitHub.
>
Gitlab only has private repositories and GitHub is already our "home" for
repo hosting.
···
On Mon, Jul 15, 2013 at 4:08 PM, Ståle Dagfinrud wrote:
I’m not sure how the issue tracker compares with the ones mentioned,
but it could be worth 5 minutes to have a look, since the familiar
“GitHub” interface is very similar (if not too similar…)
If I had to guess, I assume that more people have a github account than a redmine account.
The other caveat is becoming a member of the foreman-users google group. It is usually quicker for some users to send an email to foreman-users@googlegroups.com than sign in to RedMine and submit an issue. However, his/her first email is moderated afair and not automatically sent it to the mailing list. Is there a way to automatically add all redmine users and all github users that starred, watched, or forked foreman to be added to foreman-users@googlegroups.com
Besides irc, is there a preferred way to first raise a bug issue - redmine/github issue vs. google group email?
Joseph
···
----- Original Message -----
From: "Ohad Levy"
To: foreman-dev@googlegroups.com
Sent: Tuesday, July 16, 2013 10:03:12 AM
Subject: Re: [foreman-dev] Re: [foreman-users] RedMine vs Github Issues - opinions?
On Tue, Jul 16, 2013 at 10:02 AM, Marek Hulan mhulan@redhat.com wrote:
Some of redmine cons can be fixed by either installing new plugins (there
are
plenty of them) or by our custom changes. I used to modify redmine
internals a
lot. Also we could write a plugin for github oauth login if you find it
useful
(I didn’t find existing one).
ooo… that would be lovely… It would be also interesting if there is a
way to add links from github to redmine?
Ohad
–
Marek
On Monday 15 of July 2013 14:34:46 Lukas Zapletal wrote:
Hello all,
last few weeks we have been discussing RedMine upgrade while few of us
raised question about using Github Issues. The key question is what you
community developers and users - think about RedMine and Github
Issues.
As a starting point for the discussion, let me summarize pros/cons from
my point of view:
RedMine Pros:
our own service
lots of fields to fill
owner
priority
category
target version
difficulty
bug/request/feature types
integrated with wiki, IRC/GIT
other features like files, roadmap, activity
RedMine Cons:
our own service
interface is a bit funky
new users need to register
multiple projects structure can be confusing
does not support “take bug” (one need to scroll through the list)
new bug form maybe too complicated for new reporters
watchers checkbox forrest is annoying (should go away with the
upgrade)
Github Issues Pros:
hosted service
excellent integration with github/pull requests
familiar and fast interface
agile fields:
owner
target version (milestone)
labels feature (can be used for the missing fields)
possibility that user already have github account
Github Issues Cons:
hosted service
missing fields:
priority
category
difficulty
no bug/request/feature types
Folks are evaluating Chilli Project which is a fork of Red Mine, we
could use that as well. I guess we can assume Chilli Project = Red Mine
for now.
So the question is - should we upgrade RedMine and stay on that or
should we evaluate Github Issues and try if that works for us?
> imho we should also see how do we align the commit messages to old bugs…
> the link between tickets and commits is pretty important imho.
If we want to deprovision RedMine (I don't think that would be good
idea), then we would need to create redirects or something. But if
RedMine Issues stays there (closed), why this is a problem? I mean,
links will stay valid.
> does it mean everybody needs a github account instead of a redmine account?
It looks like. The thing is - is that good or bad thing?
···
On Mon, Jul 15, 2013 at 03:50:05PM +0300, Ohad Levy wrote:
> Besides irc, is there a preferred way to first raise a bug issue -
> redmine/github issue vs. google group email?
Maybe we could 'merge' maillist to redmine. Redmine can create issues based on
received mails. All replies would be also added as comments. You can also set
what attributes can be modified directly from mail. On the other hand, we
probably don't want to have every question on maillist as a new issue.
···
--
Marek
Joseph
----- Original Message -----
From: “Ohad Levy” ohadlevy@gmail.com
To: foreman-dev@googlegroups.com
Sent: Tuesday, July 16, 2013 10:03:12 AM
Subject: Re: [foreman-dev] Re: [foreman-users] RedMine vs Github Issues -
opinions?
On Tue, Jul 16, 2013 at 10:02 AM, Marek Hulan mhulan@redhat.com wrote:
Some of redmine cons can be fixed by either installing new plugins (there
are
plenty of them) or by our custom changes. I used to modify redmine
internals a
lot. Also we could write a plugin for github oauth login if you find it
useful
(I didn’t find existing one).
ooo… that would be lovely… It would be also interesting if there is a
way to add links from github to redmine?
Ohad
–
Marek
On Monday 15 of July 2013 14:34:46 Lukas Zapletal wrote:
Hello all,
last few weeks we have been discussing RedMine upgrade while few of us
raised question about using Github Issues. The key question is what you
community developers and users - think about RedMine and Github
Issues.
As a starting point for the discussion, let me summarize pros/cons from
my point of view:
RedMine Pros:
our own service
lots of fields to fill
owner
priority
category
target version
difficulty
bug/request/feature types
integrated with wiki, IRC/GIT
other features like files, roadmap, activity
RedMine Cons:
our own service
interface is a bit funky
new users need to register
multiple projects structure can be confusing
does not support “take bug” (one need to scroll through the list)
new bug form maybe too complicated for new reporters
watchers checkbox forrest is annoying (should go away with the
upgrade)
Github Issues Pros:
hosted service
excellent integration with github/pull requests
familiar and fast interface
agile fields:
owner
target version (milestone)
labels feature (can be used for the missing fields)
possibility that user already have github account
Github Issues Cons:
hosted service
missing fields:
priority
category
difficulty
no bug/request/feature types
Folks are evaluating Chilli Project which is a fork of Red Mine, we
could use that as well. I guess we can assume Chilli Project = Red Mine
for now.
So the question is - should we upgrade RedMine and stay on that or
should we evaluate Github Issues and try if that works for us?
Exactly, it does not look like switching to GitHub is preferred much.
Thanks!
LZ
···
On Mon, Jul 22, 2013 at 10:41:53AM +0100, Greg Sutcliffe wrote:
> The discussion seems to be coming down in favour of Redmine (which is also
> my view) - I'll try to get the Redmine instance updated soon, and then we
> can see what gaps we can fill in with new plugins.
>
> Greg
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
