Difference between revisions of "GitHubEtc"

From Cibernética Americana
 
(28 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
<blockquote>
 
<blockquote>
  
= <font color=black>Code, etc venues, my stuff will always primarily be here, in JIRA, etc. </font> =
+
= <font color=black>Sources for code, docs, 3rd party venues. My stuff will always primarily be here. </font> =
  
 
<blockquote>
 
<blockquote>
  
# [http://fisheye.ai-integration.biz FishEye] used with [http://jira.ai-integration.biz JIRA] against git.meansofproduction.biz .
+
* [http://fisheye.ai-integration.biz FishEye] is used under these special circumstances:
# [https://github.com/RenRenJuan <b>github</b>], [http://thoughtcrime.biz/git.html old vcs page]  
+
# 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]  
 
<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:
 
  <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
 
  <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>
 
     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>
# [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.  
# [http://www.linkedin.com/pub/juan-daugherty/36/b3/101/ 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.
+
* [http://www.linkedin.com/pub/juan-daugherty/36/b3/101/ 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 shirt and tie image, c. 1996.
+
* Gravatar, associates juan@acm.org with the Lycurgus or hammer and lambda images, or possibly a mugshot c. 4714.
  
 +
&#42; Used [http://jira.ai-integration.biz JIRA] for most of this century but decommitted March 2019.
 
</blockquote>
 
</blockquote>
  
 
= <font color=black>See Also</font> =
 
= <font color=black>See Also</font> =
* (older) <b><font color=black>Source Codes</font> in "Web Portfolio" in wiki nav to your left.</b>
+
* (older) <b><font color=black>Source Codes</font> in "[https://meansofproduction.biz/eg/index.php/Programming_Practice(HTML5) Web Portfolio]".</b>
 
* w3.n in left navigation.
 
* w3.n in left navigation.
 
</blockquote>
 
</blockquote>

Latest revision as of 01:15, 23 May 2020

Sources for code, docs, 3rd party venues. My stuff will always primarily be here.

  • FishEye is used under these special circumstances:
  1. Contract client projects
  2. Public codesets which are solely maintained by me or unchanging
  3. By generic proxy accounts (developer, operator) as which agents of those classes can masquerade.

otherwise

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.

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