GitHubEtc: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
Line 7: Line 7:
= <font color=black>VCS, here and elsewhere </font> =
= <font color=black>VCS, here and elsewhere </font> =
<blockquote style="font-size:16px;font-weight:bold;">
<blockquote style="font-size:16px;font-weight:bold;">
git domain migrated to [https://forgejo.meansofproduction.biz/explore forgejo], below not maintained but all checked at last edit.
git domain migrated to [https://forgejo.meansofproduction.biz forgejo], below not maintained but all checked at last edit.
</blockquote>
</blockquote>
<blockquote>
<blockquote>

Revision as of 20:49, 4 December 2023

VCS, here and elsewhere

git domain migrated to forgejo, below not maintained but all checked at last edit.

Go there for current state. I'll fork a pkg at github for these reasons:

  • I make changes for my or a clients purpose which are to be shared. This was done with FireBreath, but I deleted that because it (FireBreath) was based on now obsolete browser plugin stuff.
  • If I have possible development intentions and want to make sure the code is there should I choose to act.
  • FishEye (obsolete once gitea replaces under same apex)

Bugzilla* against git.meansofproduction.biz is the default for all active codesets (see discussion for pre 2019 repos).

SSO access, as usual manual login for devops use only and new account creation is disabled.

  • Source Forge Whatever is there, I'm not maintaining it.
  • StackOverflow Two accounts, one predating OpenID and stranded.
  • LinkedIn I don't use this anymore.
  • Gravatar, associates juan@acm.org with the Lycurgus or hammer and lambda images, or possibly a mugshot c. 4714.

* Used JIRA for most of this century but decommitted March 2019.

See Also

  • (older) Source Codes in "Web Portfolio".
  • w3.n in left navigation.