Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. @evan some time ago you queried about what would be a good comms channel for #ActivityPub API.

@evan some time ago you queried about what would be a good comms channel for #ActivityPub API.

Scheduled Pinned Locked Moved Uncategorized
activitypubgithubw3cprocessfedi
6 Posts 2 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • smallcircles@social.coopS This user is from outside of this forum
    smallcircles@social.coopS This user is from outside of this forum
    smallcircles@social.coop
    wrote last edited by
    #1

    @evan some time ago you queried about what would be a good comms channel for #ActivityPub API.

    I have some ideas / recommendations on the #Github repo that the #W3C TF uses.

    - Structure the repo to hold the work of the full task force, not just for the creation of a single specification document.

    - Use GH Discussions for all the general elaboration, feedback collection, etc. The repo forms a self-contained body of work. Move most current Issues in the tracker to become Discussions.

    - Issues are created by task force members, and always represent actionable items. They are tracked on a Project kanban board where the swimlanes represent a simple protocol development #Process with a number of stages.

    Then:

    - Primary comms channel is Discussions.
    - Issues + kanban represent work tracks.
    - Secondary comms channel can be #fedi.

    I'd reserve #SocialCG mailing list to #governance and organizational matters concerning the CG itself, and point mails on other subject to appropriate channel.

    evan@cosocial.caE 1 Reply Last reply
    0
    • smallcircles@social.coopS smallcircles@social.coop

      @evan some time ago you queried about what would be a good comms channel for #ActivityPub API.

      I have some ideas / recommendations on the #Github repo that the #W3C TF uses.

      - Structure the repo to hold the work of the full task force, not just for the creation of a single specification document.

      - Use GH Discussions for all the general elaboration, feedback collection, etc. The repo forms a self-contained body of work. Move most current Issues in the tracker to become Discussions.

      - Issues are created by task force members, and always represent actionable items. They are tracked on a Project kanban board where the swimlanes represent a simple protocol development #Process with a number of stages.

      Then:

      - Primary comms channel is Discussions.
      - Issues + kanban represent work tracks.
      - Secondary comms channel can be #fedi.

      I'd reserve #SocialCG mailing list to #governance and organizational matters concerning the CG itself, and point mails on other subject to appropriate channel.

      evan@cosocial.caE This user is from outside of this forum
      evan@cosocial.caE This user is from outside of this forum
      evan@cosocial.ca
      wrote last edited by
      #2

      @smallcircles I'm not sure. It's pretty important for me to track user stories as issues -- that's been the best way to get things done in task forces so far.

      smallcircles@social.coopS 1 Reply Last reply
      1
      0
      • R relay@relay.mycrowd.ca shared this topic
      • evan@cosocial.caE evan@cosocial.ca

        @smallcircles I'm not sure. It's pretty important for me to track user stories as issues -- that's been the best way to get things done in task forces so far.

        smallcircles@social.coopS This user is from outside of this forum
        smallcircles@social.coopS This user is from outside of this forum
        smallcircles@social.coop
        wrote last edited by
        #3

        @evan is it an official list, or is it a brainstormed list in an ideation phase?

        smallcircles@social.coopS 1 Reply Last reply
        0
        • smallcircles@social.coopS smallcircles@social.coop

          @evan is it an official list, or is it a brainstormed list in an ideation phase?

          smallcircles@social.coopS This user is from outside of this forum
          smallcircles@social.coopS This user is from outside of this forum
          smallcircles@social.coop
          wrote last edited by
          #4

          @evan

          Note that my proposal reserves the issue tracker for the 'best way to get things done', and filters out the much more chaotic discussion environment to be in a separate place, yet part of the repo.

          If User Stories should be issue tracked, that's fine. But perhaps when a user story is still a vague idea, or something someone posted off the cuff, it starts its lifecycle in Discussions.

          smallcircles@social.coopS 1 Reply Last reply
          0
          • smallcircles@social.coopS smallcircles@social.coop

            @evan

            Note that my proposal reserves the issue tracker for the 'best way to get things done', and filters out the much more chaotic discussion environment to be in a separate place, yet part of the repo.

            If User Stories should be issue tracked, that's fine. But perhaps when a user story is still a vague idea, or something someone posted off the cuff, it starts its lifecycle in Discussions.

            smallcircles@social.coopS This user is from outside of this forum
            smallcircles@social.coopS This user is from outside of this forum
            smallcircles@social.coop
            wrote last edited by
            #5

            @evan

            I gave an elaborate follow-up to the #ActivityPub API protocol design issue, where I also cross-ref'ed this thread..

            Link Preview Image
            Protocol design · Issue #66 · swicg/activitypub-api

            (This issue is created in follow-up of #63 Avoid misconception and #4 Rate limiting, and related fedi thread.) Avoiding misconceptions: What is a profile? I think my overarching concern is that the ActivityPub API specification doesn't b...

            favicon

            GitHub (github.com)

            evan@cosocial.caE 1 Reply Last reply
            0
            • smallcircles@social.coopS smallcircles@social.coop

              @evan

              I gave an elaborate follow-up to the #ActivityPub API protocol design issue, where I also cross-ref'ed this thread..

              Link Preview Image
              Protocol design · Issue #66 · swicg/activitypub-api

              (This issue is created in follow-up of #63 Avoid misconception and #4 Rate limiting, and related fedi thread.) Avoiding misconceptions: What is a profile? I think my overarching concern is that the ActivityPub API specification doesn't b...

              favicon

              GitHub (github.com)

              evan@cosocial.caE This user is from outside of this forum
              evan@cosocial.caE This user is from outside of this forum
              evan@cosocial.ca
              wrote last edited by
              #6

              @smallcircles OK, great. Let's try to keep the conversations there instead of here, so everyone can participate.

              1 Reply Last reply
              1
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups