GitHubEtc: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
m (Protected "GitHubEtc" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
(5 intermediate revisions by the same user not shown)
Line 5: Line 5:
<blockquote>
<blockquote>


= <font color=black>Sources for code, docs, 3rd party venues. My stuff will always primarily be here. </font> =
= <font color=black>VCS, here and elsewhere </font> =


<blockquote>
<blockquote>
* [http://fisheye.ai-integration.biz FishEye] is used under these special circumstances:
# Contract client projects
# Public codesets which are solely maintained by me or unchanging
# By generic proxy accounts (developer, operator) as which agents of those classes can masquerade.
otherwise
<blockquote>
[https://issues.meansofproduction.biz Bugzilla]* against git.meansofproduction.biz is the default for all active codesets (see discussion for pre 2019 repos).<br>
All SSO users will have access, the account creation is for devops use only.</blockquote>
* [https://github.com/RenRenJuan <b>github</b>], [http://thoughtcrime.biz/git.html old vcs page]  
* [https://github.com/RenRenJuan <b>github</b>], [http://thoughtcrime.biz/git.html old vcs page]  
<blockquote>Go there for current state. I'll fork a pkg at github for these reasons:
<blockquote>Go there for current state. I'll fork a pkg at github for these reasons:
Line 22: Line 13:
     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] is for internal git with
<blockquote>
[https://issues.meansofproduction.biz Bugzilla]* against git.meansofproduction.biz is the default for all active codesets (see discussion for pre 2019 repos).<br>
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.
* [http://stackoverflow.com/users/1005791/ StackOverflow] Two accounts, one predating OpenID and stranded.  
* [http://stackoverflow.com/users/1005791/ StackOverflow] Two accounts, one predating OpenID and stranded.  

Revision as of 07:11, 11 January 2022

VCS, here and elsewhere

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.

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 mainly use this as the biz FB, so not so much, see also CII in the left nav for non-code related web presence.
  • 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.