Moving from Redmine to GitHub?

Community
41

when you need help, you missed something good in the design…

42

  1. Issues on a single repo are a central point to collect bug reports and new feature requests.
    An issue could be related to more than one package/repository. This is the reason for “multiple-packages” category in our Redmine. With GitHub labels it’s easy to assign an issue to multiple packages.

  2. Issues on a single repo have an unique numbering.
    When the developer writes a commit message or a comment from another repository he can reference the issue by using a syntax like: nethserver/dev#1234.
    This is an example of pull request that references an issue of another project:

A link between the issue and the PR is created with the syntax above, in the issue title, or comment. Consider also the scenarios

  • multiple PR from multiple repositories referencing the same issue
  • a PR without issue

OwnCloud uses a “mixed” approach. Main components have their trackers, the “apps” share a single one. https://github.com/owncloud/core/blob/master/CONTRIBUTING.md

I’d prefer not relying on other tools. The waffle.io dashboard is for @giacomo that loves summaries :wink:

However the Milestone view is a good starting point to catch the state of the whole project, together with the organization dashboard. Also queries can be saved somewhere (wiki.nethserver.org?) or bookmarked: NethServer v6.7.

2 Likes
43

What do you mean with “fine search”? What are you searching for?

44

agreed, one example Bugzilla Reports - SME Server

actually you can search easily by milestone or labels, but in redmine you have much more settings, however like @alefattorini proposed a search syntax exists

2 Likes
45

It’s a common approach, Discourse use a similar sintax
https://meta.discourse.org/t/advanced-search/2267/13

46

I admit Redmine has an advanced and complete search form, but I must also say I rarely use it. And I’m a top user of our Redmine :wink:

47

Checkin last two months activity you’re a top user togheter with @giacomo @filippo_carletti @jobezic @alep @dz00te @Adam
http://dev.nethserver.org/projects/nethserver/activity

48

I’d like to propose a real world test: use github instead of redmine for the “initial work” on NethServer 7.
Initial work means some small adjustments to a number of packages to make them work on CentOS 7.
My idea for a workflow is:

  1. clone nethserver-xxx source
  2. try to build rpm
  3. fix build errors (if present)
  4. install rpm
  5. create pull request
  6. open issue for unsolved errors

What do you think?

5 Likes
49

Okay, let’s give it a try for NethServer 7 since we do not expect to have many major issues during the porting.
If the GitHub tracker is not good enough, we will switch back to Redmine. In this case, probably we can also afford to lose few more issues (or we can copy them by hand).

At the end of the porting work, let’s say after the release of NethServer 7 beta, we will gather all the opinions to get final decision.

1 Like
50

So let’s move forward, what are the next steps? /cc @davidep

51

A post was split to a new topic: NethServer 7-alpha2

52

I will check it, but i’m a redmine fan so my opinion will be a little sided
, it was a breakthrough tool for the company i’m working.