-
Notifications
You must be signed in to change notification settings - Fork 480
Transfer issues from old repo #2
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
Comments
Thanks Rebecca. For issues on https://github.com/rmurphey/jqfundamentals/issues that merit transferring, is the consensus that we should continue the discussions related to those tickets on the original/old repo (with respect to them getting integrated), or just create new tickets for them here? Integration wise, I would vote for here. |
I'd also vote for moving stuff to the new repo as much as is practical. There aren't a ton of issues that have extensive discussions, and I think most of the discussions can be boiled down to clear action items. On Tuesday, May 10, 2011 at 9:44 AM, addyosmani wrote:
|
Awesome. I'm not sure if it would help, but when I'm moving over issues, I can close them on the other repo so we know that they we've already added them here or just makes notes that they've already been addressed when Dan was splitting out sections. |
Yeah, I think closing them on the old repo is good. I've added you as a collab on that repo so you can do that :) |
Thanks Rebecca! :) |
Hey @rmurphey. I notice that on the main jQuery fundamentals site the current issue tracker and pull request links are linked back to your original repository. I was just wondering what your plans were with that and if the idea was to maintain a single point of issue tracking (ie. back to web-learn-jquery) or whether it made more sense for you to keep requests coming through to the other repo which would then be transferred here as necessary. Ideally it would be nice to have a single-point, but again, it is your book/content/project so entirely up to you :) |
I'm eagerly awaiting the arrival of the learn.jquery.com site so that I can take down jqfundamentals entirely :) In the meantime I haven't done anything with it in ages, but I'll get it pointing here for issue tracking. |
Just to update: Rebecca has since updated the jqf repo to no longer display the issues list. As all issues are now being posted directly to learn.jquery.com, I'll close this. |
Lots of these are going to end up being irrelevant, but some probably merit transferring to this repo: https://github.com/rmurphey/jqfundamentals/issues.
The text was updated successfully, but these errors were encountered: