Difference between revisions of "GitHubEtc"

From Cibernética Americana
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>
 
+
* [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:
 +
<ul><li>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.</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>
 
* [https://fisheye.ai-integration.biz FishEye] is used under these special circumstances:
 
* [https://fisheye.ai-integration.biz FishEye] is used under these special circumstances:
 
# Contract client projects
 
# Contract client projects
Line 17: Line 21:
 
[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 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>
 
All SSO users will have access, the account creation is for devops use only.</blockquote>
otherwise
 
* [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:
 
<ul><li>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.</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>
 
 
* [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 14:04, 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.
  • FishEye is used under these special circumstances:
  1. Contract client projects
  2. Public code which is solely maintained by me or unchanging, accessible by any entitled user.
  3. High entitlement level (developer, operator) access to a larger scope of code, essentially everything that wouldn't compromise security.

with

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

All SSO users will have access, the account creation is for devops use only.

  • 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.