Moving from Redmine to GitHub Issues

[Elizabeth Quigley]

Hi all,

Dataverse has moved from using Redmine as our way to track bugs, features, and suggestions and is now using GitHub Issues. You can see what the Dataverse Development Team is working on here: github.com/IQSS/dataverse/issues and add any bugs you come across or feature requests. When you click on New Issue, you'll be asked to sign in to GitHub. After that, you'll be brought to the New Issue form which includes a link to our Contributing to Dataverse documentation (also found here: github.com/IQSS/dataverse/blob/master/CONTRIBUTING.md). 

Check it out and let us know if you have any questions!

Best,

Elizabeth

Elizabeth Quigley

Usability Specialist

Institute for Quantitative Social Science

Harvard University

We're redesigning Dataverse and want your feedback! Please check out our Beta Site.

[Philip Durbin]

I'm super excited about the migration* from Redmine to GitHub. I especially like the integration between commits and issues and that I can use Markdown in tickets. Oh, and being able to @mention people (even outside the IQSS team) is awesome: https://github.com/IQSS/dataverse/issues/754#issuecomment-50151448

I'm already finding that the CONTRIBUTING.md file is very useful in explaining to potential contributors how they might help: http://irclogs.jackgrigg.com/irc.freenode.net/openhatch/2014-07-25#i_3408867

I'm glad CONTRIBUTING.md also explains what the issue labels mean but I'm wondering if we should have a label like "low hanging fruit" or something to indicate to potential contributors which issues are relatively small and could more easily be worked on by someone new: http://irclog.iq.harvard.edu/dataverse/2014-07-26#i_11503

Of course, I don't want to encourage *too* many labels... just something to think about. :)

Phil

p.s. By the way, the migration scripts are open source! Thanks, Raman! https://github.com/IQSS/redmine2github

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/9da271af-3521-4a7b-bcdb-ea34b550af14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[sheila miguez]

On Sat, Jul 26, 2014 at 8:13 AM, Philip Durbin <philip...@harvard.edu> wrote:

Of course, I don't want to encourage *too* many labels... just something to think about. :)

You could try "bite-sized" and "fly-by". Bite-sized would label small tasks that are good for beginners. Fly-by would label small to medium tasks good for more experienced people starting with the project. #openhatch organizers could offer suggestions for handling labels without unwieldy label proliferation.

I am glad you moved to github issues! It will make it easier to follow progress on things.

--

she...@pobox.com

[Philip Durbin]

I like "bite-sized" as a term.

I'll tell ya, we picked a good time to move. Lots of new GitHub Issues
features were just announced:
https://github.com/blog/1866-the-new-github-issues

> --
> You received this message because you are subscribed to the Google Groups
> "Dataverse Users Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dataverse-commu...@googlegroups.com.
> To post to this group, send email to dataverse...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/dataverse-community/CAHCs_racZDANmoQDyC3TdUeuF3umDYEaAqGnLKwLKkuEd9y86Q%40mail.gmail.com.