Post AL12ucvsimfkyA5ncG by conservancy@mastodon.technology
(DIR) More posts by conservancy@mastodon.technology
(DIR) Post #AL12YXZtwsedzYHPn6 by conservancy@mastodon.technology
2022-06-30T13:38:35Z
4 likes, 13 repeats
Today is the day to #GiveUpGitHub
(DIR) Post #AL12YYfbt8obNXxUKO by conservancy@mastodon.technology
2022-06-30T13:38:40Z
0 likes, 10 repeats
We tried to communicate w/ #GitHub re: #Copilot; they have outright refused to answer community questions on Copilot & took it for-profit. Copilot ignores copyleft requirements; so it's time to #GiveUpGitHub https://GiveUpGitHub.org
(DIR) Post #AL12YZs3QMMb6QmwMa by conservancy@mastodon.technology
2022-06-30T13:38:50Z
0 likes, 1 repeats
We can no longer in good conscience stay silent about problems w/#GitHub's products. This latest effort to capitalize on the corpus of #copyleft code hosted on GitHub is merely the latest of their many ethical and moral lapses.
(DIR) Post #AL12ub0Psx6yzeCOPI by conservancy@mastodon.technology
2022-06-30T13:39:00Z
5 likes, 10 repeats
We call on people in positions of power in their FOSS communities to stop using GitHub and stop recommending it. GitHub, as a proprietary, trade-secret platform cannot be the singular development community for FOSS projects.
(DIR) Post #AL12ubbHfsbOpzRps8 by conservancy@mastodon.technology
2022-06-30T13:39:08Z
0 likes, 1 repeats
Gratis resources often entice & trap FOSS developers into a proprietary gated community — the walled garden of @GitHub. Remember: FOSS faced similar before — triumphantly. We'll do so again if take action now to protect our communities.
(DIR) Post #AL12ubwuNTtpv3Z6Zs by conservancy@mastodon.technology
2022-06-30T13:39:17Z
0 likes, 0 repeats
Over the coming months @conservancy will release guides and stories from projects that have moved away from GitHub. Let's shed light on the damage that is caused by centralizing community development on proprietary platforms.
(DIR) Post #AL12ucS6VUqxToA1Ca by conservancy@mastodon.technology
2022-06-30T13:39:31Z
1 likes, 6 repeats
Please join us and #GiveUpGitHub by visiting https://GiveUpGitHub.org/ and while you are still on #GitHub, adding information to your README that you do not agree with GitHub's policies and monopolized place in our community.
(DIR) Post #AL12ucvsimfkyA5ncG by conservancy@mastodon.technology
2022-06-30T13:39:43Z
2 likes, 4 repeats
To read more about this effort see our blog post at https://sfconservancy.org/blog/2022/jun/30/give-up-github-launch/
(DIR) Post #AL14qvogljvUHr5sTQ by Suiseiseki@freesoftwareextremist.com
2022-06-30T14:05:58.080480Z
0 likes, 0 repeats
@conservancy Nice blog post, but are you really planning on creating a guide for using gitlab?gitlab unfortunately doesn't show anything without JavaScript and some of the JavaScript is nonfree (as it is auto-generated, and so therefore has no source code).Have this issue been fixed?
(DIR) Post #AL14yTxkDHFODSviYy by Suiseiseki@freesoftwareextremist.com
2022-06-30T14:07:20.969180Z
0 likes, 0 repeats
@conservancy Nice blog post, but are you really planning on creating a guide for using gitlab?gitlab unfortunately doesn't show anything without JavaScript and some of the JavaScript is nonfree (as it is auto-generated, and so therefore has no source code).Has this issue been fixed?
(DIR) Post #AL1LgDWSITRTEi2fRY by straw@socks.pinnoto.org
2022-06-30T17:14:31.856439Z
0 likes, 0 repeats
@conservancy this looks like a really kinky way to illustrate it
(DIR) Post #AL1W0DeEXUpExUrAX2 by technomancy@icosahedron.website
2022-06-30T19:06:31Z
0 likes, 0 repeats
LB: I moved all my projects except Leiningen off github a couple years ago, and now I'm looking into moving that as well. a read-only mirror will probably remain on github for a few years to ease the transition, but I'm looking at @codeberg as the new home for my last remaining github-hosted project once I can get the CI setup switched over.
(DIR) Post #AL1W0E5ssgwYLFnFdA by technomancy@icosahedron.website
2022-06-30T19:08:19Z
1 likes, 1 repeats
if you've looked at moving off github in the past and ended up extremely unimpressed by the janky ui and bugs of gitlab, i don't blame you. but please give https://codeberg.org and other gitea sites a second look; they are head and shoulders above gitlab in usability and stability.
(DIR) Post #AL1qJJTl58i1d2L5Ci by Seirdy@pleroma.envs.net
2022-06-30T16:05:52.326518Z
1 likes, 1 repeats
@conservancy I might drop GitHub mirrors for new projects, but I worry that this could disproportionately cause friction among disabled users.The main reason I currently mirror to GitHub is accessibility. The only other forge I know of that’s usable with assistive technologies is Sourcehut, my primary forge. Many feel uncomfortable with Sourcehut’s style of contribution and the other FOSS forges are severely lacking, so that leaves GitHub.GitLab requires JavaScript for basic functionality, which itself is a little problematic from a FOSS perspective and very problematic from a privacy perspective: there’s a reason why the Tor Browser disables JavaScript on its “Safest” mode.“the GitLab Enterprise Edition, which is provided to the public on gitlab.com, is (like GitHub) trade-secret, proprietary, vendor-lock-in software”I agree with this statement except for the “trade-secret” choice of words. The “Enterprise Edition” is source-available proprietary software.Some things I think you should consider adding:Notes on CI solutions. While SourceHut and GitLab provide excellent CI, Gitea does not. Codeberg offers CI in the form of Woodpecker CI. I don’t know how good Woodpecker is from an accessibility perspective, but Sourcehut’s “builds” service is excellent.Notes on measures taken by forges to escape vendor lock-in through the network effect (I like to call this “user domestication”). Sourcehut uses mailing lists and does not require making an account.#POSSE note from https://seirdy.one/notes/2022/06/30/give-up-github/
(DIR) Post #AL1qJKKvtRFAHxDY5Q by Seirdy@pleroma.envs.net
2022-06-30T19:41:07.083959Z
0 likes, 0 repeats
@jookia I won't pretend that the Sourcehut accessibility situation ideal, but it's usable for the most part with assistive technologies IME. From what I can tell, it doesn't have critical issues like hidden/un-focusable items, interactive widgets that don't change states, keyboard traps, etc. The only other forge that generally passes that is GitHub.Core functionality all works, but ancillary functionality and quality-of-life could use some significant improvements. I'll file some tickets later today; they're generally easy to fix. Some that come to mind are using additional `<nav>` elements with different labels, and naming in-page heading anchors.#POSSE note from https://seirdy.one/notes/2022/06/30/sourcehut-accessibility/
(DIR) Post #AL1qJKujkJsq4zy8tU by Seirdy@pleroma.envs.net
2022-06-30T16:57:04.773879Z
0 likes, 0 repeats
@conservancy Oh, regarding vendor lock-in: I mentioned Sourcehut's email-based approach but I didn't mention that Gitea is working on ActivityPub-based federation. Edited my website's copy of the parent post to reflect that.
(DIR) Post #AL1qJLBkj3UivlvjPs by Seirdy@pleroma.envs.net
2022-06-30T19:44:55.805176Z
0 likes, 0 repeats
@jookia Just saw your thread on the matter, updated my website's copy of that post with a link.
(DIR) Post #AL1qJMB532YDzyci0W by Seirdy@pleroma.envs.net
2022-06-30T19:57:23.007356Z
0 likes, 0 repeats
@jookia Ok you're def right about sourcehut's navigation issues. No way to go from a project's repo/list/tickets to the parent project page is concerning; think there's a ticket for that. I wanted to tackle it last year, I think I should give it another look. Would love to know how I can make my site's nav better. Right now: I use labelled navigation, make the source/DOM/visual order identical, use headings and sections to break up content, and test it with multiple browser/screen-reader combinations regularly.The only major issue I think is that I broke the first rule of ARIA for heading permalinks to make reading modes and assistive technology happy: these two agents receive different semantics for the permalinks.I think another issue would be a lack of navigation context (e.g. breadcrumbs) for pages that aren't direct descendants of the sections listed in the navbar. My fediverse greeting (linked in my profile and "about" page) and my site design standards (linked in the footer) come to mind.I have multiple blind readers who regularly give feedback, so I'm really interested in this.
(DIR) Post #AL1qJNJGq4hFVfSlPc by Seirdy@pleroma.envs.net
2022-06-30T20:31:21.608174Z
0 likes, 0 repeats
@jookia I made full conformance with the AA level and partial conformance with AAA a goal in my site’s accessibility statement, the first sub-section of my “site design standards” page. I’ve been writing about my progress in meeting each SC in WCAG 2.2 for a while now, and plan on publishing it when finished. Here’s an excerpt of the WIP document containing every SC under Guideline 2.4:SC 2.4.1: I use navigation landmarks and headings to bypass blocks. This includes sufficient techniques ARIA11 and H69. I also follow advisory techniques C6 and H97.SC 2.4.2: All pages use the title element, which is sufficient technique H25. Automated checkers will flag any exceptions; I regularly crawl my entire site with HTML-Proofer.SC 2.4.3: My source, visual, and DOM order are identical (assuming you read top-to-bottom, left-to-right). Sufficient technique C27.SC 2.4.4 and SC 2.4.9: I’m not aware of any ambiguous link names in context; I’m open to hearing about exceptions. I try to make links comprehensible without context; this is a WIP.SC 2.4.5: Pages can be reached through the search bar in the footer of every page (sufficient technique G161), and either my archive pages (“posts” and “notes”) listing all subpages (sufficient technique…G126 I think?), or by following in-page links on other pages (sufficient technique G125?); all posts and notes also have a next/prev link.SC 2.4.6: I use sufficient techniques G130 and G131. I generally prefer using aria-labelledby over aria-label because the latter doesn’t translate well using machine-translation, and because I usually want assistive technologies to report content that’s similar to what sighted users see.SC 2.4.7, SC 2.4.11, SC 2.4.12, SC 2.4.13: my focus indicators should exceed all of these requirements. They aren’t obscured, are at least 3px thick, and use both AAA contrast ratios and the APCA contrast ratios. Focus indicators for non-interactive elements (necessary for VoiceOver compatibility) use the browser default styles.SC 2.4.8: I make correct use of aria-current in the global navigation. For subpages of each section listed in the global navigation, I emphasize the relevant section by making it a <strong> element. This represents sufficient techniques G128. As I mentioned in the grandparent post: I should do more than the bare minimum, perhaps by adding a breadcrumb list. Screen readers don’t usually pronounce <strong>.SC 2.4.10: All sections have headings. No heading levels are skipped. Automated checkers will flag any exceptions: I regularly crawl my entire site with both axe-core and IBM Equal Access Checker.SC 2.4.14: Not applicable; I do not have any page breaks.Conclusion: For AAA conformance I haven’t fully met SC 2.4.9. While I do the bare minimum to meet SC 2.4.8, I should do more by adding a breadcrumb trail. I don’t think my website “fail[s] section 2.4” unless you look for strict AAA conformance, but it could certainly improve in these aspects.
(DIR) Post #AL1qJOWQKeoPGkcmYK by Seirdy@pleroma.envs.net
2022-06-30T20:51:16.337753Z
1 likes, 1 repeats
@jookia I spent a long timw evaluating skip links, and even included one at one point!Skip links are not required for guideline 2.4; they make for one of many possible techniques to conform to it.Regarding skipping the nav links:1. I asked multiple blind people who read my site, and none of them used skip links; they use headings and landmarks.2. Heading-based navigation will let you skip the navigation bar since every page follows the navigation bar immediately with a heading level 13. Landmark-based navigation should let you skip the navigation bar because I use a `nav` and `main` element.Furthermore, the navigation bar is...really minimal. It's six elements in a single row, one of which is a link to the homepage. The usability gain for skipping it is far too low. It's not worth picking one of these tradeoffs:1. dealing with hidden/visible elements that can overlap with others2. Adding a seventh navigation link before the rest with a different functionality than the other six3. Adding an empty space above the navbar for a persistent and/or non-overlapping skip link, decreasing the odds of the page heading showing up in the viewport (tiny mobile screens with spatial navigation, e.g. KaiOS Devices)I personally think "skip links" make sense on a great number of sites, but they should't be cargo-culted for sites with very little skippable content that already use a semantic approach to skippable content.@Mayana shared similar thoughts on Fedi. Let me see if I can dig up the relevant thread…
(DIR) Post #AL3qiFFyyQ5Awi1Vw0 by hamblingreen@fosstodon.org
2022-07-01T21:21:18Z
1 likes, 0 repeats
@kop316 it was time to #giveupgithub long ago
(DIR) Post #AL3qiFj3ELKoOrcjFA by kop316@fosstodon.org
2022-07-01T22:11:39Z
0 likes, 0 repeats
@hamblingreen I did as soon as I learned about copilot. All of my stuff is on gitlab.
(DIR) Post #AL3uGNiwIceEukXLt2 by hamblingreen@fosstodon.org
2022-07-01T22:51:27Z
0 likes, 0 repeats
@kop316 i gave up github after i realized it was owned my microsoft lol, now everything of mine is on sourcehut and mirrored on gitlab
(DIR) Post #ALAkQiirRUN1V9VjzE by astrojuanlu@fosstodon.org
2022-07-04T17:48:41Z
0 likes, 0 repeats
Pretty weak arguments to #GiveUpGithub. Lots of reasons to stay: UI that works, low friction, accessibility, lots of value at zero cost (gratis).@conservancy When are copyleft zealots going to value good UI design, accessibility, and products that work for once?
(DIR) Post #ALAkQjA9o0CkroHXX6 by strypey@mastodon.nzoss.nz
2022-07-05T06:03:55Z
0 likes, 0 repeats
@astrojuanlu I agree that the UX of much free code software needs improving and lots of people are working on that. But keep in mind that one thing driving those improvements in the UX of proprietary software is the existential risk of users switching to the free code equivalent. If the vendors of proprietary software can scupper their free code competitors - eg by diluting copyleft protection - then there's a risk that those who sacrifice freedom for convenience will have neither.@conservancy
(DIR) Post #ALDWVx5fpmes1W1R9E by astrojuanlu@fosstodon.org
2022-07-06T14:12:06Z
0 likes, 0 repeats
@strypey @conservancy Copyleft protection has been with us 40 years and the UI/UX of most free-as-in-freedom user applications is still terrible, with no signs of improving. The Copilot thing hardly changes anything.
(DIR) Post #ALE0z4PEiAvpjcyOAK by straw@socks.pinnoto.org
2022-07-06T19:53:53.458715Z
0 likes, 0 repeats
@conservancy thank you for setting an example and acting on your principles :marseyjam:
(DIR) Post #ALEUtEbmrb0GGSydto by strypey@mastodon.nzoss.nz
2022-07-07T01:28:44Z
0 likes, 0 repeats
@astrojuanlu Two things. This ...> the UI/UX of most free-as-in-freedom user applications is still terrible, with no signs of improving. ... is blatantly untrue. Which suggests your comments are based on what suits your argument, not actual observations over that time. Yet you call us zealots?Secondly, you've ignored the actual point, which is the is role of free code competitors as a driver of UX improvements in proprietary products.@conservancy
(DIR) Post #ALEVNBEFzcZuTFFZXU by strypey@mastodon.nzoss.nz
2022-07-07T01:33:08Z
0 likes, 0 repeats
@astrojuanlu Two things. This ...> the UI/UX of most free-as-in-freedom user applications is still terrible, with no signs of improving. ... is blatantly untrue. I can give multiple counter-examples. Your comment is based on what suits your argument, not actual observations over that time. Yet you call us zealots?Secondly, you've ignored the actual point of my post, which is the role of free code competitors as a driver of UX improvements in proprietary products.@conservancy
(DIR) Post #ALJhSF7F8hcvDJwwTI by tk@bbs.kawa-kun.com
2022-07-09T13:43:19.582649Z
0 likes, 0 repeats
@conservancy People started using it for the same reason why they switched from personal homepages and Web forums to social networks like Myspace and Facebook: convenience.
(DIR) Post #AMzGfPUMiRYXVSs5Z2 by dsfgs@activism.openworlds.info
2022-06-30T17:17:06Z
0 likes, 1 repeats
@conservancyThanks for doing this, Software Conservancy. 💖 Its indeed time to #GiveUpGIthub.Thanks also for pointing out that #gitlab.com is problematic, its also CloudFlare. Likewise Sourceforge is CloudFlare and #Atlassian and #Gitter are Amazon.DotCons abound.Gitea seems to work well. Some Gitea instances include:- Disroot- unite.openworlds.info- phreedom.club- mirkodi.techWe will be boosting, for different timezones.#griftHub #deletegIthUB #deCloudFlare
(DIR) Post #AOKnThYbESJvhUJh2m by vandys@noagendasocial.com
2022-10-07T20:01:50Z
0 likes, 0 repeats
@conservancy If you want to consider human-scale source code control outside of Github (i.e., Microsoft), please take a look at:https://fossil-scm.org/It can be run as a daemon and offer remote users, documentation wiki, forum, chat, and issue tracking. From the people who brought you sqlite, it's been rock solid for me.Most of the projects under sources.vsta.org are using it.