GitHubEtc: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(21 intermediate revisions by the same user not shown)
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>


= <font color=black>VCS, here and elsewhere </font> =
= <font color=black><span class=plainlinks>[[:en:Version control#History | VCS]]</span> trail of tears </font> =
<blockquote style="font-size:16px;font-weight:bold;">
<blockquote style="color:purple;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 <span style="background-color:white;">forgejo</span>] <br>consolidating function previously fulfilled by fisheye and bugzilla<br>
<span style="font-size:10px;">below preserved but not maintained</span>
</blockquote>
</blockquote>
<blockquote>
<blockquote>
Line 15: Line 16:
     now obsolete browser plugin stuff.</li>
     now obsolete browser plugin stuff.</li>
     <li>If I have possible development intentions and want to make sure the code is there should I choose to act. </li></ul></blockquote>
     <li>If I have possible development intentions and want to make sure the code is there should I choose to act. </li></ul></blockquote>
* [https://fisheye.ai-integration.biz FishEye] (obsolete once gitea replaces under same apex)
* [https://fisheye.ai-integration.biz FishEye] (obsolete once gitea replaces under MoP apex)
<blockquote>
<blockquote>
[https://issues.meansofproduction.biz Bugzilla]* against git.meansofproduction.biz is the default for all active codesets (see discussion for pre 2019 repos).<br>
[https://issues.meansofproduction.biz Bugzilla]* against git.meansofproduction.biz was the default for all active codesets (replaced by issues in forgejo).<br>
SSO access, as usual manual login for devops use only and new account creation is disabled.</blockquote>
SSO access, as usual manual login for devops use only and new account creation is disabled.</blockquote>
* [http://sourceforge.net/users/kyberuserid Source Forge] Whatever is there, I'm not maintaining it.
* [http://sourceforge.net/users/kyberuserid Source Forge] Whatever is there, I'm not maintaining it.

Latest revision as of 03:09, 12 January 2024

VCS trail of tears

git domain migrated to forgejo
consolidating function previously fulfilled by fisheye and bugzilla
below preserved but not maintained

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.