Docs/quick-docs
2
0
Fork 0
Code Issues 48 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Migrate package update HOWTO and related docs #10

New issue
Closed
opened 2018-01-23 13:15:44 +00:00 by mattdm · 7 comments
mattdm commented 2018-01-23 13:15:44 +00:00
Contributor
Copy link

Not the packaging guidelines, but

This could either be a subsection of the quick docs, or its own stand-alone document.

Not the packaging guidelines, but * https://fedoraproject.org/wiki/Package_maintenance_guide * https://fedoraproject.org/wiki/Package_update_HOWTO * https://fedoraproject.org/wiki/New_package_process_for_existing_contributors * https://fedoraproject.org/wiki/PackageDB_admin_requests This could either be a subsection of the quick docs, or its own stand-alone document.
bex commented 2018-01-23 13:58:46 +00:00
Copy link

Is this tied to the potential move of the Packaging guidelines?

Is this tied to the potential move of the Packaging guidelines?
mattdm commented 2018-01-23 14:11:43 +00:00
Author
Contributor
Copy link

No, it's separate. Different wiki namespace, and not FPC-owned per se. They could go together but don't have to.

No, it's separate. Different wiki namespace, and not FPC-owned per se. They _could_ go together but don't _have_ to.
ankursinha commented 2018-09-03 19:50:25 +00:00
Contributor
Copy link

If you can tell me where these should go, I can work on them. I could just asciidocsify them to begin with, and then we could move them around wherever they're supposed to go?

I'm a package maintainer too, so I can check the docs for correctness while I'm at it too.

If you can tell me where these should go, I can work on them. I could just asciidocsify them to begin with, and then we could move them around wherever they're supposed to go? I'm a package maintainer too, so I can check the docs for correctness while I'm at it too.
bex commented 2018-09-10 15:16:44 +00:00
Copy link

@ankursinha I suggest we create a new repository for this. If you have a good suggestion for naming, let's use it. If not, we can create one under the fedora-docs namespace.

@ankursinha I suggest we create a new repository for this. If you have a good suggestion for naming, let's use it. If not, we can create one under the fedora-docs namespace.
jflory7 commented 2019-03-19 14:45:12 +00:00
Member
Copy link

@ankursinha @bex @mattdm What is the status of this ticket? I have seen a lot of traffic about packaging guidelines in the docs site, but I'm not sure if it includes these specific pages.

In either case, I agree it makes sense that this change is out of scope for the Fedora Quick Docs. Per the discussion above, I am closing this ticket as out of scope. If there is not a good home for these wiki pages yet, I suggest opening a new meta issue on pagure.io/fedora-docs/docs-fp-o.

@ankursinha @bex @mattdm What is the status of this ticket? I have seen a lot of traffic about packaging guidelines in the docs site, but I'm not sure if it includes these specific pages. In either case, I agree it makes sense that this change is out of scope for the Fedora Quick Docs. Per the discussion above, I am closing this ticket as `out of scope`. If there is not a good home for these wiki pages yet, I suggest opening a new meta issue on [pagure.io/fedora-docs/docs-fp-o](https://pagure.io/fedora-docs/docs-fp-o).
jflory7 commented 2019-03-19 14:45:12 +00:00
Member
Copy link

Metadata Update from @jflory7:

  • Issue close_status updated to: out of scope
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @jflory7**: - Issue close_status updated to: out of scope - Issue status updated to: Closed (was: Open)
jflory7 commented 2019-03-19 14:45:24 +00:00
Member
Copy link

Metadata Update from @jflory7:

  • Issue tagged with: new change
**Metadata Update from @jflory7**: - Issue tagged with: new change
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
bug

Something isn't working

  
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!

  
improvement

Improves on something that already exists

  
needs changes

Needs changes or fixes before closing

  
needs committer review

Needs review by a person with committer privileges or a subject-matter expert (SME)

  
needs info

Extra attention or information needed

  
new change

Adds new capabilities or functionality

  
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

No labels
bug
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
improvement
needs changes
needs committer review
needs info
new change
Priority
awaiting triage
Priority
needs review
Priority
next meeting
Priority
waiting on assignee
Priority
waiting on external
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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: Docs/quick-docs#10
No description provided.
Delete branch "%!s()"

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?