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


    smallcircles@social.coopS
    38
    0

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

    I have some ideas / recommendations on the repo that the 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 with a number of stages.

    Then:

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

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

  • evan@cosocial.caE
    197
    0

    @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
    38
    0

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

  • smallcircles@social.coopS
    38
    0

    @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
    38
    0

    @evan

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

  • evan@cosocial.caE
    197
    0

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


Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy

Il server utilizzato è quello di Webdock, in Danimarca. Se volete provarlo potete ottenere il 20% di sconto con questo link e noi riceveremo un aiuto sotto forma di credito da usare proprio per mantenere Citiverse.