Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Finish migration to GitHub #210

Closed
13 tasks done
myurkin opened this issue Aug 13, 2015 · 9 comments
Closed
13 tasks done

Finish migration to GitHub #210

myurkin opened this issue Aug 13, 2015 · 9 comments
Assignees
@myurkin @dsmunev
Labels
maintainability Simplifies further code development (standardization, robustness) pri-Critical Should be fixed quickly task Not directly related to code (e.g., documentation)
Milestone
1.4

Comments

@myurkin
Copy link
Member

myurkin commented Aug 13, 2015 •
edited
Loading

This includes a number of components:

  • notifying/incorporating other contributors/project members. Possibly update acknowledgments.
  • issues (assignees, labels, milestones, links in comments).
  • wiki pages (placement at wiki tab, images, cross links).
  • readme at main landing page.
  • try to place all downloads in "releases" (Release Notes can also go there)
  • update links in documentation (manual and text files).
  • update build scripts
  • set some git property on win32\README and win64\README so that they are always checked with Windows-style EOL
  • transfer svn properties to git attributes
  • change code license to a github style, as LICENSE
  • use README in different folders as much, as possible. Especially, in misc/. Very convenient for code browsing.
  • add files CONTRIBUTING and CODE_OF_CONDUCT
  • add issue templates for bugs, questions, etc.
@myurkin myurkin added maintainability Simplifies further code development (standardization, robustness) pri-Critical Should be fixed quickly task Not directly related to code (e.g., documentation) labels Aug 13, 2015
@myurkin myurkin self-assigned this Aug 13, 2015
@myurkin myurkin added this to the 1.3 milestone Aug 13, 2015
@myurkin myurkin mentioned this issue Sep 25, 2015
Closed
@myurkin
Copy link
Member Author

myurkin commented Nov 13, 2015

All issues have been processed, adding cross-references that were not created automatically. The only remaining part is links to wiki pages - they need to be updated, after wiki pages themselves are updated (including their location).

@myurkin
Copy link
Member Author

myurkin commented May 23, 2016

README has been created, linking to current placement of wiki pages. Should be updated after wikis are moved, and possibly to reflect the changes in downloads.

@myurkin
Copy link
Member Author

myurkin commented Sep 16, 2016

I have fixed some formatting problems in wiki pages (tables, code inside lists, internal links and cross references to other wiki pages and images).
One of the remaining problems is that of showing svg files, related to isaacs/github#316 . One of the solution is using https://rawgit.com/ . That should be fine for images of code comparisons - ComparisonOtherCodes.md (are not expected to change), but not so much for CodeDesign.md (where the images are expected to change with each version). However, the latter can be alleviated by using links with tags, which would be updated each new version.
This can probably be used to return the logo somewhere on the README page.

@myurkin
Copy link
Member Author

myurkin commented Oct 14, 2017

The problem with svg files has been fixed by GitHub itself.

@myurkin
Copy link
Member Author

myurkin commented Jun 5, 2018

Added a few tasks. One (licencse) is already solved.
@dsmunev

@myurkin myurkin mentioned this issue Jun 19, 2018
Closed
@myurkin
Copy link
Member Author

myurkin commented Jun 22, 2018

After moving wikis to a special repo, svg stopped working again. But it was fixed by a workaround - see github/markup#556 (comment)

@myurkin
Copy link
Member Author

myurkin commented Jul 9, 2018 •
edited
Loading

Nobody at Google Code is responding to my e-mails, so it seems that the ADDA title page there will stay a bit confusing with regards to the move. That is not a big deal, since most links on the web point already to GitHub.

The issue with a separate landing page has been postponed - #243

@myurkin
Copy link
Member Author

myurkin commented Jul 12, 2018

All community related stuff is finalized https://github.com/adda-team/adda/community , at least in some beta-version state.

@myurkin
Copy link
Member Author

myurkin commented Dec 11, 2020

Updating InstructionCommitters is moved to #283

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

@myurkin myurkin

@dsmunev dsmunev

Labels
maintainability Simplifies further code development (standardization, robustness) pri-Critical Should be fixed quickly task Not directly related to code (e.g., documentation)
Projects
None yet
Milestone
1.4
Development

No branches or pull requests
2 participants
@myurkin @dsmunev