Council/council-docs
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

Update council docs for Discourse (and Matrix, while I'm at it) #138

Closed
mattdm wants to merge 5 commits from discussion into main
pull from: discussion
merge into: Council:main
Conversation 9 Commits 5 Files changed 3 +70 -25
mattdm commented 2022-01-02 20:10:33 +00:00
Contributor
Copy link

This is mostly a significant rewrite of contact.adoc, plus some other changes in other pages.

This is mostly a significant rewrite of `contact.adoc`, plus some other changes in other pages.
bcotton commented 2022-01-06 16:45:35 +00:00
Contributor
Copy link

rebased onto ee96a2d0c7

rebased onto ee96a2d0c70fedfa3191206345ee1fe6cb478ff1
bcotton commented 2022-01-06 16:48:42 +00:00
Contributor
Copy link

I don't think this qualifies for inclusion here. I'd argue it's not a change in meaning, just a change in implementation of existing meaning. "Did the Council have to vote on this change?" is a reasonable bar, IMO

I don't think this qualifies for inclusion here. I'd argue it's not a change in meaning, just a change in implementation of existing meaning. "Did the Council have to vote on this change?" is a reasonable bar, IMO
bcotton commented 2022-01-06 16:51:38 +00:00
Contributor
Copy link

We should take this opportunity to tighten the language a bit. "If you have a specific proposal for the Council..." is too tight, but it'd be helpful to make it more clear that tickets are for actions, not discussions. I'd rather have people start "this should be a ticket" threads on Discussion than open "this should be a Discussion thread" tickets, if that makes sense.

We should take this opportunity to tighten the language a bit. "If you have a specific proposal for the Council..." is *too* tight, but it'd be helpful to make it more clear that tickets are for actions, not discussions. I'd rather have people start "this should be a ticket" threads on Discussion than open "this should be a Discussion thread" tickets, if that makes sense.
mattdm commented 2022-01-10 22:44:45 +00:00
Author
Contributor
Copy link

1 new commit added

  • This is just a change of implementation, not governing policy
**1 new commit added** * ``This is just a change of implementation, not governing policy``
mattdm commented 2022-01-10 22:45:14 +00:00
Author
Contributor
Copy link

1 new commit added

  • new wording encouraging discussion over filing tickets
**1 new commit added** * ``new wording encouraging discussion over filing tickets``
bcotton commented 2022-03-02 16:56:17 +00:00
Contributor
Copy link

+1 from me

+1 from me
jflory7 commented 2023-02-07 17:28:24 +00:00
Contributor
Copy link

Metadata Update from @jflory7:

  • Pull-request tagged with: needs changes, type - existing docs
  • Request assigned
**Metadata Update from @jflory7**: - Pull-request tagged with: needs changes, type - existing docs - Request assigned
jflory7 commented 2023-02-08 15:31:56 +00:00
Contributor
Copy link

This Pull Request is over one year old and has a merge conflict with changes introduced during the 2023 Council hackfest in Frankfurt, Germany.

I superseded this Pull Request with a new one. See #174 for the final changeset.

This Pull Request is over one year old and has a merge conflict with changes introduced during the [2023 Council hackfest](https://fedoraproject.org/wiki/Council/2023_Hackfest) in Frankfurt, Germany. I superseded this Pull Request with a new one. See #174 for the final changeset.
jflory7 commented 2023-02-08 15:32:04 +00:00
Contributor
Copy link

Pull-Request has been closed by jflory7

Pull-Request has been closed by jflory7

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
blocked

Progress blocked by another task or issue

  
Closed As
complete
Closed with the reason of complete

  
Closed As
duplicate
Closed with the reason of duplicate

  
Closed As
insufficient data
Closed with the reason of insufficient data

  
Closed As
moved
Closed with the reason of moved

  
Closed As
not possible
Closed with the reason of not possible

  
Closed As
out of scope
Closed with the reason of out of scope

  
Closed As
stale
Closed with the reason of stale

  
good first issue

Good for newcomers (if you want to get involved, try working on one of these!)

  
help wanted

Anyone is welcome to help us with this!

  
needs changes

Needs changes or fixes before closing

  
needs feedback

Extra attention or feedback needed

  
needs testing

Needs testing or QA before closing

  
Priority
awaiting triage
Priority of awaiting triage

  
Priority
needs review
Priority of needs review

  
Priority
next meeting
Priority of next meeting

  
Priority
waiting on assignee
Priority of waiting on assignee

  
Priority
waiting on external
Priority of waiting on external

  
type - dev tools

Related to developer tooling or build scripts

  
type - existing docs

Improves or changes existing documentation

  
type - new docs

Adds or creates new documentation

No labels
blocked
Closed As
complete
Closed As
duplicate
Closed As
insufficient data
Closed As
moved
Closed As
not possible
Closed As
out of scope
Closed As
stale
good first issue
help wanted
needs changes
needs feedback
needs testing
Priority
awaiting triage
Priority
needs review
Priority
next meeting
Priority
waiting on assignee
Priority
waiting on external
type - dev tools
type - existing docs
type - new docs
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Council/council-docs#138
No description provided.
Delete branch "discussion"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?