bill-auger

bill-auger pushed to master at bill-auger/scripts

2 weeks ago

bill-auger commented on issue peers/forgefed#51

Purpose of issues and forum

i should add that notabug does not allow incoming email - i would be against the proposal, if only for that reason - i do not want to visit 20 websites each morning just to check messages for all projects that interest me - email makes that extremely convenient - if the socialhub forum still does not allow incoming email, i would still suggest aginast using it for discussions - that is the main reason we moved to feneas

2 months ago

bill-auger commented on issue peers/forgefed#51

Purpose of issues and forum

i struggle to see the problem in this - any confusion expressed here is artificial and easily avoidable; due only to conflating distinct aspects of the development process, namely: design specification and implementation

2 months ago

bill-auger commented on issue peers/forgefed#50

Working Group

that is all perfectly reasonable, but there is really nothing new that needs to be done - the feneas forum was intended to replace the git-pub mailing list for discussions - IIRC, that was already made known to the mailing list

2 months ago

bill-auger pushed to master at peers/forgefed

2 months ago

bill-auger pushed to development at bill-auger/git-status-prompt

3 months ago

bill-auger commented on issue peers/forgefed#34

Who generates the Push activity?

3 months ago

bill-auger pushed to master at bill-auger/scripts

3 months ago

bill-auger commented on issue peers/forgefed#33

Write/design main page

a website will surely exist someday - we discussed it some months ago and decided that it would not be valuable until after the spec was completed and a complete working demo was running - regardless of when a website is created though, in the end, i cant imagine the website presenting any information that is not also, in this repo - i have been intentionally keeping these two READMEs in this repo as brief and concise as possible, precisely to avoid being overly verbose or confusing; and to avoid maintaining essentially duplicate information in multiple places

3 months ago

bill-auger commented on issue peers/forgefed#30

Status

fr33domlover -

3 months ago

bill-auger pushed to development at bill-auger/git-status-prompt

3 months ago

bill-auger pushed to development at bill-auger/git-status-prompt

3 months ago

bill-auger pushed to master at peers/forgefed

  • e15bf281a4 add note about activity-pub to doc/README.md

4 months ago

bill-auger pushed to development at bill-auger/git-status-prompt

4 months ago

bill-auger pushed to development at bill-auger/git-branch-status

4 months ago

bill-auger pushed to master at bill-auger/git-status-prompt

4 months ago

bill-auger pushed to development at bill-auger/git-status-prompt

4 months ago

bill-auger created new branch development at bill-auger/git-status-prompt

4 months ago

bill-auger commented on issue peers/forgefed#30

Status

we wanted to keep the README lean as possible - it was once much more verbose; and much of it was moved into separate documents in the docs/ dir, and much of it (the history section) was deleted entirely

5 months ago

bill-auger pushed to master at peers/forgefed

5 months ago