New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team Activity Tracking Tools #101

Closed
clanmills opened this Issue Oct 3, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@clanmills
Collaborator

clanmills commented Oct 3, 2017

Luis mentioned a "scrum board" tool. Sure why not.

Before we moved to GitHub (at the end of April), I tracked everything in Redmine. I have a python script (svn://dev.exiv2.org/svn/team/contrib/redmine/progress.py) to compute various metrics. http://dev.exiv2.org/news/2

We're now living in the world of GitHub and perhaps we should make Redmine read-only and start moving away from that. For that matter, I also wonder if we should be shut down exiv2.org in 2018.

Suggestions welcome.

@piponazo

This comment has been minimized.

Collaborator

piponazo commented Oct 3, 2017

I did not put too much attention in the existing things in redmine, but I would vote for centralise as much as possible the work on GitHub. If we are doing here the main development, people will create issues here and we should try to make here visible most of the information.

For example, we can handle different projects, milestones and issues in GitHub. We also have now some sort of Continuous Integration with Travis-CI and AppVeyor. More things will come related to CI (run unit tests automatically, coverage tools, static analyzers, etc).

Let's see what is the opinion of other active collaborators ;)

@D4N

This comment has been minimized.

Contributor

D4N commented Oct 3, 2017

I don't think exiv2.org should be shut down, it is a good thing to have a separate website where the source & documentation can be hosted. Also I think Github issues are not a good replacement for the forum.

I think we should use the tools GitHub gives us but not overly rely on it. Imho the CI should be still done by Jenkins as Travis & AppVeyor cannot build on all platforms that we support.

For the communication I'd actually prefer the good-ol' mailing list (I find it to be more of a persistent medium than a chat like slack and far better suited for a discussion).

@piponazo

This comment has been minimized.

Collaborator

piponazo commented Apr 10, 2018

Let's close this issue then. We can discuss more about this in the team meeting if you want.

@piponazo piponazo closed this Apr 10, 2018

@clanmills

This comment has been minimized.

Collaborator

clanmills commented Apr 11, 2018

I've put this "on the list" for discussion in England. http://dev.exiv2.org/news/3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment