IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Skip to content
GitLab
  1. 30 Oct, 2020 1 commit
  3. 27 Oct, 2020 1 commit
  5. 15 Sep, 2020 1 commit
  7. 24 Aug, 2020 1 commit
  9. 18 Aug, 2020 3 commits
  11. 04 Jun, 2020 3 commits
  13. 29 Apr, 2020 2 commits
  15. 28 Apr, 2020 2 commits
  17. 27 Apr, 2020 1 commit
  19. 23 Apr, 2020 2 commits
  21. 21 Apr, 2020 2 commits
  23. 20 Apr, 2020 1 commit
  25. 09 Apr, 2020 1 commit
    • Justin W. Flory (he/him)'s avatar
      💹 librecorps: Add suggested SJ edits (#140) · 62d02bdc
      Justin W. Flory (he/him) authored 
      

Added a few suggested edits by @itprofjacobs:

1. Our work with UNICEF Innovation Fund: Specifically describing the
   mentorship and collaboration with portfolio teams
2. Resources: Add roadmap template and self-evaluation rubric
3. Past LibreCorps student contributors: Brief shout-out for our past
   and current students who worked on RIT LibreCorps initiatives

Signed-off-by: Justin W. Flory (he/him)'s avatarJustin W. Flory <git@jwf.io>
      62d02bdc
  27. 03 Apr, 2020 1 commit
    • Christian Martin's avatar
      Update calendar for virtual FOSS Hours (#138) · 81228b42
      Christian Martin authored 
      

* Update calendar for virtual FOSS Hours

* update virtual foss hours url (*see also note)

as per @jwflofy's request

Note: while it seems that it might _technical_ work, I can not comfortably say that putting a normal URL in the `location` field is a good idea nor best practice. As far as I can tell, this behavior seems to work on at least some calendar clients, but is not definitively to-spec.

Based on what I can find online, the best practice would be to put something to the effect of "Jitsi/Online" in the `location` field and the URL in the `url` field (populated by the `redirect` front matter) as well as in the description/summary (since not all clients support the `url` field, including Google).

Co-authored-by: default avatarChristian Martin <ct-martin@users.noreply.github.com>
      81228b42
  29. 26 Mar, 2020 2 commits
  31. 24 Mar, 2020 2 commits
    • Justin W. Flory (he/him)'s avatar
      🔩 ci: Revert Travis deploy pipeline (#135) · 5c781902
      Justin W. Flory (he/him) authored 
      

In favor of simplicity, this PR undoes the Travis CI deployment
pipeline. While all changes will _still_ be tested and required to pass
before new changes can be merged, Travis is no longer responsible for
pushing the built site source to the GitHub Pages environment.

The purpose of this change is to drop the `src` branch, revert `master`
to the default branch, and use a single branch for building and
deploying the site source. Since we are not using any advanced
functionality of Jekyll yet that warrants us to build outside of the
github-pages Gem, I think it is better to keep this simple for those who
will come after me.

Since this will bring us back to a fairly simple, single-branch workflow
with `master`, I no longer see the need in documenting the Runbook CI
deployment pipeline because there is no longer a pipeline. It goes back
to being a simple CI test.

Closes FOSSRIT/runbook#47.

Signed-off-by: Justin W. Flory (he/him)'s avatarJustin W. Flory <git@jwf.io>
      5c781902
    • Justin W. Flory (he/him)'s avatar
      🌁 gitignore: Cover more tools and editors (#129) · ad3f1229
      Justin W. Flory (he/him) authored 
      

This commit greatly expands the coverage of the `.gitignore` file to the
following types of categories:

* Frameworks (Jekyll)
* Operating Systems (Linux, macOS, Windows)
* Programming Languages (Ruby)
* Text Editors (Sublime Text, Vim)

Signed-off-by: Justin W. Flory (he/him)'s avatarJustin W. Flory <git@jwf.io>
      ad3f1229
  33. 23 Mar, 2020 5 commits
  35. 19 Mar, 2020 2 commits
  37. 18 Mar, 2020 1 commit
  39. 16 Mar, 2020 1 commit
  41. 13 Mar, 2020 1 commit
  43. 11 Mar, 2020 3 commits
  45. 10 Mar, 2020 1 commit
    • Justin W. Flory (he/him)'s avatar
      ❓ ci: Change default branches · d4688c9d
      Justin W. Flory (he/him) authored 
      

This is a risky change but I'm going to try it out. GitHub Pages only
allows `master` branch for user pages:

> User pages must be built from the `master` branch.

Soooo, now the source theoretically lives on the `src` branch, and the
`master` branch is where Travis pushes the generated site content. If
this doesn't work, I'm reverting.

Signed-off-by: Justin W. Flory (he/him)'s avatarJustin W. Flory <git@jwf.io>
      d4688c9d

  Home      |      Contact & Support      |     Accessibility     |     Terms & Conditions      |     Nondiscrimination Policy     |     IEEE Privacy Policy     |     IEEE SA Copyright Policy