WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Data-Integrity-Group/WelcomeNewUsers

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 

Repository files navigation

WelcomeNewUsers

  • SRED text
    • ...

Most of the current work is part of an Experimental Development process that is exploring the interactions between a Real and a Virtual (Socercy) author.

The obvious goal is to automate as much of the development process as possible and to resolve apparent issues, such as:

  • the need for a common subset of conventions that can co-exist in the various envbironments employed to achieve Best-of-Class performance

    • At this time, these include:
      • GitHub inself (to manage complex interactions among the various development environments),
      • POE as an entry point to a few of the most useful AI tools and as an entry point to the rapidly emerging ones,
      • TiddlyWiki and its platform variants
      • Python as a dominant programming language
      • the aggressive use of UniCode to enhance Information density given the need to encode data in a minimum of four dimensions consisting of:
        • Q - an initial Queue used tp capture values prior to encoding them
        • R - a subjective Ranking of the relative importance of Queued items
        • S - Spatial coordinates generally comprized of latiture and longitude pairs
        • T - Time values that are part of a 10 element Scope continuum
  • Illustrate the practical need for this Experimental Development that is an inherent part of refining the ability to deliver improved Voting services to the considerable majority of Canada's Electoral Authorities.


2025-04:

...


2025-03:

...

  • increase the focus on OnTheList ( use headings as HTML anchors ( temporarily ?)
    • suggest ( and assign ) Business Case responsibilitiy
      • provide a loom account to Andrea
        • guide her with a statement of the relative priorities
          • of (just) two Tasks (initially)
      • re-test this at DiigoH
      • immediately after -02-27
        • emphasize that this is slipping ever more due to delays like Loom.
          • always chasing candyland rainbows
            • 0226: loom license now acquired
              • needs verification
    • 0303: this should likely be a separate (external ?)page
      • DiigoH outliner?

2025-02:

  • Try resurecting this repo
    • perhaps adding LsT reports to PbWorks will help
      • encourage this and see if it can be delegated to a bot - perhaps as a better form of Scrapping
        • this should be tried even if just for a small section
      • Loom and Lz may be informative
        • ask for a training demo - scheduled for -02-17
          • reminded LzT - insisted on a new tine
            • postponed the 09:00 session until 13:00 - then failed to initiate via teams as promised.
        • create a Team/Loom account - this can be a routine Df/account
          • use this as an opportunity for a Corporate card review
            • confirm/Deny the limits management changes at BMO/MC
    • review the CAD/USD product DanS has suggested
      • test exhaustively in order the refine the Banking Operations methodologies we use actively
        • the documentation is now available

2022-08

  • 11-17: Consider which repos to enable for TreeFort

  • -08-14: Anticipate the needs of newcomers.

    • -08-20: Navigation will be a significant impediment.
      • 2025-02-24 indentation works well with either '-' or '*' ( even if intermingled )
      • Evaluate both Notion & Hypothesis as possible mitigations
        • Notion may be the more promising, but may hit restictions even for Authorized shares.
        • editView in GitHub seems to allow Hypothesis to function
  • -08-09: A HoneyPost design is needed.

    • Can PDF's be uploaded into GitHub?
      • if not, I may need to make use of my OneDrive quota
        • the Publix version, since DataFix admnin must get involved for the corporate version.
    • Check ChrisA's work to see if he inter-twingles GitHub and Hypotesis
      • ...
  • -08-07: confirmed MAIN

2022-07:

  • starting to integrate more styling via a ReMarkable tablet

2022-06:

  • -06-22: focused on a couple of Business challenges for the first half of this week.
  • -06-20: exploring GIST interactions for a streamlined user experience
  • -06-19: reviewing metrics that may be useful feedback
    • these should be merged with those from LinkedIn and Twitter
  • -06-18: linked DigCa @ GitHub & AdManCa @ Notion
    • Interface to LinkedIn & Twitter
  • -06-12: slowly re-connecting
  • -06-02: EmbOn43 precludes regular changes pre -06-06. Exceptions may be noted.
    • monthly maintenance is needed
  • -05-29: There is a diminished Pulse issue, indicating this concern may be passe.
    • -05-27: Closed
    • -05-26: confirming
  • Some of this material needs to be relocated into shared Doc(s) file(s)
    • pulse considerations can be ingored for now since deletions show
  • NAMMU discussions
    • chat with Patrick regarding delivery tracking for Emb(s)
      • this should benefit from the Bureau RFP work
        • issue an RFP to the Bureaux for MailFail on behalf of EmbCa(s) with a duration of 2 Events+
      • anticipate TsAndCs that may be requested
    • ESDB collaboration as a OnceAndDone effort.
      • confirmed Mike will work thru an Account Manager for EmbCa
        • he does, however, remain fixed in HIS views
        • but may soften on Data
  • refine TapestryH (TasksLegoBlocks) plans
    • consider
        • raw SSV suppport within HTML seems more than adequate for qyuick&dirty sketches.
  • disemination via
  • consider the Primary/Secondary & online/offline issues
  • AdManCa RFP issue
    • AddressCertification
  • CPC discussions
  • ...

prior notes

  • key features to document include:
    • MailFail notifications
      • intended recipient
      • Mailer
      • mail services provider
      • NAMMU/CPC
    • AI (preliminary) approved self-identification
      • Automated recognition and reliable certification
        • dpl chat garned "That approach to APIU development makes sense."
        • Joshua: API development is reduced with a StateDd
  • promote GeoCoding as part of ID = 1/2Name + 1/2Por
    • PoR is P(lace) o(f) r(esidence)
      • a Canadian twist is 'nearestTower+vector" as an alternative to (public domain) civic Address
  • Enhance this material to support a petition for NAMMU recognition
  • suggest use of PlusCodes, rather than traditional Addresses
    • and explain their importance & benefits
  • reference whatThreeWords

About

...

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published