GitHubEtc: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
<html>
<html>
<div style="background-color: black;  width: 1100px";>
<div style="background-color: black;  width: 1100px";>
<div style="position: relative; top: 10px; left:10px; background-color: antiquewhite;color: black;"></html>
<div style="position: relative; top: 10px; left:10px; background-color: #fff5ee;color: black;"></html>


<blockquote>
<blockquote>

Revision as of 20:10, 7 December 2023

VCS, here and elsewhere

git domain migrated to forgejo, below will not be maintained but worked when page last edited.

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 MoP apex)

Bugzilla* against git.meansofproduction.biz was the default for all active codesets (replaced by issues in forgejo).

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.